Update to Web App QA & Release Copilot

{
  "description": "Produce a traceable Ready, Ready with known limitations, or Not ready release verdict.",
  "included_files": [],
  "name": "decide-release",
  "skill_md_contents": "---\nname: decide-release\ndescription: Produce a traceable Ready, Ready with known limitations, or Not ready release verdict.\n---\n\n# Decide Release\n\n**Use when:** The user requests a final decision, launch checklist synthesis, sign-off or go/no-go review.\n\n## Workflow\n1. Gather the release scope, required checks, approval policy and current evidence report.\n2. Check critical flows, security/privacy, relevant accessibility gates, data migration integrity, supported browsers and rollback where required.\n3. Use the executable evidence checker when available for structured reports; it checks completeness, not the underlying truth of evidence.\n4. Distinguish failed gates, unknown gates and accepted non-blocking limitations; require explicit acceptance for material known limitations.\n5. Give Ready only if mandatory gates have verified passes and no P0/P1 blocker; use Not ready if a blocker exists or mandatory gate is unknown.\n6. Include a short rationale, evidence links, owners and exact next verification needed; avoid generic sign-off language.\n\n## Non-negotiable checks\n- A lack of evidence cannot be silently promoted into a pass.\n- No release approval or deployment action is implied by a conversational verdict.\n\n## Deliverable\nOne of three verdicts, concise supporting matrix, blockers, accepted risks and next action.\n\n## References\n- Read `../../references/release-gates.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"
}