@vibe-agent-toolkit/cli 0.1.37 → 0.1.39-rc.1

package/docs/audit.md

@@ -555,6 +555,31 @@ Windows users: Use forward slashes even on Windows - they work correctly in Node
 
 SKILL.md files can use any line ending (LF, CRLF) - the parser handles both.
 
+## Requirements
+
+`vat audit` has an unusual policy because it operates on per-skill
+governing context rather than a single top-level `projectRoot`:
+
+- **`projectRoot`**: per-skill walk-up. There is no single `projectRoot` for an
+  audit run. Each `SKILL.md` discovered during scanning walks up to its own
+  nearest `vibe-agent-toolkit.config.yaml`-or-`.git/` ancestor and uses that as
+  *its* `projectRoot`. Skills with no governing config or git ancestor are
+  reported as ungoverned (an audit finding, not a fatal error). This lets `vat
+  audit` work on external community trees, downloaded plugin bundles, and
+  monorepos with multiple sub-package configs.
+- **Config**: accept defaults. Per-skill `validation.severity` and
+  `validation.allow` overrides come from whichever
+  `vibe-agent-toolkit.config.yaml` each skill walks up to. The audit itself
+  always exits 0 (advisory) regardless of severity outcomes.
+
+The per-skill walk-up is cached via a module-level two-layer cache and pre-warmed
+during top-down descent for efficiency on large trees.
+
+See [Roots and Config — Canonical Concepts](../../../docs/concepts/roots-and-config.md)
+for the `projectRoot` ladder and the audit walk-up model. See
+[`docs/skill-quality-and-compatibility.md`](../../../docs/skill-quality-and-compatibility.md)
+for VAT's advisory-audit stance.
+
 ## Related Commands
 
 - `vat agent audit <path>` - Legacy skill-only audit (deprecated)

package/docs/doctor.md

@@ -260,6 +260,19 @@ fi
 - **Skipped:** When running installed VAT globally
 - **Fix:** Run `bun run build` in VAT source directory
 
+## Requirements
+
+- **`projectRoot`**: optional. `vat doctor` tolerates a missing `projectRoot`
+  and reports its absence as a diagnostic finding rather than refusing to run.
+  This is by design: doctor is the command users invoke when they suspect their
+  setup is wrong, so it must run anywhere.
+- **Config**: not used as input. Doctor checks whether a config file *exists*
+  and parses as a finding, but it does not consume config fields to drive its
+  behavior.
+
+See [Roots and Config — Canonical Concepts](../../../docs/concepts/roots-and-config.md)
+for terminology.
+
 ## Tips
 
 - Run `vat doctor` before reporting issues to verify environment

package/docs/index.md

@@ -332,6 +332,25 @@ The `vat` wrapper automatically detects your execution context:
 When running global `vat` from within the toolkit repository, it automatically
 switches to dev mode and shows the `-dev` suffix.
 
+## Requirements
+
+Every VAT command declares a `projectRoot` policy and a config policy. The
+short version:
+
+- **`projectRoot` = the VAT authoring boundary.** Discovered as: nearest
+  `vibe-agent-toolkit.config.yaml` → else nearest `.git/` → else `null`.
+- **Per-command policy varies.** Some commands require it (`vat skills build`,
+  `vat agent build`, `vat build`, `vat verify`). Some tolerate its absence
+  (`vat skills validate --user`, `vat agent list`, `vat rag *` with `--db`).
+  Some have a **loud-cwd fallback** that warns to stderr and continues
+  (`vat resources scan`, `vat resources validate`).
+- **`vat audit` is special:** there is no single `projectRoot`; each scanned
+  skill walks up to its own governing context.
+
+Every command's `--help` output includes a `Requirements:` section declaring
+its policy. The full matrix and rationale live in
+[Roots and Config — Canonical Concepts](../../../docs/concepts/roots-and-config.md).
+
 ## Configuration
 
 Place `vibe-agent-toolkit.config.yaml` at project root:

package/docs/mcp.md

@@ -310,6 +310,22 @@ All implementations must:
 
 See [MCP Gateway README](../../gateway-mcp/README.md) for planned features.
 
