[NathanFlurry]

• Map exact branches to existing Rivet v3 Cloud clusters using the official CLI, preserving pool settings.
• Deploy optional previews on one Machine with a 20 GiB volume, automatic local Engine startup, sleep/wake, and cleanup on PR closure.
• Report deployment, skipped, failure, cancellation, and cleanup states in a consistent PR comment; identify the provider only while deploying.
• Document the v2 action migration and pin the shared example to published RivetKit 3.0.1-preview.2 with plain registry.start(), no dependency overrides, and no separate metrics listener.
• Validation: 26 unit tests and typechecking pass. Real consumer workflows verified Cloud rollout and preview create/redeploy/cleanup; the published SDK passed actor calls and persistent stop/wake cycles. Cold actor reads can take about a minute.