skannr 0.1.3 → 0.1.4

package/.eslintrc.js

@@ -1,22 +1,22 @@
-module.exports = {
-  parser: '@typescript-eslint/parser',
-  extends: [
-    'eslint:recommended',
-    'plugin:@typescript-eslint/recommended',
-  ],
-  parserOptions: {
-    ecmaVersion: 2022,
-    sourceType: 'module',
-  },
-  env: {
-    node: true,
-    es6: true,
-    jest: true,
-  },
-  rules: {
-    '@typescript-eslint/explicit-function-return-type': 'off',
-    '@typescript-eslint/no-explicit-any': 'warn',
-    '@typescript-eslint/no-unused-vars': ['error', { argsIgnorePattern: '^_' }],
-    'no-console': 'off',
-  },
-};
+module.exports = {
+  parser: '@typescript-eslint/parser',
+  extends: [
+    'eslint:recommended',
+    'plugin:@typescript-eslint/recommended',
+  ],
+  parserOptions: {
+    ecmaVersion: 2022,
+    sourceType: 'module',
+  },
+  env: {
+    node: true,
+    es6: true,
+    jest: true,
+  },
+  rules: {
+    '@typescript-eslint/explicit-function-return-type': 'off',
+    '@typescript-eslint/no-explicit-any': 'warn',
+    '@typescript-eslint/no-unused-vars': ['error', { argsIgnorePattern: '^_' }],
+    'no-console': 'off',
+  },
+};

package/README.md

