chore(deps): bump the npm-minor-and-patch group across 1 directory with 12 updates

[dependabot]

Bumps the npm-minor-and-patch group with 12 updates in the / directory:

Package	From	To
@assistant-ui/core	0.2.22	0.3.15
@assistant-ui/react	0.14.27	0.15.16
@assistant-ui/store	0.2.21	0.3.10
monaco-editor	0.52.2	0.56.0
@anthropic-ai/sandbox-runtime	0.0.71	0.0.73
@daytona/sdk	0.204.1	0.207.0
@hono/swagger-ui	0.2.2	0.6.1
@nats-io/nats-core	3.0.2	3.4.0
@openuidev/react-headless	0.9.4	0.9.12
@openuidev/react-lang	0.2.9	0.2.15
@openuidev/react-ui	0.13.3	0.13.9
lucide-react	0.562.0	0.577.0

Updates @assistant-ui/core from 0.2.22 to 0.3.15

Release notes

Sourced from @​assistant-ui/core's releases.

@​assistant-ui/core@​0.3.15

Patch Changes

• #6100fa30915 - fix: propagate AssistantFrame tool cancellation across the frame boundary (@​Kinfe123)

• #5823b355aef - fix: prevent AssistantFrameProvider from ignoring a later explicit targetOrigin (@​Kinfe123)

• #6136f7bd2d9 - fix: keep DevTools updates flowing when a subscriber throws (@​Kinfe123)

• #61074947ef4 - fix: preserve falsy assistant transport artifacts (@​Kinfe123)

• #5809332f736 - fix: load archived threads in the cloud thread list adapter (@​SnowingFox)

• #6112ef9254d - fix: contain a synchronously throwing clipboard writer in useActionBarCopy (@​samdickson22)

• #61569c65b51 - deprecate leftover Primitive.If and Empty wrappers on react-native and react-ink, and point them at AuiIf (@​okisdev)

  ThreadIf now reads thread.isEmpty instead of messages.length === 0, matching the loading-aware field already used by ThreadEmpty and AuiIf. First-party examples and docs samples that still called the leftover wrappers now use AuiIf directly.

• #61065845ba7 - fix: ExternalThread no longer reports an empty thread while it is loading (@​samdickson22)

  ExternalThread computed thread.isEmpty as messages.length === 0, omitting the isLoading term that thread-runtime-client.ts already applies. A thread with isLoading: true and no messages yet reported isEmpty: true, so <ThreadPrimitive.Empty>, useThreadIsEmpty(), and AuiIf on s.thread.isEmpty rendered their empty state underneath the loading indicator. The ThreadState type already documents the intended contract: a thread is empty when it has no messages and is not loading.

  Both producers now define isEmpty identically. Consumers that pass isLoading to ExternalThread and render empty-state UI will see that UI stay hidden until loading finishes. useExternalStoreRuntime is unaffected — it already carried the isLoading term.

• #61251b30bfd - refactor: collapse the two inert thread cores onto a shared base (@​okisdev)

• #6159365e763 - fix: avoid ancestor scans when importing new messages (@​rupic-app)

• #6135d19921d - fix: prevent cancelled external-store runs from resyncing after teardown (@​Kinfe123)

• #6080996aa57 - fix: reset remote thread selection and cached records when the thread-list adapter is replaced (@​okisdev)

• #617721d6e87 - fix: notify thread subscribers when a remote thread core is republished (@​Yonom)

• #6092cd247e5 - fix: traverse long message branches without recursive stack growth (@​Kinfe123)

• #61421bf263b - fix: settle aborted and superseded local runs without continuing them, while keeping approval pauses answerable after cancel (@​Kinfe123)

• #612406b04a7 - chore: update dependencies (@​okisdev)

... (truncated)

Changelog

Sourced from @​assistant-ui/core's changelog.

0.3.15

Patch Changes

• #6100fa30915 - fix: propagate AssistantFrame tool cancellation across the frame boundary (@​Kinfe123)

• #5823b355aef - fix: prevent AssistantFrameProvider from ignoring a later explicit targetOrigin (@​Kinfe123)

• #6136f7bd2d9 - fix: keep DevTools updates flowing when a subscriber throws (@​Kinfe123)

• #61074947ef4 - fix: preserve falsy assistant transport artifacts (@​Kinfe123)

• #5809332f736 - fix: load archived threads in the cloud thread list adapter (@​SnowingFox)

• #6112ef9254d - fix: contain a synchronously throwing clipboard writer in useActionBarCopy (@​samdickson22)

