@lacneu/wix-openclaw 0.3.1 → 0.5.0

package/CHANGELOG.md

@@ -5,6 +5,183 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [Unreleased]
+
+## [0.5.0] - 2026-08-29
+
+Six accessibility tools, off by default behind **their own** switch. The 0.4
+line could correct a site's SEO tags and say nothing about whether the site
+could be used with a screen reader; Wix runs an accessibility scan of its own,
+and this release reads it.
+
+Nothing in this family writes to the site, so there are no tokens and no
+refusals here. The discipline moved instead to what an answer is allowed to
+CLAIM — see below.
+
+### Added — Accessibility: Wix runs the scan, this reads the result
+
+> Developer Preview, and **off by default behind its own switch**,
+> `enableAccessibilityTools`. Nothing in this family writes to the site.
+
+Six tools: `wix_a11y_list_page_collections`, `wix_a11y_run_scan`,
+`wix_a11y_get_scan`, `wix_a11y_get_latest_scan`,
+`wix_a11y_list_page_summaries` and `wix_a11y_list_findings`.
+
+### The discipline moves, because the danger moved
+
+The SEO writes needed tokens because they destroyed the previous value of what
+they wrote. Nothing here destroys anything — so the way this family hurts a user
+is different, and Wix names it: **a page is clear only when it has no findings,
+its page status is completed, and its coverage confirms the relevant checks
+ran**. A page that failed to scan reports zero findings too, because nothing was
+read.
+
+So no answer here can be skimmed into a clean one. Page summaries carry `clear`,
+valued `true`, `false` or `"unknown"`, instead of a bare count — and a `true`
+comes with `clearFor`, naming the checks it is true for, because coverage says
+which checks ran, not that the right ones did. The `"unknown"` pages are
+counted for you. A scan reports `resultIsWhole`;
+`PARTIALLY_COMPLETED` never collapses into success, a running scan says its
+numbers are progress rather than a result, and a failed scan refuses to be a
+result at all. An unfiltered empty findings list says that an absent finding is
+not a rule that passed.
+
+### `attempt` is what tells a retry apart from a new scan
+
+Wix takes a caller-generated idempotency key so a lost response cannot create
+duplicate work, and requires a **new** key for a genuinely new scan — verifying
+a fix is a new scan, not a retry. The key is derived from the site, the target
+and the `attempt` label the caller passes. A random key per call would satisfy
+the schema and make the guarantee inert against a 5-per-minute limit; deriving
+it from the target alone would turn every verification into a retry that hands
+back the stale result.
+
+### Recovery paths that would otherwise be unreachable
+
+`SCAN_ALREADY_IN_PROGRESS` and `SCAN_STATE_UNKNOWN` carry a scan id the caller
+is meant to poll. Left inside a thrown message, the only move an agent has left
+is to start a duplicate — so those errors return the id and the instruction not
+to. `SCAN_SIZE_LIMIT_EXCEEDED` returns with an explicit ban on describing the
+site as fully scanned.
+
+### The SDK view is not the wire view
+
+The Wix SDK renames three keys coming back from REST — `id` → `_id`,
+`createdDate` → `_createdDate`, `updatedDate` → `_updatedDate`. This plugin
+speaks REST directly, so the wire says `id`. Every field name here was taken
+from the SDK typings, which made that rename the one place the typings are not
+the contract: reading `_id` returned `undefined` on every real call, so a
+started scan handed back no id and the polling flow had nothing to poll. The
+tests agreed, because the fixtures had been shaped from the same typings.
+
+Query encoding came from the same source and had the same shape of trap: Wix's
+serialiser flattens nested objects to dotted keys (`filter.severity`) but emits
+a repeated field as a **repeated key** (`filter.categories=A&filter.categories=B`).
+An indexed `filter.categories.0` is a different parameter, and a filter the API
+ignores returns unfiltered findings that the tool would then label filtered.
+
+### Fixed
+
+- **A raw NUL byte had been written into a source file.** It was a legitimate
+  HMAC separator written the wrong way, and its effect was not on the running
+  code: `grep` treats a file containing NUL as binary and answers **nothing**,
+  silently, so searches reported symbols absent that were present. Written as
+  an escape now, and a guard rejects any raw control character in `src/` and
+  `test/` — the same class as a stray U+2028 that once landed in a test regex.
+- Stale counts in the SEO opt-in comments in `src/config.ts` and the manifest
+  test, still saying four tools write irreversibly when eleven do.
+
+## [0.4.0] - 2026-08-29
+
+Ten more `wix_seo_*` tools, still **off by default**, close the other half of
+the SEO gap: 0.3.x could audit a site's tags and never correct them. Writing
+them is a different destructiveness from deleting a redirect — a tag write
+replaces **the previous value of what it writes** — so the guard is different
+too, and most of this entry is about that.
+
+### Added — SEO: writing tags, and the patterns behind them
+
+> Same warning as the audit tools: these endpoints are in Developer Preview,
+> Wix states they should not be used on live sites, and **every tool here
+> replaces what it writes**. They register only with `enableSeoTools: true`.
+
+Ten tools complete the SEO surface: you could audit tags but not correct them.
+
+**Per-item and site-wide tags.** `wix_seo_set_item_tags`,
+`wix_seo_bulk_set_item_tags`, `wix_seo_reset_item_tags` and
+`wix_seo_set_site_tags`.
+
+**Patterns.** `wix_seo_list_patterns`, `wix_seo_get_pattern`,
+`wix_seo_list_pattern_variables` (read-only) plus `wix_seo_set_pattern`,
+`wix_seo_create_pattern` and `wix_seo_reset_pattern`.
+
+### The destructiveness is a different shape, so the guard is too
+
+A redirect delete destroys another row — it can be listed and named. A tag write
+destroys **the previous value of what it writes**: `tags` replaces the item's set
+in full, so a caller that sets a title wipes the description it never mentioned,
+gets exactly what it asked for, and loses something it never saw. That is this
+half's "redirects do not chain".
+
+The pre-flight therefore reports what **disappears** — the tags held today whose
+slot the incoming set does not fill — never an echo of the input. A caller
+reading its own request back learns nothing. Nothing is lost, nothing is
+refused: the ceremony exists for the unannounced loss, not for its own sake.
+
+A pattern write earns the heaviest pre-flight in the plugin. It re-renders
+**every page of its type**, it has no revision, and the Wix dashboard writes to
+the same object — last write wins. So the refusal reports the page count
+downstream alongside the templates, and the token is bound to the pattern read
+immediately before — **and to that page count**, because the radius is part of
+what was accepted: a token minted while a type held twelve pages does not
+authorise the same write once it holds four hundred.
+
+Every refusal in this family carries the **value** of what it names, not only
+its slot.
+Editing `{{title}}` into `{{title}} — Ataraxis` loses no tag, so a report by
+slot alone read identically before and after — an operator signing a rewrite of
+every page of a type without seeing either version.
+
+### Three contract facts that live in code, not in prose
+
+- **`fieldMask` is a comma-separated STRING over REST.** The SDK takes an array,
+  which is what a model reaches for. It is built here, never accepted.
+- **`language` is actively dropped.** Tags can only be written for the item's
+  primary language, and sending one fails `LANGUAGE_NOT_SUPPORTED` *even when
+  the field mask omits it* — so not declaring the field is not enough, TypeBox
+  passes undeclared properties through.
+- **Site SEO Tags accepts only `meta`.** Wix rejects `title`, `script` and
+  `link` there despite the shared tag shape listing them, and there is no way to
+  set site-wide structured data through any Wix API — a per-page `script` tag is
+  the route.
+
+`BLOG_POST` bulk writes are capped at 20 entries, not 100, and Wix rejects the
+**whole call** past an item type's limit — a 40-post batch would write nothing —
+so the cap is enforced before the request leaves.
+
+### The `publish` split, stated where a model will read it
+
+For a static page, `publish: true` updates **only** the published revision. The
+read tools always return the **saved** one, so after such a write they keep
+showing the old values — that is not a failed write, and re-sending will not
+change it. The method's own response is not a read of the published page either.
+A caller following the description literally converges instead of retrying.
+
+## [0.3.1] - 2026-08-28
+
+**The version that actually reached npm for the 0.3 line.** `v0.3.0` was
+tagged, failed to compile in the release workflow and was never published, so
+`0.3.1` carries the whole 0.3.0 entry below plus the fix that unblocked it.
+
+### Fixed
+
+- **The build imported a type from a subpath that does not exist across the
+  supported range.** `openclaw/plugin-sdk/agent-core` only appeared in
+  2026.5.28, while this plugin declares `>=2026.5.0`, so CI failed on the lower
+  bound. The shared tool-result type is declared locally instead — verified at
+  both ends of the supported range rather than at the version that happened to
+  be installed.
+
 ## [0.3.0] - 2026-08-28
 
 Nine `wix_seo_*` tools, **off by default**, close the gap that made this plugin