@@ -1,174 +1,260 @@
-# Skannr
-
-A CLI tool and MCP server that helps AI agents understand **any codebase**.
-It scans files, generates compressed structural "skeletons", and ranks results
-using hybrid retrieval — reducing token usage by ~96% vs full file scans.
-
-## How It Works
-
-1. You point it at any repo with `--root /path/to/repo`
-2. It auto-detects the language (TypeScript, JavaScript, Python, or generic fallback)
-3. It auto-discovers your project's modules from the folder structure
-4. For your question, it ranks the most relevant files using lexical + structural + dependency-graph analysis
-5. It strips function bodies from files (keeping types, signatures, imports)
-6. Returns compact skeletons an AI can reason over without blowing the context window
-
-## Install
-
-```bash
-npm install -g skannr
-```
-
-## Usage
-
-### CLI
-
-```bash
-# Basic
-skannr --question "how does authentication work?" --root /path/to/any/repo
-
-# Limit results
-skannr --question "database connection setup" --root . --limit 5
-
-# Focus on specific modules (auto-discovered if not specified)
-skannr --question "permission checks" --root . --modules auth,middleware
-
-# Force language
-skannr --question "class structure" --root /path/to/python/project --lang python
-
-# Interactive agent mode
-skannr-agent --root /path/to/repo
-
-# Cache management
-skannr --cache-stats
-skannr --cache-clear
-skannr --question "..." --skip-cache
-
-# Output: human (default), markdown, or json
-skannr --question "..." --root . --format markdown
-skannr --question "..." --root . --format json
-
-# Repository health report (JSON on stdout)
-skannr --report --root .
-
-# Re-run analysis when files change (debounced; uses fresh analysis each pass)
-skannr --question "..." --root . --watch
-```
-
-### Watch mode (`--watch`)
-
-Use `--watch` when you want Skannr to stay running and **re-analyze after relevant file changes** (large repos you edit often). Changes under common build/vendor dirs are ignored (`node_modules`, `.git`, `dist`, etc.). Press **Ctrl+C** to stop.
-
-Each run bypasses the analysis cache so results reflect the tree as it is now.
-
-### Anonymous telemetry (opt-in)
-
-Telemetry is **off unless you enable it** (or accept deferred opt-in — see below). It sends **only which CLI flags were used** — never your question text, file paths, or code.
-
-- Enable: `skannr --telemetry-on`
-- Disable: `skannr --telemetry-off`
-
-Settings are stored under `~/.skannr/config.json`. The first time you run an analyze command with no config yet, Skannr may show a short notice; you can opt in or out anytime with the flags above.
-
-If you take no action, telemetry may turn on automatically **after 7 days** from that notice unless you explicitly disabled it with `--telemetry-off`.
-
-## MCP Server
-
-`skannr` ships with a built-in MCP server. One-time setup per AI tool:
-
-### Cursor
-
-`~/.cursor/mcp.json`:
-
-```json
-{
-  "mcpServers": {
-    "skannr": {
-      "command": "npx",
-      "args": ["-y", "skannr", "--mcp"]
-    }
-  }
-}
-```
-
-### Claude Desktop / Claude Code
-
-`~/Library/Application Support/Claude/claude_desktop_config.json`:
-
-```json
-{
-  "mcpServers": {
-    "skannr": {
-      "command": "npx",
-      "args": ["-y", "skannr", "--mcp"]
-    }
-  }
-}
-```
-
-### Gemini CLI
-
-`~/.gemini/config.json`:
-
-```json
-{
-  "mcpServers": {
-    "skannr": {
-      "command": "npx",
-      "args": ["-y", "skannr", "--mcp"]
-    }
-  }
-}
-```
-
-Alternatively run the dedicated binary: `skannr-mcp` (same stdio server).
-
-## Config File (optional)
-
-Drop a `code-analyzer.config.json` in your repo root:
-
-```json
-{
-  "modules": {
-    "auth": ["src/auth", "lib/auth"],
-    "api": ["src/api", "src/routes"]
-  },
-  "exclude": ["**/generated/**", "**/migrations/**"],
-  "extensions": [".ts", ".js"],
-  "defaultLimit": 10
-}
-```
-
-## Supported Languages
-
-| Language | Skeleton Support |
-|---|---|
-| TypeScript / TSX | Full AST (ts-morph) |
-| JavaScript / JSX | Full AST (ts-morph) |
-| Python | Regex-based (signatures + types) |
-| Others | First 50 lines (generic fallback) |
-
-## Performance
-
-Benchmarked on large TypeScript monorepo:
-
-| Metric | Result |
-|---|---|
-| Token Reduction vs Full Scan | ~96.5% |
-| Token Reduction vs Top-N | ~78.2% |
-| Avg keyword coverage | ~75% |
-| Directory diversity (top-5) | ~80% |
-| Average execution time | ~1.2s |
-
-## Interactive Agent Commands
-
-```
-/help              Show all commands
-/files             List retrieved files
-/symbols <query>   Search for symbols
-/symbol <id>       Get full implementation
-/deps <file>       Show imports for a file
-/refresh           Re-analyze with new context
-/stats             Show mapping statistics
-/exit              Quit
-```
+# Skannr
+
+A CLI tool and MCP server that helps AI agents understand **any codebase**.
+It scans files, generates compressed structural "skeletons", and ranks results
+using hybrid retrieval — reducing token usage by ~96% vs full file scans.
+
+## How It Works
+
+1. You point it at any repo with `--root /path/to/repo`
+2. It auto-detects the language (TypeScript, JavaScript, Python, or generic fallback)
+3. It auto-discovers your project's modules from the folder structure
+4. For your question, it ranks the most relevant files using lexical + structural + dependency-graph analysis
+5. It strips function bodies from files (keeping types, signatures, imports)
+6. Returns compact skeletons an AI can reason over without blowing the context window
+
+## Install
+
+```bash
+npm install -g skannr
+```
+
+## Usage
+
+### CLI
+
+```bash
+# Basic
+skannr --question "how does authentication work?" --root /path/to/any/repo
+
+# Limit results
+skannr --question "database connection setup" --root . --limit 5
+
+# Focus on specific modules (auto-discovered if not specified)
+skannr --question "permission checks" --root . --modules auth,middleware
+
+# Force language
+skannr --question "class structure" --root /path/to/python/project --lang python
+
+# Interactive agent mode
+skannr-agent --root /path/to/repo
+
+# Cache management
+skannr --cache-stats
+skannr --cache-clear
+skannr --question "..." --skip-cache
+
+# Output: human (default), markdown, or json
+skannr --question "..." --root . --format markdown
+skannr --question "..." --root . --format json
+
+# Repository health report (JSON on stdout)
+skannr --report --root .
+
+# Re-run analysis when files change (debounced; uses fresh analysis each pass)
+skannr --question "..." --root . --watch
+```
+
+### Watch mode (`--watch`)
+
+Use `--watch` when you want Skannr to stay running and **re-analyze after relevant file changes** (large repos you edit often). Changes under common build/vendor dirs are ignored (`node_modules`, `.git`, `dist`, etc.). Press **Ctrl+C** to stop.
+
+Each run bypasses the analysis cache so results reflect the tree as it is now.
+
+### Anonymous telemetry (opt-in)
+
+Telemetry is **off unless you enable it** (or accept deferred opt-in — see below). It sends **only which CLI flags were used** — never your question text, file paths, or code.
+
+- Enable: `skannr --telemetry-on`
+- Disable: `skannr --telemetry-off`
+
+Settings are stored under `~/.skannr/config.json`. The first time you run an analyze command with no config yet, Skannr may show a short notice; you can opt in or out anytime with the flags above.
+
+If you take no action, telemetry may turn on automatically **after 7 days** from that notice unless you explicitly disabled it with `--telemetry-off`.
+
+## MCP Server
+
+`skannr` ships with a built-in MCP server. One-time setup per AI tool:
+
+### Cursor
+
+`~/.cursor/mcp.json`:
+
+```json
+{
+  "mcpServers": {
+    "skannr": {
+      "command": "npx",
+      "args": ["-y", "skannr", "--mcp"]
+    }
+  }
+}
+```
+
+### Claude Desktop / Claude Code
+
+`~/Library/Application Support/Claude/claude_desktop_config.json`:
+
+```json
+{
+  "mcpServers": {
+    "skannr": {
+      "command": "npx",
+      "args": ["-y", "skannr", "--mcp"]
+    }
+  }
+}
+```
+
+### Gemini CLI
+
+`~/.gemini/config.json`:
+
+```json
+{
+  "mcpServers": {
+    "skannr": {
+      "command": "npx",
+      "args": ["-y", "skannr", "--mcp"]
+    }
+  }
+}
+```
+
+Alternatively run the dedicated binary: `skannr-mcp` (same stdio server).
+
+## Config File (optional)
+
+Drop a `code-analyzer.config.json` in your repo root:
+
+```json
+{
+  "modules": {
+    "auth": ["src/auth", "lib/auth"],
+    "api": ["src/api", "src/routes"]
+  },
+  "exclude": ["**/generated/**", "**/migrations/**"],
+  "extensions": [".ts", ".js"],
+  "defaultLimit": 10
+}
+```
+
+## Supported Languages
+
+| Language | Skeleton Support |
+|---|---|
+| TypeScript / TSX | Full AST (ts-morph) |
+| JavaScript / JSX | Full AST (ts-morph) |
+| Python | Regex-based (signatures + types) |
+| Others | First 50 lines (generic fallback) |
+
+## Performance
+
+Benchmarked on large TypeScript monorepo:
+
+| Metric | Result |
+|---|---|
+| Token Reduction vs Full Scan | ~96.5% |
+| Token Reduction vs Top-N | ~78.2% |
+| Avg keyword coverage | ~75% |
+| Directory diversity (top-5) | ~80% |
+| Average execution time | ~1.2s |
+
+## Interactive Agent Commands
+
+```
+/help              Show all commands
+/files             List retrieved files
+/symbols <query>   Search for symbols
+/symbol <id>       Get full implementation
+/deps <file>       Show imports for a file
+/refresh           Re-analyze with new context
+/stats             Show mapping statistics
+/exit              Quit
+```
+
+## Blast Radius
+
+Analyze the downstream impact and risk of a code change. Given a git diff,
+blast-radius identifies which files are affected, how central they are in the
+dependency graph, and whether they have test coverage.
+
+**Limitation (v1):** Traversal is computed at file granularity — "file A
+imports file B" — not at function-call level. Function-level resolution is
+planned for a future version.
+
+### CLI
+
+```bash
+# Analyze working tree changes vs HEAD (default)
+skannr blast-radius --root .
+
+# Analyze a specific diff file, 3 hops deep
+skannr blast-radius --root . --diff changes.patch --hops 3
+
+# JSON output for CI pipelines
+skannr blast-radius --root . --json
+```
+
+Sample terminal output:
+
+```
+  Blast Radius Analysis (2-hop traversal)
+  ──────────────────────────────────────────────────
+
+  Risk Score: 5.8/10
+  Risk 5.8/10 (moderate): 1 file(s) changed, 4 downstream affected, 3 untested.
+
+  Changed files:
+    src/auth/session.ts
+
+  Changed symbols:
+    function validateToken (src/auth/session.ts)
+
+  Hop 1 (2 files):
+    src/middleware/auth-guard.ts  centrality=0.85 [NO TEST]
+    src/api/login.ts              centrality=0.60
+
+  Hop 2 (2 files):
+    src/routes/index.ts           centrality=0.45 [NO TEST]
+    src/api/admin.ts              centrality=0.30 [NO TEST]
+
+  Formula inputs:
+    affected_count (normalized): 0.080
+    avg_centrality:              0.550
+    untested_ratio:              0.750
+    hop_spread (normalized):     1.000
+```
+
+### MCP
+
+The `blast_radius` tool is exposed via the same MCP server (`skannr --mcp`).
+
+Input schema:
+
+```json
+{
+  "root": "/path/to/repo",
+  "diff": "<optional unified diff content>",
+  "hops": 2
+}
+```
+
+If `diff` is omitted, the tool runs `git diff HEAD` in the given root.
+The output is the same JSON structure as `skannr blast-radius --json`.
+
+### Risk Score Formula
+
+```
+risk = 2.5 × normalizedAffectedCount
+     + 2.5 × avgCentrality
+     + 3.5 × untestedRatio
+     + 1.5 × normalizedMaxHopSpread
+```
+
+| Input | Range | Meaning |
+|-------|-------|---------|
+| normalizedAffectedCount | 0–1 | Affected files / total project files |
+| avgCentrality | 0–1 | Mean in-degree centrality of affected files |
+| untestedRatio | 0–1 | Fraction of affected files with no test file |
+| normalizedMaxHopSpread | 0–1 | Deepest hop reached / max configured hops |