+## Requirements
+
+Both MCP subcommands run as server / discovery operations and do not consume a
+VAT authoring context:
+
+- **`vat mcp list-collections`**
+  - **`projectRoot`**: N/A.
+  - **Config**: not used.
+- **`vat mcp serve <package>`**
+  - **`projectRoot`**: N/A. The server resolves `<package>` from `node_modules`
+    or an explicit path; project context is not needed.
+  - **Config**: not used.
+
+See [Roots and Config — Canonical Concepts](../../../docs/concepts/roots-and-config.md)
+for terminology.
+
 ## See Also
 
 - [MCP Gateway README](../../gateway-mcp/README.md)

package/docs/rag.md

@@ -441,6 +441,24 @@ vat rag index docs/
 2. Query too broad/vague → Be more specific
 3. Chunk boundaries split relevant content → Adjust chunk size (future feature)
 
+## Requirements
+
+| Subcommand | `projectRoot` | Config |
+|---|---|---|
+| `vat rag index [path]` | optional (tolerates absence — `--db` supplies the path directly) | required fields (`rag.*`) when `--db` is not supplied; otherwise unused |
+| `vat rag query <text>` | optional (`--db` overrides) | required file with `rag.*` for default db lookup |
+| `vat rag stats` | optional (`--db` overrides) | required file with `rag.*` for default db lookup |
+| `vat rag clear` | optional (`--db` overrides) | required file with `rag.*` for default db lookup |
+
+RAG commands are unusual: they tolerate a missing `projectRoot` because the
+caller can always specify `--db <path>` explicitly. But when `--db` is omitted,
+VAT needs `rag.*` config fields to locate the configured store. The two
+mechanisms are complementary — `--db` is for one-off use, `rag.*` config is for
+project-default behavior.
+
+See [Roots and Config — Canonical Concepts](../../../docs/concepts/roots-and-config.md)
+for terminology.
+
 ## More Information
 
 - **GitHub:** https://github.com/jdutton/vibe-agent-toolkit

package/docs/resources.md

@@ -53,6 +53,20 @@ vat resources scan docs/
 # ---
 ```
 
+**Requirements:**
+
+- **`projectRoot`**: optional with **loud-cwd fallback**. When invoked with an
+  explicit `[path]`, that path is the effective base. Without a path, VAT walks
+  up from `cwd` for `vibe-agent-toolkit.config.yaml` then `.git/`; if neither is
+  found, the command falls back to `cwd` and emits a single stderr warning
+  identifying the fallback. The scan still completes — the warning is the
+  contract that prevents silent surprise.
+- **Config**: optional. Uses built-in include/exclude defaults if no config file
+  is present.
+
+See [Roots and Config — Canonical Concepts](../../../docs/concepts/roots-and-config.md)
+for the loud-cwd fallback policy and the projectRoot discovery ladder.
+
 ### vat resources validate [path]
 
 **Purpose:** Validate markdown resources with strict error reporting
@@ -121,6 +135,30 @@ vat resources validate docs/
 # ---
 ```
 
+**Requirements:**
+
+- **`projectRoot`**: optional with **loud-cwd fallback**. With an explicit
+  `[path]` the path is used as the base directory; without it VAT walks for a
+  `vibe-agent-toolkit.config.yaml` then `.git/` ancestor, and falls back to
+  `cwd` with a stderr warning if neither is found.
+- **Config**: optional. Defaults are applied when no config file is present;
+  `--frontmatter-schema` is independent of config.
+
+**Leading-`/` URI-reference resolution.** Markdown body links and frontmatter
+URI-references whose path component starts with `/` (e.g.
+`[See](/docs/foo.md)`, `parent_spec: /docs/foo.md`) are RFC 3986 §4.2
+absolute-path references and are resolved against the discovered `projectRoot`.
+Once cwd-fallback has fired, the effective `projectRoot` is `cwd` and leading-`/`
+links resolve against `cwd` — consistent with the loud-cwd contract. The
+`absolute_no_root` failure mode fires only when `projectRoot` is genuinely
+undefined (e.g. a programmatic embedder that did not supply one); leading-`/`
+links that escape `projectRoot` via path traversal surface as
+`absolute_escapes_root`. Both surface as `broken_file` issues.
+
+See [Roots and Config — Canonical Concepts](../../../docs/concepts/roots-and-config.md)
+for the projectRoot ladder, the loud-cwd fallback policy, and the rationale
+behind RFC-3986-compliant leading-`/` resolution.
+
 ## Configuration
 
 Place `vibe-agent-toolkit.config.yaml` at project root:
