Rename FABRIC series: FABRIC.md->0, FABRIC-2.md->1, FABRIC-3.md->2, FABRIC-4.md unchanged

FABRIC.md -> FABRIC-0.md
FABRIC-2.md -> FABRIC-1.md
FABRIC-3.md -> FABRIC-2.md (the current/living document)
FABRIC-4.md unchanged (new #3 to follow separately)

Every cross-reference repo-wide updated to match, including doc-comment
citations inside kernel source (.c/.h) files -- done via an ordered
placeholder substitution (FABRIC-3.md->placeholder2, FABRIC-2.md->
placeholder1, FABRIC.md->placeholder0, then placeholders resolved to
final names) in a single pass per file to avoid double-shifting
already-renamed references.

One line in capsules/font.4th grew past the 64-char block-format limit
as a side effect of the longer filename; shortened it and reverified
with mkcapsule --lint (34/34 pass) before rebuilding.

Verified 3-arch boot to ok> (amd64/aarch64/riscv64, each in the
foreground) after the fix; logs and DoE CSVs from this session's
verification runs included per this repo's own audit-artifact
convention.

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

include/starkernel/capsule_wirebind.h

@@ -9,7 +9,7 @@
 
 /**
  * capsule_wirebind.h - WIREBIND: the real thumbdrive-attach call site
- * (FABRIC-3.md §F.5/§F.23). Assembles pieces already built and
+ * (FABRIC-2.md §F.5/§F.23). Assembles pieces already built and
  * individually verified this session -- CERTVERIFY (vm_identity.h's
  * vm_identity_from_cert()), RUNCAP (capsule_runcap.h), the console-VM +
  * user-VM pair (capsule_console.h, sk_repl_dispatch_line() in repl.c) --
@@ -33,7 +33,7 @@ struct blkio_dev;
  * it against mama_vm's own Zuse identity. Shared by both
  * capsule_wirebind_try_attach() (the original attach) and BINDSTEP
  * (mama_word_use(), mama_forth_words.c -- re-verifies live on every USE
- * of an identity-locked VM, per FABRIC-3.md §F.9 decision 1) so both
+ * of an identity-locked VM, per FABRIC-2.md §F.9 decision 1) so both
  * call sites check the exact same thing the exact same way.
  *
  * No-op-and-fail (-1) if sig->cert_offset is 0 (no cert region -- a
@@ -80,7 +80,7 @@ void capsule_wirebind_try_attach(struct blkio_dev *dev,
 
 /**
  * capsule_wirebind_eject - Graceful detach of whatever VM is currently
- * attached via the home-blocks USB path (FABRIC-3.md §F.10, decision 1).
+ * attached via the home-blocks USB path (FABRIC-2.md §F.10, decision 1).
  * The drive is still physically present when this runs.
  *
  * Sequence: resolve the tracked attached-VM id to a live registry entry
@@ -102,7 +102,7 @@ int capsule_wirebind_eject(void);
 
 /**
  * capsule_wirebind_unclean_detach - Abrupt-path counterpart to
- * capsule_wirebind_eject() (FABRIC-3.md §F.10, decision 2 -- the UNCLEAN
+ * capsule_wirebind_eject() (FABRIC-2.md §F.10, decision 2 -- the UNCLEAN
  * node, closed alongside EJECT). Called from the existing
  * bot_msc_detach_pending hot-unplug signal (repl.c) -- the device is
  * already gone by the time this runs, so no flush is attempted; data
@@ -115,7 +115,7 @@ void capsule_wirebind_unclean_detach(void);
 /**
  * capsule_wirebind_attached_username - The plain username (no "~user"
  * registry-name suffix) of whichever identity is currently tracked as
- * attached, or NULL if none is (FABRIC-3.md §I.1/4.4s -- the `(user)`
+ * attached, or NULL if none is (FABRIC-2.md §I.1/4.4s -- the `(user)`
  * console prompt segment reads this). Points into WIREBIND's own
  * internal storage; valid only until the next attach/eject/detach, same
  * caveat as console_get_vm_name().