renma 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Kazuaki Matsuo
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,350 @@
+# Renma - 練磨
+
+Renma helps teams keep LLM-ready context assets and skills healthy in Git.
+
+Renma is a Git-native governance and quality layer for shared context repositories. It prepares repositories so Codex, Claude, Cursor, and future agents can consume team-owned expertise correctly. Renma does not choose task context, assemble prompts, inject context, or execute agent workflows; agents and runtimes decide how to use the assets for a task.
+
+```text
+Skill = LLM-facing entrypoint / routing contract / usage guide
+Context = independently owned source-of-truth knowledge asset
+```
+
+## Why Renma?
+
+As AI-agent repositories grow, expertise often gets copied into many skills. Testing heuristics, domain risks, tool usage notes, and team-specific contracts drift apart. Ownership becomes unclear, references break, deprecated guidance remains reachable, and new engineers or agents cannot tell which knowledge is authoritative.
+
+Renma treats context as a software asset:
+
+- Reusable
+- Owned
+- Reviewable
+- Versioned
+- Composable
+- Validated
+- Easy to inspect in CI and code review
+
+The first strong product focus is QA/testing: boundary value analysis, negative testing, regression risk, payment idempotency, duplicate charge prevention, refund edge cases, mobile offline behavior, mobile automation usage, internal test strategy, and known team-specific risks can live as shared context assets instead of being buried inside individual skills.
+
+## Repository Shape
+
+Renma supports skill-local references, profiles, and examples, but the target repository model gives shared context assets first-class space:
+
+```text
+skills/
+  testing/
+    test-case-generation.skill.md
+    spec-review.skill.md
+    regression-planning.skill.md
+contexts/
+  testing/
+    boundary-value-analysis.md
+    negative-testing.md
+    regression-risk.md
+  domain/
+    payment/
+      idempotency.md
+      duplicate-charge.md
+      refund-risk.md
+    mobile/
+      offline-behavior.md
+      background-resume.md
+  tools/
+    mobile/
+      device-setup.md
+      helper-guidelines.md
+  teams/
+    checkout/
+      payment-api-contracts.md
+      known-risk-patterns.md
+```
+
+`contexts/` is preferred. `context/` is also scanned for compatibility. Files under either root are cataloged as first-class `context` assets, while skill-local `references/` remain `reference` assets.
+
+## What Renma Does
+
+Today Renma is a minimal-dependency TypeScript CLI that scans AI-agent skills, repository instructions, shared context Markdown, profile overlays, references, and examples. It runs deterministic quality, structure, and safety rules, then emits text or JSON reports with file and line evidence. It also emits deterministic catalog, ownership coverage, graph, and agent readiness reports from the same local catalog model.
+
+Renma findings are intended to be actionable repair prompts for humans and LLM
+tools such as Codex, Claude, and Cursor. Findings should explain what is wrong,
+why it matters, where the evidence is, what a safe repair should preserve, and
+how to verify the fix. Renma does not apply large semantic rewrites itself; it
+emits structured diagnostics so a human or agent can propose a reviewable patch
+and run Renma again.
+
+Completed baseline:
+
+- Bounded filesystem discovery
+- Stable POSIX-style repo-relative paths
+- Markdown parsing for headings, links, code fences, metadata, and evidence
+- Structural quality checks for skills, shared context assets, and local support files
+- Safety checks for risky instructions and literal secrets
+- Deterministic catalog output for assets and dependency metadata
+- Deterministic ownership coverage reporting for cataloged assets
+- Context graph snapshot reporting
+- Deterministic agent readiness scoring for static repository health
+- Deterministic metadata governance for duplicate asset IDs, unknown declared references, references to deprecated or archived assets, and orphaned shared context assets
+- Repository file outline and line-slice inspection helper
+- Semantic split prompt helper for oversized context files
+- CI-friendly exit behavior with `--fail-on`
+- Config loading from `renma.config.json` and `.renma.json`
+
+Near-term direction:
+
+- Agent readiness report
+- Repeated context and duplicate knowledge discovery
+- Semantic diff for context changes
+- Optional LLM-assisted repository evaluation bundles
+- Optional external signal import
+
+See [architecture.md](./architecture.md) and [plan.md](./plan.md) for the current design direction.
+
+## Requirements
+
+- Node.js 22.17 or newer
+- npm
+
+Install:
+
+```bash
+npm install
+npm run build
+```
+
+After building, run the CLI directly:
+
+```bash
+node dist/index.js scan .
+```
+
+When installed as a package, the binary name is:
+
+```bash
+renma scan .
+```
+
+## Usage
+
+```bash
+renma scan [path] [options]
+renma catalog [path] [options]
+renma graph [path] [options]
+renma ownership [path] [options]
+renma readiness [path] [options]
+renma inspect <file> [options]
+renma suggest-semantic-split <file> [options]
+```
+
+Readiness output also includes a compact workflow readiness summary that groups workflow-level checks, counts pass/warn/fail states, and reports a deterministic workflow readiness percentage.
+
+`renma readiness` emits a static, deterministic agent-readiness report with a score, level, summary metrics, checks, and diagnostics. It exits 0 only when the level is `ready`; `needs_attention` and `not_ready` exit 1 for CI use. It does not call LLMs, choose runtime context, assemble prompts, or repair files.
+
+### Agent readiness v1
+
+Agent readiness v1 is a deterministic static report for checking whether skill workflow entrypoints are safe and understandable enough for human or agent consumption. It does not decide runtime context selection, assemble prompts, call an LLM, or repair files.
+
+The v1 workflow checks cover:
+
+- required context closure
+- optional context health
+- routing and usage clarity
+- required inputs / prerequisites
+- completion criteria / definition of done
+
+The report also includes a workflow readiness summary that counts workflow pass/warn/fail states and reports a deterministic workflow readiness percentage.
+
+A ready report is intentionally compact enough to paste into a PR description, for example: level, score, workflow readiness, graph resolution, ownership coverage, diagnostics, and layout status.
+
+Dogfooding against the `appium/skills` branch `refine2` produced a ready v1 report with all workflow checks passing, all graph edges resolved, all assets owned, no diagnostics, and passing layout checks. The example confirmed that the Markdown recap is useful for PR reviews without changing Renma's deterministic static boundaries.
+
+The JSON and Markdown reports expose `summary.workflow` counts, graph resolution, ownership coverage, diagnostics, and layout status. They do not perform runtime context selection, assemble prompt packages, call an LLM, auto-repair files, score repairability, or plan per-skill patches.
+
+Workflow context closure checks that each skill entrypoint's declared required context references resolve to usable, non-deprecated, non-archived assets.
+
+Workflow optional-context checks warn when declared optional context references are unresolved, deprecated, or archived, without deciding whether optional context should be loaded at runtime.
+
+Workflow clarity warns when skill entrypoints lack deterministic routing, preflight, examples, verification, or other static guidance needed for responsible agent use.
+
+Workflow required-input checks warn when skill entrypoints do not document the inputs, prerequisites, or permissions agents need before starting.
+
+Workflow completion-criteria checks warn when skill entrypoints do not state the final output, evidence, report contents, patch expectations, or stop condition needed to complete the workflow.
+
+`renma inspect` is a repository inspection helper for outlines and exact line slices; it does not choose task context or assemble prompts.
+
+Options:
+
+```text
+-c, --config <path>      Read JSON config from path
+    --fail-on <level>    Exit 1 when findings meet severity: low, medium, high, critical
+    --format <format>    scan: text or json; catalog/ownership: json or markdown; graph: json, markdown, or mermaid; suggest: prompt or json
+    --include-owned      ownership: include owned asset details
+    --json               Shortcut for --format json
+    --view <view>        graph: summary, workflow, or full
+    --lines <range>      inspect: exact line range, e.g. L10-L42
+    --max-source-bytes <n>
+                          suggest-semantic-split: source file byte budget
+    --max-context-bytes <n>
+                          suggest-semantic-split: nearby context byte budget
+-h, --help               Show help
+-v, --version            Show version
+```
+
+Examples:
+
+```bash
+renma scan .
+renma scan ./my-repo --json
+renma scan . --fail-on medium
+renma scan . --config ./renma.config.json
+renma catalog . --format markdown
+renma catalog . --json
+renma graph . --format markdown
+renma graph . --format mermaid
+renma graph . --format mermaid --view workflow
+renma graph . --json
+renma ownership . --format markdown
+renma ownership . --json
+renma ownership . --json --include-owned
+renma readiness . --format markdown
+renma readiness . --json
+renma inspect contexts/testing/boundary-value-analysis.md --format json
+renma inspect contexts/testing/boundary-value-analysis.md --lines L40-L90 --format text
+renma suggest-semantic-split contexts/testing/boundary-value-analysis.md
+```
+
+## What Gets Scanned
+
+By default, Renma looks for:
+
+```text
+skills/**/SKILL.md
+.agents/**/*.md
+AGENTS.md
+README.md
+context/**/*.md
+contexts/**/*.md
+tools/**/*
+```
+
+It skips `node_modules`, `dist`, and `.git`, ignores symbolic links, enforces a maximum file size, and reports paths in stable POSIX-style form.
+
+## Configuration
+
+Renma automatically looks for `renma.config.json`, then `.renma.json`.
+
+Configuration is applied in this order:
+
+1. Defaults
+2. Config file
+3. CLI flags
+
+Example:
+
+```json
+{
+  "fail_on": "high",
+  "format": "json",
+  "globs": [
+    "skills/**/SKILL.md",
+    "AGENTS.md",
+    "contexts/**/*.md"
+  ],
+  "exclude": ["node_modules", "dist", ".git"],
+  "max_file_size_bytes": 524288,
+  "max_depth": 16,
+  "concurrency": 16,
+  "layout": {
+    "workflow_aliases": {}
+  }
+}
+```
+
+Supported fields:
+
+- `fail_on`: `low`, `medium`, `high`, or `critical`
+- `format`: `text` or `json`
+- `globs`: array of glob patterns
+- `exclude`: array of path segment names to skip
+- `max_file_size_bytes`: positive integer
+- `max_depth`: positive integer
+- `concurrency`: positive integer
+- `layout`: optional strict layout policy configuration
+  - `tool_namespace`: optional namespace for suggested `contexts/tools/<namespace>/...` and `tools/<namespace>/...` paths
+  - `workflow_aliases`: map of skill directory names to canonical workflow directory names
+
+Invalid config fields exit with code `2`.
+
+## Layout Policy
+
+Strict layout diagnostics are generic by default. Renma suggests context assets under `contexts/<workflow>/...` and helper assets under `tools/<workflow>/...` unless a repository config adds a tool namespace.
+
+- `layout.tool_namespace` is optional. When set, it controls the namespace used in suggested `contexts/tools/<namespace>/<workflow>/...` and `tools/<namespace>/<workflow>/...` paths. When omitted, Renma suggests `contexts/<workflow>/...` and `tools/<workflow>/...` paths.
+- `layout.workflow_aliases` maps skill directory names to canonical workflow directory names.
+
+Example:
+
+```json
+{
+  "layout": {
+    "tool_namespace": "mobile",
+    "workflow_aliases": {
+      "device-setup": "real-device"
+    }
+  }
+}
+```
+
+## Exit Codes
+
+- `0`: Scan completed and no findings met the failure threshold
+- `1`: Scan completed and at least one finding met `fail_on`
+- `2`: CLI usage error, invalid config, or unreadable required input
+
+## Checks
+
+Current rules include:
+
+- Missing skill description, examples, preflight, verification, negative routing, or explicit routing clarity
+- Short frontmatter descriptions
+- Oversized `SKILL.md` entrypoints
+- Metadata governance findings surfaced through `scan`, including invalid lifecycle status values, missing shared context `id` or `owner`, duplicate asset IDs, unknown declared references, declared references to deprecated or archived assets, and orphaned shared context assets
+- Oversized shared context assets or local support files in `contexts/`, `context/`, `profiles/`, `references/`, and `examples/`
+- Unreachable skill-local profiles, references, and examples
+- Profile overlays missing base skill declaration
+- Skills that still route through deprecated or superseded local support assets after reusable knowledge has moved to canonical shared context assets
+- Non-skill assets that still reference deprecated or superseded support files instead of canonical shared context assets
+- Advisory reusable-context candidates in `SKILL.md` files with enough size and diverse setup, troubleshooting, platform, testing, risk, or domain-rule signals
+- Advisory shared-context candidates in large `contexts/**/*.md` assets with generic source-of-truth headings and reusable guidance phrases
+- Advisory shared-context assets under process-state folders such as `contexts/promoted/`, `contexts/generated/`, or `contexts/drafts/` that should become semantic final paths
+- Literal secret-like values
+- Private key material
+- Destructive commands without nearby confirmation or recovery context
+- Risky remote defaults
+- Broad environment copying into subprocesses
+- Hardcoded user-local paths
+
+Declared reference validation resolves exact asset IDs and repository-relative paths, including paths with a leading `./` normalized away. It does not perform fuzzy matching, semantic lookup, runtime context selection, or prompt assembly.
+
+Static checks are evidence. Passing a scan does not prove a repository or agent workflow is safe.
+
+## Development
+
+```bash
+npm run build
+npm run typecheck
+npm test
+```
+
+The package build emits the CLI to `dist/index.js`. Tests compile to `dist-test/`.
+
+## Inspirations
+
+Renma is inspired by:
+
+- [Waza](https://github.com/microsoft/waza), especially skill eval coverage, task-based regression checks, and readiness-oriented validation.
+- [SkillSpector](https://github.com/NVIDIA/skillspector), especially deterministic security scanning, risk-oriented findings, SARIF/reporting direction, and analyzer-style rule organization.
+
+Renma is an independent implementation focused on lightweight deterministic governance checks for AI-agent skill and context repositories.
+
+## License
+
+MIT. See [LICENSE](./LICENSE).

package/dist/catalog.d.ts

@@ -0,0 +1,8 @@
+import type { Catalog } from "./model.js";
+import type { Diagnostic, ParsedDocument } from "./types.js";
+/** Build a deterministic catalog of skill and context entries from parsed documents. */
+export declare function buildCatalog(documents: ParsedDocument[]): {
+    catalog: Catalog;
+    diagnostics: Diagnostic[];
+};
+//# sourceMappingURL=catalog.d.ts.map

package/dist/catalog.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"catalog.d.ts","sourceRoot":"","sources":["../src/catalog.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAEV,OAAO,EAIR,MAAM,YAAY,CAAC;AAEpB,OAAO,KAAK,EAAE,UAAU,EAAY,cAAc,EAAE,MAAM,YAAY,CAAC;AAEvE,wFAAwF;AACxF,wBAAgB,YAAY,CAAC,SAAS,EAAE,cAAc,EAAE,GAAG;IACzD,OAAO,EAAE,OAAO,CAAC;IACjB,WAAW,EAAE,UAAU,EAAE,CAAC;CAC3B,CAkEA"}

package/dist/catalog.js

@@ -0,0 +1,140 @@
+import { createHash } from "node:crypto";
+import { parseAssetMetadata } from "./metadata.js";
+/** Build a deterministic catalog of skill and context entries from parsed documents. */
+export function buildCatalog(documents) {
+    const diagnostics = [];
+    const entries = documents
+        .map((document) => {
+        const result = parseAssetMetadata(document);
+        diagnostics.push(...result.diagnostics);
+        diagnostics.push(...sharedContextMetadataDiagnostics(document, result.metadata));
+        const base = {
+            id: result.metadata.id ?? document.artifact.path,
+            sourcePath: document.artifact.path,
+            contentHash: contentHash(document.artifact.content),
+            metadata: result.metadata,
+        };
+        if (document.artifact.kind === "skill") {
+            return {
+                ...base,
+                kind: "skill",
+                requiredContext: result.metadata.requiresContext,
+                optionalContext: result.metadata.optionalContext,
+                conflicts: result.metadata.conflicts,
+            };
+        }
+        if (document.artifact.kind === "context" ||
+            document.artifact.kind === "profile" ||
+            document.artifact.kind === "reference" ||
+            document.artifact.kind === "example") {
+            return {
+                ...base,
+                kind: document.artifact.kind,
+            };
+        }
+        return undefined;
+    })
+        .filter((entry) => entry !== undefined)
+        .sort((a, b) => {
+        const byKind = kindOrder(a.kind) - kindOrder(b.kind);
+        if (byKind !== 0)
+            return byKind;
+        return a.sourcePath.localeCompare(b.sourcePath);
+    });
+    const dependencies = entries
+        .flatMap((entry) => dependenciesForEntry(entry))
+        .sort((a, b) => {
+        const byFrom = a.from.localeCompare(b.from);
+        if (byFrom !== 0)
+            return byFrom;
+        const byKind = dependencyKindOrder(a.kind) - dependencyKindOrder(b.kind);
+        if (byKind !== 0)
+            return byKind;
+        return a.to.localeCompare(b.to);
+    });
+    return {
+        catalog: {
+            entries,
+            assets: entries,
+            dependencies,
+        },
+        diagnostics,
+    };
+}
+function contentHash(content) {
+    return `sha256:${createHash("sha256").update(content).digest("hex")}`;
+}
+function sharedContextMetadataDiagnostics(document, metadata) {
+    if (document.artifact.kind !== "context")
+        return [];
+    const diagnostics = [];
+    if (!metadata.id) {
+        diagnostics.push({
+            severity: "warning",
+            path: document.artifact.path,
+            message: "Shared context asset is missing an id.",
+        });
+    }
+    if (!metadata.owner) {
+        diagnostics.push({
+            severity: "warning",
+            path: document.artifact.path,
+            message: "Shared context asset is missing an owner.",
+        });
+    }
+    return diagnostics;
+}
+/** Convert metadata relationship lists into graph edges for a catalog entry. */
+function dependenciesForEntry(entry) {
+    return [
+        ...metadataDependencies(entry, "requires", entry.metadata.requiresContext),
+        ...metadataDependencies(entry, "optional", entry.metadata.optionalContext),
+        ...metadataDependencies(entry, "conflicts", entry.metadata.conflicts),
+        ...metadataDependencies(entry, "references", entry.metadata.supersededBy),
+    ];
+}
+function metadataDependencies(entry, kind, targets) {
+    return targets.map((target) => ({
+        from: entry.id,
+        to: target,
+        kind,
+        sourcePath: entry.sourcePath,
+        evidence: metadataEvidence(entry.sourcePath),
+    }));
+}
+/** Evidence points at frontmatter until metadata parsing preserves field line ranges. */
+function metadataEvidence(path) {
+    return {
+        path,
+        startLine: 1,
+        endLine: 1,
+        snippet: "frontmatter dependency metadata",
+    };
+}
+/** Keep catalog output stable across filesystems and Node versions. */
+function kindOrder(kind) {
+    if (kind === "skill")
+        return 0;
+    if (kind === "context")
+        return 1;
+    if (kind === "profile")
+        return 2;
+    if (kind === "reference")
+        return 3;
+    return 4;
+}
+/** Keep dependency output stable while grouping the most important edges first. */
+function dependencyKindOrder(kind) {
+    if (kind === "requires")
+        return 0;
+    if (kind === "optional")
+        return 1;
+    if (kind === "conflicts")
+        return 2;
+    if (kind === "extends")
+        return 3;
+    if (kind === "references")
+        return 4;
+    return 5;
+}
+//# sourceMappingURL=catalog.js.map

package/dist/catalog.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"catalog.js","sourceRoot":"","sources":["../src/catalog.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAE,MAAM,aAAa,CAAC;AAQzC,OAAO,EAAE,kBAAkB,EAAE,MAAM,eAAe,CAAC;AAGnD,wFAAwF;AACxF,MAAM,UAAU,YAAY,CAAC,SAA2B;IAItD,MAAM,WAAW,GAAiB,EAAE,CAAC;IACrC,MAAM,OAAO,GAAG,SAAS;SACtB,GAAG,CAAC,CAAC,QAAQ,EAA4B,EAAE;QAC1C,MAAM,MAAM,GAAG,kBAAkB,CAAC,QAAQ,CAAC,CAAC;QAC5C,WAAW,CAAC,IAAI,CAAC,GAAG,MAAM,CAAC,WAAW,CAAC,CAAC;QACxC,WAAW,CAAC,IAAI,CACd,GAAG,gCAAgC,CAAC,QAAQ,EAAE,MAAM,CAAC,QAAQ,CAAC,CAC/D,CAAC;QAEF,MAAM,IAAI,GAAG;YACX,EAAE,EAAE,MAAM,CAAC,QAAQ,CAAC,EAAE,IAAI,QAAQ,CAAC,QAAQ,CAAC,IAAI;YAChD,UAAU,EAAE,QAAQ,CAAC,QAAQ,CAAC,IAAI;YAClC,WAAW,EAAE,WAAW,CAAC,QAAQ,CAAC,QAAQ,CAAC,OAAO,CAAC;YACnD,QAAQ,EAAE,MAAM,CAAC,QAAQ;SAC1B,CAAC;QAEF,IAAI,QAAQ,CAAC,QAAQ,CAAC,IAAI,KAAK,OAAO,EAAE,CAAC;YACvC,OAAO;gBACL,GAAG,IAAI;gBACP,IAAI,EAAE,OAAO;gBACb,eAAe,EAAE,MAAM,CAAC,QAAQ,CAAC,eAAe;gBAChD,eAAe,EAAE,MAAM,CAAC,QAAQ,CAAC,eAAe;gBAChD,SAAS,EAAE,MAAM,CAAC,QAAQ,CAAC,SAAS;aACrC,CAAC;QACJ,CAAC;QAED,IACE,QAAQ,CAAC,QAAQ,CAAC,IAAI,KAAK,SAAS;YACpC,QAAQ,CAAC,QAAQ,CAAC,IAAI,KAAK,SAAS;YACpC,QAAQ,CAAC,QAAQ,CAAC,IAAI,KAAK,WAAW;YACtC,QAAQ,CAAC,QAAQ,CAAC,IAAI,KAAK,SAAS,EACpC,CAAC;YACD,OAAO;gBACL,GAAG,IAAI;gBACP,IAAI,EAAE,QAAQ,CAAC,QAAQ,CAAC,IAAI;aAC7B,CAAC;QACJ,CAAC;QAED,OAAO,SAAS,CAAC;IACnB,CAAC,CAAC;SACD,MAAM,CAAC,CAAC,KAAK,EAAyB,EAAE,CAAC,KAAK,KAAK,SAAS,CAAC;SAC7D,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE;QACb,MAAM,MAAM,GAAG,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC,GAAG,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC;QACrD,IAAI,MAAM,KAAK,CAAC;YAAE,OAAO,MAAM,CAAC;QAChC,OAAO,CAAC,CAAC,UAAU,CAAC,aAAa,CAAC,CAAC,CAAC,UAAU,CAAC,CAAC;IAClD,CAAC,CAAC,CAAC;IAEL,MAAM,YAAY,GAAG,OAAO;SACzB,OAAO,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,oBAAoB,CAAC,KAAK,CAAC,CAAC;SAC/C,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE;QACb,MAAM,MAAM,GAAG,CAAC,CAAC,IAAI,CAAC,aAAa,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC;QAC5C,IAAI,MAAM,KAAK,CAAC;YAAE,OAAO,MAAM,CAAC;QAChC,MAAM,MAAM,GAAG,mBAAmB,CAAC,CAAC,CAAC,IAAI,CAAC,GAAG,mBAAmB,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC;QACzE,IAAI,MAAM,KAAK,CAAC;YAAE,OAAO,MAAM,CAAC;QAChC,OAAO,CAAC,CAAC,EAAE,CAAC,aAAa,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC;IAClC,CAAC,CAAC,CAAC;IAEL,OAAO;QACL,OAAO,EAAE;YACP,OAAO;YACP,MAAM,EAAE,OAAO;YACf,YAAY;SACb;QACD,WAAW;KACZ,CAAC;AACJ,CAAC;AAED,SAAS,WAAW,CAAC,OAAe;IAClC,OAAO,UAAU,UAAU,CAAC,QAAQ,CAAC,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC,MAAM,CAAC,KAAK,CAAC,EAAE,CAAC;AACxE,CAAC;AAED,SAAS,gCAAgC,CACvC,QAAwB,EACxB,QAAuB;IAEvB,IAAI,QAAQ,CAAC,QAAQ,CAAC,IAAI,KAAK,SAAS;QAAE,OAAO,EAAE,CAAC;IAEpD,MAAM,WAAW,GAAiB,EAAE,CAAC;IACrC,IAAI,CAAC,QAAQ,CAAC,EAAE,EAAE,CAAC;QACjB,WAAW,CAAC,IAAI,CAAC;YACf,QAAQ,EAAE,SAAS;YACnB,IAAI,EAAE,QAAQ,CAAC,QAAQ,CAAC,IAAI;YAC5B,OAAO,EAAE,wCAAwC;SAClD,CAAC,CAAC;IACL,CAAC;IAED,IAAI,CAAC,QAAQ,CAAC,KAAK,EAAE,CAAC;QACpB,WAAW,CAAC,IAAI,CAAC;YACf,QAAQ,EAAE,SAAS;YACnB,IAAI,EAAE,QAAQ,CAAC,QAAQ,CAAC,IAAI;YAC5B,OAAO,EAAE,2CAA2C;SACrD,CAAC,CAAC;IACL,CAAC;IAED,OAAO,WAAW,CAAC;AACrB,CAAC;AAED,gFAAgF;AAChF,SAAS,oBAAoB,CAAC,KAAmB;IAC/C,OAAO;QACL,GAAG,oBAAoB,CAAC,KAAK,EAAE,UAAU,EAAE,KAAK,CAAC,QAAQ,CAAC,eAAe,CAAC;QAC1E,GAAG,oBAAoB,CAAC,KAAK,EAAE,UAAU,EAAE,KAAK,CAAC,QAAQ,CAAC,eAAe,CAAC;QAC1E,GAAG,oBAAoB,CAAC,KAAK,EAAE,WAAW,EAAE,KAAK,CAAC,QAAQ,CAAC,SAAS,CAAC;QACrE,GAAG,oBAAoB,CAAC,KAAK,EAAE,YAAY,EAAE,KAAK,CAAC,QAAQ,CAAC,YAAY,CAAC;KAC1E,CAAC;AACJ,CAAC;AAED,SAAS,oBAAoB,CAC3B,KAAmB,EACnB,IAAoB,EACpB,OAAiB;IAEjB,OAAO,OAAO,CAAC,GAAG,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,CAAC;QAC9B,IAAI,EAAE,KAAK,CAAC,EAAE;QACd,EAAE,EAAE,MAAM;QACV,IAAI;QACJ,UAAU,EAAE,KAAK,CAAC,UAAU;QAC5B,QAAQ,EAAE,gBAAgB,CAAC,KAAK,CAAC,UAAU,CAAC;KAC7C,CAAC,CAAC,CAAC;AACN,CAAC;AAED,yFAAyF;AACzF,SAAS,gBAAgB,CAAC,IAAY;IACpC,OAAO;QACL,IAAI;QACJ,SAAS,EAAE,CAAC;QACZ,OAAO,EAAE,CAAC;QACV,OAAO,EAAE,iCAAiC;KAC3C,CAAC;AACJ,CAAC;AAED,uEAAuE;AACvE,SAAS,SAAS,CAAC,IAA0B;IAC3C,IAAI,IAAI,KAAK,OAAO;QAAE,OAAO,CAAC,CAAC;IAC/B,IAAI,IAAI,KAAK,SAAS;QAAE,OAAO,CAAC,CAAC;IACjC,IAAI,IAAI,KAAK,SAAS;QAAE,OAAO,CAAC,CAAC;IACjC,IAAI,IAAI,KAAK,WAAW;QAAE,OAAO,CAAC,CAAC;IACnC,OAAO,CAAC,CAAC;AACX,CAAC;AAED,mFAAmF;AACnF,SAAS,mBAAmB,CAAC,IAAoB;IAC/C,IAAI,IAAI,KAAK,UAAU;QAAE,OAAO,CAAC,CAAC;IAClC,IAAI,IAAI,KAAK,UAAU;QAAE,OAAO,CAAC,CAAC;IAClC,IAAI,IAAI,KAAK,WAAW;QAAE,OAAO,CAAC,CAAC;IACnC,IAAI,IAAI,KAAK,SAAS;QAAE,OAAO,CAAC,CAAC;IACjC,IAAI,IAAI,KAAK,YAAY;QAAE,OAAO,CAAC,CAAC;IACpC,OAAO,CAAC,CAAC;AACX,CAAC"}

package/dist/cli.d.ts

@@ -0,0 +1,2 @@
+export declare function main(argv?: string[]): Promise<number>;
+//# sourceMappingURL=cli.d.ts.map

package/dist/cli.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"cli.d.ts","sourceRoot":"","sources":["../src/cli.ts"],"names":[],"mappings":"AA2BA,wBAAsB,IAAI,CAAC,IAAI,WAAwB,GAAG,OAAO,CAAC,MAAM,CAAC,CA6ExE"}