* fix(#3370): state checkpoint gate semantics in executor dispatch prompts * fix(#3370): set changeset pr to 3478 * fix(#3370): keep gate rule in routing fragment under phase-6 ceiling --------- Co-authored-by: sim <sim@local>
This commit is contained in:
@@ -130,7 +130,7 @@ Run the loop below once per runnable plan in the wave, **one plan at a time** (`
|
||||
|
||||
**Before running the bash block, substitute the plan's identifiers into it** exactly as you do for the `Agent()` prompt on the harness path: replace `{plan_number}` and `{phase_number}` with this plan's values. They are template placeholders, not shell variables. `$ORCH_ROOT` and `$EXPECTED_BASE` are real shell variables, already assigned earlier in this step; `$WAVE_WORKTREE_MANIFEST` was initialized above.
|
||||
|
||||
First build the executor prompt. It is the **same prompt text the harness path's `Agent()` call uses**, with the harness-only framing removed — drop the `<worktree_branch_check>` build-time embed note and the `<parallel_execution>` harness block, keep `<objective>`, the execution context, and `<success_criteria>` verbatim. Assign it to a shell variable so it can be passed as one argument:
|
||||
First build the executor prompt. It is the **same prompt text the harness path's `Agent()` call uses**, with the harness-only framing removed — drop the `<worktree_branch_check>` build-time embed note and the `<parallel_execution>` harness block, keep `<objective>`, the execution context, and `<success_criteria>` verbatim. The checkpoint gate rule (#3370, in `per-plan-executor-routing.md`) applies here too: add no prompt text refusing or overriding auto-approval for the default `gate="blocking"` — only `blocking-human` always surfaces. Assign it to a shell variable so it can be passed as one argument:
|
||||
|
||||
```bash
|
||||
# Compose the executor prompt for THIS plan. Single-quoted multi-line
|
||||
|
||||
@@ -52,3 +52,22 @@ Routing applies to the `Agent()`-based dispatch (harness-worktree and sequential
|
||||
modes). The `orchestrator-worktree` isolation backend spawns executors via a
|
||||
separate process path that has no `subagent_type` and is not routed in this
|
||||
release.
|
||||
|
||||
## Checkpoint gate rule (#3370)
|
||||
|
||||
Loaded with the routing resolution so the orchestrator reads it immediately
|
||||
before composing each dispatch prompt, in every isolation mode.
|
||||
|
||||
On `checkpoint:human-verify` / `checkpoint:decision` tasks, `gate="blocking"`
|
||||
(the default) is auto-approvable in auto-mode — that is the executor's own
|
||||
`<checkpoint_protocol>` (`agents/gsd-executor.md`), and `checkpoints.md` (the
|
||||
full gate table) is embedded in the dispatch `<execution_context>` verbatim.
|
||||
Only `gate="blocking-human"` always surfaces to a human, regardless of
|
||||
auto-mode.
|
||||
|
||||
When composing the `Agent()` prompt, do NOT add text refusing or overriding
|
||||
auto-approval for a `blocking` gate. Orchestrator-composed instructions that contradict the
|
||||
executor's protocol win the executor's attention, stall autonomous runs at the
|
||||
checkpoint, and defeat `_auto_chain_active`/auto-advance for the common case.
|
||||
Executor-side gate semantics are already complete; compose nothing about gates
|
||||
beyond what the template already embeds.
|
||||
|
||||
Reference in New Issue
Block a user