Prove application-owned thread session lifetime - #1131
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
Contributor
Contributor
Contributor
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.
Applications need to change conversations without mixing old execution, history or tool settlement into the new thread. This PR demonstrates selecting application-owned, fixed-thread sessions in both native bindings: selection starts empty, history is explicitly loaded, and the example disposes the outgoing session. Separate binding tests demonstrate retaining it instead.
The new
/?threadsinstalled-consumer view covers same-thread selection, returning to a fresh session, switching during a running stream or pending history request, and permanent owner disposal. React observes the selected session; Angular recreates a keyed observation scope. Runtime regressions cover late history, concurrent sessions, thread-scoped tool claims and late durable settlement under a retired thread. No production runtime, core or binding API changes are needed.Validation:
Source fingerprints, actual installed package hashes, command logs and browser proof are recorded in
fixtures/react-parity/runtime/evidence.json. Contributor guidance explains the lifetime policy and manual review sequence.Scope and review: thread creation/list CRUD, actual URL routing integration, checkpoint execution, public backend cutover and native component parity remain later work. Disposal cancels local ownership, not remote execution or side effects. Parent spec/source/lifecycle/type/evidence audits completed; independent agent capacity is exhausted in this thread. A hosted review job is counted as review only if it produces substantive output.
Main integration includes #1129's website split (20 workspace checks passed) and the later #1130/#1135 Resend fixes (focused growth webhook Nx checks passed). The recorded 813-file runtime fingerprint remains unchanged on current head
0a5bb0979.Hosted review jobs, including workflow 35807392284 on
0a5bb0979, returnedis_error: truedespite successful job conclusions. They produced no substantive review and are not counted as independent review evidence.