testbook-generatelisted

# testbook-generate — the test book Follow the shared contract in `../README.md`. Prerequisites: `03-design.md` and `04-priorities.md` (else offer the missing step). Output directory: `.qaia/testbooks/<US-ID>/`. ## Generation rules (non negotiable) - **Gherkin, English keywords — always, whatever the project language**: `Feature / Background / Scenario / Scenario Outline / Given / When / Then / And / But`. Only the **prose inside a step** follows the project language. A French project still writes `Scenario:`, never `Scénario:`. This clause is explicit because the previous wording was not: a model given this skill emitted `Scénario:` and `Etant donné`, producing an unparsable file, having read "project language" as covering the keywords too. The ambiguity was ours. - **Atomic** — one scenario verifies exactly one behavior. No UI-step chains covering several cases. **Exactly one `When` (the action) per scenario; outcomes live only in `Then`** — never bury the action in a `Given` or the outcome in the `When`. `Background` is for shared *state* setup only. `Scenario Outline` + `Examples` covers partitions or boundaries of the *same* behavior, **merged only when all example rows share the same priority and confidence** — otherwise split. - **Journey exception**: at most one end-to-end scenario per US (use-case technique), tagged `@smoke`, single journey-level `Then`, excluded from atomicity accounting — see `istqb-design`. - **Preconditions are declarat