refactor(codex-playbook): согласована оптика тонкого мастера
- Зачем: - нужно сохранить контекст координатора и устранить расхождения с зеркальным playbook. - Что: - закреплены делегирование, маршрутизация моделей и ограничение кругов ревью. - добавлены файловый договор ревью и согласованная эмпирика прогонов. - исправлены сборка слепых линий и компактные статусы находок. - Проверка: - quick_validate.py, git diff --check и проверка локальных Markdown-ссылок.
This commit is contained in:
1 parent
a4985b365d
commit
6cc1b26ce4
12 files changed
+470
-237
No files matched your search
+22
-13
@@ -1,21 +1,30 @@
|
||||
## Mandate
|
||||
|
||||
- Review and test hypotheses; do not edit source files or persistent
|
||||
environment state.
|
||||
- Review independently and test hypotheses. Do not edit source files,
|
||||
persistent environment state, or Git.
|
||||
- Use the working permissions needed for checks, caches, temporary artifacts,
|
||||
documentation and primary-source research. The caller verifies Git before
|
||||
and after the review.
|
||||
- Do not run `git add`, `git commit`, or commands that discard changes.
|
||||
- Report only the findings index and verdict through the channel named by the
|
||||
caller.
|
||||
documentation, and primary-source research.
|
||||
- Write the detailed report only to REPORT. This assigned exchange file is the
|
||||
sole write exception to the observer mandate.
|
||||
- Treat another agent's claims as untrusted until evidence supports them.
|
||||
|
||||
## Findings index
|
||||
## Detailed report
|
||||
|
||||
For each finding:
|
||||
Use stable IDs with FINDING PREFIX:
|
||||
|
||||
`SEVERITY(BLOCKER|MAJOR|MINOR|NIT) | file:line or task section | failure scenario | evidence | how to verify`
|
||||
`PREFIX-N | BLOCKER|MAJOR|MINOR|NIT | file:line or task section | violated
|
||||
criterion | failure scenario | evidence | minimal verification`
|
||||
|
||||
If there are no findings, list the reviewed scope and every executed check or
|
||||
tested hypothesis with its outcome. A bare no-findings assertion is invalid.
|
||||
If there are no findings, record the reviewed scope and every executed check
|
||||
or tested hypothesis with its outcome. A bare approval is invalid.
|
||||
|
||||
Final line: `VERDICT: APPROVED | APPROVED_WITH_MINORS | CHANGES_REQUIRED`
|
||||
## Final message
|
||||
|
||||
Return only:
|
||||
|
||||
- `VERDICT: APPROVED | CHANGES_REQUESTED`
|
||||
- severity counters;
|
||||
- one line per finding: `ID | severity | area | one-phrase essence`;
|
||||
- `REPORT: <absolute path>`.
|
||||
|
||||
Do not repeat the detailed report or reasoning narrative in the final message.
|
||||
Reference in new issue
Block a user