squawklisted

# Squawk A squawk is what aviation calls a defect written into the aircraft's logbook by whoever just flew it. The word matters less than the discipline around it: the mechanic reproduces the defect before repairing anything, repairs the cause rather than the gauge that revealed it, and nobody signs the logbook without a functional check. This skill applies that discipline to one reported bug at a time. It is the reactive counterpart to a full QA pass: not a sweep of the product, one incident, run end to end. It depends on nothing but itself. **Front end only.** The defect gets reproduced and proven in a driven browser (Playwright, a browser MCP, whatever driver is available), by accessibility tree and locators, never by curling endpoints. An API-only symptom still closes through the screen where a user meets it. ## Where the fleet keeps its state Every path below written `.squawk/...` resolves under the fleet's shared root: `.qmw/squawk/...` at the repository top. One root is what lets the skills read each other - the gate another skill already established, the registry a past pass wrote, the log of what was repaired last month - instead of each one guessing at a sibling's private directory. A project set up before this convention keeps them at a bare `.squawk/`. **Read the legacy path when the shared root holds nothing**, work from what is there, and say once that moving it is a single `git mv`. Never write to both. ## Before the first squawk: setup If neither root