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/usenet-rebuild-resume.sh

@@ -6,13 +6,11 @@ exec 9>.cache/deploy.lock
 flock 9
 rm -f .cache/paused
 date "+%F %T resuming"
-if [ -e .cache/v2-reset ]; then
-  # The voyager 2 catalog is reset (2026-10-26, LOG.md (112)): only the coordinator (the corpus fill) runs until voyager 3
-  # is deployed; the edge, prober, merger, judge, spotter and spot inspector would fill the old catalog again.
-  echo "v2 reset: only the coordinator"
-  docker compose up -d --no-deps coordinator
+docker compose up -d --no-deps coordinator prober merger judge spotter spot-inspector
+if [ -e .cache/no-edge ]; then
+  # Voyager 3 without its window worker yet (deploy.sh, LOG.md (116)): the edge stays stopped.
+  echo "no-edge: the edge worker left stopped"
 else
-  docker compose up -d --no-deps coordinator prober merger judge spotter spot-inspector
   docker compose up -d --no-deps edge
 fi
 docker compose ps --format "{{.Service}} {{.Status}}"