scan-next: erase hash cells pointing at a ceiling extent
An extent at or above rewrite.refs-max cannot take another reference, so
it can never serve as a dedupe src again. Its block hashes stay in the
hash table regardless, and every later scan that shares one of them pays
a lookup and an extent resolve to rediscover that the extent is
unusable. Nothing ever clears this: the crawler advances past the
extent and will not return, because nothing about the extent changes.
Erase the cell instead. The candidate search already erases cells that
resolve into a gap between extents, and normalizes cells that point into
the middle of an extent; a ceiling extent belongs in the first category
rather than the second, since normalizing its address only preserves a
pointer to something that has permanently withdrawn from dedupe.
This erases only the hashes that actually surface in a lookup, which is
the complete set of hashes that cost anything -- a hash nobody looks up
is free to leave in place. It also needs no reference list, which
matters here because a ceiling extent has none to offer.
Telling a ceiling extent apart from a freed one needs the same
disambiguation the start-extent path needed, so the candidate gate now
asks refs_at_ceiling() as well, and counts the two separately.
Document the candidate event group, which was missing entirely.