Conversation
meta-d
approved these changes
Jul 12, 2026
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.
Summary
Why
Drawing review evidence previously relied on external PDF tabs or coarse normalized coordinates, so evidence markers could not be rendered or resumed reliably in the host. Remote component navigation also depended on string-only commands and could fall back to legacy conversation pages. Background assistant execution needed stable conversation/execution state and context propagation so created records remain in the correct user scope and ChatKit streams can be resumed.
Impact
Validation
corepack pnpm exec tsc -p apps/cloud/tsconfig.app.json --noEmitcorepack pnpm nx build plugin-sdkgit diff --check