@tinycloud/node-sdk 3.12.0-beta.3 → 3.12.0-beta.4

package/README.md

@@ -8,7 +8,7 @@ Routing uses the complete space URI, not a short space name or a single account-
 
 Encryption is resolved separately: descriptor reads, network creation, and decrypt requests use the signed `encryptionNode`, including its invocation audience. A data-space host does not become an encryption destination, or vice versa.
 
-Explicit `host`, saved-profile hosts, local discovery, and new-user defaults are onboarding hints. The lookup checks v2 first, then v1 to distinguish absence from an existing v1 registration. Cold HTTP5xx, transport errors and timeouts without cached or remembered registration retain configured/default-host compatibility, including direct Core callers without a cache adapter; the verdict is marked `offline`, not genuine registry absence. HTTP4xx refusals, v1-only registrations, corrupt caches, invalid responses, remembered registrations, empty registered memberships and missing encryption destinations never authorize fallback. Signed strings are validated without rewriting them.
+Explicit `host`, saved-profile hosts, local discovery, and new-user defaults are onboarding hints only after the reachable registry confirms genuine absence. The lookup checks v2 first, then v1 to distinguish absence from an existing v1 registration. Cold HTTP5xx, transport errors and timeouts without saved settings refuse live routing with `registry_unavailable`; neither a configured/default host nor `onNodeNotFound` may override that refusal. Low-level background lookup may still describe an offline unregistered verdict, but policy lookups do not authorize it. HTTP4xx refusals, v1-only registrations, corrupt caches, invalid responses, remembered registrations, empty registered memberships and missing encryption destinations never authorize fallback. Signed strings are validated without rewriting them.
 
 `NodeNotRespondingError` has code `NODE_NOT_RESPONDING`. Registry refusals and node-identity mismatches remain distinct errors. Multi-node writes are not atomic: `PartialNodeWriteError` exposes `succeeded` URLs and `failed` destinations/statuses/causes so callers do not mistake incomplete writes for success.
 
@@ -32,7 +32,7 @@ Each caller retains registration evidence observed before joining an in-flight r
 
 Restored host hints install alongside the replacement session and service graph. Subsequent public delegation preparation uses that installed hint when fresh routing permits onboarding; verified signed destinations still take precedence.
 
-Actual cold fallback logs `registry unavailable; using the default node`; warm fallback logs `Storage settings are unreachable; using cached settings checked less than 1 hour ago.` Each diagnostic is emitted once per owner/client cache and fallback kind, only after a route is selected. `onRegistryFallback(reason, code?)` collects these value-free diagnostics instead of the default console warning; semantic codes are `using_default_node` and `using_cached_settings`. Background refresh alone does not warn.
+With no saved settings, an unreachable registry refuses before data requests; it does not select a default host or emit a default-host warning. Warm fallback still logs `Storage settings are unreachable; using cached settings checked less than 1 hour ago.` once per owner/client cache after selecting the verified cached route. `onRegistryFallback(reason, code?)` collects that value-free diagnostic instead of the default console warning, using `using_cached_settings`. Background refresh alone does not warn. CLI errors keep `REGISTRY_UNAVAILABLE` and explain that no settings are saved on this computer.
 
 This is a client cache: a node that performs online registry admission still needs its own registry connectivity. It is not a whole-service-outage guarantee.
 

package/dist/core.cjs

@@ -6590,8 +6590,7 @@ var _TinyCloudNode = class _TinyCloudNode {
       stagedSessionExpiry = signedExpiry ?? persistedPolicyExpiry ?? persistedExpiry(void 0);
     }
     const restoreHints = this.explicitHost ? [this.explicitHost] : sessionData.tinycloudHosts ?? [];
-    const resolvedHost = this.config.replication?.enabled ? (await this.routingDestinations(sessionData.spaceId, "read", restoreHints))[0]?.url : void 0;
-    const stagedHost = resolvedHost ?? (0, import_sdk_core11.exactHttpOrigin)(restoreHints[0] ?? this.config.host, "restored host hint");
+    const stagedHost = (0, import_sdk_core11.exactHttpOrigin)(restoreHints[0] ?? this.config.host, "restored host hint");
     let restoredNodeFeatures;
     let replicaProtocolMismatch = false;
     if (this.config.replication?.enabled) {