post-deploy-qalisted

# Post-deploy QA ## Input Requirements Read before starting: - `user-spec.md` — acceptance criteria - `tech-spec.md` — Agent Verification Plan (AVP) section + technical acceptance criteria - `decisions.md` — deviations from plan (if exists) - Pre-deploy QA report (`logs/working/qa-report.json`) — check `deferredToPostDeploy` section for criteria that could not be verified pre-deploy - Confirmation that deploy is complete and environment is live If tech-spec has no AVP section — still proceed with acceptance criteria verification. ## Verification Methodology Two verification directions (both required): ### 1. Agent Verification Plan (AVP) Execute each step from AVP section in tech-spec: 1. Read AVP section — it lists verification steps with expected outcomes and MCP tools to use 2. For each step: - Use the specified MCP tool (Telegram MCP, Playwright, curl, bash, etc.) - Perform the described action on live environment - Compare result with expected outcome - Record: tool used, step performed, result 3. If MCP tool is unavailable — mark step as `not_verifiable`, continue with remaining steps **Checkpoint:** All AVP steps executed or marked `not_verifiable`. Proceed to acceptance criteria. ### 2. Acceptance Criteria Verification Verify all acceptance criteria from user-spec and tech-spec against live behavior, including criteria pre-deploy QA could not check without a live system. 1. Read pre-deploy QA report (`logs/working/qa-report.json`) → `deferredTo