What problem does it solve? Renames and removals of committed identifiers — alert names, Terraform variables, dashboard names, recording rules — silently break customer routing, plans, and links, and they slip through review because a rename reads as an edit rather than a removal. ## Core Features & Use Cases - Committed-surface detection: Flags renames and removals across alerts, recording rules, Terraform variables/outputs, dashboard identities, and metric tier keys that owe a 30-day deprecation cycle. - False-positive guardrails: Lists what is not a breakage — additions, query id changes, expression changes, dashboard internals — so the deprecation policy is not over-applied. - Alternative-first feedback: Suggests designs that avoid the cycle entirely, such as minting recording rules, keeping old identifiers working, or carrying severity in labels instead of names. - Use Case: While reviewing a PR that renames an alert from mz-mon-env-top to mz-mon-environment-overview, the reviewer catches the delete-plus-add pattern and asks for a **Deprecated:** bullet in the PR description with both names working for 30 days. ## Quick Start Review this pull request diff and flag any renames or removals on the customer-facing surface that owe a deprecation cycle.
