22 lines
1.0 KiB
Markdown
22 lines
1.0 KiB
Markdown
# Success Criteria
|
|
|
|
## Project Success
|
|
|
|
- Production cutover of the Go backend passes the executable contract suites under `contracts/` with real RDS/OSS/provider/Webhook dependencies, without visible user-facing behavior change.
|
|
|
|
## Task Completion Standard
|
|
|
|
- A task is complete when the Concurrent Task Gate and Planning Gate passed, the implementation meets its scope and constraints, verification commands pass, the task record is updated with outcome and promotion candidates, the drift check passes, and ownership is released from a clean worktree.
|
|
|
|
## Quality Checks
|
|
|
|
- `npm test` (full Vitest suite), `npx tsc --noEmit`, and `npm run build` pass.
|
|
- `go test -count=1 ./...` and `go vet ./...` pass for backend changes.
|
|
- `node scripts/check-ack-manifests.mjs` and `npm run deploy:check` pass for deployment changes.
|
|
- `check_project_docs.py` and `check_doc_drift.py --task-id <task_id>` pass for documentation changes.
|
|
- Diff hygiene: no generated binaries, secrets, or unrelated files committed.
|
|
|
|
## Last Reviewed
|
|
|
|
2026-08-14
|