What problem does it solve? Porting a Cloudflare Sandbox application from the stable @cloudflare/sandbox SDK to the @next 1.0 preview involves breaking API changes—removed sessions, handle-based exec, new terminal and interpreter patterns, and incompatible container rollout behavior—that are easy to get wrong without a structured procedure. ## Core Features & Use Cases - Guided migration workflow: Audit the codebase with ready-made grep patterns, clarify cutover decisions with the user, upgrade package and container image, then validate the result. - Replacement map and code shapes: Concrete before/after TypeScript snippets for exec handles, terminals, interpreters, and git operations, plus a stable-to-next API mapping table. - Safe production cutover: Enforces matching Worker/image versions and immediate container rollout to avoid a broken mixed-protocol window. - Use Case: You maintain a Worker using sandbox.exec with sessions and want to move to @cloudflare/sandbox@next; the skill audits your code, rewrites each call site, and walks you through a safe deploy. ## Quick Start Migrate my Cloudflare Sandbox app from the stable SDK to @cloudflare/sandbox@next, auditing the code and updating each API call site.