@velarscript/desktop 0.10.1

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,247 @@
+# @velarscript/desktop
+
+The optional single-project VelarScript Desktop framework. Application authors
+write one ordinary VelarScript source graph with the same components, JSX,
+Look, state, derived values, resources, and actions used by
+`@velarscript/web`. There is no user-facing renderer project, main project,
+local server, port, or IPC layer.
+
+Internally the package composes the Web compiler/runtime with a least-privilege
+Node capability host and a thin operating-system WebView shell. Privileged APIs
+remain asynchronous and are transported through a versioned bridge generated
+by the framework. That separation is an implementation and security boundary,
+not a second application programming model.
+
+Each official target module captures the bridge identity, its data-valued
+invoke operation, and any platform/environment snapshot fields when that module
+initializes. Replacing a global bridge later cannot reroute an official API.
+The system-WebView transport also captures its serializer, encoders, timers,
+collections, Promise constructor, and native message handler before application
+JavaScript executes, so ordinary dependency code cannot monkey-patch an active
+capability call into a different transport.
+`velar/desktop-test` is the intentional exception: the controller installs a
+fresh isolated browser Page for each test, so the helper resolves and validates
+one data-only controller snapshot per call instead of retaining authority from
+the previous test.
+
+```json
+{
+  "formatVersion": 2,
+  "entry": "src/main.vel",
+  "outDir": "dist/renderer",
+  "publicDir": "public",
+  "extensions": ["@velarscript/desktop"],
+  "desktop": {
+    "productName": "Example",
+    "identifier": "com.example.app",
+    "permissions": {
+      "files": ["project"],
+      "processes": ["git"],
+      "terminal": true,
+      "network": ["https://api.example.com"]
+    }
+  }
+}
+```
+
+The macOS host uses the system WKWebView and never bundles Chromium, Electron,
+or Tauri. Thin builds keep Node external and require Node.js 24 or newer. The
+package supplies the borderless VelarScript mark as the default application
+icon, so a project receives a branded Dock and Finder identity without owning
+platform icon files. A future custom-icon contract must remain an explicit
+project setting rather than replacing this package default implicitly.
+The host resolves an explicit absolute `VELAR_DESKTOP_NODE`, absolute entries from
+the launch environment's `PATH`, and trusted system package-manager locations
+without a shell, then verifies the runtime version. Build-machine executable
+paths and versions are not embedded in the application.
+A future standalone profile must report its runtime bytes separately instead
+of hiding them from the application size budget.
+`velar package` asks the CLI package host to build the exact official language
+server, the bounded project-task launcher, the platform build engine, and the
+native PTY helper. They
+are stored under `Contents/Resources/host` and counted separately as language,
+task, build-engine, terminal-host, and capability-Worker bytes. The generated tools contain the official
+Core/Web/Desktop compiler extensions and source-backed standard assets, so the
+installed application neither searches `PATH` for `velar`, resolves project npm
+packages, nor depends on the build workspace. The default Desktop size budget
+is currently 32 MiB. It is an accounting threshold rather than an architecture
+ceiling: a project may set `desktop.build.sizeBudgetBytes` to a larger measured
+value when the bundle composition explains the growth. The package command
+still reports every component and the application tree hash; size pressure must
+not split a privileged owner across the renderer boundary.
+
+Desktop owns `velar/desktop` and permission-scoped target implementations of
+`velar/fs`, `velar/path`, `velar/process`, `velar/http`, and `velar/env`.
+Packaged applications may call `languageServer() -> Promise<LanguageServer>`.
+The returned owner sends and pulls bounded JSON message bodies through
+`send(message)`, `next()`, and idempotent `close()`; Content-Length framing,
+the exact official executable, and child-process ownership remain private to
+Desktop. Only one pull may be pending, at most four servers may be live, and
+document-generation retirement, project-grant replacement, Worker failure, or
+host shutdown reaps the corresponding process group. This exact official tool
+does not require a general process permission and cannot launch an arbitrary
+command.
+Applications with the `project` file grant may also call
+`projectChanges() -> Promise<ProjectChanges>`. Desktop binds the returned owner
+to the same durable `@velaros-ai/project` kernel that prepares and validates
+transactions. The public surface is intentionally finite: `list(limit)`,
+`get(transactionId)`, pull-based `subscribe()`, `apply(transactionId)`,
+`rollback(transactionId)`, and idempotent `close()`. It exposes reviewable
+intent, patch, diff, risk, revision, lifecycle, and timestamp projections, but
+never the project root, persistence paths, policies, providers, old/new full
+file contents, arbitrary metadata, or a caller-selected file operation.
+Transactions and their latest projections are committed under the app-data
+root before project mutation; a restarted Worker restores an interrupted
+apply/rollback to its prior durable state and fails closed if an external edit
+conflicts with that recovery. The JSONL change feed is fsynced before
+subscribers observe a row. Subscriptions coalesce the latest record per
+transaction and request a full `list()` rescan on bounded queue overflow.
+Changing the project grant retires existing handles; an already-running
+apply/rollback finishes against the original durable owner before that owner is
+closed. The complete owner is bundled into the existing Node capability Worker
+and adds about 4.39 MiB; there is still no Electron-style user main process,
+second source graph, local server, port, or renderer-accessible IPC design.
+
+Applications with the `project` file grant may also call
+`startProjectTask(ProjectTaskCommand, arguments, options)`. The finite command
+set is `check`, `test`, `browserTest`, `build`, `fix`, `package`, and `run`;
+only `run` accepts program arguments. `browserTest` always runs all three
+engines through the packaged official browser-test supervisor and cannot
+accept a browser, output-directory, or CLI-flag override. The Playwright driver
+is counted in the application bundle; matching Chromium, Firefox, and WebKit
+binaries remain an explicit external Playwright cache and a missing engine
+fails the task instead of silently reducing coverage.
+The returned `ProjectTask` exposes its package-owned PID plus pull-based
+`next()`, terminal `wait()`, and bounded `stop()` operations. Desktop fixes the
+working directory to the current canonical project grant, injects only its
+counted build-engine path, and for `package` only, the Worker-validated current
+application Resources template. The package host rebuilds the target renderer
+and copies the same versioned official tools and native system-WebView assets;
+it does not resolve project `node_modules`, a source checkout, or `PATH`.
+Desktop exposes no executable, shell, working-directory, environment,
+package-manager, or caller-controlled browser-test option. Output is incrementally
+decoded and tagged by `ProjectTaskOutputChannel`, only one pull may be active,
+at most four tasks may live, output and timeout are bounded, and callers must
+consume output before waiting. Explicit stop, timeout, document retirement,
+project replacement, Worker failure, and host shutdown reuse the same
+process-group termination and confirmed-reaping owner as `velar/process`.
+Applications with the `project` file grant and an explicit
+`desktop.permissions.terminal: true` grant may call
+`openTerminal({columns, rows}) -> Promise<TerminalSession>`. Desktop fixes the
+working directory to the current canonical project, launches only the user's
+trusted login shell, and exposes no executable, shell path, cwd, environment,
+or command-string option. The returned owner publishes the shell PID and
+bounded `write(text)`, `resize(columns, rows)`, pull-based `next()`, terminal
+`wait()`, and idempotent `close()` operations. Input chunks are capped at 1 MiB,
+the decoded output queue applies PTY backpressure at 2 MiB and fails closed
+above 4 MiB, one pull may be active, and at most four sessions may live. The
+output stream must be consumed through its final `null` before `wait()`; an
+explicit `close()` discards that requirement while still confirming cleanup. The
+package-owned native helper and the shell occupy separate process groups;
+Desktop publishes both to its native crash owner before returning the session.
+Explicit close, document retirement, project replacement, Worker failure, and
+host shutdown terminate and confirm reaping of both groups. Terminal output is
+the PTY's UTF-8 text, including control sequences emitted by interactive
+programs; presentation and session/tab orchestration remain application UX.
+Applications with the `project` file grant may call
+`selectProjectDirectory()` to open the native directory chooser. A successful
+choice atomically replaces the single project grant for subsequent relative
+`velar/fs`, `velar/path`, and default process-working-directory operations;
+cancel returns `null`. `selectedProjectDirectory()` reports only a user-picked
+or restored grant, while `projectDirectory()` continues to report the current
+effective root, including the private app-data fallback before any selection.
+The macOS host persists the user's explicit choice as a bounded bookmark and
+restores it before renderer startup. Project selection has no arbitrary timeout
+while the native chooser is open. Replacing the grant cancels unpublished
+capability work and releases project-owned processes; filesystem effects that
+already reached the operating system may still settle, with their retired
+results discarded. The capability Worker revalidates the replacement directory
+and keeps the independent `app-data` grant unchanged. This is one dynamic
+single-project authority, not a renderer-owned allowlist and not a second file
+API.
+`velar/fs.createText` preserves Node's exclusive no-clobber contract inside the
+capability Worker; authorization and creation remain one bounded native effect
+rather than a renderer-side check followed by an overwriting write.
+`replaceTextIfMatches` carries the same optimistic edit contract: file
+mutations for one canonical target are coordinated inside the capability
+Worker and a matching replacement commits by same-directory rename. External
+processes outside the bridge are not silently described as participants in
+that lock.
+`watchFiles` also preserves Node's public pull contract and bounds: one active
+`next()`, at most 128 live watchers, a 4,096-path/2 MiB coalescing queue, and
+`rescan=true` when a native event cannot identify a safe path. Watcher handles
+belong to the current document generation and granted roots. Explicit
+`close()`, owner retirement, input shutdown, fatal drain, and a successful
+project-root replacement all close them; a pending pull cannot publish an
+event from the old project after authority changes.
+Desktop preserves the shared HTTP failure model across its native bridge:
+non-2xx, cancellation/timeout, and request/response transport failures remain
+distinct typed errors instead of collapsing Worker failures into one string.
+`process.start` is async on Node and Desktop. Process-only applications may
+omit file grants and use the launch directory as the default working directory;
+an explicit working directory must be inside a granted file root. Exact
+executable grants prevent shell parsing but do not claim to OS-sandbox the
+native program's own effects—product approval and tool policy remain outside
+the language package. Process stdout/stderr crosses the worker bridge as
+enum-tagged pull chunks consumed by `async for`; incremental UTF-8 decoding,
+single-reader ownership, output bounds, and the consume-before-`wait` lifecycle
+match the Node target. The renderer reuses Node's internal process host ABI for
+value validation, Map snapshots, Promise operations, and result assembly, and
+composes the compiler-owned UTF-8 budget runtime. Desktop does not maintain a
+second semantic implementation and adds only its capability bridge and isolated
+worker. HTTP response bodies cross the
+bridge as bounded pull-based chunks, so timeout and cancellation remain active
+through body consumption. Redirects continue only while every exact origin is
+granted. `desktop.permissions.secrets` is disjoint from readable environment
+permissions; `velar/http.secretHeader` lets the worker inject those values
+without exposing them to the renderer, and cross-origin redirects strip every
+secret-derived header. Large filesystem, process-input, and HTTP-request values use a bounded
+bidirectional chunk transport instead of inheriting WebView message-size
+accidents.
+
+Each loaded main document owns a private bridge generation. Page request IDs
+may restart at one after reload, but the native host translates the generation
+and page ID to a host-global Worker request ID before forwarding. Committed
+navigation retires the old generation: late responses are discarded, old
+process groups are terminated, old HTTP streams are aborted, and the Worker
+rejects any handle used by a different generation. Native completion injection
+requires the private generation as well, so application JavaScript cannot
+resolve a pending bridge request by invoking the transport hook with only a
+guessed numeric ID. Filesystem work that has already reached the OS may finish;
+its retired response is never routed into the replacement document.
+Pending serialized requests and assembled response chunks each share a 128 MiB
+aggregate bridge budget, so the 1,024-request count cannot multiply every
+per-request limit into unbounded transport memory. A finite bridge timeout
+sends a private generation-qualified cancellation before rejecting. Native
+code discards the later response without treating it as an unknown protocol
+message, and the Worker aborts an active HTTP request or stops a process that
+has not safely transferred its public handle. Filesystem effects remain
+non-cancellable and retain their bounded request reservation until they settle.
+
+Filesystem content calls follow symlinks only when the canonical target stays
+inside a granted root. Metadata, move, and removal operate on the final entry
+instead; dangling links cannot be used as write targets. The renderer, native
+worker, and deterministic test host independently enforce the same path,
+file-size, list-count, list-text, result-shape, and replacement contracts.
+Desktop path composition rejects sparse/accessor-backed Lists and checks the
+combined result, not just each input. Native home, app-data, and project paths
+must remain absolute and bounded. Readable environment values are snapshotted
+from data descriptors under the same 64-variable, 64 KiB item, and 1 MiB total
+budgets enforced by the native host.
+
+```sh
+velar package .
+velar test . --browser=all
+```
+
+`velar test --browser` runs `.browser.test.vel` files without opening a window.
+It installs a deterministic, permission-aware in-memory Desktop filesystem,
+finite ProjectChanges owner, and deterministic handles for manifest-granted
+processes; the native worker keeps a separate integration suite for real
+filesystem, process, network, and durable transaction enforcement. Test
+modules may import the restricted `velar/desktop-test` helpers to inspect
+app-data/project text, create a bounded test directory, and call
+`seedProjectChange(transactionId, lifecycle, diff)` through the page's actual
+capability bridge;
+ordinary `velar/fs` remains application-side and is not faked in the test
+controller process.

