journal: or.1 audit close (clean after tidy) — 0 bench regressions, 4-file drift sweep

docs/journals/2026-05-11-iter-or.1.md

@@ -113,3 +113,39 @@ artefact introduced by the orchestrator-agent (Phase 5 of its
 process). This iter was executed in pre-refactor mode by the Boss
 directly, so no stats file exists. The first stats file will be
 written by the orchestrator-agent on the next real `/implement` run.
+
+## Audit / milestone close
+
+Audit ran post-iter (skill-system mandatory at milestone close).
+
+- **Architect drift review:** `drift_found`. Live docs and a handful
+  of concept-noun sites still mentioned `JOURNAL.md` as if it were a
+  current path. Highest-impact misses were `docs/WhatsNew.md` (live
+  changelog framing-text — wrongly carved out of the Task 3 plan as
+  "dated artifact"), `docs/roadmap.md` lines 25-27 (live convention
+  text), and four bare `JOURNAL` mentions in `CLAUDE.md` (lines 108,
+  267, 285, 287). Five concept-noun spots in
+  `skills/audit/agents/ailang-architect.md` (Iron Law line 100 was
+  already correct; the others were process descriptions). All
+  resolved inline via `iter or.1.tidy` (single commit, four files).
+  Spec-vs-shipped divergences (the spec still prescribes the invalid
+  `git rebase ... onto main` and lists 3 blocked reasons where the
+  agent ships 5) were intentionally left as-is — specs are dated
+  artefacts capturing design at time of writing; the per-iter journal
+  is the running annotation.
+- **Bench-regression check:** `bench/check.py` 63 metrics stable
+  (exit 0); `bench/compile_check.py` 24 metrics stable (exit 0);
+  `bench/cross_lang.py` 25 metrics stable (exit 0). No language code
+  changed; the green result was expected and confirms it.
+- **Rustdoc:** 18 pre-existing warnings (2 in `ailang-core`, 16 in
+  `ailang-check`) about private-item links and unresolved cross-refs.
+  None caused by this iter. Deferred to a future docwriter sweep.
+
+Milestone close: clean after `or.1.tidy`. Three roadmap follow-ups
+worth noting:
+- WhatsNew.md should NOT be carved out as "dated artifact" in any
+  future doc-sweep plan; it is a live changelog.
+- A separate docwriter sweep for the 18 pre-existing rustdoc warnings.
+- Once a real `/implement` run goes through the new orchestrator-agent,
+  ladders 1–5 of the verification ladder in `docs/specs/
+  2026-05-11-implement-orchestrator-agent.md` are checked off.