Produce an Impact Manifest (a machine-readable change-safety assertion) from a Terraform plan, using blastcheck.

plan_path may point at terraform show -json output or at a saved .tfplan file (converted automatically). The analysis is offline and plan-only: nothing is sent anywhere, no cloud credentials are used, and a plan-only manifest can never claim safe - it says what it verified and what it could not.

Returns a manifest_handle (pass it to impact_explain) plus a short summary. The full manifest is written to a private temp file rather than returned inline, because it is large.

Explain an Impact Manifest in plain language.

Provide exactly one of: manifest_handle (from impact_emit), manifest_path (a manifest JSON file on disk), or manifest (the document inline). Returns markdown covering the verdict and why, each change's noteworthy findings, a "safe if ..." checklist of unmet preconditions, and what could not be verified.

Output is capped by a hard budget (BLASTCHECK_MCP_EXPLAIN_BUDGET env, default 32000 characters). Large plans get a compact grouped view with an explicit partial-view notice - never a silent cut. Drill down with the optional filters, which combine with AND: severity (e.g. ["blocking"]), module_prefix (address prefix), resource_type (exact, e.g. "azurerm_managed_disk"), and addresses (exact addresses, always rendered in full detail - the guaranteed path to any specific change). All lists are lexically sorted before any cut, so the same plan always shows the same subset.

Purely local and deterministic; nothing is sent anywhere.