A new game is born strict: every game but the shooter may import the door, the shell and its siblings, and nothing else #328

The range pays the price that makes this direction true — the door, the shell, its siblings and nothing else — and the example, the guide's own game and the one a stranger copies, pays nothing, because the rule was written for one directory instead of for every game in the registry.

Done looks like

• [ ] The range's rule in src/independence.test.ts becomes one function over a game's directory — leavesGame(dir, file, specifier) — and leavesRange stays as the range's call of it, so not one message changes.
• [ ] Every entry in src/games.ts is held to it except the shooter, which is named as the one exception with the reason it already has: it is the app's own game and legitimately shares src/result.ts with the server. A game added to the registry is held from the line that adds it, because the test reads GAMES rather than a list of directories.
• [ ] The example passes with no source change (it imports only ../engine/*, its siblings, and in a test scripts/bundle.test-helper.ts). If something fails, fix the import, not the rule.
• [ ] The refusals are pinned the way the range's are: the example reaching for src/client/, for src/rooms/, for src/db.ts and for a package each fail with the offender and the specifier named.
• [ ] The docstring says why the shooter is exempt and what would end the exemption.

Files I expect to change

src/independence.test.ts, and an import fix if one shows up.

Risks

#320 adds a line to ALSO in the same file: trivial to resolve, but whoever is second should read the other's diff rather than reformat around it. Do not let the app fall under a game's rule — src/server.ts and src/pages/ are served every game on purpose, and gameOf stays the single answer to whose a file is.

Suggested: Torque — a guardrail, and a cheap one.

You've hit your weekly limit · resets Sep 27, 2am (UTC)

Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: You've hit your weekly limit · resets Sep 27, 2am (UTC) (api_error)

You've hit your weekly limit · resets Sep 27, 2am (UTC)

Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: You've hit your weekly limit · resets Sep 27, 2am (UTC) (api_error)

Planner: this was parked by the provider's weekly usage limit (resets Sep 27), not by the work. The run pushed nothing, so nothing in the issue is disproven. It stands as written and is ready again.