fix(codex-playbook): уточнён вердикт ревью планов
- Зачем: - ревью высокоуровневых документов могло требовать преждевременных деталей и постоянно блокировать одобрение. - Что: - находки ограничены дефектами на уровне самого документа. - существенные отложенные риски отделены от блокирующих замечаний. - уточнено, что APPROVED допускает открытые вопросы будущей реализации. - Проверка: - quick_validate.py, git diff --check и проверка локальных Markdown-путей.
This commit is contained in:
1 parent
70b18b9e9a
commit
02a98df8c3
3 files changed
+35
-3
No files matched your search
+10
@@ -15,6 +15,14 @@ Use stable IDs with FINDING PREFIX:
|
||||
`PREFIX-N | BLOCKER|MAJOR|MINOR|NIT | file:line or task section | violated
|
||||
criterion | failure scenario | evidence | minimal verification`
|
||||
|
||||
A non-gating consideration has no stable ID, severity, or counter. Use it only
|
||||
for a material risk from a safely deferred decision, and do not prescribe the
|
||||
downstream implementation. It does not change the verdict.
|
||||
|
||||
Use CHANGES_REQUESTED only when at least one finding requires revision at the
|
||||
reviewed artifact's own level. APPROVED means that no such defect remains; it
|
||||
does not mean that every downstream question has been answered.
|
||||
|
||||
If there are no findings, record the reviewed scope and every executed check
|
||||
or tested hypothesis with its outcome. A bare approval is invalid.
|
||||
|
||||
@@ -25,6 +33,8 @@ Return only:
|
||||
- `VERDICT: APPROVED | CHANGES_REQUESTED`
|
||||
- severity counters;
|
||||
- one line per finding: `ID | severity | area | one-phrase essence`;
|
||||
- optional one-line material considerations:
|
||||
`CONSIDERATION | area | one-phrase risk`;
|
||||
- `REPORT: <absolute path>`.
|
||||
|
||||
Do not repeat the detailed report or reasoning narrative in the final message.
|
||||
Reference in new issue
Block a user