iter cadence.2: skills/audit — drop docwriter step (now own skill)

skills/audit/SKILL.md

@@ -69,22 +69,16 @@ The exit code is the gate:
 | `1` | Drift / regression | At least one metric regressed past tolerance. Treat like a drift item. |
 | `2` | Infrastructure failure | Bench-output format changed, fixture missing, or harness can't spawn. **Fix the infrastructure FIRST**, re-run. Never claim a regression on exit 2. |
 
-### Step 3 — Optional rustdoc audit
+### Step 3 — Classify and report
 
-If `cargo doc --no-deps 2>&1` shows new warnings, dispatch
-`ailang-docwriter` to clean them. This step is optional — only run
-when rustdoc warnings are present.
-
-### Step 4 — Classify and report
-
-Combine architect drift items + bench results + rustdoc warnings
-into one report to the orchestrator (me). Each item is one of:
+Combine architect drift items + bench results into one report to
+the orchestrator (me). Each item is one of:
 - **fix** (specific iter scoped, plan + implement)
 - **ratify** (`--update-baseline` on the firing script + JOURNAL
   entry naming the iter that intentionally moved the metric and why)
 - **carry-on** (architect found nothing actionable, bench green)
 
-### Step 5 — Resolve
+### Step 4 — Resolve
 
 The orchestrator picks per item:
 - **fix path:** dispatch `planner` + `implement` for a tidy iteration.
@@ -104,7 +98,6 @@ The orchestrator picks per item:
 | `drift_items` | prioritised list (path + 1-line justification) from architect |
 | `bench_exit_code` | `0` / `1` / `2` |
 | `bench_numbers` | raw figures from the three scripts (verbatim) |
-| `rustdoc_warnings` | count + list (or 0 / clean) |
 | `recommendation` | per-item: `fix` / `ratify` / `carry-on` |
 
 The orchestrator decides the per-item outcome; `audit` does not
@@ -119,7 +112,6 @@ self-resolve.
 | "Drift item is trivial, ignore it" | Trivial drift left open trains future-me to treat the architect's findings as advisory. Six items in, six items out. |
 | "Bench scripts are hanging, skip them this milestone" | Exit code 2 = fix infrastructure FIRST. No skipping. |
 | "Architect report is empty, fast-close" | Empty report is a possible outcome. Run the bench scripts anyway. Both gates must pass. |
-| "Rustdoc warnings are just style, no real drift" | rustdoc drift IS drift. If the docwriter agent exists and warnings are present, run it. |
 
 ## Red Flags — STOP
 
@@ -137,7 +129,6 @@ self-resolve.
   - `skills/audit/agents/ailang-architect.md` — drift review
   - `skills/audit/agents/ailang-bencher.md` — bench-regression
     diagnostics if a metric needs localising
-  - `skills/audit/agents/ailang-docwriter.md` — rustdoc cleanup
 - **Hand-off target:** orchestrator (me), or `planner` + `implement`
   for a tidy iteration.
 - **Project source:** former CLAUDE.md sections "Iter cycle / Tidy-iter