Unify action evidence, recovery checks, readiness and incident eval drafts - #135
Merged
Merged
Conversation
alimobrem
marked this pull request as ready for review
October 3, 2026 19:32
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Successful tool calls, denied/no-op fixes and missing resources could be confused with verified recovery, while monitor and durable execution paths could attach the wrong snapshot or lose their action outcome. This change binds snapshots, controller identity, mutation preconditions and recovery evidence to the actual action. Explicit execution completion is persisted separately from verified, failed, recurring or unverifiable recovery; existing Temporal histories retain compatible behavior.
It also adds scoped authenticated installation readiness and its analytics summary, review-only incident evaluation drafts that cannot masquerade as recorded fixtures, mandatory safety/recovery acceptance, and current operational docs and GitHub Pages. Provider connectivity remains explicitly unknown until separately tested.
Validation on7cdf3d6: CI run37128873842 attempt2 passed3614 tests, lint, formatting, types, discipline, live replay regression and simulation gates. The exact rerun artifact11276657748 reports mandatory acceptance passed with no errors; crashloop recovery is verified after mutation with no policy/confirmation violations. Live replay had36/49 fixture passes against a28-pass baseline and no suspected regressions; a green regression gate does not mean all fixtures passed. The causally inconsistent benchmark fixture was corrected in PulseSRE/sre-bench#1, resolved commitd0868298a0efa4998b9c968d63188a758e1aa92b.
An isolated wheel build passed, including required package data. Real-cluster installation, two-cluster isolation and the three deployed incident flows remain unverified pending infrastructure. No local product runtime, deployment or release was performed. Includes and supersedes PR134.