@harapter/adapter-hermes 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,225 @@
+# `@harapter/adapter-hermes`
+
+`@harapter/adapter-hermes` maps the official Hermes Agent API Server HTTP and
+Server-Sent Events interface to the portable Harapter lifecycle.
+
+The host installs, configures, authenticates, starts, and stops Hermes Agent.
+The Adapter connects only to a host-selected endpoint. It does not install the
+Hermes Agent Runtime or SDK, start a server, configure models or tools, or own
+the host security policy.
+
+## Installation
+
+```bash
+pnpm add @harapter/core@next @harapter/adapter-hermes@next
+```
+
+## Runtime prerequisites and compatibility
+
+The Adapter targets the current documented API Server interface. Connection
+requires a valid `GET /v1/capabilities` document with the Session creation,
+Session lookup, Run submission, Run status, and Run event routes used by the
+Adapter. Stop and approval support are declared only when the connected server
+advertises the corresponding feature and exact route.
+
+Every response and SSE event used for portable lifecycle authority is
+structurally validated. A stable diagnostic fingerprint is derived from the
+validated capability subset. Harapter does not pin the Hermes executable to a
+release number or use its identity to infer capabilities. Incompatible current
+or future response shapes fail closed at the boundary where they are used.
+
+The fixture manifest records the upstream source revision inspected for the
+evidence baseline. That revision is provenance, not a runtime allowlist. Hermes
+Agent is MIT licensed; Harapter does not redistribute it. See the
+[license record](../../licenses/hermes-agent.md).
+
+The latest trusted live validation ran on 2026-09-03 against
+`hermes-agent@0.21.0` from
+`nousresearch/hermes-agent@sha256:023d61b3ec803093827e10999e54abdbd379d1ed6adba59b45a6b89c1b4233b8`.
+The [passing workflow run][hermes-live-2026-09-03] verified an exact completed
+text response with `run.started`, `message.completed`, and authoritative
+`run.completed` Events. It then closed the first local handle, resumed the same
+native Session, and verified native cancellation of a second Run with an
+authoritative `run.cancelled` terminal. Both local Session handles and the
+Client were disposed, and no model-facing toolset was enabled. The API Server
+does not negotiate a Runtime compatibility version, so the Adapter remains
+`experimental`. Harapter attempts other Runtime releases and rejects
+incompatible response or event shapes when they are used; it does not reject a
+release by version number alone.
+
+[hermes-live-2026-09-03]:
+  https://github.com/yunfeizhu/harapter/actions/runs/33737478620
+
+## Profile and authentication
+
+Hermes Agent uses an `endpoint` Profile with HTTP transport and host or external
+ownership:
+
+```ts
+import { HarnessRegistry, profileId } from '@harapter/core';
+import {
+  HERMES_PROVIDER_ID,
+  createHermesProviderFactory,
+} from '@harapter/adapter-hermes';
+
+const registry = new HarnessRegistry();
+registry.register(
+  createHermesProviderFactory({
+    resolveAuthHeaders: async (reference) => headersFor(reference),
+  }),
+);
+
+const client = await registry.connect({
+  profileId: profileId('hermes-local'),
+  providerId: HERMES_PROVIDER_ID,
+  displayName: 'Hermes Agent',
+  connection: {
+    kind: 'endpoint',
+    url: 'http://127.0.0.1:8642/',
+    transport: 'http',
+    ownership: 'host',
+    authRef: { scheme: 'host-secret-store', id: 'hermes-api-key' },
+  },
+});
+```
+
+`authRef` is optional. When it is present, the host must provide
+`resolveAuthHeaders`. Harapter does not resolve, log, persist, or expose the
+header values.
+
+Profile `providerOptions` accepts positive bounded values for
+`requestTimeoutMs`, `sseConnectTimeoutMs`, `reconcileTimeoutMs`,
+`reconcilePollIntervalMs`, `cancelSettlementTimeoutMs`,
+`lateEventDrainTimeoutMs`, and `maxRunEvents`. Unknown options are rejected.
+`maxRunEvents` must be between 2 and 4096 so the unread event queue always
+reserves terminal capacity.
+
+## Session and Run lifecycle
+
+`createSession()` uses the documented Session creation route. Portable system
+context and model selection are sent at creation and retained as bounded,
+non-secret provider state. Native model settings use
+`model.providerOptions.provider` and `model.providerOptions.modelOptions`;
+credential-shaped option keys are rejected. Native `modelOptions` are applied to
+the creating Session handle but omitted from `SessionRef.providerState`; a
+resumed handle relies on the native Hermes Session state.
+
+`resumeSession()` validates the Provider, Profile, compatibility reference,
+native Session identifier, retained state, and remote Session response before
+returning a handle. Session state is bound to the connection Profile that
+created it and does not imply checkpoint portability. Portable workspace
+selection is unsupported. `session.close()` releases the local handle and aborts
+active local observation; it does not delete the upstream Session.
+
+One Run may be active per Session. Portable Runs accept text parts only. Run
+submission returns an acknowledgement. Before opening SSE, the Adapter validates
+that the acknowledged Run status belongs to the submitting Session. It then
+consumes the bounded stream and reconciles lifecycle evidence against
+`GET /v1/runs/{run_id}`. Non-empty Session, input, and Run metadata are rejected
+because the current API mapping has no documented portable destination for them.
+The status route is the terminal authority:
+
+- `completed` maps to `run.completed` only with matching Run and Session
+  ownership plus `last_event: "run.completed"`;
+- `failed` maps to `run.failed` without exposing the Provider failure body;
+- `cancelled` maps to `run.cancelled` only from authoritative Provider status;
+- `queued`, `running`, `waiting_for_approval`, and `stopping` remain
+  nonterminal;
+- SSE EOF, disconnect, malformed data, duplicate terminals, or contradictory
+  evidence never become success.
+
+After terminal evidence, the Adapter drains only for a bounded interval to
+detect contradictory or duplicate lifecycle events. A terminal portable event is
+always the last event in the parent Run trace. Malformed or uncertain settlement
+quarantines the Session handle within the Client until the host performs
+explicit recovery through a new connection.
+
+Run submission, stop, and approval are non-idempotent mutations. A malformed
+success response, server failure, response loss, or ownership mismatch after
+possible execution quarantines the affected Session instead of reopening it for
+an unsafe retry.
+
+## Stop, timeout, and approval
+
+When the capability handshake advertises the official stop route, `run.cancel()`
+posts to it. A `stopping` response is only an acknowledgement; Harapter reports
+native cancellation after authoritative `cancelled` evidence. If settlement
+remains uncertain, the result is `connection_aborted`, not `run.cancelled`.
+Without the advertised route, portable cancellation is unsupported.
+
+A positive `RunOptions.timeoutMs` uses native stop when available. Otherwise it
+aborts only the Adapter connection. Client close, Session close, HTTP abort, and
+SSE loss are connection lifecycle events and never proof of native cancellation.
+
+Advertised approval requests map to portable approval interactions. Approval
+supports `once`, `session`, and `always`; denial maps to `deny`. Overlapping
+requests, an approval event without advertised support, or a mismatched
+acknowledgement fails closed. Matching HTTP acknowledgement and SSE resolution
+evidence is accepted in either arrival order and produces one portable
+resolution.
+
+## Events, extensions, and native access
+
+Message deltas, Tool lifecycle, reasoning, usage, approval, and terminal events
+map to portable events. Unknown upstream events remain observable through a
+bounded, content-free `provider` event and
+`HermesNativeClient.onUnknownEvent()`. Raw observation limits depth, node count,
+array length, and object fields; arbitrary scalar content and unknown fields are
+not exposed.
+
+`nous.hermes-agent.subagents` is a typed observer for bounded child-Session
+events. The current capability document does not advertise this event family, so
+its capability status remains `unknown`. A child event received before the
+parent terminal boundary can also appear as a parent Provider event. A late
+child event is delivered only to the extension and cannot append to, delay, or
+rewrite the terminated parent Run.
+
+`client.native()` returns a `HermesNativeClient` with endpoint-bound JSON
+requests, the non-sensitive compatibility identity, and unknown-event
+observation. Native requests remain Provider-specific and do not gain portable
+ordering, ownership, lifecycle, redaction, or authorization guarantees.
+
+## Evidence and limitations
+
+Evidence for this experimental Adapter includes:
+
+- deterministic synthetic capability, completed, failed, cancelled, approval,
+  late-child, and unknown-event fixtures in
+  [`fixtures/hermes/api-server-current`](../../fixtures/hermes/api-server-current/manifest.json);
+- mapping, ownership, malformed-input, authentication, timeout, stop,
+  disconnect, terminal reconciliation, event-bound, approval, observer, and
+  native-access tests;
+- the shared portable Provider conformance suite;
+- an opt-in live-runtime test for a host-operated endpoint;
+- a trusted live-canary path that pulls the current official container, records
+  its package version and immutable image digest, and exercises Session, Run,
+  SSE, terminal-result, and disposal behavior.
+
+Run live verification only against an isolated endpoint whose work and cost are
+acceptable to the host:
+
+```bash
+HARAPTER_HERMES_LIVE=1 \
+HARAPTER_HERMES_ENDPOINT=http://127.0.0.1:8642/ \
+pnpm vitest run providers/hermes/test/live.test.ts
+```
+
+Set `HARAPTER_HERMES_API_KEY` when the endpoint requires bearer authentication.
+The live test logs no Provider traffic. A skipped or unrecorded live test is not
+support evidence.
+
+The repository live canary mounts only an isolated temporary data directory and
+publishes the API Server on host loopback. It disables bundled skills, plugins,
+MCP servers, memory, compression, checkpoints, title generation, background
+review, and every API Server toolset. An authenticated toolset inventory must
+confirm that every configurable toolset is disabled, and the Runtime's full
+Agent-side resolver must return no enabled toolsets, before the canary submits
+two synthetic Prompts. The first requires one exact text response and validates
+the completed lifecycle. After closing and resuming the same native Session, the
+second requests a deliberately long response so the canary can require native
+cancellation and an authoritative cancelled terminal. The weekly schedule is
+enabled after the passing manual run recorded above.
+
+Portable workspace selection, file and image input, Server lifecycle, Session
+deletion, automatic SSE reconnection, and strict child-Session capability claims
+are outside the current compatibility boundary.

