THE FREEZE IS AN INFINITE LIST-SCAN LOOP, NOT A DISPATCH CYCLE

CORRECTED MODEL: the "display loop" of F162/F163 is not a degenerate dispatch cycle — the CPU is stuck inside ONE C function (sub_0110C0, the same function iter-34's non-TAS natural-exit implicated) in a goto-only infinite loop; frames keep advancing solely because io_tick inside the spinning loop drives the frame clock, and the TIA snapshot state (olive bk, no objects) is whatever the last full frame left behind.

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