The re-encode that quadrupled a GIF was passing every test that looked at pixels

The check that would have caught this is not one most pipelines run. Every frame the old encoder emitted was individually correct and the animation played correctly ^[8], so a visual diff passes it, and so does a hash of the decoded frame buffers. What went missing was structure, not pixels. A GIF is a sequence of image blocks, each with its own disposal method and local palette, and nothing requires a block to cover the whole canvas or to be a complete picture ^[5]. The pendulum source used that: a static rig and a dark background left alone, bytes spent on a bob occupying a few percent of the pixels ^[7]. The re-encode wrote full-canvas opaque keyframes instead and paid for that background 287 extra times ^[9].

That is the general shape. Any step that decodes a format to a canonical intermediate and re-serialises it discards the source's encoding decisions, and if those decisions were the compression, no output check based on appearance can see the loss. The size ratio is the detector, which is how this one surfaced at all: 1074 KB to 4881 KB on a 288-frame file ^[1], 116 KB to 1232 KB on a 70-frame one ^[2], with the same inflation on a pure re-encode with no crop ^[4].

The most useful part of the writeup is the heuristic that was built and then deleted ^[12]. The intuitive rule is to skip the delta when too much of the frame changed, and the measurements inverted it: the file that changed twice as much was the one that should have used deltas, the file that changed less was the one that should not ^[13]. LZW pays for runs, not for pixels, so what decides the outcome is how scattered the movement is, and no threshold over a changed-pixel count can see scatter ^[14]. So the encoder measures instead. Three sample frames per file, encoded both ways, winner kept ^[15], with both candidates appended after an identical frame 0 so the header, global palette and loop block cancel out of the comparison ^[16].

Across ten Wikimedia Commons animations ^[17], output runs 15% to 100% of the previous encoder's, median 90%, nothing bigger ^[18]. That median is the number worth holding: at least half the set gained 10% or less ^[5]. This is not a compression improvement with a long tail. It is a repair with a very short one, and the two repaired cases move 6.7x and 3.8x ^[1][2].

The numbers do not fully close. The fixed turret is 184 KB and the fixed pendulum 1292 KB ^[19], which are 59% and 20% above the input sizes quoted earlier in the same piece ^[3][4], while the summary says all ten finished at 17% to 79% of their sources ^[20]. The writeup does not say which files that band covers.

The palette footgun is the same failure mode in miniature: hand `quantize()` a subarray view and it reads the whole underlying buffer, builds the palette from the wrong pixels, and returns something plausible with no error ^[21].