ffa2ad7f72
All checks were successful
deploy / deploy (push) Successful in 5m32s
The status said "nothing has been deployed to bob, the workflow has never run", which stopped being true at run 8. Leaving it would be the same class of misleading state this repo keeps trying to remove. Also record the seven faults it took to get green, because six of the eight were silent rather than loud: a runner label that meant the job was never scheduled, a vhost that nginx -t accepts and the SNI router never reaches, a cert whose SAN only the client checks, an ordering trap, a --chmod that stops applying after the first deploy, an API that looks healthy from the host it is unreachable on, and a health probe checking a unit name that expanded to nothing. The pattern is the useful part for later stages: the expensive faults were the ones where a check passed while measuring nothing. Closes #9 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013TxK1CWPkFXqdcXMJ4hVe6