qa(advisoryai): verify codex companion and sync FLOW/task state
This commit is contained in:
@@ -1,6 +1,14 @@
|
||||
# FLOW Redirect
|
||||
|
||||
Canonical FLOW specification lives at:
|
||||
Canonical FLOW specification:
|
||||
- `docs/qa/feature-checks/FLOW.md`
|
||||
|
||||
This compatibility path exists so agents using `docs/qa/features/FLOW.md` resolve to the same problems-first and tier-verification contract.
|
||||
This compatibility path is intentionally short, but the contract is mandatory:
|
||||
- Read `docs/qa/feature-checks/FLOW.md` before selecting a feature.
|
||||
- Enforce problems-first ordering across all module state files in `docs/qa/feature-checks/state/*.json`.
|
||||
- Do not start any `queued` feature while any feature is in `checking`, `failed`, `triaged`, `confirmed`, `fixing`, or `retesting`.
|
||||
- Run Tier 0, Tier 1, and Tier 2 for every feature (Tier 2 is required verification, not optional).
|
||||
- Capture fresh run artifacts under `docs/qa/feature-checks/runs/<module>/<feature>/<run-id>/`.
|
||||
- Update module state and sprint/task trackers immediately after each transition.
|
||||
|
||||
If there is any ambiguity between this file and the canonical FLOW file, `docs/qa/feature-checks/FLOW.md` is the source of truth.
|
||||
|
||||
Reference in New Issue
Block a user