id-plan

/foundry:id-plan — the read-only PRE-MERGE seam (plan/diff → review artifact + step-report note)

The infra-delivery step sequence (a documented procedure this skill family forms — no workflow engine or state-machine file ships) drives an IaC change spec → merge. Step 8 is the PRE-MERGE seam: before an infrastructure change is merged, prove read-only that the change does what its spec says and nothing else — that the codified IaC, refreshed against the real environment, matches reality with no unexpected add/change/destroy/replace and a clean policy pass. Infrastructure has no app to boot, so the app live-seam (boot → exercise a surface → assert no new 5xx) has no analog here. id-plan is the disciplined procedure the generic agent runs instead: it resolves the active profile, drives the profile's infra_binding.plan command strings read-only against the real environment, collects the structured plan/diff, and turns it into the review artifact (the hand-off the human / id-review / the merge floor reads) plus a .foundry/-partitioned plan STEP-REPORT NOTE. The infra live-seam's dedicated walk-evidence recorder + verdict machinery this skill used to compose with was retired (see docs/DESIGN.md) — there is no live consumer that adjudicates this note into a PASS/FAIL today; it is advisory input for the human review at the merge floor.

When to trigger

• The infra-delivery sequence advances to the pre-merge seam (step 8), after an IaC change is written and before it is merged.
• The operator says "/foundry:id-plan", "run the pre-merge plan seam", or "plan this infra change read-only".

ADVISORY — this skill advises the trusted operator; it is NOT a gate, and it does NOT self-certify

This skill is an ADVISORY craft procedure + mechanical mistake-catcher FOR the trusted operator. It produces the review artifact + records a plan STEP-REPORT NOTE; it is NOT a gate and NOT the merge authority, and it does NOT decide its own PASS. Honest disclosure: earlier design intent had the FROZEN acceptance-contract compute a PASS via derive_walk_verdict (and the per-surface derive_infra_walk_verdict) at a dedicated live-seam blocking merge gate — that verdict machinery, and the gate that consumed it, were retired (docs/DESIGN.md) and do not exist in scripts/ today. id-plan records observations; it does not adjudicate them, and nothing currently machine-adjudicates them either — the merge floor (the adopter's branch protection + CI checks — see docs/merge-floor.md) is the merge authority, and this note is advisory input for the operator/reviewer at that floor. It catches the forgotten refresh, the unexamined destroy in the plan, the policy fail waved through, the plan run against the wrong profile a busy operator would miss. The trusted operator may override or short-circuit it at will; that is in-model, not an attack to defend against. Skipping it only forfeits the seam's benefit.