@will-17173/telegram-cli 0.1.0

package/README.md

@@ -0,0 +1,264 @@
+# Telegram CLI
+
+[简体中文](README.zh-CN.md)
+
+A TypeScript command-line client for syncing Telegram chats, listening to live messages, searching locally stored messages, and managing Telegram tasks from the terminal.
+
+## Features
+
+- Sign in to Telegram and inspect the current account or available chats.
+- Manage multiple Telegram accounts with isolated sessions and message databases.
+- Fetch chat history into a local SQLite database for fast, offline search.
+- Sync one chat incrementally or sync many chats with a single command.
+- Listen for new messages in real time, with optional attachment summaries.
+- Download attachments from channels that restrict content saving.
+- Search, filter, summarize, and export locally stored messages.
+- Send, edit, and delete messages from the command line.
+- Use human-readable output or structured JSON/YAML where supported.
+
+## Built for AI agents
+
+Telegram CLI gives AI agents a command-based interface to Telegram and locally synced messages. After a human authenticates an account with `tg account add`, an agent can run online and local commands without browser automation.
+
+The CLI supports agent workflows through these interfaces:
+
+- JSON and YAML output gives agents structured data instead of terminal-formatted text.
+- Nonzero exit codes and structured error codes let agents detect and handle failures.
+- `--account <name>` selects an explicit account without changing the current account.
+- Local search and analysis commands let agents inspect synced messages without reconnecting to Telegram.
+
+For example, an agent can search one account and parse the result as JSON:
+
+```sh
+tg search "release" --account work --json
+```
+
+## Installation
+
+Telegram CLI requires Node.js 22 or later.
+
+After the package is published to npm, install it globally with:
+
+```sh
+npm install -g @will-17173/telegram-cli
+```
+
+## Configuration
+
+Configuring personal Telegram API credentials is optional. To use your own, create them at [my.telegram.org](https://my.telegram.org), then save them with:
+
+```sh
+tg config set --api-id <id> --api-hash <hash>
+```
+
+If both `TG_API_ID` and `TG_API_HASH` are unset and the saved configuration file is missing, the CLI uses built-in Telegram API credentials. When a Telegram client is created, it writes this warning to stderr once per process:
+
+```text
+warning: using default Telegram API credentials. Run tg config set --api-id <id> --api-hash <hash> to configure your own.
+```
+
+Setting only one of `TG_API_ID` or `TG_API_HASH` is an error. A malformed or unreadable saved configuration file is also an error; the CLI does not fall back to the built-in credentials in either case.
+
+Personal credentials are stored locally as sensitive configuration. Never share them. API credentials are shared by all registered accounts, while each account keeps its own authentication session.
+
+Run `tg account add` to authenticate and create a local session. Other commands never start the interactive login flow.
+
+You can override the root directory for configuration, account sessions, and message databases:
+
+```sh
+export DATA_DIR=/path/to/tg-cli-data
+```
+
+## Quick start
+
+```sh
+# Add and authenticate the first account
+tg account add
+
+# Check authentication status
+tg status
+
+# List chats, then use a chat name, username, or ID where `<chat>` appears
+tg chats
+
+# Save a chat's history locally
+tg sync <chat>
+
+# Search the locally synced messages
+tg search "keyword" --chat <chat>
+
+# Sync across all chats
+tg sync-all --max-chats 20 --delay 1
+
+# Listen for new messages from one or more chats
+tg listen <chat-or-id> [another-chat ...] --no-media
+
+# Send a message
+tg send <chat> "Hello from tg"
+```
+
+## Multiple accounts
+
+Each Telegram account has its own persisted authentication session and local message database. Add and authenticate an account interactively with:
+
+```sh
+tg account add
+```
+
+The first account you add becomes the current account. Adding another account does not switch the current account automatically. Use the account commands to inspect or change the selection:
+
+```sh
+# List registered accounts
+tg account list
+
+# Show the current account
+tg account current
+
+# Set the default account used by commands
+tg account switch <name>
+
+# Remove an account and its local session/data
+tg account remove <name> --force
+```
+
+Commands use the current account by default. Commands that support `--account` can target another registered account for one invocation without changing the current account:
+
+```sh
+tg chats --account <name>
+tg sync-all --account <name>
+tg search "keyword" --account <name>
+```
+
+Account names are shown by `tg account list`; they are normally derived from the Telegram username. Sessions and message databases remain isolated under each account's directory inside `DATA_DIR`.
+
+Telegram API credentials apply to every registered account. You don't need to configure separate API credentials when adding another account.
+
+## Online and local commands
+
+Online commands connect to Telegram and require a valid session. These include `status`, `whoami`, `chats`, `history`, `sync`, `sync-all`, `refresh`, `info`, `send`, `edit`, `delete`, and `listen`.
+
+Local commands read or modify the selected account's message database without connecting to Telegram. These include `search`, `recent`, `stats`, `top`, `timeline`, `today`, `filter`, `export`, and `purge`.
+
+## Command reference
+
+Run the built-in help for the complete, current command list:
+
+```sh
+tg --help
+```
+
+Common commands:
+
+| Command | Purpose |
+| --- | --- |
+| `tg account add` | Authenticate and register another Telegram account. |
+| `tg account list` | List registered accounts and show which one is current. |
+| `tg account current` | Show the current account. |
+| `tg account switch <name>` | Set the default account used by commands. |
+| `tg account remove <name> --force` | Remove an account and its local session/data. |
+| `tg status` | Check whether the Telegram account is authenticated. |
+| `tg whoami` | Show basic authenticated account information. |
+| `tg config set --api-id <id> --api-hash <hash>` | Save Telegram API credentials for persistent use. |
+| `tg chats` | List available chats. |
+| `tg history <chat> -n <limit>` | Fetch and store full chat history (default up to 1000 messages). |
+| `tg sync <chat>` | Incrementally sync new messages for one chat. |
+| `tg sync-all` | Sync messages from all chats, using local last-message IDs for incremental updates. |
+| `tg refresh` | Alias-like command for bulk sync with same runtime options as `sync-all`. |
+| `tg listen [chat ...]` | Stream incoming messages from selected chats or all chats. |
+| `tg listen --no-media` | Hide attachment summary lines while listening. |
+| `tg search "keyword" --chat <chat>` | Search messages already stored locally. |
+| `tg recent`, `tg today`, `tg stats`, `tg top`, `tg timeline` | Explore local message data. |
+| `tg filter <keywords>` | Filter local messages by keyword with optional chat/hour filters. |
+| `tg export <chat>` | Export local messages from a chat. |
+| `tg send <chat> "Hello from tg"` | Send a message. |
+| `tg edit <chat> <msgId> <text>` | Edit a message. |
+| `tg delete <chat> <msgIds...>` | Delete one or more messages. |
+| `tg purge <chat> --yes` | Remove a chat's locally stored messages. |
+| `tg info <chat>` | Show metadata for a Telegram chat. |
+
+All sync-like commands write to local SQLite storage. The `sync-all` and `refresh` commands process multiple chats based on locally stored message IDs.
+
+Many commands support `--json` or `--yaml` for structured output. Failed commands return a nonzero exit code, so scripts can detect errors without parsing human-readable text.
+
+Common options:
+
+| Option | Purpose |
+| --- | --- |
+| `--account <name>` | Use a registered account without changing the current account. |
+| `--json` / `--yaml` | Emit structured output when the command supports it. |
+| `-v`, `--verbose` | Enable debug logging. |
+| `-V`, `--version` | Print the installed version. |
+
+Use `tg <command> --help` to inspect command-specific options. For example, `listen` supports reconnection and plain-text modes, while `search` supports sender, time, regular-expression, and result-limit filters.
+
+### Sync and listen behavior
+
+- `sync-all` and `refresh` are batch operations for local persistence; they are not read-only.
+- `listen` prints a concise separator for each incoming message and can optionally suppress attachment summaries.
+
+## Troubleshooting
+
+### No active account
+
+If a command reports `account_required`, add an account or select an existing one:
+
+```sh
+tg account add
+tg account switch <name>
+```
+
+### Session is no longer valid
+
+If Telegram returns `AUTH_KEY_UNREGISTERED`, remove the invalid local session and authenticate again:
+
+```sh
+tg account remove <name> --force
+tg account add
+```
+
+### Default API credentials warning
+
+The built-in API credentials remain usable, but the CLI prints a warning when it creates a Telegram client. Configure personal credentials to remove the warning:
+
+```sh
+tg config set --api-id <id> --api-hash <hash>
+```
+
+Set both `TG_API_ID` and `TG_API_HASH` when using environment variables. Setting only one causes a configuration error.
+
+## Local data and privacy
+
+Persisted configuration, authentication sessions, and synced messages remain on your machine unless you copy or export them. The relevant files under `DATA_DIR` are:
+
+```text
+config.json
+accounts.json
+accounts/<name>/session
+accounts/<name>/messages.db
+```
+
+Treat persisted configuration, `.env`, Telegram credentials, session files, and SQLite data as sensitive. Never share them or commit them to version control.
+
+## Development
+
+This project uses pnpm:
+
+```sh
+pnpm install
+pnpm dev --help
+pnpm test
+pnpm typecheck
+```
+
+For local source development, create a `.env` file in the project root:
+
+```dotenv
+TG_API_ID=your_telegram_api_id
+TG_API_HASH=your_telegram_api_hash
+```
+
+`pnpm dev` loads this file only for local source development. An installed `tg` does not automatically load `.env`; use `tg config set --api-id <id> --api-hash <hash>` for persistent production configuration.
+
+## License
+
+Licensed under [GPL-3.0](LICENSE).

package/README.zh-CN.md

@@ -0,0 +1,264 @@
+# Telegram CLI
+
+[English](README.md)
+
+一个 TypeScript 命令行客户端，用于同步 Telegram 聊天记录、监听实时消息、搜索本地存储的消息，并在终端中管理 Telegram 任务。
+
+## 功能
+
+- 登录 Telegram，并查看当前账户或可用聊天列表。
+- 管理多个 Telegram 账号，每个账号使用独立的会话和消息数据库。
+- 将聊天记录提取到本地 SQLite 数据库，以便快速离线搜索。
+- 通过增量同步和批量同步命令更新本地数据。
+- 监听实时消息，并可选显示附件摘要。
+- 从限制下载的频道中下载附件。
+- 搜索、筛选、汇总和导出本地存储的消息。
+- 通过命令行发送、编辑和删除消息。
+- 在支持的场景下使用人类可读输出，或结构化的 JSON/YAML 输出。
+
+## 为 AI Agent 设计
+
+Telegram CLI 为 AI Agent 提供基于命令的 Telegram 和本地消息访问接口。由人工通过 `tg account add` 完成账号认证后，Agent 无需操作浏览器即可执行在线命令和本地命令。
+
+以下接口适合 Agent 工作流：
+
+- JSON 和 YAML 输出让 Agent 直接读取结构化数据，而不是解析终端表格。
+- 非零退出码和结构化错误码让 Agent 能够检测并处理失败。
+- `--account <name>` 可以明确指定账号，且不会改变 current 账号。
+- 本地搜索和分析命令无需重新连接 Telegram，即可查询已同步消息。
+
+例如，Agent 可以搜索指定账号，并将结果作为 JSON 解析：
+
+```sh
+tg search "release" --account work --json
+```
+
+## 安装
+
+Telegram CLI 需要 Node.js 22 或更高版本。
+
+在该软件包发布到 npm 后，可通过以下命令全局安装：
+
+```sh
+npm install -g @will-17173/telegram-cli
+```
+
+## 配置
+
+配置个人 Telegram API 凭据是可选的。如需使用自己的凭据，请先在 [my.telegram.org](https://my.telegram.org) 创建，然后通过以下命令保存：
+
+```sh
+tg config set --api-id <id> --api-hash <hash>
+```
+
+如果 `TG_API_ID` 和 `TG_API_HASH` 均未设置，且已保存的配置文件不存在，CLI 会使用内置的 Telegram API 凭据。创建 Telegram 客户端时，每个进程只会向 stderr 输出一次以下警告：
+
+```text
+warning: using default Telegram API credentials. Run tg config set --api-id <id> --api-hash <hash> to configure your own.
+```
+
+这表示 CLI 正在使用默认凭据；如需配置自己的凭据，请运行 `tg config set --api-id <id> --api-hash <hash>`。只设置 `TG_API_ID` 或 `TG_API_HASH` 其中之一会导致错误。已保存的配置文件格式错误或无法读取也会导致错误；这两种情况下 CLI 都不会改用内置凭据。
+
+个人凭据会作为敏感配置存储在本地，切勿与他人分享。所有已添加账号共用一套 API 凭据，但每个账号都有独立的身份验证会话。
+
+运行 `tg account add` 完成身份验证并创建本地会话。其他命令不会启动交互式登录流程。
+
+你可以通过环境变量修改配置、账号会话和消息数据库的根目录：
+
+```sh
+export DATA_DIR=/path/to/tg-cli-data
+```
+
+## 快速开始
+
+```sh
+# 添加并登录第一个账号
+tg account add
+
+# 检查身份验证状态
+tg status
+
+# 列出聊天，然后在出现 `<chat>` 的位置使用聊天名称、用户名或 ID
+tg chats
+
+# 将聊天记录保存到本地
+tg sync <chat>
+
+# 搜索已同步到本地的消息
+tg search "keyword" --chat <chat>
+
+# 同步全部聊天
+tg sync-all --max-chats 20 --delay 1
+
+# 监听实时消息（可指定多个聊天）
+tg listen <chat-or-id> [another-chat ...] --no-media
+
+# 发送消息
+tg send <chat> "Hello from tg"
+```
+
+## 多账号
+
+每个 Telegram 账号都有独立持久化的身份验证会话和本地消息数据库。通过以下命令交互式登录并添加账号：
+
+```sh
+tg account add
+```
+
+添加的第一个账号会自动成为 current 账号。继续添加其他账号时不会自动切换 current 账号，可通过以下命令查看或更改选择：
+
+```sh
+# 列出已添加的账号
+tg account list
+
+# 查看 current 账号
+tg account current
+
+# 设置命令默认使用的账号
+tg account switch <name>
+
+# 删除账号及其本地会话和数据
+tg account remove <name> --force
+```
+
+各命令默认使用 current 账号。支持 `--account` 的命令可以临时指定另一个已添加的账号，且不会改变 current 账号：
+
+```sh
+tg chats --account <name>
+tg sync-all --account <name>
+tg search "keyword" --account <name>
+```
+
+账号名称可通过 `tg account list` 查看，通常由 Telegram 用户名生成。各账号的会话和消息数据库分别保存在 `DATA_DIR` 下对应的账号目录中。
+
+Telegram API 凭据对所有已添加账号生效，添加其他账号时无需单独配置 API 凭据。
+
+## 在线命令与本地命令
+
+在线命令会连接 Telegram，因此需要有效的账号会话。这类命令包括 `status`、`whoami`、`chats`、`history`、`sync`、`sync-all`、`refresh`、`info`、`send`、`edit`、`delete` 和 `listen`。
+
+本地命令只读取或修改所选账号的消息数据库，不会连接 Telegram。这类命令包括 `search`、`recent`、`stats`、`top`、`timeline`、`today`、`filter`、`export` 和 `purge`。
+
+## 命令参考
+
+运行内置帮助以查看完整且最新的命令列表：
+
+```sh
+tg --help
+```
+
+常用命令：
+
+| 命令 | 用途 |
+| --- | --- |
+| `tg account add` | 登录并添加另一个 Telegram 账号。 |
+| `tg account list` | 列出已添加的账号及 current 状态。 |
+| `tg account current` | 查看 current 账号。 |
+| `tg account switch <name>` | 设置各命令默认使用的账号。 |
+| `tg account remove <name> --force` | 删除账号及其本地会话和数据。 |
+| `tg whoami` | 显示当前登录账号的基本信息。 |
+| `tg config set --api-id <id> --api-hash <hash>` | 持久化保存 Telegram API 凭据。 |
+| `tg status` | 检查 Telegram 账户是否已完成身份验证。 |
+| `tg chats` | 列出可用聊天。 |
+| `tg history <chat> -n <limit>` | 获取并保存完整聊天历史（默认最多 1000 条）。 |
+| `tg sync <chat>` | 将聊天消息同步到本地存储。 |
+| `tg sync-all` | 从全部聊天同步消息，按本地已同步进度做增量更新。 |
+| `tg refresh` | 与 `sync-all` 相同用途的批量同步命令。 |
+| `tg listen [chat ...]` | 实时监听指定聊天（或监听全部聊天）。 |
+| `tg listen --no-media` | 监听时隐藏附件摘要。 |
+| `tg search "keyword" --chat <chat>` | 搜索已存储在本地的消息。 |
+| `tg recent`, `tg today`, `tg stats`, `tg top`, `tg timeline` | 浏览本地消息数据。 |
+| `tg filter <keywords>` | 按关键词筛选本地消息（支持按聊天和时间范围过滤）。 |
+| `tg export <chat>` | 导出本地存储的消息。 |
+| `tg send <chat> "Hello from tg"` | 发送消息。 |
+| `tg edit <chat> <msgId> <text>` | 编辑消息。 |
+| `tg delete <chat> <msgIds...>` | 删除一条或多条消息。 |
+| `tg purge <chat> --yes` | 移除某个聊天在本地存储的消息。 |
+| `tg info <chat>` | 查看聊天元信息。 |
+
+所有同步类命令都会写入本地 SQLite 数据库。`sync-all` 和 `refresh` 根据本地已保存的消息 ID 增量处理多个聊天。
+
+许多命令支持通过 `--json` 或 `--yaml` 输出结构化数据。命令失败时会返回非零退出码，脚本无需解析人类可读文本即可判断执行结果。
+
+常用选项：
+
+| 选项 | 用途 |
+| --- | --- |
+| `--account <name>` | 临时使用已添加的账号，不改变 current 账号。 |
+| `--json` / `--yaml` | 在命令支持时输出结构化数据。 |
+| `-v`, `--verbose` | 启用调试日志。 |
+| `-V`, `--version` | 输出当前安装版本。 |
+
+使用 `tg <command> --help` 查看命令专用选项。例如，`listen` 支持自动重连和纯文本模式，`search` 支持发送者、时间、正则表达式和结果数量筛选。
+
+### 同步与监听行为
+
+- `sync-all` 和 `refresh` 是写入本地数据库的批量同步流程，不是只读命令。
+- `listen` 会实时打印每条到达消息；可用 `--no-media` 关闭附件摘要显示。
+
+## 故障排查
+
+### 没有可用的当前账号
+
+如果命令返回 `account_required`，请添加账号或选择已有账号：
+
+```sh
+tg account add
+tg account switch <name>
+```
+
+### 账号会话已经失效
+
+如果 Telegram 返回 `AUTH_KEY_UNREGISTERED`，请删除失效的本地会话并重新登录：
+
+```sh
+tg account remove <name> --force
+tg account add
+```
+
+### 默认 API 凭据警告
+
+内置 API 凭据仍可使用，但 CLI 创建 Telegram 客户端时会输出警告。配置个人凭据即可移除该警告：
+
+```sh
+tg config set --api-id <id> --api-hash <hash>
+```
+
+通过环境变量配置时，必须同时设置 `TG_API_ID` 和 `TG_API_HASH`。只设置其中一个会导致配置错误。
+
+## 本地数据与隐私
+
+除非你明确复制或导出，否则持久化配置、身份验证会话和已同步消息都会保留在本机。`DATA_DIR` 下的相关文件如下：
+
+```text
+config.json
+accounts.json
+accounts/<name>/session
+accounts/<name>/messages.db
+```
+
+请将持久化配置、`.env`、Telegram 凭据、会话文件和 SQLite 数据视为敏感信息，切勿与他人分享或将它们提交到版本控制中。
+
+## 开发
+
+本项目使用 pnpm：
+
+```sh
+pnpm install
+pnpm dev --help
+pnpm test
+pnpm typecheck
+```
+
+在本地进行源码开发时，请在项目根目录创建 `.env` 文件：
+
+```dotenv
+TG_API_ID=your_telegram_api_id
+TG_API_HASH=your_telegram_api_hash
+```
+
+`pnpm dev` 仅在本地源码开发时加载此文件。安装后的 `tg` 不会自动加载 `.env`；如需持久化生产配置，请使用 `tg config set --api-id <id> --api-hash <hash>`。
+
+## 许可证
+
+采用 [GPL-3.0](LICENSE) 许可证。

package/dist/account/account-context.js

@@ -0,0 +1,22 @@
+import { getAccountRegistryPath, getDataDir } from '../config/env.js';
+import { AccountStore } from './account-store.js';
+import { toAccountContext } from './account-presets.js';
+export function resolveAccountContext(input = {}) {
+    const dataDir = input.dataDir?.trim() ? input.dataDir.trim() : getDataDir();
+    const store = new AccountStore(getAccountRegistryPath(dataDir));
+    const registry = store.read();
+    const name = explicitOrCurrent(input.explicitName, registry.current_account);
+    if (!name) {
+        throw new Error('account_required: no active account found');
+    }
+    const account = store.get(name);
+    if (!account) {
+        throw new Error(`account_not_found: account "${name}"`);
+    }
+    return toAccountContext(dataDir, account);
+}
+function explicitOrCurrent(explicitName, currentAccount) {
+    const explicit = explicitName?.trim();
+    return explicit ? explicit : currentAccount ?? undefined;
+}
+//# sourceMappingURL=account-context.js.map

package/dist/account/account-context.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"account-context.js","sourceRoot":"","sources":["../../src/account/account-context.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,sBAAsB,EAAE,UAAU,EAAE,MAAM,kBAAkB,CAAA;AACrE,OAAO,EAAE,YAAY,EAAE,MAAM,oBAAoB,CAAA;AAEjD,OAAO,EAAE,gBAAgB,EAAE,MAAM,sBAAsB,CAAA;AAOvD,MAAM,UAAU,qBAAqB,CAAC,QAAgC,EAAE;IACtE,MAAM,OAAO,GAAG,KAAK,CAAC,OAAO,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC,UAAU,EAAE,CAAA;IAC3E,MAAM,KAAK,GAAG,IAAI,YAAY,CAAC,sBAAsB,CAAC,OAAO,CAAC,CAAC,CAAA;IAC/D,MAAM,QAAQ,GAAG,KAAK,CAAC,IAAI,EAAE,CAAA;IAC7B,MAAM,IAAI,GAAG,iBAAiB,CAAC,KAAK,CAAC,YAAY,EAAE,QAAQ,CAAC,eAAe,CAAC,CAAA;IAE5E,IAAI,CAAC,IAAI,EAAE,CAAC;QACV,MAAM,IAAI,KAAK,CAAC,2CAA2C,CAAC,CAAA;IAC9D,CAAC;IAED,MAAM,OAAO,GAAG,KAAK,CAAC,GAAG,CAAC,IAAI,CAAC,CAAA;IAC/B,IAAI,CAAC,OAAO,EAAE,CAAC;QACb,MAAM,IAAI,KAAK,CAAC,+BAA+B,IAAI,GAAG,CAAC,CAAA;IACzD,CAAC;IAED,OAAO,gBAAgB,CAAC,OAAO,EAAE,OAAO,CAAC,CAAA;AAC3C,CAAC;AAED,SAAS,iBAAiB,CAAC,YAAgC,EAAE,cAA6B;IACxF,MAAM,QAAQ,GAAG,YAAY,EAAE,IAAI,EAAE,CAAA;IACrC,OAAO,QAAQ,CAAC,CAAC,CAAC,QAAQ,CAAC,CAAC,CAAC,cAAc,IAAI,SAAS,CAAA;AAC1D,CAAC"}

package/dist/account/account-presets.js

@@ -0,0 +1,22 @@
+import { join } from 'node:path';
+export function toAccountContext(dataDir, account) {
+    const accountCopy = Object.freeze({
+        name: account.name,
+        user_id: account.user_id,
+        username: account.username,
+        phone: account.phone,
+        display_name: account.display_name,
+    });
+    return Object.freeze({
+        account: accountCopy,
+        sessionPath: accountSessionPath(dataDir, account.name),
+        dbPath: accountDbPath(dataDir, account.name),
+    });
+}
+export function accountSessionPath(dataDir, accountName) {
+    return join(dataDir, 'accounts', accountName, 'session');
+}
+export function accountDbPath(dataDir, accountName) {
+    return join(dataDir, 'accounts', accountName, 'messages.db');
+}
+//# sourceMappingURL=account-presets.js.map

package/dist/account/account-presets.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"account-presets.js","sourceRoot":"","sources":["../../src/account/account-presets.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAA;AAgBhC,MAAM,UAAU,gBAAgB,CAAC,OAAe,EAAE,OAAoB;IACpE,MAAM,WAAW,GAAG,MAAM,CAAC,MAAM,CAAC;QAChC,IAAI,EAAE,OAAO,CAAC,IAAI;QAClB,OAAO,EAAE,OAAO,CAAC,OAAO;QACxB,QAAQ,EAAE,OAAO,CAAC,QAAQ;QAC1B,KAAK,EAAE,OAAO,CAAC,KAAK;QACpB,YAAY,EAAE,OAAO,CAAC,YAAY;KACnC,CAAC,CAAA;IAEF,OAAO,MAAM,CAAC,MAAM,CAAC;QACnB,OAAO,EAAE,WAAW;QACpB,WAAW,EAAE,kBAAkB,CAAC,OAAO,EAAE,OAAO,CAAC,IAAI,CAAC;QACtD,MAAM,EAAE,aAAa,CAAC,OAAO,EAAE,OAAO,CAAC,IAAI,CAAC;KAC7C,CAAC,CAAA;AACJ,CAAC;AAED,MAAM,UAAU,kBAAkB,CAAC,OAAe,EAAE,WAAmB;IACrE,OAAO,IAAI,CAAC,OAAO,EAAE,UAAU,EAAE,WAAW,EAAE,SAAS,CAAC,CAAA;AAC1D,CAAC;AAED,MAAM,UAAU,aAAa,CAAC,OAAe,EAAE,WAAmB;IAChE,OAAO,IAAI,CAAC,OAAO,EAAE,UAAU,EAAE,WAAW,EAAE,aAAa,CAAC,CAAA;AAC9D,CAAC"}