QA

Home for qa-engineer artifacts — test plans, regression suites, playtest scenarios, anti-cheat metrics, MR review notes.

What lives here

Artifact	Owner	When it lands
Backend test plans (NestJS / Prisma)	`qa-engineer` paired with `backend-engineer`	Per backend phase (currently 11d-1, 11d-2 implemented; 103/103 tests passing as of 2026-05-20)
Mobile / watch test plans	`qa-engineer` paired with `mobile-developer`	Phase 13+
Regression suites	`qa-engineer`	After first beta cohort feedback
Playtest scenarios	`qa-engineer` paired with `mechanics-designer`	Closed beta milestone (D-009 phasing)
Anti-cheat metrics + thresholds	`qa-engineer` paired with `tech-architect`	When restrictive anti-cheat (D-007 §3) lands
MR review notes	`qa-engineer`	Per MR (currently inline in commit history, no standalone artifact yet)

What does NOT live here

The actual test code — backend/src/**/*.spec.ts and future mobile / data test files.
The Zod schemas validating content — data/src/schemas/.
ADRs about anti-cheat strategy — wiki/src/content/docs/tech/.
Canonical decisions about test posture — wiki/src/content/docs/canon/decisions/ (per-decision files; see index.md for the table).

Status

Placeholder. First page lands when qa-engineer is dispatched on a real artifact — likely the closed-beta playtest scenario set or the anti-cheat metric threshold spec.