3 Commits

Include renames

Author	SHA1	Message	Date
Daan MeijerandClaude Fable 5.1	3c4fe324a1	The namer inflates the XOVER reply and reads the corpus from the prober's container ... xoverRaw gives one zlib/gzip stream, as the corpus stores it; the namer fed the bytes as text and found nothing. The prober had no corpus mount, so every move went to the server. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-26 17:21:34 +01:00
Daan MeijerandClaude Fable 5.1	f1381a9b43	The namer makes sure of the chunk month partition before its write ... CI's fresh database had no release_chunks partition yet: the batch store creates it on its own path, the namer's test wrote a chunk without it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-26 17:08:19 +01:00
Daan MeijerandClaude Fable 5.1	e135076fcd	The pending ladder in the prober: unnamed releases probed cheapest first, signatures learned, the named moved into the catalog ... pending_ladder.ts claims the oldest waiting pending releases' next target (par2, archive, lone, 7z-tail in that order) as at least PENDING_SHARE of each claim; a usable name (the largest named file of a par2 set or a listing, or a lone file's yEnc name, neither packaging nor random) hands the release to the namer, no name the next target or the end of the climb; climbs count on pending_signatures per (tool, group, poster) and (tool, group), and a signature with 100 climbs and 0.5% named or fewer is dropped: its waiting releases are discarded without a probe, the rules' sample excepted. pending_namer.ts reads a named release's articles again from the corpus or by XOVER and writes it to the catalog under the pending key (source weak-stem, the name as inner name) with its chunk and candidates. Migration 6400; config PENDING_*. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-26 13:41:30 +01:00