dsh-connect 0.9.0 → 0.9.2

package/lib/settings/namespace.d.ts

@@ -1,55 +1,130 @@
 /**
- * The `dsh-connect` user-settings namespace.
+ * The `dsh-connect` user-settings seam.
  *
- * DSH ships a first-party user-settings seam (`ctx.settings`, backed by
- * `$DSH_HOME/settings.yaml` via `@deepseek-ai/dsh-settings-file`, hot-reloaded,
- * atomic, file-locked, comment-preserving). Registering a namespace is how a
- * plugin makes its configuration user-editable *and effective*: the official
- * Plugins page renders the fields from the schema, writes go through the
- * provider, and `scope.watch()` tells the plugin to re-read.
+ * DSH 0.2 replaced the plugin-facing settings API. The old `ctx.settings`
+ * namespace contract (`installSection(owner, ns, schema, entry, hooks)` backed by
+ * a `$DSH_HOME/settings.yaml` section keyed by the plugin *name*) is gone; what
+ * is left is `SettingsForms`, which edits a plugin's **profile entry** and
+ * hot-commits the fields that plugin declared `volatile`:
  *
- * Two properties of that seam shape this module:
+ * - **Reads come from our own config.** A field declared with
+ *   `z.…volatile()` arrives in `apply()` as a *reference* (`{ get() }`) rather
+ *   than a value, and the loader updates that reference in place when the
+ *   profile entry changes — no remount, no `apply()` re-entry. So there is no
+ *   read API to call: the live state is `refs.get()`, and this module's
+ *   `materializeConfig()` turns the ref-carrying config into a plain snapshot.
+ * - **Writes go through `SettingsForms.replace(ns, section)`**, where `ns` is
+ *   the profile entry id (`connect`) — *not* the package name. `replace` resets
+ *   every live field to its inherited value and then applies the supplied ones,
+ *   which is exactly "this is the user's complete visible config" — and why a
+ *   *partial* section is a destructive write: a field the caller omits is
+ *   reset, not preserved. Callers that mean to preserve something must merge
+ *   it in first ({@link mergeSections}).
+ * - **`volatileForm(schema)` must not be empty**, or `replace` refuses the
+ *   write with `Plugin entry "connect" has no volatile fields`. That is why
+ *   `paneConfigFields()` exists and must keep declaring the pane's field set.
  *
- * - **`installSection` is the consumer entry point.** It registers the plugin's
- *   own composition entry as the schema's *base* layer while the settings
- *   service is present, and falls back to that entry if the service detaches.
- *   Bare `register` would make `$DSH_HOME/settings.yaml` the only source and
- *   silently drop a YAML-configured profile.
- * - **The schema is applied to `mergeLayers(base, userSection)` at registration
- *   time**, so a stored section that fails validation throws out of
- *   `installSection`. Every install here is therefore guarded: a hand-edited
- *   `settings.yaml` with a typo must degrade to the plugin config, not abort
- *   the plugin's `apply`.
+ * **Only volatile *leaves* may be declared — never a volatile container.**
+ * `projectForm(form, base)` projects the *base* layer down to volatile fields
+ * before the write is merged: if `feishu` itself were volatile it would be
+ * copied whole into the settings document, `appSecret` and all. Declaring the
+ * leaves keeps every non-pane key (`appSecret`, `appId`, …) in the raw
+ * remainder, where `strip()` leaves ordinary config untouched. This is the same
+ * hazard `sectionOf()` guards on the write path, from the other side: an
+ * undeclared key in a *submitted* section must not reach the document either.
  *
- * **Secrets are deliberately not part of this schema.** They live in the DSH
- * credential store (`ctx.credentials`), which is where the onboarding flow and
- * the `FEISHU_*`-style env layering already put them; `settings.yaml` is a
- * plain document users are invited to paste into bug reports. `sectionOf()`
- * projects secret keys *out* of the base for the same reason — schemastery
- * preserves undeclared keys verbatim, so anything left in the base rides out
- * through `describe()` and the settings RPC. The same projection guards the
- * write path (`LiveConnectSection.write`), which is the mirror hazard: an
- * undeclared key in a *submitted* section would be preserved into the document.
- *
- * `installSection` returns nothing, so the write handle it hands back is built
- * here: `setSource` already wires a thunk onto `scope.get()`, which reads the
- * registration's resolved value at call time — live in both directions.
+ * Secrets therefore never appear in either declared surface: they live in the
+ * DSH credential store (`ctx.credentials`), which is where onboarding and the
+ * `FEISHU_*`-style env layering already put them, and `settings`-side documents
+ * are plain files users are invited to paste into bug reports.
  *
  * @module dsh-connect/settings/namespace
  */
 import z from "@deepseek-ai/schemastery";
