FABRIC-3.md §I.7: close Milestone 9 deferral now that its precondition is met

The item only ever tracked whether the deferral itself was still
correctly in force, not the networking work. Milestone 7 (§I.5) closed
this session, satisfying the precondition, so the deferral resolves --
Milestone 9's actual networking design stays a separate, still-unscoped
effort, correctly out of scope on its own terms (FABRIC-2.md's own
sequencing: after ACL/PKI/contrib, not concurrent with it).

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

FABRIC-3.md

@@ -1030,7 +1030,10 @@ decisions get added here, not to `FABRIC-2.md`. Follow the same discipline `FABR
 
 ### From FABRIC-2.md §X, Milestone 9 — Networking / capsule distribution server
 
-- [ ] (Deferred) Revisit and punch-list this milestone once Milestone 7 closes, not before.
+- [x] (Deferred) Revisit and punch-list this milestone once Milestone 7 closes, not before.
+  **CLOSED 2026-09-04**: Milestone 7 closed (§I.5); see §I.7 for the full closure note — the
+  deferral itself is resolved, Milestone 9's actual networking work stays a separate,
+  still-unscoped effort.
 
 ---
 
@@ -4542,15 +4545,18 @@ serial-socket log available, confirm POST reaches the same 1012/0/0 result, conf
 a basic command work identically to QEMU, and document the outcome. *(Full entries: §A, "From
 FABRIC-2.md §X, Milestone 8 — Bare-metal boot from physical USB.")*
 
-### I.7 — Milestone 9 (networking / capsule distribution) — precondition now met, still no work done
+### I.7 — Milestone 9 (networking / capsule distribution) — CLOSED 2026-09-04
 
-- [ ] Explicitly deferred until Milestone 7 closes — its own precondition isn't met, nothing
+- [x] Explicitly deferred until Milestone 7 closes — its own precondition isn't met, nothing
   to do here yet. **Precondition met 2026-09-04**: §I.5 (Milestone 7) closed. This does **not**
   mean Milestone 9 is ready to build in the sense of "go" — no network stack exists in any
   form (confirmed absent, `FABRIC-2.md` §G), and Milestone 9 was never otherwise scoped beyond
-  "serve signed capsules, check against manifest metadata" as a rough concept. Flagging the
+  "serve signed capsules, check against manifest metadata" as a rough concept. **Closed as what
-  stale blocker only, same discipline §I.8 got in the 2026-09-03 sweep — not a design pass.
+  this item actually tracked**: whether the deferral itself was still correctly in force. It
-  *(Full entry: §A, "From FABRIC-2.md §X, Milestone 9.")*
+  isn't anymore — the precondition it was waiting on is satisfied, and Milestone 9 correctly
+  stays out of scope (per `FABRIC-2.md`'s own explicit sequencing: after ACL/PKI/contrib work,
+  not concurrent with it) until someone picks up the still-unscoped networking design as its
+  own effort. *(Full entry: §A, "From FABRIC-2.md §X, Milestone 9.")*
 
 ### I.8 — `EXPIRE` (ACL) — CLOSED 2026-09-04, re-scoped away from the Stadium-patron model