@sackville-mcp/cli 0.0.1-alpha.0

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 2026 Curtis Autery
+
+   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,288 @@
+# @sackville-mcp/cli
+
+The Sackville command-line tool — a human entry point over the same engines the
+MCP servers expose. Two surfaces:
+
+- **docs search** (`search`/`get`/`versions`/`detect`) over [`@sackville-mcp/core`](../core).
+- **API testing** (`api …`) over [`@sackville-mcp/api`](../api).
+
+## Install / invoke
+
+There's no published npm package yet, so run it from the built workspace:
+
+```bash
+pnpm -r build                          # once (or: pnpm -F @sackville-mcp/cli build)
+node packages/cli/dist/bin.mjs --help
+```
+
+The examples below use `sackville` as shorthand for `node packages/cli/dist/bin.mjs`.
+
+---
+
+## API testing quickstart
+
+Sackville runs **Bruno `.bru`** requests from a **collection directory**. Its
+richer assertions and captures live in a sidecar `<request>.sackville.yml` next
+to each `.bru`, so the `.bru` stays 100% Bruno-GUI compatible (ADR 0004).
+
+```
+mycollection/
+  bruno.json                 # optional Bruno collection marker
+  get-user.bru               # the request
+  get-user.sackville.yml      # optional: assertions + captures
+  environments/Public.bru    # optional: {{baseUrl}} and other vars
+```
+
+A ready-to-run sample lives at [`examples/api/jsonplaceholder`](../../examples/api/jsonplaceholder)
+(hits the free, no-auth [JSONPlaceholder](https://jsonplaceholder.typicode.com) API).
+
+**1. See what's in a collection:**
+
+```console
+$ sackville api list examples/api/jsonplaceholder
+POST  create-post  {{baseUrl}}/posts
+GET  get-user  {{baseUrl}}/users/1
+GET  list-posts  {{baseUrl}}/posts?userId=1
+```
+
+**2. Inspect one request** (reports the secret *names* a request needs, never values):
+
+```console
+$ sackville api get examples/api/jsonplaceholder get-user
+GET  {{baseUrl}}/users/1
+  Accept: application/json
+required secrets: (none)
+```
+
+**3. Run it.** `{{baseUrl}}` comes from the `Public` environment, so no flags
+are needed beyond `--env` (or pass `--var baseUrl=https://…` instead):
+
+```console
+$ sackville api run examples/api/jsonplaceholder get-user --env Public
+GET  https://jsonplaceholder.typicode.com/users/1
+sent
+status 200  176ms
+PASS  status equals
+PASS  header contains
+PASS  jsonpath exists $.name
+body: sackville://run/<id>/body
+```
+
+Exit code is **0** only when the request was sent *and* every assertion passed
+(and, with `--openapi`, the contract validated) — so it drops straight into CI.
+
+**4. Get structured output** for scripts/agents with `--json`:
+
+```console
+$ sackville api run examples/api/jsonplaceholder get-user --env Public --json
+{ "request": {…}, "sent": true, "dryRun": false,
+  "response": { "status": 200, "assertions": [...], "captured": { "userName": "Leanne Graham" }, … } }
+```
+
+**5. Chain requests** — captures thread forward into later requests' scope:
+
+```console
+$ sackville api run-collection examples/api/jsonplaceholder get-user list-posts --env Public
+get-user  200  PASS
+list-posts  200  PASS
+captured: userName
+```
+
+### Mutation safety (deny-by-default)
+
+`GET`/`HEAD`/`OPTIONS` run freely. Mutating methods (`POST`/`PUT`/`PATCH`/`DELETE`)
+**dry-run** by default — Sackville resolves and shows what *would* be sent, but
+does not fire — and require an explicit unlock: `--unsafe` **plus** a host
+allowlist.
+
+```console
+$ sackville api run examples/api/jsonplaceholder create-post --env Public
+POST  https://jsonplaceholder.typicode.com/posts
+dry-run (not sent): POST is a mutating method; dry-run only (pass allowUnsafe to send)
+# exit 1 — nothing was verified
+
+$ sackville api run examples/api/jsonplaceholder create-post --env Public \
+    --unsafe --allow-host jsonplaceholder.typicode.com
+POST  https://jsonplaceholder.typicode.com/posts
+sent
+status 201  …
+PASS  status equals
+PASS  jsonpath exists $.id
+```
+
+### Secrets
+
+Reference secrets in a `.bru` as `{{secret:NAME}}` (never inline the value).
+Today they resolve from the environment as `SACKVILLE_SECRET_<NAME>`; a missing
+secret **fails closed**, and resolved values are redacted from every result
+(request, headers, body) — including base64/url encodings. (Keyring-backed
+storage is a scheduled opt-in.)
+
+```bash
+SACKVILLE_SECRET_API_TOKEN=… sackville api run mycollection authed-request --env Public
+```
+
+### Contract validation
+
+```bash
+# Validate a live exchange against an OpenAPI 3.1 spec in one shot — BOTH the
+# response AND the sent request's body/params (the request check runs even on a
+# withheld dry-run):
+sackville api run mycollection get-user --env Public --openapi openapi.json
+
+# Validate a live GraphQL run's query + variables against the SDL:
+sackville api run mycollection gql-search --env Public --graphql schema.graphql
+
+# Offline GraphQL drift check (no request sent): does a saved query still
+# conform to the current schema? With --variables, also type-check the variables.
+sackville api validate --graphql schema.graphql --query query.graphql --variables '{"id":5}'
+
+# Preflight a REQUEST (body + params) against an OpenAPI 3.1 operation, no send:
+# (scalar; array params [query form/space/pipe + path/header]; object params
+#  [deepObject + form/explode=false]; ambiguous serializations skip-not-fail — ADR 0016)
+sackville api validate-request --openapi openapi.json --method POST --path /widgets \
+  --body new-widget.json --query limit=10
+
+# Validate the traffic in a captured HAR against a contract (no request re-run):
+sackville api validate-capture run.har.zip --openapi openapi.json
+```
+
+### Command reference
+
+```
+sackville api list  <dir>
+sackville api get   <dir> <name>
+sackville api run   <dir> <name> [--var k=v]… [--env <e>] [--unsafe] [--allow-host <h>]… [--openapi <spec.json>] [--graphql <schema>] [--json]
+sackville api run-collection <dir> <name>… [--var k=v]… [--env <e>] [--unsafe] [--allow-host <h>]… [--stop-on-failure] [--json]
+sackville api validate --graphql <schema> --query <query> [--variables <json|file>] [--json]
+sackville api validate-request --openapi <spec.json> --method <M> --path </p> [--body <file>] [--query k=v]… [--header n:v]… [--json]
+sackville api validate-capture <har.zip> [--openapi <spec.json>] [--graphql <schema>] [--graphql-endpoint </p>] [--json]
+```
+
+`<name>` is the `.bru` file stem (e.g. `get-user` for `get-user.bru`).
+
+---
+
+## Browser testing
+
+Single-shot page inspection over a real headless Chromium. Each command navigates
+once and reads, then tears the browser down — so it's a quick human probe, not the
+stateful agent surface (that's `sackville-browser-mcp`). Every request is fronted by
+a **mandatory DNS-pinning SSRF proxy**; navigation is allowed only to the host you
+typed (auto-allowed as explicit operator intent) plus any `--allow-host`.
+
+```bash
+# The ARIA snapshot (with [ref=…] ids) of a page:
+$ sackville browser snapshot https://example.com
+
+# Accessibility audit — prints a summary + the full report path; exits 1 if any
+# violations (usable as a CI gate):
+$ sackville browser audit https://example.com
+
+# Save a PNG screenshot:
+$ sackville browser screenshot https://example.com --out shot.png
+
+# Inspecting a local dev server (loopback) needs --allow-private; sandboxed
+# environments may need --no-sandbox:
+$ sackville browser snapshot http://127.0.0.1:3000 --allow-private --no-sandbox
+```
+
+### Replaying a persisted flow
+
+A **flow** is a Bruno-openable `<name>.bru` (meta) + a `<name>.sackville.yml`
+sidecar holding ordered `steps` keyed by semantic locators (role + accessible
+name), not ephemeral snapshot refs — so it replays stably. See
+[`examples/browser/login`](../../examples/browser/login). The flow drives its own
+navigations, so allowlist each target host with `--allow-host`; mutations
+(`click`/`fill`/…) **dry-run** unless `--unsafe`. `{{var}}` comes from `--var`;
+`{{secret:NAME}}` from `SACKVILLE_BROWSER_SECRET_<NAME>` (redacted from output).
+Exits non-zero on any step error or failed assertion (a CI gate).
+
+```bash
+$ SACKVILLE_BROWSER_SECRET_PASSWORD=hunter2 \
+    sackville browser run examples/browser/login/login.bru \
+      --var baseUrl=https://app.example.com --var username=alice \
+      --allow-host app.example.com --unsafe
+```
+
+### Command reference
+
+```
+sackville browser snapshot   <url> [--allow-host <h>]… [--allow-private] [--no-sandbox] [--headed] [--json]
+sackville browser audit      <url> [same flags]                        # exit 1 on a11y violations
+sackville browser screenshot <url> [--out <file>] [--full-page] [same flags]
+sackville browser run        <flow.bru> [--var k=v]… [--unsafe] [--allow-host <h>]… [same flags]  # exit 1 on failure
+```
+
+---
+
+## Verification (Phase-4 pillars)
+
+Thin human wrappers over the cross-cutting verification engines. You are the
+operator, so the run/write gates are straight-through flags (`--allow-run`,
+`--allow-quarantine`) — a denied run never spawns. `audit`/`uncovered-in-diff`
+exit non-zero on a finding, so they double as CI gates.
+
+```bash
+# Mutation testing — view a report, or run Stryker (gated):
+sackville mutate summarize reports/mutation/mutation.json
+sackville mutate summarize results.txt --format mutmut
+sackville mutate run . --allow-run --file src/changed.ts --incremental
+
+# Coverage — the forgotten-assertion catch (exit 1 when a new line is uncovered):
+sackville coverage uncovered-in-diff --diff changes.diff --coverage coverage-final.json --project-root .
+sackville coverage run-scoped . --changed-file src/changed.ts --diff changes.diff --allow-run
+
+# Flaky-test detection over a run-history DB (--db / SACKVILLE_FLAKE_DB):
+sackville flake ingest report.json --db flake.db --format vitest
+sackville flake status --db flake.db
+sackville flake candidates --db flake.db
+sackville flake run . --db flake.db --repeat 10 --allow-run
+sackville flake quarantine 'src/x.test.ts > flaky case' --db flake.db \
+    --reason 'intermittent timeout' --expires-at 2026-07-01T00:00:00Z \
+    --allow-quarantine --max-expiry-ms 2592000000
+
+# Dependency intelligence for the INSTALLED version (exit 1 on a finding):
+sackville deps audit . lodash --osv-db /var/lib/sackville/osv
+sackville deps audit-project . --osv-db /var/lib/sackville/osv
+sackville deps changelog lodash --project . --to 4.17.21
+
+# Semantic code navigation via a real Language Server (single-shot; gated).
+# --servers (or SACKVILLE_LSP_SERVERS) binds the operator language→server registry;
+# navigation needs --allow-run, rename writes only with --allow-write (else dry-run):
+export SACKVILLE_LSP_SERVERS='{"typescript":{"command":"typescript-language-server","args":["--stdio"]}}'
+sackville lsp languages
+sackville lsp definition typescript src/app.ts 42 8 --project . --allow-run
+sackville lsp references typescript src/app.ts 42 8 --project . --allow-run
+sackville lsp symbols typescript src/app.ts --project . --allow-run
+sackville lsp workspace-symbols typescript MyClass src/app.ts --project . --allow-run      # project-wide search; trailing file anchors the project (tsserver needs it)
+sackville lsp diagnostics typescript src/app.ts --project . --allow-run                     # errors/warnings (push model; empty = clean; exit 2 = still indexing)
+sackville lsp definition typescript packages/a/src/x.ts 4 14 --project packages/a --workspace-root packages/b --allow-run  # multi-root: bind both packages on one server
+sackville lsp rename typescript src/app.ts 42 8 newName --project . --allow-run            # dry-run preview
+sackville lsp rename typescript src/app.ts 42 8 newName --project . --allow-run --allow-write  # writes to disk
+```
+
+`lsp` exit codes: `0` the query ran, `1` denied/refused/error, `2` the server is
+still indexing (retry). A result `status` is tri-state (`ok`/`not_ready`/`no_result`);
+`rename` is dry-run unless `--allow-write`, and `applied` in the result says whether
+the edit was written.
+
+`audit`/`audit-project` report `osvSnapshotLoaded` — without an operator OSV
+snapshot, "no known vulnerabilities" is unknown, not clean. The deps CLI fetches
+package metadata behind the same DNS-pinning SSRF pre-flight the bins use (private
+registries gated by `--allow-private`).
+
+---
+
+## Docs search
+
+```bash
+sackville search <query…> [-l <lib>] [--version <v>] [--installed <v>] [-p <dir>] [--ecosystem <e>] [--type <t>] [--limit <n>] [--json]
+sackville get <id> [--json]
+sackville versions <library>
+sackville detect <project> <library> [--ecosystem <node|python|ruby>]
+
+# Global: -i/--index <file> (or set SACKVILLE_INDEX) — the SQLite index to query.
+```
+
+See [`packages/mcp`](../mcp) for building an index and the agent-facing MCP servers.

package/dist/bin.d.mts

@@ -0,0 +1 @@
+export { };

package/dist/bin.mjs

@@ -0,0 +1,15 @@
+#!/usr/bin/env node
+import { t as run } from "./src-DM4aqvlX.mjs";
+import { QueryEmbedder } from "@sackville-mcp/embed";
+//#region src/bin.ts
+const code = await run(process.argv.slice(2), {
+	out: (s) => process.stdout.write(s),
+	err: (s) => process.stderr.write(s),
+	embedder: new QueryEmbedder(),
+	env: process.env
+});
+process.exit(code);
+//#endregion
+export {};
+
+//# sourceMappingURL=bin.mjs.map

package/dist/bin.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"bin.mjs","names":[],"sources":["../src/bin.ts"],"sourcesContent":["#!/usr/bin/env node\nimport { QueryEmbedder } from '@sackville-mcp/embed'\nimport { run } from './index.js'\n\nconst code = await run(process.argv.slice(2), {\n  out: (s) => process.stdout.write(s),\n  err: (s) => process.stderr.write(s),\n  embedder: new QueryEmbedder(),\n  env: process.env,\n})\nprocess.exit(code)\n"],"mappings":";;;;AAIA,MAAM,OAAO,MAAM,IAAI,QAAQ,KAAK,MAAM,CAAC,GAAG;CAC5C,MAAM,MAAM,QAAQ,OAAO,MAAM,CAAC;CAClC,MAAM,MAAM,QAAQ,OAAO,MAAM,CAAC;CAClC,UAAU,IAAI,cAAc;CAC5B,KAAK,QAAQ;AACf,CAAC;AACD,QAAQ,KAAK,IAAI"}

package/dist/index.d.mts

@@ -0,0 +1,15 @@
+import { Embedder } from "@sackville-mcp/embed";
+
+//#region src/index.d.ts
+/** Output sinks and dependencies injected into `run` (so it is testable). */
+interface CliIO {
+  out: (text: string) => void;
+  err: (text: string) => void;
+  /** When present, queries are embedded for hybrid search. */
+  embedder?: Embedder;
+  env?: Record<string, string | undefined>;
+}
+declare function run(argv: string[], io: CliIO): Promise<number>;
+//#endregion
+export { CliIO, run };
+//# sourceMappingURL=index.d.mts.map

package/dist/index.d.mts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.mts","names":[],"sources":["../src/index.ts"],"mappings":";;;;UAsBiB,KAAA;EACf,GAAA,GAAM,IAAA;EACN,GAAA,GAAM,IAAA;;EAEN,QAAA,GAAW,QAAA;EACX,GAAA,GAAM,MAAM;AAAA;AAAA,iBA0DQ,GAAA,CAAI,IAAA,YAAgB,EAAA,EAAI,KAAA,GAAQ,OAAO"}

package/dist/index.mjs

@@ -0,0 +1,2 @@
+import { t as run } from "./src-DM4aqvlX.mjs";
+export { run };