Agreed retro with the Decoder at docs/agents/RETRO-2026-08-31-agreed.md; their own
review is at docs/agents/RETRO-2026-08-31.md on auto/frame-blend-draw-path.
Twelve rules, of which the ones neither of us had: a refutation whose instrument is
one of our renderers is not a refutation but "our renderer disagrees" (this cost
weeks, both ways); a negative must carry a positive control, which no "undecodable
with reach" page either of us has written ever did; and a disagreement is evidence
about the chain disc -> decode -> render -> capture, not about the link being
looked at.
The gap underneath our controls, stated: they verified capability, not
configuration. My additive material passed every control because they tested
whether the method detects a blend difference, not whether this run had blend_mode
set -- it was Godot's default MIX. Their vertex dump passed every control because
they tested the NDC conversion, not whether it captured all six quads.
Nothing applied to PROTOCOL.md. The register re-classification changes the file
both agents read to decide what not to try, and two agents agreeing is not the
right authority for that.
Also committing the work that was pending when the stop came: verify-menu-audio
now settles cue presence by suppression -- silence one cue's .ogg, re-record the
same walk, and require its own correlation to collapse. All three cues sound
(+0.158 / +0.637 / +0.526). The bed-only margin no longer renders a verdict: it
called `move` NOT FOUND on three runs at 0.109-0.131 while the cue was
demonstrably sounding, and across runs the same cue reads 0.131 and 0.158, so the
threshold was never a property of the cue.
The off-diagonal is reported as masking rather than asserted: silencing confirm
raises back by 0.468 because the game plays them 90 ms apart under a 0.15 s
template. An assertion there would fail forever on correct audio.
2af316dd82