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>

deploy/replay-window.sh

@@ -33,7 +33,8 @@ replay() {
   local group=$1 from=$2 to=$3
   say "$group: replaying $from–$to"
   if docker run --rm --name "replay-${group//./-}" --network usenet-rebuild --env-file .env \
-      -e NODE_ENV=production -e DB_HOST=postgres -e DB_PORT=5432 -e DB_DATABASE=usenet_replay -e CORPUS_DIR=/corpus \
+      -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 \
       -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"