fix: stabilize core recovery tool projection - #293
Merged
James3014 merged 1 commit intoSep 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
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.
Keep the owner-only orphan PROCESS recovery tool in the MCP catalog regardless of deployment-time owner configuration, while preserving fail-closed authorization at invocation time. This prevents ChatGPT from getting stuck on a stale tool projection when owner recovery is enabled after the initial catalog was projected.
Verification on latest main (including #291): target regression 1/1 PASS; caller-rebind suite 8/8 PASS; typecheck PASS; build PASS; git diff --check PASS.
Issue #240 remains open until the merged build is deployed to the M5 DevSpace service and the preserved historical orphan session completes the live recovery → caller rebind → real Candidate provenance E2E.