pre-deploy-qalisted

# Pre-deploy QA ## Input Requirements Read before starting: - `user-spec.md` — acceptance criteria - `tech-spec.md` — technical acceptance criteria - `decisions.md` — deviations from plan (if exists) - Project Knowledge — architecture.md, patterns.md (incl. Testing & Git Workflow sections) If user-spec or tech-spec missing — request before proceeding. ## Verification Directions Three verification directions (order doesn't matter): ### Test Suite Run all tests (unit, integration, E2E). All must pass. - Identify test runner from project config (package.json, pyproject.toml, Makefile, etc.) - Run full test suite - Record: total tests, passed, failed, skipped ### Acceptance Criteria Check every criterion from user-spec and tech-spec: - **passed** — criterion met, evidence provided - **failed** — the feature exists but does not meet the criterion - **not_verifiable** — cannot be checked without live environment, external service, or MCP tool (scope of post-deploy-qa) For each criterion — provide evidence (test name, code path, log output). ### Coverage Verification After test suite passes, verify that tests actually exercise the feature: - Each file in the feature's scope (from tech-spec "Files to modify") must have a corresponding test. Feature code without any test → `critical`. - If project has coverage tooling (jest --coverage, pytest --cov, vitest --coverage), run it. Coverage of feature files below project threshold → `critical`. - For each `passed` acceptance