I read this as a hands-on offline QA investigation - I’ll validate the exact candidate in disposable locations and report each requested scenario with executed evidence.


The sealed bundle is available and Python 3.12.9 is installed; I’ll now create an independent private copy and rehydrated runtime, with all execution limited to loopback or faked provider seams.


The first bootstrap was blocked by my copied bundle’s altered read-only wheelhouse modes (`0700/0600` versus the sealed `0500/0400` inventory), not candidate bytes. I restored the copy from the untouched seal before continuing.


The independent rehydration, both Golden verifiers, and a new actual loopback revocation run passed. I’m now exercising the controller CLI against a disposable synthetic fixture only; no service start or Telegram action is requested.


type: cancelled

previous_status: running

reason: v33 invalidated: profile receipt is synthetically forgeable and inbound revocation has an ingress TOCTOU race