track-review ยท diff
git:20260924.f9963aa to git:20260927.1cfa911
5 added, 1 removed. Audit A to A.
---
name: track-review
description: Independently assess an exact TODO Flow change against condition IDs and verification evidence.
---
# track-review
Read installed `project.json` for STATE and primary language, then STATE's `config/1.json`. Use the project language for user-facing reports and new documents unless explicitly overridden; default to English. Preserve protocol keys, identifiers, commands and source quotations.
Use a fresh read-only context, independent of the authoring session. Read the actual files/diff, goal revision and verification evidence. Return summary, verdict (met/unmet/cannot-assess), and exactly one conditions row per condition ID with verdict and evidence. Identify real failures and uncertainties; don't invent test execution.
+ Assess the selected outcome using recorded user decisions and the existing invariants affected by the change. Tie each required correction to a condition and a demonstrated failure or missing evidence for that condition. A preferred design, hypothetical risk, optional feature or unrelated defect is not by itself an unmet condition. Record useful out-of-scope observations as optional findings; do not require them for this track to finish. Keep verification proportional to the changed behavior rather than demanding every conceivable failure scenario. If a registered condition conflicts with a later user decision, identify the exact conflict for scope reconciliation instead of silently strengthening or waiving it.
+
+ If the selected conditions are met but mandatory verification fails on an unrelated pre-existing defect, report condition satisfaction and the failed gate separately. Landing/completion remains blocked. Resolve the gate using existing authority or explicit scope reconciliation; do not waive verification or silently require that unrelated repair within this track.
+
Request bounded correction work when unmet, land only for an authorized land endpoint, or complete for a review-only endpoint. The runtime publishes your full assessment on the exact PR head as a COMMENT when the GitHub account owns that PR. This is independent agent review, not a GitHub APPROVE from another account.
- Record extra observations as findings[{observation,evidence}] or additional condition assessments. After authorized landing, track-triage compares them with actual landed code. A required unmet condition still blocks landing; optional findings do not replace the required verdict.
+ Use registered condition IDs only in `conditions`. Record extra observations as findings[{observation,evidence}]. After authorized landing, track-triage compares them with actual landed code. A required unmet condition still blocks landing; optional findings do not replace the required verdict.