• #61569c65b51 - deprecate leftover Primitive.If and Empty wrappers on react-native and react-ink, and point them at AuiIf (@​okisdev)

  ThreadIf now reads thread.isEmpty instead of messages.length === 0, matching the loading-aware field already used by ThreadEmpty and AuiIf. First-party examples and docs samples that still called the leftover wrappers now use AuiIf directly.

• #61065845ba7 - fix: ExternalThread no longer reports an empty thread while it is loading (@​samdickson22)

  ExternalThread computed thread.isEmpty as messages.length === 0, omitting the isLoading term that thread-runtime-client.ts already applies. A thread with isLoading: true and no messages yet reported isEmpty: true, so <ThreadPrimitive.Empty>, useThreadIsEmpty(), and AuiIf on s.thread.isEmpty rendered their empty state underneath the loading indicator. The ThreadState type already documents the intended contract: a thread is empty when it has no messages and is not loading.

  Both producers now define isEmpty identically. Consumers that pass isLoading to ExternalThread and render empty-state UI will see that UI stay hidden until loading finishes. useExternalStoreRuntime is unaffected — it already carried the isLoading term.

• #61251b30bfd - refactor: collapse the two inert thread cores onto a shared base (@​okisdev)

• #6159365e763 - fix: avoid ancestor scans when importing new messages (@​rupic-app)

• #6135d19921d - fix: prevent cancelled external-store runs from resyncing after teardown (@​Kinfe123)

• #6080996aa57 - fix: reset remote thread selection and cached records when the thread-list adapter is replaced (@​okisdev)

• #617721d6e87 - fix: notify thread subscribers when a remote thread core is republished (@​Yonom)

• #6092cd247e5 - fix: traverse long message branches without recursive stack growth (@​Kinfe123)

• #61421bf263b - fix: settle aborted and superseded local runs without continuing them, while keeping approval pauses answerable after cancel (@​Kinfe123)

• #612406b04a7 - chore: update dependencies (@​okisdev)

... (truncated)

Commits

