real-e2e-acceptancelisted

# Real E2E Acceptance ## Overview Real E2E acceptance means the evidence level matches the claim. It is a gate bundle, not one command: automated Playwright, Visual QA, backend/API checks, observed or approved-real runtime paths, and packaging gates are selected according to the touched surface. Stubbed, fixture, Vite renderer, observed-local, approved-real, and packaged-release checks are different evidence levels and must not be mixed. ## When To Use - Before saying a branch is ready to merge because E2E passed. - Before claiming real login, real CLI/model/API, packaged Tauri, installer, icon, sidecar, signing, release, performance, or memory-leak acceptance. - When adding or changing `scripts/verify-*`, Playwright specs, visual checks, API contracts, Hub/Edge routes, Desktop/Web/Mobile workflows, or runtime adapters. - When reviewing a handoff, PR, or roadmap item that says "real", "approved-real", "full stack", "release gate", "真实闭环", or "端到端". ## Evidence Levels | Level | Machine label | Proves | Does Not Prove | |---|---|---|---| | Fixture/unit | `fixture-unit` | Pure contracts, normalizers, model logic | Network, browser, runtime, packaging | | Playwright UI E2E | `playwright-ui` | Real browser interaction, ordering, scrolling, route guards, visible state | Packaged Tauri, real login, real CLI/model/API | | Visual QA | `visual-qa` | Screenshot, pixel/geometry, responsive layout, occlusion/overflow, visual regressions | Data correctness, backend health, runtime e