What problem does it solve? Cloudflare Sandbox apps built on the stable @cloudflare/sandbox SDK use APIs (sessions, transport settings, buffered exec, gitCheckout) that are removed or reshaped in the SDK 1.0 preview, and a careless upgrade breaks production because stable and @next control protocols are incompatible. ## Core Features & Use Cases - Guided migration workflow: Audit the codebase with ready-made grep patterns, clarify cutover decisions with the user, upgrade the package and container image, then validate the result. - Replacement map: A stable-to-@next API mapping covering exec handles, terminals, interpreters, sessions, git operations, and kill signals, with code shapes for each area. - Safe production cutover: Enforces matching Worker/image versions and immediate container rollout to avoid a broken mixed-protocol window. - Use Case: You have a Worker using await sandbox.exec("npm test") and named sessions; the skill audits every call site, rewrites them to argv-based exec with process handles, and deploys with --containers-rollout=immediate. ## Quick Start Migrate my Cloudflare Sandbox Worker from the stable @cloudflare/sandbox package to the @next SDK 1.0 preview, auditing my code and updating the package, Dockerfile, and API calls.