Allow bounded stop-start MCP rollout on the 1 GiB host - #43
Merged
Merged
Conversation
This was referenced Sep 25, 2026
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
1 participant
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.
The 1 GiB MCP host cannot keep the existing and candidate runtimes in memory together. The current overlap rollout therefore rejects the already published v8std cursor image before the first public page can be checked.
This adds an exact-target, expiring stop-start deployment mode. The controller verifies and pulls the candidate while the predecessor is live, stops the predecessor, checks real free memory, then starts and checks the candidate. It keeps a separate rollback budget and does not commit until the second public check, active pointer update, and resume succeed. Crashes and late failures restore the predecessor; normal overlap deployment remains the default. CI uses a bounded 900-second envelope only when the stop-start switch is set.
Validation: 176 release/publication tests passed before the final fault cases; 57 focused transaction/transport tests passed; late second-smoke and post-pointer resume failures passed separately; strict Zensical build and actionlint passed. The exact candidate will also pass GitHub validation before deployment. No RAM increase is required.