@redocly/recheck 0.15.0 → 2.58.1

package/presets/plain-language/PROVENANCE.md

@@ -131,27 +131,28 @@ sentences.
 
 From the same `clear-short` page:
 
-| Claim | Live quote | Shipped as |
-|---|---|---|
+| Claim                                                                    | Live quote                                                                                    | Shipped as                                                                                                                                                                                                                                                                                                                          |
+| ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Soft target (attributed to "writing experts", not the guide's own voice) | "Writing experts recommend paragraphs of no more than 150 words in three to eight sentences." | `plain-language/paragraph-sentence-count` — `length`, `unit: sentences`, `max: 8`, `severity: warn`. No `min`: a floor over-fires on ordinary, correct single-sentence paragraphs (a short lead-in to a code block, an image caption) — the identical reasoning `microsoft/paragraph-length` already documents for the same family. |
-| Hard ceiling, stated in the guide's own unconditional voice | "Paragraphs should never be longer than 250 words." | `plain-language/paragraph-max-words` — `length`, `unit: words`, `max: 250`, `severity: error` (unconditional, guide-stated — matches the severity policy behind `google/sentence-length`). |
+| Hard ceiling, stated in the guide's own unconditional voice              | "Paragraphs should never be longer than 250 words."                                           | `plain-language/paragraph-max-words` — `length`, `unit: words`, `max: 250`, `severity: error` (unconditional, guide-stated — matches the severity policy behind `google/sentence-length`).                                                                                                                                          |
 
 ## Word/phrase families shipped
 
 ### Filler / wordy phrases
+
 Source: `https://digital.gov/guides/plain-language/writing/style`
 ("Check your prepositions" table).
 
-| avoid | prefer (shipped) | note |
-|---|---|---|
-| a number of | several, a few, or many | |
-| a sufficient number of | enough | |
-| at this point in time | now | |
-| is able to | can | |
-| on a monthly basis | monthly | |
-| on the ground that | because | |
-| in order to | to | the exact pair the original plan named, confirmed verbatim |
-| an amount of X | X | templated (variable X) — ships separately as `plain-language/an-amount-of`, detection-only (`pattern`, no fixed replacement) |
+| avoid                  | prefer (shipped)        | note                                                                                                                         |
+| ---------------------- | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| a number of            | several, a few, or many |                                                                                                                              |
+| a sufficient number of | enough                  |                                                                                                                              |
+| at this point in time  | now                     |                                                                                                                              |
+| is able to             | can                     |                                                                                                                              |
+| on a monthly basis     | monthly                 |                                                                                                                              |
+| on the ground that     | because                 |                                                                                                                              |
+| in order to            | to                      | the exact pair the original plan named, confirmed verbatim                                                                   |
+| an amount of X         | X                       | templated (variable X) — ships separately as `plain-language/an-amount-of`, detection-only (`pattern`, no fixed replacement) |
 
 **Deliberately NOT shipped: `be responsible for` → `must`.** Live, verbatim
 on the same table, but this pairing is an odd 1:1 substitution that
@@ -162,6 +163,7 @@ there is no textual signal distinguishing the guide's intended sense
 excluded rather than shipped noisy.
 
 ### Excess intensifiers
+
 Source: `https://digital.gov/guides/plain-language/principles/short-simple`
 — a literal cut-list, not paired substitutions: "absolutely, actually,
 completely, really, quite, totally, very." Shipped as
@@ -169,19 +171,20 @@ completely, really, quite, totally, very." Shipped as
 an intensifier is an editorial call, not a mechanical substitution.
 
 ### Complex words / simple substitutes
+
 Source: `https://digital.gov/guides/writing-understanding/familiar-terms`
 ("Complex words and recommended terms to use instead").
 
-| avoid | prefer (shipped) |
-|---|---|
-| addressee | you |
-| assist, assistance | help |
-| commence | begin |
-| in order that | for |
-| in the amount of | for |
-| in the event of | if |
-| promulgate | issue |
-| utilize, utilization | use |
+| avoid                | prefer (shipped) |
+| -------------------- | ---------------- |
+| addressee            | you              |
+| assist, assistance   | help             |
+| commence             | begin            |
+| in order that        | for              |
+| in the amount of     | for              |
+| in the event of      | if               |
+| promulgate           | issue            |
+| utilize, utilization | use              |
 
 **Deliberately NOT shipped: `implement` → carry out, start.** Live,
 verbatim on this table — but in software/API documentation, "implement an
@@ -198,9 +201,9 @@ core developer-docs vocabulary. Excluded on both grounds.
 
 **`shall` never appears anywhere in this preset**, in any family — even
 though the SAME `familiar-terms` page, immediately after the table above,
-explicitly names it: *"Avoid 'shall' — Use 'must' not 'shall' to impose
+explicitly names it: _"Avoid 'shall' — Use 'must' not 'shall' to impose
 requirements. 'Shall' is ambiguous... 'Shall' is an aggressive and outdated
-word often used in legal style writing."* (verified verbatim, live,
+word often used in legal style writing."_ (verified verbatim, live,
 2026-07-30). **SHALL is a defined RFC 2119 normative keyword** (alongside
 MUST/SHOULD/MAY/MUST NOT) used throughout specifications and API/interface
 documentation — exactly Recheck's target content. A rule flagging it would
@@ -212,15 +215,16 @@ preset, named explicitly in the task's own domain-hazard callout alongside
 and `command`.
 
 ### Redundant pairs (doublets)
+
 Source:
 `https://digital.gov/guides/plain-language/principles/short-simple`
 ("Avoid doublets and triplets... Examples of doublets and recommended
 alternatives").
 
-| avoid | prefer (shipped) |
-|---|---|
-| Due and payable | Due |
-| Cease and desist | Stop |
+| avoid                     | prefer (shipped)         |
+| ------------------------- | ------------------------ |
+| Due and payable           | Due                      |
+| Cease and desist          | Stop                     |
 | Knowledge and information | Knowledge or information |
 
 **Note: "each and every," "null and void," "true and correct," "first and
@@ -240,24 +244,26 @@ payable", so ordinary uses of bare "due" (due date, due diligence, past due)
 are unaffected.
 
 ### Double negatives
+
 Source: `https://digital.gov/guides/plain-language/writing/style`
 ("Examples of recommended alternative terms for double negatives").
 
-| avoid | prefer (shipped) | mechanism |
-|---|---|---|
-| has not yet attained | is under | `swap` (fixed phrase) |
-| no fewer than | at least | `swap` (fixed phrase) |
-| may not … until | may only … when | `pattern` (variable text between the two halves in the guide's own quote — can't be a literal-phrase swap) |
-| is not … unless | only if | `pattern` (same reason) |
+| avoid                | prefer (shipped) | mechanism                                                                                                  |
+| -------------------- | ---------------- | ---------------------------------------------------------------------------------------------------------- |
+| has not yet attained | is under         | `swap` (fixed phrase)                                                                                      |
+| no fewer than        | at least         | `swap` (fixed phrase)                                                                                      |
+| may not … until      | may only … when  | `pattern` (variable text between the two halves in the guide's own quote — can't be a literal-phrase swap) |
+| is not … unless      | only if          | `pattern` (same reason)                                                                                    |
 
 ### Jargon → everyday language
+
 Source: `https://digital.gov/guides/plain-language/principles/avoid-jargon`
 ("Consider the following pairs").
 
-| avoid | prefer (shipped) |
-|---|---|
-| Riverine avifauna | River birds |
-| Involuntarily undomiciled | Unhoused |
+| avoid                     | prefer (shipped) |
+| ------------------------- | ---------------- |
+| Riverine avifauna         | River birds      |
+| Involuntarily undomiciled | Unhoused         |
 
 ## Families considered and NOT shipped (abstract advice, not concrete pairs)
 
@@ -294,7 +300,7 @@ Source: `https://digital.gov/guides/plain-language/principles/avoid-jargon`
 A composable preset that duplicates a flagship's own findings on the same
 span is noise, not value — measured directly with `lintContent` over this
 preset's own violations fixture, stacked onto each flagship in turn (see
-`preset-composition.test.ts`'s "duplicate findings" describe block for the
+`presets.test.ts`'s "duplicate findings" describe block for the
 live, asserted counts).
 
 Stacking `recheck/plain-language` onto `recheck/google` originally produced
@@ -302,10 +308,10 @@ Stacking `recheck/plain-language` onto `recheck/google` originally produced
 onto `recheck/microsoft`, **5**. Two pairs accounted for 3 of those on each
 side and are REMOVED as a result:
 
-| Removed pair | Was in | Already shipped, identically, by |
-|---|---|---|
-| `in order to` → `to` | `plain-language/filler-phrases` | `google/in-order-to` AND `microsoft/simple-words` |
-| `utilize`/`utilization` → `use` | `plain-language/complex-words` | `google/utilize` AND `microsoft/simple-words` |
+| Removed pair                    | Was in                          | Already shipped, identically, by                  |
+| ------------------------------- | ------------------------------- | ------------------------------------------------- |
+| `in order to` → `to`            | `plain-language/filler-phrases` | `google/in-order-to` AND `microsoft/simple-words` |
+| `utilize`/`utilization` → `use` | `plain-language/complex-words`  | `google/utilize` AND `microsoft/simple-words`     |
 
 Both are removed outright, not merely documented as an accepted overlap:
 they add zero coverage for anyone already running either flagship, and a
@@ -322,7 +328,7 @@ microsoft+plain-language: 3 of 35). These are KEPT, not removed, because
 they are not content-equivalence — each is either:
 
 1. **The accepted paragraph-length overlap** — `plain-language/paragraph-
-   max-words` and `plain-language/paragraph-sentence-count` always co-fire
+max-words` and `plain-language/paragraph-sentence-count` always co-fire
    on the same long paragraph (that's two independently-sourced numbers,
    words vs. sentences, both real); against `recheck/microsoft`
    specifically, `microsoft/paragraph-length` (a DIFFERENT number, 7
@@ -344,21 +350,21 @@ they are not content-equivalence — each is either:
 
 ## Fetch log (2026-07-30, `curl -sL`)
 
-| URL | Result |
-|---|---|
-| `https://www.plainlanguage.gov/` | 301 → `https://digital.gov/guides/plain-language` |
-| `https://www.plainlanguage.gov/guidelines/words/simple-words-phrases/` | 301 → same target |
-| `https://www.plainlanguage.gov/guidelines/sentences/` | 301 → same target |
-| `https://www.plainlanguage.gov/guidelines/paragraphs/` | 301 → same target |
-| `https://www.plainlanguage.gov/media/FederalPlainLanguageGuidelines.pdf` | 301 → same target |
-| `https://digital.gov/guides/plain-language` | 200 |
-| `https://digital.gov/guides/plain-language/principles` (+ 4 subpages) | 200 |
-| `https://digital.gov/guides/plain-language/writing` (+ 4 subpages) | 200 |
-| `https://digital.gov/guides/writing-understanding/familiar-terms` | 200 |
-| `https://digital.gov/guides/plain-language/design` (+ 5 subpages) | 200 |
-| `https://digital.gov/guides/plain-language/test` (+ 3 subpages) | 200 |
-| `https://digital.gov/resources/plain-writing-act` | 200 |
-| `https://www.whitehouse.gov/wp-content/uploads/legacy_drupal_files/omb/memoranda/2011/m11-15.pdf` (OMB Memo M-11-15) | 200, read natively as PDF |
+| URL                                                                                                                  | Result                                            |
+| -------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
+| `https://www.plainlanguage.gov/`                                                                                     | 301 → `https://digital.gov/guides/plain-language` |
+| `https://www.plainlanguage.gov/guidelines/words/simple-words-phrases/`                                               | 301 → same target                                 |
+| `https://www.plainlanguage.gov/guidelines/sentences/`                                                                | 301 → same target                                 |
+| `https://www.plainlanguage.gov/guidelines/paragraphs/`                                                               | 301 → same target                                 |
+| `https://www.plainlanguage.gov/media/FederalPlainLanguageGuidelines.pdf`                                             | 301 → same target                                 |
+| `https://digital.gov/guides/plain-language`                                                                          | 200                                               |
+| `https://digital.gov/guides/plain-language/principles` (+ 4 subpages)                                                | 200                                               |
+| `https://digital.gov/guides/plain-language/writing` (+ 4 subpages)                                                   | 200                                               |
+| `https://digital.gov/guides/writing-understanding/familiar-terms`                                                    | 200                                               |
+| `https://digital.gov/guides/plain-language/design` (+ 5 subpages)                                                    | 200                                               |
+| `https://digital.gov/guides/plain-language/test` (+ 3 subpages)                                                      | 200                                               |
+| `https://digital.gov/resources/plain-writing-act`                                                                    | 200                                               |
+| `https://www.whitehouse.gov/wp-content/uploads/legacy_drupal_files/omb/memoranda/2011/m11-15.pdf` (OMB Memo M-11-15) | 200, read natively as PDF                         |
 
 **Not fetched, and not used as a source**: the PlainLanguage.gov GitHub
 archive repository — off-domain, out of scope per the `.gov`-only rule.

