feat: request detailed reviewer guidance from cycle 3
When a run is about to start its 3rd cycle, the host review bundle asks Codex to supply a step-by-step implementation plan via the new decision field implementationGuidance, which is injected into the executor fix prompt (with re-sent plan context) so the executor can converge faster. - Add DETAILED_GUIDANCE_CYCLE_THRESHOLD and bundle signal in reviewWorkflow - Add optional detailedGuidanceRequested/reviewerInstructions to the bundle - Add optional implementationGuidance to HostDecisionV1 (validated, <=20000 chars) - Inject guidance section and re-send plan/criteria on marked fix cycles - Cover with integration, executor, and config validation tests
This commit is contained in:
@@ -97,6 +97,8 @@ Generate a Codex review bundle after executor completion. Checks HEAD stability
|
||||
agent-workflow review --run <run-id>
|
||||
```
|
||||
|
||||
Once the run is at or past the guidance threshold — the executor cycle about to start is `>= 3` (i.e. reviewing cycle 2, so the next fix cycle would be the third round) — the bundle sets `detailedGuidanceRequested: true` and includes a `reviewerInstructions` string. This asks Codex, if it decides `fix`, to return a concrete step-by-step implementation plan so the executor can converge quickly.
|
||||
|
||||
### `agent-workflow decide`
|
||||
|
||||
Submit a Codex decision (fix, accept, or needs_human). A fix decision resumes the same executor session.
|
||||
@@ -105,6 +107,8 @@ Submit a Codex decision (fix, accept, or needs_human). A fix decision resumes th
|
||||
agent-workflow decide --run <run-id> --input <decision.json|->
|
||||
```
|
||||
|
||||
A `fix` decision may include an optional `implementationGuidance` string (up to 20000 characters). When present, it is injected verbatim into the executor's fix prompt under a `## Detailed Implementation Guidance` section, and the frozen plan's `planMarkdown` and acceptance criteria are re-sent alongside it so the executor has full context. This is the channel Codex uses to answer the bundle's `detailedGuidanceRequested` signal, and it flows through the normal fix, `retry-execute`, and `extend` paths.
|
||||
|
||||
### `agent-workflow retry-review`
|
||||
|
||||
Retry review after the executor has removed approved out-of-scope artifacts.
|
||||
|
||||
Reference in New Issue
Block a user