tomo-ai 0.5.3 → 0.5.5

package/CHANGELOG.md

@@ -1,5 +1,36 @@
 # Changelog
 
+## 0.5.5 (2026-05-01)
+
+### Features
+
+- **Inbound image marker is now always emitted, with the saved disk path when local storage is on.** Previously, a `[Sent an image]` fallback only appeared when the user sent an image with no caption — captions replaced the marker outright, and the model couldn't see the on-disk file path even when `saveInboundImages` was on. Now both Telegram and iMessage prepend `[Sent an image]` (or `[Sent N images]` for iMessage's multi-attachment messages) to the user's caption, and append `saved to: /abs/path[, /abs/path…]` when storage is enabled. The agent can now reliably know an image was attached and `Read` it from disk for tool work that goes beyond what the inline content blocks support. New `formatImageMarker(intendedCount, savedPaths)` helper in `channels/imageStore.ts`; both channels thread `savedPath` through `ImageAttachment`. Marker reflects intended-image count, so a download failure for one attachment doesn't hide the fact that an image was sent.
+
+### UX
+
+- **Group sessions default to hierarchical LCM compaction.** `config.lcm.groupCompactStyle` now defaults to `"lcm"` instead of `"sdk"`. Group sessions get the same daily/weekly/monthly/yearly rollup nudges, %-based compact prompts, and `tomo-lcm-stats` MCP tool that DMs already had. Set to `"sdk"` to opt back into SDK auto-compact for groups. Existing installs with the field unset flip on next `tomo start`. Rollup nudges for group sessions splice in a "Group scope" line so summaries stay focused on that group's conversation rather than mixing in personal/DM context.
+- **`tomo-cron` skill removed; the `schedule_*` MCP tools are now the everyday interface.** The standalone `tomo-cron` skill was redundant once `schedule_create` / `schedule_list` / `schedule_remove` landed on the `tomo-internal` MCP server in 0.5.3. The `tomo-system` skill now briefly mentions the three MCP tools and notes that the `tomo cron …` CLI remains for human debugging (auditing the job store, fixing a stuck job after a restart). Built-in skills list trimmed accordingly.
+- **`tomo-browse` skill switched from `playwright-cli` to `agent-browser`.** New skill content is a thin discovery stub pointing at `agent-browser skills get core`, so workflow guidance always tracks the installed CLI version instead of going stale in this repo. Frontmatter description broadens trigger coverage to web automation, exploratory testing, Electron app automation (VS Code, Slack, Discord, Figma), Slack workspace tasks, Vercel Sandbox, and AWS Bedrock AgentCore.
+
+### Bug fixes
+
+- **`lcm compact`: fix write race that could clobber events the SDK appended while `compactSession` was running.** Symptom: when an agent invokes a long-running `tomo lcm daily/weekly/...` via Bash tool, the SDK's `thinking` + `tool_use` events for that very turn could land on disk between compactSession's initial read and its truncate-rewrite, then get wiped by the rewrite. The subsequent `tool_result` then had a `parentUuid` pointing at a vanished tool_use, breaking the chain.
+  - Fix: capture the file size at read time, re-read the tail at write time, splice any late-arriving events into the new content, and write atomically via `<path>.compacting.tmp` + `rename`.
+- **iMessage typing indicator: stop the flicker.** BlueBubbles' typing decays server-side faster than Telegram's, so the previous 6-second refresh cadence raced the decay and left the indicator visibly turning on/off between ticks during long SDK turns. Three changes: (1) refresh interval dropped from 6 s to **3 s**; (2) added a `tickInFlight` guard so a slow BlueBubbles HTTP server doesn't queue overlapping POSTs; (3) added Tomo-Telegram-style consecutive-error suspension — after 10 consecutive failed POSTs (e.g. Private API helper missing), typing self-suspends with a single `log.warn` and explicitly DELETEs the indicator instead of hammering the endpoint forever. Cross-checked the design against the openclaw bluebubbles extension's typing controller (`openclaw/src/channels/typing.ts`), which uses the same 3 s default and `tickInFlight` pattern.
+
+### Internal
+
+- **Built-in skill prune on startup.** `cli/start.ts` now removes `~/.tomo/workspace/.claude/skills/tomo-*` directories that no longer have a counterpart in bundled `defaults/skills/`. Custom skills (anything not prefixed `tomo-`) are never touched. Without this, retired built-ins like `tomo-cron` would persist forever on existing installs.
+
+## 0.5.4 (2026-04-29)
+
+### Features
+
+- **Group chat rename MCP tool**: `tomo-internal` now exposes `rename_group_chat(target, title)` for explicit user-requested group title changes. Telegram uses Bot API `setChatTitle`; iMessage uses BlueBubbles Private API `PUT /chat/:guid` with `displayName`. Successful renames update Tomo's persisted `chatTitle` immediately so `list_sessions` reflects the new name.
+- **Latest-message reaction MCP tool**: `react_to_latest_message(target, reaction, remove?)` reacts/tapbacks to the latest inbound message Tomo has seen in a session since startup. Telegram uses `setMessageReaction`; iMessage uses BlueBubbles Private API `POST /message/react`. Supported cross-channel reactions are `love`, `like`, `dislike`, `laugh`, `emphasize`, and `question`.
+- **Telegram sticker sending**: responses can now include `STICKER:<telegram_file_id>` to send a Telegram sticker via `sendSticker`, mirroring the existing `MEDIA:` attachment tag flow.
+- **Telegram sticker ingress**: inbound Telegram stickers now arrive as text metadata including `file_id`, optional emoji/set/type flags, and a ready-to-use `STICKER:<file_id>` resend hint.
+
 ## 0.5.3 (2026-04-28)
 
 ### Features

package/README.md

@@ -183,7 +183,7 @@ Run `tomo config` for interactive setup, or edit `~/.tomo/config.json` directly:
   "lcm": {
     "nudgeAtPct": 70,
     "nudgeResetPct": 60,
-    "groupCompactStyle": "sdk"
+    "groupCompactStyle": "lcm"
   }
 }
 ```

package/defaults/AGENT.md

@@ -20,3 +20,7 @@ You have `list_sessions` and `send_message` tools for proactively posting to ano
 - **`direct`**: send verbatim text. Use for factual broadcasts ("meeting moved to 3pm"), pasted content, or self-targeted mid-loop progress updates.
 
 Call `list_sessions` first if you're unsure which group to address. For normal in-conversation responses, just reply with text — don't reach for these tools.
+
+You also have `rename_group_chat` for changing the real title of a Telegram or iMessage group. Only use it when the user explicitly asks to rename a group, and pass a group session key from `list_sessions`.
+
+You also have `react_to_latest_message` for reacting/tapbacking to the latest inbound message Tomo has seen in a session. Latest-message state is in-memory since startup; if the tool says none is known, wait for a new inbound message. Usually pass the current Session key.

package/defaults/skills/browse/SKILL.md

@@ -1,159 +1,40 @@
 ---
 name: tomo-browse
-description: Browse the web with a real browser using playwright-cli. Navigate pages, click elements, fill forms, take screenshots. Use when WebFetch isn't enough — pages need JavaScript, interaction, or visual capture.
+description: Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
 ---
 
-# Browser Automation with playwright-cli
+# agent-browser
 
-## Installation
+Fast browser automation CLI for AI agents. Chrome/Chromium via CDP with
+accessibility-tree snapshots and compact `@eN` element refs.
 
-Before using any playwright-cli command, check if it's installed. If not, install it automatically — don't ask the user:
+Install: `npm i -g agent-browser && agent-browser install`
 
-```bash
-which playwright-cli || npm install -g @playwright/cli@latest
-```
+## Start here
 
-## Quick start
+This file is a discovery stub, not the usage guide. Before running any
+`agent-browser` command, load the actual workflow content from the CLI:
 
 ```bash
-playwright-cli open -s=tomo --browser=chrome --persistent --headed
-playwright-cli goto https://example.com
-playwright-cli snapshot
-playwright-cli click e15
-playwright-cli type "search query"
-playwright-cli screenshot
-playwright-cli -s=tomo close
+agent-browser skills get core             # start here — workflows, common patterns, troubleshooting
+agent-browser skills get core --full      # include full command reference and templates
 ```
 
-**Always use `-s=tomo --browser=chrome --persistent --headed`** when opening a browser. This uses real Chrome with a persistent profile (cookies/logins survive), and the user can see the browser window.
+The CLI serves skill content that always matches the installed version,
+so instructions never go stale. The content in this stub cannot change
+between releases, which is why it just points at `skills get core`.
 
-The agent profile is separate from the user's personal Chrome. The user can interact with the visible browser (e.g., to log in) while the agent operates it.
+## Specialized skills
 
-**Important:** After opening, all subsequent commands must include `-s=tomo` to target the named session:
-```bash
-playwright-cli -s=tomo goto https://example.com
-playwright-cli -s=tomo snapshot
-playwright-cli -s=tomo click e15
-playwright-cli -s=tomo close
-```
-
-## Commands
-
-### Core
+Load a specialized skill when the task falls outside browser web pages:
 
 ```bash
-playwright-cli open -s=tomo --browser=chrome --persistent --headed
-playwright-cli open -s=tomo --browser=chrome --persistent --headed https://example.com/
-playwright-cli goto https://playwright.dev
-playwright-cli type "search query"
-playwright-cli click e3
-playwright-cli dblclick e7
-playwright-cli fill e5 "user@example.com" --submit
-playwright-cli drag e2 e8
-playwright-cli hover e4
-playwright-cli select e9 "option-value"
-playwright-cli upload ./document.pdf
-playwright-cli check e12
-playwright-cli uncheck e12
-playwright-cli snapshot
-playwright-cli eval "document.title"
-playwright-cli dialog-accept
-playwright-cli dialog-dismiss
-playwright-cli -s=tomo close
+agent-browser skills get electron          # Electron desktop apps (VS Code, Slack, Discord, Figma, ...)
+agent-browser skills get slack             # Slack workspace automation
+agent-browser skills get dogfood           # Exploratory testing / QA / bug hunts
+agent-browser skills get vercel-sandbox    # agent-browser inside Vercel Sandbox microVMs
+agent-browser skills get agentcore         # AWS Bedrock AgentCore cloud browsers
 ```
 
-### Navigation
-
-```bash
-playwright-cli go-back
-playwright-cli go-forward
-playwright-cli reload
-```
-
-### Keyboard
-
-```bash
-playwright-cli press Enter
-playwright-cli press ArrowDown
-playwright-cli keydown Shift
-playwright-cli keyup Shift
-```
-
-### Save as
-
-```bash
-playwright-cli screenshot
-playwright-cli screenshot e5
-playwright-cli screenshot --filename=page.png
-playwright-cli pdf --filename=page.pdf
-```
-
-### Tabs
-
-```bash
-playwright-cli tab-list
-playwright-cli tab-new https://example.com/page
-playwright-cli tab-close
-playwright-cli tab-select 0
-```
-
-### Storage
-
-```bash
-playwright-cli cookie-list
-playwright-cli cookie-get session_id
-playwright-cli cookie-set session_id abc123
-playwright-cli localstorage-get theme
-playwright-cli localstorage-set theme dark
-```
-
-## Raw output
-
-Use `--raw` to get clean output for piping:
-
-```bash
-playwright-cli --raw eval "document.title"
-playwright-cli --raw snapshot > page.yml
-```
-
-## Snapshots
-
-After each command, playwright-cli provides a snapshot with element refs (e.g., `e15`, `e3`). Use these refs to interact:
-
-```bash
-playwright-cli snapshot
-playwright-cli click e15
-```
-
-You can also use CSS selectors or Playwright locators:
-
-```bash
-playwright-cli click "#main > button.submit"
-playwright-cli click "getByRole('button', { name: 'Submit' })"
-```
-
-## Targeting elements
-
-Prefer refs from snapshots. Fall back to CSS selectors or locators when refs are ambiguous.
-
-## Example: Form submission
-
-```bash
-playwright-cli open -s=tomo --browser=chrome --persistent --headed https://example.com/form
-playwright-cli snapshot
-playwright-cli fill e1 "user@example.com"
-playwright-cli fill e2 "password123"
-playwright-cli click e3
-playwright-cli snapshot
-playwright-cli -s=tomo close
-```
-
-## Example: Multi-tab workflow
-
-```bash
-playwright-cli open -s=tomo --browser=chrome --persistent --headed https://example.com
-playwright-cli tab-new https://example.com/other
-playwright-cli tab-select 0
-playwright-cli snapshot
-playwright-cli -s=tomo close
-```
+Run `agent-browser skills list` to see everything available on the
+installed version.

package/defaults/skills/lcm/DAILY.md

@@ -15,7 +15,7 @@ tomo lcm daily --session-id SESSION_ID --summary "<today's summary>"
 ## When to run
 
 - **End of day** (before bed or before a long idle). Cleanest shape.
-- **Mid-day** when the harness nudges you that raw tail > 40 events.
+- **Mid-day** when the harness nudges you that the raw tail has grown past the fresh-tail floor (default 32 events; tune via `lcm.dailyFreshTail` in config.json).
 - **Before a big task** when you want clean context for an involved piece of work.
 - **After long tool-heavy work** — reduce clutter before the conversation continues.
 

package/defaults/skills/system/CONFIG.md

@@ -40,7 +40,8 @@ Prefer editing via `tomo config` (interactive TUI). This reference is for readin
   "lcm": {
     "nudgeAtPct": 70,
     "nudgeResetPct": 60,
-    "groupCompactStyle": "sdk"
+    "groupCompactStyle": "sdk",
+    "dailyFreshTail": 32
   }
 }
 ```
