Three paths that stopped being true when the packages split

[dhobi]

Follow-up to #279, which documented these rather than changing them. Each is a default that was correct when there was one root, and that the move to four packages made wrong. All three fail silently — none is on a path CI takes, which is why they survived.

taoot/tests/browser/driver.ts pointed at the front door

APP_URL falls back to a local dev server, and the fallback stayed 5173 when Titanic's page moved to its own Vite root on 5174. A bare npx tsx taoot/tests/browser/playthrough.ts asked the site for a play/ it does not serve and got the sibling signpost — a 404 page explaining which server to start, which is a puzzling thing for a suite to try to boot a game out of.

CI never saw it: browser.yml passes APP_URL explicitly, which is also why the default could rot without a red tick anywhere.

Verified by running menu-movie.ts with the variable unset — it boots, plays menu.mov and clicks its regions:

movie: menu.mov (7 frames, interactive)
movie click (460,350) frame 1 -> type 2 "frame2"
movie: nightdive.mov segment 2/2 (3 frames, interactive)

taoot/tools/flowmap.ts looked beside the wrong directory — twice

rootDir defaulted to the bare string "gamefiles", resolved against the working directory, naming a path that no longer exists from the repository root. It now goes through gamefilesRoot(), which resolves from the file and honours TAOOT_GAMEFILES — as everything else in that directory already did.

The second one matters more. The publish step computed the repository root as one level up from taoot/tools/, from when the tool lived in tools/. So docs/public was looked for at taoot/docs/public, and the whole publish sits behind existsSync — a wrong path is indistinguishable from "you have no docs checkout", the run still reports success for everything else it wrote, and the interactive flow map quietly stopped being regenerated at the move. git log on docs/public/flow-map/ shows one commit, the initial import.

Same bug for node_modules: a workspace package's own directory holds its symlinks and none of the hoisted dependencies, so the vendor copy could not have found cytoscape either.

Before / after, same command:

(docs/public not found — skipped publishing the interactive map)
published interactive map -> docs/public/flow-map/index.html

tools/dumpscripts.ts assumed a rip at the root

It is a shared tool — it works on any rip because it takes one as an argument — so it may not import a game to find one. The default is discovered instead: the two environment variables the runner sets, then each game's gamefiles/ resolved from this file, and a named error rather than a stack trace when there is none.

invocation	result
from the repo root, no args	2,927 files, 17,111 scripts
from taoot/, no args	identical
explicit dust/gamefiles	326 files, 423 scripts
both rips absent	no rip found: pass one as the first argument, or set TAOOT_GAMEFILES / DUST_GAMEFILES., exit 1

Docs

#279 described all three as known-stale and told the reader to work around them (export APP_URL=…, spelling out taoot/gamefiles in every example). Those passages now describe what the code does. ci.md's "the dev server does not get port 5173" is now 5174, which is the port the runner actually has to stay off.

Not included, deliberately

Running the two tools rewrites taoot/tests/playthrough/nav/shipgraph.gen.ts and the flow map's DATA, and both come out different here — 271 → 326 trips — because this machine has seven trees installed where whoever last generated them had fewer. demo in particular is a different cut of the game, not a translation, so it contributes genuinely different scripts.

That makes regeneration a real change to what the playthrough navigator reads, and it depends on which editions the generating machine happens to have. It should be its own commit, made on purpose, rather than a side effect of fixing a path. Both files are reverted here.

Verified

npm test 534/534 · npm run test:playthrough 30/30 · tsc --noEmit clean · VitePress build clean · all three tools exercised from two working directories each.

🤖 Generated with Claude Code