v0.17.6

Three releases required the reviewer to locate the counterexample's red run in the
implementer's dispatch record, adding escape branches when that proved impossible.
A Spike measured the lookup instead of extending it again.

What was measured

worker-read across ten settled dispatches returns one of two shapes. One harness
gives a bounded terminal window — 120 lines, truncated, with no cursor to page
backwards. Another gives a transcript, warning that older messages were omitted.

Searching an implementer's retained window for its own evidence found the fixture
command 0 times and the failing output 0 times. Those lines are the
worker's closing summary, not the middle of the session where the counterexample
ran. Where that harness is pinned for implementation, the record structurally
cannot hold the red run.

Across the five reviews written under the rule, none located it. All five
reproduced the counterexample themselves.

What changed

The lookup is deleted with both escapes. The surviving obligation joins the rule
it always belonged to: the reviewer observes the counterexample discriminate for
itself, and an instrument red only because the behaviour was absent is not that
observation.

Review's opening no longer describes worker-read; the evidence and handoff
sections already carry that machinery. Removing the dependency on plane retention
also removes the need for a third branch that had been queued.

The ## Review section falls from 353 words to 206. It remains 26 words larger
than before the lookup existed — a reduction against the peak, not a return to the
starting point.

What this does not do

It does not make a reviewer look. Nothing in the repository observes that. A later
controlled probe confirmed the limit is sharper still: a dispatched worker reads
the task spec its coordinator writes, not this protocol, so a rule placed here
reaches the role it governs only when the coordinator relays it.