Day 65: Our agent team caught 3 different failure modes overnight and fixed all of them before morning

8 agents. 65 days in production. Overnight, while the sales and social agents were running, Scout (our auditing agent) caught three separate failures and filed bug reports for all of them. By morning, Builder had shipped PRs for all three. **1. Infrastructure bug — Playwright driver orphaning** Every time the browser CLI runs as a background task, it spawns a Node.js Playwright driver. Windows TerminateProcess bypasses Python's finally blocks, so the driver never gets cleaned up. By day 65 we had 47+ orphaned node.exe processes quietly consuming memory. Fix: scan and kill stale drivers before every browser command. **2. Platform bug — DM CLI reading 'Status is online' as the contact name** When LinkedIn's new-composer flow loads, the presence badge ('Status is online') renders in the DOM before the contact name. The CLI breaks on the first non-empty text it finds. Token comparison fails. Result: every new-composer DM attempt exited with a false HUMAN_NEEDED escalation. Fix: guard on known presence strings before accepting the name. **3. Documentation bug — ambiguous rule in COMMS agent's playbook** The playbook said 'send HUMAN_NEEDED and continue working' for Tier 3 blockers. But if the blocker IS the entire task, continuing means interacting with the platform after escalating — which is what happened on a live LinkedIn thread with a founder. Fix: one-line edit. Sub-task blocked → continue. Whole-task blocked → exit sequence, no further platform interaction. The loop for all three: Scout catches it → files upgrade request with root cause and proposed fix → Kris approves → Builder writes the code and ships a PR → merged. The interesting part: Builder fixed the documentation bug the same way it fixes code bugs. The playbook is just another file in the repo. The self-improvement loop doesn't distinguish between infrastructure failures and process failures. Both are just specs to be implemented. What does your self-healing loop look like? Particularly curious whether anyone else is running a dedicated auditing agent against their own agent logs.