@synapsor/runner 1.1.1 → 1.4.1

package/CHANGELOG.md

@@ -1,6 +1,128 @@
 # Changelog
 
-## 1.1.1 (prepared, not published)
+## 1.4.1 (prepared, not published)
+
+### Canonical Bounded-Set Digest Verification
+
+- Fixes contract-authored bounded-set proposals that could fail unchanged
+  apply with `SET_DIGEST_MISMATCH` after protocol parsing reordered aggregate
+  object fields.
+- Uses recursive canonical JSON key ordering for new member and set digests,
+  while narrowly accepting the deterministic raw representations emitted by
+  `1.4.0` so valid stored proposals remain applyable.
+- Keeps every frozen member, expected version, reviewed value, aggregate,
+  tenant guard, and atomic source check intact; malformed digests and genuine
+  source drift still fail closed.
+- Adds PostgreSQL/MySQL regression coverage for the exact DSL-to-contract path
+  under source-database and Runner-ledger receipt authority, plus independent
+  version, predicate, aggregate, writable-value, missing-member, and tenant
+  drift checks.
+- Ships the bounded-set guide and other linked public docs in the Runner
+  tarball, and fails package assembly when a shipped local Markdown link cannot
+  resolve.
+- Removes obsolete `0.1 preview` wording from the DSL package without changing
+  canonical Spec `spec_version: "0.1"`.
+- Adds a build-vs-adopt guide for teams already using prompts and custom
+  parameterized tools. It distinguishes behavioral instructions from
+  structural authorization, explains where SQL authority lives, and documents
+  the approval, receipt, replay, and compensation layer without claiming
+  prompt-injection prevention or compliance certification.
+- Stages `@synapsor/runner@1.4.1` and `@synapsor/dsl@1.4.1`;
+  `@synapsor/spec` remains `1.4.0` because the public contract schema did not
+  change. Nothing is published by this change.
+
+## 1.4.0 (prepared, not published)
+
+### Reviewed Reversible Change Sets
+
+- Adds opt-in canonical `reversibility.mode = reviewed_inverse` and DSL
+  `REVERSIBLE` for direct SQL capabilities with human/operator approval and
+  operation-specific exact guards.
+- Captures bounded inverse descriptors only after an unambiguous successful
+  source transaction. Inverses retain trusted identity, version metadata, and
+  reviewed writable values; kept-out data is excluded.
+- Adds operator-only `revert <proposal-id>`, which creates a new proposal and
+  never writes or approves. Compensation inherits reviewer role/quorum and
+  passes normal approval, guarded apply, receipt, reconciliation, and replay.
+- Supports reviewed UPDATE, INSERT, soft-delete, and exact frozen-set
+  compensation on PostgreSQL and MySQL. Fresh-state conflicts and one stale set
+  member fail closed without partial effects.
+- Reports hard DELETE and app-owned/external effects as specifically
+  unavailable instead of claiming rollback or time travel. Successful
+  compensation captures its own bounded inverse with linear lineage capped at
+  16.
+- Adds compensation change-set and protocol-v4 job/receipt schemas,
+  conformance fixtures, owner-authorized resources, local UI/doctor/preview
+  state, bounded metrics, crash-reconciliation tests, and the disposable
+  `corepack pnpm test:reversible` gate.
+- Stages `@synapsor/spec@1.4.0`, `@synapsor/dsl@1.4.0`, and
+  `@synapsor/runner@1.4.0`. No npm package is published by this change.
+
+## 1.3.0 (prepared, not published)
+
+### Bounded Set Writeback
+
+- Adds canonical and DSL semantics for fixed-predicate set `UPDATE`/`DELETE`
+  and exact-review batch `INSERT`, with mandatory `MAX ROWS`, aggregate value
+  bounds, and a hard 100-row implementation ceiling.
+- Freezes ordered primary keys, tenant scope, reviewed before/after values,
+  exact versions, per-member digests, and a set digest before approval. Apply
+  locks only that frozen set and never reruns a broad selection predicate.
+- Applies every member in one source transaction. Cap overflow, aggregate
+  overflow, stale/missing members, anomalous affected counts, dedup conflicts,
+  triggers, or widening delete cascades fail closed without partial effects.
+- Requires human/operator approval for all bounded sets in this release;
+  policy auto-approval is rejected. Hard set delete remains exceptional and
+  soft delete is preferred.
+- Adds protocol-v3 change-set, writeback-job, result, and receipt envelopes
+  with exact member identities and bounded safe digests, plus reconciliation
+  support for Runner-ledger crash ambiguity.
+- Adds executable R1-R7 conformance coverage and a disposable PostgreSQL/MySQL
+  live gate for cap/aggregate rejection, atomic rollback, exact receipts,
+  batch deduplication, delete hazards, reconciliation, and 1/10/100-row bounds.
+- Stages `@synapsor/spec@1.3.0`, `@synapsor/dsl@1.3.0`, and
+  `@synapsor/runner@1.3.0`. No npm package is published by this change.
+
+## 1.2.0 (prepared, not published)
+
+### Guarded CRUD And Receipt Authority
+
+- Adds canonical and DSL operation semantics for native guarded single-row
+  `INSERT`, `UPDATE`, and `DELETE`, while preserving operation-less contracts
+  and v1 writeback jobs as guarded UPDATE.
+- Adds operation-aware v2 change-set, writeback-job, and execution-receipt
+  schemas with trusted tenant binding, source-enforced INSERT deduplication,
+  DELETE cascade/trigger refusal, bounded diffs, and replay-safe digests.
+- Separates receipt authority (`source_db` or `runner_ledger`) from source
+  receipt provisioning (`precreated` or `auto_migrate`). Runner-ledger mode
+  records durable intents without source receipt DDL and stops ambiguous
+  post-commit outcomes for verified operator reconciliation.
+- Extends Postgres and MySQL adapters, onboarding, doctor, tools preview, and
+  the support-plan-credit example with least-privilege guarded CRUD paths.
+- Adds disposable-engine verification for every operation and receipt mode,
+  retries, crash windows, concurrent applies, stale guards, and hidden DELETE
+  effects. No npm package is published by this change.
+- Stages `@synapsor/spec@1.2.0`, `@synapsor/dsl@1.2.0`, and
+  `@synapsor/runner@1.2.0`.
+
+## 1.1.2 (prepared, not published)
+
+### Fleet Error And Batch Apply Correctness
+
+- Classifies bounded source-pool saturation and recognized transient
+  PostgreSQL, MySQL, and network failures as `TEMPORARILY_UNAVAILABLE` with
+  `retryable: true` and a bounded `retry_after_ms`, while keeping raw driver
+  details out of MCP results and operational logs.
+- Keeps non-transient database failures fail-closed as non-retryable
+  `INTERNAL` errors.
+- Preserves the existing shared `runtime_store` bridge while
+  `apply --all-approved` applies each selected proposal, preventing stale
+  bridge state from silently skipping policy- or human-approved proposals.
+- Adds policy-approved unit coverage and a two-Runner synthetic Postgres fleet
+  check for durable batch results and receipts.
+- Stages only `@synapsor/runner@1.1.2`; canonical Spec and DSL remain `1.1.0`.
+
+## 1.1.1
 
 ### Resource Read Authorization
 

