id-importlisted

# id-import — read-only live-env → IaC import craft (infra-delivery step 2, ★ entry mode) The `infra-delivery` step sequence (a documented procedure this skill family forms — no workflow engine or state-machine file ships) drives an infra change → merge. Step 2 has four **entry modes**, one per starting condition. `id-import` is the entry mode for **"infra already exists in the cloud, but there is no IaC"** — the ★ thin-slice front door (the operator's staging-import test). The procedure the generic agent **runs**: survey the live environment **read-only**, codify it into OpenTofu/Kubernetes IaC, and prove the codification is faithful by the **acceptance seam `tofu plan == ∅`** — an empty plan means the IaC equals reality (which doubles as the forever drift check). It produces an **IaC skeleton** + a **`.foundry/`-partitioned import step-report note** (empty-plan ⇒ import complete). It **NEVER applies** — import is discover-and-codify, proven by the empty diff. ## ADVISORY — not a gate This skill is **ADVISORY**. It **produces an IaC skeleton + an import step-report note**; it does **NOT gate, approve, or block** any merge. The both-modes floor is unchanged: front-authorization, **the merge floor** (the adopter's branch protection + CI checks — see `docs/merge-floor.md`) **remains the merge authority**, security review, and typed contracts. Running `id-import` makes the infra change start from a faithful codification of reality — it is craft guidance **FOR** the trusted op