@@ -134,10 +172,14 @@ resources:
   exclude:
     - "node_modules/**"
     - "**/test/fixtures/**"
+  # Optional: per-code severity overrides (keys are validation codes,
+  # values are error | warning | info | ignore). External-URL findings
+  # default to `warning` (non-fatal), so a dead external link won't fail
+  # the build unless you raise its severity here.
   validation:
-    checkLinks: true
-    checkAnchors: true
-    allowExternal: true
+    severity:
+      EXTERNAL_URL_DEAD: ignore        # don't fail the build on dead external links
+      FRONTMATTER_SCHEMA_ERROR: error
 ```
 
 ## Integration with vibe-validate

package/docs/skills.md

@@ -128,6 +128,19 @@ vat skills validate --user
 vat skills validate packages/my-agent/resources/skills
 ```
 
+**Requirements:**
+
+- **`projectRoot`**: required. `vat skills validate` refuses to run if no
+  `vibe-agent-toolkit.config.yaml` or `.git/` ancestor is found. Source-mode
+  validation always runs against a real authoring boundary.
+- **Config**: optional. Falls back to built-in defaults if no config file is
+  present, but a `projectRoot` is still required to anchor link resolution and
+  the gitignore-safety gate.
+
+See [Roots and Config — Canonical Concepts](../../../docs/concepts/roots-and-config.md)
+for the discovery ladder, the loud-cwd fallback policy, and the CLI-boundary
+discovery rule that this command participates in.
+
 ---
 
 ### vat skills build
@@ -203,6 +216,18 @@ vat skills build --skill my-skill
 vat skills build --dry-run
 ```
 
+**Requirements:**
+
+- **`projectRoot`**: required. `vat skills build` refuses to run if no
+  `vibe-agent-toolkit.config.yaml` or `.git/` ancestor is found. This guards
+  against accidental builds outside a VAT project.
+- **Config**: required file with `skills.*` fields populated. The build
+  pipeline reads `skills.discovery` and `skills.config.*` directly — there are
+  no useful defaults for these.
+
+See [Roots and Config — Canonical Concepts](../../../docs/concepts/roots-and-config.md)
+for terminology.
+
 ---
 
 ### vat skills package <skill-path>
@@ -270,6 +295,18 @@ vat skills package SKILL.md -o dist --no-rewrite-links
 vat skills package SKILL.md -o dist -b /custom/base
 ```
 
+**Requirements:**
+
+- **`projectRoot`**: required. Packaging is an explicit-adoption operation and
+  is refused outside a discovered VAT project (no `vibe-agent-toolkit.config.yaml`
+  or `.git/` ancestor).
+- **Config**: required file with `skills.*` fields populated. Per-skill packaging
+  options (`skills.config.<name>`) drive link rewriting, bundle inclusion, and
+  validation overrides.
+
+See [Roots and Config — Canonical Concepts](../../../docs/concepts/roots-and-config.md)
+for terminology.
+
 ---
 
 ### vat skills install \<source\>
@@ -378,7 +415,17 @@ vat skills install ./dist/skills/my-skill --target claude --scope project
 **Post-Installation:**
 After installation, you need to:
 1. Restart Claude Code (or the target agent), or
-2. Run `/reload-skills` in Claude Code to load the new skill
+2. Run `/reload-plugins` in Claude Code to load the new skill
+
+**Requirements:**
+
+- **`projectRoot`**: N/A. `vat skills install` is a user-level operation that
+  installs into platform target directories (`~/.claude/skills/`,
+  `.claude/skills/`, etc.) regardless of where it is invoked.
+- **Config**: not used.
+
+See [Roots and Config — Canonical Concepts](../../../docs/concepts/roots-and-config.md)
+for terminology.
 
 ---
 
