Document rolling-target readiness in the deploy runbook

Co-Authored-By: Christopher David <chris@openagents.com>

Co-Authored-By

Christopher David <chris@openagents.com>

Deploy story

What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.

built

21 modules in 106.8 s

deployed

live · 21 modules on 3 nodes · push→live —

deployed

needs_rolling_replace · 21 modules on 0 nodes · push→live —

Changed files

• modified docs/operations/production-deploy-runbook.md

Diff

1 file changed, +9 -0

     --health-checks sarah-hc-tcp --global-health-checks

   ```

With the HTTP check active, a structural rolling replacement depends on

boot convergence accepting a node that runs the newest

`needs_rolling_replace` target's image. Nodes replaced before settlement

report `image_matches_rolling_target` and stay in rotation; settlement

through `finish_rolling_replacement/2` flips the target live and the next

convergence attempt reports `image_matches_live`. Images older than commit

`a79bfce` degrade with `artifact_not_direct` instead and return `503` for

the whole roll, which would empty the backend.

## Known failure modes

| Symptom | Cause | Fix |