@subako-ai/assistant-ui 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Kikuvi, Inc.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,300 @@
+# @subako-ai/assistant-ui
+
+[assistant-ui](https://www.assistant-ui.com) over a Subako session: one hook
+that turns the session into an assistant-ui runtime, and one component that
+renders a working chat with no setup at all.
+
+Requires **React 19**, **`@assistant-ui/react` 0.15** with
+**`@assistant-ui/react-markdown` 0.14**, and **Node 22 or newer** for the
+build. The package is **ESM only**.
+
+```sh
+pnpm add @subako-ai/assistant-ui @subako-ai/react @subako-ai/sdk @assistant-ui/react @assistant-ui/react-markdown
+```
+
+## Getting started
+
+The provider and the session are `@subako-ai/react`'s; this package is what
+draws them.
+
+```tsx
+import { SubakoSessionClient } from "@subako-ai/sdk";
+import { SubakoProvider, useSession } from "@subako-ai/react";
+import { SubakoChat } from "@subako-ai/assistant-ui";
+
+const subako = new SubakoSessionClient({
+	baseUrl: "https://api.kikuvi.com",
+	getToken: (sessionId) => fetch(`/api/subako/token/${sessionId}`).then((r) => r.text()),
+});
+
+function Assistant({ sessionId }: { sessionId: string }) {
+	// The app opens the session and hands it down, so the chat opens no second connection.
+	return <SubakoChat session={useSession(sessionId)} />;
+}
+
+export function App({ sessionId }: { sessionId: string }) {
+	return (
+		<SubakoProvider client={subako}>
+			<Assistant sessionId={sessionId} />
+		</SubakoProvider>
+	);
+}
+```
+
+That is the whole chat: the transcript, the tool calls with their results, the
+approval prompt, a composer, and a stop button while a run is under way. The
+assistant's text is drawn as markdown, tables and all, with links that open in
+a new tab; what the person typed is shown as typed. The
+`session` is the one the app opened — `useSession` hands back `null` until its
+effect has connected, which the chat renders as an empty thread with a disabled
+composer — so the tools the app declares and the thread share one connection. It
+brings its own small stylesheet, so it renders acceptably with nothing else
+installed — no CSS framework, no shadcn registry, no `@assistant-ui/styles`.
+`className` lands on the root element for an app that wants to style it, and
+the class names below are stable:
+
+| Class                                      | What it is                                    |
+| ------------------------------------------ | --------------------------------------------- |
+| `.subako-chat`                             | The root.                                     |
+| `.subako-viewport`                         | The scrolling message list.                   |
+| `.subako-message`, `-user`, `-assistant`   | One bubble.                                   |
+| `.subako-markdown`                         | The assistant's body, as markdown.            |
+| `.subako-thinking`                         | A `thinking` block.                           |
+| `.subako-tool`                             | One tool call, folded to its name and status. |
+| `.subako-tool-args`, `.subako-tool-result` | The input and the output behind the fold.     |
+| `.subako-approval`                         | The allow / deny prompt.                      |
+| `.subako-composer`, `.subako-input`        | The composer.                                 |
+
+### Overriding the styles
+
+Every rule of the stylesheet sits in a cascade layer named `subako`. A rule
+of the app's own that names one of the classes above wins over it, at any
+specificity and from anywhere in the page:
+
+```css
+.subako-user {
+	border-radius: 4px;
+}
+```
+
+A rule that names no class — a reset's `*` and `button`, the app's own `pre` —
+does not reach the chat's own elements. Each of them carries a guard, in no
+layer, that turns unlayered element rules away and takes the layered ones
+instead, so Tailwind v3's preflight, a `normalize.css`, and the app's global
+`button` all leave the chat as it is. The one rule of a reset's that still
+reaches a button is `[type="button"]`, which names an attribute; it takes the
+background only, and the buttons are the colour of the bar they sit on. A tool
+UI the app draws itself is not guarded: that is the app's own markup.
+
+An app whose CSS is layered itself — Tailwind v4 is one — says where `subako`
+goes by naming it in its layer order, ahead of anything else that declares a
+layer. After `base`, so preflight does not strip the chat's own buttons;
+before `components` and `utilities`, so a class the app puts on the root, and
+an override the app writes inside a layer of its own, both win:
+
+```css
+@layer theme, base, subako, components, utilities;
+@import "tailwindcss";
+```
+
+Left unnamed, `subako` lands last and the chat's own rules beat the app's
+layered ones.
+
+### A page with a Content Security Policy
+
+The stylesheet above is an inline `<style>`, so a page whose `style-src-elem`
+names a nonce drops it and the thread renders unstyled. Hand the chat the same
+nonce the page puts on its own tags:
+
+```tsx
+<SubakoChat session={session} nonce={cspNonce} />
+```
+
+A page with no such policy needs nothing: left out, the attribute is not
+written at all.
+
+### Colours
+
+Every surface names its own colour and its own background, so the chat is
+legible on a page of any colour instead of inheriting half of one. They come
+from eight custom properties, light by default and dark under
+`prefers-color-scheme: dark`; the root also carries `color-scheme: light dark`
+so form controls follow. Set the properties on `.subako-chat` itself to theme
+the chat with the app's own palette — a value set above it is shadowed by the
+chat's own defaults — which is how an app
+whose dark mode is a class or a `data-theme`, rather than the OS setting, keeps
+the chat in step:
+
+```css
+.subako-chat {
+	--subako-bg: var(--card);
+	--subako-fg: var(--ink);
+	--subako-muted: var(--dim);
+	--subako-accent: var(--accent);
+	--subako-accent-fg: #fff;
+	--subako-border: var(--line);
+	--subako-surface: var(--bg);
+	--subako-error: var(--danger);
+	color-scheme: inherit;
+}
+```
+
+`--subako-bg` is the panel, the composer and its controls; `--subako-surface`
+is the raised one — the assistant bubble, the tool call's arguments and result,
+the approval bar; `--subako-accent` with `--subako-accent-fg` is the user
+bubble; `--subako-muted` is the reasoning block and the placeholder;
+`--subako-error` is a failed tool result.
+
+## `useSubakoRuntime`
+
+```tsx
+const session = useSession(sessionId);
+const runtime = useSubakoRuntime(session);
+```
+
+`useExternalStoreRuntime` over the session. The log stays the only store: the
+runtime keeps no messages of its own, so a send that fails leaves the thread as
+the server has it. A `null` session — the one `useSession` has yet to open — is
+a thread with no messages and a composer that cannot be typed into.
+
+The runtime subscribes to the session itself, with `@subako-ai/react`'s
+`useSessionState`, so the thread follows the log wherever it is mounted. That
+matters because `useSession` only acquires: hand the session to a `<SubakoChat>`
+sitting in some provider's `children` and its props never change, so React would
+never redraw it. Nothing above the chat has to re-render for a new message to
+appear.
+
+| assistant-ui              | Subako                                                         |
+| ------------------------- | -------------------------------------------------------------- |
+| `messages`                | `state.transcript`, through `convertMessage`                   |
+| `isRunning`               | `state.isRunning`                                              |
+| `onNew`                   | `send(text)`, over the text parts of the appended message      |
+| `onCancel`                | `cancel()`                                                     |
+| `onRespondToToolApproval` | `resolveApproval(callId, approved ? "allow" : "deny", reason)` |
+
+The argument is anything carrying those members, or `null`, which is what
+`useSession` hands back.
+
+### `convertMessage`
+
+The pure half, exported so an app can convert a transcript without a runtime:
+
+| Log                | assistant-ui                                                |
+| ------------------ | ----------------------------------------------------------- |
+| `text` block       | a text part                                                 |
+| `thinking` block   | a reasoning part                                            |
+| `tool_call` block  | a tool-call part, with the joined `tool_result` as its text |
+| a pending approval | an approval with no decision, which is what shows a prompt  |
+| a settled approval | the same approval, carrying the decision                    |
+| the event's `seq`  | the message id                                              |
+
+The conversion is cached on the identity of the message object, not on the id,
+and the connection's `transcript` folds a new event into the messages it already
+made — replacing only the ones that event touched — so every other message is
+converted once and stays converted. A user message carries where it came from as
+`metadata.custom.source`.
+
+## Your own thread
+
+`<SubakoChat>` exists for the first ten minutes. A real app keeps the runtime
+and builds the thread from assistant-ui's primitives, or from the components
+its shadcn registry installs:
+
+```tsx
+function Chat({ sessionId }: { sessionId: string }) {
+	const session = useSession(sessionId);
+	const runtime = useSubakoRuntime(session);
+
+	return (
+		<AssistantRuntimeProvider runtime={runtime}>
+			<ThreadPrimitive.Root>
+				<ThreadPrimitive.Viewport>
+					<ThreadPrimitive.Messages components={{ UserMessage, AssistantMessage }} />
+				</ThreadPrimitive.Viewport>
+				<ComposerPrimitive.Root>
+					<ComposerPrimitive.Input />
+					<ComposerPrimitive.Send>Send</ComposerPrimitive.Send>
+				</ComposerPrimitive.Root>
+			</ThreadPrimitive.Root>
+		</AssistantRuntimeProvider>
+	);
+}
+```
+
+The approval prompt is a tool-call part with an `approval` that carries no
+decision; answer it with the part's own `respondToApproval({ approved })`, which
+is what reaches `resolveApproval`. The stop button is
+`<ComposerPrimitive.Cancel>`, which the runtime wires to `cancel()`.
+
+## Tool UI
+
+A tool call renders as a row folded to its name and its status — running,
+done, failed, needs approval, denied. Opening the row shows the input and the
+output, laid out as JSON when they are JSON. The approval prompt sits outside
+the fold, so a closed row still asks. To draw one of your tools yourself,
+register a tool UI the ordinary assistant-ui way; it wins over the default row.
+`<SubakoChat>` renders its children inside the runtime, which is where the
+registration has to happen:
+
+```tsx
+import { makeAssistantToolUI } from "@assistant-ui/react";
+
+const FillForm = makeAssistantToolUI<{ email?: string }, string>({
+	toolName: "client__chat__fill_contact_form",
+	render: ({ args, result }) => (result === undefined ? <p>Filling…</p> : <p>Filled {args.email}</p>),
+});
+
+<SubakoChat session={session}>
+	<FillForm />
+</SubakoChat>;
+```
+
+The name is what the model sees the tool under, which for a client tool is
+`client__<client name>__<tool>`.
+
+### `components`
+
+The same renderers go on `<SubakoChat>` as `components`, which takes what
+`MessagePrimitive.Parts` takes: `tools.by_name` for the tools named,
+`tools.Fallback` for every other one in place of the chat's own row, and
+`Text` for the body in place of the chat's own markdown — for a renderer with
+a syntax highlighter, say, built on `MarkdownTextPrimitive` the way the chat's
+is. The chat's body, its reasoning block and its tool row stay wherever nothing
+is named.
+
+```tsx
+function FilledForm({ args, result }: ToolCallMessagePartProps) {
+	return result === undefined ? <p>Filling…</p> : <p>Filled {String(args.email)}</p>;
+}
+
+<SubakoChat session={session} components={{ tools: { by_name: { client__chat__fill_contact_form: FilledForm } } }} />;
+```
+
+### `SubakoToolApproval`
+
+A tool that needs approval has to ask for it from whatever draws it: a row of
+the app's own gets `approval` and `respondToApproval` like any tool-call part,
+and the run waits until something answers. `SubakoToolApproval` is the chat's
+own prompt, for dropping in — Allow and Deny while the server waits on the
+person, nothing once there is an answer or the run was cancelled:
+
+```tsx
+import { SubakoToolApproval } from "@subako-ai/assistant-ui";
+
+function Terse(props: ToolCallMessagePartProps) {
+	return (
+		<div>
+			{props.toolName}
+			<SubakoToolApproval {...props} />
+		</div>
+	);
+}
+
+<SubakoChat session={session} components={{ tools: { Fallback: Terse } }} />;
+```
+
+## What it does not do
+
+No thread list, no branching, no editing, no attachments, no speech: the
+session is one conversation, its log is append-only, and the runtime declares
+only what the session can actually do.

package/dist/chat.d.ts

@@ -0,0 +1,49 @@
+import type { ToolCallMessagePartProps } from "@assistant-ui/react";
+import { MessagePrimitive } from "@assistant-ui/react";
+import type { ComponentProps, ReactNode } from "react";
+import type { SubakoSession } from "./runtime.js";
+/** What the approval prompt reads off a tool-call part: the call's name, its approval, and the answer. */
+export type SubakoToolApprovalProps = Pick<ToolCallMessagePartProps, "toolName" | "approval" | "respondToApproval">;
+/**
+ * The approval prompt of the chat's own tool row, for a tool UI the app draws
+ * itself: Allow and Deny while the server waits on the person, and nothing
+ * once there is an answer or the run was cancelled. Spread the tool call's
+ * props into it; the answer reaches `resolveApproval` the same way.
+ */
+export declare function SubakoToolApproval({ toolName, approval, respondToApproval }: SubakoToolApprovalProps): ReactNode;
+/** The components an assistant message's parts are drawn with, as `MessagePrimitive.Parts` takes them. */
+type PartComponents = NonNullable<ComponentProps<typeof MessagePrimitive.Parts>["components"]>;
+export interface SubakoChatProps {
+    /** The connection from `useSession`, which is `null` until its effect has opened one. */
+    readonly session: SubakoSession | null;
+    /** Added to the root element, for an app that styles the thread itself. */
+    readonly className?: string;
+    /**
+     * The components an assistant message's parts are drawn with, as
+     * `MessagePrimitive.Parts` takes them: `Text` for the body, in place of the
+     * chat's own markdown; `tools` for the tool calls, whose `Fallback` replaces
+     * the chat's own row and whose `by_name` replaces it for the tools named.
+     * The chat's body, reasoning block and tool row stay wherever nothing is
+     * named.
+     */
+    readonly components?: PartComponents;
+    /**
+     * The page's CSP nonce, for a page whose `style-src-elem` names one. Without
+     * it the browser drops the chat's own stylesheet and the thread renders
+     * unstyled; a page with no such policy needs nothing here.
+     */
+    readonly nonce?: string;
+    /** Rendered inside the runtime, which is where a tool UI registers itself. */
+    readonly children?: ReactNode;
+}
+/**
+ * One session as a working chat: the transcript, the tool calls with their
+ * approvals, a composer, and a stop button while a run is under way. The
+ * session is the app's own, so the chat opens no second connection; until it
+ * has one the thread is empty and the composer is disabled. It exists for the
+ * first ten minutes; an app that wants its own thread keeps `useSubakoRuntime`
+ * and builds the rest from assistant-ui's primitives.
+ */
+export declare function SubakoChat({ session, className, components, nonce, children }: SubakoChatProps): ReactNode;
+export {};
+//# sourceMappingURL=chat.d.ts.map

package/dist/chat.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"chat.d.ts","sourceRoot":"","sources":["../src/chat.tsx"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAA6B,wBAAwB,EAAE,MAAM,qBAAqB,CAAC;AAC/F,OAAO,EAIN,gBAAgB,EAEhB,MAAM,qBAAqB,CAAC;AAG7B,OAAO,KAAK,EAAE,cAAc,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AAGvD,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,cAAc,CAAC;AAyKlD,0GAA0G;AAC1G,MAAM,MAAM,uBAAuB,GAAG,IAAI,CAAC,wBAAwB,EAAE,UAAU,GAAG,UAAU,GAAG,mBAAmB,CAAC,CAAC;AAEpH;;;;;GAKG;AACH,wBAAgB,kBAAkB,CAAC,EAAE,QAAQ,EAAE,QAAQ,EAAE,iBAAiB,EAAE,EAAE,uBAAuB,GAAG,SAAS,CAehH;AA8CD,0GAA0G;AAC1G,KAAK,cAAc,GAAG,WAAW,CAAC,cAAc,CAAC,OAAO,gBAAgB,CAAC,KAAK,CAAC,CAAC,YAAY,CAAC,CAAC,CAAC;AA0C/F,MAAM,WAAW,eAAe;IAC/B,yFAAyF;IACzF,QAAQ,CAAC,OAAO,EAAE,aAAa,GAAG,IAAI,CAAC;IACvC,2EAA2E;IAC3E,QAAQ,CAAC,SAAS,CAAC,EAAE,MAAM,CAAC;IAC5B;;;;;;;OAOG;IACH,QAAQ,CAAC,UAAU,CAAC,EAAE,cAAc,CAAC;IACrC;;;;OAIG;IACH,QAAQ,CAAC,KAAK,CAAC,EAAE,MAAM,CAAC;IACxB,8EAA8E;IAC9E,QAAQ,CAAC,QAAQ,CAAC,EAAE,SAAS,CAAC;CAC9B;AAED;;;;;;;GAOG;AACH,wBAAgB,UAAU,CAAC,EAAE,OAAO,EAAE,SAAS,EAAE,UAAU,EAAE,KAAK,EAAE,QAAQ,EAAE,EAAE,eAAe,GAAG,SAAS,CAqB1G"}