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

src/starkernel/capsule/capsule_zuse_boot.c

@@ -16,19 +16,26 @@
 #include "starkernel/zuse_genesis_marker.h"
 #include "starkernel/user_identity_seed.h"
 #include "starkernel/console.h"
-#include "starkernel/repl.h" /* sk_console_mark_login() -- FABRIC-2.md headless-until-login gate */
 #include "block_subsystem.h" /* compute_crc64(), blk_meta_zone_read/write */
 #include "blkio.h"
 #include <string.h>
 #include <stddef.h>
 
-/* FABRIC-2.md §I.8 (re-scoped 2026-09-04): tracks whether the currently
- * home-blocks-attached device is Zuse's own -- the single-USB-device
- * constraint (§F.8) means capsule_zuse_boot_logout() only needs one flag,
- * not a device/uuid comparison, to know a detach event is hers to act on
- * (a regular WIREBIND user occupying the one slot instead is tracked
- * separately, in capsule_wirebind.c -- the two paths never overlap). */
+/* FABRIC-3.md §VII follow-on, 2026-09-06: g_zuse_attached_this_device was a
+ * bare boolean under the single-USB-device constraint (§F.8) -- "a detach
+ * event is hers" needed no device comparison because only one device could
+ * ever be attached at all. That premise is stale (FABRIC-3.md §VII, the
+ * xHCI/BOT driver now supports genuine simultaneous multi-device attach) --
+ * confirmed live during this session's own 8-identity verification: with
+ * Zuse's drive and a WIREBIND target both attached, detaching the *target*
+ * incorrectly logged Zuse out too, because capsule_zuse_boot_logout() had
+ * no way to tell "some other device detached" from "my own device
+ * detached." g_zuse_attached_dev is the fix, mirroring capsule_wirebind.c's
+ * own g_wirebind_attached_dev precedent exactly -- the boolean stays (still
+ * useful as a fast "is she attached at all" check) but logout now also
+ * requires the departing device to match. */
 static int g_zuse_attached_this_device = 0;
+static struct blkio_dev *g_zuse_attached_dev = (struct blkio_dev *) 0;
 
 /* Read exactly one devblock (4096 bytes) at devblock offset `devblock`,
  * as 4 consecutive 1KiB forth-block reads -- mirrors capsule_runcap.c's
@@ -53,7 +60,8 @@ static int genesis_marker_read(zuse_genesis_marker_t *out) {
     return 0;
 }
 
-static void install_and_activate(VM *mama_vm, const uint8_t seed[32], const uint8_t pubkey[32]) {
+static void install_and_activate(VM *mama_vm, struct blkio_dev *dev,
+                                  const uint8_t seed[32], const uint8_t pubkey[32]) {
     /* vm_zuse_cert_install() is deliberately one-way (returns -1, no-op,
      * once vm->zuse_cert_installed is already 1) -- that's a real
      * security property (the cert/pubkey must never be re-installed or
@@ -75,13 +83,16 @@ static void install_and_activate(VM *mama_vm, const uint8_t seed[32], const uint
      * convention. */
     vm_interpret(mama_vm, "ACL-ZUSE-BOOT");
     g_zuse_attached_this_device = 1;
+    g_zuse_attached_dev         = dev;
 
     /* Decided 2026-09-05: no console for the running system unless a
      * thumbdrive is present. Zuse's own login is not special here --
      * "nothing special about zuse as a user except zuse has no ACLs,"
-     * per direct instruction -- so this is the same shared signal
-     * capsule_wirebind.c's own successful login sets. See repl.h. */
-    sk_console_mark_login();
+     * per direct instruction. Revised 2026-09-06: no longer calls
+     * sk_console_mark_login() (a one-way sticky flag) -- the gate is now a
+     * live check (sk_console_identity_present(), repl.c) driven directly
+     * by mama_vm->zuse_session, which vm_interpret(mama_vm,
+     * "ACL-ZUSE-BOOT") above already sets. Nothing to call here anymore. */
 }
 
 void capsule_zuse_boot_try_attach(struct blkio_dev *dev,
@@ -125,7 +136,7 @@ void capsule_zuse_boot_try_attach(struct blkio_dev *dev,
             console_println("Zuse: genesis minted onto attached thumbdrive");
         }
 
-        install_and_activate(mama_vm, seed, pubkey);
+        install_and_activate(mama_vm, dev, seed, pubkey);
         return;
     }
 
@@ -148,14 +159,24 @@ void capsule_zuse_boot_try_attach(struct blkio_dev *dev,
     if (memcmp(idrec.pubkey, marker.zuse_pubkey, 32) != 0) return; /* not Zuse's drive */
 
     console_println("Zuse: identity confirmed from attached thumbdrive");
-    install_and_activate(mama_vm, idrec.seed, idrec.pubkey);
+    install_and_activate(mama_vm, dev, idrec.seed, idrec.pubkey);
 }
 
-void capsule_zuse_boot_logout(VM *mama_vm) {
+void capsule_zuse_boot_logout(VM *mama_vm, struct blkio_dev *dev) {
     if (!mama_vm || !g_zuse_attached_this_device) return;
+    /* The device actually detaching must be hers -- see g_zuse_attached_dev's
+     * own doc comment above. A different device (a WIREBIND target,
+     * general-purpose USB use) detaching while her own drive stays
+     * attached must not touch her session at all. */
+    if (dev != g_zuse_attached_dev) return;
 
     mama_vm->zuse_session       = 0;
     g_zuse_attached_this_device = 0;
+    g_zuse_attached_dev         = (struct blkio_dev *) 0;
 
     console_println("Zuse: session ended -- reattach to re-authenticate");
 }
+
+struct blkio_dev *capsule_zuse_boot_attached_dev(void) {
+    return g_zuse_attached_this_device ? g_zuse_attached_dev : (struct blkio_dev *) 0;
+}