@@ -402,7 +579,7 @@ For instance owners on `@lacneu/wix-openclaw@0.2.2`:
 3. Verify in the boot log:
    `wix-openclaw: ready — 50 tool(s) registered`.
 
-Fifty, not fifty-nine: the SEO tools are not registered until you opt in. Nothing
+Fifty, not sixty-nine: the SEO tools are not registered until you opt in. Nothing
 else changes, and the approval fix applies as soon as the plugin loads — a gated
 tool that used to fail without asking will now put its prompt to the operator.
 
@@ -418,7 +595,7 @@ To add the SEO tools:
    `openclaw config set plugins.entries.wix-openclaw.config.enableSeoTools true`.
    `update` carries your existing config forward and the new field simply
    defaults to `false`, so nothing turns on by surprise.
-3. Restart, and expect `59 tool(s) registered`.
+3. Restart, and expect `69 tool(s) registered`.
 4. Read the Developer Preview warning at the top of this section before pointing
    any of the four writing tools at a live site.
 

package/README.md

@@ -15,10 +15,12 @@
 ## Overview
 
 `wix-openclaw` is an OpenClaw plugin that lets your agent operate a Wix site
-through the official Wix REST API. It registers ~60 tools split across a dozen
-Wix products (Blog, CMS Data, Forms, Bookings, Contacts, Events, Reviews, FAQ,
-Multilingual, Sites, Site Media, SEO), plus a `wix_design_brief` helper that
-turns loose textual briefs into structured markdown artefacts.
+through the official Wix REST API. It registers **50 tools by default** across a
+dozen Wix products (Blog, CMS Data, Forms, Bookings, Contacts, Events, Reviews,
+FAQ, Multilingual, Sites, Site Media), plus a `wix_design_brief` helper that
+turns loose textual briefs into structured markdown artefacts. Two families are
+opt-in and add to that: SEO (`enableSeoTools`, 19 tools) and accessibility
+(`enableAccessibilityTools`, 6 tools) — **75 with both**.
 
 Every tool funnels through a single authenticated HTTP client that:
 
