The namer re-reads partial releases as the Rust window writes them

The pending namer's TypeScript re-index gave a file short of parts on the
server to the range path's fragment rule, so a partial release the edge
wrote (Bob's hex-named uploads in chello, ratcave, font, storage) never came
out again: 10 of 148k named releases moved. RangeIndexer's partialFiles
keeps such a file in its release, marked partial; tools/namer_check.ts
replays sample rows from the corpus (10 of 10 found with it, 1 without).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

REBUILD.md

@@ -880,7 +880,10 @@ f. **Nothing enters the catalog without a usable name** (amended
    (`app/services/pending_namer.ts`, in the prober's process): a named
    release's article span read again from the corpus (the stored range's
    chunks) or by XOVER on a connection of its own, through the TypeScript
-   indexer, written as a release under the pending key with `source`
+   indexer with `partialFiles` (a file given up short of parts stays a
+   partial file of its release, as the Rust window writes it; without it
+   the range path's fragment rule left nothing to find, and 10 of 148k named
+   releases were moved by 2026-10-29), written as a release under the pending key with `source`
    weak-stem, the name as `inner_name`, its chunk and its candidates (the
    prober answers those from `probe_cache`: inspections, par2 sets, hashes,
    the password flag). Not built: the spot/NZB match on pending keys (step