amend-blueprintlisted

Amend a **locked** blueprint after a build-time discovery. Load `method-rules` and the `method-rules-gate-contracts-bp` skill (BP's contract satellite); read `state.json`. This exists because a mid-build discovery is **not drift**: nothing built departs from recorded truth — the *spec* is defective or silent, still inside MVP scope, and the correction must land where a build session will actually read it. Reconcile's machinery (source observations, claim registry, baselines) answers a different question; its output is not in the build read order. Idea slug = $0, discovery = $1 (ask if missing — the observation, not the proposed fix). ## Preconditions 1. `state.blueprint.status` is `locked`. If not, this is ordinary stage-6 drafting — say so, point at the `stage-6-blueprint` skill, and return. 2. The discovery is stated as an **observation** (failing test name, provider error payload, quoted third-party doc + URL). Method-rules §1 applies verbatim: no narrated cause you did not check; `[UNVERIFIED CAUSE]` otherwise. ## The scope test — the routing gate (founder-answered; `auto_continue` NEVER covers it) Propose an answer with reasoning, then ask the founder (AskUserQuestion; prose fallback when it is unavailable — the checkpoint may not degrade): > Does this change any of: a core-loop step · the cut-list boundary (adds or removes user-visible > capability) · an MSP commitment · a DoD item · the aha event · price/payer · any outward promise? - **YES → this is no