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>

deploy/replay-window.sh

@@ -8,13 +8,17 @@
 # from the deployment root:
 #   setsid nohup deploy/replay-window.sh > .cache/replay/driver.log 2>&1 &
 # No new group starts while the nightly pause is on (.cache/paused); the running ones finish.
+# DB=usenet_rebuild replays into the catalog itself (voyager 3 deployed, 2026-10-26: history comes from the corpus
+# this way until the window worker is built); the harness then needs REPLAY_INTO_CATALOG=1, passed here. OUT keeps
+# a run's logs and markers apart (.cache/replay-catalog for the catalog's).
 set -u
 ROOT=${ROOT:-/mnt/bulk/usenet-rebuild}
 PRIORITY=${PRIORITY:-0}
 PARALLEL=${PARALLEL:-4}
 MEMORY=${MEMORY:-12g}
 IMAGE=${IMAGE:-usenet-voyager3:latest}
-OUT=$ROOT/.cache/replay
+DB=${DB:-usenet_replay}
+OUT=${OUT:-$ROOT/.cache/replay}
 mkdir -p "$OUT"
 cd "$ROOT" || exit 1
 
@@ -34,7 +38,7 @@ replay() {
   say "$group: replaying $from–$to"
   if docker run --rm --name "replay-${group//./-}" --network usenet-rebuild --env-file .env \
       -e NODE_ENV=production -e HOST=0.0.0.0 -e PORT=3334 -e APP_URL=http://web:3334 -e SPOOL_DIR=/spool -e CORPUS_DIR=/corpus \
-      -e DB_HOST=postgres -e DB_PORT=5432 -e DB_DATABASE=usenet_replay -e CHUNK_TABLESPACE=pg_default \
+      -e DB_HOST=postgres -e DB_PORT=5432 -e DB_DATABASE="$DB" -e CHUNK_TABLESPACE=pg_default -e REPLAY_INTO_CATALOG=1 \
       -v "$ROOT/corpus:/corpus:ro" --memory "$MEMORY" "$IMAGE" \
       node ace replay:corpus --group "$group" --from "$from" --to "$to" > "$OUT/$group.log" 2>&1; then
     touch "$OUT/$group.done"