generatelisted

# Generate tests Input: `$ARGUMENTS`. A path to a test design, a ticket key, or a described behaviour. ## When to delegate If the input is a design with more than about three rows, hand it to the `test-author` agent. It reads a lot of files (the profile, the conventions, the existing suite) and none of that needs to come back into this conversation. For one or two tests, or when the user is iterating and wants to see each step, do it here and follow the same rules. ## Steps **1. Read the setup.** `qa-context <platform>`. Then read the whole `CONVENTIONS.md` for the resolved profile. **2. Read the design.** If the input is not a design, run `/qa:design` first, or at minimum agree the expected result with the user before writing an assertion against it. **3. Read the neighbours.** Two or three existing tests from `layout.tests`. Where they disagree with the conventions file, the existing tests win, and the gap is worth mentioning. **4. Write only the automatable rows.** Rows marked `no` or `later` stay unwritten. Rows at a layer this project does not have stay unwritten, and you say which and why. **5. Run it.** `commands.test_one` from the profile, with `{file}` and `{title}` substituted. **6. Prove it can fail.** Break the expected value, run again, confirm it goes red for the right reason, put it back. A locator that matches nothing produces a test that never asserts anything and passes forever. **7. Lint.** `commands.lint` if the profile has one. ## Report - F