id-impactlisted

# id-impact — two advisory pre-merge reads (policy-risk findings + the KEPT blast-radius tier hint) > **v2 amendment (additive).** `id-impact` now gives the operator **two advisory pre-merge reads** of a > change, BEFORE authorize: **(1)** the **policy-risk findings** (the REAL change-risk) — surface > `foundry_plan_model.parse_policy_findings` output and distinguish, per the corrected gating table, which > findings are HARD-FAIL-shaped (no ack path) vs. ackable-shaped vs. advisory; and **(2)** the > **KEPT v1 `blast_radius` fast tier hint** (the pre-policy heuristic, untouched, below). It is **advisory > + read-only** — `id-impact` reads the real `parse_policy_findings` output directly (no second > computation, no divergent re-implementation). > > **Honest disclosure — no live enforcer.** Earlier design intent named a `feat-foundry-infra-change-verdict` > component that would mechanically ENFORCE this gating table at merge time. **That verdict-enforcement > machinery does not exist in `scripts/`** — it was part of the bespoke merge-gate stack retired in the > **earlier realignment** (see `docs/DESIGN.md`, `docs/merge-floor.md`). Today `id-impact`'s > two reads are **surfaced for the operator/reviewer to weigh at the merge floor** (the adopter's branch > protection + CI checks + human review) — nothing currently blocks a merge on a `deny` finding or an > un-acked HIGH finding automatically. Wiring that as a required CI check is the adopter's own > policy-as-code job, per `do