# QA, Release, and Docs Roadmap

Status: Draft
Parent: `docs/ROADMAP.md`

# Phase Q0 — Foundations

- [x] Define local run commands
- [x] Define test commands
- [x] Define typecheck commands
- [ ] Define smoke-check commands
- [ ] Define manual QA matrix

# Phase Q1 — MVP Coverage

- [x] Backend CRUD/search test coverage
- [ ] Web flow coverage
- [ ] Mobile smoke coverage
- [ ] Platform integration smoke coverage
- [x] Artifact/task/relationship test coverage

# Phase Q2 — Agent Coverage

- [x] MCP tool tests
- [ ] Approval workflow tests
- [ ] Audit verification tests
- [x] Regression coverage for agent-mediated note changes

# Phase Q3 — Release

- [ ] Production-readiness checklist
- [ ] Release commands and docs
- [ ] Deferred-items list
- [ ] PRD and roadmap status update
- [ ] Local development workflow docs
- [ ] Agent ownership/runbook docs

# Continuous Documentation Tasks

- [ ] Keep PRD aligned with implementation reality
- [ ] Keep `ROADMAP.md` phase status current
- [ ] Keep workstream docs updated when scope changes
- [ ] Record known limitations and explicit deferrals

# Progress Notes

- 2026-03-10 — Added initial backend verification command set:
  - run: `cd backend && npm run dev`
  - build: `cd backend && npm run build`
  - test: `cd backend && npm test`
  - typecheck: `cd backend && npm run typecheck`
- 2026-03-10 — Backend verification materially advanced:
  - `backend` `npm run typecheck` passes
  - `backend` `npm test` passes
  - MCP contract tests and executable MCP tool tests now pass
  - MCP scope-guard regression tests now pass for invalid product-scoped mutating requests

# Open Questions

- Should smoke checks include both `/health` and `/ready` once local env is configured?
- What minimum regression matrix is required before MCP mutating tools begin landing?

# Blockers

- Shared platform integration smoke coverage is still pending.

# Deferred

- Production-readiness checklist
- Full manual QA matrix
- Agent ownership and release runbooks

# Done When

- [ ] Build/test/release flows are documented and repeatable
- [ ] QA coverage is good enough to support multi-agent development safely
- [ ] Docs reflect shipped state rather than planned-only state