id-rollbacklisted

# id-rollback — the incident safe-revert procedure (git revert → reconcile → verify-landed) The `infra-delivery` step sequence (a documented procedure this skill family forms — no workflow engine or state-machine file ships)'s **incident path**. When a delivered change did **NOT land** — a **NOT-LANDED** realization (the `derive_realization_verdict` consequence), an escaped defect, bad config — the operator runs this **safe-revert PROCEDURE** to restore the last-known-good IaC and **prove reality matches it again**. The shape is **`git revert` → reconcile → verify-landed**: revert the offending commit (restoring the prior **authorized** IaC via the governed `/foundry:revert`), drive the GitOps controller's **idempotent** reconcile toward the **reverted IaC**, then run the **realization read** through the **post-deploy realization frame** — ArgoCD **Synced ∧ Healthy** + post-revert **`tofu plan == ∅` against the reverted IaC** ⇒ the revert **LANDED** (the incident is closed); a residual OutOfSync / non-empty plan ⇒ **NOT-LANDED** (the revert itself did not realize — escalate). It is a PROCEDURE skill the generic agent runs. ## ADVISORY — observe-and-record, the floor re-derives, the skill self-certifies nothing This skill is **ADVISORY**. The post-deploy **realization frame** is an **observe-and-record** path (the `id-sync`/`id-verify` discipline): `id-rollback` **records** the post-revert realization observation; the **realization gate** (`derive_realization_verdict` — a r