@@ -176,8 +178,10 @@ Tick these only if the corresponding Wix product is actually in use on
 the target site:
 
 - [ ] **Manage SEO** (`SCOPE.PROMOTE.MANAGE-SEO`) — **only if you set
-  `enableSeoTools: true`.** In the default configuration the SEO tools are not
-  registered at all, so granting this scope would hand the key the power to
+  `enableSeoTools: true`**, which registers **nineteen** tools of which
+  **eleven write irreversibly** (four on redirects, seven on tags and
+  patterns; a pattern write re-renders every page of its type). In the default
+  configuration the SEO tools are not registered at all, so granting this scope would hand the key the power to
   delete redirects for tools that cannot run. Wix exposes a **single** SEO
   scope, not a read/write pair: ticking it grants redirect creation and deletion
   along with the read-only audit, so there is no such thing as an audit-only SEO
@@ -185,8 +189,20 @@ the target site:
   *Social Posts* and *Import orders*; its label is currently untranslated and
   renders literally as `site.scope.SCOPE.PROMOTE.MANAGE-SEO.name`. Since Wix
   cannot narrow it, the read/write boundary is enforced by this plugin instead —
-  the four writing tools require an approval naming every redirect they would
-  destroy.
+  each of the eleven writing tools refuses until what it would destroy, be it a
+  redirect, a tag or a template, has been named and acknowledged.
+
+- [ ] **Manage Accessibility Scans** — **only if you set
+  `enableAccessibilityTools: true`**, which registers six tools. None of them
+  writes to the site: Wix runs the scan, the plugin reads the result. **The
+  scope identifier for this permission is not published in the API reference
+  and is NOT recorded here** — the last time this README guessed a Wix
+  permission name it invented one that does not exist, so this line stays empty
+  until the exact label is read off the Wix permissions page. Note that reading
+  page collections or past results does **not** prove the key may start a scan:
+  Wix states that starting one needs this permission specifically, and answers
+  `403` / `PERMISSION_DENIED` otherwise — which the tools surface as a
+  permission problem, never as an empty site.
 
 - [ ] **Pricing Plans** — if you sell subscription packages
 - [ ] **Wix Stores** + **Wix eCommerce** — if you sell physical/digital
