Stage E: Category B strip -- remove Hermes, messaging.4th, old routing (FABRIC-3.6.md task 4.1-4.4)

All FORTH-owned message types were cut over to kernel-Hermes in Phase 3
(tasks 3.8-3.10). This removes the now-dead FORTH messaging layer and
the Hermes VM itself: capsules/common/messaging.4th, capsules/hermes/init.4th,
the slot-3 VM-NAME-REG pairing convention, and every load-site/birth-site
reference across capsules/init.4th, artemis/init.4th, hestia/init.4th,
doe-campaign.4th (Artemis-only now), capsule_console.c, capsule_mint.c,
capsule_wirebind.c, capsule_birth.c, and kernel_main.c.

Verified on all three architectures: clean boot, mkcapsule --lint clean
(36 files, 0 violations), zero UNKNOWN WORD, identical dict_hash across
amd64/aarch64/riscv64 for every VM, and a full mint -> WIREBIND-attach ->
USE -> relay round-trip exercising the two highest-risk edits
(capsule_console.c/capsule_mint.c).

Found, not fixed: deleting messaging.4th removes SEND-ELEVATE-REQUEST,
which was the only caller of KH-ELEVATE-SEND and the only path to
ELEVATE-GRANT (zuse-eligibility.4th, still loaded at boot) -- Phase 8
PKI's own elevation entrypoint. Needs a decision before Phase 5 close-out.

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

capsules/artemis/init.4th

@@ -492,13 +492,9 @@ Block 4853
 CD-INIT
 S" lib.4th" EXEC
 Block 4854
-( Phase C 2026-08-28: own messaging vocab + subscribe into )
-( Hermes's canonical COMMON-CH (idx 2 = Artemis, VM-NAMES- )
-( INIT). Hermes always exists by Artemis's birth. )
-S" common:messaging.4th" EXEC
-MSG-CD-INIT
-2 MY-CH-ID !
-S" 2 COMMON-CH @ CH-ADD-MBR" S" Hermes" VM-EXEC
+( FABRIC-3.6.md Phase 4, Stage E: common:messaging.4th/ )
+( MSG-CD-INIT/MY-CH-ID/COMMON-CH subscription all removed )
+( -- Hermes, the channel, and the words are all gone. )
 STARTUP-BANNER
 
 Block 4856