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.
Issue #240 exposed a remaining host-coupling bug: the live DevSpace catalog can add the owner orphan-PROCESS recovery tool while an already-open ChatGPT conversation keeps its older callable projection. That made a critical continuation path depend on the host hot-adding a new top-level tool.
This keeps the existing
core_mutation_session_rebindschema stable and lets that already-projected surface consume a strict owner-recovery evidence envelope only when the bound session isPROCESS / OUTCOME_UNKNOWN. The exact configured OAuth owner is still required, physical snapshot/scope/deletion evidence is verified by the existing Core recovery path, and only after the PROCESS pin is cleared does the normal atomic caller handoff run. Ordinary rebind behavior is unchanged and foreign owner clients remain fail-closed.Verification on the exact patch: new positive/hostile recovery cases 3/3 PASS; caller-rebind suite 8/8 PASS; typecheck PASS; production build PASS;
git diff --checkPASS; fullserver.test.ts87/88 with the sole failure the pre-existing Issue #194 G2ECONNRESETtransport test. Core Candidatea363e2970320625daf481ad5670f4a255ee6b9bb, tree2bc511a88ff9dbb47bda58df65dd0597f062fea4, diff hashsha256:15feaf08d18493d3ada5dd476e4639765d2bbff65546a594c2608527eb1dfc63.