Fix rollout health-check timeouts from transient container states

[arjunkomath]

Problem

Rollouts intermittently failed with health_check_timeout even though every container was running. Verified against rollout 4e8afd45: during a fast deploy burst, an agent status report snapshotted containers still in podman's created state (podman ps -a includes them). The agent mapped any non-running/non-exited state to "stopped", and the control plane moved those deployments to observedPhase: "stopped" — a phase non-serverless deployments never recovered from, and one that emits no resource/status-changed event. The rollout's waitForEvent then timed out after 10 minutes and rolled back.

Fix

Agent (reporting.go): skip containers in transient states when building the status report, mirroring the existing log-collector filter. A created container is simply reported on a later tick once it settles.

Control plane (agent-status.ts): the stale-stopped restore path is no longer serverless-only — any runtimeDesiredState: "running" deployment stuck in stopped/sleeping gets promoted back to ready when its container reports running. When the promotion reaches a ready phase and the deployment belongs to a rollout, it emits resource/status-changed and a rollout log so the waiting workflow unblocks immediately instead of timing out. Helper renamed getStaleStoppedServerlessReportUpdate → getStaleStoppedReportUpdate.

Testing

• Added a regression test: a non-serverless stopped-phase deployment with a running container is promoted and notifies its rollout via Inngest.
• bun run test: 288 tests pass (44 files)
• go build ./... && go vet clean, bunx tsc --noEmit clean

🤖 Generated with Claude Code

[github-actions]

React Doctor found no issues. 🎉

⚠️ Warning: .github/workflows/react-doctor.yml is configured incorrectly. See below to fix.

React Doctor compares against main to report only the issues this pull request introduces. This run couldn't complete that comparison (usually a shallow CI checkout with no merge base), so it listed every issue in the changed files, including ones that already existed on main.

Add fetch-depth: 0 to the actions/checkout step in .github/workflows/react-doctor.yml so the checkout includes the history React Doctor needs:

 jobs:
   react-doctor:
     steps:
       - uses: actions/checkout@v5
+        with:
+          fetch-depth: 0

       - uses: millionco/react-doctor@v2

To silence this warning, set silence-missing-baseline-warning: true on the React Doctor action.

_{Reviewed by React Doctor for commit df568c5.}