game

# Create a game people can play Read the workspace and [project contract](references/project.md). Preserve working source, approved components and the person's decisions. Use the coding agent to author original mechanics in `game/rules.mjs` and their physical components/rulebook in `game/project.json`. Build an end-to-end game: setup, meaningful choices, chance if any, visible consequences, scoring, ties and an ending. Any style of self-contained component face can be embedded as original or supplied SVG/PNG/JPEG/WebP artwork. Numeric settings are explicitly authored design parameters; there is no fixed genre enum or fake generation button. Do not make people write the JavaScript. Run `node tools/build.mjs`, then play the actual game in the viewer. The person can edit cards, quantities, values, color, artwork and rulebook; lock approved components; save source; undo edits; and apply a new edition while retaining the old playable game and replay. Keep these capabilities when adapting the renderer for the user's brief. For a different presentation, change the studio source deliberately and recheck its exports and accessibility. Run `node tools/check.mjs --seeds 80`. Its uniform-choice simulations measure only the supplied seeds and policy. An optional authored bot receives observations and legal actions, not hidden state. Compare distributions with clear policy names; never imply that automated play proves fun, fairness, human strategy or commercial quality. Play real deci...