mandala-computer-mcp 0.1.1 → 0.4.0

package/README.md

@@ -19,7 +19,24 @@ the way you would treat a password.
 Node 20.3 or newer. There is nothing else to install: `npx` fetches the server
 the first time a client starts it.
 
-**Claude Code**
+**Claude Code** — as a plugin, which installs the server and a skill together:
+
+```sh
+export MANDALA_API_KEY=com_…       # in the shell Claude Code starts from
+/plugin marketplace add mandalacomputer/mcp
+/plugin install mandala-computer@mandala
+```
+
+The skill — [`plugin/skills/mandala-computer/SKILL.md`](plugin/skills/mandala-computer/SKILL.md)
+— is the part the tools cannot say for themselves: when a cloud desktop is the
+right answer at all, that it costs money until it is suspended or stopped, that
+`run_agent` is usually the right level and a screenshot per click is not, and
+which refusals are worth a second try. It is a description of *when and how*,
+not a second client; once the server is installed it stays out of the way.
+`MANDALA_MODEL_KEY`, if exported alongside, is passed through and turns on
+`run_agent`.
+
+Or the server on its own, with the key inline:
 
 ```sh
 claude mcp add mandala -e MANDALA_API_KEY=com_… -- npx -y mandala-computer-mcp
@@ -122,8 +139,14 @@ already supports for when they are.
 **A running computer costs money, and a forgotten one keeps costing it.**
 `create_computer` says so in its own description, and so does everything that
 starts a machine by a side door — `restore_snapshot` boots a stopped computer,
-`write_clipboard` resumes a suspended one, and each of those is charged like
-any other start. When a stretch of work is over, `suspend_computer` (a pause:
+and `write_clipboard`, `read_file` and `cursor_position` each resume a suspended
+one, because each has to reach the guest agent to do its job. All of them are
+charged like any other start, and on a plan at its limit can come back 402
+rather than a result. The two reads are the surprising half of that list, and
+are why neither is annotated `readOnlyHint`: a host that auto-approves
+read-only tools would otherwise wake and bill a machine with nobody asked.
+`screenshot`, `read_clipboard` and `list_windows` genuinely do not start
+anything and keep the hint. When a stretch of work is over, `suspend_computer` (a pause:
 `start_computer` brings the same session back in about a second) or
 `stop_computer` (a shutdown: the disk is kept, the session is not). Idle
 suspend catches the ones a model forgets, but only after 30 minutes untouched.
@@ -134,9 +157,11 @@ time — `screenshot`, `click`, `screenshot` — puts an image in the calling
 model's context for every step. `run_agent` hands a task in plain language to
 the platform's own loop instead, which screenshots, decides and clicks inside
 the platform and answers with a sentence and the list of what it did. It is
-registered only when a model key is present (see [Configuration](#configuration)),
-bills that key for every step, and `max_steps` is the spending cap as much as
-the loop bound.
+registered only when a model key is present (see [Configuration](#configuration))
+and bills that key for the run. `max_steps` bounds the WORK rather than the
+bill: a step is one action on the desktop, one model reply can ask for several
+and spends a step on each, a paused turn costs tokens and no step, and not every
+step takes a screenshot. It defaults to 20 and is capped at 100 here.
 
 **A screenshot is how you find out what the screen looks like.** A click that
 landed and a click that did nothing produce the same tool result, so a model
@@ -258,6 +283,44 @@ they are doing — it does not receive them and has no `verify`, because a
 server with no endpoint has nothing to verify. `list_webhook_deliveries` is
 where a delivery that ran out of retries shows up; nothing is dropped silently.
 
+**A capture outlives the request that starts it.** `POST /computers/:id/snapshots`
+answers `202` with a placeholder row and copies the disk afterwards, which takes
+minutes and scales with how much has been written — longer than any HTTP request
+survives. So `create_snapshot` polls: it holds the id the platform allocated
+before the copy, watches `list_snapshots` for that row to stop reading
+`capturing`, and answers with the finished snapshot. It waits for *not
+capturing* rather than for `pending`, because replication can carry a small
+snapshot straight on to `durable` between two polls; and it matches on the id
+rather than on the newest row for the computer, because a scheduled capture
+finishing in the same window makes that wrong on exactly the long captures where
+it matters. `wait: false` hands back the id instead, for a caller that would
+rather poll on its own schedule.
+
+The three answers it can end on are kept apart deliberately. A capture that
+lands is the snapshot. A capture that FAILS mid-copy leaves no snapshot and no
+row — the `capturing` row simply disappears, and that absence is the only signal
+there is, which is why an incomplete listing is never allowed to decide it. A
+wait that runs out says the capture is still running and names the id to follow,
+because that one asks for a look rather than for another attempt.
+
+**A deletion outlives its request too, and reads the other way round.**
+`DELETE /snapshots/:id` answers `202` and then detaches the dependent snapshots
+and removes the stored objects. There is no state that means deleted, so
+`delete_snapshot` polls for the row to **go** — the mirror of a capture, which
+polls for a row to stay and change. A row that stays is one that STALLED, and it
+sits in `deleting`, a state a bare listing hides: the poll asks with
+`include=unfinished` for exactly that reason, since without it a half-deleted
+snapshot is indistinguishable from a deleted one. The platform retries a stalled
+deletion itself every fifteen minutes, so the give-up sentence says to watch
+rather than to repeat.
+
+Because absence is the success signal here, "Deleted" is said only off a listing
+read **whole**. A row missing because a hypervisor did not answer is not a row
+that is gone, and that mistake is unrecoverable in a way the others are not:
+nobody goes looking for a snapshot they have been told was destroyed. A `409`
+saying the snapshot is already being deleted is progress, not a fault — the
+answer is to watch that deletion finish, never to go and delete something else.
+
 **A schedule says when, not how long.** `snapshot_schedule` sets the window a
 computer's automatic snapshot is taken in; `get_retention` is what says how many
 of them survive, and it takes no computer because the window belongs to the
@@ -304,9 +367,12 @@ nothing; `background: true` is the only thing that works. The abandoned command
 keeps running, so the call after one of these often reports the guest agent as
 busy — that is the first failure continuing, not a second one.
 
-The ceiling belongs to that proxy rather than to the platform, which is why
-`timeout_s` still accepts up to 300: a `MANDALA_BASE_URL` pointed at an origin
-reached without the proxy in front of it does not have one.
+That roughly two-minute ceiling belongs to the hosted proxy. The server accepts
+integer foreground `timeout_s` values from 1 through 600 seconds (default 30),
+and the tool exposes that range for a `MANDALA_BASE_URL` reached without the
+proxy. The HTTP client allows 630 seconds for response headers so the server can
+report a 600-second timeout. Use `background: true` and poll the handle for
+longer work.
 
 **`list_windows` sees what a screenshot cannot.** It is how you tell an
 application that failed to start from one that has not painted yet. Match on
@@ -362,11 +428,25 @@ simply has fewer rows, an unknown number missing and nothing marking the gap.
 The other two append a row marked `unreachable` for each thing they could not
 reach — but only for a key that spans the account. A WORKSPACE-SCOPED key gets
 no marked rows either, because naming the missing ids would mean reading them
-out of a placement cache that has no workspace column, and handing a confined
+out of a host cache that has no workspace column, and handing a confined
 credential ids from the workspaces it is confined away from. For such a key all
 three listings are the `INCOMPLETE:` line and nothing else, which is why that
 line is written first and in prose.
 
+**A computer has a lifecycle of its own, separate from what its guest is
+doing.** `state` is the platform's record of whether the machine exists —
+`live`, `deleting`, `deleted`, `lost`, or `unreachable` when a listing could not
+confirm the row against its host — while `status` is the host's answer about the
+guest. A row served from the record has the first and not the second, so
+`list_computers` prints both when both are there: a computer can be running and
+being deleted at once.
+
+An unfiltered listing is `live`, `unreachable` and `deleting`. The two terminal
+states are withheld from it, so `list_computers(state: 'deleted')` is the only
+way a computer that has gone is ever shown — and an empty answer to a filtered
+listing is a fact about the filter rather than about the account, which is what
+it says rather than inviting you to create one.
+
 **Snapshots mid-deletion are billed but hidden.** A deletion that began and did
 not finish still holds objects and still counts against storage, and the default
 listing leaves it out — every ordinary caller is asking "what can I restore".
@@ -382,6 +462,10 @@ by default — the platform drops input on that socket, so it is safe to hand to
 somebody. `control: true` returns the full-control one, which is root-equivalent
 on that machine. Neither appears in any other tool's output, deliberately: a
 tool result lands in a model's context and from there in whatever captured it.
+It is also why `get_desktop_url` carries no `readOnlyHint` even though its route
+neither writes nor spends: hosts treat that hint as licence to call without
+asking, so keeping it would let a model pass out control of a desktop with
+nobody prompted.
 
 **Retiring a template cannot be undone, and takes more than it looks.**
 `retire_template` without a `version` retires **every** version of the name —
@@ -411,18 +495,47 @@ default request timeout is 60 seconds and only a progress notification can reset
 it — but the SDK resets it only for a caller that passed that option, so a client
 which merely accepts progress is still cancelled a minute into a fifteen-minute
 build. `get_build` is the answer for a client that cannot hold a request open:
-it reads once and returns. A build that *failed* is a normal answer from
+it reads once and returns.
+
+**The same applies to every tool here that waits.** `wait_for_computer`,
+`move_computer`, `create_snapshot` and `delete_snapshot` all poll, and all report
+progress on every poll — a changed line at once, an unchanged one on a ten-second
+heartbeat, so the request stays open without flooding the client. A live capture
+took 107 seconds and was cancelled at 60 before this existed, which turned every
+carefully-worded answer about what had actually happened into a transport error.
+Each of them has a way out for a client that cannot opt in: `wait: false` on the
+two snapshot tools, `list_moves` after a move, a shorter `timeout_s` and a second
+call on the wait. A build that *failed* is a normal answer from
 `watch_build`, not an error — it names the step that stopped it, which is the
 thing to fix. An `error` event is the *stream* failing and says nothing about the
 build, and the tool says so rather than letting a model rewrite a document that
 is fine.
 
-What you build is **not launchable yet**: the fleet does not advertise a family
-it built rather than shipped, so a create naming such a ref is still refused.
-`publish_template` says the same thing where it matters — publishing and being
-launchable are different questions, and its result no longer ends on a flat
-"launch it with `create_computer`" that a document declaring `spec.build` would
-have led straight into a refusal on.
+A completed template build can launch with `create_computer` when eligible
+capacity and its image are available. Publishing a template and completing its
+build are separate steps; publication alone does not guarantee launch capacity.
+
+When the API supports image preparation continuation, a `create_computer`
+refusal with code `template_image_preparing` preserves `template_transfer` and
+`preparation` (including `state` and `error`) in the JSON appended to the tool's
+error text. `retry_after_ms`, when present, is the parsed `Retry-After` delay in
+**milliseconds**, also available to embedders as `APIError.retryAfterMs`. Both
+integer seconds and HTTP dates are accepted; missing or invalid delays are
+omitted. Delays are capped at 2,147,483,647 milliseconds to fit a timer.
+
+For `preparing`, `copying`, or `ready` with a usable token and delay, wait for
+that delay, then repeat the original identical create arguments, including
+`template`, adding the token exactly as returned. The token must be a nonblank
+string, requires the original `template`, and cannot be combined with `size`.
+A `failed` preparation reports its error for inspection before deciding what to
+do next. Missing or unknown states and missing or invalid delays do not supply
+automatic retry advice. The server never replays a create automatically, and
+`isTransient` returns false for this refusal code because unchanged replay is
+not the continuation protocol.
+
+The token selects the image build; it is **not a create idempotency key**. Stop
+after success. After a lost or ambiguous response, inspect `list_computers`
+before deciding what to do; never automatically replay the create.
 
 ## Running it as a service
 
@@ -472,7 +585,7 @@ naming the fix.
 | `MANDALA_BASE_URL` | Defaults to `https://app.mandala.computer/api/v1`. |
 | `MANDALA_COMPUTER_ID` | Bind a computer at startup, so `use_computer` is not needed. **stdio only** — under `--http` it is ignored rather than bound into every caller's session, since it names a machine on the operator's account. |
 | `MANDALA_MODEL_KEY` | An Anthropic key. Enables `run_agent`, which runs the platform's own loop on that key. **stdio only** — under `--http` each caller sends their own as `X-Model-Key`, and this variable is ignored. |
-| `MANDALA_NO_LIFECYCLE` | `1` withholds `create_computer`, `clone_computer`, `clone_snapshot`, `delete_computer` and `delete_snapshot` — every tool that makes a computer or destroys one. |
+| `MANDALA_NO_LIFECYCLE` | `1`, `true`, `yes` or `on` withholds `create_computer`, `clone_computer`, `clone_snapshot`, `delete_computer` and `delete_snapshot` — every tool that makes a computer or destroys one. `0`, `false`, `no`, `off` or unset leaves them registered. Any other value is **refused at startup** rather than read as off: a typo here would otherwise leave those tools in place on a server whose operator believes they are gone. The `--no-lifecycle` flag reads the same vocabulary and refuses the same way, except that it has no spelling for *unset*: `--no-lifecycle=` is refused rather than ignored, so a launcher template whose variable did not expand stops instead of quietly leaving the tools registered. |
 | `PORT`, `HOST` | For `--http`. Default `3000`, `127.0.0.1`. |
 | `MANDALA_ALLOWED_HOSTS`, `MANDALA_ALLOWED_ORIGINS` | Comma-separated. Which `Host` and `Origin` values this server answers to. On a loopback bind the host list defaults to the address it was given, so DNS-rebinding protection is on without configuration; set this when serving under a name. |
 
@@ -519,14 +632,16 @@ written down in `UNIMPLEMENTED`. A route added upstream becomes a failing test
 here rather than a feature nobody noticed.
 
 `npm run check:surface` goes further and diffs the mirror against the platform's
-own route table, whenever the platform repository happens to be checked out next
-door — or wherever `MANDALA_PLATFORM_REPO` points. Without it the script says
-it is skipping and exits 0, which is what it does for anyone outside the
-platform team; the diff is enforced from the platform's own CI, which checks
-this repository out beside itself and runs the same script.
+published surface manifest — a file the platform generates from its own tables
+and commits like a lockfile — whenever the platform repository happens to be
+checked out next door, or wherever `MANDALA_PLATFORM_REPO` points. Without it
+the script says it is skipping and exits 0, which is what it does for anyone
+outside the platform team; a manifest it cannot read is a failure, never a
+comparison of nothing. The diff is enforced from the platform's own CI, which
+checks this repository out beside itself and runs the same script.
 
 ```
-check:surface — the mirror matches the platform (56 routes, 89 parameters, from …/mandala-computer).
+check:surface — the mirror matches the platform (N routes, N parameters, from …).
 ```
 
 ## See also

package/dist/api.d.ts

@@ -1,3 +1,4 @@
+import { Agent } from 'undici';
 export declare const DEFAULT_BASE_URL = "https://app.mandala.computer/api/v1";
 /** Anthropic's own key, forwarded for the one route that runs a model. */
 export declare const MODEL_KEY_HEADER = "X-Model-Key";
@@ -54,10 +55,10 @@ export type Bytes = {
     unrangeable: boolean;
 };
 /**
- * The longest guest exec waits 300 seconds before it answers. Node's bundled
- * fetch also gives response headers 300 seconds by default, so the client can
- * lose that race while the command is still finishing in the guest. Keep the
- * public exec limit and give the platform enough time to report its timeout.
+ * The longest foreground guest exec waits 600 seconds before it answers.
+ * Node's bundled fetch gives response headers 300 seconds by default, so the
+ * client can lose that race while the command is still finishing in the guest.
+ * Allow 30 seconds beyond the public exec limit for the timeout response.
  *
  * The body is a different clock. undici's default `bodyTimeout` is 300 seconds
  * of silence *between chunks*, and `run_agent` SSE (or a long exec that has
@@ -66,9 +67,10 @@ export type Bytes = {
  * disables it: a quiet gap is not a dead connection, and the caller's
  * AbortSignal is what ends a request nobody is waiting for.
  */
-export declare const PLATFORM_HEADERS_TIMEOUT_MS = 330000;
+export declare const PLATFORM_HEADERS_TIMEOUT_MS = 630000;
 /** Disabled. A finite idle limit is what used to kill a quiet SSE stream. */
 export declare const PLATFORM_BODY_TIMEOUT_MS = 0;
+export declare const PLATFORM_DISPATCHER: Agent;
 /**
  * The fetch a platform request actually goes through, and why it is not simply
  * `fetch`.
@@ -160,7 +162,7 @@ export declare class Api {
      * short 200 — but a caller that opts in gets the list plus `X-GC-Incomplete`,
      * and a header is only a warning if something reads it.
      *
-     * It is the count of what the placement cache could account for, and it is
+     * It is the count of what the host cache could account for, and it is
      * legitimately `0`: a computer created during the outage was never cached
      * against the host now holding it. So presence is the signal and the number is
      * detail, which is why this returns `null` versus a number rather than a
@@ -181,6 +183,17 @@ export declare class Api {
      */
     sse(method: string, path: string, opts?: RequestOptions): AsyncGenerator<SSEEvent>;
 }
+/**
+ * Every error under one, including the ones a fetch hides two levels down.
+ *
+ * A rejected fetch is a `TypeError: fetch failed` whose `cause` is what
+ * actually went wrong, and on a dual-stack host that cause is an
+ * `AggregateError` holding one attempt per address. Neither the top error nor
+ * its immediate cause carries the code the classifiers below read, so both
+ * links have to be followed. Bounded, because a cause chain is user-reachable
+ * data and nothing here needs to be robust to a cycle.
+ */
+export declare function causes(err: unknown, depth?: number): Generator<Record<string, unknown>>;
 /** The filename the platform put on a download, if it put one there. */
 export declare function filenameFrom(disposition: string | null): string | undefined;
 //# sourceMappingURL=api.d.ts.map

