Bump @assistant-ui/core from 0.3.12 to 0.3.17 in /assets

[dependabot]

Bumps @assistant-ui/core from 0.3.12 to 0.3.17.

Changelog

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

0.3.17

Patch Changes

• #6723 8cc962e - feat: let a tool approval request describe itself and report its outcome (@​okisdev)

  an approval carries prompt, display, and allowFreeform, so a renderer can tell a question from a permission gate without reading provider metadata, and ToolApprovalResponse gains a text answer that resolves the request as answered rather than approved. respondToToolApproval now returns a promise that rejects when the runtime could not record the response, instead of the external-store runtime logging the rejection away, so a refused response leaves the request retryable.

• #6539 2a31285 - fix: avoid duplicate external-store runtime publications (@​rupic-app)

• #6685 205acf5 - refactor: walk the nested tool-call tree through one shared traversal (@​okisdev)

• #6678 740a573 - fix: never execute a frontend tool on a tool call ADK resolves itself; a client-executed tool must be registered as a LongRunningFunctionTool on the agent (@​okisdev)

• #6498 65d449b - feat: background thread bodies and a plain cloud adapter factory (@​okisdev)

  RemoteThreadList gains a backgroundThreads mode that keeps every visited thread mounted: runs continue across switches, per-item isRunning is live, per-thread history and adapters mount once per body, and a freshly initialized thread generates its title. createCloudThreadListAdapter builds the assistant-cloud adapter without a hook call site so non-React hosts can construct it in plain code.

• #6671 79283c5 - fix: report lifecycle events from background thread runtimes (@​rupic-app)

• #6645 9ec29e1 - fix: report run start and end for threads a remote thread list keeps alive in the background (@​Kinfe123)

• #6702 14fc938 - fix: cancel AssistantFrame tool calls when their provider is removed (@​Kinfe123)

• #6562 3f7af8b - fix: preserve composer queue item component identity after removals (@​Kinfe123)

• #6597 5511057 - fix: preserve thread list item state when preceding threads are removed (@​Kinfe123)

• #6580 dc2cab3 - chore: stop hand-rolling the cloud adapter provider that the hosts synthesize (@​okisdev)

• #6587 d75944b - fix: keep Cloud thread adapter options scoped to committed renders (@​Kinfe123)

• #6547 6bd1570 - fix: drop zustand from core (@​okisdev)

  core declared zustand as an optional peer while importing create and useShallow unconditionally. pnpm keys a package instance on its resolved peers, so two dependency branches landing on different zustand patches (5.0.14 under one, 5.0.15 under the other) produced two physical copies of core. React context is per copy, so a RuntimeAdapterProvider rendered by one copy was invisible to a runtime hook imported from the other: unstable_Provider supplied a history adapter, useAISDKRuntime read undefined, withFormat() never fired, and every thread loaded with no messages and no error.

  core no longer uses zustand at all, so the peer is gone rather than reclassified. the four internal stores now use WritableSubscribable, a mutable cell built on the existing BaseSubscribable and read through useSubscribable. the two useShallow call sites wrapped selectors passed to useAuiState, aui's own store, so they now use useShallowSelector from @assistant-ui/store/internal, which memoizes a selector against the shallowEqual that already lived there.

  WritableSubscribable reports a server snapshot and useSubscribable forwards one when the subscribable offers it, so the components reading these stores render under SSR the way the zustand hook did. Subscribables without one, including every existing runtime client, keep their current behaviour.

  @assistant-ui/react-native and @assistant-ui/react-ink declared zustand only to satisfy core's optional peer and never imported it, so they no longer declare it. @assistant-ui/react and @assistant-ui/ui keep theirs because they import it directly, and @assistant-ui/react additionally exposes StoreApi through ReadonlyStore in its published types.

• #6758 60ae973 - fix: keep model context callbacks scoped to committed React renders (@​Kinfe123)

• #6719 0fb5390 - fix: never run a frontend tool on a call the provider is about to answer or gate (@​okisdev)

  a tool call whose name matched a registered tool closed its args stream, and therefore executed, as soon as argsText parsed. providers that answer or gate a call do so one or more snapshots later, so in that window a frontend execute fired on a call the provider was about to take: the AG-UI interrupt protocol carries the outcome only on RUN_FINISHED, so the gate landed on a call the client had already run.

  closing the args stream now waits until the provider can no longer speak about the call. unstable_isClientToolCall decides that per call: a call the adapter reports as client-owned closes as soon as its arguments parse, and a call whose ownership is unknown closes when the run ends. @assistant-ui/react-google-adk supplies the predicate and keeps its previous timing; every other runtime defers a frontend tool to the end of the run. streamCall still fires once and still streams partial arguments as they arrive, so rendering is unchanged, but a tool that pairs streamCall with execute (interactables) now commits its authoritative merge when the run settles.

... (truncated)

Commits

• d511ff4 chore: update versions (#6482)
• 0c68179 fix(core): isolate model context update listener errors (#6781)
• ddaac94 fix(core): isolate late initialize listener errors (#6728)
• 1fa3e09 fix(ai-sdk): mark stopped runs as cancelled (#6761)
• 0c5c574 fix(core): keep a pending human() interrupt when execution starts (#6764)
• 47a46db fix: keep remote thread clients commit-safe (#6760)
• 60ae973 fix(core): keep model context hooks commit-safe (#6758)
• 8cc962e feat: let a tool approval request describe itself and report its outcome (#6723)
• 0fb5390 fix(core): run a frontend tool only once the provider's run settles (#6719)
• 6fdfc23 fix(core): keep remote thread runtime hooks commit-safe (#6711)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)