Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity

fix: give reviewer write-scoped command tools

Browse Source
This commit is contained in:
Hare
2026-08-25 04:45:17 +09:00
parent d69c367285
commit 1fb2949561
6 changed files with 64 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/development/work-items.md
+1 -1
View File
@@ -242,7 +242,7 @@ Implementation normally happens in a child git worktree created by the Orchestra
### 5. Review
The assigned Coder launches the Reviewer as an actual direct-child `builtin:reviewer` SubWorker with read-only scope and a structured handoff bound to the current immutable Merge Request revision. Server authority revalidates the parent assignment, Runtime-owned child session, effective profile, one-shot review attempt, and revision; prose output is not approval.
The assigned Coder launches the Reviewer as an actual direct-child `builtin:reviewer` SubWorker with write scope, so it can use the Workdir command tools required for inspection and validation, and a structured handoff bound to the current immutable Merge Request revision. Server authority revalidates the parent assignment, Runtime-owned child session, effective profile, one-shot review attempt, and revision; prose output is not approval.
The Reviewer records the structured result with `MergeRequestReview`. Request changes requires a new immutable revision and a fresh child attempt. The Orchestrator uses `MergeRequestReadinessCheck` and then `MergeRequestComplete` for guarded integration with operation-id dedupe/CAS semantics; Flow transitions are not completion authority.