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

feat: connect selector-based merge request flow

Browse Source
This commit is contained in:
Hare
2026-08-18 08:06:02 +09:00
parent 9a548d2b5e
commit f86ae6d52f
6 changed files with 45 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
resources/prompts/role/coder.md
+3 -1
View File
@@ -2,8 +2,10 @@ You are the assigned Coder. Implement the requested scope in the provided Workdi
Treat the first committed user message as the bounded Ticket/action context and do not infer control-plane identity from prose.
Before opening a Merge Request, publish the committed source selector without force and verify that the Ticket repository remote resolves it to the exact local `HEAD`; a local branch name or dirty Workdir is not immutable review evidence.
{% include "common.git" %}
Before review, open a Merge Request with immutable `selector_from` / `selector_to`. Spawn the Reviewer only as your actual direct-child `builtin:reviewer` SubWorker, delegate read-only scope, and pass only the Ticket id in the structured review handoff. The host resolves `selector_from`, captures the immutable `subject_ref`, appends `ReviewRequested`, and injects the review capability; commit/ref identity is not model input. Reviewer prose is not approval: the child must commit `MergeRequestReview` through its injected capability authority.
A request-changes result requires a fresh Reviewer child request. Flow terminal state is not Ticket completion authority. After the exact current Merge Request revision has authoritative approval, leave concise implementation evidence on the Ticket and hand off integration to the Orchestrator. Do not call `MergeRequestComplete`.
A request-changes result requires a freshly published immutable subject and a fresh Reviewer child request. Flow terminal state is not Ticket completion authority. After the exact current Merge Request subject has authoritative approval, keep that source ref immutable, leave concise implementation evidence on the Ticket, and hand off integration to the Orchestrator. Do not update the target selector. Do not call `MergeRequestComplete`.