test(runtime): verify installed checkpoint ownership - #1157
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
blove
enabled auto-merge (squash)
September 24, 2026 18:25
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This branch was successfully deployed
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.
Installed consumers previously exercised thread selection and run recovery without proving that checkpoint selection stays separate from execution authority. Add a fixture-only
/?checkpointsworkflow for native React and Angular: fork completed A, continue and reload A2 while B is selected, reject pending P, reconnect the same interrupted run into A3, and reject commands after disposal.The installed factory exposes a narrow, readonly checkpoint signature. An independent HTTP oracle checks the complete 15-request sequence and exact checkpoint/run routing. A deliberate mutation routing continuation back to original A fails the browser test; the production source was restored. Production runtime, native binding implementations and public package exports are unchanged.
Validation:
The fixture record adds scoped evidence while preserving historical records. The whole-workspace emitted-boundary scan in this worktree was not completed because an unchanged AG-UI build artifact was absent; both exercised installed consumer declaration boundaries passed. This proves the private runtime through installed bindings, not a neutral published backend, live-deployment compatibility, SSR or production component parity. No release or dependency changes.