211a48187f
All checks were successful
check / gate (push) Successful in 18s
The retry fix already existed: a parallel session landed c79f196 (#172) with a test. Kit 0 was ONE COMMIT BEHIND and did not have it — which is the entire reason the loop ran. Deployed by ff-merging /root/windy-chat ac61db6 -> c79f196 and rebuilding only agent-roster (--no-deps). Never reset --hard; that checkout has a documented history of local edits a hard reset would eat. account-server CPU 168-210% -> 0.00% roster failures 74/min -> 0/min agent chat stopped -> up, healthy login timeout -> HTTP 200 ~18s The lesson: a merged fix that has not reached production is not a fix, it is a belief. That is exactly what both August audits named — nothing checks whether a decision reached production — arriving as an outage instead of a report finding. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>