showdar-qualitylisted

# Showdar Quality ## Purpose - Decide what should be verified, which risks matter, and what evidence supports acceptance confidence. - Produce compact QA scenarios, manual test cases, risk matrices, compatibility plans, regression scope, release checklists, or complete bug reports. - Cover behavior beyond automated tests: exploratory, platform, permission, network, data, accessibility, localization, performance, and recovery quality. - Use `data/quality-patterns.csv` as a searchable prompt and read `references/qa-guide.md` when a broad verification plan is needed. ## When to use - QA needs scenarios, manual cases, risk-based coverage, acceptance verification, exploratory charters, or a regression scope. - A release needs a platform/browser/device matrix, smoke/sanity checklist, or evidence review. - A requirement needs coverage analysis across happy, negative, boundary, state, offline, concurrency, retry, or idempotency behavior. - A bug report is incomplete and needs reproducible environment, steps, actual/expected result, evidence, and impact. - The user asks what to verify, not how to implement an automated test. ## When not to use - Do not use this to implement unit, integration, component, or E2E tests; use `showdar-test` for automated test-level selection and code changes. - Do not use this as a code/diff defect review; use `showdar-review`. - Do not use this as the overall delivery-readiness decision; use `showdar-ship`. - Do not mutate application source, produc