doc-synclisted

Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md). Local, on-demand documentation synchronization. This is the **third trigger mode** for doc maintenance, complementing the event-driven layer (pre-commit warn) and the scheduled layer (periodic report): the human runs it when they know they've changed something doc-affecting, to pull drifted docs back in line with the code — but the human keeps the landing authority. **Relationship to `qq:doc-drift`:** doc-drift is report-only (it outputs a P0/P1/P2 attention list). doc-sync is the *reconcile loop* — it **calls** doc-drift (and the project's drift detectors) as its detection stage, then adds the two stages doc-drift lacks: **draft** the fixes and **land** what the human approves. Arguments: $ARGUMENTS - No arguments: full sweep of the project's living docs - `--since <ref>`: only docs affected by code changed since `<ref>` (windowed reconcile) - `--scope <design|memory|seams|rules>`: restrict to one class of living doc - `--all`: include archived/historical docs (default excludes `Docs/archive/` and old review artifacts) ## Principle (do not violate) > **Detectors are read-only; doc-sync is the sole writer; the human is the sole lander. Reference drift (a dead anchor) is auto-drafted; semantic/process drift is only flagged for the human to decide.** > Graphs say "what is wired now"; the seam registry says "what should be wired / what breaks if m