3 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	f437929181	Homelab: the replay container's app environment; the nightly resume honours the v2 reset ... deploy/replay-window.sh passes the compose app environment (HOST, PORT, APP_URL, SPOOL_DIR, CHUNK_TABLESPACE) the ace command validates. The resume script starts only the coordinator (the corpus fill) while .cache/v2-reset exists: the voyager 2 catalog was reset on 2026-10-26 and its workers would fill it again. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-26 08:09:45 +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