ah-1cx.14 runner: the crash-confirmed full parse repeats every poll while finalize keeps failing Lined Up

Noted while fixing ah-1cx.1.

ah-1cx.1 added a full ParseEventsFile to Status's crash-confirmed branch, because a confirmed crash writes an immutable finished row and previously relied on the top-of-Status parse for the failure comment's session id and cost. Correct — but once past the grace, every subsequent Status of a still-unfinalized crashed attempt re-reads the whole stream.

Bounded in practice (finalize normally succeeds on the first observation), and far less severe than the original ah-1cx.1 bug, which hit every in-progress task on every tick. But it is the one remaining O(stream) call reachable from the poll loop, so it is worth closing once ah-1cx.8's or ah-1cx.9's stream-size work lands — a 202 MB stream re-read in a loop is the same starvation shape.

A crashed-but-unfinalized attempt does not re-read the whole event stream on every poll — either the facts are cached per (task, attempt) or the parse moves to the finalize call itself.