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

Добавить status-команду для stage-loop

Browse Source
This commit is contained in:
dctouch
2026-05-09 13:07:12 +03:00
parent f628266e44
commit 73b9053bab
3 changed files with 113 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/orchestration/domain_scenario_loop_repo_adapter.md
+3
View File
@@ -95,6 +95,7 @@ python scripts/stage_agent_loop.py run --manifest docs/orchestration/<stage_loop
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 status --manifest docs/orchestration/<stage_loop>.json
python scripts/stage_agent_loop.py summarize --manifest docs/orchestration/<stage_loop>.json
```
@@ -141,6 +142,8 @@ It stores the GUI review under `artifacts/domain_runs/stage_agent_loops/<stage_i
`stage_loop_summary.json` also includes `next_step_guidance.command_templates`, so the next operator or agent pass can continue from machine-readable commands instead of re-inferring the workflow from prose.
Use `python scripts/stage_agent_loop.py status --manifest docs/orchestration/<stage_loop>.json` as the cheap read-only checkpoint before continuing a stage. It prints the current next action, closing gate, latest GUI run, latest repair coder status, and latest repair validation status without modifying artifacts.
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: