SILVER/NODEDC_1C
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Связать repair-pass со статусом stage-loop

Browse Source
This commit is contained in:
dctouch
2026-05-09 12:43:36 +03:00
parent fdf70b3d4f
commit b4f50346cc
3 changed files with 327 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/orchestration/domain_scenario_loop_repo_adapter.md
+9
View File
@@ -94,6 +94,7 @@ python scripts/stage_agent_loop.py plan --manifest docs/orchestration/<stage_loo
python scripts/stage_agent_loop.py run --manifest docs/orchestration/<stage_loop>.json
python scripts/stage_agent_loop.py ingest-gui-run --manifest docs/orchestration/<stage_loop>.json --run-id assistant-stage1-<id>
python scripts/stage_agent_loop.py prepare-repair --manifest docs/orchestration/<stage_loop>.json
python scripts/stage_agent_loop.py run-repair --manifest docs/orchestration/<stage_loop>.json --dry-run
python scripts/stage_agent_loop.py summarize --manifest docs/orchestration/<stage_loop>.json
```
@@ -148,6 +149,14 @@ python scripts/stage_agent_loop.py prepare-repair --manifest docs/orchestration/
This writes `repair_iterations/<iteration_id>/repair_iteration_plan.json`, `repair_prompt.md`, and `repair_checklist.md`. The plan enriches GUI repair targets with candidate runtime files and rerun instructions, so the next coder pass can start from a bounded business defect instead of a full transcript archaeology dig.
To materialize or execute the coder command for that repair iteration, run:
```powershell
python scripts/stage_agent_loop.py run-repair --manifest docs/orchestration/<stage_loop>.json --dry-run
```
`--dry-run` writes `repair_coder.command.txt`, records `repair_execution_summary.json`, updates `stage_loop_summary.json`, and prints the exact non-interactive Codex command without changing code. Without `--dry-run`, it executes the coder command with the prepared `repair_prompt.md`, writes `repair_coder_result.json`, captures stdout/stderr, records `repair_execution_summary.json`, and updates the stage next action to rerun/ingest, inspect, or stop for a decision depending on the coder status. After a real coder patch, rerun the same semantic pack or GUI session and ingest the new `assistant-stage1-<id>`.
## Placeholder contract
Scenario questions can reference earlier step outputs with placeholders such as: