carnival-lock-test

Add a new game to the Tessl Carnival midway, following the water cannon pattern and the house rules. Use when asked to build, add or create a carnival game or booth, such as ring toss, whack-a-mole or hook a duck.

Check that a laptop and fork are ready for the Tessl Carnival workshop (git, Node, the GitHub CLI, the Tessl CLI and credits, and a fork with Issues, Actions, Pages and the interaction lock on), then report a short pass or fix list. Only checks, and changes nothing without asking. Use when someone asks to check they're ready for the workshop, or before they start the core path in WORKSHOP.md.

Find docs and agent instructions in the carnival that no longer match the code, and file one GitHub issue per stale doc. Use when running the doc gardening maintenance loop, or when asked to check whether the README, AGENTS.md, a game's README or a skill is out of date. Files issues only; never changes code or docs.

Read recent code review on this repository's pull requests, find the mistakes reviewers keep catching, and file a GitHub issue proposing a rule so agents get it right next time. Use when running the rule mining maintenance loop, or when asked what the agent keeps getting wrong in review. Files issues only; never changes code or docs.

Turn on the GitHub features a fork of the carnival needs (Issues, Actions and GitHub Pages) using the GitHub CLI, lock the fork down so only its owner can open issues, comment and open pull requests, then deploy the carnival and share its link. Use when someone asks to set up their fork, turn on issues or Pages, lock down their fork, get a shareable link to their carnival, or when the Issues tab, CI checks or the Pages deploy are missing on a fork.

Find weak, dead or misleading tests in the carnival and file a GitHub issue for each one worth repairing. Use when running the test health maintenance loop, or when asked whether the tests actually check what they claim to. Files issues only; never changes code or tests.