• 75e3ef7 chore: update versions (#6086)
• 21d6e87 fix(core): notify thread subscribers when a remote thread core is republished...
• 92e52bd fix(core): widen tool-call status reasons (#6165) (#6168)
• d19921d fix(core): suppress stale cancellation resyncs (#6135)
• f7bd2d9 fix(react): isolate devtools subscribers (#6136)
• 1bf263b fix(core): stop superseded local runs before tool continuation (#6142)
• 365e763 fix(core): avoid quadratic import checks (#6157) (#6159)
• cd247e5 fix(core): traverse long message branches iteratively (#6092)
• 9c65b51 fix(react-native,react-ink): honor thread.isEmpty in leftover ThreadIf (#6156)
• 5845ba7 fix(core): ExternalThread no longer reports an empty thread while loading (#6...
• Additional commits viewable in compare view

Updates @assistant-ui/react from 0.14.27 to 0.15.16

Release notes

Sourced from @​assistant-ui/react's releases.

@​assistant-ui/react@​0.15.16

Patch Changes

• #6136f7bd2d9 - fix: keep DevTools updates flowing when a subscriber throws (@​Kinfe123)

• #60551f3eaa7 - fix: contain SandboxHost render failures after teardown (@​Kinfe123)

• #611048f95b1 - chore: delete the dead ensureBinding and useRuntimeState utilities (@​samdickson22)

  src/context/react/utils/ensureBinding.ts and src/context/react/utils/useRuntimeState.ts imported only each other. Nothing else in the repo referenced them, neither appears in the package barrel or the api-surface snapshot, and the "."-only exports map made them unreachable to consumers. ensureBinding was an external caller of __internal_bindMethods that no longer had a caller of its own; the runtime classes bind themselves in their constructors, so nothing changes at runtime. The public API surface is unchanged and every other emitted file is byte-identical.

• #61569c65b51 - deprecate leftover Primitive.If and Empty wrappers on react-native and react-ink, and point them at AuiIf (@​okisdev)

  ThreadIf now reads thread.isEmpty instead of messages.length === 0, matching the loading-aware field already used by ThreadEmpty and AuiIf. First-party examples and docs samples that still called the leftover wrappers now use AuiIf directly.

• #6084ca9e72c - fix: resync trigger popover cursor after selection (@​rupic-app)

• #605459e9a08 - fix: handle rejected asynchronous Markdown exports (@​Kinfe123)

• #6098b9b9dad - fix: drain unrevealed smooth text when a message completes before any frame (@​rupic-app)

• #606175dfbe3 - docs: document Escape-to-stop-speaking on ThreadPrimitive.Root (@​samdickson22)

• #612406b04a7 - chore: update dependencies (@​okisdev)

• Updated dependencies [fa30915, b355aef, f7bd2d9, 4947ef4, 332f736, ef9254d, 9c65b51, 5845ba7, 1b30bfd, 365e763, d19921d, 996aa57, 21d6e87, cd247e5, f2b3ef8, 1bf263b, 19e52c4, 06b04a7, a614b5e, 07b51db, 92e52bd]:

  • @​assistant-ui/core@​0.3.15
  • @​assistant-ui/tap@​0.9.14
  • assistant-stream@0.3.39

@​assistant-ui/react@​0.15.15

Patch Changes

• #6071c3fd447 - feat: host assistant-cloud thread lists on AISDKThreads via RemoteThreadList (@​okisdev)

  AISDKThreads({ cloud }) uses RemoteThreadList and remounts each thread like useChatRuntime. Cloud history withFormat resolves persistence per call so one adapter can serve many threads. useExternalHistory waits for threadListItem.remoteId instead of latching on the first empty paint.

• #5872f9529bf - feat: move useAssistantTransportRuntime into core/react (@​okisdev)

• #5872f9529bf - fix: persist data message parts in aui/v0 cloud history (@​okisdev)

• #583924a1af7 - fix: validate MCP App resource responses (@​Kinfe123)

• #5817dab7b7a - fix: dispose sandbox frames when bridge setup fails (@​Kinfe123)

... (truncated)

Changelog

Sourced from @​assistant-ui/react's changelog.

0.15.16

Patch Changes

• #6136f7bd2d9 - fix: keep DevTools updates flowing when a subscriber throws (@​Kinfe123)

• #60551f3eaa7 - fix: contain SandboxHost render failures after teardown (@​Kinfe123)

• #611048f95b1 - chore: delete the dead ensureBinding and useRuntimeState utilities (@​samdickson22)

  src/context/react/utils/ensureBinding.ts and src/context/react/utils/useRuntimeState.ts imported only each other. Nothing else in the repo referenced them, neither appears in the package barrel or the api-surface snapshot, and the "."-only exports map made them unreachable to consumers. ensureBinding was an external caller of __internal_bindMethods that no longer had a caller of its own; the runtime classes bind themselves in their constructors, so nothing changes at runtime. The public API surface is unchanged and every other emitted file is byte-identical.

• #61569c65b51 - deprecate leftover Primitive.If and Empty wrappers on react-native and react-ink, and point them at AuiIf (@​okisdev)

  ThreadIf now reads thread.isEmpty instead of messages.length === 0, matching the loading-aware field already used by ThreadEmpty and AuiIf. First-party examples and docs samples that still called the leftover wrappers now use AuiIf directly.

• #6084ca9e72c - fix: resync trigger popover cursor after selection (@​rupic-app)

• #605459e9a08 - fix: handle rejected asynchronous Markdown exports (@​Kinfe123)

• #6098b9b9dad - fix: drain unrevealed smooth text when a message completes before any frame (@​rupic-app)

• #606175dfbe3 - docs: document Escape-to-stop-speaking on ThreadPrimitive.Root (@​samdickson22)

• #612406b04a7 - chore: update dependencies (@​okisdev)

• Updated dependencies [fa30915, b355aef, f7bd2d9, 4947ef4, 332f736, ef9254d, 9c65b51, 5845ba7, 1b30bfd, 365e763, d19921d, 996aa57, 21d6e87, cd247e5, f2b3ef8, 1bf263b, 19e52c4, 06b04a7, a614b5e, 07b51db, 92e52bd]:

  • @​assistant-ui/core@​0.3.15
  • @​assistant-ui/tap@​0.9.14
  • assistant-stream@0.3.39

0.15.15

Patch Changes

• #6071c3fd447 - feat: host assistant-cloud thread lists on AISDKThreads via RemoteThreadList (@​okisdev)

  AISDKThreads({ cloud }) uses RemoteThreadList and remounts each thread like useChatRuntime. Cloud history withFormat resolves persistence per call so one adapter can serve many threads. useExternalHistory waits for threadListItem.remoteId instead of latching on the first empty paint.

• #5872f9529bf - feat: move useAssistantTransportRuntime into core/react (@​okisdev)

• #5872f9529bf - fix: persist data message parts in aui/v0 cloud history (@​okisdev)

• #583924a1af7 - fix: validate MCP App resource responses (@​Kinfe123)

... (truncated)

Commits

• 75e3ef7 chore: update versions (#6086)
• f7bd2d9 fix(react): isolate devtools subscribers (#6136)
• 9c65b51 fix(react-native,react-ink): honor thread.isEmpty in leftover ThreadIf (#6156)
• 48f95b1 chore(react): delete the dead ensureBinding and useRuntimeState utilities (#6...
• 06b04a7 chore: update dependencies (#6124)
• b9b9dad fix: drain smooth text when a message completes before an animation frame (#6...
• 10a0f3a test(react): vary live-completion fetcher and cacheKey independently (#6062)
• b355aef fix(core): prevent assistant frame origin downgrades (#5823)
• 75dfbe3 docs(react): document Escape-to-stop-speaking on ThreadPrimitive.Root (#6061)
• ca9e72c fix(react): resync trigger cursor after selection (#6082) (#6084)
• Additional commits viewable in compare view

Updates @assistant-ui/store from 0.2.21 to 0.3.10

Release notes

Sourced from @​assistant-ui/store's releases.

@​assistant-ui/store@​0.3.10

Patch Changes

• #6068ac0c836 - fix: stabilize unstable_useAdapters results on both adapter faces and warn on an unkeyed history factory. the React host's synthesized provider now absorbs a fresh but shallow-equal adapters bag the same way the RemoteThreadList store entry does, reusing the store's useShallowStable primitive through its internal entry, and the store entry warns in development when a history adapter arrives while the thread factory is unkeyed, since switching threads would silently keep the first thread's history. (@​okisdev)

• #58312b0fec7 - feat: aui.optional.<scope> resolves an unavailable scope to undefined instead of a throwing accessor, mirroring s.optional on the state side; the documented availability check moves off source != null (@​okisdev)

• #5998f44163f - fix: stop active chats only when their standalone client is destroyed (@​Kinfe123)

• #5834d80e988 - fix: model-context registrations follow the committed scope across structural replacements. The new useAssistantScopeEffect(scope, effect, deps) re-runs a registration when the scope's bound client is replaced (cleaning up against the old one first) while ignoring value updates, and the toolkit, runtime-adapter, interactables, and MCP registration sites now use it instead of registering once against a stable client ref. (@​okisdev)

• #589774dca03 - fix: cache live config source reads between notifications so getConfig satisfies the useSyncExternalStore getSnapshot contract (@​Yonom)

• #59131b9c33d - feat: hoist the shared binding utilities to the client entry. createClientFacade (stable client facade over a source) and createLastValidCache/createStaleReporter (by-index shrink guard with an injectable expiry scheduler) were duplicated per framework bridge; they now live on @​assistant-ui/store/client so bridges cannot drift. (@​okisdev)

• #561882e2bde - refactor: the config path rides React's scheduler instead of a self-scheduled tap root (@​Yonom)

• #588952df42d - feat: subscription-owned lifecycle for createAssistantClient. the handle now rides tap's mountOnSubscribe: scopes render lazily on first read, mount when the first subscriber attaches, and soft unmount one task after the last subscriber releases (effects clean up, state is retained, a later subscriber remounts the same scopes). state updates before the first subscriber throw; an imperative consumer without a reactive framework holds a no-op subscription. destroy() remains the permanent teardown: synchronous while subscribers are attached; after the last release it defers to the soft unmount that release already scheduled. requires @​assistant-ui/tap ^0.9.12. (@​okisdev)

• #59286c9e7dd - feat: hoist the viewport scroll math to the client entry. isViewportAtBottom, viewportOverflows, isUserScrollUp, and observeContentResize were vue-local; they now live on @​assistant-ui/store/client so the svelte viewport consumes the same implementation. (@​okisdev)

• #60147748e15 - feat: host remote thread runtimeHooks as keyed tap resources on the list hook. useRemoteThreadListRuntime mounts one useResources host after each thread's unstable_Provider, so the first runtimeHook call already sees Provider adapters. AdapterSink only publishes those adapters. @assistant-ui/store/client exports useConfiguredAui and useAssistantContextProvider so that host can extend and provide a client the same way AuiProvider does in React. (@​okisdev)

• #59140d2e23f - feat: new threads.selectionChanged event carrying threadId and previousThreadId; deprecate threadListItem.switchedTo/switchedAway in its favor. Un-deprecate the semantically meaningful events (thread.runStart, thread.runEnd, thread.initialize, composer.send, composer.attachmentAdd). (@​Yonom)

  The new event fires in situations where the deprecated pair did not, so the selection-driven defaults (scrollToBottomOnThreadSwitch, unstable_focusOnThreadSwitched) now engage there too: InMemoryThreadList emits on selection changes (it previously emitted no switch events at all), switchToNewThread() emits for the newly created thread, and runtimes that resolve a deep-linked threadId/initialThreadId after mount (useRemoteThreadListRuntime) emit when the deep link resolves, with the initial placeholder thread as previousThreadId.

@​assistant-ui/store@​0.3.9

Patch Changes

• #58294b75b8f - fix: scoped event listeners under a derived-only provider filter against the child's own bindings instead of the parent's, in both directions and through scope-less intermediate hosts (@​okisdev)

• #579500a630a - fix: publish hosted scope rebinds before descendant layout effects (@​Gujiassh)

• #5769f59d24b - fix: deliver threadListItem.switchedTo to default-scope listeners (#5699). the thread list item client now emits the switch from its own observed selection transition, after the flush that rebinds the derived scopes, instead of relaying the runtime's synchronous notification. scoped listeners now resolve their scope against the host's current client at delivery time, so a listener subscribed before a structural swap follows the scope's present binding; the notification manager re-reads the listener set at flush time per the documented live-set semantics. listeners that need a pinned instance subscribe on an id-scoped client instead. (@​okisdev)

Changelog

Sourced from @​assistant-ui/store's changelog.

0.3.10

Patch Changes

• #6068ac0c836 - fix: stabilize unstable_useAdapters results on both adapter faces and warn on an unkeyed history factory. the React host's synthesized provider now absorbs a fresh but shallow-equal adapters bag the same way the RemoteThreadList store entry does, reusing the store's useShallowStable primitive through its internal entry, and the store entry warns in development when a history adapter arrives while the thread factory is unkeyed, since switching threads would silently keep the first thread's history. (@​okisdev)

• #58312b0fec7 - feat: aui.optional.<scope> resolves an unavailable scope to undefined instead of a throwing accessor, mirroring s.optional on the state side; the documented availability check moves off source != null (@​okisdev)

• #5998f44163f - fix: stop active chats only when their standalone client is destroyed (@​Kinfe123)

• #5834d80e988 - fix: model-context registrations follow the committed scope across structural replacements. The new useAssistantScopeEffect(scope, effect, deps) re-runs a registration when the scope's bound client is replaced (cleaning up against the old one first) while ignoring value updates, and the toolkit, runtime-adapter, interactables, and MCP registration sites now use it instead of registering once against a stable client ref. (@​okisdev)

• #589774dca03 - fix: cache live config source reads between notifications so getConfig satisfies the useSyncExternalStore getSnapshot contract (@​Yonom)

• #59131b9c33d - feat: hoist the shared binding utilities to the client entry. createClientFacade (stable client facade over a source) and createLastValidCache/createStaleReporter (by-index shrink guard with an injectable expiry scheduler) were duplicated per framework bridge; they now live on @​assistant-ui/store/client so bridges cannot drift. (@​okisdev)

• #561882e2bde - refactor: the config path rides React's scheduler instead of a self-scheduled tap root (@​Yonom)

• #588952df42d - feat: subscription-owned lifecycle for createAssistantClient. the handle now rides tap's mountOnSubscribe: scopes render lazily on first read, mount when the first subscriber attaches, and soft unmount one task after the last subscriber releases (effects clean up, state is retained, a later subscriber remounts the same scopes). state updates before the first subscriber throw; an imperative consumer without a reactive framework holds a no-op subscription. destroy() remains the permanent teardown: synchronous while subscribers are attached; after the last release it defers to the soft unmount that release already scheduled. requires @​assistant-ui/tap ^0.9.12. (@​okisdev)

• #59286c9e7dd - feat: hoist the viewport scroll math to the client entry. isViewportAtBottom, viewportOverflows, isUserScrollUp, and observeContentResize were vue-local; they now live on @​assistant-ui/store/client so the svelte viewport consumes the same implementation. (@​okisdev)

• #60147748e15 - feat: host remote thread runtimeHooks as keyed tap resources on the list hook. useRemoteThreadListRuntime mounts one useResources host after each thread's unstable_Provider, so the first runtimeHook call already sees Provider adapters. AdapterSink only publishes those adapters. @assistant-ui/store/client exports useConfiguredAui and useAssistantContextProvider so that host can extend and provide a client the same way AuiProvider does in React. (@​okisdev)

• #59140d2e23f - feat: new threads.selectionChanged event carrying threadId and previousThreadId; deprecate threadListItem.switchedTo/switchedAway in its favor. Un-deprecate the semantically meaningful events (thread.runStart, thread.runEnd, thread.initialize, composer.send, composer.attachmentAdd). (@​Yonom)

  The new event fires in situations where the deprecated pair did not, so the selection-driven defaults (scrollToBottomOnThreadSwitch, unstable_focusOnThreadSwitched) now engage there too: InMemoryThreadList emits on selection changes (it previously emitted no switch events at all), switchToNewThread() emits for the newly created thread, and runtimes that resolve a deep-linked threadId/initialThreadId after mount (useRemoteThreadListRuntime) emit when the deep link resolves, with the initial placeholder thread as previousThreadId.

0.3.9

Patch Changes

• #58294b75b8f - fix: scoped event listeners under a derived-only provider filter against the child's own bindings instead of the parent's, in both directions and through scope-less intermediate hosts (@​okisdev)

• #579500a630a - fix: publish hosted scope rebinds before descendant layout effects (@​Gujiassh)

• #5769f59d24b - fix: deliver threadListItem.switchedTo to default-scope listeners (#5699). the thread list item client now emits the switch from its own observed selection transition, after the flush that rebinds the derived scopes, instead of relaying the runtime's synchronous notification. scoped listeners now resolve their scope against the host's current client at delivery time, so a listener subscribed before a structural swap follows the scope's present binding; the notification manager re-reads the listener set at flush time per the documented live-set semantics. listeners that need a pinned instance subscribe on an id-scoped client instead. (@​okisdev)

0.3.8

Patch Changes

• #572394dc3e5 - chore: update dependencies (@​okisdev)

0.3.7

Patch Changes

• #56774e99deb - feat: createAssistantClient accepts an AssistantConfigSource, re-read in the root render so bindings can deliver config changes (updated element args, added or removed scopes) without remounting surviving scopes (@​okisdev)

... (truncated)

Commits

• 4db781c chore: update versions (#5832)
• ac0c836 fix(core): stabilize useAdapters on both faces, warn on unkeyed history (#6068)
• f44163f fix(ai-sdk): stop owned chats on client destroy (#5998)
• 7748e15 feat(core): host remote thread runtimeHooks as keyed tap resources (#6014)
• 6c9e7dd feat(svelte): thread viewport and scroll to bottom builders (#5928)
• 0d2e23f feat(core): threads.selectionChanged event; deprecate threadListItem.switched...
• 1b9c33d feat: dedupe the binding layer into neutral seams (#5913)
• Cursor Bugbot for commit 8f908b0. Bugbot is set up for automated code reviews on this repo. Configure here.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8f908b0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[cursor]

Published packages lack a changeset

Low Severity

This PR changes runtime dependencies that ship in published packages but does not add a .changeset/*.md. Run pnpm changeset and bump @truefoundry/trueforge-core, @truefoundry/trueforge, and @truefoundry/trueforge-ui (frontend is bundled into the server tarball).

Additional Locations (2)

• packages/trueforge-core/package.json#L109-L113
• packages/trueforge/package.json#L57-L61

^{Triggered by project rule: TrueForge review rules}

^{Reviewed by Cursor Bugbot for commit a82da72. Configure here.}

[cursor]

Stale assistant-ui peer ranges

Medium Severity

@truefoundry/trueforge-ui now depends on @assistant-ui/core0.3.15 and @assistant-ui/react0.15.16, but optional peers remain ^0.2.22 and ^0.14.24. Those 0.x caret ranges do not include the new minors, so hosts that install the peers get a conflict with the bundled copies.

^{Reviewed by Cursor Bugbot for commit abcd91f. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

There are 3 total unresolved issues (including 2 from previous reviews).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 8f908b0. Configure here.}

[cursor]

Published packages missing changeset

Low Severity

This PR changes dependencies that ship in published packages but adds no .changeset/*.md file. A changeset is needed so the next release bumps @truefoundry/trueforge-core, @truefoundry/trueforge, and @truefoundry/trueforge-ui (frontend assets are bundled into the @truefoundry/trueforge tarball).

Additional Locations (2)

• packages/trueforge/package.json#L57-L61
• packages/trueforge-ui/package.json#L94-L103

^{Triggered by project rule: TrueForge review rules}

^{Reviewed by Cursor Bugbot for commit 8f908b0. Configure here.}