package/dist/agent-cli.js

@@ -140,31 +140,31 @@ function parseArgs() {
  * Print help message
  */
 function printHelp() {
-    console.log(`
-skannr-agent — AI-powered code analysis (Gemini)
-
-Usage:
-  skannr-agent --question "<text>" [options]
-  skannr-agent --interactive [options]
-
-Options:
-  --root <path>        Project root directory (default: current directory)
-  --question "<text>"  Question to analyze (required unless --interactive)
-  --limit <number>     Number of top files to analyze (default: 10)
-  --api-key <key>      Gemini API key (or set GEMINI_API_KEY env var)
-  --model <name>       Gemini model name (default: gemini-2.0-flash-exp)
-  --interactive, -i  Start interactive chat mode
-  --help, -h           Show this help message
-
-Examples:
-  skannr-agent --question "How does authentication work?"
-  skannr-agent --interactive --root ./my-project
-  skannr-agent --question "Find all API endpoints" --limit 15
-
-Environment variables:
-  GEMINI_API_KEY       Gemini API key (alternative to --api-key)
-
-Docs: https://skannr-ten.vercel.app
+    console.log(`
+skannr-agent — AI-powered code analysis (Gemini)
+
+Usage:
+  skannr-agent --question "<text>" [options]
+  skannr-agent --interactive [options]
+
+Options:
+  --root <path>        Project root directory (default: current directory)
+  --question "<text>"  Question to analyze (required unless --interactive)
+  --limit <number>     Number of top files to analyze (default: 10)
+  --api-key <key>      Gemini API key (or set GEMINI_API_KEY env var)
+  --model <name>       Gemini model name (default: gemini-2.0-flash-exp)
+  --interactive, -i  Start interactive chat mode
+  --help, -h           Show this help message
+
+Examples:
+  skannr-agent --question "How does authentication work?"
+  skannr-agent --interactive --root ./my-project
+  skannr-agent --question "Find all API endpoints" --limit 15
+
+Environment variables:
+  GEMINI_API_KEY       Gemini API key (alternative to --api-key)
+
+Docs: https://skannr-ten.vercel.app
   `);
 }
 /**

package/dist/agent.js

@@ -48,8 +48,8 @@ const path = __importStar(require("path"));
  */
 exports.getSymbolDetailsTool = {
     name: 'get_symbol_details',
-    description: `Retrieve the full implementation of a code symbol (function, method, class) from the original source file.
-Use this when you need to see the actual implementation of a function or method that was marked with [SYMBOL:...] in the skeleton.
+    description: `Retrieve the full implementation of a code symbol (function, method, class) from the original source file.
+Use this when you need to see the actual implementation of a function or method that was marked with [SYMBOL:...] in the skeleton.
 The symbolId is in the format "ClassName.methodName" or "functionName" for top-level functions.`,
     parameters: {
         type: generative_ai_1.SchemaType.OBJECT,
@@ -67,7 +67,7 @@ The symbolId is in the format "ClassName.methodName" or "functionName" for top-l
  */
 exports.searchSymbolsTool = {
     name: 'search_symbols',
-    description: `Search for available symbols in the generated skeletons. Returns a list of matching symbols that can be retrieved using get_symbol_details.
+    description: `Search for available symbols in the generated skeletons. Returns a list of matching symbols that can be retrieved using get_symbol_details.
 Use this to discover what functions/methods are available before requesting their full implementation.`,
     parameters: {
         type: generative_ai_1.SchemaType.OBJECT,
@@ -90,7 +90,7 @@ Use this to discover what functions/methods are available before requesting thei
  */
 exports.analyzeFileDependenciesTool = {
     name: 'analyze_file_dependencies',
-    description: `Analyze import/export relationships for a specific file from the skeleton.
+    description: `Analyze import/export relationships for a specific file from the skeleton.
 Use this to understand what other files a given file depends on.`,
     parameters: {
         type: generative_ai_1.SchemaType.OBJECT,

package/dist/blast-radius.d.ts

@@ -0,0 +1,80 @@
+/**
+ * Blast Radius: determines downstream impact and risk of a git diff.
+ *
+ * Pipeline: parse diff → identify changed files → traverse reverse dependency
+ * graph N hops → score affected nodes by centrality → flag untested nodes →
+ * compute aggregate risk score.
+ *
+ * Limitation (v1): graph traversal is file-level, not symbol-level.
+ * A changed file is treated as a unit; individual function-call edges are not
+ * tracked. Symbol extraction from diffs is used for reporting only.
+ */
+import type { Symbol } from './languages/LanguageAdapter';
+/** A symbol touched by the diff within a single file. */
+export interface ChangedSymbol {
+    name: string;
+    kind: Symbol['kind'];
+    file: string;
+}
+/** A downstream file affected by the change, with metadata. */
+export interface AffectedNode {
+    /** Path relative to project root. */
+    file: string;
+    /** Number of hops from a changed file (1 = direct importer). */
+    hopDistance: number;
+    /** Normalized centrality score [0,1] — how many files depend on this one. */
+    centrality: number;
+    /** Whether a corresponding test file was found for this file. */
+    hasTest: boolean;
+}
+/** Full blast-radius analysis result (shared between CLI text and JSON output). */
+export interface BlastRadiusResult {
+    /** Aggregate risk score (0–10). */
+    riskScore: number;
+    /** One-line human-readable summary. */
+    summary: string;
+    /** Files directly modified by the diff (relative paths). */
+    changedFiles: string[];
+    /** Symbols identified as changed within those files. */
+    changedSymbols: ChangedSymbol[];
+    /** All downstream affected files grouped by hop distance. */
+    affectedNodes: AffectedNode[];
+    /** Breakdown of the risk formula inputs (for transparency). */
+    formulaInputs: {
+        normalizedAffectedCount: number;
+        avgCentrality: number;
+        untestedRatio: number;
+        normalizedMaxHopSpread: number;
+    };
+    /** Max hops used for this analysis. */
+    hops: number;
+}
+/** Options accepted by computeBlastRadius. */
+export interface BlastRadiusOptions {
+    /** Absolute path to project root. */
+    root: string;
+    /** Raw unified diff content. If omitted, working-tree diff against HEAD is used. */
+    diffContent?: string;
+    /** Path to a diff file on disk. Takes precedence over diffContent if both given. */
+    diffPath?: string;
+    /** Maximum hop distance for traversal (default: 2). */
+    hops?: number;
+}
+/** Compute the blast radius for a diff against a project. */
+export declare function computeBlastRadius(options: BlastRadiusOptions): BlastRadiusResult;
+/**
+ * Invert the forward graph (file → imports) into a reverse graph
+ * (file → files that import it).
+ */
+export declare function buildReverseGraph(forwardGraph: Map<string, string[]>): Map<string, string[]>;
+/**
+ * BFS from changed files outward on the reverse graph, up to maxHops.
+ * Returns a map of affected file → hop distance (excluding the changed files
+ * themselves).
+ */
+export declare function traverseAffected(changedFiles: string[], reverseGraph: Map<string, string[]>, maxHops: number): Map<string, number>;
+/** Plain-text report for terminal output. */
+export declare function formatBlastRadiusText(result: BlastRadiusResult): string;
+/** JSON output (for --json flag and MCP). */
+export declare function formatBlastRadiusJson(result: BlastRadiusResult): string;
+//# sourceMappingURL=blast-radius.d.ts.map

package/dist/blast-radius.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"blast-radius.d.ts","sourceRoot":"","sources":["../src/blast-radius.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAUH,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,6BAA6B,CAAC;AAe1D,yDAAyD;AACzD,MAAM,WAAW,aAAa;IAC5B,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC,MAAM,CAAC,CAAC;IACrB,IAAI,EAAE,MAAM,CAAC;CACd;AAED,+DAA+D;AAC/D,MAAM,WAAW,YAAY;IAC3B,qCAAqC;IACrC,IAAI,EAAE,MAAM,CAAC;IACb,gEAAgE;IAChE,WAAW,EAAE,MAAM,CAAC;IACpB,6EAA6E;IAC7E,UAAU,EAAE,MAAM,CAAC;IACnB,iEAAiE;IACjE,OAAO,EAAE,OAAO,CAAC;CAClB;AAED,mFAAmF;AACnF,MAAM,WAAW,iBAAiB;IAChC,mCAAmC;IACnC,SAAS,EAAE,MAAM,CAAC;IAClB,uCAAuC;IACvC,OAAO,EAAE,MAAM,CAAC;IAChB,4DAA4D;IAC5D,YAAY,EAAE,MAAM,EAAE,CAAC;IACvB,wDAAwD;IACxD,cAAc,EAAE,aAAa,EAAE,CAAC;IAChC,6DAA6D;IAC7D,aAAa,EAAE,YAAY,EAAE,CAAC;IAC9B,+DAA+D;IAC/D,aAAa,EAAE;QACb,uBAAuB,EAAE,MAAM,CAAC;QAChC,aAAa,EAAE,MAAM,CAAC;QACtB,aAAa,EAAE,MAAM,CAAC;QACtB,sBAAsB,EAAE,MAAM,CAAC;KAChC,CAAC;IACF,uCAAuC;IACvC,IAAI,EAAE,MAAM,CAAC;CACd;AAED,8CAA8C;AAC9C,MAAM,WAAW,kBAAkB;IACjC,qCAAqC;IACrC,IAAI,EAAE,MAAM,CAAC;IACb,oFAAoF;IACpF,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,oFAAoF;IACpF,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,uDAAuD;IACvD,IAAI,CAAC,EAAE,MAAM,CAAC;CACf;AAMD,6DAA6D;AAC7D,wBAAgB,kBAAkB,CAAC,OAAO,EAAE,kBAAkB,GAAG,iBAAiB,CA8CjF;AA6GD;;;GAGG;AACH,wBAAgB,iBAAiB,CAC/B,YAAY,EAAE,GAAG,CAAC,MAAM,EAAE,MAAM,EAAE,CAAC,GAClC,GAAG,CAAC,MAAM,EAAE,MAAM,EAAE,CAAC,CAcvB;AAMD;;;;GAIG;AACH,wBAAgB,gBAAgB,CAC9B,YAAY,EAAE,MAAM,EAAE,EACtB,YAAY,EAAE,GAAG,CAAC,MAAM,EAAE,MAAM,EAAE,CAAC,EACnC,OAAO,EAAE,MAAM,GACd,GAAG,CAAC,MAAM,EAAE,MAAM,CAAC,CA8BrB;AA4PD,6CAA6C;AAC7C,wBAAgB,qBAAqB,CAAC,MAAM,EAAE,iBAAiB,GAAG,MAAM,CAyDvE;AAED,6CAA6C;AAC7C,wBAAgB,qBAAqB,CAAC,MAAM,EAAE,iBAAiB,GAAG,MAAM,CAEvE"}