- Зачем: - Актуализирована координация под Astra с сохранением замысла и бюджета контекста. - Что: - Разделены роли Astra, Sol и Luna; выбор приемов оставлен координатору. - Сохранены независимое ревью, триаж и проверка соразмерности исправлений. - Обновлены нативные механики и необязательная линия Claude CLI. - Проверка: - Проверены Markdown-ссылки, YAML и git diff --check; описано ограничение валидатора. - Пройден поведенческий сценарий с тремя тестами и независимое ревью Claude. - Перепроверены находки и фактическое продолжение фоновой сессии Claude.
27 lines
1.2 KiB
Markdown
27 lines
1.2 KiB
Markdown
# Narrow re-check
|
|
|
|
Continue from your original review. Read that report, the resolution report,
|
|
and the new reviewed version. Re-check only your original findings and changes
|
|
immediately adjacent to their resolution.
|
|
|
|
For every `FIXED` or `REJECTED` ID report `CLOSED`, `NOT_CLOSED`,
|
|
`REJECTION_VALID`, or `REJECTION_INVALID` with concise evidence. Carry
|
|
`OUT_OF_SCOPE` and `NEEDS_DECISION` into the index unchanged; do not
|
|
re-judge them or include them in your verdict. They remain open for their
|
|
owner. Judge a rejection by its contract and evidence. For a `FIXED`
|
|
resolution also report
|
|
`PROPORTIONATE` or `OVERREACH`; put your own earlier prescription on trial
|
|
and price added complexity against the risk it removes.
|
|
|
|
Narrow scope limits exploration, not honest reporting. Give a newly exposed
|
|
adjacent defect a new stable ID and return it for triage. `OVERREACH` is an
|
|
upward signal and does not by itself reopen the original defect.
|
|
|
|
Preserve sources and persistent state. Write the detailed re-check to REPORT.
|
|
Return only:
|
|
|
|
- `VERDICT: APPROVED | CHANGES_REQUESTED`;
|
|
- status counters;
|
|
- one line per original or new ID: `ID | status | one-phrase essence`;
|
|
- `REPORT: <absolute path>`.
|