@@ -67,7 +68,8 @@ Prefer editing via `tomo config` (interactive TUI). This reference is for readin
 | `maxTurns` | number | Max agent turns per single user message (one turn ≈ one tool-use round). Default `50`. Raise if you see "max turns exceeded" on long tool chains. |
 | `lcm.nudgeAtPct` | number | Context-usage % at which the harness nudges the agent to run `tomo lcm daily`. Default `70`. Lower = compact earlier and more often. |
 | `lcm.nudgeResetPct` | number | Hysteresis reset threshold — the "already nudged" flag clears once usage drops below this %. Default `60`. Must be less than `nudgeAtPct`; invalid values fall back to defaults. |
-| `lcm.groupCompactStyle` | string | `"sdk"` (default) or `"lcm"`. `"sdk"` lets the SDK auto-compact group sessions; `"lcm"` opts groups into the same hierarchical LCM flow as DMs (disables SDK auto-compact and fires the daily/80% nudges). DMs always use LCM regardless. |
+| `lcm.groupCompactStyle` | string | `"sdk"` (default) or `"lcm"`. `"sdk"` lets the SDK auto-compact group sessions; `"lcm"` opts groups into the same hierarchical LCM flow as DMs (disables SDK auto-compact and fires all three harness nudges: 70% daily, 80% safety net, and the periodic rollup runner). DMs always use LCM regardless. |
+| `lcm.dailyFreshTail` | number | Number of most-recent raw user/assistant events kept outside today's daily rollup so mid-day compacts don't wipe warm short-term texture. Default `32`. Counts SDK events (one tool round = multiple events), not user-typed messages. Set to `0` to compact every event into today's block. Past days are always compacted in full regardless of this value. |
 
 ## Requirements and overrides
 

