FABRIC-2.md: fix stale §12 Q5 tracking — checkbox and punch-list drift

Found while checking for the same scattered-punch-list problem that
forced FABRIC.md's closure: §12 Q5 was actually closed 2026-08-15 (the
STADIUM_CAPACITY_TICK flat-4000-divisor fix), but Section D's checkbox
was never flipped to [x], and Section F.3's punch list still re-listed
it as an open question. Fixed both; corrected the F.2/F.3 "net result"
summary to match.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

FABRIC-2.md

@@ -574,10 +574,16 @@ and recorded.
 
 ## D. Design questions still genuinely open
 
-- [ ] **§12 Q5 — the full eight-loop interference analysis has not been done.** Its stated
+- [x] **§12 Q5 — the full eight-loop interference analysis has not been done.** Its stated
   blocker ("no real time base on all three ISAs") is gone — Phase 0 completed that — so this
   is now unblocked and simply never picked back up.
 
+  > **CLOSED 2026-08-15** — see the full closure writeup under Section F, "§12 Q5's
+  > `STADIUM_CAPACITY_TICK` wiring — CLOSED 2026-08-15." This box was left unchecked after
+  > that closure landed; corrected 2026-08-18 (Captain Bob caught the drift). The F.3
+  > punch-list bullet re-asking this same question was stale for the same reason and has been
+  > removed there.
+
   > **ANALYSIS DONE 2026-08-13 — found a real violation of §22.4's required ordering, left
   > open pending Captain Bob's call on how to handle it.** Traced every loop's actual firing
   > cadence from source (`src/starkernel/vm/vm_core.c`, `vm_runtime.c`,
@@ -843,18 +849,20 @@ redirect to `FABRIC.md`/`FABRIC-2.md`. Nothing left pending in this track.
 
 **Code / actionable — pending Captain Bob's call or Artemis landing:**
 
-- [ ] §12 Q5 — give `STADIUM_CAPACITY_TICK` a real threshold against the existing
-      `fleet_heartbeat_tick_count` (one clock, bigger divisor — not a second tick source), or
-      resolve the ordering some other way?
 - [ ] 4.4s → 1.11 → 4.3 → §17.4 chain — no ruling needed, just unstarted work blocked on ACL
       Phase 8 (identity storage), out of this pass's scope
 - [ ] 5.1 (DoE re-run) + ACL-RWT re-measurement — run now, or wait for Artemis (recommended)?
 
+(§12 Q5 was listed here too as of this writing; removed 2026-08-18 — it was already closed
+under Section F's `STADIUM_CAPACITY_TICK` writeup and Section D's checkbox, both dated
+2026-08-15. This bullet re-asked the same already-answered question.)
+
 **Net result:** F.1 (documentation) is fully closed. F.2 has four closed items (three from
-the original pass plus the RAM-derived Stadium VM-count fix, Section G), four
-sequencing-blocked items (no ruling needed, just not startable yet), and one open code
-question (§12 Q5). Nothing left open is closeable without either Artemis or an explicit
-decision from Captain Bob on §12 Q5.
+the original pass plus the RAM-derived Stadium VM-count fix, Section G), and two
+sequencing-blocked items (no ruling needed, just not startable yet) — §12 Q5, the one open
+code question this summary used to cite here, was already closed elsewhere in this
+document (see Section D and Section F above) as of 2026-08-15. Nothing left open here is
+closeable without either Artemis landing or a sequencing decision on the ACL-blocked chain.
 
 ---