5 Commits

Include renames

Author	SHA1	Message	Date
Daan MeijerandClaude Fable 5.1	8f5f83b4ea	Deploying voyager 3 without its edge worker: the no-edge marker, history replayed into the catalog ... deploy.sh and the nightly resume leave the edge stopped while .cache/no-edge exists (range by range it would split releases at every edge with no merger left). deploy/replay-window.sh takes DB and OUT and passes REPLAY_INTO_CATALOG=1, which lets replay:corpus write a database not named *_replay or *_scratch (never the test one). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-26 16:30:56 +01:00
Daan MeijerandClaude Fable 5.1	9cf85e09d8	Nothing enters the catalog without a usable name: the pending store (decision f amended) ... An unnamed release (no readable file name) is written to pending_releases (migration 6300, the HDD) with its keys, counts, article span, upload tool and probe targets, instead of releases, release_texts, posters and a chunk. The edge sends it with an empty payload and its tool; the batch store splits a batch by readable. The pending ladder (probes cheapest first, signature verdicts, the move into the catalog) comes next. The replay report shows the pending releases. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-26 13:18:14 +01:00
Daan MeijerandClaude Fable 5.1	6860e6ccaf	Albums: no numbered volumes or stray suffixes; the replay report counts the group's releases ... acs5152s1.11 is a volume, Broforce.vol00+01.par2.temp a par2: neither an album's member. replay:corpus reported every release in the scratch catalog as the group's. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-26 12:28:40 +01:00
Daan MeijerandClaude Fable 5.1	ae735361a0	Replay harness: a --to bound and the homelab window driver ... edge-bench --group and replay:corpus take --to <article> next to --from, so a replay covers one window of a group's history while the corpus holds others (the 2016 ranges next to 2021's and 2025's). deploy/replay-window.sh runs a window on homelab: every group whose window ranges are all stored is replayed once into usenet_replay through the voyager-3 app image, 4 groups at a time, looping while the corpus fill completes the rest. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-26 07:56:39 +01:00
Daan MeijerandClaude Fable 5.1	72e973d006	The replay harness: a group's corpus through one carried window into a scratch catalog ... replay:corpus runs edge-bench --group over a group's complete corpus ranges in article order (one window, carried from range to range, finished after the last range; edge/src/lease.rs holds the lease JSON the worker and the bench share) and stores every batch through BatchStore as the worker would, then reports releases finished, provisional, complete and the bytes per header of the NVMe and HDD tables. Refuses a database not named *_replay or *_scratch. The app image carries edge-bench; compose gets a replay profile for homelab. Design amended (REBUILD.md 1, 2, 5): the window is carried by one worker a group, no block leases and no block merger; provisional writes stay for the lease ends. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-26 00:27:09 +01:00