Repository navigation
fix(tools): persist idle promotion prune after fold - #1241
Merged
Merged
Conversation
Fold already drops execute-promoted schemas off the wire. Persist that empty set to run.json and the crash handle so resume cannot restore them.
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.
Summary
run.jsonthe same way execute-promote persist does (TUIpersistRunSnapshot/syncRunStateHandle, execpersist), so a crash or resume cannot re-flush pruned MCP schemas.docs/MCP.mddescribes promote-on-execute only;tool_searchdoes not join the next infer orrun.json.Verification
bun run checkpasses (lint, typecheck, dead-exports, build, 7846 tests)