Repository navigation
Honor initialization execution budget - #647
Merged
Merged
Conversation
SaladDay
force-pushed
the
honor-initialization-execution-budget
branch
from
October 10, 2026 16:39
ccae2b7 to
e45241d
Compare
SaladDay
force-pushed
the
honor-initialization-execution-budget
branch
from
October 10, 2026 17:00
e45241d to
5718fc1
Compare
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.
Package installation and setup were canceled after two minutes because transport staging timers also bounded execution. Core now carries its remaining thirty-minute initialization budget in the Runtime preparation protocol; two minutes bounds staging, while apply uses the remaining operation budget. The five-minute input admission deadline is unchanged.
The mandatory field advances the Core–Runtime protocol to 0.15.0; both peers must use this revision. Unknown side effects remain unconfirmed and are never replayed.
Validation: independent full-diff review without findings; protocol, gateway, dispatch and initialization tests; runtime contract gate; Core/daemon build and vet; targeted race checks; real database initialization/restart tests; bilingual documentation checks. Exact npm/Python/native-extension/Skill/MCP cold-continuation acceptance runs on the combined candidate before this draft is completed.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.