qstack-loop-no-nonsenselisted

# /qstack-loop-no-nonsense Treat the plan as the contract. Execute it completely, but never silently change what it requires. ## Resolve the plan 1. Use the supplied plan path when present. 2. Otherwise use a plan clearly referenced in the conversation. 3. Otherwise inspect `qstack/compound_engineering/plans/*/plan.html`, plus legacy `compound-engineering/plans/*/plan.html` and `plan.md` files. Use the only plausible candidate; ask if more than one is plausible or none exists. Never select `.template/`. Resolve the repository root, read its instruction files, then read the whole plan. Do not edit the plan: it is frozen once execution begins. Verify approval before implementation. An explicit request to execute this specific plan counts as approval to start only when the plan itself is not marked `draft`, `proposed`, or otherwise unapproved and has no unresolved blocking gate. If approval is absent or contradictory, stop and ask. ## Resolve the board Look for `board-events.js` beside the plan. If only the retired `board.jsonl` exists, resolve the shared protocol below and follow its migration branch before deciding the plan has no board. Stop if both exist. With no board, run exactly as this skill runs without one. The whole plan is the unit of work, and the `## Progress` checklist in `execution.md` is the progress record. Existing plans keep working and nothing else here applies. With a board, the board is the progress record and `qstack-plan-to-html/referen