qa-configlisted

# Reading the QA setup Nothing in this plugin knows what stack a project uses until it asks. Run this first, always, before touching a test file or reasoning about the suite: ```bash qa-context # every stack in the config qa-context web # just one stack qa-context --paths # paths only, when you already know the contents ``` If `qa-context` is not on PATH, run it from the plugin: `bin/qa-context`. ## What comes back ``` config: /repo/qa.config.yml project root: /repo web: ts-playwright -> /plugin/profiles/ts-playwright ===== /repo/qa.config.yml ===== ...the whole config... ===== /plugin/profiles/ts-playwright/profile.yaml ===== ...commands, layout, templates, selector priority... conventions for web: /plugin/profiles/ts-playwright/CONVENTIONS.md ``` Read `CONVENTIONS.md` before you write or change any test. It is the difference between code that looks like it belongs in the repo and code that looks bolted on. It is not optional and it is not a summary of the profile, it holds the things the machine readable part cannot express. ## Which file answers what | Question | Where | |---|---| | What is this project, what are the house rules | `qa.config.yml` | | Which stack am I in | `stacks.<platform>.profile` | | Where does test code live | `stacks.<platform>.root` plus `layout` in the profile | | How do I run the suite, or one test | `commands` in the profile | | What locator should I reach for | `selector_priority`, then `CONVEN