clarify-docslisted

# clarify-docs — Hygiene-Phase Documentation Fix When a worker notices drift between code and docs during its primary slice, the temptation is to fix it inline. Resist. A doc fix bundled into a code slice violates G-0005 (one slice per worktree per commit) and obscures the audit trail. Instead, emit a `class=hygiene` followup row pointing at this skill. ## When to use - Glossary term referenced in code but missing from CONTEXT.md (or vice versa). - CHOICES.md decision id (`G-0007`, `I-0006`, etc.) cited in code/comments but no matching row in CHOICES.md, or row text contradicts current behavior. - ADR claims behavior that the code no longer matches. - Broken file/path/skill-name reference in any markdown doc. - Example command in README/CLAUDE.md/skill doc fails when run literally. - Two docs (CONTEXT.md and a contexts/<bc>/CONTEXT.md, or an ADR and CHOICES.md) disagree on the same fact. ## Inputs expected on the row The bookie-created row should include in `body_md`: - **Target files** — explicit paths (e.g. `CONTEXT.md`, `docs/adr/0005-ledger-schema-prd-v1.md`). - **Observation** — one sentence stating the drift, with line numbers if useful. - **Suggested edit** (optional) — only if the answer is obvious; otherwise let the hygiene worker investigate. ## Deliverable shape - Docs-only PR. **No** code changes, no test changes. If the fix requires code, the row is mis-classified — bookie should `update --state cancelled` and the original worker should emit a `class=qual