[NathanFlurry]

• Map exact branches to existing Rivet v3 clusters through the official CLI; preserve pool settings and skip unmapped branches unless Fly is enabled.
• Run each Fly preview on one Machine with the automatic local engine, a 20 GiB persistent volume, and stop/wake support. Increasing the requested size grows existing storage without replacing it; PR closure cleans up the preview.
• Include one vanilla counter app and Dockerfile for both providers, using plain registry.start(). Document setup, migration, and release prerequisites.
• Validation: 21 unit tests, TypeScript checks, and GitHub CI pass, including real container cold-start/restart actor calls. Live Fly verified volume growth from 10 to 20 GiB, preserved state, stop/wake, and idempotent cleanup.
• Live Cloud deployment through MCP and the action entrypoint passed upload, rollout, app HTTP checks, and SDK actor persistence. The shared vanilla example also passed Cloud HTTP and actor checks with unchanged source and Dockerfile. MCP actor listing remains unverified because it returns HTTP 501.
• Release prerequisites: publish the v3 CLI and RivetKit artifacts containing the existing startup-overload retry fix. Published 3.0.0-preview.4 exited once on a temporary local storage overload during Fly redeployment; Fly restarted it and state survived. All seven relevant regression tests pass on current v3 source. Revalidate the updated package before release.