feat(runtime): preserve owned citation metadata - #1158
Merged
Merged
Conversation
# Conflicts: # fixtures/react-parity/runtime/README.md # fixtures/react-parity/runtime/evidence.json
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
blove
enabled auto-merge (squash)
September 24, 2026 18:45
Contributor
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.
The staged shared runtime dropped LangGraph citation metadata before either native binding could observe it. Messages now expose readonly, owned citation data with source alias normalization, explicit empty-list replacement, canonical clearing, and generation isolation. Equal metadata reuses its existing references, including when answer text changes.
The private adapter keeps citation projection separate from execution authority. Exact checkpoint ownership, tool admission, the legacy Angular adapter and public package roots are unchanged. Installed React and Angular fixtures read the real snapshot and cover history retention/clearing and resumed approval completion.
Verification:
This is staged message-data support. Rich content, reasoning/timing, citation UI and public backend cutover remain separate. Plain checkpoint ingress still rejects unsupported instances/cycles. No release or dependency change.