Documentation debt sweep: 5 of 6 items resolved, 1 confirmed accurate

- docs/lithosananke/ROADMAP.md + M7.1.md: fixed stale "Branch: lithosananke"
  (no such branch post-split), M7.1's "Design Complete" status (shipped
  and live, redirected to FABRIC*.md), the M8/success-criteria
  self-contradiction (OBSOLETE marking vs. unqualified live criterion),
  and the stale AHCI/SATA claim for M9 (real implementation is
  virtio_blk.c) -- also corrected BLOCK/BUFFER/UPDATE/FLUSH and block
  device abstraction to [x] since both are confirmed live in
  src/word_source/block_words.c and block_subsystem.c.
- Top-level ROADMAP.md: marked OBSOLETE (Captain Bob's call -- more than
  "stale," the architecture/branch topology/terminology it describes no
  longer exist), pointing to docs/lithosananke/ROADMAP.md and
  FABRIC*.md for current status.
- docs/03-architecture/word-acl/DESIGN.md: fixed the ACL Phase 7
  contradiction -- Phase 7 (LithosAnanke kernel parity) is independently
  verified complete per .claude/CLAUDE.md, not "remaining"; removed the
  stale lithosananke-branch-parity framing.
- VM-FLEET-ATTRACTOR-DESIGN-20260705.md's doe-campaign.4th "broken" claim:
  investigated, ran SMOKE-CAMPAIGN live (completes clean, fleet heat
  conserved) -- initially read as contradicting the claim, corrected
  directly by Captain Bob: a clean execution trace doesn't disprove the
  doc's actual argument (no real controlled-experimental-factor
  mechanism). Confirmed accurate, left untouched.
- Isabelle/HOL pipeline-metrics model/C-struct mismatch: confirmed a real
  proof-modeling gap (pm_last_accuracy_num/den has no analogue in the
  real PipelineGlobalMetrics struct), not stale prose -- tracked here
  rather than fixed, matching the .thy file's own scope boundary and
  this project's standing caution that each Isabelle gap needs its own
  subsystem model.

ACL-RWT DoE overhead re-measurement (the 6th item) intentionally not
started -- a full multi-architecture DoE campaign, not a doc-text fix,
holding for explicit confirmation given the scale.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CXjAPTEKrgY2Mrk25KoLDn

FABRIC-3.md

@@ -78,12 +78,27 @@ decisions get added here, not to `FABRIC-2.md`. Follow the same discipline `FABR
   is still "remaining" — direct contradiction with `.claude/CLAUDE.md`, which states Phase 7
   is independently verified complete. Not fixed.
 
-- [ ] `VM-FLEET-ATTRACTOR-DESIGN-20260705.md` claims `doe-campaign.4th` is "broken and being
-  superseded" — unverified against repeated successful `L8-DOE` runs (a different FORTH entry
-  point; not confirmed either way).
+- [x] Confirmed accurate, not stale (2026-08-26): `VM-FLEET-ATTRACTOR-DESIGN-20260705.md`'s
+  claim that `doe-campaign.4th` is "broken and being superseded." Live-ran `SMOKE-CAMPAIGN`
+  from the current capsule (amd64) — it completes without error and correctly conserves fleet
+  heat (`VM-PHYSICS: conserved=CONSERVED`, `fleet_heat_sum=65536`). Initially read that as
+  contradicting the doc's claim; **Captain Bob corrected this directly — it's broken.**
+  "Doesn't crash" and "runs" are not the same claim: the doc's actual argument is that the
+  capsule has no real controlled-experimental-factor mechanism (no manual heat-injection
+  point under the current design, so it cannot drive the fleet through controlled scenarios
+  the way a DoE campaign needs to), a methodological gap a clean execution trace doesn't
+  surface or disprove. Doc's claim stands; not touched.
 
-- [ ] Isabelle/HOL: the pipeline-metrics model/C-struct mismatch this sweep surfaced —
-  flagged in the `.thy` file itself, not independently tracked elsewhere, not fixed.
+- [x] Tracked (2026-08-26) — real proof-modeling gap, not just stale prose, so not fixed
+  here. Confirmed by reading `StarForth_Loop4_Pipeline.thy`'s own comment (lines 127–137):
+  `pipeline_metrics_state`'s `pm_last_accuracy_num`/`pm_last_accuracy_den` fraction pair
+  doesn't correspond to anything in the real C struct — `include/vm.h`'s
+  `PipelineGlobalMetrics` has a single `double last_checked_accuracy` field, no num/den pair
+  anywhere. The `.thy` file's own comment already scopes the real fix correctly: "a full
+  field-level pass over `pipeline_metrics_state` is its own separate task" — matches this
+  project's standing caution that each remaining Isabelle gap needs its own subsystem model,
+  not a documentation-sprint patch. The punch-list ask was tracking this outside the buried
+  `.thy` comment, which it now has here — the actual re-model stays unattempted, on purpose.
 
 ### From FABRIC-2.md §X, Milestone 2 — USB hardware stack