[NathanFlurry]

• Move to RivetKit and Rivet Engine 3.0.2 and remove the serverless path (runner configs, Engine callbacks, RIVETKIT_RUNTIME_MODE=serverless).
• Run each app's active RivetKit release as an always-on envoy in an agentOS VM, owned by the app's private actor. The guest exits are restarted with backoff.
• Roll out new releases by starting the new envoy at a higher node version, waiting for it to connect, then draining the previous one.
• Add a recovery loop on every host that wakes RivetKit apps once a minute, so an app whose host process died restarts its envoy elsewhere.
• Add startDynamicAppsHost() for hosts to call at boot, and use it in the examples.
• Retry the Engine's structured overloaded refusals during namespace and pool provisioning.
• RivetKit apps must now export registry and no longer mount registry.handler(); update the skill, examples, README, and docs.
• Extend the end-to-end test with guest crash recovery, a redeploy rollout, and a host failover scenario (pnpm test:e2e:failover).

🤖 Generated with Claude Code

[railway-app]

🚅 Environment dynamic-apps-pr-307 in rivet-frontend has no services deployed.

3 services not affected by this PR

• kitchen-sink
• mcp-hub
• sentry-tunnel

---

🚅 Deployed to the dynamic-apps-pr-307 environment in secure-exec

Service	Status	Web	Updated
secure-exec	❌ Build Failed (View Logs)	Web	Nov 5, 2026 at 6:56 am UTC