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>

REBUILD.md

@@ -690,7 +690,15 @@ 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).
+numbers, (112) the homelab run). **Deployed 2026-10-26** (LOG.md (116)):
+voyager 3 runs on homelab without its edge worker (`.cache/no-edge`:
+deploy.sh and the nightly resume leave it stopped, since range by range
+it would split releases at every edge with no merger left), and history
+comes from the corpus through this driver into the catalog itself
+(`DB=usenet_rebuild OUT=.cache/replay-catalog`, the harness allowed by
+`REPLAY_INTO_CATALOG=1`), the prober's ladder, the merger and the judge
+working on it as it fills; the scratch run's numbers (63 groups) were
+read before (LOG.md (115)). The tail waits for the window worker.
 
 Next: the replay on homelab over the 2016 window (the NVMe bytes per
 header for real), the ordered range leases with the carried window in