bmad-loop-resolvelisted

## Metodoloji Bu yuzey arastirma metodolojisine baglidir: `docs/bmad/research-methodology.md` — Mod A (sayisal) — loop cozumleme; E-id kaydi. Belgesel karar kod yazma izni degildir; kod her durumda Mod A mekanik onayini ister (run_experiment.py --verify + guard-code.sh). Uydurma kanit/olcum sahtekarliktir. # bmad-loop Escalation Resolution A `bmad-loop` run drove a story through dev → review, a session raised a **CRITICAL escalation** (work could not proceed safely — usually a contradiction or an unanswered question in the _frozen spec_), and the orchestrator paused the whole run for a human. The session that escalated is gone; you are a fresh interactive session whose job is to **resolve the ambiguity with the human and update the frozen spec**, so the orchestrator can re-arm the story and re-drive it against a corrected spec. This is **interactive**: a human IS present. Ask questions, present options, recommend — but the human makes the call. (`$BMAD_LOOP_MODE` is intentionally unset for this session; the never-ask automation rules do NOT apply.) ## Identity & I/O contract These environment variables are set: - `$BMAD_LOOP_RUN_DIR` — the paused run's directory. - `$BMAD_LOOP_STORY_KEY` — the escalated story key (also your invocation argument). - `$BMAD_LOOP_RESOLVE_CONTEXT` — path to a `context.json` written for you. **Read `$BMAD_LOOP_RESOLVE_CONTEXT` FIRST.** Its schema: ```json { "story_key": "6-4-cli-list-command", "run_id": "20260613-111429-6a14", "spec