Context status + a fresh download URL

Status of an uploaded context plus, once finalized, a presigned download url - the import path for bytes that exist only in your sandbox (a prepared dataset, an eval set, a wheel): create_context → PUT → finalize_context → get_context, then land it on a node with one command - run_command(node, "curl -o ~/data.tar.zst '<url>'", detach: true) for the big ones, tar xf if you tarred it - the node has the bandwidth and the disk; nothing rides through MCP. Returns {status: "ready", size_bytes, sha256, download: {url, expires_at}}; the url expires in minutes (this is a read: re-call for a fresh one), the object lives ~30 days unless you delete_context it sooner (which also answers here: {status: "deleted", deleted_at, bytes_deleted_at once the store confirms removal}). One finalized upload is reusable: curl it onto five nodes, build a job image from it - same object. While a big finalize runs you may see {status: "finalizing"} (or "uploading" from the other api instance) - keep polling until ready. {status: "failed", error} means the last finalize attempt died server-side: the uploaded parts are untouched - re-call finalize_context to retry. The download url points at the object store's own hostname (currently fly.storage.tigris.dev), NOT the API's - an egress allowlist needs that host too.