package/dist/build.d.ts

@@ -0,0 +1,53 @@
+import type { VelarDesktopConfig } from "./config.ts";
+export interface DesktopBuildManifest {
+    readonly formatVersion: 2;
+    readonly kind: "velar-desktop-build";
+    readonly productName: string;
+    readonly identifier: string;
+    readonly version: string;
+    readonly platform: "macos";
+    readonly architecture: string;
+    readonly hostProtocolVersion: 1;
+    readonly runtime: {
+        readonly kind: "external-node";
+        readonly minimumMajor: 24;
+        readonly discovery: "environment-and-system-paths";
+        readonly embedded: false;
+    };
+    readonly applicationBundle: string;
+    readonly sizeBudgetBytes: number;
+    readonly sizes: {
+        readonly hostBytes: number;
+        readonly rendererBytes: number;
+        readonly capabilityHostBytes: number;
+        readonly languageServerBytes: number;
+        readonly projectTaskBytes: number;
+        readonly buildEngineBytes: number;
+        readonly terminalHostBytes: number;
+        readonly toolchainBytes: number;
+        readonly metadataBytes: number;
+        readonly totalBytes: number;
+    };
+    readonly sha256: string;
+}
+export interface DesktopBuildResult {
+    readonly outputDirectory: string;
+    readonly applicationBundle: string;
+    readonly manifestPath: string;
+    readonly manifest: DesktopBuildManifest;
+}
+export type DesktopBuildSizes = DesktopBuildManifest["sizes"];
+/**
+ * MIG-3: a budget failure that reports only the total forces upstream
+ * archaeology before anyone can judge whether raising the budget is safe. The
+ * composition — every component, its share, and the mandatory first-party
+ * tooling floor no project can shrink — makes that judgment possible in one
+ * pass, so this is the one message the failure prints.
+ */
+export declare function desktopSizeBudgetFailure(sizes: DesktopBuildSizes, sizeBudgetBytes: number): string | null;
+export declare function formatDesktopBytes(value: number): string;
+export declare function buildDesktopApplication(projectRoot: string, config: VelarDesktopConfig, buildRenderer: (outputDirectory: string) => Promise<void>, buildTool: (tool: {
+    readonly id: string;
+    readonly outputFile: string;
+}) => Promise<void>): Promise<DesktopBuildResult>;
+//# sourceMappingURL=build.d.ts.map

package/dist/build.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"build.d.ts","sourceRoot":"","sources":["../src/build.ts"],"names":[],"mappings":"AAKA,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,aAAa,CAAC;AAEtD,MAAM,WAAW,oBAAoB;IACnC,QAAQ,CAAC,aAAa,EAAE,CAAC,CAAC;IAC1B,QAAQ,CAAC,IAAI,EAAE,qBAAqB,CAAC;IACrC,QAAQ,CAAC,WAAW,EAAE,MAAM,CAAC;IAC7B,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAC;IAC5B,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;IACzB,QAAQ,CAAC,QAAQ,EAAE,OAAO,CAAC;IAC3B,QAAQ,CAAC,YAAY,EAAE,MAAM,CAAC;IAC9B,QAAQ,CAAC,mBAAmB,EAAE,CAAC,CAAC;IAChC,QAAQ,CAAC,OAAO,EAAE;QAChB,QAAQ,CAAC,IAAI,EAAE,eAAe,CAAC;QAC/B,QAAQ,CAAC,YAAY,EAAE,EAAE,CAAC;QAC1B,QAAQ,CAAC,SAAS,EAAE,8BAA8B,CAAC;QACnD,QAAQ,CAAC,QAAQ,EAAE,KAAK,CAAC;KAC1B,CAAC;IACF,QAAQ,CAAC,iBAAiB,EAAE,MAAM,CAAC;IACnC,QAAQ,CAAC,eAAe,EAAE,MAAM,CAAC;IACjC,QAAQ,CAAC,KAAK,EAAE;QACd,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;QAC3B,QAAQ,CAAC,aAAa,EAAE,MAAM,CAAC;QAC/B,QAAQ,CAAC,mBAAmB,EAAE,MAAM,CAAC;QACrC,QAAQ,CAAC,mBAAmB,EAAE,MAAM,CAAC;QACrC,QAAQ,CAAC,gBAAgB,EAAE,MAAM,CAAC;QAClC,QAAQ,CAAC,gBAAgB,EAAE,MAAM,CAAC;QAClC,QAAQ,CAAC,iBAAiB,EAAE,MAAM,CAAC;QACnC,QAAQ,CAAC,cAAc,EAAE,MAAM,CAAC;QAChC,QAAQ,CAAC,aAAa,EAAE,MAAM,CAAC;QAC/B,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAC;KAC7B,CAAC;IACF,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;CACzB;AAED,MAAM,WAAW,kBAAkB;IACjC,QAAQ,CAAC,eAAe,EAAE,MAAM,CAAC;IACjC,QAAQ,CAAC,iBAAiB,EAAE,MAAM,CAAC;IACnC,QAAQ,CAAC,YAAY,EAAE,MAAM,CAAC;IAC9B,QAAQ,CAAC,QAAQ,EAAE,oBAAoB,CAAC;CACzC;AAED,MAAM,MAAM,iBAAiB,GAAG,oBAAoB,CAAC,OAAO,CAAC,CAAC;AAkE9D;;;;;;GAMG;AACH,wBAAgB,wBAAwB,CAAC,KAAK,EAAE,iBAAiB,EAAE,eAAe,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAoBzG;AAED,wBAAgB,kBAAkB,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM,CAIxD;AAED,wBAAsB,uBAAuB,CAC3C,WAAW,EAAE,MAAM,EACnB,MAAM,EAAE,kBAAkB,EAC1B,aAAa,EAAE,CAAC,eAAe,EAAE,MAAM,KAAK,OAAO,CAAC,IAAI,CAAC,EACzD,SAAS,EAAE,CAAC,IAAI,EAAE;IAAE,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;IAAC,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAA;CAAE,KAAK,OAAO,CAAC,IAAI,CAAC,GACvF,OAAO,CAAC,kBAAkB,CAAC,CA6H7B"}