id-baselinelisted

# id-baseline — read-only adopt-existing-IaC 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-baseline` is the entry mode for **"an IaC repo already exists"** — the operator points at an existing OpenTofu/Terraform repo and **adopts** it. Unlike `id-import` (greenfield — codify live infra that has NO IaC), `id-baseline` **adopts** an existing repo and **validates it is drift-free** against the live environment. The procedure the generic agent **runs**: point at the existing IaC root, resolve the active stack profile, run the **acceptance seam `infra_binding.plan` read-only** and require the plan **empty**, then produce the **drift-free / drift REPORT** and record the observation. The acceptance seam is **`tofu plan == ∅`** — an empty plan means the IaC equals reality (the adoption is clean, which doubles as the forever drift check). It **NEVER applies** and **NEVER auto-reconciles** — adoption is read-only validation, proven by the empty diff; **drift is surfaced, never fixed**. ## ADVISORY — not a gate, no machine-adjudicated GREEN verdict This skill is **ADVISORY**. It produces a **baseline/drift report + a `.foundry/`-partitioned drift step-report note**; it does **NOT gate, approve, or block** any merge. **Crucially, adoption VALIDATES — it is not