Repository navigation
Allow bounded native maintenance inspection to finish - #3
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.
Company maintenance preflight completes native package inspection in about 50 seconds, exceeding the MCP's ordinary 30-second HTTP deadline. The local client now gives the three closed maintenance phases bounded timeout floors of 90 seconds for preflight, 180 seconds for execution and 90 seconds for independent readback. Longer configured budgets are retained; unrelated requests keep their configured deadline.
Authentication, response limits, external cancellation, backup receipts, exact versions, plan expiry, human confirmation and unknown-outcome handling remain unchanged. No write retries or stock/core fallback are added. The maintenance documentation now distinguishes the separately deployed provider/guard from local fixture qualification and per-site adoption.
Validation: 3,153 tests passed, including transport deadline/cancellation fixtures; 39 packed fixture acceptance scenarios passed (six environment/write scenarios intentionally excluded); lint, typecheck, formatting, build, version/plugin/skill checks, scoped MRN QA and exact staged-tree MRN QA passed. An initial unrestricted parallel test run hit one pre-existing npm-pack harness's 5-second limit; the complete suite passed with two workers. An additional all-source QA scan flagged existing upstream synthetic credential fixtures and CLI logging; changed-source and staged scans passed. WordPress/browser/a11y/performance rows are inapplicable to this local Node transport patch and were not claimed as runtime coverage.
A fresh source-build process connected to wpcontrol.mrndev.io, preserved the exact 69-tool allowlist, and refused missing receipts, unapproved majors and core. No maintenance update was executed. Local pin replacement and an authorized company preview will be verified separately after merge.