I read this as a read-only root-cause investigation of the deep-link double-validation hypothesis - I’ll inspect the isolated runtime, installed wheel, ledger transitions, and audit evidence, then report exact values and causal lines to the lead. I'll stop right away when the lead has a sourced verdict confirming or rejecting H1.


The live process is confirmed to be the isolated `dac4e812` venv, and the bootstrap ledger changed at 09:46:51 immediately before the generic response window; I’m now tracing the installed handler and correlating those writes with logs.