package/defaults/skills/system/SKILL.md

@@ -29,15 +29,19 @@ Session stats show:
 
 **Note:** Context stats come from the SDK API and reflect the state at the end of the *previous* query. After compacting or other changes, you need to wait for a new query to complete before the numbers update.
 
-When context crosses the nudge threshold (default 70%, set via `lcm.nudgeAtPct` in config.json), the harness sends a system message asking you to run `tomo lcm daily` — see the `tomo-lcm` skill. A second nudge at 80% asks you to use the `lcm compact` skill before the next user message. Group sessions default to SDK auto-compact instead (override with `lcm.groupCompactStyle: "lcm"`).
+When context crosses the nudge threshold (default 70%, set via `lcm.nudgeAtPct` in config.json), the harness sends a system message asking you to run `tomo lcm daily` — see the `tomo-lcm` skill. A second nudge at 80% asks you to use the `lcm compact` skill before the next user message. A periodic rollup runner also nudges you when daily/weekly/monthly/yearly blocks are due. Group sessions default to SDK auto-compact instead (override with `lcm.groupCompactStyle: "lcm"` to enroll groups in all three nudges).
 
 ## Cron Jobs
 
-```bash
-tomo cron list                 # All scheduled jobs with status
-tomo cron add --name "X" --schedule "in 20m" --message "Y"
-tomo cron remove <id>          # Delete a job
-```
+Schedule reminders and recurring tasks via the `tomo-internal` MCP tools:
+
+- `schedule_create` — create a one-shot or recurring job (`schedule` accepts `in 20m`, `every 6h`, or a 5-field cron expression; `sessionKey` controls where the fired message lands)
+- `schedule_list` — list every job with `id`, `nextRunAt`, `lastStatus`, etc.
+- `schedule_remove` — delete by `id`
+
+These are the everyday interface — load them via tool search ("schedule reminder cron") when the user asks to schedule something.
+
+The `tomo cron list / add / remove` CLI is still here for human debugging (auditing the job store, fixing a stuck job after a restart). Prefer the MCP tools in normal conversation.
 
 ## File Paths
 
@@ -67,6 +71,9 @@ Responses stream to Telegram in real-time — messages update every 1.5s as toke
 ### MEDIA: tag
 To send an image/file to the user, include `MEDIA:/path/to/file.png` in your response. The harness strips it from text and sends the file. Text before/after becomes the caption.
 
+### STICKER: tag
+To send a Telegram sticker by file_id, include `STICKER:<telegram_file_id>` in your response. The harness strips it from text and sends the sticker on Telegram; other channels ignore sticker sends. Only use file_ids you have seen or been given.
+
 ### NO_REPLY
 Reply with exactly `NO_REPLY` to suppress delivery to the channel. Use for background tasks that found nothing to report.
 
@@ -85,12 +92,14 @@ Two listen modes per group:
 The active mode plus group title and known participants are part of your per-session system prompt under `## Group Chat Context` whenever you're in a group session — survives compaction. Each incoming group message is prefixed with the sender name (`Alice: ...`) so you can attribute it.
 
 ### Proactive messaging (MCP tools)
-Two in-process MCP tools let you message outside the current conversation:
+In-process MCP tools let you message outside the current conversation:
 
 - `mcp__tomo-internal__list_sessions` — discover valid targets. Returns `{identities: [{name}], groups: [{key, title?, participants?}]}`. Group titles and participants populate as messages arrive in the group; an entry without them just hasn't seen activity since the schema landed.
 - `mcp__tomo-internal__send_message(target, message, mode?)` — send to a target. Two modes:
   - `delegate` (default): describe the *intent* (e.g. "follow up with Alice about her recent trip"). The recipient session's Claude composes the actual message in its own voice/context. Best for social or contextual relays. Fire-and-forget.
   - `direct`: send the verbatim text. Recipient is not triggered into a Claude turn. Best for factual broadcasts ("meeting moved to 3pm"), pasted content, or self-targeted mid-loop progress updates.
+- `mcp__tomo-internal__rename_group_chat(target, title)` — rename the real Telegram or iMessage group title. Use only when the user explicitly asks for a rename; `target` must be a group session key from `list_sessions`.
+- `mcp__tomo-internal__react_to_latest_message(target, reaction, remove?)` — react/tapback to the latest inbound message Tomo has seen in that session since startup. This latest-message state is in-memory; after a restart, wait for a new inbound message before using it. Usually pass the current Session key. Reactions: `love`, `like`, `dislike`, `laugh`, `emphasize`, `question`.
 
 Pass identity name (`"alice"`) or session key (`"telegram:-1001234567"`) as `target`. Call `list_sessions` first if unsure. Tool result lines (with `is_error` flag) appear in `tomo logs` immediately after the corresponding tool call.
 
@@ -99,7 +108,7 @@ Pass identity name (`"alice"`) or session key (`"telegram:-1001234567"`) as `tar
 ### Built-in skills (`tomo-*`)
 Skills prefixed with `tomo-` are bundled with Tomo and automatically updated on every `tomo start`. Do not edit these — your changes will be overwritten on next restart.
 
-Current built-in skills: `tomo-system`, `tomo-lcm`, `tomo-browse`, `tomo-cron`.
+Current built-in skills: `tomo-system`, `tomo-lcm`, `tomo-browse`.
 
 ### Custom / third-party skills
 Place skill directories under `~/.tomo/workspace/.claude/skills/`. Each skill needs a `SKILL.md` with YAML frontmatter (`name` and `description`). The harness picks them up automatically — restart Tomo to load new skills.
@@ -143,7 +152,7 @@ tomo restart         # Restart
 
 ### Session feels stale or confused
 ```bash
