sysadminandClaude Opus 4.8
429faccd08
Add reviewer_handoff_consistency validation for narrative vs mutation ledger contradictions, wire it into review_pr final-report rules, and document the blocked-review handoff template. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
22 lines
847 B
Markdown
22 lines
847 B
Markdown
# Blocked review submission handoff
|
|
|
|
Use when `gitea_submit_pr_review` or the terminal mutation gate blocks review
|
|
submission.
|
|
|
|
```text
|
|
## Blocked Review Submission Handoff
|
|
|
|
- Tool called: gitea_submit_pr_review
|
|
- Mutation attempted: yes
|
|
- Mutation rejected: yes
|
|
- No server-side state changed: confirmed
|
|
- Proof/source: <paste exact tool error or gate reason>
|
|
- Prior terminal mutation that consumed budget: <exact prior mutation or none>
|
|
- Review decision (local intent): <approve | request_changes | comment only>
|
|
- Server-side final decision marked: <yes with tool proof | no>
|
|
- Gitea review submitted: no
|
|
- Gitea review blocked because: <exact gate/error>
|
|
- Review mutations: none (submission blocked)
|
|
- MCP/Gitea mutations: <only mutations that actually occurred>
|
|
- Safe next action: rewrite handoff with consistent ledger before posting
|
|
``` |