v0.17.3

A harness-matrix probe ran a full Bounded delivery across three coding agents.
The implementer used its instrument's failure against an absent feature as the
baseline — which the protocol says in as many words does not count — and neither
the control session nor the reviewer caught it. The reviewer accepted.

None of the three broke a rule. The rules did not join up: the obligation sat
entirely on the implementer as prose in a handoff field nothing could check,
review received dispatch evidence passively, and "Reproduce, do not accept" was
scoped to gates.

What changed

The reviewer now reads the implementer's dispatch record itself rather than being
handed a summary of it, and a disposition is not reachable until it has located,
in that record, the run where the counterexample was observed red. An instrument
red because the behaviour was absent is not that run. Where the execution plane
cannot recover the record, the reviewer says so with the reason the plane gave,
and the counterexample rests on the implementer's account rather than on evidence.

No new mechanism was introduced. worker-read already returns the hook-reported
transcript when the session can be proven, with a typed fallback reason otherwise;
the change is which role goes and fetches it.

How this one was verified

The new text is pinned verbatim in the contract script. The counterexample is a
weakened variant of the sentence itself — "should read the dispatch record" —
which keeps every distinctive keyword, passes plausible keyword checks, and fails
the pin. Deleting the paragraph outright also passes those keyword checks, so the
absence of the text is provably not the discriminator.

What this does not do

The pin stops the sentence being silently weakened later. It cannot make a future
reviewer look. No instrument available in the repository can observe that, and the
decision record says so rather than implying otherwise.

Also

The contract script's line ceiling rises from 250 to 280 to make room for the pin;
the script is now 260 lines. The ceiling exists to stop that script becoming a test
suite, and raising it deliberately keeps that intent.