Repository navigation
Preserve maintenance confirmation and report exact failure stages - #4
Merged
Merged
Conversation
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
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.
Maintenance confirmation currently loses the reason for a changed plan and collapses failed applications into two booleans. Preserve server expiry, identify changed plan components and distinguish provider, child execution and independent readback, with conservative mutation evidence for legacy results. Normalize one trailing root slash.
Validation: 3,170 tests; lint, typecheck, build, fixture acceptance and MRN QA passed. Two fresh MCP processes exposed the same 67 schemas and refused missing receipts, implicit major updates and core. No credential, allowlist or production change. Existing backup, exact-version, approval and rollback gates remain.