-tomo sessions clear  # Reset sessions
+tomo sessions clear  # Reset sessions (Must ask user to confirm)
 tomo restart
 ```
 Or tell the user to send `/new` in Telegram.

package/dist/agent/live-session.d.ts

@@ -0,0 +1,57 @@
+import { type SDKUserMessage } from "@anthropic-ai/claude-agent-sdk";
+import type { sdkOptions } from "./sdk-options.js";
+export interface MessageRequest {
+    message: SDKUserMessage;
+    /** Called for each text-delta as it streams (cumulative running text). */
+    onText?: (text: string) => void;
+    /**
+     * Called once per text block when an `assistant` event arrives, after the
+     * block's deltas have all been streamed. Receives the block's full text.
+     * Channels can use this to seal the in-flight streamed message and start
+     * fresh on the next block, so multi-block turns ship as multiple messages
+     * instead of a single edit-in-place that drops earlier blocks.
+     */
+    onBlockComplete?: (text: string) => void | Promise<void>;
+    resolve: (response: string) => void;
+    reject: (err: Error) => void;
+}
+export interface QueryResult {
+    costUsd: number;
+    inputTokens: number;
+    outputTokens: number;
+    cacheReadTokens: number;
+    cacheCreationTokens: number;
+    contextUsed: number;
+    contextMax: number;
+    contextBreakdown?: {
+        name: string;
+        tokens: number;
+    }[];
+}
+export declare class LiveSession {
+    private q;
+    private pendingMessage;
+    private currentRequest;
+    private parts;
+    private streamingText;
+    private sessionId;
+    private alive;
+    lastResult: QueryResult | null;
+    private prevTotalCost;
+    private eventLoopDone;
+    private sessionKey;
+    private pendingToolNames;
+    constructor(options: ReturnType<typeof sdkOptions>, sessionKey?: string);
+    private messageGenerator;
+    private consumeEvents;
+    private handleEvent;
+    private logContextUsage;
+    send(text: string, onText?: (text: string) => void, images?: Array<{
+        data: string;
+        mediaType: string;
+    }>, onBlockComplete?: (text: string) => void | Promise<void>): Promise<string>;
+    getSessionId(): string | null;
+    isAlive(): boolean;
+    close(): void;
+}
+//# sourceMappingURL=live-session.d.ts.map

package/dist/agent/live-session.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"live-session.d.ts","sourceRoot":"","sources":["../../src/agent/live-session.ts"],"names":[],"mappings":"AAAA,OAAO,EAAqB,KAAK,cAAc,EAAmB,MAAM,gCAAgC,CAAC;AAEzG,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,kBAAkB,CAAC;AAEnD,MAAM,WAAW,cAAc;IAC7B,OAAO,EAAE,cAAc,CAAC;IACxB,0EAA0E;IAC1E,MAAM,CAAC,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,CAAC;IAChC;;;;;;OAMG;IACH,eAAe,CAAC,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,GAAG,OAAO,CAAC,IAAI,CAAC,CAAC;IACzD,OAAO,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,IAAI,CAAC;IACpC,MAAM,EAAE,CAAC,GAAG,EAAE,KAAK,KAAK,IAAI,CAAC;CAC9B;AAED,MAAM,WAAW,WAAW;IAC1B,OAAO,EAAE,MAAM,CAAC;IAChB,WAAW,EAAE,MAAM,CAAC;IACpB,YAAY,EAAE,MAAM,CAAC;IACrB,eAAe,EAAE,MAAM,CAAC;IACxB,mBAAmB,EAAE,MAAM,CAAC;IAC5B,WAAW,EAAE,MAAM,CAAC;IACpB,UAAU,EAAE,MAAM,CAAC;IACnB,gBAAgB,CAAC,EAAE;QAAE,IAAI,EAAE,MAAM,CAAC;QAAC,MAAM,EAAE,MAAM,CAAA;KAAE,EAAE,CAAC;CACvD;AAuCD,qBAAa,WAAW;IACtB,OAAO,CAAC,CAAC,CAAQ;IACjB,OAAO,CAAC,cAAc,CAAgD;IACtE,OAAO,CAAC,cAAc,CAA+B;IACrD,OAAO,CAAC,KAAK,CAAgB;IAC7B,OAAO,CAAC,aAAa,CAAM;IAC3B,OAAO,CAAC,SAAS,CAAuB;IACxC,OAAO,CAAC,KAAK,CAAQ;IACrB,UAAU,EAAE,WAAW,GAAG,IAAI,CAAQ;IACtC,OAAO,CAAC,aAAa,CAAK;IAC1B,OAAO,CAAC,aAAa,CAAgB;IACrC,OAAO,CAAC,UAAU,CAAqB;IAGvC,OAAO,CAAC,gBAAgB,CAA6B;gBAEzC,OAAO,EAAE,UAAU,CAAC,OAAO,UAAU,CAAC,EAAE,UAAU,CAAC,EAAE,MAAM;YAMxD,gBAAgB;YAUjB,aAAa;YAeb,WAAW;YA2GX,eAAe;IA6CvB,IAAI,CACR,IAAI,EAAE,MAAM,EACZ,MAAM,CAAC,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,EAC/B,MAAM,CAAC,EAAE,KAAK,CAAC;QAAE,IAAI,EAAE,MAAM,CAAC;QAAC,SAAS,EAAE,MAAM,CAAA;KAAE,CAAC,EACnD,eAAe,CAAC,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,GAAG,OAAO,CAAC,IAAI,CAAC,GACvD,OAAO,CAAC,MAAM,CAAC;IA6ClB,YAAY,IAAI,MAAM,GAAG,IAAI;IAI7B,OAAO,IAAI,OAAO;IAIlB,KAAK,IAAI,IAAI;CAId"}