The deduplicate-by-id case of overzoom-test writes six artifacts but its
cleanup line removes only five: tests/pbf/merged-dedup.pbf, created by the
--deduplicate-by-id overzoom run, is the one left out, while its decoded
.json.check counterpart is removed. So a full `make test` leaves an untracked
file in the working tree, which shows up as spurious `git status` noise and
can be committed by accident.
No CHANGELOG entry or version bump: this only affects the test harness, and
nothing about a released build changes. Keeping those files untouched also
means this does not collide with the 2.81.1 entry in the label-anchor fix,
so the two can merge in either order.
Verified by running `make overzoom-test` both ways: with the old line the
file is left behind as untracked, with the new one the tree is clean, and
the target passes either way.
Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NcSXLjtokxioaBCCwGTEv1
