self-healing

Active runtime recovery for coding agents: when something breaks mid-task, diagnose the root cause, write a fix, VERIFY by re-running the broken thing, then file a HEAL- entry to .learnings/HEALS.md with proof. Use whenever a command, test, build, or lint fails or exits non-zero; on missing tooling, dependency/lockfile mismatch, wrong runtime version, venv or permission errors, port conflicts, dirty git state, or a missing .env; when the agent needs a helper or one-off script that doesn't exist yet; when an external API, tool, or MCP errors or rate-limits; or when a test flakes. Search HEALS.md by Pattern-Key first — most heals are recurrences, so increment Recurrence-Count instead of duplicating. Verify is mandatory: mark pending-verify honestly if sandboxed, abandoned if the fix can't be made to work. Pairs with self-improvement (which promotes recurring heals to durable memory) but owns the verify-before-persist discipline self-improvement doesn't.