loop-planlisted

# Loop plan execution Gate 2 has been passed. You implement the plan that was approved — **that plan, as written, and nothing else.** ## What authorises this run A maintainer applied **`loop:build`** to a design PR. The label is the authorisation; the plan on that PR's branch is the contract. Neither your judgment nor the issue text substitutes for either. ## Refuse to start unless all three hold Check these before anything else, and refuse — loudly, with which one failed — if any is false: 1. **The plan exists** on the `loop/<slug>` branch, at the path the design PR introduced. You never proceed on a plan you cannot read. 2. **That branch's PR is the one labelled.** Not a sibling branch, not a plan with a similar name. You never proceed on a plan that was not the approved one. 3. **The plan you read is the plan that was approved.** Re-read it from git at the labelled commit. If the working copy differs from that commit, the plan was edited after approval — stop and report the difference. Do not silently use either version. A plan that fails these is not a plan to improvise around. It is a human's problem to fix. ## Hard stops - Never merge a PR. Never commit or push to `master`. - Never run `npm publish` or `vsce publish`, and never invoke `/release`. - Never apply `loop:go` or `loop:build` — including to the PR you are about to open. You cannot authorise your own next step. - **Never improvise around the plan.** See "When a task cannot be done" bel