prove_loop `--watch` passthrough landed (first TAS+watch capture) and the DEATH SEQUENCE IS ON TAPE

CAPABILITY: prove_loop.py now accepts repeatable --watch ADDR,MODE and forwards them to the exe run — watch evidence under TAS replay, previously impossible (prove_loop.py is not in _HASH_INPUTS, so no regen invalidation). INTERPRETATION: $83 counting $0F→$0B looks like a death/expiry timer; at the $0B transition a state change fires whose post-transition dispatch path loops display-only — the logic re-entry (overscan logic segment of the frame chain)…

Raw traces, ROM material, local paths, and personal data are not part of this public record.