fix(tcloud): support Sandbox 0.60 consumers

[drewstone]

Problem

The canonical Runtime consumer installs Sandbox 0.60.0, while Knowledge 18 loads tcloud 0.8.1. tcloud's Sandbox range ends below 0.60.0, so npm must install a second Sandbox 0.59.0. Runtime's existing strict packed-consumer gate rejects this duplicate.

Change

Extend the existing Sandbox dependency range from >=0.58.4 <0.60.0 to >=0.58.4 <0.61.0.
Keep the supported floor and earlier minors.
Select public SDK 0.60.0 in the frozen development lockfile and prepare the normal tcloud 0.8.2 patch release.
No application source, route, credential handling or release gate changes.

Proof

• Built tcloud and its workspace dependency using the maintained release build command.
• Verified the installed development SDK is exactly 0.60.0.
• 297 package tests passed; 32 existing integration cases remain skipped without their external environments.
• The maintained first-party dependency-range check passed.
• Causal old-package failure is retained in /tmp/runtime-unassessed-child-release-package-20261001.log on GTR: root SDK 0.60.0 plus tcloud's nested SDK 0.59.0.
• Final-head SDK frozen-workspace CI passed.
• A fresh strict npm consumer installs Knowledge 18, packed tcloud 0.8.2, public SDK 0.60.0 and Interface 2.16.0. Root and Knowledge-to-tcloud resolution reach the same physical Sandbox module; both public tcloud entrypoints import successfully. No inference calls.
• Candidate tarball SHA256: be8710613afa9580e4f640f5e63d16686496cb0dc23faac31098964238b7e50a.
• The existing release workflow verifies the exact final archive before publishing.

After normal merge, publish the exact merged source through the existing @tangle-network/tcloud@0.8.2 tag workflow. Runtime release PR1493 then reruns its unchanged strict public consumer gate. Evidence is retained under /mnt/traces/frontier-qualification-20260930/tcloud-sandbox060-cohort-20261001.

[tangletools]

✅ Auto-approved PR — 54b26772

Blanket team auto-approval is intentional. The merge gates are CI and codex-p1.
No automated review runs on this PR. This approval rests on the rule above alone.

_{tangletools · auto-approval · reason: blanket_auto_approve · 2026-10-01T14:25:46Z}