Repository navigation
Recover original maintenance previews without resending work - #7
Merged
mrnwebdesigns merged 1 commit intoOct 26, 2026
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.
A successful Dashboard maintenance preflight can take longer than the existing 90-second HTTP budget. With the matching four-helper provider contract, recover the original attempt through bounded read-only polling after a timeout; never resend preparation or retry an uncertain execute. Confirmation uses a fresh attempt and preserves the existing plan, receipt, approval and independent-readback checks.
No extra public MCP tools, longer per-request timeout, stock update fallback, credential changes or settings-policy changes. Partial or blocked helper contracts fail closed. GET recovery carries only site identity, attempt UUID and input digest.
Validation: 104 focused maintenance tests, all 3,197 tests across 44 files, typecheck, focused ESLint, formatting, build, MRN source QA and exact staged gate passed. The fixture reproduces the observed 157.274-second preparation with a lost 90-second response and verifies no resend or write retry. Production provider deployment and fresh configured-process verification are still required.