Update to Web App QA & Release Copilot

{
  "description": "Turn a web defect, screenshot, trace or error report into an actionable bug investigation.",
  "included_files": [],
  "name": "triage-bug",
  "skill_md_contents": "---\nname: triage-bug\ndescription: Turn a web defect, screenshot, trace or error report into an actionable bug investigation.\n---\n\n# Triage Bug\n\n**Use when:** The user reports a broken flow, screenshot regression, error, console trace or customer issue.\n\n## Workflow\n1. Separate expected behavior from observed behavior and reproduce only with available permission and tools.\n2. Record route, build, device/browser, role, locale, network, feature flags and relevant initial data.\n3. Identify the smallest reliable steps and capture console/network/screenshots/traces with sensitive values redacted.\n4. Localize the likely layer: UI, routing, auth, backend, database, environment, dependency or unknown; cite evidence for hypotheses.\n5. Assign P0-P3 severity from real impact and confidence; distinguish suspected root causes from confirmed causes.\n6. Specify smallest verification, regression test and acceptance conditions. Fix code only if user explicitly asks.\n\n## Non-negotiable checks\n- Never turn every screenshot pixel shift into a P1 blocker.\n- Do not represent speculation as observed failure.\n\n## Deliverable\nOne reproducible bug record and targeted regression recommendation.\n\n## References\n- Read `../../references/severity-and-triage.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"
}