Four bugs found live verifying the 8 identity thumbdrives (FABRIC-3.md §IX)

All found by actually running the identity workflow §VII/§VIII made
possible, not by code review:

1. Zuse/WIREBIND cross-contamination on detach: capsule_zuse_boot_logout()
   and capsule_wirebind_unclean_detach() both had no device parameter, so
   an unrelated device detaching (while the real owner's own stayed
   attached) incorrectly tore down the wrong session. Both now compare
   the departing device against their own tracked one, mirroring
   capsule_wirebind.c's pre-existing g_wirebind_attached_dev precedent.

2. Dictionary-entry memory leak: vm_create_word()'s sf_malloc()'d
   DictEntry (plus a second per-entry allocation for transition_metrics)
   was never freed by vm_cleanup(), in both the hosted and kernel
   implementations. Caused a real kernel PANIC after 8-9 repeated VM
   birth/kill cycles in one boot. Fixed by walking vm->latest in both.

3. sf_malloc/sf_free (alloc_kernel.c) was a 4MB bump arena with a
   deliberate no-op free, sized on "VM born once, never killed" -- fix #2
   alone didn't stop the panic because free() itself discarded the
   pointer regardless. Given a real free list (first-fit reuse).

4. Headless-console gate didn't re-engage after a mid-boot logout: the
   original fix (sk_console_mark_login(), one-way sticky) only gated the
   first login of the boot. Replaced with a live check
   (sk_console_identity_present()) re-evaluated continuously, including
   inside sk_console_readline()'s own blocking idle loop -- the console
   is normally sitting blocked there when a hot-unplug logout happens, so
   checking only at the top of the REPL loop wasn't enough.

Also: MINT now verifies its own write (verify_mint(), capsule_mint.c) by
reading back through the same check a real attach performs, rather than
trusting blkio_write()'s BLK_OK alone -- logged via log_message(), not
console_println(), per direct instruction.

Verified live, amd64: the full 8-identity repeated attach/detach cycle
that previously panicked at the same point every time now completes
clean, and a full serial-log sweep found zero bare unauthenticated
prompts anywhere in the run. Three-arch clean-qemu acceptance passed.

Still open, not fixed here: a 3+-simultaneous-device USB enumeration
failure found in a separate live test, not yet root-caused.

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

include/starkernel/capsule_zuse_boot.h

@@ -68,17 +68,35 @@ void capsule_zuse_boot_try_attach(struct blkio_dev *dev,
  * one function covers both the graceful (EJECT) and abrupt (hot-unplug)
  * call sites identically.
  *
- * No-op if the currently-tracked attached device isn't Zuse's own
- * (nothing to do -- some other identity's drive is what's leaving, or
- * nothing is attached at all). Clears mama_vm->zuse_session only --
- * zuse_cert_installed and the cert itself stay put, permanently, per
- * vm_zuse_cert_install()'s own one-way design; re-attaching her own
- * drive re-authenticates via capsule_zuse_boot_try_attach() without
- * re-minting anything.
+ * No-op if `dev` isn't the device currently tracked as Zuse's own (nothing
+ * to do -- some other identity's drive is what's leaving, or nothing is
+ * attached at all) -- FABRIC-3.md §VII follow-on, 2026-09-06: this doc
+ * comment always claimed that no-op, but the check itself was missing
+ * until now (the function took no device parameter at all) -- confirmed
+ * live as a real bug once genuine multi-device attach made it reachable
+ * (detaching an unrelated device logged Zuse out too). Clears
+ * mama_vm->zuse_session only -- zuse_cert_installed and the cert itself
+ * stay put, permanently, per vm_zuse_cert_install()'s own one-way design;
+ * re-attaching her own drive re-authenticates via
+ * capsule_zuse_boot_try_attach() without re-minting anything.
  *
  * @param mama_vm Hera's own VM (zuse_session lives here).
+ * @param dev The device that just detached -- compared against the one
+ *            tracked as hers; every other value is a no-op.
  */
-void capsule_zuse_boot_logout(VM *mama_vm);
+void capsule_zuse_boot_logout(VM *mama_vm, struct blkio_dev *dev);
+
+/**
+ * capsule_zuse_boot_attached_dev - The device currently tracked as Zuse's
+ * own, or NULL if she isn't attached this boot. FABRIC-3.md §VII follow-on,
+ * 2026-09-06: exists so an explicit, operator-initiated logout (EJECT,
+ * mama_forth_words.c) can pass her own device back into
+ * capsule_zuse_boot_logout() without needing to already know it -- unlike
+ * the abrupt hot-unplug path, EJECT isn't reacting to any specific
+ * device's detach event, so there is no other device value available at
+ * that call site to check against.
+ */
+struct blkio_dev *capsule_zuse_boot_attached_dev(void);
 
 #endif /* __STARKERNEL__ */