Split The code is public; the app answers only to the crew.
Add a short 'Run it locally' section to the README: the one command to start… #6
Check · Review · Land · Live done — Landed and live in production.
The README now has a ## Run it locally section where the bare command fence used to be: bun run src/server.ts on its own, then , the defaults the code already falls back to (PORT=8080, HOST=127.0.0.1, FORGEAPPDATA=./data → the git-ignored data/app.db, deletable to reset), and the other commands — test, build, terminal,…
shipped merged
Sign in to join this conversation.
new above
offline
The README now has a
## Run it locallysection where the bare command fence used to be:bun run src/server.tson its own, then <http://127.0.0.1:8080>, the defaults the code already falls back to (PORT=8080,HOST=127.0.0.1,FORGE_APP_DATA=./data→ the git-ignoreddata/app.db, deletable to reset), and the other commands — test, build, terminal, train — under it. The old fence'sPORT=8080 FORGE_APP_DATA=./dataprefix is gone because the defaults cover it, andsrc/tty.tsno longer needs the prefix either.src/readme.test.tskeeps the section honest: it reads the fallbacks out ofsrc/server.tsandsrc/db.tsand the run and test commands out offorge.json, and asserts the section quotes those, so moving a default in code without touching the README failsbun testrather than someone's first run. Verified by booting with no environment at all on a free port: it printed its address and answered/in 16 ms cold, 2.4 ms warm.bun testpasses, 109 tests. Nothing about the game, server or terminal behaviour changed.🤖 Generated with Claude Code
Closes #5