@@ -453,6 +500,17 @@ vat skills list packages/my-agent
 vat skills list --verbose
 ```
 
+**Requirements:**
+
+- **`projectRoot`**: optional. `vat skills list` tolerates a missing
+  `projectRoot`. With `--user` it scans user installation directories directly
+  and skips project-root discovery entirely.
+- **Config**: optional. Project mode honors config-defined include/exclude
+  patterns when present; defaults are used otherwise.
+
+See [Roots and Config — Canonical Concepts](../../../docs/concepts/roots-and-config.md)
+for terminology.
+
 ---
 
 ## Distribution Workflow
@@ -580,7 +638,7 @@ User: /my-skill
 - Use `--dry-run` to preview what will be installed before committing
 - Use `--force` flag carefully (overwrites existing skills)
 - Verify installation: `vat skills list --user`
-- Remember to restart the target agent or run `/reload-skills` in Claude Code
+- Remember to restart the target agent or run `/reload-plugins` in Claude Code
 
 ---
 
@@ -660,7 +718,7 @@ name: my-help  # Instead of "help"
 **Solution:**
 1. Verify installation: `vat skills list --user`
 2. Check location: Should be in `~/.claude/skills/` not `~/.claude/plugins/`
-3. Restart Claude Code or run `/reload-skills`
+3. Restart Claude Code or run `/reload-plugins`
 
 ### "Windows-style backslashes"
 **Problem:** Links use backslashes: `resources\SKILL.md`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibe-agent-toolkit/cli",
-  "version": "0.1.37",
+  "version": "0.1.39-rc.1",
   "description": "Command-line interface for vibe-agent-toolkit",
   "type": "module",
   "bin": {
@@ -41,27 +41,26 @@
   "//dependencies-note": "DO NOT add example agent packages or adopter packages here. Adopter packages (like vat-development-agents) depend on the CLI binary at build time — declaring them as deps creates a circular build dependency. They are built in a second turbo pass via package#task overrides in turbo.json.",
   "dependencies": {
     "@anthropic-ai/sdk": "^0.71.2",
-    "@vibe-agent-toolkit/agent-config": "0.1.37",
-    "@vibe-agent-toolkit/agent-schema": "0.1.37",
-    "@vibe-agent-toolkit/agent-skills": "0.1.37",
-    "@vibe-agent-toolkit/claude-marketplace": "0.1.37",
-    "@vibe-agent-toolkit/discovery": "0.1.37",
-    "@vibe-agent-toolkit/gateway-mcp": "0.1.37",
-    "@vibe-agent-toolkit/rag": "0.1.37",
-    "@vibe-agent-toolkit/rag-lancedb": "0.1.37",
-    "@vibe-agent-toolkit/resources": "0.1.37",
-    "@vibe-agent-toolkit/utils": "0.1.37",
+    "@vibe-agent-toolkit/agent-config": "0.1.39-rc.1",
+    "@vibe-agent-toolkit/agent-schema": "0.1.39-rc.1",
+    "@vibe-agent-toolkit/agent-skills": "0.1.39-rc.1",
+    "@vibe-agent-toolkit/claude-marketplace": "0.1.39-rc.1",
+    "@vibe-agent-toolkit/discovery": "0.1.39-rc.1",
+    "@vibe-agent-toolkit/gateway-mcp": "0.1.39-rc.1",
+    "@vibe-agent-toolkit/rag": "0.1.39-rc.1",
+    "@vibe-agent-toolkit/rag-lancedb": "0.1.39-rc.1",
+    "@vibe-agent-toolkit/resources": "0.1.39-rc.1",
+    "@vibe-agent-toolkit/utils": "0.1.39-rc.1",
     "adm-zip": "^0.5.16",
     "commander": "^12.1.0",
-    "js-yaml": "^4.1.0",
     "picomatch": "^4.0.3",
     "semver": "^7.7.3",
     "tar": "^7.5.7",
+    "yaml": "^2.6.1",
     "zod": "^3.24.1"
   },
   "devDependencies": {
     "@types/adm-zip": "^0.5.7",
-    "@types/js-yaml": "^4.0.9",
     "@types/node": "^22.10.5",
     "@types/picomatch": "^4.0.2",
     "@types/semver": "^7.7.1",

package/dist/commands/claude/marketplace/tag-utils.d.ts

@@ -1,11 +0,0 @@
-/**
- * Format a per-plugin source-repo tag name for the multi-plugin marketplace
- * publish flow.
- *
- * Plugin-name validation (`/^[a-z0-9][a-z0-9-]*$/`) is enforced upstream by
- * `ClaudeMarketplacePluginEntrySchema`; semver validation is enforced upstream
- * by the schema's `version` refine. This formatter only enforces non-empty
- * inputs.
- */
-export declare function pluginTagName(name: string, version: string): string;
-//# sourceMappingURL=tag-utils.d.ts.map

package/dist/commands/claude/marketplace/tag-utils.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"tag-utils.d.ts","sourceRoot":"","sources":["../../../../src/commands/claude/marketplace/tag-utils.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,wBAAgB,aAAa,CAAC,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,GAAG,MAAM,CAInE"}

package/dist/commands/claude/marketplace/tag-utils.js

@@ -1,17 +0,0 @@
-/**
- * Format a per-plugin source-repo tag name for the multi-plugin marketplace
- * publish flow.
- *
- * Plugin-name validation (`/^[a-z0-9][a-z0-9-]*$/`) is enforced upstream by
- * `ClaudeMarketplacePluginEntrySchema`; semver validation is enforced upstream
- * by the schema's `version` refine. This formatter only enforces non-empty
- * inputs.
- */
-export function pluginTagName(name, version) {
-    if (!name)
-        throw new Error('Plugin name is required for tag naming');
-    if (!version)
-        throw new Error('Version is required for tag naming');
-    return `${name}-v${version}`;
-}
-//# sourceMappingURL=tag-utils.js.map

package/dist/commands/claude/marketplace/tag-utils.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"tag-utils.js","sourceRoot":"","sources":["../../../../src/commands/claude/marketplace/tag-utils.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,MAAM,UAAU,aAAa,CAAC,IAAY,EAAE,OAAe;IACzD,IAAI,CAAC,IAAI;QAAE,MAAM,IAAI,KAAK,CAAC,wCAAwC,CAAC,CAAC;IACrE,IAAI,CAAC,OAAO;QAAE,MAAM,IAAI,KAAK,CAAC,oCAAoC,CAAC,CAAC;IACpE,OAAO,GAAG,IAAI,KAAK,OAAO,EAAE,CAAC;AAC/B,CAAC"}

package/dist/utils/project-root.d.ts

@@ -1,30 +0,0 @@
-/**
- * Project root detection utility
- * Walks up directory tree to find .git or vibe-agent-toolkit.config.yaml
- *
- * Environment Variables:
- * - VAT_TEST_ROOT: Override project root for testing (bypasses detection)
- */
-/**
- * Find project root by walking up directory tree
- *
- * @param startDir - Directory to start search from
- * @returns Project root path or null if not found
- *
- * @remarks
- * Can be overridden with VAT_TEST_ROOT environment variable for testing.
- * This allows tests to specify an exact project root without relying on
- * directory structure (.git or config file presence).
- *
- * @example
- * ```typescript
- * // Normal usage
- * const root = findProjectRoot(process.cwd());
- *
- * // Test usage with override
- * process.env.VAT_TEST_ROOT = '/path/to/test/fixtures';
- * const root = findProjectRoot(process.cwd()); // Returns /path/to/test/fixtures
- * ```
- */
-export declare function findProjectRoot(startDir: string): string | null;
-//# sourceMappingURL=project-root.d.ts.map

package/dist/utils/project-root.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"project-root.d.ts","sourceRoot":"","sources":["../../src/utils/project-root.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAOH;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,wBAAgB,eAAe,CAAC,QAAQ,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CA+B/D"}

package/dist/utils/project-root.js

@@ -1,59 +0,0 @@
-/**
- * Project root detection utility
- * Walks up directory tree to find .git or vibe-agent-toolkit.config.yaml
- *
- * Environment Variables:
- * - VAT_TEST_ROOT: Override project root for testing (bypasses detection)
- */
-import * as fs from 'node:fs';
-import * as path from 'node:path';
-import { safePath } from '@vibe-agent-toolkit/utils';
-/**
- * Find project root by walking up directory tree
- *
- * @param startDir - Directory to start search from
- * @returns Project root path or null if not found
- *
- * @remarks
- * Can be overridden with VAT_TEST_ROOT environment variable for testing.
- * This allows tests to specify an exact project root without relying on
- * directory structure (.git or config file presence).
- *
- * @example
- * ```typescript
- * // Normal usage
- * const root = findProjectRoot(process.cwd());
- *
- * // Test usage with override
- * process.env.VAT_TEST_ROOT = '/path/to/test/fixtures';
- * const root = findProjectRoot(process.cwd()); // Returns /path/to/test/fixtures
- * ```
- */
-export function findProjectRoot(startDir) {
-    // Override for testing: VAT_TEST_ROOT bypasses detection
-    if (process.env['VAT_TEST_ROOT']) {
-        return process.env['VAT_TEST_ROOT'];
-    }
-    let current = safePath.resolve(startDir);
-    const root = path.parse(current).root;
-    while (current !== root) {
-        // Check for .git directory
-        // eslint-disable-next-line security/detect-non-literal-fs-filename -- path walking is intentional
-        if (fs.existsSync(safePath.join(current, '.git'))) {
-            return current;
-        }
-        // Check for config file
-        // eslint-disable-next-line security/detect-non-literal-fs-filename -- path walking is intentional
-        if (fs.existsSync(safePath.join(current, 'vibe-agent-toolkit.config.yaml'))) {
-            return current;
-        }
-        // Move up one directory
-        const parent = path.dirname(current);
-        if (parent === current) {
-            break; // Reached root
-        }
-        current = parent;
-    }
-    return null;
-}
-//# sourceMappingURL=project-root.js.map

package/dist/utils/project-root.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"project-root.js","sourceRoot":"","sources":["../../src/utils/project-root.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,KAAK,EAAE,MAAM,SAAS,CAAC;AAC9B,OAAO,KAAK,IAAI,MAAM,WAAW,CAAC;AAElC,OAAO,EAAE,QAAQ,EAAE,MAAM,2BAA2B,CAAC;AAErD;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,MAAM,UAAU,eAAe,CAAC,QAAgB;IAC9C,yDAAyD;IACzD,IAAI,OAAO,CAAC,GAAG,CAAC,eAAe,CAAC,EAAE,CAAC;QACjC,OAAO,OAAO,CAAC,GAAG,CAAC,eAAe,CAAC,CAAC;IACtC,CAAC;IAED,IAAI,OAAO,GAAG,QAAQ,CAAC,OAAO,CAAC,QAAQ,CAAC,CAAC;IACzC,MAAM,IAAI,GAAG,IAAI,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,IAAI,CAAC;IAEtC,OAAO,OAAO,KAAK,IAAI,EAAE,CAAC;QACxB,2BAA2B;QAC3B,kGAAkG;QAClG,IAAI,EAAE,CAAC,UAAU,CAAC,QAAQ,CAAC,IAAI,CAAC,OAAO,EAAE,MAAM,CAAC,CAAC,EAAE,CAAC;YAClD,OAAO,OAAO,CAAC;QACjB,CAAC;QAED,wBAAwB;QACxB,kGAAkG;QAClG,IAAI,EAAE,CAAC,UAAU,CAAC,QAAQ,CAAC,IAAI,CAAC,OAAO,EAAE,gCAAgC,CAAC,CAAC,EAAE,CAAC;YAC5E,OAAO,OAAO,CAAC;QACjB,CAAC;QAED,wBAAwB;QACxB,MAAM,MAAM,GAAG,IAAI,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;QACrC,IAAI,MAAM,KAAK,OAAO,EAAE,CAAC;YACvB,MAAM,CAAC,eAAe;QACxB,CAAC;QACD,OAAO,GAAG,MAAM,CAAC;IACnB,CAAC;IAED,OAAO,IAAI,CAAC;AACd,CAAC"}