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>

REBUILD.md

@@ -628,7 +628,7 @@ window holds a day of a group's segments in memory (the busiest group's
 ### The replay harness (built 2026-10-26)
 
 `node ace replay:corpus --group <name> [--dir CORPUS_DIR] [--from article]
-[--limit ranges] [--batch-chunks 5] [--no-finish]` (commands/
+[--to article] [--limit ranges] [--batch-chunks 5] [--no-finish]` (commands/
 replay_corpus.ts; design 8): a group's complete corpus ranges in article
 order through one window in the Rust edge (`edge-bench --group <dir>
 --rules rules.json --wire -`: the window carried from range to range, the
@@ -646,10 +646,16 @@ headers; bytes per header of the NVMe tables (releases, release_texts,
 posters, group_sets, rule counts and samples) and of those on
 CHUNK_TABLESPACE (release_chunks, probe_candidates, release_inspections).
 The app image carries `edge-bench` for it (Dockerfile); on homelab the
-scratch catalog is a second database on bulk (`usenet_replay`, migrated
-with the voyager-3 image, `groups` and `rule_sets` copied over), the
-corpus mounted read-only: not run there yet (LOG.md 2026-10-26 (111) has
-the first local numbers).
+scratch catalog is a second database (`usenet_replay`, default tablespace
+`nvme` like the catalog, the chunk tables on `pg_default`; migrated with
+the voyager-3 image built from the deploy cache's repo, `groups` and
+`rule_sets` copied over), the corpus mounted read-only.
+`deploy/replay-window.sh` runs a window there: each group whose window
+ranges are all stored is replayed once with the window's bounds as
+`--from`/`--to` (the corpus holds other windows of the same group), 4
+groups at a time, logs and `.done` markers in `.cache/replay/`, looping
+until the window is done (LOG.md 2026-10-26 (111) has the first local
+numbers, (112) the homelab run).
 
 Next: the replay on homelab over the 2016 window (the NVMe bytes per
 header for real), albums in the edge (design 3), the ordered range leases