AdventureBreaker

Bulk, looping bug-hunt for the ZorkAI engine: given a COUNT and a GAME (zork or planetfall), adversarially playtest in production and keep going until COUNT distinct, real bugs are found, confirmed, filed as GitHub issues against arsindelve/zorkai, and recorded in the coverage ledger — one bug per area, moving to a new part of the game after each. This is the `/play` skill run in a loop with the per-bug user-confirmation waived, so use it whenever the user gives a NUMBER of bugs to hunt: "find ten bugs in planetfall", "find and log 5 bugs", "loop zork until you find 8 bugs", "do a bulk bug hunt", or `/find-bugs 10 planetfall`. For a single bug WITH per-bug confirmation, use `/play` instead.

Adversarially playtest the ZorkAI engine's Zork I or Planetfall in production to find ONE new, real bug. Black-box play through the AdventureBreaker harness (real prod HTTP), using the walkthrough spine to reach deep states and the coverage matrix to pick what to probe; stay black-box until something looks wrong, then go white-box (engine C# + original ZIL) to confirm it's a genuine divergence. On a confirmed bug, ask the user to confirm, file a GitHub issue against arsindelve/zorkai, record it in the coverage ledger, then commit + push the ledger and STOP. Invoke as `/play planetfall`, `/play zork`, or with a focus area: `/play planetfall rift`.

Verify a shipped ZorkAI release in production. Given a release number (a tag like 1.6.5), look up its GitHub release notes (the merged PRs / fixes), confirm the release actually deployed to prod, then smoke-test each shipped fix and feature LIVE through the AdventureBreaker harness — driving the walkthrough spine to each affected area and asserting the fixed behavior a real player would see. Reports a pass/fail matrix; if a shipped fix regressed (doesn't work in prod), surfaces it and, on user confirm, files a GitHub issue and records it. Invoke as `/test 1.6.5` (or `/test` for the latest release).