id-discoverlisted

# id-discover — read-only everyday-change survey 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-discover` is the **everyday-change default** — the entry mode for **"a baseline already exists and you're making a routine change."** Unlike the three onboarding modes that *establish* a baseline — `id-import` (greenfield — codify live infra that has NO IaC), `id-baseline` (adopt an existing IaC repo + validate it drift-free), `id-architect` (forward-design a topology) — `id-discover` **assumes** a baseline and **surveys the change**: a **read-only inventory** of the target infra (the relevant IaC roots, the in-scope live resources) plus the **change surface** the intended change touches, so the downstream spine (id-implement → id-validate → id-plan → id-impact) starts idiom-faithful and correctly scoped. It is the infra analog of the `sd-discover` brownfield survey — same role at the same SDLC position (survey BEFORE implement) over infra instead of an application codebase. It **NEVER mutates** — discovery is read-only inventory; it does not `apply`, scaffold, or reconcile. ## ADVISORY — not a gate, no machine-adjudicated GREEN verdict This skill is **ADVISORY**. It produces a **change-scope report + a `.foundry/`-partitioned survey step-report note**; it