Create capsules/hestia/init.4th -- FABRIC-3.6.md task 1.2

The third Tripod leg's first real file (FABRIC-3.5.md SII/SIV). Blocks
4986-4987 of the 4986-4996 allocated in task 1.1 (b624133a): WELCOME
banner, then common:messaging.4th load + MSG-CD-INIT + COMMON-CH join
on slot 11, modeled on hermes/init.4th's equivalent shape. No fabric.4th/
font.4th yet -- tasks 1.6/1.7. Not yet birthed -- task 1.4.

Slot 11 is a fresh routing-table slot, not Hermes's slot 1: Hera/
Hermes/Artemis hold 0/1/2 and identities hold 3-10 (messaging.4th:
78-85), and Hermes stays live and fleet-foundation through Phase 1-3
(SXXXIV.4) so his slot isn't free yet.

Deliberately did not add a VM-NAME-REG entry for "Hestia" to
messaging.4th's VM-NAMES-INIT -- Phase 1's own gate is "messaging
untouched" and that table lives in messaging.4th. Consequence: once
birthed, Hestia is COMMON-CH-reachable by raw slot but not yet
VM-EXEC-addressable by name. Flagged in FABRIC-3.6.md rather than
decided -- whichever task first needs name lookup settles where that
one-line addition goes, and it will need its own authorization since
it touches a file Phase 1 promised not to.

mkcapsule --lint capsules/ clean, 38 files / 0 violations. MANIFEST.md
given a matching entry. Three-arch boot clean: amd64/aarch64/riscv64
all reach [zuse@Hera] ok>, zero UNKNOWN WORD, byte-identical to task
0.7's baseline (same dict_hash triple) -- exactly as expected, since an
unbirthed capsule is inert.

Authorized by Captain Bob ("YES").

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

FABRIC-3.6.md

@@ -328,8 +328,30 @@ Hestia; headless policy intact.
       vocabulary, per §XVIII.5) without colliding with anything. No `.4th` file created yet.
       `mkcapsule --lint capsules/` still clean, 37 files, 0 violations (documentation-only, no
       capsule content changed).
-- [ ] **1.2** — Create `capsules/hestia/init.4th`: messaging load, `MSG-CD-INIT`, banner. **No
+- [x] **1.2** — Create `capsules/hestia/init.4th`: messaging load, `MSG-CD-INIT`, banner. **No
       fabric yet.** *Check:* boots; Hestia not yet birthed.
+      2026-09-19 · `logs/20260919-162642/amd64/`, `logs/20260919-162747/aarch64/`,
+      `logs/20260919-162920/riscv64/` — all three reach `[zuse@Hera] ok>`, zero `UNKNOWN WORD`,
+      **byte-identical to task 0.7's baseline** (same `dict_hash` triple, same word counts) —
+      exactly as expected, since an unbirthed capsule is inert. Created
+      `capsules/hestia/init.4th` (blocks 4986–4987 of the 4986–4996 allocated in task 1.1, only 2
+      used so far): `WELCOME` banner (block 4986) plus `common:messaging.4th` load + `MSG-CD-INIT`
+      + `COMMON-CH` join on **slot 11** (block 4987), modeled on `hermes/init.4th`'s equivalent
+      shape. `mkcapsule --lint capsules/` clean, 38 files, 0 violations. `MANIFEST.md` given a
+      matching entry (same pass, since the file now exists — unlike task 1.1, which deliberately
+      held off documenting a file that didn't exist yet).
+
+      **A scope decision, not a defect:** slot 11 is a fresh routing-table slot (0–2 are Hera/
+      Hermes/Artemis, 3–10 are the 8 identities, `messaging.4th:78-85`) rather than Hermes's slot
+      1, because Hermes stays live and fleet-foundation through Phase 1–3 (§XXXIV.4) — his slot
+      isn't free yet. **Deliberately did not add a `VM-NAME-REG` entry for "Hestia"** to
+      `messaging.4th`'s `VM-NAMES-INIT`, since Phase 1's own gate is "messaging untouched" and
+      that table lives in `messaging.4th`. Consequence: once birthed, Hestia will be
+      `COMMON-CH`-reachable by raw slot number but **not yet `VM-EXEC`-addressable by name**
+      (`S" Hestia" VM-EXEC` would fail to resolve). Flagged here rather than decided — whichever
+      later task first needs name lookup (birth itself, task 1.4, or something after) is where
+      that one-line addition belongs, and it will need explicit authorization since it touches
+      the file Phase 1 promised not to.
 - [ ] **1.3** — Add Hestia to `is_fleet_foundation` (`capsule_birth.c:793-796`) — **four names,
       Hermes retained** (§XXXIV.4). *Check:* 3-arch boot; Hermes still live.
 - [ ] **1.4** — Birth Hestia in `kernel_main.c`, **alongside** Hermes's existing birth.