Update to Web App QA & Release Copilot

{
  "description": "Write or review maintainable Playwright tests focused on user-visible behavior.",
  "included_files": [],
  "name": "build-playwright-tests",
  "skill_md_contents": "---\nname: build-playwright-tests\ndescription: Write or review maintainable Playwright tests focused on user-visible behavior.\n---\n\n# Build Playwright Tests\n\n**Use when:** The user requests browser automation, test implementation, locator repair or E2E test coverage.\n\n## Workflow\n1. Inspect the repository test framework, Playwright version/config and existing fixture conventions before authoring code.\n2. Choose isolated test data, proper test IDs for stable contract boundaries, and role/label/text locators for user-facing controls.\n3. Use Playwright actionability and auto-retrying web-first assertions. Avoid arbitrary waitForTimeout and brittle nth-child or CSS selectors.\n4. Cover the critical happy path and one meaningful failure path per flow, asserting visible outcomes and persistence.\n5. Use browser/device projects only when required by support; collect trace on first retry and redact sensitive artifacts.\n6. Run tests only when executable tools are present; report counts, failing assertions, commands and artifacts, not invented passes.\n\n## Non-negotiable checks\n- Keep credentials in secure secrets managers or test fixtures, never hard-coded in generated tests.\n- Do not mock the core behavior being asserted away.\n\n## Deliverable\nActual test files or patch, commands to run, failure evidence and scope limits.\n\n## References\n- Read `../../references/playwright-practices.md` when relevant.\n- Read `../../references/critical-journeys.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"
}