Function has_a_transcript_row 

pub fn has_a_transcript_row(message: &Message) -> bool

Whether a transcript row carries a frame, which is what tells a copy’s numbering from the file’s when the frames the CLI never wrote are in it. Whether a transcript row carries this frame.

The row rule’s other half, and the one place it is stated. A frame whose kind no row round-trips - a Result, a thinking-token frame, a system subtype whose row belongs to another surface - is one the live stream emits and the CLI never writes, so a copy holding it counts a frame the file counts no row for. That difference is what a page below the floor has to be numbered through, by whoever still holds the frames the drops took.

A live hook frame has no row, though the read now serves hook rows. The CLI mints three ids for one run - the attachment row’s uuid, the live hook_id and the live frame’s uuid - and none of them equals another, so a live hook frame names no row a walk could resolve; the row the read synthesizes is a copy of the run, not the frame. The answer stays false, which is what keeps a stop off a frame the file cannot be asked for.