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>

src/starkernel/capsule/mama_forth_words.c

@@ -1450,7 +1450,8 @@ static void mama_word_name_to_xt(VM *vm)
  * buffer at buf-addr, matching ZUSE-PUBKEY@'s own convention exactly:
  * chunk i (0..3) is the 8-byte little-endian encoding of pubkey bytes
  * [i*8 .. i*8+7] -- this is that packing's inverse, so a pubkey sent as
- * 4 cells (see common:messaging.4th's SEND-ELEVATE-REQUEST) round-trips
+ * 4 cells (the convention SEND-ELEVATE-REQUEST used before it was
+ * deleted with messaging.4th, FABRIC-3.6.md Phase 4 Stage E) round-trips
  * byte-exact regardless of any individual chunk's sign bit.
  */
 static void mama_word_elevate_pubkey_unpack(VM *vm)