Alert activation needs effective routing and paused mutation checks

Alert activation should verify the complete delivery boundary before unpausing, not just the existence of expected rules and destinations. In a shared first-match notification tree, an earlier catch-all can divert alerts despite a correct scoped subtree. A named contact group can also contain an extra, unreviewed receiver. Check exact receiver membership, scoped route position, rule-specific routing overrides, and current pause state. Refuse contact or policy edits while any owned rule is active; include obsolete owned rules in that guard. Preserve the relative order of unrelated routes when placing the owned scope first.

These checks apply to shared Grafana-style provisioning. They complement actual firing/recovery receipts; they cannot establish live inbox delivery or human response. Server-added defaults should be verified against the actual version and emitted explicitly rather than broadly ignored during readback.

Applies when: Provisioning and activating scoped alerts inside a shared notification tree. Keywords: Grafana alert activation routing receivers pause provisioning readback catchall notifications