@@ -238,7 +254,8 @@ columns and remove the matching tools from your agent's allow-list.
 | `wix_reviews_*` | Wix Reviews | Reviews moderation |
 | `wix_faq_*` | Manage FAQ | FAQ tooling |
 | `wix_multilingual_*` | Multilingual Translation Schema Read | Translation reads |
-| `wix_seo_*` (all nine) | Manage SEO (`SCOPE.PROMOTE.MANAGE-SEO`) | SEO audit **and** redirect changes — Wix has no read-only SEO scope, so this one permission covers both |
+| `wix_seo_*` (all nineteen) | Manage SEO (`SCOPE.PROMOTE.MANAGE-SEO`) | SEO audit **and** redirect changes — Wix has no read-only SEO scope, so this one permission covers both |
+| `wix_a11y_*` (all six) | Manage Accessibility Scans (identifier not published — read it off the Wix permissions page) | Starting a scan. Reading collections or stored results does not imply it |
 | `wix_design_brief` | _(none — no API call)_ | Always |
 
 ### Wix app installation requirements
@@ -487,19 +504,22 @@ neither answer has been tested.
 ### SEO
 
 > **Developer Preview, and OFF by default.** Every Wix endpoint behind these
-> nine tools is listed in Wix's
+> nineteen tools is listed in Wix's
 > [Developer Preview](https://dev.wix.com/docs/api-reference/articles/work-with-wix-apis/platform/about-developer-preview)
-> — Item SEO Tags, Site SEO Tags and all six Redirects methods. Wix may change
+> — Item SEO Tags, Site SEO Tags, SEO Patterns and all six Redirects methods.
+> Wix may change
 > them at any time, and states plainly that you **shouldn't use them on live
 > sites**: they are for testing and feedback. An API stays in preview for at
 > most six months.
 >
 > Nothing here registers unless you set `enableSeoTools: true` in the plugin
-> config. Four of the tools write irreversibly to the live site the moment they
-> succeed, so opting in is the operator saying they accept both risks.
+> config. Eleven of the tools write irreversibly to the live site the moment
+> they succeed — and a pattern write re-renders every page of its type — so
+> opting in is the operator saying they accept both risks.
 > _Preview status verified against the Wix reference on 2026-08-28._
 
-Auditing a site's SEO, and managing its URL redirects.
+Auditing a site's SEO, correcting its tags, and managing its URL redirects and
+tag patterns.
 
 | Tool | What it does | Approval | Validated |
 |---|---|---|---|
@@ -512,6 +532,16 @@ Auditing a site's SEO, and managing its URL redirects.
 | `wix_seo_delete_redirect` | Delete one redirect (re-reads it and refuses until its token is acknowledged) | **required** | schema |
 | `wix_seo_bulk_create_redirects` | Create 1–100 redirects | **required** | schema |
 | `wix_seo_bulk_delete_redirects` | Delete 1–500 redirects | **required** | schema |
+| `wix_seo_set_item_tags` | Set one item's tags — REPLACES its own set in full; refuses until the tags it would drop are acknowledged | **required** | schema |
+| `wix_seo_bulk_set_item_tags` | Set tags for many items of one type (100 max, 20 for `BLOG_POST`); per-entry results | **required** | schema |
+| `wix_seo_reset_item_tags` | Give an item back the tags it inherits, discarding its own (all or nothing) | **required** | schema |
+| `wix_seo_set_site_tags` | Set the site-wide tags — `meta` only; Wix rejects `title`/`script`/`link` here | **required** | schema |
+| `wix_seo_list_patterns` | The site's tag templates, per page type | — | schema |
+| `wix_seo_get_pattern` | One page type's pattern; read `source` to know whose it is — an owned pattern may hold zero templates, so empty ≠ absent | — | schema |
+| `wix_seo_list_pattern_variables` | The variables a page type's pattern may reference | — | schema |
+| `wix_seo_set_pattern` | Change an existing pattern — re-renders EVERY page of the type | **required** | schema |
+| `wix_seo_create_pattern` | Give a page type its first pattern (same path as the set, `POST` not `PATCH`) | **required** | schema |
+| `wix_seo_reset_pattern` | Return a page type to the Wix default pattern | **required** | schema |
 
 **Three things to know before using these.**
 
@@ -550,6 +580,65 @@ delete it, then create it carrying **every** field over — an omitted field is
 filled with its default, not its previous value. To find one, list them all and
 filter client-side.
 
+### Accessibility
+
+> **Developer Preview, and OFF by default — separately from SEO.** The Wix
+> Accessibility Scans endpoints are in Developer Preview and may change without
+> notice. Nothing here writes to the site, so there is no approval to give and
+> nothing to undo; the switch exists because starting a scan needs its own Wix
+> permission, which the SEO scope does not grant. Set
+> `enableAccessibilityTools: true` to opt in.
+> _Contract read from the public Introduction, Sample Flows and agent Skill
+> pages, and from the published SDK package
+> `@wix/auto_sdk_accessibility_accessibility-scans`, whose own host mapping
+> gives the REST prefix `/accessibility/v1/accessibility-scans` verbatim. The
+> per-method reference pages are listed in the Wix menu but return 404, so no
+> field name here was taken from a rendered page — verified 2026-08-29._
+
+Wix runs the scan; these tools start it and read what it found.
+
+| Tool | What it does | Approval | Validated |
+|---|---|---|---|
+| `wix_a11y_list_page_collections` | The page collections this site supports right now — pass a `collectionId` back unchanged | — | schema |
+| `wix_a11y_run_scan` | Start a scan of one target: the site, one page, or one collection. Returns a scan id immediately | — | schema |
+| `wix_a11y_get_scan` | Poll target: lifecycle, progress, aggregate totals. No pages, no findings | — | schema |
+| `wix_a11y_get_latest_scan` | The most recent stored scan for a target, without starting a new one | — | schema |
+| `wix_a11y_list_page_summaries` | Every discovered page, including clear ones and ones that failed to scan | — | schema |
+| `wix_a11y_list_findings` | The actionable findings, filterable by page, rule, severity or category | — | schema |
+
+**What makes a page clear, and why it takes three conditions.**
+
+Wix states it plainly: a page is clear only when it has no findings, **its page
+status is completed**, and **its coverage confirms the relevant checks ran**. A
+page that failed to scan also reports zero findings — because nothing was read,
+not because nothing is wrong. So every page summary carries `clear`, valued
+`true`, `false` or `"unknown"`, rather than a bare count — with `clearFor`
+naming the checks a `true` is true *for* — a scan reports `resultIsWhole`, and
+`PARTIALLY_COMPLETED` never collapses into success. The
+failure mode this family has is not data loss, it is an agent reporting a clean
+site from an incomplete scan.
+
+**Scans are asynchronous, and these tools do not wait.** `wix_a11y_run_scan`
+returns a scan id; poll `wix_a11y_get_scan` after `suggestedPollIntervalSeconds`
+(every 5 seconds when absent) until the status is terminal. A tool that blocked
+for the length of a site scan would be the wrong shape for an agent turn.
+
+**`attempt` is what tells a retry apart from a new scan.** Wix takes a
+caller-generated idempotency key so a lost response cannot create duplicate
+work, and requires a *new* key for a genuinely new scan. The plugin derives that
+key from the site, the target and the `attempt` label you pass: reuse the label
+to retry, change it to scan again. A random key per call would satisfy the
+schema and make the whole guarantee inert.
+
+**Limits worth knowing.** Runs are capped at 5 per minute per site; a multi-page
+scan covers at most 300 pages and answers `SCAN_SIZE_LIMIT_EXCEEDED` beyond that
+— after which the site must never be described as fully scanned. Stored results
+are kept about six months, and `resultsExpirationDate` says exactly when. A
+published site is scanned from its published version, an unpublished one from
+its latest saved version — the opposite way round from the SEO tag reads above.
+
+---
+
 ### Design
 
 | Tool | What it does | Approval | Validated |

package/dist/config.js

@@ -34,6 +34,15 @@ export const DEFAULT_APPROVAL_REQUIRED = [
     "wix_seo_delete_redirect",
     "wix_seo_bulk_create_redirects",
     "wix_seo_bulk_delete_redirects",
+    // Tranche 2 — writing tags. Each REPLACES what it writes: the previous
+    // value is gone, and a pattern write re-renders every page of its type.
+    "wix_seo_set_item_tags",
+    "wix_seo_bulk_set_item_tags",
+    "wix_seo_reset_item_tags",
+    "wix_seo_set_site_tags",
+    "wix_seo_set_pattern",
+    "wix_seo_create_pattern",
+    "wix_seo_reset_pattern",
 ];
 const VALID_LOG_LEVELS = ["debug", "info", "warn", "error"];
 /**
@@ -60,10 +69,16 @@ export function resolveConfig(cfg = {}) {
         enabled: cfg.enabled !== false,
         // OPT-IN, unlike every other tool group. The Wix SEO endpoints are in
         // Developer Preview: Wix may change them at any time and says they
-        // "shouldn't be used on live sites". Four of these tools also write
+        // "shouldn't be used on live sites". Eleven of these tools also write
         // irreversibly to a live site the moment they succeed. Defaulting them on
         // would enable that on every existing install without anyone deciding to.
         enableSeoTools: cfg.enableSeoTools === true,
+        // A SEPARATE SWITCH, not a sub-case of the SEO one. These tools destroy
+        // nothing, but starting a scan needs its own Wix permission that the SEO
+        // scope does not grant — so an install that turned SEO on has not thereby
+        // decided anything about this, and folding the two together would enable a
+        // family of calls that would only fail with 403.
+        enableAccessibilityTools: cfg.enableAccessibilityTools === true,
         apiKey,
         accountId,
         allowedSiteIds,

package/dist/config.js.map

@@ -1 +1 @@
-{"version":3,"file":"config.js","sourceRoot":"","sources":["../src/config.ts"],"names":[],"mappings":"AAAA,gCAAgC;AAChC,EAAE;AACF,2EAA2E;AAC3E,6DAA6D;AAQ7D;;;;;GAKG;AACH,MAAM,UAAU,UAAU,CAAI,KAAQ;IACpC,IAAI,OAAO,KAAK,KAAK,QAAQ;QAAE,OAAO,KAAK,CAAC;IAC5C,OAAO,KAAK,CAAC,OAAO,CAAC,cAAc,EAAE,CAAC,CAAC,EAAE,IAAY,EAAE,EAAE;QACvD,OAAO,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,IAAI,EAAE,CAAC;IACjC,CAAC,CAAiB,CAAC;AACrB,CAAC;AAED,MAAM,CAAC,MAAM,yBAAyB,GAAG;IACvC,wBAAwB;IACxB,oBAAoB;IACpB,uBAAuB;IACvB,sBAAsB;IACtB,qBAAqB;IACrB,yBAAyB;IACzB,qBAAqB;IACrB,sBAAsB;IACtB,yBAAyB;IACzB,sEAAsE;IACtE,6EAA6E;IAC7E,2EAA2E;IAC3E,6EAA6E;IAC7E,6DAA6D;IAC7D,yBAAyB;IACzB,yBAAyB;IACzB,+BAA+B;IAC/B,+BAA+B;CAChC,CAAC;AAEF,MAAM,gBAAgB,GAAkB,CAAC,OAAO,EAAE,MAAM,EAAE,MAAM,EAAE,OAAO,CAAC,CAAC;AAE3E;;;;;;;;;GASG;AACH,MAAM,UAAU,aAAa,CAC3B,MAAuB,EAAE;IAEzB,MAAM,MAAM,GAAG,UAAU,CAAC,GAAG,CAAC,MAAM,IAAI,EAAE,CAAC,CAAC;IAC5C,MAAM,SAAS,GAAG,UAAU,CAAC,GAAG,CAAC,SAAS,IAAI,EAAE,CAAC,CAAC;IAClD,MAAM,cAAc,GAAG,CAAC,GAAG,CAAC,cAAc,IAAI,EAAE,CAAC,CAAC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,UAAU,CAAC,EAAE,CAAC,CAAC,CAAC;IAC9E,MAAM,eAAe,GAAG,UAAU,CAAC,GAAG,CAAC,aAAa,IAAI,EAAE,CAAC,CAAC;IAC5D,MAAM,aAAa,GACjB,eAAe,IAAI,CAAC,cAAc,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC;IAE/C,MAAM,gBAAgB,GAAG,GAAG,CAAC,gBAAgB,IAAI,yBAAyB,CAAC;IAE3E,MAAM,QAAQ,GAAgB,gBAAgB,CAAC,QAAQ,CACrD,GAAG,CAAC,QAAuB,CAC5B;QACC,CAAC,CAAE,GAAG,CAAC,QAAwB;QAC/B,CAAC,CAAC,MAAM,CAAC;IAEX,OAAO;QACL,OAAO,EAAE,GAAG,CAAC,OAAO,KAAK,KAAK;QAC9B,sEAAsE;QACtE,mEAAmE;QACnE,oEAAoE;QACpE,0EAA0E;QAC1E,0EAA0E;QAC1E,cAAc,EAAE,GAAG,CAAC,cAAc,KAAK,IAAI;QAC3C,MAAM;QACN,SAAS;QACT,cAAc;QACd,aAAa;QACb,gBAAgB,EAAE,IAAI,GAAG,CAAC,gBAAgB,CAAC;QAC3C,QAAQ;KACT,CAAC;AACJ,CAAC"}
+{"version":3,"file":"config.js","sourceRoot":"","sources":["../src/config.ts"],"names":[],"mappings":"AAAA,gCAAgC;AAChC,EAAE;AACF,2EAA2E;AAC3E,6DAA6D;AAQ7D;;;;;GAKG;AACH,MAAM,UAAU,UAAU,CAAI,KAAQ;IACpC,IAAI,OAAO,KAAK,KAAK,QAAQ;QAAE,OAAO,KAAK,CAAC;IAC5C,OAAO,KAAK,CAAC,OAAO,CAAC,cAAc,EAAE,CAAC,CAAC,EAAE,IAAY,EAAE,EAAE;QACvD,OAAO,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,IAAI,EAAE,CAAC;IACjC,CAAC,CAAiB,CAAC;AACrB,CAAC;AAED,MAAM,CAAC,MAAM,yBAAyB,GAAG;IACvC,wBAAwB;IACxB,oBAAoB;IACpB,uBAAuB;IACvB,sBAAsB;IACtB,qBAAqB;IACrB,yBAAyB;IACzB,qBAAqB;IACrB,sBAAsB;IACtB,yBAAyB;IACzB,sEAAsE;IACtE,6EAA6E;IAC7E,2EAA2E;IAC3E,6EAA6E;IAC7E,6DAA6D;IAC7D,yBAAyB;IACzB,yBAAyB;IACzB,+BAA+B;IAC/B,+BAA+B;IAC/B,uEAAuE;IACvE,wEAAwE;IACxE,uBAAuB;IACvB,4BAA4B;IAC5B,yBAAyB;IACzB,uBAAuB;IACvB,qBAAqB;IACrB,wBAAwB;IACxB,uBAAuB;CACxB,CAAC;AAEF,MAAM,gBAAgB,GAAkB,CAAC,OAAO,EAAE,MAAM,EAAE,MAAM,EAAE,OAAO,CAAC,CAAC;AAE3E;;;;;;;;;GASG;AACH,MAAM,UAAU,aAAa,CAC3B,MAAuB,EAAE;IAEzB,MAAM,MAAM,GAAG,UAAU,CAAC,GAAG,CAAC,MAAM,IAAI,EAAE,CAAC,CAAC;IAC5C,MAAM,SAAS,GAAG,UAAU,CAAC,GAAG,CAAC,SAAS,IAAI,EAAE,CAAC,CAAC;IAClD,MAAM,cAAc,GAAG,CAAC,GAAG,CAAC,cAAc,IAAI,EAAE,CAAC,CAAC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,UAAU,CAAC,EAAE,CAAC,CAAC,CAAC;IAC9E,MAAM,eAAe,GAAG,UAAU,CAAC,GAAG,CAAC,aAAa,IAAI,EAAE,CAAC,CAAC;IAC5D,MAAM,aAAa,GACjB,eAAe,IAAI,CAAC,cAAc,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC;IAE/C,MAAM,gBAAgB,GAAG,GAAG,CAAC,gBAAgB,IAAI,yBAAyB,CAAC;IAE3E,MAAM,QAAQ,GAAgB,gBAAgB,CAAC,QAAQ,CACrD,GAAG,CAAC,QAAuB,CAC5B;QACC,CAAC,CAAE,GAAG,CAAC,QAAwB;QAC/B,CAAC,CAAC,MAAM,CAAC;IAEX,OAAO;QACL,OAAO,EAAE,GAAG,CAAC,OAAO,KAAK,KAAK;QAC9B,sEAAsE;QACtE,mEAAmE;QACnE,sEAAsE;QACtE,0EAA0E;QAC1E,0EAA0E;QAC1E,cAAc,EAAE,GAAG,CAAC,cAAc,KAAK,IAAI;QAC3C,wEAAwE;QACxE,yEAAyE;QACzE,0EAA0E;QAC1E,2EAA2E;QAC3E,iDAAiD;QACjD,wBAAwB,EAAE,GAAG,CAAC,wBAAwB,KAAK,IAAI;QAC/D,MAAM;QACN,SAAS;QACT,cAAc;QACd,aAAa;QACb,gBAAgB,EAAE,IAAI,GAAG,CAAC,gBAAgB,CAAC;QAC3C,QAAQ;KACT,CAAC;AACJ,CAAC"}