package/presets/technical-english/PROVENANCE.md

@@ -17,11 +17,11 @@ The full reply is preserved on issue #25886.
 
 ## What ships
 
-| Rule | Principle | Default |
-| --- | --- | --- |
-| `technical-english/sentence-length` | Short sentences: at most 20 words in procedures, 25 in descriptive text | `warn`, max 25 (a linter cannot tell procedure from description; tighten to 20 for procedure-only content) |
-| `technical-english/paragraph-length` | At most 6 sentences per paragraph | `warn` |
-| `technical-english/passive-voice` | Use the active voice | `info` (heuristic: be-verb + participle; the irregular-participle list is ordinary linguistic knowledge) |
+| Rule                                 | Principle                                                               | Default                                                                                                    |
+| ------------------------------------ | ----------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
+| `technical-english/sentence-length`  | Short sentences: at most 20 words in procedures, 25 in descriptive text | `warn`, max 25 (a linter cannot tell procedure from description; tighten to 20 for procedure-only content) |
+| `technical-english/paragraph-length` | At most 6 sentences per paragraph                                       | `warn`                                                                                                     |
+| `technical-english/passive-voice`    | Use the active voice                                                    | `info` (heuristic: be-verb + participle; the irregular-participle list is ordinary linguistic knowledge)   |
 
 The numeric thresholds are factual claims about what the standard recommends, widely documented in public secondary material and ASD's own public pages.
 Facts are not copyrightable expression; the rule messages state them in this project's own words.

package/skills/recheck-config/SKILL.md

@@ -1,15 +1,52 @@
 ---
 name: recheck-config
