fix

scripts/daily.sh

@@ -1,5 +1,5 @@
 #!/usr/bin/env bash
-# Run one simulated day inside the running container.
+# Run one day of the belt inside the running container.
 #
 #   scripts/daily.sh [daily flags...]
 #
@@ -9,7 +9,7 @@
 # Environment:
 #   HALCYON_CONTAINER   container name (default: halcyon, as in docker-compose.yml)
 #
-# The world settings (WH_SEED, WH_ASTEROIDS, ...) come from the container's
+# The world settings (HALCYON_SEED, HALCYON_ASTEROIDS, ...) come from the container's
 # environment, so the daily run always matches the server.
 set -euo pipefail
 

scripts/manual-pdf.sh

@@ -0,0 +1,10 @@
+#!/usr/bin/env bash
+# Render docs/manual.md to docs/generated/manual.pdf, for a locally run server
+# (go run ./cmd/server serves that path at /manual.pdf by default). Needs Docker.
+# The compose deployment uses scripts/render-manual.sh instead.
+set -euo pipefail
+cd "$(dirname "$0")/.."
+mkdir -p docs/generated
+docker build --quiet --target manual -t halcyon-manual .
+docker run --rm -v "$PWD/docs/generated:/out" halcyon-manual
+echo "wrote docs/generated/manual.pdf"

scripts/render-manual.sh

@@ -0,0 +1,13 @@
+#!/usr/bin/env bash
+# Render docs/manual.md to the PDF served at /manual.pdf, without touching the
+# running app: the renderer writes into the volume the web container reads, and
+# the new file is picked up on the next request (no restart).
+#
+# Takes a couple of minutes; run it in the background after a deploy:
+#   scripts/render-manual.sh > /tmp/render-manual.log 2>&1 &
+set -euo pipefail
+cd "$(dirname "$0")/.."
+echo "$(date -u +%Y-%m-%dT%H:%M:%SZ) rendering the manual..."
+docker compose --profile manual build --quiet manual
+docker compose --profile manual run --rm manual
+echo "$(date -u +%Y-%m-%dT%H:%M:%SZ) done: /manual.pdf now serves the new render"