test-per-ac-plannerlisted

## What It Does Maps each acceptance criterion to the narrowest useful verification path so important behavior does not reach implementation without a proof strategy. ## Use This When Use this after acceptance criteria exist and before coding or handoff, especially when the work spans multiple layers or mixes automated and manual verification. ## Inputs - Read the current acceptance criteria and sequence or story artifact first. - Read the existing test layout and stack verification guidance for the affected modules. - Read `references/verification-mapping.md` before selecting test layers. ## Procedure 1. Run `scripts/extract-ac-ids.sh <ac-file>` to load the canonical AC id set. 2. For each AC, choose the smallest test layer that can prove it; reuse existing test patterns/files before proposing new surfaces. 3. Assign each test a `T{ac}.{idx}` id whose `{ac}` segment matches the parent AC (script-checked). 4. Add manual verification only when automation is not practical. 5. Format per `assets/output.template.md` and run `scripts/check-coverage.sh <ac-file> <plan>` to find uncovered ACs; record those under `## Uncovered Criteria`. 6. Validate the final markdown with `scripts/lint-output.sh`. ## Output Contract - Return a heading named `Verification Plan`. - For each criterion, emit a third-level heading combining the AC identifier with its assigned test ids, e.g. `### AC-1.1 → T1.1, T1.2`. - Under each heading, provide a table with columns `Test ID`, `Layer`, `File`,