-description: Use when you create or tune a recheck.yaml for a project — choose presets, set severities from measured counts, add exceptions, adopt a baseline, and validate the result.
+description: Use when you create or tune the recheck block and recheck/* presets in redocly.yaml for a project — choose presets, set severities from measured counts, add exceptions, adopt a baseline, and validate the result.
 ---
 
-# Write and tune recheck.yaml
+# Configure recheck in redocly.yaml
+
+Configure `redocly recheck` for a project the way its maintainers would: measure first, decide per rule, and record intent.
+The documentation is at [redocly.com/docs/cli/recheck](https://redocly.com/docs/cli/recheck); favor it over memory for rule names and options.
+
+## How the configuration is shaped
+
+Presets go in the root `extends`.
+Adjustments go in the `recheck` block, with rules nested under `rules`.
+The `lint` command ignores both, so they live next to the API ruleset:
+
+```yaml
+extends:
+  - recommended
+  - recheck/markdown
+  - recheck/prose
+recheck:
+  excludes:
+    - CHANGELOG.md
+  rules:
+    recheck/line-length: off
+    recheck/no-duplicate-heading:
+      severity: warn
+      assertions:
+        no-duplicate-heading:
+          siblingsOnly: true
+```
+
+Rules of the shape:
 
-Configure recheck for a project the way its maintainers would: measure first, decide per rule, and record intent.
+- A rule key is `<namespace>/<name>`: `recheck/line-length`, `google/no-via`, or your own, such as `acme/product-names`.
+- A severity string (`off`, `info`, `warn`, `error`) adjusts a rule that a preset defines.
+  For a key no preset defines, it is a configuration error, because the rule has no assertions.
+- A rule object merges over the preset's rule, but its `assertions` merge by assertion id: one option you set on a `swap` or `pattern` assertion replaces the preset's whole word list.
+  To reject one term from a preset's list, turn the rule off, restate the full list, or use an inline directive.
+- A new prose rule needs `severity`, `message`, and `assertions`.
+  A new Markdown rule, such as `recheck/list-length`, needs only `severity` and `assertions`.
+- The block does not accept `extends` or `baseline`; both are configuration errors.
+- The command reads the root block only.
+  A `recheck` block under `apis.<name>` does nothing and prints a warning.
 
 ## Start a new config
 
-1. Begin with the structural preset and validate:
+1. Begin with the structural preset, and run recheck to validate it:
 
    ```yaml
    extends:
@@ -17,50 +54,63 @@ Configure recheck for a project the way its maintainers would: measure first, de
    ```
 
    ```bash
-   npx recheck --validate-config
+   npx @redocly/cli recheck docs
+   npx @redocly/cli check-config
    ```
 
-2. Add prose rules deliberately, not wholesale.
-   `recheck/prose` is a small starter; `recheck/google` and `recheck/microsoft` are large style guides that need tuning before they help.
+   The `recheck` command reports configuration errors before it lints anything, and `check-config` validates the block's shape.
+
+2. Add prose presets deliberately, not wholesale.
+   `recheck/prose` is a small starter at `warn`.
+   `recheck/google` and `recheck/microsoft` are large style guides, detection-only, that need tuning before they help.
+   `recheck/plain-language`, `recheck/inclusive-language`, and `recheck/technical-english` compose onto either.
+
+3. If the project writes Markdoc tags, add `recheck/markdoc` to `extends` and `markdoc: true` to the block.
+   Without the flag, the Markdoc rules never report.
 
 ## Tune severities from measurements, not taste
 
-1. Run the whole corpus and count findings per rule:
+1. Run the whole document set and count findings per rule:
 
    ```bash
-   npx recheck docs --output json --annotations-limit 5000 --output-path findings.json
+   npx @redocly/cli recheck docs --summary=json --summary-path=recheck-summary.json
    ```
 
-   Group the findings by `ruleName` and look at real examples of each before deciding anything.
+   The summary's `breakdown` has the count per rule and severity.
+   For examples of each rule's findings, run `--rule=<name>` and read a few.
 
 2. Decide per rule from the counts:
-   - `error` — enforce now; the corpus is clean or you fix it in the same change.
+   - `error` — enforce now; the document set is clean or you fix it in the same change.
    - `warn` — a worklist; visible, not blocking.
-   - `off` — decided against; keep a comment that says why, or the decision is lost.
+   - `off` — decided against; keep a YAML comment that says why, or the decision is lost.
 
 3. Prefer fixing content over configuring around it.
    Run `--fix` first; most structural findings repair themselves.
+   Review the fix list before you commit: fixes that re-indent lines can move content out of an indented Markdoc tag body.
 
 ## Exceptions, in order of preference
 
 1. Fix the content.
-2. `exceptions.files` for generated or frozen content (archives, vendored docs) — with a comment naming the reason.
+2. The top-level `excludes` list, or a rule's `excludes` or `appliesTo`, for generated or frozen content such as archives and vendored docs — with a comment naming the reason.
 3. `exceptions.lines` for a recurring true positive that must stay as written.
 4. An inline `<!-- recheck-disable-next-line rule-name -->` for a single line.
 
-## Adopt strictness on a large corpus with a baseline
+## Adopt strictness on a large document set with a baseline
 
-When the corpus has too many errors to fix at once, record them and gate only new ones:
+When the document set has too many errors to fix at once, record them and gate only new ones:
 
 ```bash
-npx recheck --generate-baseline
+npx @redocly/cli recheck docs --generate-baseline
 ```
 
-Commit `recheck-baseline.yaml` and add `baseline: recheck-baseline.yaml` to the config.
-Counts only step down: when findings get fixed, regenerate the baseline and commit the diff.
+Commit `.redocly.recheck-baseline.yaml`.
+The command writes it next to `redocly.yaml`, and later runs pick it up by presence; there is no configuration key.
+It records errors only, as one count per file per rule.
+
+Counts only step down: when findings get fixed, the run reports stale entries, so regenerate the baseline and commit the diff.
 
 ## Finish
 
-- `npx recheck --validate-config` must pass.
+- `npx @redocly/cli recheck docs` and `npx @redocly/cli check-config` report no configuration errors.
 - Every `off` and every exception carries a comment with its reason.
-- The config's README section or the project docs say how contributors run recheck locally.
+- The project's contributing docs say how contributors run recheck locally, and CI runs it with `--format=github-actions`.

package/skills/recheck-lint/SKILL.md

@@ -1,36 +1,55 @@
 ---
 name: recheck-lint
-description: Use when you write or edit markdown in a project that has a recheck.yaml — run recheck on the touched files before you commit them or hand them over, and fix what it finds.
+description: Use when you write or edit Markdown in a project whose redocly.yaml has a recheck block or a recheck/* preset in extends — run redocly recheck on the touched files before you commit them or hand them over, and fix what it finds.
 ---
 
-# Lint markdown with recheck before you commit it
+# Lint Markdown with recheck before you commit it
 
-This project lints markdown and prose with recheck.
-Your markdown must pass it, the same as code must pass its tests.
+This project lints Markdown structure and prose with `redocly recheck`.
+Your Markdown must pass it, the same as code must pass its tests.
 
 ## When this applies
 
-A `recheck.yaml` (or `recheck.yml`) exists in the project root or above the files you touched.
-If none exists, this skill does not apply.
+Look for a `redocly.yaml` in the project root or above the files you touched.
+This skill applies when that file has a `recheck` block, or a `recheck/*` preset in its root `extends`, for example:
+
+```yaml
+extends:
+  - recommended
+  - recheck/markdown
+recheck:
+  rules:
+    recheck/line-length: off
+```
+
+If neither exists, skip this skill.
+The command checks nothing in that case and says so.
 
 ## What to do
 
-1. After you write or edit markdown files, run recheck on them:
+1. After you write or edit Markdown files, run recheck on them:
 
    ```bash
-   npx recheck <file-or-directory>
+   npx @redocly/cli recheck <file-or-directory>
    ```
 
+   Pass the files you touched, not the whole repository, so the report is yours to act on.
+
 2. If it reports errors, run the auto-fix first — most structural findings repair themselves:
 
    ```bash
-   npx recheck <file-or-directory> --fix
+   npx @redocly/cli recheck <file-or-directory> --fix
    ```
 
+   The command lists every edit it made.
+   Read the list: a fix inside a Markdoc tag body or a code sample deserves a look.
+
 3. Fix the remaining errors by hand.
    Read each message; the rule name links the finding to its intent.
+   To see one rule at a time, add `--rule=<name>` with the name the report prints.
 
 4. Re-run until it reports no errors, and only then commit or output the content.
+   The command exits with code 1 while errors remain.
 
 ## Rules of conduct
 
@@ -41,9 +60,14 @@ If none exists, this skill does not apply.
   <!-- recheck-disable-next-line recheck/rule-name -->
   ```
 
-  Never disable a rule project-wide to make your change pass, and never edit `recheck.yaml` to get past a finding.
-- Warnings do not block you.
+  Name the rule by its full key or by the short name the report prints.
+  Never disable a rule project-wide to make your change pass, and never edit the `recheck` block to get past a finding.
+
+- Warnings and info findings do not block you.
   Leave them unless the task asks for cleanup.
-- If the project has a baseline file (a `baseline:` key in `recheck.yaml`), old findings are budgeted; only new findings are yours to fix.
-  Do not regenerate the baseline to absorb findings your change introduced.
+- If a `.redocly.recheck-baseline.yaml` file sits next to `redocly.yaml`, the baseline already covers old findings; only new findings are yours to fix.
+  Do not run `--generate-baseline` to absorb findings your change introduced.
+  If your change removed old findings, the run reports stale baseline entries; regenerate the baseline then, and commit the smaller file with your change.
 - A finding you believe is a false positive is worth reporting to the maintainer, not silently suppressing.
+- Do not add `markdownlint` or `vale` comments.
+  Recheck does not read them.

package/dist/cli.d.ts

@@ -1,3 +0,0 @@
-#!/usr/bin/env node
-export {};
-//# sourceMappingURL=cli.d.ts.map

package/dist/cli.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"cli.d.ts","sourceRoot":"","sources":["../src/cli.ts"],"names":[],"mappings":""}