phase6-adr-update

# Phase-6 ADR Update / Amendment This skill writes a new ADR or amends an existing ADR in the Phase-6 family. Style and structure follow `docs/adr/0001-0011*` — concise, with decision and consequences. ## When to use - A new Phase-6 architecture decision is due (e.g. a new worker-backend type, a new sandbox strategy, a Critic-Verdict schema extension). - An existing decision must be revised (e.g. the ADR-0009 hard cap MAX_CRITIC_LOOPS=3 is changed to 5 after empirical evidence). - After a successful Phase-6 increment that is not covered by an existing ADR. ## Steps 1. **Scan the existing ADRs:** `ls docs/adr/` — determine the highest number; the new ADR gets next-N. 2. **Read the style reference:** `docs/adr/0009-self-healing-worker-critic.md` is the Phase-6 style reference. Format: ``` # ADR-NNNN — Short Title **Status:** Accepted | Superseded by ADR-XXXX | Amended <Date> **Date:** YYYY-MM-DD **Reference:** <Phases / Plan-Section / Predecessor-ADR> ## Context <why this decision is needed now> ## Decision <exactly what is being decided, in 3-5 sentences> ## Consequences - <positive outcome> - <negative outcome / trade-off> - <what we can no longer do> ## Alternatives considered - <Option A>: why rejected - <Option B>: why rejected ## Follow-up items - <what must change in the code> - <which tests must be created> - <which documentation must be updated> ``` 3. **If an amendment** (no new ADR, instead A...