Связать GUI-прогоны со stage-loop агентной петли

docs/orchestration/domain_scenario_loop_repo_adapter.md

@@ -92,6 +92,7 @@ Canonical commands:
 ```powershell
 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 summarize --manifest docs/orchestration/<stage_loop>.json
 ```
 
@@ -125,6 +126,17 @@ This bridge is intentionally business-first:
 
 Use this bridge when the operator would otherwise say “чекни прогон `assistant-stage1-...`”. The expected next step is no longer manual eyeballing first; it is: review by id, inspect `run_review.md`, map `repair_targets.json` into the current stage loop, patch, and rerun.
 
+For stage work, prefer the integrated command:
+
+```powershell
+python scripts/stage_agent_loop.py ingest-gui-run --manifest docs/orchestration/<stage_loop>.json --run-id assistant-stage1-<id>
+```
+
+It stores the GUI review under `artifacts/domain_runs/stage_agent_loops/<stage_id>/gui_run_reviews/<run_id>/`, updates `stage_loop_summary.json`, and writes the next stage action:
+- `continue_repair_from_gui_review_p0` when the GUI run exposes business-wrong or missing direct-answer defects;
+- `continue_repair_from_gui_review_p1` when the run is semantically usable but still noisy, over-broad, or poorly layered;
+- `manual_gui_confirmation_or_stage_close` when the GUI run is clean enough for final human confirmation.
+
 ## Placeholder contract
 
 Scenario questions can reference earlier step outputs with placeholders such as: