@aotter/mantle 0.1.4 → 0.2.0-alpha.1

package/README.md

@@ -1,319 +1,52 @@
 # @aotter/mantle
 
-Umbrella entry for the embeddable Mantle SDK — a manifest-driven application
-engine built around a 4-atom YAML model (Schema / View / Procedure / Trigger)
-where agents write config and the runtime carries the complexity.
+Mantle is a manifest-driven service core. A service declares Schemas, Views,
+Procedures and Triggers in YAML. Views and Procedures are SQL
+(PostgreSQL syntax). `mantle generate` compiles them into a sealed plan and a
+typed module. The runtime serves the plan through one Store, which adds each
+caller's scope, TTL, publishing state and optimistic locks to every statement.
 
-> Mantle's first stable release is `0.1.2`. Use this package's `package.json`
-> as the exact installed version.
+## Subpaths
 
-## Install
+Each folder of `src/` is one subpath. `check:boundaries` enforces what each may
+import.
 
-Cold start for a new application is the install skill, not a bare npm add:
-
-```sh
-npx skills add aotter/mantle
-```
-
-To depend on this package in an existing project, pin the exact version
-from `package.json` (currently `0.1.4`):
-
-```bash
-npm install @aotter/mantle
-# or
-pnpm add @aotter/mantle
-```
-
-## What's inside
-
-The umbrella provides Spec and Runtime by default. Install an optional package
-before importing its matching Web, Admin, Auth, Bun, Vercel, Cloudflare, or Admin UI
-subpath. Every sub-package also remains directly installable.
-
-| Subpath | Re-exports |
+| Subpath | Contents |
 |---|---|
-| `@aotter/mantle/spec` (or root) | Manifest grammar, validators, JSON-Schema→Zod, diagnostic catalog (no env / no IO) |
-| `@aotter/mantle/runtime` | Hexagonal runtime: domain ports, use cases, infrastructure helpers (no adapter deps) |
-| `@aotter/mantle/runtime/testing` | Node-only crowded SQLite planner and HTTP sampling helpers |
-| `@aotter/mantle/codegen` | Pure linked manifests or compiled plan → typed runtime module emitter (no IO) |
-| `@aotter/mantle/web` | Optional HTML, Markdown, `llms.txt`, sitemap, SEO, and preview composition (no routes or platform deps) |
-| `@aotter/mantle/admin` | Optional Admin API, auth routes, and static-asset composition |
-| `@aotter/mantle/auth` | Optional host-neutral Better Auth identity; adapters own IP headers and storage bindings |
-| `@aotter/mantle/bun` | Bun adapter — caller-owned `bun:sqlite` and Web-standard View/Trigger transport |
-| `@aotter/mantle/vercel` | Vercel Functions adapter — injected durable storage and platform `waitUntil` |
-| `@aotter/mantle/vercel/libsql` | Optional application-owned Turso/libSQL driver |
-| `@aotter/mantle/cloudflare` | Cloudflare Workers adapter — D1, Workers Cache, R2, and Better Auth 1.7 MCP/CIMD |
-| `@aotter/mantle/admin-ui` | Pre-built React 19 admin SPA bundle |
-
-```ts
-import { linkManifestSet, parseManifestSources } from "@aotter/mantle/spec";
-import { bootMantleRuntime, compileRuntimePlan } from "@aotter/mantle/runtime";
-import { createMantleWeb } from "@aotter/mantle/web";
-import { mountRuntimeEndpoints } from "@aotter/mantle/cloudflare";
-```
-
-The umbrella installs only Spec and Runtime. Web, Admin, Auth, Admin UI, Bun,
-Vercel, and Cloudflare are optional peers; install only the subpaths selected
-by the application.
-
-The package also installs `mantle` and `mantle-harness`:
-
-```bash
-pnpm exec mantle generate
-pnpm exec mantle generate --check
-pnpm exec mantle skills
-pnpm exec mantle skills --check
-pnpm exec mantle-harness indexes --require-public
-pnpm exec mantle-harness http --base-url http://127.0.0.1:8787 --route page=/en/example
-```
-
-`mantle generate` validates and compiles `./manifests/`, then writes one typed
-`.mantle/generated/mantle.ts` module. When `@aotter/mantle-admin-ui` is
-installed, it also syncs the Admin SPA to `public/_mantle/admin/` (excluding
-`server.*` package exports). Core-only installs skip that copy. It performs no
-skill sync, package update, styling, provisioning, or deployment.
-The same pure emitter is available from `@aotter/mantle/codegen` when a host
-wants to own parsing and filesystem IO. TypeScript-authored manifests can pass
-their already-compiled `plan` directly:
-
-```ts
-import { emitMantleModule } from "@aotter/mantle/codegen";
-
-const emitted = emitMantleModule({ plan });
-if (!emitted.ok) throw new Error(emitted.diagnostics.map(({ message }) => message).join("\n"));
-```
-
-```ts
-import { createMantle } from "../.mantle/generated/mantle.js";
-
-const mantle = await createMantle({ storage, handlers, ports });
-const notes = await mantle.views.publishedNotes();
-const result = await mantle.procedures.expireOrder(
-  { orderId },
-  { user: null, staff: null, env },
-);
-await mantle.entries.orders.createDraft({ data, authorId: user.id });
-
-// The typed projection never hides the underlying Core runtime.
-await mantle.runtime.archive.execute({ id: noteId, ctx });
-```
-
-Generated property names are deterministic lower-camel identifiers; calls keep
-the authored wire names internally. `createMantle()` eagerly prepares once and
-does not cache or retry. Dynamic and platform hosts can keep their own lifecycle,
-use generated `bindMantle(runtime)`, or skip code generation and call
-`runtime.executeView({ view: "published-notes" })` directly.
-
-Author the application directly using [the installed guide](docs/handbook/start/project-and-cli.md).
-Admin is opt-in; use [local Admin OTP](docs/handbook/start/quickstart-admin.md)
-only when humans need a console.
-The CLI has no scaffold/type picker; missing manifests fail without creating
-an application or a visitor home page.
-
-`mantle skills` copies every skill the installed package marks
-`projection: project` in its front matter into matching
-`.agents/skills/mantle-*` and `.claude/skills/mantle-*` paths — no list of
-skill names is maintained anywhere else. Skills that act destructively or
-target one platform stay out of that set and are opt-in. Both tool layouts
-receive identical bytes; `--check` detects drift without writing. An older
-project may also carry `.agent/skills/`, which is left untouched. Manifest
-generation never rewrites agent instructions.
-
-SDK upgrades use the package manager and the version-matched update skill.
-For npm peer-resolution troubleshooting, see [the authoring guide](docs/handbook/start/project-and-cli.md).
-See [Releases](docs/handbook/releases/index.md) for what each stable version
-contains and what it requires.
-
-## Conventional Cloudflare Worker
-
-The normal Worker entry delegates Core-owned assembly to the SDK:
-
-```ts
-import { createMantleWorker } from "@aotter/mantle/cloudflare";
-import { plan } from "../.mantle/generated/mantle.js";
-
-export default createMantleWorker({ plan });
-```
-
-`createMantleWorker` owns conventional D1/assets bindings, Auth, Admin,
-manifest REST/HTTP routes, OAuth, MCP, cache safety, and rejection-safe
-per-isolate boot. Use its single `extend` seam for application handlers and
-new Hono routes; use the public low-level exports when the deployment does not
-fit the conventional binding or lifecycle contract.
-
-Conventional Auth requires an explicit `MANTLE_AUTH_MODE`: `self-managed`
-uses the site's GitHub OAuth credentials, while `hosted` uses a same-origin
-Mantle Hosted Auth PKCE client. Missing, invalid, partial, or mixed-mode
-configuration keeps public routes available but returns `503 setup_incomplete`
-from Auth-owned private routes. Pass `auth: (env) => Auth` only when the site
-needs to replace this conventional factory; Core still owns the Auth routes.
-The exact bindings and validation rules are in the
-`node_modules/@aotter/mantle-cloudflare/README.md`, under “Conventional Auth”
-(path relative to the application root).
-
-Extensions may add routes but may not replace Core surfaces. These paths are
-reserved:
-
-- `/admin` and `/admin/*`
-- `/_mantle` and `/_mantle/*`
-- `/api/auth` and `/api/auth/*`
-- `/api/views` and `/api/views/*`
-- `/oauth` and `/oauth/*`
-- `/mcp` and `/mcp/*`
-- `/.well-known/oauth*`
-- global `*` and `/*` handlers
-
-A custom Auth factory's `basePath` and exact manifest-owned method/path pairs
-are also reserved at assembly. Static literal conflicts fail TypeScript during
-the consumer build. Computed paths cannot be proven statically, so the facade
-checks Hono's assembled route table and fails closed before serving requests.
-There is no standard-route override option.
-
-Cloudflare projects may expose an independently installed Admin bundle and the
-application's own frontend assets through one native binding:
-
-```toml
-[assets]
-directory = "./public"
-binding = "ASSETS"
-```
-
-Declare browser, Admin, and MCP identity once. Multiple renditions are allowed;
-keep SVG as the source and add PNG renditions when a target MCP client requires
-the baseline raster formats:
-
-```ts
-siteDefaults: {
-  icons: [
-    { src: "/site-icon.png", mimeType: "image/png", sizes: ["64x64"] },
-    { src: "/site-icon.svg", mimeType: "image/svg+xml", sizes: ["any"] },
-  ],
-}
-```
-
-Keep both files in the project's `public/` directory. They are one site
-identity reused by browser favicons, Admin chrome, and MCP `serverInfo.icons`;
-PNG is the compatibility rendition and SVG remains the editable source.
-
-For an uncommon deployment that must own the top-level assembly, use the
-embedded [`docs/handbook/cloudflare/low-level-composition.md`](docs/handbook/cloudflare/low-level-composition.md)
-fixture. It composes the same public primitives without importing package
-internals or rebuilding Mantle's adapters.
-
-## Getting started
-
-Cold start from GitHub or a marketplace host:
-
-```sh
-npx skills add aotter/mantle
-```
-
-That skill interviews, pins this package, then uses the CLI and the
-[direct-authoring guide](docs/handbook/start/project-and-cli.md).
-The owner or agent writes the application's manifests, entry and configuration;
-`generate` compiles them and `skills` projects the version-matched instructions.
-The [minimal Worker reference](docs/examples/host-minimal-worker/README.md) is
-the embed / adapter path without Admin. The
-[local Admin OTP reference](docs/examples/host-local-admin-otp/README.md) is the
-opt-in Dev UI path. Neither is a scaffold command. Admin is optional.
-
-## Agent marketplace install
-
-Install the Mantle Core skill bundle before authoring or maintaining a
-consumer application. The canonical command is:
+| `@aotter/mantle` | `createMantle`, `createMantleRuntime`, Store, `Caller`, the handler contract, `withCaller` |
+| `@aotter/mantle/spec` | The manifest grammar, validation and `compilePlan` (the CLI side) |
+| `@aotter/mantle/d1`, `/d1/compile` | The built-in SQLite dialect: runtime and compile sides (ADR-0035) |
+| `@aotter/mantle/postgres`, `/postgres/compile` | The PostgreSQL reference dialect: `postgresStorage`, `pgDatabaseDriver`, `pgPool`, and its compile side (ADR-0037) |
+| `@aotter/mantle/bun` | Native Bun.SQL PostgreSQL, bun:sqlite and Admin assets (ADR-0038) |
+| `@aotter/mantle/cloudflare` | `d1Storage`, `d1Driver`, `r2MediaStorage`, `toCloudflareCron` |
+| `@aotter/mantle/auth` | `createMantleAuth` (Better Auth), `createCallerResolver`, `createAuthRoutes` |
+| `@aotter/mantle/admin` | `createAdminSurface` |
+| `@aotter/mantle/mcp` | `createMcpSurface` |
+| `@aotter/mantle/web` | `createRestSurface` |
+| `@aotter/mantle/testing` | `runStorageConformance`, the dialect compliance suite |
+
+## CLI
 
 ```sh
-npx skills add aotter/mantle
+mantle generate           # manifests + mantle.config.json -> .mantle/generated/, and the preset once
+mantle generate --check   # the gate: fails when anything generated is stale
 ```
 
-Claude Code and Codex can install the plugin, then run that skill:
-
-```bash
-# Claude Code
-/plugin marketplace add aotter/mantle
-/plugin install mantle@mantle
-
-# Codex
-codex plugin marketplace add aotter/mantle
-codex plugin add mantle@mantle
-```
-
-Cursor and VS Code Copilot can auto-discover the GitHub repo through
-`.cursor-plugin/plugin.json` and `.copilot-plugin/plugin.json` after the repo
-is cloned or opened. Still start from the `npx skills add` sentence (or open
-`skills/install/SKILL.md`). Untagged `aotter/mantle` resolves to `main`, which
-can contain a source-only hotfix ahead of the latest npm release. Add
-`@vX.Y.Z` only to reproduce an older project; never point a consumer at
-`develop` or another moving branch.
-
-## Marketplace capability installs
-
-In a consumer application, tell your coding agent:
-
-```txt
-Use repo-local mantle:plugin to install <plugin slug or recipe URL> in this repo.
-Use repo-local mantle:plugin to update <plugin id> in this repo.
-Use repo-local mantle:plugin to remove <plugin id> from this repo.
-```
-
-Mantle marketplace entries are agent-installable recipes. They declare the
-plugin source, Mantle version range, files/atoms/routes/tools, adapter
-requirements, secrets, and checks. The agent applies the recipe through the
-Core-owned `mantle:plugin` skill and records it in `.mantle/plugins.json` plus
-`.mantle/plugins.lock.json`. There is no `mantle plugin add` CLI yet.
-
-## Adapter targets
-
-| Adapter | Status |
-|---|---|
-| Bun | ✅ shipping |
-| Vercel Functions (Node.js) | ✅ shipping |
-| Cloudflare Workers | ✅ shipping |
-
-The `mantle-runtime` package never imports platform-specific types — adapters
-bind concrete storage and lifecycle primitives to Core ports, so adding a new
-adapter is a port-implementation exercise, not a runtime refactor.
-
-## Documentation
-
-- The handbook is the user documentation and ships inside this npm package:
-  `node_modules/@aotter/mantle/docs/handbook/` (start, concepts, Cloudflare
-  guides, example redirects, reference; `navigation.json` lists every page in order).
-  Worked Manifests live in `node_modules/@aotter/mantle/docs/examples/`
-  ([index](docs/examples/README.md)).
-  The copy in `node_modules` describes the installed release.
-- Embedded docs and agent skills ship inside this npm package for
-  agents working from the installed package:
-  - `node_modules/@aotter/mantle/docs/handbook/reference/manifest.md`
-  - `node_modules/@aotter/mantle/docs/examples/cf-primitives-guarded-api.md` (anonymous,
-    API-key, paid guard, personal-token, OAuth, REST, and MCP examples)
-  - `node_modules/@aotter/mantle/docs/handbook/cloudflare/media-r2.md` (Cloudflare R2 adapter recipe)
-  - `node_modules/@aotter/mantle/docs/handbook/cloudflare/deferred-hooks-queues.md` (versioned
-    Queue wiring, retry/DLQ, idempotency, and delivery guarantees)
-  - `node_modules/@aotter/mantle/docs/handbook/reference/schema.md` (Schema grammar,
-    ordered composite JSON-field indexes and the safe Procedure SQL helper)
-  - `node_modules/@aotter/mantle/docs/performance-harness.md` (crowded SQLite,
-    Wrangler-local D1 origin paths and coding-agent guardrails)
-  - `node_modules/@aotter/mantle/docs/adr/`
-  - `node_modules/@aotter/mantle/skills/develop/SKILL.md`
-  - `node_modules/@aotter/mantle/skills/plugin/SKILL.md`
-  - `node_modules/@aotter/mantle/skills/theme/SKILL.md`
-  - `node_modules/@aotter/mantle/skills/update/SKILL.md`
-  - `node_modules/@aotter/mantle/skills/install/SKILL.md`
-  - `node_modules/@aotter/mantle/skills/provision/SKILL.md`
-- [4-atom manifest model (ADR-0001)](docs/adr/0001-four-atom-manifest-model.md)
-- [API and MCP authorization](docs/examples/cf-primitives-guarded-api.md)
-- [Deferred lifecycle Queues](docs/handbook/cloudflare/deferred-hooks-queues.md)
-- [Schema indexes on D1](docs/handbook/reference/schema.md)
-- [Release process](docs/release-process.md)
-- [Source repository](https://github.com/aotter/mantle)
-- [Issues](https://github.com/aotter/mantle/issues)
+While `src/service.ts` does not exist, `mantle generate` writes the service
+preset for the chosen host (ADR-0036): on `cloudflare`, the default,
+`src/service.ts`, `src/index.ts`, `src/handlers.ts`, `wrangler.jsonc`,
+`tsconfig.json`, `.gitignore`, and `.dev.vars.example` with identity `mantle`
+(`src/identity.ts` with `custom`); on `bun`, the same without
+`wrangler.jsonc`, with `.env.example`; on `none`, nothing. It never writes
+those files again, and it never installs packages. It names each missing
+package together with the install command.
 
-## License
+## Start
 
-Apache-2.0
+Read [the reference service](docs/examples/reference-service/README.md).
+It is a whole service with its smoke test. The installed docs are under
+`node_modules/@aotter/mantle/docs/`: the handbook (`handbook/start/overview.md`),
+the examples, the agent workflow skills (`skills/`), and
+`upgrade-0.1-to-0.2.md` for projects on 0.1.x.
 
-Pure extension routes do not await content preparation. Before an extension
-uses Mantle data or database-backed Auth, await its supplied `getRuntime()`
-(or `ref.get()`). Standard protected routes establish this readiness themselves;
-queue/scheduled handlers continue to use `worker.getRuntime(env)`.
+The decisions behind the design are ADR-0032 to ADR-0038 in `docs/adr/`.

package/dist/admin/consent.d.ts

@@ -0,0 +1,17 @@
+/** What the consent screen and the connected-apps list need of an OAuth provider, and the member list's cursor (Admin's, used by the identity provider). */
+export interface OAuthConsentRequest {
+    readonly clientName: string;
+    readonly redirectUri: string;
+    readonly scopes: readonly string[];
+    /** Signed provider query returned unchanged with the consent decision. */
+    readonly oauthQuery: string;
+}
+export interface OAuthConsentInfo {
+    readonly id: string;
+    readonly clientId: string;
+    readonly clientName: string;
+    readonly scopes: readonly string[];
+}
+export declare function encodeMemberCursor(createdAt: string, id: string): string;
+export declare function decodeMemberCursor(cursor: string): readonly [string, string] | null;
+//# sourceMappingURL=consent.d.ts.map

package/dist/admin/consent.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"consent.d.ts","sourceRoot":"","sources":["../../src/admin/consent.ts"],"names":[],"mappings":"AAAA,4JAA4J;AAE5J,MAAM,WAAW,mBAAmB;IAClC,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAC;IAC5B,QAAQ,CAAC,WAAW,EAAE,MAAM,CAAC;IAC7B,QAAQ,CAAC,MAAM,EAAE,SAAS,MAAM,EAAE,CAAC;IACnC,0EAA0E;IAC1E,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAC;CAC7B;AAED,MAAM,WAAW,gBAAgB;IAC/B,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;IACpB,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;IAC1B,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAC;IAC5B,QAAQ,CAAC,MAAM,EAAE,SAAS,MAAM,EAAE,CAAC;CACpC;AAID,wBAAgB,kBAAkB,CAAC,SAAS,EAAE,MAAM,EAAE,EAAE,EAAE,MAAM,GAAG,MAAM,CAExE;AAED,wBAAgB,kBAAkB,CAAC,MAAM,EAAE,MAAM,GAAG,SAAS,CAAC,MAAM,EAAE,MAAM,CAAC,GAAG,IAAI,CAQnF"}

package/dist/admin/consent.js

@@ -0,0 +1,17 @@
+/** What the consent screen and the connected-apps list need of an OAuth provider, and the member list's cursor (Admin's, used by the identity provider). */
+const PREFIX = "m:";
+export function encodeMemberCursor(createdAt, id) {
+    return `${PREFIX}${encodeURIComponent(JSON.stringify([createdAt, id]))}`;
+}
+export function decodeMemberCursor(cursor) {
+    if (!cursor.startsWith(PREFIX))
+        return null;
+    try {
+        const v = JSON.parse(decodeURIComponent(cursor.slice(PREFIX.length)));
+        return Array.isArray(v) && v.length === 2 && typeof v[0] === "string" && !Number.isNaN(Date.parse(v[0])) && typeof v[1] === "string" && v[1] ? [v[0], v[1]] : null;
+    }
+    catch {
+        return null;
+    }
+}
+//# sourceMappingURL=consent.js.map

package/dist/admin/consent.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"consent.js","sourceRoot":"","sources":["../../src/admin/consent.ts"],"names":[],"mappings":"AAAA,4JAA4J;AAiB5J,MAAM,MAAM,GAAG,IAAI,CAAC;AAEpB,MAAM,UAAU,kBAAkB,CAAC,SAAiB,EAAE,EAAU;IAC9D,OAAO,GAAG,MAAM,GAAG,kBAAkB,CAAC,IAAI,CAAC,SAAS,CAAC,CAAC,SAAS,EAAE,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;AAC3E,CAAC;AAED,MAAM,UAAU,kBAAkB,CAAC,MAAc;IAC/C,IAAI,CAAC,MAAM,CAAC,UAAU,CAAC,MAAM,CAAC;QAAE,OAAO,IAAI,CAAC;IAC5C,IAAI,CAAC;QACH,MAAM,CAAC,GAAG,IAAI,CAAC,KAAK,CAAC,kBAAkB,CAAC,MAAM,CAAC,KAAK,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC,CAAY,CAAC;QACjF,OAAO,KAAK,CAAC,OAAO,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,MAAM,KAAK,CAAC,IAAI,OAAO,CAAC,CAAC,CAAC,CAAC,KAAK,QAAQ,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,IAAI,OAAO,CAAC,CAAC,CAAC,CAAC,KAAK,QAAQ,IAAI,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC;IACrK,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,IAAI,CAAC;IACd,CAAC;AACH,CAAC"}

package/dist/admin/createAdminSurface.d.ts

@@ -0,0 +1,22 @@
+import { type MantleRuntime, type MediaStorage, type Surface } from "../core/index.js";
+import type { AdminIdentity } from "./identity.js";
+/** The built SPA: `path` is relative to the base path (`index.html` is the shell). `null` is a missing file. */
+export type AdminAssets = (path: string) => Response | null | Promise<Response | null>;
+export interface AdminSurfaceOptions {
+    /** Where Admin answers, e.g. `/admin`; the API is `{basePath}/api`. */
+    readonly basePath: string;
+    readonly identity?: AdminIdentity;
+    /** The Admin SPA's files (`@aotter/mantle-ui/admin`), which are built for `basePath: "/admin"` only. */
+    readonly assets?: AdminAssets;
+    /** The MCP surfaces the service mounted, as paths or URLs; `/site` resolves them against the public URL. */
+    readonly site?: {
+        readonly mcpEndpoints?: {
+            readonly public: string | null;
+            readonly staff: string | null;
+        };
+    };
+    /** Media objects; the media routes also need `runtime.site`, which owns the tables, and answer 501 without either. */
+    readonly media?: MediaStorage;
+}
+export declare function createAdminSurface(runtime: MantleRuntime, options: AdminSurfaceOptions): Surface;
+//# sourceMappingURL=createAdminSurface.d.ts.map

package/dist/admin/createAdminSurface.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"createAdminSurface.d.ts","sourceRoot":"","sources":["../../src/admin/createAdminSurface.ts"],"names":[],"mappings":"AAOA,OAAO,EAAkD,KAAK,aAAa,EAAmB,KAAK,YAAY,EAAiH,KAAK,OAAO,EAAE,MAAM,kBAAkB,CAAC;AAIvQ,OAAO,KAAK,EAAE,aAAa,EAAiC,MAAM,eAAe,CAAC;AAGlF,gHAAgH;AAChH,MAAM,MAAM,WAAW,GAAG,CAAC,IAAI,EAAE,MAAM,KAAK,QAAQ,GAAG,IAAI,GAAG,OAAO,CAAC,QAAQ,GAAG,IAAI,CAAC,CAAC;AAEvF,MAAM,WAAW,mBAAmB;IAClC,uEAAuE;IACvE,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;IAC1B,QAAQ,CAAC,QAAQ,CAAC,EAAE,aAAa,CAAC;IAClC,wGAAwG;IACxG,QAAQ,CAAC,MAAM,CAAC,EAAE,WAAW,CAAC;IAC9B,4GAA4G;IAC5G,QAAQ,CAAC,IAAI,CAAC,EAAE;QAAE,QAAQ,CAAC,YAAY,CAAC,EAAE;YAAE,QAAQ,CAAC,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC;YAAC,QAAQ,CAAC,KAAK,EAAE,MAAM,GAAG,IAAI,CAAA;SAAE,CAAA;KAAE,CAAC;IAC9G,sHAAsH;IACtH,QAAQ,CAAC,KAAK,CAAC,EAAE,YAAY,CAAC;CAC/B;AAwGD,wBAAgB,kBAAkB,CAAC,OAAO,EAAE,aAAa,EAAE,OAAO,EAAE,mBAAmB,GAAG,OAAO,CA0chG"}