Update to Web App QA & Release Copilot

{
  "description": "Identify and test web application user journeys with clear preconditions, actions and outcomes.",
  "included_files": [],
  "name": "map-critical-journeys",
  "skill_md_contents": "---\nname: map-critical-journeys\ndescription: Identify and test web application user journeys with clear preconditions, actions and outcomes.\n---\n\n# Map Critical Journeys\n\n**Use when:** The user wants E2E journey mapping, acceptance testing, or coverage for login, checkout, onboarding, forms, core workflows.\n\n## Workflow\n1. Determine personas/roles, environments, data fixtures, preconditions and highest-value tasks.\n2. Capture each journey as Given state → user action → observable outcome, including persistence and recovery after reload when relevant.\n3. Add negative paths: invalid inputs, expired sessions, permission changes, API failures and duplicate submissions.\n4. Prefer stable, user-facing assertions; identify external dependencies to stub or seed deterministically.\n5. When tools are available, execute the smallest critical path, capture actual outcomes, and distinguish passed, failed, blocked and untested.\n6. Export the journey inventory and hand off candidate automation to build-playwright-tests.\n\n## Non-negotiable checks\n- Never claim a simulated expectation was observed.\n- Do not request real passwords, tokens or live payment credentials in chat.\n\n## Deliverable\nJourney table with preconditions, assertions, environment, test data, evidence and status.\n\n## References\n- Read `../../references/critical-journeys.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"
}