2.3 KiB
2.3 KiB
QA, Release, and Docs Roadmap
Status: Draft
Parent: docs/ROADMAP.md
Phase Q0 — Foundations
- Define local run commands
- Define test commands
- Define typecheck commands
- Define smoke-check commands
- Define manual QA matrix
Phase Q1 — MVP Coverage
- Backend CRUD/search behavior coverage
- Web flow coverage
- Mobile smoke coverage
- Platform integration smoke coverage
- Artifact/task/relationship behavior coverage
Phase Q2 — Agent Coverage
- MCP tool tests
- Approval workflow tests
- Audit verification tests
- 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.mdphase 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
- run:
- 2026-03-10 — Backend verification materially advanced:
backendnpm run typecheckpassesbackendnpm testpasses- MCP contract tests and executable MCP tool tests now pass
- MCP scope-guard regression tests now pass for invalid product-scoped mutating requests
- current route-module coverage is still shallow in places and should not yet be treated as full CRUD/integration behavior coverage
Open Questions
- Should smoke checks include both
/healthand/readyonce 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