@taco-ai/pi-harness 0.0.0-stage → 0.1.0

package/LICENSE

@@ -0,0 +1,26 @@
+MIT License
+
+Copyright (c) 2025 Mario Zechner
+Copyright (c) 2026 NiumAgents
+
+This package contains code extracted from Earendil Works `pi`
+(`@earendil-works/pi-agent-core` 0.99.2). The upstream license is
+reproduced in `LICENSE.upstream`.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/LICENSE.upstream

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Mario Zechner
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,3 +1,171 @@
-# Temporary Holding Version
+# @taco-ai/pi-harness
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+English | [简体中文](./README.zh-CN.md)
+
+The experimental **AgentHarness** that Pi 1.0 deleted from `@earendil-works/pi-agent-core`,
+extracted into its own package so consumers can keep the 0.99.2 harness and JSONL session
+line while running on the **latest** pi base packages.
+
+> **This is not an official Earendil Works package.**
+
+## Why this package exists
+
+Pi 1.0 deleted the harness and replaced it with `@earendil-works/pi-durable`. But `pi-durable`
+is still marked unstable — its API can and does change between releases. So an application
+that wants to leave the 0.99.2 harness line has nothing stable to move to *yet*.
+
+This package is the bridge for that gap. It keeps the old surface running on **current** base
+packages, so migrating to `pi-durable` is a step you schedule, not a step you are forced into
+by an upstream deletion. Until `pi-durable` drops its unstable marker and becomes a stable API,
+this package is maintained: broken builds against new base packages get fixed, and the session
+format stays byte-compatible so nothing on disk has to be rewritten.
+
+**This package is expected to be retired once `pi-durable` is stable.** It is a compatibility
+line with a sunset condition, not a long-term fork. When `pi-durable` settles, consumers should
+move to it, and this package should stop taking new work.
+
+## Quick start
+
+Requires Node.js **22.19+**. The package is ESM-only, and the pi base packages are peers, so
+your application must provide them. Once the first release is published:
+
+```bash
+pnpm add @taco-ai/pi-harness
+```
+
+Until then, build it from a checkout and consume it as a workspace or path dependency:
+
+```bash
+pnpm install
+pnpm build
+```
+
+Switching over is an import rewrite. The harness takes a pi-ai `Models` instance and a model:
+
+```ts
+import { createModels } from "@earendil-works/pi-ai"; // register your provider(s) here
+import { AgentHarness, BACKGROUND_CONTEXT } from "@taco-ai/pi-harness";
+import { NodeExecutionEnv } from "@taco-ai/pi-harness/harness/env/nodejs";
+import { JsonlSessionRepo } from "@taco-ai/pi-harness/harness/session";
+
+const models = createModels(); // your app's configured Models instance
+const model = models.getModel("anthropic", "claude-opus-4-7");
+if (!model) throw new Error("configure a provider and model first");
+
+const fileSystem = new NodeExecutionEnv({ cwd: process.cwd() });
+const repo = new JsonlSessionRepo({ fileSystem, sessionsRoot: ".sessions" });
+const session = await repo.create({ cwd: process.cwd() }, BACKGROUND_CONTEXT);
+
+const { harness } = await AgentHarness.create({ session, models, model }, BACKGROUND_CONTEXT);
+const lane = await harness.lane("main", BACKGROUND_CONTEXT);
+await lane.prompt("Hello", undefined, BACKGROUND_CONTEXT);
+```
+
+## Provenance
+
+Extracted from [`earendil-works/pi`](https://github.com/earendil-works/pi) at **tag `v0.99.2`**,
+package `@earendil-works/pi-agent-core` (`packages/agent`). Upstream is MIT, © Mario Zechner —
+see `LICENSE.upstream`. The vendored shims are marked in `src/shims/`.
+
+Pi 1.0 removed `AgentHarness`, the session/storage layer, compaction, skills, prompt templates
+and the whole `./harness/*` surface from `pi-agent-core`, replacing them with `pi-durable`.
+This package keeps the old surface alive without depending on a dead version.
+
+## What is in scope
+
+| Content | In this package |
+|---|---|
+| `AgentHarness`, agent loop, lanes, hooks | yes |
+| `JsonlSessionRepo` and the session/storage layer | yes |
+| Compaction, branch summarization | yes |
+| Skills, prompt templates, tools (`read`/`write`/`edit`) | yes |
+| Telemetry spans and schemas — see [`docs/telemetry-schema.md`](./docs/telemetry-schema.md) | yes |
+| `NodeExecutionEnv` and the other execution envs | yes |
+| pico3 (the experimental harness) | yes |
+| Your own session/permission/protocol layer | no — keep it in your app |
+
+The export map mirrors the old `pi-agent-core` subpaths one-for-one (`.`, `./node`,
+`./harness/context`, `./harness/session`, `./harness/env/nodejs`,
+`./harness/runtime/reducer`, `./harness/session/testing`, `./experimental/pico3`) so switching
+over is an import rewrite, not a redesign.
+
+## Dependencies
+
+The pi base packages are **peer** dependencies, pinned to the latest line:
+
+```jsonc
+"peerDependencies": {
+  "@earendil-works/pi-ai": "^1.3.0",
+  "@earendil-works/chord": "^1.3.0",
+  "@earendil-works/pi-telemetry": "^1.3.0"
+}
+```
+
+There is deliberately **no** dependency on `@earendil-works/pi-agent-core` (any version — 1.x
+has no harness) and none on `@earendil-works/pi-durable` (a separate migration track).
+
+What is frozen here is the **harness/session API and the JSONL format**. The **model stack
+tracks upstream**, so new models, auth fixes and provider fixes arrive by bumping the peers.
+
+## Vendored shims
+
+Two upstream APIs this harness needs were removed from the base packages. Both are vendored
+under `src/shims/` — verbatim except for their imports — rather than pinning the package to an
+old base version:
+
+| Shim | Removed from | Why it is safe to vendor |
+|---|---|---|
+| `assistant-message-frame.ts` | `pi-ai@1.3.0` | `AssistantMessageFrame`, `AssistantMessageFrameEncoder` and `reduceAssistantMessageFrames` were removed as "unused" *because* the harness was being deleted. The frames are part of the on-disk session format, so reimplementing them would break session compatibility. Frozen on purpose. |
+| `define-service.ts` | `chord@1.x` | Chord dropped the whole facet/service subsystem. `defineService` was a frozen identity descriptor (`Object.freeze({ id, local })`) with no runtime coupling to the chord kernel, and nothing in this package hands a descriptor to a chord host. The new `Service` in `chord/object` is a different concept and is not a drop-in replacement. |
+
+Both shims are marked with the upstream version they came from and a note not to "fix them up".
+
+## Session compatibility
+
+The JSONL session format is **byte-compatible with 0.99.2**. Existing session directories open
+and continue without migration. `test/harness/memory-conformance.test.ts` is the conformance
+gate; run it with:
+
+```bash
+pnpm run test:session:conformance
+```
+
+## Maintenance rules
+
+- **Fix breakage, do not chase features.** Compile and runtime fixes against new base-package
+  versions are in scope. Porting harness features from `pi-durable` is not.
+- **Do not unfreeze the shims.** Session compatibility depends on them.
+- **Sunset condition:** maintain until `@earendil-works/pi-durable` removes its unstable marker
+  and becomes a stable API. After that this line takes no new work — the migration target has
+  arrived and consumers should be on it.
+
+## Development
+
+```bash
+pnpm install
+pnpm build                              # tsc -p tsconfig.build.json
+pnpm test                               # full suite (878 tests)
+pnpm test:harness                       # harness suite (788 tests)
+pnpm run test:session:conformance       # JSONL conformance gate
+pnpm docs:telemetry                     # regenerate docs/telemetry-schema.md
+pnpm docs:telemetry:check               # fail if the generated doc is stale
+```
+
+Tests resolve `@earendil-works/pi-ai`, `chord` and `pi-telemetry` from `node_modules` — the
+published 1.x builds, not sibling monorepo source. That is the point of the package: the suite
+is the evidence that the frozen harness runs against the latest base packages.
+
+`docs/telemetry-schema.md` is generated from the exported telemetry schemas. Regenerate it with
+`pnpm docs:telemetry` instead of editing it by hand; `docs:telemetry:check` verifies that the
+checked-in copy is current. `docs/` ships in the published tarball.
+
+## License
+
+MIT. See `LICENSE` (this package) and `LICENSE.upstream` (the original Earendil Works terms).
+
+[`earendil-works/pi`](https://github.com/earendil-works/pi) is MIT © Mario Zechner.
+
+## Contributing
+
+Security-sensitive reports are best sent privately to `niuma1024@outlook.com`. Everything
+else — bugs, ideas, questions — is welcome as a GitHub issue.

package/README.zh-CN.md

@@ -0,0 +1,165 @@
+# @taco-ai/pi-harness
+
+[English](./README.md) | 简体中文
+
+把 Pi 1.0 从 `@earendil-works/pi-agent-core` 中删除的实验性 **AgentHarness** 抽取为独立包，
+让使用方在运行 **最新版** pi 基础包的同时，保留 0.99.2 的 harness 与 JSONL 会话线。
+
+> **本包不是 Earendil Works 官方包。**
+
+## 为什么需要这个包
+
+Pi 1.0 删掉了 harness，改由 `@earendil-works/pi-durable` 取代。但 `pi-durable` 目前仍标记为
+不稳定 —— 它的 API 会在版本之间发生变动。想要离开 0.99.2 harness 线的应用，眼下**没有**
+一个稳定的目标可以迁移过去。
+
+本包就是为这段空窗期准备的过渡层：让旧接口继续跑在**当前**基础包上，使迁移到
+`pi-durable` 成为一件你可以排期去做的事，而不是被上游删除逼着立刻做的事。在
+`pi-durable` 去掉不稳定标记、转为稳定 API 之前，本包会持续维护：针对新基础包的构建失败
+会被修复，会话格式保持逐字节兼容，磁盘上的会话不需要重写。
+
+**预期在 `pi-durable` 稳定之后本包即行退出。** 这是一条带退出条件的兼容性线，而不是一个
+长期 fork。当 `pi-durable` 稳定下来，使用方应当迁移过去，本包也应停止接受新工作。
+
+## 快速开始
+
+需要 Node.js **22.19+**。本包仅支持 ESM；pi 基础包是 peer 依赖，需要由你的应用提供。
+首个版本发布后可直接安装：
+
+```bash
+pnpm add @taco-ai/pi-harness
+```
+
+在此之前，请在本地检出并构建，再以 workspace 或 path 依赖的方式引入：
+
+```bash
+pnpm install
+pnpm build
+```
+
+切换过来本质上只是改 import。harness 接收 pi-ai `Models` 实例和模型：
+
+```ts
+import { createModels } from "@earendil-works/pi-ai"; // 在这里注册你的 provider
+import { AgentHarness, BACKGROUND_CONTEXT } from "@taco-ai/pi-harness";
+import { NodeExecutionEnv } from "@taco-ai/pi-harness/harness/env/nodejs";
+import { JsonlSessionRepo } from "@taco-ai/pi-harness/harness/session";
+
+const models = createModels(); // 你应用里已配置好的 Models 实例
+const model = models.getModel("anthropic", "claude-opus-4-7");
+if (!model) throw new Error("请先配置 provider 与模型");
+
+const fileSystem = new NodeExecutionEnv({ cwd: process.cwd() });
+const repo = new JsonlSessionRepo({ fileSystem, sessionsRoot: ".sessions" });
+const session = await repo.create({ cwd: process.cwd() }, BACKGROUND_CONTEXT);
+
+const { harness } = await AgentHarness.create({ session, models, model }, BACKGROUND_CONTEXT);
+const lane = await harness.lane("main", BACKGROUND_CONTEXT);
+await lane.prompt("Hello", undefined, BACKGROUND_CONTEXT);
+```
+
+## 来源
+
+抽取自 [`earendil-works/pi`](https://github.com/earendil-works/pi) 的 **`v0.99.2`** 标签，
+对应包为 `@earendil-works/pi-agent-core`（`packages/agent`）。上游为 MIT，© Mario Zechner ——
+见 `LICENSE.upstream`。内置的 shim 在 `src/shims/` 中有标注。
+
+Pi 1.0 从 `pi-agent-core` 中移除了 `AgentHarness`、session/storage 层、compaction、skills、
+prompt templates 以及整个 `./harness/*` 接口，改由 `pi-durable` 取代。本包在不依赖已停更
+版本的前提下，让旧接口继续可用。
+
+## 收录范围
+
+| 内容 | 是否在本包中 |
+|---|---|
+| `AgentHarness`、agent loop、lanes、hooks | 是 |
+| `JsonlSessionRepo` 及 session/storage 层 | 是 |
+| Compaction、branch summarization | 是 |
+| Skills、prompt templates、工具（`read`/`write`/`edit`） | 是 |
+| Telemetry span 与 schema —— 见 [`docs/telemetry-schema.md`](./docs/telemetry-schema.md) | 是 |
+| `NodeExecutionEnv` 及其他 execution env | 是 |
+| pico3（实验性 harness） | 是 |
+| 你自己的 session/permission/protocol 层 | 否 —— 留在你的应用里 |
+
+导出映射与旧 `pi-agent-core` 的子路径一一对应（`.`、`./node`、`./harness/context`、
+`./harness/session`、`./harness/env/nodejs`、`./harness/runtime/reducer`、
+`./harness/session/testing`、`./experimental/pico3`），因此切换过来只是改 import，
+不需要重新设计。
+
+## 依赖
+
+pi 基础包是 **peer** 依赖，固定在最新版本线上：
+
+```jsonc
+"peerDependencies": {
+  "@earendil-works/pi-ai": "^1.3.0",
+  "@earendil-works/chord": "^1.3.0",
+  "@earendil-works/pi-telemetry": "^1.3.0"
+}
+```
+
+刻意**不**依赖 `@earendil-works/pi-agent-core`（任何版本都不依赖 —— 1.x 已无 harness），
+也**不**依赖 `@earendil-works/pi-durable`（那是另一条迁移路线）。
+
+这里冻结的是 **harness/session API 与 JSONL 格式**。**模型栈跟随上游**，所以新模型、
+鉴权修复和 provider 修复通过升级 peer 即可获得。
+
+## 内置 shim
+
+harness 需要的两个上游 API 已从基础包中移除。两者都内置在 `src/shims/` 下 —— 除 import
+外保持原样 —— 而不是把整个包固定在旧的基础包版本上：
+
+| Shim | 移除自 | 为什么内置是安全的 |
+|---|---|---|
+| `assistant-message-frame.ts` | `pi-ai@1.3.0` | `AssistantMessageFrame`、`AssistantMessageFrameEncoder` 和 `reduceAssistantMessageFrames` 被以「未使用」为由移除 —— 原因正是 harness 正在被删除。这些 frame 是磁盘会话格式的一部分，重新实现会破坏会话兼容性。属于有意冻结。 |
+| `define-service.ts` | `chord@1.x` | Chord 整个丢弃了 facet/service 子系统。`defineService` 原是一个冻结的身份描述符（`Object.freeze({ id, local })`），与 chord 内核没有运行时耦合，本包也没有任何地方把描述符交给 chord host。`chord/object` 中的新 `Service` 是另一个概念，不能作为直接替代。 |
+
+两个 shim 都标注了它们来自哪个上游版本，并注明不要「顺手修好」它们。
+
+## 会话兼容性
+
+JSONL 会话格式与 0.99.2 **逐字节兼容**。既有会话目录可直接打开并继续使用，无需迁移。
+`test/harness/memory-conformance.test.ts` 是一致性校验，运行方式：
+
+```bash
+pnpm run test:session:conformance
+```
+
+## 维护规则
+
+- **只修破坏性问题，不追新功能。** 针对新基础包版本的编译与运行时修复在范围内；
+  从 `pi-durable` 移植 harness 功能不在范围内。
+- **不要解冻 shim。** 会话兼容性依赖它们。
+- **退出条件：** 维护到 `@earendil-works/pi-durable` 去掉不稳定标记、API 转为稳定为止。
+  之后这条线不再接受新工作 —— 迁移目标已经就位，使用方应当迁移过去。
+
+## 开发
+
+```bash
+pnpm install
+pnpm build                              # tsc -p tsconfig.build.json
+pnpm test                               # 全量测试（878 个）
+pnpm test:harness                       # harness 测试（788 个）
+pnpm run test:session:conformance       # JSONL 一致性校验
+pnpm docs:telemetry                     # 重新生成 docs/telemetry-schema.md
+pnpm docs:telemetry:check               # 检查生成文档是否已过期
+```
+
+测试从 `node_modules` 解析 `@earendil-works/pi-ai`、`chord` 和 `pi-telemetry` ——
+用的是已发布的 1.x 构建，而不是同仓库 monorepo 的源码。这正是本包的要点：
+测试套件就是「冻结的 harness 能跑在最新基础包上」的证据。
+
+`docs/telemetry-schema.md` 由导出的 telemetry schema 生成，请用 `pnpm docs:telemetry`
+重新生成，不要手工编辑；`docs:telemetry:check` 会校验仓库内的副本是否最新。`docs/` 会随
+npm 包一起分发。
+
+## 许可证
+
+MIT。见 `LICENSE`（本包）与 `LICENSE.upstream`（Earendil Works 原始条款）。
+
+[`earendil-works/pi`](https://github.com/earendil-works/pi) 为 MIT © Mario Zechner。
+
+## 参与贡献
+
+安全相关的报告，建议私下发送至 `niuma1024@outlook.com`。其余问题 —— bug、想法、
+疑问 —— 欢迎提 GitHub issue。

package/dist/agent-loop.d.ts

@@ -0,0 +1,49 @@
+/**
+ * Agent loop that works with AgentMessage throughout.
+ * Transforms to Message[] only at the LLM call boundary.
+ */
+import { type AssistantMessage, EventStream } from "@earendil-works/pi-ai";
+import type { AgentContext, AgentEvent, AgentLoopConfig, AgentMessage, AgentTool, AgentToolCall, AgentToolCallOutcome, AgentToolResult, StreamFn } from "./types.ts";
+export type AgentEventSink = (event: AgentEvent) => Promise<void> | void;
+/**
+ * Start an agent loop with a new prompt message.
+ * The prompt is added to the context and events are emitted for it.
+ */
+export declare function agentLoop(prompts: AgentMessage[], context: AgentContext, config: AgentLoopConfig, signal: AbortSignal | undefined, streamFn: StreamFn): EventStream<AgentEvent, AgentMessage[]>;
+/**
+ * Continue an agent loop from the current context without adding a new message.
+ * Used for retries - context already has user message or tool results.
+ *
+ * **Important:** The last message in context must convert to a `user` or `toolResult` message
+ * via `convertToLlm`. If it doesn't, the LLM provider will reject the request.
+ * This cannot be validated here since `convertToLlm` is only called once per turn.
+ */
+export declare function agentLoopContinue(context: AgentContext, config: AgentLoopConfig, signal: AbortSignal | undefined, streamFn: StreamFn): EventStream<AgentEvent, AgentMessage[]>;
+export declare function runAgentLoop(prompts: AgentMessage[], context: AgentContext, config: AgentLoopConfig, emit: AgentEventSink, signal: AbortSignal | undefined, streamFn: StreamFn): Promise<AgentMessage[]>;
+export declare function runAgentLoopContinue(context: AgentContext, config: AgentLoopConfig, emit: AgentEventSink, signal: AbortSignal | undefined, streamFn: StreamFn): Promise<AgentMessage[]>;
+/** The `beforeToolCall` and `afterToolCall` hooks of {@link AgentLoopConfig}. */
+export type ToolCallHooks = Pick<AgentLoopConfig, "beforeToolCall" | "afterToolCall">;
+type ToolUpdateSink = (partialResult: AgentToolResult<any>) => Promise<void> | void;
+/** Options for {@link runToolCall}. */
+export interface RunToolCallOptions extends ToolCallHooks {
+    /** Tools the call resolves against. */
+    tools: readonly AgentTool<any>[];
+    /** Passed to the hooks as the message that issued the call. */
+    assistantMessage: AssistantMessage;
+    /** Passed to the hooks as the current agent context. */
+    context: AgentContext;
+    signal?: AbortSignal;
+    onUpdate?: ToolUpdateSink;
+}
+/**
+ * Run one tool call through the same steps as a model-issued call: argument preparation, schema
+ * validation, `beforeToolCall`, execution, and `afterToolCall`. Emits no events and adds no
+ * messages. Tools that call other tools use this so the hooks (for example permission checks)
+ * apply to those calls too.
+ *
+ * Never rejects for tool failures: unknown tools, validation errors, blocked calls, and thrown
+ * errors come back as `isError: true`.
+ */
+export declare function runToolCall(toolCall: AgentToolCall, options: RunToolCallOptions): Promise<AgentToolCallOutcome>;
+export {};
+//# sourceMappingURL=agent-loop.d.ts.map

package/dist/agent-loop.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"agent-loop.d.ts","sourceRoot":"","sources":["../src/agent-loop.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,EACN,KAAK,gBAAgB,EACrB,WAAW,EASX,MAAM,uBAAuB,CAAC;AAE/B,OAAO,KAAK,EACX,YAAY,EACZ,UAAU,EACV,eAAe,EACf,YAAY,EACZ,SAAS,EACT,aAAa,EACb,oBAAoB,EACpB,eAAe,EAEf,QAAQ,EACR,MAAM,YAAY,CAAC;AAEpB,MAAM,MAAM,cAAc,GAAG,CAAC,KAAK,EAAE,UAAU,KAAK,OAAO,CAAC,IAAI,CAAC,GAAG,IAAI,CAAC;AAEzE;;;GAGG;AACH,wBAAgB,SAAS,CACxB,OAAO,EAAE,YAAY,EAAE,EACvB,OAAO,EAAE,YAAY,EACrB,MAAM,EAAE,eAAe,EACvB,MAAM,EAAE,WAAW,GAAG,SAAS,EAC/B,QAAQ,EAAE,QAAQ,GAChB,WAAW,CAAC,UAAU,EAAE,YAAY,EAAE,CAAC,CAiBzC;AAED;;;;;;;GAOG;AACH,wBAAgB,iBAAiB,CAChC,OAAO,EAAE,YAAY,EACrB,MAAM,EAAE,eAAe,EACvB,MAAM,EAAE,WAAW,GAAG,SAAS,EAC/B,QAAQ,EAAE,QAAQ,GAChB,WAAW,CAAC,UAAU,EAAE,YAAY,EAAE,CAAC,CAwBzC;AAED,wBAAsB,YAAY,CACjC,OAAO,EAAE,YAAY,EAAE,EACvB,OAAO,EAAE,YAAY,EACrB,MAAM,EAAE,eAAe,EACvB,IAAI,EAAE,cAAc,EACpB,MAAM,EAAE,WAAW,GAAG,SAAS,EAC/B,QAAQ,EAAE,QAAQ,GAChB,OAAO,CAAC,YAAY,EAAE,CAAC,CAiBzB;AAED,wBAAsB,oBAAoB,CACzC,OAAO,EAAE,YAAY,EACrB,MAAM,EAAE,eAAe,EACvB,IAAI,EAAE,cAAc,EACpB,MAAM,EAAE,WAAW,GAAG,SAAS,EAC/B,QAAQ,EAAE,QAAQ,GAChB,OAAO,CAAC,YAAY,EAAE,CAAC,CAiBzB;AAmhBD,iFAAiF;AACjF,MAAM,MAAM,aAAa,GAAG,IAAI,CAAC,eAAe,EAAE,gBAAgB,GAAG,eAAe,CAAC,CAAC;AAEtF,KAAK,cAAc,GAAG,CAAC,aAAa,EAAE,eAAe,CAAC,GAAG,CAAC,KAAK,OAAO,CAAC,IAAI,CAAC,GAAG,IAAI,CAAC;AAwGpF,uCAAuC;AACvC,MAAM,WAAW,kBAAmB,SAAQ,aAAa;IACxD,uCAAuC;IACvC,KAAK,EAAE,SAAS,SAAS,CAAC,GAAG,CAAC,EAAE,CAAC;IACjC,+DAA+D;IAC/D,gBAAgB,EAAE,gBAAgB,CAAC;IACnC,wDAAwD;IACxD,OAAO,EAAE,YAAY,CAAC;IACtB,MAAM,CAAC,EAAE,WAAW,CAAC;IACrB,QAAQ,CAAC,EAAE,cAAc,CAAC;CAC1B;AAED;;;;;;;;GAQG;AACH,wBAAsB,WAAW,CAAC,QAAQ,EAAE,aAAa,EAAE,OAAO,EAAE,kBAAkB,GAAG,OAAO,CAAC,oBAAoB,CAAC,CAQrH"}