night-market-failure-archaeology

# Night Market Failure Archaeology This is a reference document, not a runbook. It records every major investigation, dead end, rejected fix, and revert in this repo as symptom, root cause, evidence, status, and lesson, so nobody re-fights a settled battle. For triage of a failure happening right now, use `night-market-debugging-playbook`. Come here when a proposed change smells like something the repo already tried and rejected. Jargon used below: - "py39 hooks": hook scripts run under the host system Python (3.9 floor), while the rest of the repo requires Python 3.12. Enforced by `.github/workflows/python39-compat.yml`. - "unbloat": the conserve plugin's dead-code deletion campaign. - "Stop hook": a Claude Code hook that runs when a session turn ends. - "settled": the fight is over. Re-opening it requires new evidence and a note in the collective memory, not a hunch. ## How to use this chronicle 1. Before implementing, scan the battle titles and the recurring-class table for anything resembling your plan. 2. If a battle matches, read its lesson. Follow it, or write down why this time is different before overriding it. 3. Verify any hash you rely on: `git log --format='%h %s' -1 <hash>`. 4. When your own battle settles, add an entry (format at the bottom). ## Settled battles ### SB1: tasks_manager cross-plugin DRY consolidation (reverted) - Symptom: three near-identical `tasks_manager.py` copies in attune, sanctum, and spec-kit looked like textbook dupl...