@harapter/adapter-pi 0.1.1

package/LICENSE

@@ -0,0 +1,201 @@
+                                 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 Harapter contributors
+
+   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,228 @@
+# `@harapter/adapter-pi`
+
+`@harapter/adapter-pi` maps the official Pi Agent RPC mode to the portable
+Harapter lifecycle.
+
+The host installs, configures, authenticates, and operates Pi Agent. Harapter
+starts only the exact adapter-owned command selected by the Profile. It does not
+install a Pi Runtime or SDK, select models, manage credentials, read Session
+files, or change host security policy.
+
+## Installation
+
+```bash
+pnpm add @harapter/core@next @harapter/adapter-pi@next
+```
+
+## Runtime prerequisites and compatibility
+
+Connection requires the current documented `pi --mode rpc` strict LF-delimited
+JSONL interface. The Adapter probes the supplied command with `--version`,
+validates the semantic version response, and fails closed when required RPC
+responses or events are incompatible. The Runtime release is not pinned; a
+non-sensitive version hash participates in diagnostics and capability evidence.
+
+The fixture manifest records the upstream source revision inspected for the
+evidence baseline. That revision and Runtime version are provenance, not an
+allowlist. Pi Agent is MIT licensed; Harapter does not redistribute it. See the
+[license record](../../licenses/pi-agent.md).
+
+## Profile and process ownership
+
+A Pi Profile uses an adapter-owned process. The host provides the base command:
+
+```ts
+import { HarnessRegistry, profileId } from '@harapter/core';
+import { PI_PROVIDER_ID, createPiProviderFactory } from '@harapter/adapter-pi';
+
+const registry = new HarnessRegistry();
+registry.register(createPiProviderFactory());
+
+const client = await registry.connect({
+  profileId: profileId('pi-local'),
+  providerId: PI_PROVIDER_ID,
+  displayName: 'Pi Agent',
+  connection: {
+    kind: 'process',
+    command: '/opt/harapter-runtimes/bin/pi',
+    args: [],
+    ownership: 'adapter',
+  },
+});
+```
+
+The Adapter appends
+`--no-extensions --no-skills --no-prompt-templates --mode rpc` for each Session.
+The host must provide an absolute executable path. Shell execution, unresolved
+`envRefs`, external process ownership, explicit extensions, and arguments that
+override RPC mode, Session ownership, credentials, system prompts, or resource
+discovery policy are rejected. The Adapter does not inspect or interpolate
+environment entries, but the child process inherits the host-controlled
+environment that Pi may use for model configuration and authentication.
+
+Profile `providerOptions` accepts positive bounded values for
+`operationTimeoutMs`, `cancelSettlementTimeoutMs`, `maxRunEvents`,
+`maxPendingInteractions`, `maxPendingRequests`, `maxBufferedMessages`,
+`maxMessageBytes`, `maxPendingWrites`, and `writeTimeoutMs`. `persistSessions`
+defaults to `true`; `false` adds `--no-session` and disables resume. Unknown
+options are rejected. `maxRunEvents` must be between 2 and 4096 so an unread Run
+queue always reserves terminal capacity.
+
+## Session and Run lifecycle
+
+Each Harapter Session owns a separate Pi RPC process. This permits parallel
+Sessions without sharing Pi's mutable current-Session state, while each Session
+allows one active Run. The child always uses the Profile working directory, so
+version probing and Session execution interpret all Runtime arguments in the
+same directory. The Adapter resolves an omitted or relative Profile working
+directory once before probing. Portable per-Session Workspace selection is
+unsupported.
+
+After startup, the Adapter validates `get_state` and binds the native Session
+identifier, persistence mode, Provider, Profile, and compatibility family in
+`SessionRef`. Persisted resume starts a new process with `--session <native-id>`
+and requires the opened Session to report the same identifier. Harapter does not
+store or expose Pi Session-file paths and never implies that a Session reference
+is portable to another Provider or Profile.
+
+Session Workspace, system context, model selection, Session Provider options,
+and metadata are unsupported. Portable Runs accept non-empty text only; multiple
+text parts are joined with a newline. Input whose first non-whitespace character
+is `/` is rejected because Pi can interpret it as a slash command or Session
+mutation instead of an Agent Run. Extension, skill, and prompt-template
+discovery are disabled so ordinary portable text cannot be intercepted and
+reported as handled without an Agent lifecycle. Image, file, Provider-native
+input parts, Run metadata, and Run Provider options remain unsupported.
+
+Message, reasoning, tool lifecycle, usage, and extension UI observations map to
+portable events. Tool identifiers are hashed, and tool arguments or results are
+never retained in portable events. A successful `prompt` response proves only
+that Pi accepted the command. `agent_end` can precede retry activity and is not
+a stable terminal boundary. The Adapter waits for `agent_settled` and then uses
+the most recent validated Assistant `message_end` as terminal authority:
+
+- `stop` maps to `run.completed`;
+- `aborted` maps to `run.cancelled` only after a correlated successful `abort`
+  response; an unsolicited aborted terminal fails the Run;
+- `error`, `length`, `toolUse`, `deferred`, or `pending` maps to `run.failed`;
+- a missing or malformed Assistant outcome fails closed;
+- EOF, process loss, Client close, queue overflow, or unconfirmed cancellation
+  maps to `connection.aborted`.
+
+Events received after the terminal boundary cannot append to or rewrite the
+finished Run. Client and Session close reject with `connection_aborted` when
+child-process exit cannot be confirmed after bounded termination. The Client
+retains ownership records until cleanup succeeds, so a later close cannot report
+success for an unconfirmed child.
+
+## Cancellation, timeout, and interactions
+
+`run.cancel()` sends the official `abort` command, waits for its response, and
+reports `{ mode: 'native' }` only after an authoritative Assistant
+`stopReason: 'aborted'` followed by `agent_settled`. An abort acknowledgement,
+process termination, or connection loss alone is not cancellation evidence.
+
+A positive `RunOptions.timeoutMs` invokes the same abort operation but remains
+an emulated Harapter timer capability. If Pi does not establish the required
+terminal result within the bounded settlement window, the owning connection is
+aborted rather than reopened in an uncertain state.
+
+Pi extension UI requests for `select`, `confirm`, `input`, and `editor` map to
+portable Provider interactions. Their responses use the exported
+`PiProviderInteractionResponse` union. This capability starts as `unknown` and
+becomes `native` only after the connected Runtime emits a valid request.
+Portable approval and user-input capabilities remain unsupported because the
+official RPC surface exposes these calls as extension-owned UI methods rather
+than a general permission contract.
+
+## Unknown events, extension, and native access
+
+Unknown RPC events remain observable as bounded `provider` events and through
+`pi.agent.rpc.observations`. The observation channel limits nesting and
+collection sizes, hashes arbitrary strings, numbers, and identifiers, and does
+not retain prompts, paths, credentials, environment values, tool arguments, tool
+results, or Provider errors. Unknown events never establish success.
+
+`client.native()` returns a `PiNativeClient` that exposes the non-sensitive
+Runtime identity, observation subscription, and ownership-preserving read
+commands for an active Session. Arbitrary Run or Session mutation commands are
+rejected. A bounded correlation tombstone consumes a matching late response
+after a local read wait times out or is aborted; exhaustion closes the
+connection rather than accepting an unmatched response. Native access remains
+outside portable lifecycle and compatibility guarantees.
+
+## Evidence and limitations
+
+Evidence for this experimental Adapter includes:
+
+- deterministic synthetic completion, cancellation, failure, interaction, and
+  unknown-event fixtures in
+  [`fixtures/pi/rpc-current`](../../fixtures/pi/rpc-current/manifest.json);
+- mapping, ownership, resume, cancellation, retry, timeout, interaction,
+  disconnect, malformed-input, event-bound, process cleanup, version-probe,
+  native-access, and Provider-negative tests;
+- the shared portable Provider conformance suite;
+- an opt-in live lifecycle test for a host-installed Pi Runtime;
+- a trusted live-canary path that installs the current official release on an
+  ephemeral runner and exercises a completed text Run, streamed Events, the
+  authoritative terminal, persisted Session resume, native cancellation, Session
+  close, and Client disposal.
+
+The last repository-recorded live lifecycle run passed on 2026-09-03 with
+`@earendil-works/pi-coding-agent@0.84.4` in
+[Provider live canary run 33732602596](https://github.com/yunfeizhu/harapter/actions/runs/33732602596).
+It verified current-package installation, version probing, the model-facing CLI
+safety surface, RPC handshake, an exact completed text response, streamed
+`message.completed` and authoritative `run.completed` Events, persisted Session
+resume, correlated native cancellation with authoritative `run.cancelled`,
+Session close, Client disposal, isolated-state cleanup, and the absence of tool
+or interaction Events. It did not prove image or file input, extension UI
+interactions, or other capabilities outside that path. A production host may pin
+that release for reproducibility. Harapter continues to admit newer releases and
+validates their observed structures instead of using the recorded version as an
+executable allowlist. The Adapter remains experimental because the current RPC
+family does not negotiate a protocol version that can bind an arbitrary
+connected Runtime to this evidence before use.
+
+Run live verification only when two synthetic text Prompts, one completed model
+request, and one native cancellation attempt are acceptable to the host. The
+isolated config must define a `harapter-live` model and reference
+`HARAPTER_LIVE_MODEL_API_KEY` rather than storing the credential:
+
+```bash
+pi_live_home="$(mktemp -d)"
+trap 'rm -rf "$pi_live_home"' EXIT
+mkdir -p "$pi_live_home/sessions"
+
+HARAPTER_LIVE_MODEL_ID=... \
+HARAPTER_LIVE_MODEL_URL=https://model.example/v1 \
+node scripts/prepare-live-canary.mjs \
+  write-pi-config "$pi_live_home/config/models.json"
+
+PI_CODING_AGENT_DIR="$pi_live_home/config" \
+PI_CODING_AGENT_SESSION_DIR="$pi_live_home/sessions" \
+PI_OFFLINE=1 \
+PI_SKIP_VERSION_CHECK=1 \
+PI_TELEMETRY=0 \
+HARAPTER_LIVE_MODEL_API_KEY=... \
+HARAPTER_PI_LIVE=1 \
+HARAPTER_PI_COMMAND=/opt/harapter-runtimes/bin/pi \
+HARAPTER_PI_MODEL=... \
+pnpm vitest run providers/pi/test/live.test.ts
+```
+
+The live test requires the exact completed response, a completed message Event,
+and the authoritative completed Run Event. It resumes the same native Session,
+then requires a correlated native cancellation and authoritative cancelled Run.
+The Pi Runtime starts with tools, extensions, skills, prompt templates, and
+context-file discovery disabled; any tool or interaction Event fails the test.
+The test logs no Provider traffic and deletes its isolated Session state. A
+skipped or failed live test is not support evidence. Passing trusted manual and
+scheduled runs refresh evidence for the installed release without creating a
+version allowlist or changing the unnegotiated compatibility boundary.
+
+Image and file input, portable model selection, system-context overrides,
+generic approvals, per-Session Workspace selection, Runtime extension loading,
+skills, prompt templates, shared-process Session multiplexing, automatic process
+restart, Session-file access, arbitrary native mutations, and live authenticated
+extension-interaction evidence are outside the current compatibility boundary.

package/dist/adapter.d.ts

@@ -0,0 +1,40 @@
+import { type ProviderAdapterFactory, type ProviderSessionId } from '@harapter/core';
+/** Connection limits accepted in a Pi Profile's providerOptions. */
+export interface PiProfileOptions {
+    readonly cancelSettlementTimeoutMs?: number;
+    readonly maxBufferedMessages?: number;
+    readonly maxMessageBytes?: number;
+    readonly maxPendingInteractions?: number;
+    readonly maxPendingRequests?: number;
+    readonly maxPendingWrites?: number;
+    readonly maxRunEvents?: number;
+    readonly operationTimeoutMs?: number;
+    readonly persistSessions?: boolean;
+    readonly writeTimeoutMs?: number;
+}
+/** Provider extension for observing bounded, redacted Pi RPC messages. */
+export interface PiObservationExtension {
+    onObservation(listener: (event: unknown) => void): () => void;
+}
+/** Typed response accepted for a Pi extension UI interaction. */
+export type PiProviderInteractionResponse = Readonly<{
+    cancelled: true;
+}> | Readonly<{
+    confirmed: boolean;
+}> | Readonly<{
+    value: string;
+}>;
+/** Read-only Provider-native access that cannot mutate Session ownership. */
+export interface PiNativeClient {
+    readonly runtimeIdentity: string;
+    request<TResult = unknown>(sessionId: ProviderSessionId, command: Readonly<Record<string, unknown>> & {
+        readonly type: string;
+    }, options?: Readonly<{
+        signal?: AbortSignal;
+        timeoutMs?: number;
+    }>): Promise<TResult>;
+    onObservation(listener: (event: unknown) => void): () => void;
+}
+/** Create a fresh Pi Agent RPC Provider Adapter factory. */
+export declare function createPiProviderFactory(): ProviderAdapterFactory;
+//# sourceMappingURL=adapter.d.ts.map

package/dist/adapter.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"adapter.d.ts","sourceRoot":"","sources":["../src/adapter.ts"],"names":[],"mappings":"AAQA,OAAO,EAmBL,KAAK,sBAAsB,EAE3B,KAAK,iBAAiB,EAMvB,MAAM,gBAAgB,CAAC;AAoFxB,oEAAoE;AACpE,MAAM,WAAW,gBAAgB;IAC/B,QAAQ,CAAC,yBAAyB,CAAC,EAAE,MAAM,CAAC;IAC5C,QAAQ,CAAC,mBAAmB,CAAC,EAAE,MAAM,CAAC;IACtC,QAAQ,CAAC,eAAe,CAAC,EAAE,MAAM,CAAC;IAClC,QAAQ,CAAC,sBAAsB,CAAC,EAAE,MAAM,CAAC;IACzC,QAAQ,CAAC,kBAAkB,CAAC,EAAE,MAAM,CAAC;IACrC,QAAQ,CAAC,gBAAgB,CAAC,EAAE,MAAM,CAAC;IACnC,QAAQ,CAAC,YAAY,CAAC,EAAE,MAAM,CAAC;IAC/B,QAAQ,CAAC,kBAAkB,CAAC,EAAE,MAAM,CAAC;IACrC,QAAQ,CAAC,eAAe,CAAC,EAAE,OAAO,CAAC;IACnC,QAAQ,CAAC,cAAc,CAAC,EAAE,MAAM,CAAC;CAClC;AAED,0EAA0E;AAC1E,MAAM,WAAW,sBAAsB;IACrC,aAAa,CAAC,QAAQ,EAAE,CAAC,KAAK,EAAE,OAAO,KAAK,IAAI,GAAG,MAAM,IAAI,CAAC;CAC/D;AAED,iEAAiE;AACjE,MAAM,MAAM,6BAA6B,GACrC,QAAQ,CAAC;IAAE,SAAS,EAAE,IAAI,CAAA;CAAE,CAAC,GAC7B,QAAQ,CAAC;IAAE,SAAS,EAAE,OAAO,CAAA;CAAE,CAAC,GAChC,QAAQ,CAAC;IAAE,KAAK,EAAE,MAAM,CAAA;CAAE,CAAC,CAAC;AAEhC,6EAA6E;AAC7E,MAAM,WAAW,cAAc;IAC7B,QAAQ,CAAC,eAAe,EAAE,MAAM,CAAC;IACjC,OAAO,CAAC,OAAO,GAAG,OAAO,EACvB,SAAS,EAAE,iBAAiB,EAC5B,OAAO,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC,GAAG;QAAE,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAA;KAAE,EACtE,OAAO,CAAC,EAAE,QAAQ,CAAC;QAAE,MAAM,CAAC,EAAE,WAAW,CAAC;QAAC,SAAS,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC,GAC/D,OAAO,CAAC,OAAO,CAAC,CAAC;IACpB,aAAa,CAAC,QAAQ,EAAE,CAAC,KAAK,EAAE,OAAO,KAAK,IAAI,GAAG,MAAM,IAAI,CAAC;CAC/D;AAyCD,4DAA4D;AAC5D,wBAAgB,uBAAuB,IAAI,sBAAsB,CAQhE"}