Found live while building a cross-ISA FORTH-79 dictionary exerciser:
- capsule_exec_init() zeroed a capsule's block content immediately after
running it, so LOAD (a genuine FORTH-79 standard word, ACL-allowed even
for locked identities) could never actually read back what EXEC had
just written. Removed the clear from capsule_exec_init(); block content
now persists like any other Standard BLOCK/BUFFER/UPDATE write.
kernel_main.c's own explicit post-birth clear of Mama's init.4th range
is untouched.
- USE could redirect the console to a WIREBIND identity's VM before that
VM's vm_enable_interpreter() step of its own birth sequence had run,
causing the next typed line to hit vm_assert_interpreter_enabled() and
panic the entire machine -- not the per-session-recoverable ACL-fault
path a redirected VM otherwise gets. USE now checks interpreter_enabled
first and refuses with a retry message instead.
Also includes the amd64/aarch64/riscv64 acceptance boot logs and DoE CSVs
from this session.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EXieurDfDSsDFdnSyusuWo