The repository tells the truth about the game it has become: what drift is, what the rule is, what the
numbers are, what a guest is, and how to run all of it from a clean clone.
Done looks like
[ ] README: drift in two sentences, the one rule, the shape of a round, how to play, how to run, the
file table rewritten to the modules that now exist, what the guest cookie is for and what losing
it means, and how the ladder scores.
[ ] Every constant a player can feel — tick rate, round length, thrust, decay, roster cap — is named
in one place, and the README says where.
[ ] forge.json still names run, test and tty, and all three work from a clean clone with no
data directory: a cold boot creates FORGE_APP_DATA, answers /, and runs a round.
[ ] No dependency was added; if one was, the README carries the line that justifies it.
[ ] AGENTS.md still describes the shape the code actually has — update its "to add a concept" list
if the world, the round or the socket changed it.
[ ] bun test green, and every command in the README is copy-pasteable.
The repository tells the truth about the game it has become: what drift is, what the rule is, what the numbers are, what a guest is, and how to run all of it from a clean clone.
Done looks like
file table rewritten to the modules that now exist, what the guest cookie is for and what losing it means, and how the ladder scores.
in one place, and the README says where.
forge.jsonstill namesrun,testandtty, and all three work from a clean clone with nodata directory: a cold boot creates
FORGE_APP_DATA, answers/, and runs a round.AGENTS.mdstill describes the shape the code actually has — update its "to add a concept" listif the world, the round or the socket changed it.
bun testgreen, and every command in the README is copy-pasteable.Files
README.md,forge.json,AGENTS.md,package.json(description).Risks Written too early this goes stale in a week — it is last on purpose. Describe what the code does, not what the map planned.
Fits Quill's brief.