-import { type ChannelName, type ChannelsConfig, type LoggerLike } from "./channels.js";
-/** The settings namespace this plugin owns. */
-export declare const CONNECT_SETTINGS_NS = "dsh-connect";
+import { type ChannelName, type LoggerLike } from "./channels.js";
+/**
+ * The section key the pre-0.2 harness read from `$DSH_HOME/settings.yaml`, keyed
+ * by plugin *name*. Nothing writes it any more; `legacy-import.ts` reads it once
+ * so an upgrading user's pane settings survive the switch to the new store.
+ */
+export declare const LEGACY_CONNECT_SECTION = "dsh-connect";
+/**
+ * The automatic-page policy for our entry. `auto: false` stops the host's
+ * Plugins page from generating a second, generic form for `connect`: this
+ * plugin ships its own client pane (`client/settings-client.mjs`), and two
+ * editors writing the same fields through different UIs is how a save silently
+ * reverts. Register it with `settings.configure(policy, ctx.fiber)` — the
+ * `owner` argument matters, see `index.ts`.
+ */
+export declare const CONNECT_PRESENTATION: Record<string, unknown>;
+/** A config reference: a stable handle whose value the loader replaces in place. */
+export interface ConfigRef<T = unknown> {
+    /** The current immutable snapshot; `undefined` for a field absent from the config. */
+    get(): T;
+}
+/** Whether a parsed config value is a volatile reference rather than plain data. */
+export declare function isConfigRef(value: unknown): value is ConfigRef;
+/**
+ * Copy a ref-carrying config into plain data: every reference replaced by its
+ * current snapshot, recursively, so callers can hand the result to code that
+ * only understands plain objects (the adapters, the settings pane, tests).
+ *
+ * The copy is *fresh* rather than the snapshot itself, deliberately: snapshots
+ * are deeply frozen, and both `ChannelRuntime` (which spreads a channel's
+ * config into a new object) and the pane (which holds a form to edit) want
+ * mutable data. Cycles in ordinary config are tolerated via `seen`; a snapshot
+ * cannot contain references (the loader commits plain data), but the walk
+ * treats them uniformly so it does not matter.
+ *
+ * **A key that materializes to `undefined` is dropped, not copied.** Every
+ * declared volatile leaf is present in the parsed config even when the profile
+ * never set it — `z.object({transport: z.any().volatile()})` resolves an absent
+ * `transport` to a reference to `undefined` — so a faithful copy would hand the
+ * adapters `{transport: undefined, language: undefined, …}`. That is not the
+ * same as absent: `ChannelRuntime` resolves a channel as
+ * `{...channelDefaults, ...overrides}`, and since `language` is a key of *both*
+ * tables, a channel's own `language: undefined` would mask the shared
+ * `channelDefaults.language` every other channel still gets. Config here is
+ * JSON-shaped (a profile entry, a YAML document, the settings RPC), where
+ * `undefined` can only ever mean "this key was not set", so dropping it restores
+ * exactly the shape a plain `z.any()` field used to produce.
+ */
+export declare function materializeConfig<T>(value: T): T;
+/**
+ * The volatile half of the plugin `Config`, derived from the same field tables
+ * the settings pane renders. Deriving rather than restating them is the point:
+ * a field added to `CHANNEL_CONFIG_FIELDS` becomes user-editable *and*
+ * hot-appliable in one edit, and a field the pane offers can never be missing
+ * from the schema (a write of an undeclared path is refused by the host).
+ *
+ * Every leaf is `z.any()` on purpose. A stricter node would let a stale value
+ * in a profile — a `webhookPort` written as a string, a `dmMode` from a version
+ * that spelled it differently — abort config validation and keep the bridge
+ * from loading at all. The pane's own `coerceConfigValue` is what keeps types
+ * honest; the schema's job here is only to say "these paths are live-editable".
+ *
+ * `channels` is a loose `z.array(z.string())` for the same reason, and it is
+ * safe because `ChannelRuntime` skips a name it has no adapter for (with a log
+ * line) instead of throwing. Its explicit `.default([...CHANNELS])` is load
+ * bearing, not cosmetic: a volatile *array* resolves an absent key to `[]`
+ * rather than `undefined`, so a profile that never set `channels` would
+ * otherwise materialize an empty list and start no adapter at all, where the
+ * documented default — and the pre-volatile behaviour — is every channel. A
+ * default also keeps `replace()`'s reset target honest: an omitted `channels`
+ * in a section resets to all channels, not to none. `[...CHANNELS]` rather than
+ * `CHANNELS` so the schema cannot hand out the module's own array.
+ */
+export declare function paneConfigFields(): Record<string, z<any>>;
 /** Channel-agnostic defaults section of the namespace. */
 export type ConnectSectionDefaults = Record<string, unknown> & {
     language?: string;
     notifyLevel?: string;
 };
 /**
- * The resolved namespace value. Every field is optional: a user who only ever
- * edits `channels` leaves the rest absent, and each adapter applies its own
- * default for anything missing.
+ * The pane-editable slice of the config: the whole of what this plugin stores
+ * on the user's behalf. Every field is optional — a user who only ever edits
+ * `channels` leaves the rest absent, and each adapter applies its own default
+ * for anything missing.
  */
 export interface ConnectSection {
     channels?: ChannelName[];
@@ -59,117 +134,130 @@ export interface ConnectSection {
     dingtalk?: Record<string, unknown>;
     web?: Record<string, unknown>;
 }
+export interface SectionOptions {
+    /**
+     * Materialize `channels` even when the source omits the key. True (the
+     * default) for the *write* path: there an absent key means "the caller did
+     * not speak to the channel list", and a section without `channels` handed to
+     * `replace()` is a reset — reading it as "activate nothing" would switch
+     * every adapter off. False for the legacy import, where an absent key must
+     * stay absent so the profile's own `channels` keeps applying.
+     *
+     * Note this is about the *key being absent*, not about an empty array: a user
+     * who unchecks every channel saves `channels: []`, which is an explicit
+     * "none" and is left alone.
+     */
+    defaultChannels?: boolean;
+}
 /**
- * The namespace schema, derived from the same field tables the settings pane
- * renders. Deriving rather than restating them is the point: a field added to
- * `CHANNEL_CONFIG_FIELDS` becomes user-editable and hot-appliable in one edit,
- * and a field that the pane exposes can never be silently unrepresentable in
- * `settings.yaml`.
+ * Project a config onto the pane's field set: declared, non-secret keys only.
+ *
+ * Two callers, one guard. For a **read** the input is a materialized snapshot
+ * of our own config (a profile may legitimately carry `appSecret`, and it must
+ * not travel out through the snapshot the pane receives); for a **write** the
+ * input is untrusted JSON from the settings RPC, and an undeclared key would
+ * otherwise be preserved into the profile by schemastery's passthrough. Both
+ * are the same projection, so both get the same answer.
  *
- * `required(false)` on every field means an absent key stays absent — it does
- * *not* materialize a default. That matters for `dmMode`, whose first option is
- * the permissive one: a schema-provided default would silently open DMs for
- * every user who never touched the field.
+ * `channels` is emitted unconditionally on the write path because an absent
+ * array resolves to `[]` (schemastery's array default), which would read as
+ * "activate nothing". Unknown channel names are dropped rather than refused:
+ * a name this version does not know is not a reason to reject the whole save.
  */
-export declare const ConnectSectionSchema: z<Schemastery.ObjectS<{
-    channels: z<ChannelName[], ChannelName[]>;
-    channelDefaults: z<any, any>;
-    feishu: z<any, any>;
-    telegram: z<any, any>;
-    dingtalk: z<any, any>;
-    web: z<any, any>;
-}>, Schemastery.ObjectT<{
-    channels: z<ChannelName[], ChannelName[]>;
-    channelDefaults: z<any, any>;
-    feishu: z<any, any>;
-    telegram: z<any, any>;
-    dingtalk: z<any, any>;
-    web: z<any, any>;
-}>>;
+export declare function sectionOf(config: unknown, options?: SectionOptions): ConnectSection;
 /**
- * Project a channel config onto the namespace's schema: only declared,
- * non-secret keys, with `channels` always present.
- *
- * `channels` is emitted unconditionally because an absent array resolves to
- * `[]` (schemastery's array default), which would read as "activate nothing".
+ * Layer one section over another: for each channel and for the shared defaults,
+ * the override's own keys win and the base's surviving keys are kept.
  *
- * Secret keys are dropped here, not by the schema: `redactSecrets` only strips
- * nodes declared with `role("secret")`, and we declare none — so the projection
- * is what keeps an `appSecret` from a legacy profile out of the settings
- * document and off the RPC.
- *
- * The argument is typed `unknown` because this doubles as the *write* guard:
- * a section submitted through the settings RPC is untrusted JSON, and it must
- * go through the same projection before it can reach the document.
+ * This exists because of how `replace()` treats an omission — see the module
+ * doc. A caller that has a section in force and only wants to change part of it
+ * must merge, never pass the part alone: `feishu: { transport }` resets every
+ * other declared `feishu` field, and a section without `channels` resets the
+ * channel list itself, which switches every adapter off.
  */
-export declare function sectionOf(config: unknown): ConnectSection;
+export declare function mergeSections(base: ConnectSection, override: ConnectSection): ConnectSection;
 /**
- * The slice of the settings service this module calls. Declared structurally so
- * the plugin keeps no dependency on `@deepseek-ai/dsh-settings` — the service is
- * a `dsh-base` row, present whenever dsh-connect loads, and a missing method
- * degrades to "no settings support" rather than a crash.
+ * The slice of `SettingsForms` this module calls. Declared structurally so the
+ * plugin keeps no dependency on `@deepseek-ai/dsh-settings` (a `dsh-base` row we
+ * cannot import at build time): a missing method degrades to "no live store"
+ * rather than a crash, and the settings service falls back to its JSON file.
  */
 export interface SettingsProviderLike {
-    installSection?(owner: unknown, ns: string, schema: unknown, entry: unknown, hooks: {
-        setSource: (source: () => unknown) => void;
-        onChange: () => void;
-    }): void;
-    /** Resolved value of a registered namespace, `undefined` while unregistered. */
-    get?(ns: string): unknown;
     /**
-     * Replace a registered namespace's *user* section wholesale (validated by the
-     * provider, persisted by whichever file provider is wired up). Resolves after
-     * the new value is committed, so a read straight after it is fresh.
+     * Register this plugin instance's page policy. `owner` must be the plugin's
+     * own fiber — the default is the *service's* fiber, which would make the
+     * policy invisible to this instance's page and leak on every reload.
+     * @returns Disposer; register it with the plugin's effects.
+     */
+    configure?(presentation: Record<string, unknown>, owner?: unknown): () => void;
+    /**
+     * Reset every live field to its inherited value, then apply `section`;
+     * ordinary (non-live) config is preserved.
      *
-     * Replace rather than merge, because the settings pane always submits its
-     * complete visible config: a merge would make a cleared field un-clearable
-     * (the stale value stays in the user layer and reappears on the next read).
-     * The declared-key set is identical for both writers of this namespace (this
-     * plugin's pane and the host's own Plugins page, which renders the same
-     * schema), so a replace cannot drop anything either surface can produce.
+     * `expectedRevision` is deliberately omitted by every caller here: `write`
+     * only enforces the revision check when it is defined, and we read our state
+     * from config references rather than from `describe()`, so there is no
+     * revision to round-trip. Two concurrent editors of the pane would still both
+     * land, last write winning — the same behaviour the JSON store had.
      */
     replace?(ns: string, section: unknown, expectedRevision?: number): Promise<unknown>;
 }
-/** A live handle onto the installed namespace: read the effective section, write a new one. */
+/** A live handle onto the profile entry: read the effective section, write a new one. */
 export interface LiveConnectSection {
-    /** The section in force right now (base layered under the user's section). */
+    /** The section in force right now, read from the config references. */
     read(): ConnectSection;
     /**
-     * Replace the user's section with the declared-key projection of `config`.
-     * Rejects if the provider's schema refuses the result — the caller is
-     * expected to surface that rather than swallow it.
+     * Replace the user's section with the declared-key projection of `config`,
+     * then hand the new section to `onChange`. Rejects if the host refuses the
+     * write (a non-volatile path, a missing entry) — the caller is expected to
+     * surface that rather than swallow it.
      */
     write(config: unknown): Promise<void>;
 }
-/** Outcome of wiring the namespace. */
+/** Outcome of wiring the seam. */
 export interface InstallConnectSectionResult {
-    /** True when this fiber owns the namespace and receives live updates. */
+    /** True when a write handle exists, i.e. a save can land and take effect. */
     live: boolean;
-    /** The section in force at install time (resolved, or the entry fallback). */
+    /** The section in force at install time. */
     section: ConnectSection;
-    /**
-     * Read/write onto the registration. Present only when this fiber owns a live
-     * namespace *and* the provider exposes a write method; otherwise the caller
-     * keeps its own fallback (the plugin config, or the legacy state file).
-     */
+    /** Read/write onto the profile entry; absent when the seam is unavailable. */
     handle?: LiveConnectSection;
 }
 export interface InstallConnectSectionOptions<Ctx extends LoggerLike> {
-    /** Context whose unload releases the registration. */
+    /** The plugin's own context: `logger` for diagnostics, and the fallback owner. */
     owner: Ctx;
     settings: SettingsProviderLike | undefined;
-    /** The plugin's own config: the schema's `base` layer and the fallback. */
-    entry: ChannelsConfig | null | undefined;
-    /** Called with the in-force section now and on every change. */
+    /** The ref-carrying config this plugin was applied with (see `materializeConfig`). */
+    config: unknown;
+    /** The profile entry id (`connect`), from the loader entry. */
+    ns: string | undefined;
+    /** Called with the in-force section at install and after every successful write. */
     onChange: (section: ConnectSection) => void;
 }
 /**
- * Register `dsh-connect` and report the section in force.
+ * Wire the plugin's config references to the host's settings service.
  *
- * Never throws: a missing settings service, an already-claimed namespace, or a
- * `settings.yaml` section that fails validation all fall back to the plugin's
- * own config with a warning. A user's typo in a settings document must not be
- * able to stop the bridge from starting.
+ * Never throws. A host without `SettingsForms`, a context where the entry id
+ * cannot be resolved (a bare unit-test context, or a plugin mounted outside the
+ * loader) and a refused `replace` all degrade to `live: false` with one warning
+ * line — a settings integration that cannot work must never be the reason a
+ * bridge fails to start.
  */
 export declare function installConnectSection<Ctx extends LoggerLike>(options: InstallConnectSectionOptions<Ctx>): InstallConnectSectionResult;
+declare module "@deepseek-ai/cordis" {
+    interface Events {
+        /**
+         * Dispatched to the owning fiber when the loader commits changed volatile
+         * config paths **in place**, without remounting the plugin — a settings-pane
+         * save, or an edit to a running profile's patch. The payload is the changed
+         * paths; a consumer re-reads the references it was applied with
+         * ({@link materializeConfig}) rather than being told the new values.
+         *
+         * Declared here because cordis's `on()` typechecks event names against this
+         * interface and nothing this plugin depends on names the event — an
+         * undeclared name would be a type error at the only call site (`index.ts`).
+         */
+        "loader/volatile-update"(paths: readonly (readonly string[])[]): void;
+    }
+}
 //# sourceMappingURL=namespace.d.ts.map

package/lib/settings/namespace.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"namespace.d.ts","sourceRoot":"","sources":["../../src/settings/namespace.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAsCG;AAEH,OAAO,CAAC,MAAM,0BAA0B,CAAC;AACzC,OAAO,EAAY,KAAK,WAAW,EAAE,KAAK,cAAc,EAAE,KAAK,UAAU,EAAE,MAAM,eAAe,CAAC;AAOjG,+CAA+C;AAC/C,eAAO,MAAM,mBAAmB,gBAAgB,CAAC;AAEjD,0DAA0D;AAC1D,MAAM,MAAM,sBAAsB,GAAG,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG;IAAE,QAAQ,CAAC,EAAE,MAAM,CAAC;IAAC,WAAW,CAAC,EAAE,MAAM,CAAA;CAAE,CAAC;AAE3G;;;;GAIG;AACH,MAAM,WAAW,cAAc;IAC7B,QAAQ,CAAC,EAAE,WAAW,EAAE,CAAC;IACzB,eAAe,CAAC,EAAE,sBAAsB,CAAC;IACzC,MAAM,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IACjC,QAAQ,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IACnC,QAAQ,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IACnC,GAAG,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CAC/B;AAyBD;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,oBAAoB;;;;;;;;;;;;;;GAO/B,CAAC;AAEH;;;;;;;;;;;;;;;GAeG;AACH,wBAAgB,SAAS,CAAC,MAAM,EAAE,OAAO,GAAG,cAAc,CAoBzD;AAED;;;;;GAKG;AACH,MAAM,WAAW,oBAAoB;IACnC,cAAc,CAAC,CACb,KAAK,EAAE,OAAO,EACd,EAAE,EAAE,MAAM,EACV,MAAM,EAAE,OAAO,EACf,KAAK,EAAE,OAAO,EACd,KAAK,EAAE;QAAE,SAAS,EAAE,CAAC,MAAM,EAAE,MAAM,OAAO,KAAK,IAAI,CAAC;QAAC,QAAQ,EAAE,MAAM,IAAI,CAAA;KAAE,GAC1E,IAAI,CAAC;IACR,gFAAgF;IAChF,GAAG,CAAC,CAAC,EAAE,EAAE,MAAM,GAAG,OAAO,CAAC;IAC1B;;;;;;;;;;;OAWG;IACH,OAAO,CAAC,CAAC,EAAE,EAAE,MAAM,EAAE,OAAO,EAAE,OAAO,EAAE,gBAAgB,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC,OAAO,CAAC,CAAC;CACrF;AAED,+FAA+F;AAC/F,MAAM,WAAW,kBAAkB;IACjC,8EAA8E;IAC9E,IAAI,IAAI,cAAc,CAAC;IACvB;;;;OAIG;IACH,KAAK,CAAC,MAAM,EAAE,OAAO,GAAG,OAAO,CAAC,IAAI,CAAC,CAAC;CACvC;AAED,uCAAuC;AACvC,MAAM,WAAW,2BAA2B;IAC1C,yEAAyE;IACzE,IAAI,EAAE,OAAO,CAAC;IACd,8EAA8E;IAC9E,OAAO,EAAE,cAAc,CAAC;IACxB;;;;OAIG;IACH,MAAM,CAAC,EAAE,kBAAkB,CAAC;CAC7B;AAED,MAAM,WAAW,4BAA4B,CAAC,GAAG,SAAS,UAAU;IAClE,sDAAsD;IACtD,KAAK,EAAE,GAAG,CAAC;IACX,QAAQ,EAAE,oBAAoB,GAAG,SAAS,CAAC;IAC3C,2EAA2E;IAC3E,KAAK,EAAE,cAAc,GAAG,IAAI,GAAG,SAAS,CAAC;IACzC,gEAAgE;IAChE,QAAQ,EAAE,CAAC,OAAO,EAAE,cAAc,KAAK,IAAI,CAAC;CAC7C;AAED;;;;;;;GAOG;AACH,wBAAgB,qBAAqB,CAAC,GAAG,SAAS,UAAU,EAC1D,OAAO,EAAE,4BAA4B,CAAC,GAAG,CAAC,GACzC,2BAA2B,CAmE7B"}
+{"version":3,"file":"namespace.d.ts","sourceRoot":"","sources":["../../src/settings/namespace.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAyCG;AAEH,OAAO,CAAC,MAAM,0BAA0B,CAAC;AACzC,OAAO,EAAY,KAAK,WAAW,EAAE,KAAK,UAAU,EAAE,MAAM,eAAe,CAAC;AAG5E;;;;GAIG;AACH,eAAO,MAAM,sBAAsB,gBAAgB,CAAC;AAEpD;;;;;;;GAOG;AACH,eAAO,MAAM,oBAAoB,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAmB,CAAC;AAa7E,oFAAoF;AACpF,MAAM,WAAW,SAAS,CAAC,CAAC,GAAG,OAAO;IACpC,sFAAsF;IACtF,GAAG,IAAI,CAAC,CAAC;CACV;AAED,oFAAoF;AACpF,wBAAgB,WAAW,CAAC,KAAK,EAAE,OAAO,GAAG,KAAK,IAAI,SAAS,CAE9D;AAED;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,wBAAgB,iBAAiB,CAAC,CAAC,EAAE,KAAK,EAAE,CAAC,GAAG,CAAC,CAEhD;AAsBD;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,wBAAgB,gBAAgB,IAAI,MAAM,CAAC,MAAM,EAAE,CAAC,CAAC,GAAG,CAAC,CAAC,CAazD;AAED,0DAA0D;AAC1D,MAAM,MAAM,sBAAsB,GAAG,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG;IAAE,QAAQ,CAAC,EAAE,MAAM,CAAC;IAAC,WAAW,CAAC,EAAE,MAAM,CAAA;CAAE,CAAC;AAE3G;;;;;GAKG;AACH,MAAM,WAAW,cAAc;IAC7B,QAAQ,CAAC,EAAE,WAAW,EAAE,CAAC;IACzB,eAAe,CAAC,EAAE,sBAAsB,CAAC;IACzC,MAAM,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IACjC,QAAQ,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IACnC,QAAQ,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IACnC,GAAG,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CAC/B;AAED,MAAM,WAAW,cAAc;IAC7B;;;;;;;;;;;OAWG;IACH,eAAe,CAAC,EAAE,OAAO,CAAC;CAC3B;AAED;;;;;;;;;;;;;;GAcG;AACH,wBAAgB,SAAS,CAAC,MAAM,EAAE,OAAO,EAAE,OAAO,GAAE,cAAmB,GAAG,cAAc,CA6BvF;AAED;;;;;;;;;GASG;AACH,wBAAgB,aAAa,CAAC,IAAI,EAAE,cAAc,EAAE,QAAQ,EAAE,cAAc,GAAG,cAAc,CAa5F;AAED;;;;;GAKG;AACH,MAAM,WAAW,oBAAoB;IACnC;;;;;OAKG;IACH,SAAS,CAAC,CAAC,YAAY,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,KAAK,CAAC,EAAE,OAAO,GAAG,MAAM,IAAI,CAAC;IAC/E;;;;;;;;;OASG;IACH,OAAO,CAAC,CAAC,EAAE,EAAE,MAAM,EAAE,OAAO,EAAE,OAAO,EAAE,gBAAgB,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC,OAAO,CAAC,CAAC;CACrF;AAED,yFAAyF;AACzF,MAAM,WAAW,kBAAkB;IACjC,uEAAuE;IACvE,IAAI,IAAI,cAAc,CAAC;IACvB;;;;;OAKG;IACH,KAAK,CAAC,MAAM,EAAE,OAAO,GAAG,OAAO,CAAC,IAAI,CAAC,CAAC;CACvC;AAED,kCAAkC;AAClC,MAAM,WAAW,2BAA2B;IAC1C,6EAA6E;IAC7E,IAAI,EAAE,OAAO,CAAC;IACd,4CAA4C;IAC5C,OAAO,EAAE,cAAc,CAAC;IACxB,8EAA8E;IAC9E,MAAM,CAAC,EAAE,kBAAkB,CAAC;CAC7B;AAED,MAAM,WAAW,4BAA4B,CAAC,GAAG,SAAS,UAAU;IAClE,kFAAkF;IAClF,KAAK,EAAE,GAAG,CAAC;IACX,QAAQ,EAAE,oBAAoB,GAAG,SAAS,CAAC;IAC3C,sFAAsF;IACtF,MAAM,EAAE,OAAO,CAAC;IAChB,+DAA+D;IAC/D,EAAE,EAAE,MAAM,GAAG,SAAS,CAAC;IACvB,oFAAoF;IACpF,QAAQ,EAAE,CAAC,OAAO,EAAE,cAAc,KAAK,IAAI,CAAC;CAC7C;AAED;;;;;;;;GAQG;AACH,wBAAgB,qBAAqB,CAAC,GAAG,SAAS,UAAU,EAC1D,OAAO,EAAE,4BAA4B,CAAC,GAAG,CAAC,GACzC,2BAA2B,CA2C7B;AAED,OAAO,QAAQ,qBAAqB,CAAC;IACnC,UAAU,MAAM;QACd;;;;;;;;;;WAUG;QACH,wBAAwB,CAAC,KAAK,EAAE,SAAS,CAAC,SAAS,MAAM,EAAE,CAAC,EAAE,GAAG,IAAI,CAAC;KACvE;CACF"}