package/dist/adapter.d.ts

@@ -0,0 +1,39 @@
+import { type ProviderAdapterFactory, type SecretRef } from '@harapter/core';
+import { type HttpHeaderMap, type HttpMethod } from '@harapter/transport-http-sse';
+import { type HermesRawEvent } from './protocol.js';
+/** Host integrations available while creating a Hermes Adapter. */
+export interface HermesProviderFactoryOptions {
+    readonly fetch?: typeof fetch;
+    readonly resolveAuthHeaders?: (reference: SecretRef) => Promise<HttpHeaderMap> | HttpHeaderMap;
+}
+/** Supported bounded controls in a Hermes Profile providerOptions object. */
+export interface HermesProfileOptions {
+    readonly cancelSettlementTimeoutMs?: number;
+    readonly lateEventDrainTimeoutMs?: number;
+    readonly maxRunEvents?: number;
+    readonly reconcilePollIntervalMs?: number;
+    readonly reconcileTimeoutMs?: number;
+    readonly requestTimeoutMs?: number;
+    readonly sseConnectTimeoutMs?: number;
+}
+/** Options for an explicit Provider-native bounded request. */
+export interface HermesNativeRequestOptions {
+    readonly body?: unknown;
+    readonly method?: HttpMethod;
+    readonly signal?: AbortSignal;
+    readonly timeoutMs?: number;
+}
+/** Bounded JSON response returned by the native HTTP escape hatch. */
+export interface HermesNativeResponse<T = unknown> {
+    readonly body: T;
+    readonly status: number;
+}
+/** Provider-bound access to the official API Server HTTP surface. */
+export interface HermesNativeClient {
+    readonly runtimeIdentity: string;
+    request<T = unknown>(path: string, options?: HermesNativeRequestOptions): Promise<HermesNativeResponse<T>>;
+    onUnknownEvent(listener: (event: HermesRawEvent) => void): () => void;
+}
+/** Create a fresh Hermes Agent API Server Adapter factory. */
+export declare function createHermesProviderFactory(options?: HermesProviderFactoryOptions): 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":"AAAA,OAAO,EAmBL,KAAK,sBAAsB,EAM3B,KAAK,SAAS,EAEf,MAAM,gBAAgB,CAAC;AACxB,OAAO,EAGL,KAAK,aAAa,EAClB,KAAK,UAAU,EAIhB,MAAM,8BAA8B,CAAC;AAEtC,OAAO,EAkBL,KAAK,cAAc,EAIpB,MAAM,eAAe,CAAC;AA2BvB,mEAAmE;AACnE,MAAM,WAAW,4BAA4B;IAC3C,QAAQ,CAAC,KAAK,CAAC,EAAE,OAAO,KAAK,CAAC;IAC9B,QAAQ,CAAC,kBAAkB,CAAC,EAAE,CAC5B,SAAS,EAAE,SAAS,KACjB,OAAO,CAAC,aAAa,CAAC,GAAG,aAAa,CAAC;CAC7C;AAED,6EAA6E;AAC7E,MAAM,WAAW,oBAAoB;IACnC,QAAQ,CAAC,yBAAyB,CAAC,EAAE,MAAM,CAAC;IAC5C,QAAQ,CAAC,uBAAuB,CAAC,EAAE,MAAM,CAAC;IAC1C,QAAQ,CAAC,YAAY,CAAC,EAAE,MAAM,CAAC;IAC/B,QAAQ,CAAC,uBAAuB,CAAC,EAAE,MAAM,CAAC;IAC1C,QAAQ,CAAC,kBAAkB,CAAC,EAAE,MAAM,CAAC;IACrC,QAAQ,CAAC,gBAAgB,CAAC,EAAE,MAAM,CAAC;IACnC,QAAQ,CAAC,mBAAmB,CAAC,EAAE,MAAM,CAAC;CACvC;AAED,+DAA+D;AAC/D,MAAM,WAAW,0BAA0B;IACzC,QAAQ,CAAC,IAAI,CAAC,EAAE,OAAO,CAAC;IACxB,QAAQ,CAAC,MAAM,CAAC,EAAE,UAAU,CAAC;IAC7B,QAAQ,CAAC,MAAM,CAAC,EAAE,WAAW,CAAC;IAC9B,QAAQ,CAAC,SAAS,CAAC,EAAE,MAAM,CAAC;CAC7B;AAED,sEAAsE;AACtE,MAAM,WAAW,oBAAoB,CAAC,CAAC,GAAG,OAAO;IAC/C,QAAQ,CAAC,IAAI,EAAE,CAAC,CAAC;IACjB,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;CACzB;AAED,qEAAqE;AACrE,MAAM,WAAW,kBAAkB;IACjC,QAAQ,CAAC,eAAe,EAAE,MAAM,CAAC;IACjC,OAAO,CAAC,CAAC,GAAG,OAAO,EACjB,IAAI,EAAE,MAAM,EACZ,OAAO,CAAC,EAAE,0BAA0B,GACnC,OAAO,CAAC,oBAAoB,CAAC,CAAC,CAAC,CAAC,CAAC;IACpC,cAAc,CAAC,QAAQ,EAAE,CAAC,KAAK,EAAE,cAAc,KAAK,IAAI,GAAG,MAAM,IAAI,CAAC;CACvE;AA0BD,8DAA8D;AAC9D,wBAAgB,2BAA2B,CACzC,OAAO,GAAE,4BAAiC,GACzC,sBAAsB,CAQxB"}