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

Подготовить repair-итерации из stage GUI handoff

Browse Source
This commit is contained in:
dctouch
2026-05-09 12:29:41 +03:00
parent 2244c62554
commit fdf70b3d4f
4 changed files with 291 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
@@ -93,6 +93,7 @@ Canonical commands:
python scripts/stage_agent_loop.py plan --manifest docs/orchestration/<stage_loop>.json
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 summarize --manifest docs/orchestration/<stage_loop>.json
```
@@ -139,6 +140,14 @@ It stores the GUI review under `artifacts/domain_runs/stage_agent_loops/<stage_i
It also writes `stage_repair_handoff.md/json` next to the stage summary. That handoff is the preferred input for the next coder pass: it lists primary repair targets and sample user-facing failures without forcing the coder to reread the entire GUI conversation first.
To prepare the next repair iteration from that handoff, run:
```powershell
python scripts/stage_agent_loop.py prepare-repair --manifest docs/orchestration/<stage_loop>.json
```
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.
## Placeholder contract
Scenario questions can reference earlier step outputs with placeholders such as: