namht-qalisted

# namht-qa — user story → test cases covering OLD + NEW business flows For QA: take a user story and produce a **test plan a tester can execute**, that deliberately covers BOTH the new behavior AND the existing flows it could break (regression). Grounds the "old flow" in the repo's Knowledge Base (`10-core-flows`, `13-business-rules`, `modules/<m>`) and the code (real endpoints/handlers). This is **test design** — it does NOT write or run code (hand to `/namht-build` for automation if needed). ## Inputs - The **user story** (role / action / benefit) + its **acceptance criteria**. Accept it pasted, by ID, or from a `/namht-plan` output under `namht-sessions/`. If ACs are missing or vague, derive a draft set and flag assumptions (don't silently guess). - A **`/namht-build` session folder** (`namht-sessions/builds/<…>/`), if one exists — read `01-plan/plan.md` §2 (blast radius, cross-service consumers, risk matrix) and `07-evidence/EVIDENCE.md` (the AC → named-test map) and **reuse them instead of re-deriving**: the build already traced the callers. Your job is then the **delta** — manual/UI cases automated tests can't cover, regression targets the build's tests did NOT cover, and any AC the evidence marked ❌ or untested. Say which targets came from the build plan vs your own analysis. - The **feature/module** it touches (infer from the story; confirm via the KB/code). - If the repo has no `knowledge-base/`, say so — old-flow/regression coverage will be weaker;