id-simulatelisted

# id-simulate — OFFLINE local-simulation craft (infra-delivery step, between `id-test` and `id-plan`) 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. The **`simulate`** step runs **after** `id-test` (the Layer-0 policy/contract test) and **before** `id-plan` (the read-only pre-merge plan/diff seam). It is the **offline local-simulation** layer: a PROCEDURE skill the generic agent runs **entirely offline — with no live cloud and no credentials** — to **author-and-prove the whole IaC corpus before the live pre-merge plan**. The Layer-0 steps (`id-validate` fmt/lint/render + `id-test` policy/contract tests) prove the change *validates* and *renders / policy-passes*; they **cannot** prove the primitive modules *apply* or that the GitOps structure *reconciles*. `id-simulate` closes that gap with the two offline layers — short of live cloud, the highest-value signal an adopter can get — by driving the profile's **existing** IaC against local simulators. It needs **no new `infra_binding` slot** (it drives the profile's already-named modules + `gitops_paths` tree offline). ## OFFLINE — no live cloud, no credentials (the load-bearing safety invariant) This step is **OFFLINE**. Every Layer-1 `apply` is against the **LocalStack endpoint** (`--endpoint-url` / a `tflocal` provider override + a `backend "local"` state) — it `apply`s the primitive modules to a *simulator*