Track QA

Deprecated 2026-09-01. Every QA.md in the portfolio was deleted by decision on 2026-08-24, and the cc-dash /qa views read empty by design. Do not run any mode below: do not generate, update, audit, migrate, or resume a QA.md, and do not refile checklist items. A behavior that needs a human to exercise it is filed as one roadmap item (a playthrough, a parity gate, a release sign-off) with track-roadmap. This file is kept for one release so the cc-dash/qa@1 schema stays documented, then it is removed.

Overview

Maintain QA.md in the project root — the manual checklist of things a human must exercise (visual rendering, multi-step flows, race conditions, real integrations) before a release is ready. Tests prove correctness; QA proves shippability. Don't duplicate test coverage: if a unit or integration test can verify it, write the test instead.

The cc-dash/qa@1 schema below is machine-parsed, so its markers are exact. Everything else here is guidance to adapt to the project in front of you.

Workflow

Every mode runs the same three phases: read the current state → propose a concrete diff → write only after the user confirms. The confirm gate matters because a QA list the user didn't agree to is a list nobody runs.