package/dist/api.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"api.d.ts","sourceRoot":"","sources":["../src/api.ts"],"names":[],"mappings":"AAYA,eAAO,MAAM,gBAAgB,wCAAwC,CAAC;AAEtE,0EAA0E;AAC1E,eAAO,MAAM,gBAAgB,gBAAgB,CAAC;AAE9C,MAAM,MAAM,cAAc,GAAG;IAC3B,KAAK,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,GAAG,OAAO,GAAG,SAAS,CAAC,CAAC;IAC9D,IAAI,CAAC,EAAE,OAAO,CAAC;IACf,0FAA0F;IAC1F,GAAG,CAAC,EAAE,UAAU,CAAC;IACjB,uEAAuE;IACvE,OAAO,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IACjC,MAAM,CAAC,EAAE,WAAW,CAAC;CACtB,CAAC;AAEF,MAAM,MAAM,KAAK,GAAG;IAClB,KAAK,EAAE,UAAU,CAAC;IAClB,WAAW,EAAE,MAAM,CAAC;IACpB,kEAAkE;IAClE,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,2EAA2E;IAC3E,SAAS,EAAE,OAAO,CAAC;IACnB;;;;;;OAMG;IACH,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB;;;;;;;;;;;;OAYG;IACH,MAAM,CAAC,EAAE;QAAE,KAAK,EAAE,MAAM,CAAC;QAAC,GAAG,EAAE,MAAM,CAAC;QAAC,KAAK,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC;IACxD;;;;;;;OAOG;IACH,WAAW,EAAE,OAAO,CAAC;CACtB,CAAC;AAeF;;;;;;;;;;;;GAYG;AACH,eAAO,MAAM,2BAA2B,SAAU,CAAC;AACnD,6EAA6E;AAC7E,eAAO,MAAM,wBAAwB,IAAI,CAAC;AAe1C;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,eAAO,MAAM,aAAa,QAAO,OAAO,UAAU,CAAC,KAG7B,CAAC;AAEvB,iDAAiD;AACjD,MAAM,MAAM,QAAQ,GAAG;IAAE,KAAK,EAAE,MAAM,CAAC;IAAC,IAAI,EAAE,OAAO,CAAA;CAAE,CAAC;AAExD;;;;;;;;;;;GAWG;AACH,qBAAa,GAAG;;IACd,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;gBAQb,MAAM,EAAE,MAAM,EAAE,OAAO,GAAE,MAAyB,EAAE,MAAM,CAAC,EAAE,WAAW;IAqDpF;;;;;;;;;;;OAWG;IACH,IAAI,CAAC,MAAM,EAAE,WAAW,GAAG,SAAS,GAAG,GAAG;IA0M1C;;;;;;;;;;;;OAYG;IACG,IAAI,CAAC,CAAC,GAAG,OAAO,EAAE,MAAM,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,GAAE,cAAmB,GAAG,OAAO,CAAC,CAAC,CAAC;IAW5F;;;;;;OAMG;IACG,IAAI,CAAC,CAAC,GAAG,OAAO,EACpB,MAAM,EAAE,MAAM,EACd,IAAI,EAAE,MAAM,EACZ,IAAI,GAAE,cAAmB,GACxB,OAAO,CAAC,CAAC,GAAG,SAAS,CAAC;IAKzB;;;;;;;;;;;;;;OAcG;IACG,OAAO,CAAC,CAAC,EACb,IAAI,EAAE,MAAM,EACZ,IAAI,GAAE,cAAmB,GACxB,OAAO,CAAC;QAAE,KAAK,EAAE,CAAC,GAAG,SAAS,CAAC;QAAC,UAAU,EAAE,MAAM,GAAG,IAAI,CAAA;KAAE,CAAC;IAY/D,kFAAkF;IAC5E,KAAK,CACT,MAAM,EAAE,MAAM,EACd,IAAI,EAAE,MAAM,EACZ,IAAI,GAAE,cAAmB,EACzB,QAAQ,CAAC,EAAE,MAAM,GAAG,CAAC,CAAC,WAAW,EAAE,MAAM,KAAK,MAAM,CAAC,GACpD,OAAO,CAAC,KAAK,CAAC;IAqEjB;;;;;;OAMG;IACI,GAAG,CAAC,MAAM,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,GAAE,cAAmB,GAAG,cAAc,CAAC,QAAQ,CAAC;CAoE9F;AA0YD,wEAAwE;AACxE,wBAAgB,YAAY,CAAC,WAAW,EAAE,MAAM,GAAG,IAAI,GAAG,MAAM,GAAG,SAAS,CAuB3E"}
+{"version":3,"file":"api.d.ts","sourceRoot":"","sources":["../src/api.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,KAAK,EAAmE,MAAM,QAAQ,CAAC;AAYhG,eAAO,MAAM,gBAAgB,wCAAwC,CAAC;AAEtE,0EAA0E;AAC1E,eAAO,MAAM,gBAAgB,gBAAgB,CAAC;AAE9C,MAAM,MAAM,cAAc,GAAG;IAC3B,KAAK,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,GAAG,OAAO,GAAG,SAAS,CAAC,CAAC;IAC9D,IAAI,CAAC,EAAE,OAAO,CAAC;IACf,0FAA0F;IAC1F,GAAG,CAAC,EAAE,UAAU,CAAC;IACjB,uEAAuE;IACvE,OAAO,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IACjC,MAAM,CAAC,EAAE,WAAW,CAAC;CACtB,CAAC;AAEF,MAAM,MAAM,KAAK,GAAG;IAClB,KAAK,EAAE,UAAU,CAAC;IAClB,WAAW,EAAE,MAAM,CAAC;IACpB,kEAAkE;IAClE,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,2EAA2E;IAC3E,SAAS,EAAE,OAAO,CAAC;IACnB;;;;;;OAMG;IACH,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB;;;;;;;;;;;;OAYG;IACH,MAAM,CAAC,EAAE;QAAE,KAAK,EAAE,MAAM,CAAC;QAAC,GAAG,EAAE,MAAM,CAAC;QAAC,KAAK,CAAC,EAAE,MAAM,CAAA;KAAE,CAAC;IACxD;;;;;;;OAOG;IACH,WAAW,EAAE,OAAO,CAAC;CACtB,CAAC;AA6BF;;;;;;;;;;;;GAYG;AACH,eAAO,MAAM,2BAA2B,SAAU,CAAC;AACnD,6EAA6E;AAC7E,eAAO,MAAM,wBAAwB,IAAI,CAAC;AAC1C,eAAO,MAAM,mBAAmB,OAG9B,CAAC;AAWH;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,eAAO,MAAM,aAAa,QAAO,OAAO,UAAU,CAAC,KAG7B,CAAC;AAEvB,iDAAiD;AACjD,MAAM,MAAM,QAAQ,GAAG;IAAE,KAAK,EAAE,MAAM,CAAC;IAAC,IAAI,EAAE,OAAO,CAAA;CAAE,CAAC;AAExD;;;;;;;;;;;GAWG;AACH,qBAAa,GAAG;;IACd,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;gBAQb,MAAM,EAAE,MAAM,EAAE,OAAO,GAAE,MAAyB,EAAE,MAAM,CAAC,EAAE,WAAW;IAoDpF;;;;;;;;;;;OAWG;IACH,IAAI,CAAC,MAAM,EAAE,WAAW,GAAG,SAAS,GAAG,GAAG;IAiP1C;;;;;;;;;;;;OAYG;IACG,IAAI,CAAC,CAAC,GAAG,OAAO,EAAE,MAAM,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,GAAE,cAAmB,GAAG,OAAO,CAAC,CAAC,CAAC;IAW5F;;;;;;OAMG;IACG,IAAI,CAAC,CAAC,GAAG,OAAO,EACpB,MAAM,EAAE,MAAM,EACd,IAAI,EAAE,MAAM,EACZ,IAAI,GAAE,cAAmB,GACxB,OAAO,CAAC,CAAC,GAAG,SAAS,CAAC;IAKzB;;;;;;;;;;;;;;OAcG;IACG,OAAO,CAAC,CAAC,EACb,IAAI,EAAE,MAAM,EACZ,IAAI,GAAE,cAAmB,GACxB,OAAO,CAAC;QAAE,KAAK,EAAE,CAAC,GAAG,SAAS,CAAC;QAAC,UAAU,EAAE,MAAM,GAAG,IAAI,CAAA;KAAE,CAAC;IAY/D,kFAAkF;IAC5E,KAAK,CACT,MAAM,EAAE,MAAM,EACd,IAAI,EAAE,MAAM,EACZ,IAAI,GAAE,cAAmB,EACzB,QAAQ,CAAC,EAAE,MAAM,GAAG,CAAC,CAAC,WAAW,EAAE,MAAM,KAAK,MAAM,CAAC,GACpD,OAAO,CAAC,KAAK,CAAC;IAoFjB;;;;;;OAMG;IACI,GAAG,CAAC,MAAM,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,GAAE,cAAmB,GAAG,cAAc,CAAC,QAAQ,CAAC;CAsF9F;AAyCD;;;;;;;;;GASG;AACH,wBAAiB,MAAM,CAAC,GAAG,EAAE,OAAO,EAAE,KAAK,SAAI,GAAG,SAAS,CAAC,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC,CAQnF;AAkgBD,wEAAwE;AACxE,wBAAgB,YAAY,CAAC,WAAW,EAAE,MAAM,GAAG,IAAI,GAAG,MAAM,GAAG,SAAS,CAmD3E"}