Expose persistent sandbox timeout semantics in SDKs

[motatoes]

Context

Clawputer-style managed agents need long-lived OpenComputer sandboxes. The platform already treats timeout: 0 as persistent/no automatic idle hibernation, and the TypeScript/Python SDKs expose numeric timeout fields.

Problem

Using 0 as the public SDK signal is easy to miss and easy to confuse with an omitted timeout. We should make the SDK surface explicit enough for managed-agent callers to request persistent sandboxes intentionally.

Proposed Follow-Up

• Consider accepting semantic timeout values such as "persistent" or "never" in TypeScript and Python SDK create/wake/set-timeout paths, normalizing them to 0 at the HTTP boundary.
• Check consistency between Sandbox.create, Sandbox.createFromCheckpoint, wake, and setTimeout / set_timeout defaults.
• Update SDK docs and examples so managed-agent integrations do not rely on magic 0.

Notes

This is intentionally deferred. The managed Claw API can pass numeric timeout: 0 for now.