Rule version history in the New Kibana Alerting Experience

**What the feature is (as Title)**
Rule version history

**Value proposition**

When an alert starts behaving differently, teams need to know whether the rule changed, not just that it fired. Today, rule edits are easy to make but hard to track: there is often no clear record of who changed what, when, or why. That slows incident review, makes rollback guesswork, and weakens accountability when a misconfiguration causes noise or missed pages. Rule version history gives users a saved timeline of those changes so they can see what a rule looked like at a specific point in time and who made each update.

**Expected outcome**
Rule version history lets users review previously saved rule modifications and see who made which changes at a specific moment. Investigators can compare versions during triage, admins can trace unexpected behaviour back to a config change, and teams can iterate on rules with more confidence knowing prior states are preserved and reviewable.