refactor(codex-playbook): согласована оптика тонкого мастера

- Зачем:
  - нужно сохранить контекст координатора и устранить расхождения с зеркальным playbook.
- Что:
  - закреплены делегирование, маршрутизация моделей и ограничение кругов ревью.
  - добавлены файловый договор ревью и согласованная эмпирика прогонов.
  - исправлены сборка слепых линий и компактные статусы находок.
- Проверка:
  - quick_validate.py, git diff --check и проверка локальных Markdown-ссылок.
This commit is contained in:
Dmitriy Dementiev committed 2026-07-13 13:07:52 +03:00
1 parent a4985b365d
commit 6cc1b26ce4
12 files changed
+470 -237

No files matched your search

@@ -1,15 +1,17 @@
# Triage blind-review findings
# Triage independent-review findings
The review indexes below are immutable input. Process every finding and change
nothing outside their scope. For each finding, either:
The review reports below are immutable input. Process every stable finding ID
and change nothing outside their scope. Assign exactly one disposition:
- fix it and name the contract or check that proves closure; or
- reject it with evidence from the contract and a check, never a bare claim.
- `FIXED`: change it and name the contract or check that proves closure;
- `REJECTED`: cite the contract and a check, never a bare claim;
- `OUT_OF_SCOPE`: explain the boundary decision needed;
- `NEEDS_DECISION`: state the unresolved product, architecture, or risk choice.
Do not commit or stage changes. Propose accepted rejections and residual risks
for the orchestrator to own and record as durable task decisions. The
orchestrator cannot silently accept risk; authority must come from the user or
already be explicit in the task.
Do not commit, stage, or rewrite the source reports. Write detailed resolutions
to REPORT. Return only:
Write a full resolution report to the path supplied by the caller. Return only
status, counters, executed checks, and that path in the final message.
- overall status and disposition counters;
- one line per finding: `ID | disposition | one-phrase essence`;
- questions for the coordinator and executed-check counters;
- `REPORT: <absolute path>`.