The API on krow-2 is down on a startup guard, and the fix is two environment
variables. Written down rather than left in a chat log, in the same shape as
deploy-b6f8655.md: what is being deployed, what was actually verified before
claiming it works, the rollout, a smoke test, and rollback.
The smoke test insists on one real agent run. Boot and /health both pass with a
broken model configuration — that is precisely how the current outage stayed
invisible until run time — so a health check alone is not evidence the deploy
worked. Includes the symptom-to-cause table for the four failures this rollout
can actually produce.
Records what the preflight covered: the production image built and booted under
APP_ENV=production against a TLS Postgres, 11 migrations applied, seed and 9
agents imported, login, a real Groq-backed run terminating Completed, and SSE
streaming. 62 endpoints is written down as the expected number because two
fewer is the signature of a missing credential.
Not executed. No working SSH to that host from here, and a production rollout
wants the operator watching.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PJvibeSc1JYXjatankqM1g