package/README.md

@@ -74,9 +74,9 @@ evidence -> proposal -> approval -> receipt -> replay
 ```
 
 The model can inspect scoped data and propose an exact change. It cannot call
-approval or apply tools. A human or trusted operator approves outside MCP, then
-Runner either performs one guarded row update or routes the approved proposal
-to an app-owned executor.
+approval, apply, or revert tools. A human or trusted operator approves outside
+MCP, then Runner performs a guarded write or routes the proposal to an
+app-owned executor.
 
 The distinction is the complete boundary, not a read-only toggle or a generic
 approve/reject prompt:
@@ -88,10 +88,26 @@ approve/reject prompt:
 - evidence, query audit, idempotency receipts, and replay preserve what was
   inspected, requested, approved, and applied.
 
-Runner supports bounded production deployments when its documented database,
-identity, ledger, backup, and operational controls are satisfied. It does not
-make arbitrary agent code, raw SQL tools, host infrastructure, or
-prompt-injection-prone clients safe by itself.
+Runner supports bounded deployments when its documented database, identity,
+ledger, backup, and operational controls are satisfied. It does not make raw
+SQL tools, host infrastructure, or prompt-injection-prone clients safe.
+
+## Why Not Just Use A Prompt And App Code?
+
+Prompt instructions can guide behavior, but prompt-only enforcement is not an
+authorization boundary. First ask who produces the SQL:
+
+- **The model produces SQL:** your validator must safely understand arbitrary
+  queries, scope, and side effects. That is `execute_sql` with an extra parser.
+- **Trusted app code produces fixed, parameterized SQL:** good. You have built
+  a semantic tool, and that may be enough for a small read-only application.
+
+Runner becomes useful when those tools also need one reviewed contract for
+trusted tenant scope, field controls, evidence, approval outside MCP, guarded
+and idempotent writeback, receipts, replay, and reviewed compensation. Use your
+own code when you do not need that lifecycle. Read the [full build-vs-adopt
+guide](docs/why-synapsor-vs-app-guardrails.md) for the decision table, public
+incident evidence, and regulated-data boundaries.
 
 ## Connect A Staging Database
 
@@ -109,11 +125,9 @@ creates trusted context, generates reviewed capabilities, previews the MCP tool
 surface, and prints the next smoke and serve commands. It stores environment
 variable names, not connection strings.
 
-The interesting part of the generated configuration is the capability entry: a
-reviewed, tenant-scoped read with an explicit column allowlist and required
-evidence. The storage, source, and trusted-context wiring around it (including
-statement timeouts) is generated for you; the full file is in the
-[own-database guide](docs/getting-started-own-database.md).
+The generated capability is a tenant-scoped read with an explicit column
+allowlist and required evidence. See the [own-database
+guide](docs/getting-started-own-database.md) for the full configuration.
 
 ```json
 {
@@ -148,10 +162,20 @@ synapsor-runner mcp serve --config ./synapsor.runner.json --store ./.synapsor/lo
 ```
 
 For proposal capabilities and writes, follow the
-[complete own-database guide](docs/getting-started-own-database.md). One-row
-updates can use Runner's guarded direct writeback. Inserts, multiple tables, or
-external effects go through an [app-owned executor](docs/writeback-executors.md)
-after approval.
+[complete own-database guide](docs/getting-started-own-database.md). Reviewed
+single-row INSERT, UPDATE, and DELETE can use Runner's guarded direct
+writeback. Runner also supports tightly [bounded set
+writes](docs/bounded-set-writeback.md): fixed-predicate UPDATE/DELETE and
+exact-review batch INSERT, with human approval, a hard 100-row ceiling, atomic
+apply, and exact receipts. Free-form predicates, unbounded or cross-table work,
+and external effects go through an [app-owned
+executor](docs/writeback-executors.md) after approval.
+
+Direct writes can use [reviewed
+compensation](docs/reversible-change-sets.md). Receipts capture a
+bounded inverse; `synapsor-runner revert <proposal_id>` creates a separately
+approved proposal. This is not rollback, time travel, or app-owned
+compensation.
 
 ## Trust And Verification
 
@@ -164,10 +188,11 @@ trust boundaries, covered threats, non-goals, and required operator controls.
 - MCP proposal, evidence, and replay handles are references rather than bearer
   authority: resource reads re-check the owning tenant and principal against
   the current trusted session.
-- `corepack pnpm test:live-apply` runs disposable Postgres and MySQL scenarios.
-  It proves source rows stay unchanged before approval, guarded writeback
-  applies once, idempotent retry does not duplicate the effect, and a stale row
-  returns a conflict.
+- `test:live-apply`, `test:guarded-crud`, `test:bounded-set`, and
+  `test:reversible` run disposable PostgreSQL/MySQL scenarios. They prove no
+  pre-approval mutation, guarded single-row CRUD, idempotent retry,
+  fail-closed conflicts, bounded atomic sets, exact receipts, and reviewed
+  compensation.
 - The C++/Cloud round-trip verifier exports normalized contracts, validates
   them with `@synapsor/spec`, and loads them in Runner. The shared contract and
   verification commands are documented in [Conformance](docs/conformance.md).
@@ -179,12 +204,9 @@ See [Security Boundary](docs/security-boundary.md) and
 
 ## Operate The Approval Loop
 
-Reviewed policies can combine a per-proposal threshold with daily count and
-total ceilings. Exceeding a ceiling routes that proposal to human review; it
-never auto-applies. Operators can apply the bounded approved queue independently
-with `apply --all-approved --yes`, inspect Prometheus counters with `metrics
-show`, and consume safe newline-delimited JSON outcome logs from stderr. Signed
-operator keys can enforce contract reviewer roles and separate apply roles.
+Reviewed policies combine per-proposal and daily ceilings; exceeding one routes
+the proposal to human review. Operators use `apply --all-approved --yes`,
+Prometheus metrics, structured logs, and optional signed reviewer/apply roles.
 Shared Postgres ledger mirror mode is available for bounded operator handoffs,
 and `storage.shared_postgres.mode = "runtime_store"` lets MCP serving use
 Postgres as the primary proposal/evidence/replay store with bounded CLI
@@ -211,11 +233,10 @@ dead-letter, and rolling-upgrade rules are in
 | `@synapsor/spec` | Canonical portable contracts for contexts, capabilities, workflows, evidence, proposals, receipts, and replay. |
 | `@synapsor/dsl` | SQL-like authoring that compiles contexts, capabilities, and workflow declarations into canonical contract JSON. |
 
-Runner executes locally. The spec is the portable contract shared by Runner
-and Cloud/C++. The DSL gives that contract a reviewable source format. Start
-with [Capability Authoring](docs/capability-authoring.md). Use `.synapsor.sql`
-for DSL source files when you want editors to provide generic SQL highlighting;
-legacy `.synapsor` files remain supported and produce the same contract JSON.
+Runner executes locally. The spec is shared by Runner and Cloud/C++; the DSL
+is its reviewable source format. Start with [Capability
+Authoring](docs/capability-authoring.md). Use `.synapsor.sql` for generic SQL
+highlighting; legacy `.synapsor` files produce the same contract JSON.
 
 Use the [DSL Reference](docs/dsl-reference.md) for exact authoring grammar and
 the [Runner Config Reference](docs/runner-config-reference.md) for every wiring

package/SECURITY.md

@@ -0,0 +1,11 @@
+# Security Policy
+
+Report security issues privately to security@synapsor.ai.
+
+Do not include production credentials, customer data, or full source rows in bug reports. Include runner version, job id, proposal id, source id, engine, safe error code, and redacted logs where possible.
+
+## Supported security scope
+
+The v0.1 runner protects the local writeback boundary for approved structured jobs. It does not make the hosted Synapsor control plane self-hosted, and it does not provide HA, compliance certification, or a general database proxy.
+
+See `docs/threat-model.md` for detailed trust boundaries, covered threats, non-goals, and release blockers.

package/THREAT_MODEL.md

@@ -53,8 +53,11 @@ idempotency boundary for effects.
 - Wrong tenant or object: reads and writes include trusted primary-key and tenant predicates.
 - Disallowed field update: patch columns must be allowlisted.
 - Stale row: conflict guard mismatch returns `conflict` instead of silently writing.
-- Duplicate retry: receipt/idempotency state prevents applying the same job twice.
-- Over-broad update: only single-row `UPDATE` is supported and success requires exactly one affected row.
+- Duplicate retry: atomic source receipts or durable Runner intents plus
+  source-enforced version/unique guards prevent a known duplicate effect;
+  ambiguous ledger/source crash windows stop for reconciliation.
+- Over-broad write: direct INSERT/UPDATE/DELETE is single-row, tenant-bound,
+  operation-guarded, and success requires exactly one affected row.
 - Cloud credential leakage: database URLs and write credentials stay local and are not sent to Cloud.
 - Model-callable approval: approval/commit tools are not exposed to MCP clients by default.
 - Claims/environment confusion: an `http_claims` server fails before serving
@@ -81,8 +84,8 @@ idempotency boundary for effects.
 - Sensitive data already returned to a model.
 - Prompt injection itself.
 - Business invariants not represented in the capability config, proposal, application handler, or database constraints.
-- Generic multi-row business transactions, DDL, DELETE, INSERT, UPSERT, or
-  cross-database atomicity in the Runner direct-write path.
+- Generic multi-row business transactions, DDL, UPSERT, model-generated
+  predicates, or cross-database atomicity in the Runner direct-write path.
 - A compromised IdP/JWKS host, ledger database, source database, TLS
   terminator, or administrator-approved contract.
 - Unbounded/high-throughput or multi-region ledger scale, compliance

package/dist/cli.d.ts

@@ -1,7 +1,9 @@
 #!/usr/bin/env node
 import { type DbRowReader } from "@synapsor-runner/mcp-server";
-import { type WritebackJob } from "@synapsor-runner/protocol";
+import { type StoredWritebackIntent } from "@synapsor-runner/proposal-store";
+import { type ExecutionReceiptV2, type ExecutionReceiptV3, type ExecutionReceiptV4, type WritebackJob } from "@synapsor-runner/protocol";
 import { type SchemaInspection } from "@synapsor-runner/schema-inspector";
+import { type ReconciliationObservation } from "@synapsor-runner/worker-core";
 export declare function main(argv: string[]): Promise<number>;
 type WizardAsk = (question: string, defaultValue?: string) => Promise<string>;
 export declare function runInitWizard(args: string[], options?: {
@@ -12,5 +14,7 @@ export declare function runInitWizard(args: string[], options?: {
     stdout?: Pick<NodeJS.WriteStream, "write">;
 }): Promise<number>;
 export declare function resolveSqlWriteDatabaseUrl(job: WritebackJob, configPath: string, env: NodeJS.ProcessEnv): Promise<string>;
+export declare function reconciliationSupportedOutcome(observation: ReconciliationObservation): "applied" | "conflict" | "failed";
+export declare function reconciliationReceipt(intent: StoredWritebackIntent, observation: ReconciliationObservation, outcome: "applied" | "conflict" | "failed", runnerId: string, reason: string): ExecutionReceiptV2 | ExecutionReceiptV3 | ExecutionReceiptV4;
 export {};
 //# sourceMappingURL=cli.d.ts.map

package/dist/cli.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"cli.d.ts","sourceRoot":"","sources":["../src/cli.ts"],"names":[],"mappings":";AAYA,OAAO,EAAoP,KAAK,WAAW,EAA0H,MAAM,6BAA6B,CAAC;AAwBza,OAAO,EAA6G,KAAK,YAAY,EAAwB,MAAM,2BAA2B,CAAC;AAE/L,OAAO,EAOL,KAAK,gBAAgB,EAEtB,MAAM,mCAAmC,CAAC;AAmV3C,wBAAsB,IAAI,CAAC,IAAI,EAAE,MAAM,EAAE,GAAG,OAAO,CAAC,MAAM,CAAC,CA4D1D;AA0FD,KAAK,SAAS,GAAG,CAAC,QAAQ,EAAE,MAAM,EAAE,YAAY,CAAC,EAAE,MAAM,KAAK,OAAO,CAAC,MAAM,CAAC,CAAC;AAE9E,wBAAsB,aAAa,CACjC,IAAI,EAAE,MAAM,EAAE,EACd,OAAO,GAAE;IACP,GAAG,CAAC,EAAE,SAAS,CAAC;IAChB,GAAG,CAAC,EAAE,MAAM,CAAC,UAAU,CAAC;IACxB,UAAU,CAAC,EAAE,gBAAgB,CAAC;IAC9B,OAAO,CAAC,EAAE,WAAW,CAAC;IACtB,MAAM,CAAC,EAAE,IAAI,CAAC,MAAM,CAAC,WAAW,EAAE,OAAO,CAAC,CAAC;CACvC,GACL,OAAO,CAAC,MAAM,CAAC,CA2TjB;AA+gFD,wBAAsB,0BAA0B,CAAC,GAAG,EAAE,YAAY,EAAE,UAAU,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,CAAC,UAAU,GAAG,OAAO,CAAC,MAAM,CAAC,CAS/H"}
+{"version":3,"file":"cli.d.ts","sourceRoot":"","sources":["../src/cli.ts"],"names":[],"mappings":";AAYA,OAAO,EAAoP,KAAK,WAAW,EAA0H,MAAM,6BAA6B,CAAC;AAIza,OAAO,EAgBL,KAAK,qBAAqB,EAK3B,MAAM,iCAAiC,CAAC;AACzC,OAAO,EAAgI,KAAK,kBAAkB,EAAE,KAAK,kBAAkB,EAAE,KAAK,kBAAkB,EAAuD,KAAK,YAAY,EAAwB,MAAM,2BAA2B,CAAC;AAElV,OAAO,EAQL,KAAK,gBAAgB,EAEtB,MAAM,mCAAmC,CAAC;AAC3C,OAAO,EAUL,KAAK,yBAAyB,EAE/B,MAAM,8BAA8B,CAAC;AAyUtC,wBAAsB,IAAI,CAAC,IAAI,EAAE,MAAM,EAAE,GAAG,OAAO,CAAC,MAAM,CAAC,CA6D1D;AA0FD,KAAK,SAAS,GAAG,CAAC,QAAQ,EAAE,MAAM,EAAE,YAAY,CAAC,EAAE,MAAM,KAAK,OAAO,CAAC,MAAM,CAAC,CAAC;AAE9E,wBAAsB,aAAa,CACjC,IAAI,EAAE,MAAM,EAAE,EACd,OAAO,GAAE;IACP,GAAG,CAAC,EAAE,SAAS,CAAC;IAChB,GAAG,CAAC,EAAE,MAAM,CAAC,UAAU,CAAC;IACxB,UAAU,CAAC,EAAE,gBAAgB,CAAC;IAC9B,OAAO,CAAC,EAAE,WAAW,CAAC;IACtB,MAAM,CAAC,EAAE,IAAI,CAAC,MAAM,CAAC,WAAW,EAAE,OAAO,CAAC,CAAC;CACvC,GACL,OAAO,CAAC,MAAM,CAAC,CA0YjB;AAgmGD,wBAAsB,0BAA0B,CAAC,GAAG,EAAE,YAAY,EAAE,UAAU,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,CAAC,UAAU,GAAG,OAAO,CAAC,MAAM,CAAC,CAS/H;AAs4CD,wBAAgB,8BAA8B,CAAC,WAAW,EAAE,yBAAyB,GAAG,SAAS,GAAG,UAAU,GAAG,QAAQ,CAKxH;AAED,wBAAgB,qBAAqB,CACnC,MAAM,EAAE,qBAAqB,EAC7B,WAAW,EAAE,yBAAyB,EACtC,OAAO,EAAE,SAAS,GAAG,UAAU,GAAG,QAAQ,EAC1C,QAAQ,EAAE,MAAM,EAChB,MAAM,EAAE,MAAM,GACb,kBAAkB,GAAG,kBAAkB,GAAG,kBAAkB,CAgH9D"}

package/dist/local-ui.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"local-ui.d.ts","sourceRoot":"","sources":["../src/local-ui.ts"],"names":[],"mappings":"AAEA,OAAO,EAAsC,KAAK,MAAM,EAAuB,MAAM,WAAW,CAAC;AAIjG,OAAO,EAAE,aAAa,EAAgD,MAAM,iCAAiC,CAAC;AAI9G,MAAM,MAAM,cAAc,GAAG;IAC3B,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,eAAe,CAAC,EAAE,OAAO,CAAC;IAC1B,IAAI,CAAC,EAAE,OAAO,CAAC;IACf,WAAW,CAAC,EAAE,kBAAkB,CAAC;CAClC,CAAC;AAEF,MAAM,MAAM,kBAAkB,GAAG,CAAC,CAAC,EACjC,IAAI,EAAE,MAAM,GAAG,OAAO,EACtB,SAAS,EAAE,MAAM,EACjB,QAAQ,EAAE,CAAC,KAAK,EAAE,aAAa,KAAK,CAAC,KAClC,OAAO,CAAC,CAAC,CAAC,CAAC;AAEhB,MAAM,MAAM,aAAa,GAAG;IAC1B,MAAM,EAAE,MAAM,CAAC;IACf,GAAG,EAAE,MAAM,CAAC;IACZ,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,KAAK,EAAE,MAAM,CAAC;IACd,SAAS,EAAE,MAAM,CAAC;IAClB,KAAK,EAAE,MAAM,OAAO,CAAC,IAAI,CAAC,CAAC;CAC5B,CAAC;AAEF,wBAAsB,kBAAkB,CAAC,OAAO,GAAE,cAAmB,GAAG,OAAO,CAAC,aAAa,CAAC,CA+C7F"}
+{"version":3,"file":"local-ui.d.ts","sourceRoot":"","sources":["../src/local-ui.ts"],"names":[],"mappings":"AAEA,OAAO,EAAsC,KAAK,MAAM,EAAuB,MAAM,WAAW,CAAC;AAIjG,OAAO,EAAE,aAAa,EAA6E,MAAM,iCAAiC,CAAC;AAK3I,MAAM,MAAM,cAAc,GAAG;IAC3B,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,eAAe,CAAC,EAAE,OAAO,CAAC;IAC1B,IAAI,CAAC,EAAE,OAAO,CAAC;IACf,WAAW,CAAC,EAAE,kBAAkB,CAAC;CAClC,CAAC;AAEF,MAAM,MAAM,kBAAkB,GAAG,CAAC,CAAC,EACjC,IAAI,EAAE,MAAM,GAAG,OAAO,EACtB,SAAS,EAAE,MAAM,EACjB,QAAQ,EAAE,CAAC,KAAK,EAAE,aAAa,KAAK,CAAC,KAClC,OAAO,CAAC,CAAC,CAAC,CAAC;AAEhB,MAAM,MAAM,aAAa,GAAG;IAC1B,MAAM,EAAE,MAAM,CAAC;IACf,GAAG,EAAE,MAAM,CAAC;IACZ,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,KAAK,EAAE,MAAM,CAAC;IACd,SAAS,EAAE,MAAM,CAAC;IAClB,KAAK,EAAE,MAAM,OAAO,CAAC,IAAI,CAAC,CAAC;CAC5B,CAAC;AAEF,wBAAsB,kBAAkB,CAAC,OAAO,GAAE,cAAmB,GAAG,OAAO,CAAC,aAAa,CAAC,CA+C7F"}