add-wiki-maintenancelisted

# Wiki Maintenance — Update Discipline <!-- uses: - command: /add.wiki - script: done.sh --> ## Overview Keeps `{{addpath:wiki/}}` accurate between full `/add.wiki` regenerations. Two triggers share this ONE discipline; only evidence collection (STEP 2) differs. Surgical edits, computed candidates before judgment, no-op is a valid outcome. ## When to Use - `add.done` STEP 4.9, pre-merge — automatic, evidence = branch diff + feature context - `/add.wiki update` — manual, evidence = tiered git-log chain from `.meta.json` ## When NOT to Use - No wiki exists yet → full generation (`/add.wiki`), not this skill - Rewriting/regenerating a page wholesale → `/add.wiki` owns full generation, this skill never does ## WRITE BOUNDARY Only three writers touch `{{addpath:wiki/}}`: `/add.wiki` (full gen), this skill's executions (surgical edits), the user. `INSTRUCTIONS.md` is NEVER machine-written — read-only steering, always. This skill never touches AGENTS.md (owned by `/add.wiki` STEP 6). ## NO-OP IS A FIRST-CLASS OUTCOME Nothing relevant changed and the wiki is accurate → edit nothing, report "wiki already current". Still advance `.meta.json` (STEP 8) — a verified-current run is information, not nothing. ## The 9-Step Sequence ### STEP 1 — GATE `{{addpath:wiki/index.md}}` exists? IF NO → STOP. The caller (add.done or /add.wiki) handles the "run /add.wiki first" suggestion; this skill does not generate. ### STEP 2 — EVIDENCE (trigger-specific) **add.done trigger:** - `CHAN