Update to Web App QA & Release Copilot

{
  "description": "Diagnose nondeterministic browser/CI tests without hiding real failures.",
  "included_files": [],
  "name": "debug-flaky-tests",
  "skill_md_contents": "---\nname: debug-flaky-tests\ndescription: Diagnose nondeterministic browser/CI tests without hiding real failures.\n---\n\n# Debug Flaky Tests\n\n**Use when:** Playwright tests fail intermittently, differ across machines or require repeated retries.\n\n## Workflow\n1. Collect reproducible failed runs, retries, traces, console/network output, CI timing and worker settings.\n2. Classify race conditions, shared state, data collisions, clock dependence, network variability, animation, unstable locators and environment gaps.\n3. Form competing hypotheses, use a narrow reproduction loop and change one variable at a time.\n4. Repair synchronization with web-first assertions, isolated fixtures and deterministic state; review whether increased timeouts merely hide an issue.\n5. Re-run the affected test across multiple workers/repeats and relevant browser projects; capture pass/fail counts and environment settings.\n6. If unresolved, quarantine only with explicit issue owner, risk and exit criterion; do not silently delete the test.\n\n## Non-negotiable checks\n- A passing retry does not prove a flaky bug is fixed.\n- Do not weaken assertions solely to make CI green.\n\n## Deliverable\nFailure classification, root-cause evidence, minimal fix and repeat-run results.\n\n## References\n- Read `../../references/playwright-practices.md` when relevant.\n- Read `../../references/evidence-model.md` when relevant.\n\nOnly claim tests, browser access, scans, deployments or specialist execution supported by actual tool evidence. Retain original user constraints and avoid unsolicited code changes.\n"
}