tools/port/edge-residual-map tiles the frame at 64 px and runs the shift
discriminator inside each tile, which is what edge-residual-kind's reach statement
said it could not do. Division agreed with the Decoder: the map is mine, the
element inventory is theirs.
The first control failed and that is the useful part. A known +2 px displacement
localises perfectly but reads back +0.839 -- the slope is a linearisation and
saturates. So there are two controls now: +1 px asserts localisation AND magnitude
(+0.949), +2 px asserts localisation and sign only. A hot tile's slope is a floor
on the displacement, never a ceiling.
Result: every dx and dy in the top ten tiles is under 0.1 px. Nothing in the hot
region has moved, locally or globally, so the misplaced-soft-element candidate now
has no support on this screen. Hot tiles cluster at x 384-704, y 64-256 plus an
outlier at 640,576; the tool names nothing and the list has gone to the Decoder.
And a null: I added a flat-pixel column expecting two families, edge-only against
hot-everywhere. The hot tiles run continuously 1.24..3.37 across a median of 1.84.
What nearly manufactured the split was carrying over the frame-wide POOLED ratio
of 3.16 as the baseline -- pooling is dominated by the tiles with the most edge
pixels. Same quantity, wrong population; caught because the baseline was computed
before the claim rather than after.
6af06bd595