@codeyam/codeyam-cli 0.1.0-staging.28f73cf → 0.1.0-staging.323686

package/codeyam-cli/templates/codeyam-test-skill.md

@@ -1,178 +0,0 @@
----
-name: CodeYam Testing
-autoApprove: true
-description: |
-  Use this skill to write comprehensive unit and integration tests using CodeYam's mock generation.
-  Use when: User asks to write tests, generate mocks, understand function dependencies, or improve test coverage.
-  This skill uses the `codeyam generate-data-structure` command to create realistic test mocks based on actual code analysis.
----
-
-# CodeYam Testing Assistant
-
-Use this skill to help users write comprehensive unit and integration tests for their code using CodeYam's dependency analysis and mock generation.
-
-## When to Use This Skill
-
-- User asks to write unit or integration tests
-- User wants to generate Jest mocks for a function
-- User needs help understanding function dependencies for testing
-- User requests mock data for testing
-- You see an opportunity to improve test coverage
-- Testing complex functions with many dependencies
-
-## Important: Permissions Already Configured
-
-The `codeyam init` command has already auto-approved:
-
-- ✅ All CodeYam CLI commands (including `codeyam generate-data-structure`)
-- ✅ All CodeYam skills
-- ✅ All file operations in the `.codeyam/` directory
-
-You can freely use Read, Write, and Bash tools for CodeYam operations without asking for permission.
-
-## Workflow: Writing Tests with CodeYam
-
-### Step 1: Generate Mock Template
-
-Use `codeyam generate-data-structure` to analyze the function and generate a mock template:
-
-```bash
-codeyam generate-data-structure --entity FunctionName path/to/file.ts
-```
-
-**What this does:**
-
-1. Runs partial analysis (data structure only, no scenarios)
-2. Discovers all function dependencies
-3. Generates Jest mock template with proper types
-4. Caches results for instant subsequent runs
-
-**Optional flags:**
-
-- `--json` - Output raw data structure for advanced use cases
-- `--output path/to/output.ts` - Write to file instead of stdout
-
-**Example:**
-
-```bash
-codeyam generate-data-structure --entity computeBranchEntityDiff codeyam-cli/src/webserver/app/lib/branchEntityComparison.ts
-```
-
-### Step 2: Understand the Analysis Output
-
-The mock template shows:
-
-- **Dependencies by module** - All external functions/imports
-- **Mock declarations** - `jest.mock()` calls for each module
-- **Return value templates** - Sample data for `mockReturnValue()`
-
-**With `--json` flag, you get:**
-
-```json
-{
-  "dataForMocks": {
-    "getProjectRoot()": "/project/root",
-    "getBranchDiffForProject(baseBranch, compareBranch)": [...]
-  },
-  "dependencySchemas": {
-    "module/path": {
-      "functionName": { "type": "object", "properties": {...} }
-    }
-  }
-}
-```
-
-### Step 3: Write the Test
-
-Use the generated template as a starting point:
-
-**Key principles learned from experience:**
-
-1. **Mock external dependencies only** - Let internal functions run
-2. **Use realistic mock data** - Based on CodeYam's analysis
-3. **Test behavior, not implementation** - Focus on what the function does
-4. **Consider edge cases** - Added files, deleted files, empty results, etc.
-
-**Example pattern:**
-
-```typescript
-// Mock external dependencies
-jest.mock('path/to/module', () => ({
-  externalFunction: jest.fn(),
-}));
-
-describe('FunctionName', () => {
-  beforeEach(() => {
-    jest.clearAllMocks();
-    // Setup default mocks
-  });
-
-  it('should handle normal case', () => {
-    // Arrange: Setup mocks
-    // Act: Call function
-    // Assert: Verify behavior
-  });
-
-  it('should handle edge case', () => {
-    // Test edge cases
-  });
-});
-```
-
-### Step 4: Run the Test
-
-```bash
-npx jest path/to/test.test.ts --verbose
-```
-
-### Step 5: Iterate
-
-If tests fail:
-
-1. Check mock data matches actual usage
-2. Verify mock call counts (added files call extract once, modified call twice)
-3. Ensure edge cases are handled
-4. Use `jest.clearAllMocks()` between tests for isolation
-
-## Common Testing Patterns
-
-### Integration Tests
-
-- Mock external dependencies (fs, child_process, imports)
-- Let internal logic run naturally
-- Test complete workflows
-
-### Unit Tests
-
-- Mock all dependencies
-- Test single function in isolation
-- Focus on edge cases and error handling
-
-### Cache Testing
-
-- Test both cache hit and miss scenarios
-- Verify cache writes happen correctly
-- Ensure cache reads prevent unnecessary work
-
-## Tips from Experience
-
-1. **Call counts matter** - Different file statuses call dependencies differently:
-   - Modified files: extract entities from old AND new content (2 calls)
-   - Added files: extract only from new content (1 call)
-   - Deleted files: extract only from old content (1 call)
-
-2. **Mock isolation** - Use `jest.clearAllMocks()` between tests to prevent interference
-
-3. **Realistic data** - Use CodeYam's analysis to ensure mock data matches real usage patterns
-
-4. **Test structure** - Organize by scenarios (cache hit, cache miss, edge cases)
-
-## When NOT to Use This Skill
-
-- User wants to simulate a component in the browser → Use **CodeYam Simulation** skill instead
-- User wants to see visual screenshots of scenarios → Use **CodeYam Simulation** skill instead
-- User asks to "analyze" or "simulate" an entity → Use **CodeYam Simulation** skill instead
-
----
-
-**Remember**: This skill is for writing traditional unit/integration tests with Jest. For running CodeYam simulations with screenshots and scenarios, use the CodeYam Simulation skill.

package/codeyam-cli/templates/codeyam-verify-skill.md

@@ -1,179 +0,0 @@
----
-name: CodeYam Verify
-autoApprove: true
-description: |
-  Use this skill after making code changes that impact application functionality.
-  Automatically run simulations to verify your changes and present results to the user.
-  Use when: You've completed making changes to visual components or library functions and are ready to present your work.
-
-  NOTE: A Stop hook is installed that will remind you to use this skill if you made changes to .ts/.tsx/.jsx/.vue files during the session.
----
-
-# CodeYam Verify Assistant
-
-Use this skill to automatically verify code changes by running simulations and presenting results to the user.
-
-## When to Use This Skill
-
-**IMPORTANT: Use this skill automatically after making code changes that affect:**
-
-- Visual components (React components, Vue components, UI elements)
-- Library functions (exported functions, utility methods, business logic)
-- Any other code that impacts application functionality
-
-**You should invoke this skill:**
-
-- After completing a set of code changes
-- Before presenting your work to the user
-- When you want to demonstrate the impact of your changes
-
-**DO NOT use this skill for:**
-
-- Documentation-only changes
-- Type definition changes that don't affect runtime behavior
-- Configuration file updates (unless they affect component behavior)
-
-## Important: Permissions Already Configured
-
-The `codeyam init` command has already auto-approved:
-
-- ✅ All CodeYam CLI commands (including `codeyam verify`)
-- ✅ All CodeYam skills
-- ✅ All file operations in the `.codeyam/` directory
-
-You can freely use the verify command without asking for permission.
-
-## Workflow: Verifying Your Changes
-
-When you're ready to present your changes to the user, follow this workflow:
-
-### Step 1: Run the Verify Command
-
-Execute the verify command to detect changed entities and launch the dashboard:
-
-```bash
-codeyam verify
-```
-
-**Optional: Provide Business Logic Context**
-
-If you made business logic changes that require specific data to demonstrate, use the `--context` and `--scenario-count` flags:
-
-```bash
-codeyam verify \
-  --context "Added warning icon that displays when status is 'deleted'. Create scenarios with status='deleted' to show the warning icon prominently" \
-  --scenario-count 3
-```
-
-**When to provide context:**
-
-- ✅ New feature that depends on specific data values (e.g., "show badge when count > 0")
-- ✅ Conditional rendering added based on data (e.g., "warning icon when status is 'deleted'")
-- ✅ Business logic changed in a way that specific data reveals the change (e.g., "empty state when array is empty")
-- ❌ Pure refactoring (extracting components, renaming, reorganizing) - no context needed
-- ❌ Style-only changes (colors, fonts, spacing) - no context needed
-- ❌ Type safety improvements - no context needed
-
-**Context format:**
-
-1. Describe what changed (the new behavior)
-2. Describe what data needs to be present/missing/specific to demonstrate it
-3. Be specific about data values that trigger the behavior
-
-**What this does:**
-
-1. Scans your git working directory for changed files
-2. Detects which entities (functions, components) were modified or added
-3. Filters to only visual and library entities
-4. Starts the CodeYam dashboard server (if not already running)
-5. Opens your browser to the Git verification page
-6. **If context provided**: Passes it to the analyzer to generate scenarios demonstrating the changes
-
-### Step 2: Interpret the Results
-
-The verify command will either:
-
-**If NO visual or library entities changed:**
-
-- The command exits with a message
-- No further action needed
-- Present your changes to the user normally
-
-**If entities WERE changed:**
-
-- The command lists all changed entities
-- Opens the browser to http://localhost:3111/git
-- The dashboard shows your changes with options to analyze them
-
-### Step 3: Present Results to the User
-
-After running `codeyam verify`, tell the user:
-
-**Example message:**
-
-```
-I've completed the changes and kicked off simulations for the modified components.
-
-Changed entities:
-  • Button (visual) - components/Button.tsx
-  • formatDate (library) - utils/formatters.ts
-
-You can view the results and run simulations at: http://localhost:3111/git
-
-On the Git page, you can:
-  • View all changed entities
-  • Click "Analyze All" to run simulations for all entities
-  • Click "Analyze" on individual entities to run specific simulations
-  • View real-time progress as analyses complete
-```
-
-## Complete Example
-
-**User asks:** "Can you update the Button component to support a loading state?"
-
-**Your workflow:**
-
-1. Make the code changes to the Button component
-2. BEFORE presenting to the user, invoke this skill
-3. Run `codeyam verify` with context to demonstrate the new loading state
-4. Present the changes to the user with the verification link
-
-**Your response:**
-
-```
-I've updated the Button component to support a loading state. The changes include:
-- Added a `loading` prop to the Button interface
-- Display a spinner when loading is true
-- Disable the button during loading
-
-I've kicked off simulations to verify these changes with scenarios that show the loading state:
-
-codeyam verify \
-  --context "Added loading state to Button. Create scenarios with loading=true to show the spinner and disabled state" \
-  --scenario-count 2
-
-You can view the results at: http://localhost:3111/git
-
-The simulations will show:
-- Normal button state
-- Loading button state with spinner
-```
-
-## Important Notes
-
-- **Always run verify AFTER making changes** - not before, not during
-- **The verify command only detects uncommitted changes** - changes that aren't yet committed to git
-- **If no relevant entities changed** - the command will exit quickly and you can present your work normally
-- **Simulations run in the background** - they may take 1-5 minutes to complete
-- **Multiple entities can be analyzed at once** - use the "Analyze All" button on the Git page
-
-## Integration with Your Workflow
-
-Make this automatic part of your workflow:
-
-1. User asks for code changes
-2. You make the changes
-3. **[NEW STEP]** You run `codeyam verify` to verify the changes
-4. You present the changes to the user with the verification link
-
-This ensures the user can always see simulation results for your changes, building trust and providing visual confirmation that the changes work as expected.

package/codeyam-cli/templates/debug-command.md

@@ -1,125 +0,0 @@
-# Debug Scenario or Analysis
-
-When a user asks to debug a scenario or analysis (e.g., `/debug [ID]`), use this systematic process. The `codeyam debug` command auto-detects whether you've provided a scenario ID or analysis ID.
-
-## Step 1: Run Debug Command
-
-Set up the debug environment with the ID provided:
-
-```bash
-cd ../PROJECT_NAME
-codeyam debug ID
-```
-
-The command auto-detects whether the ID is a scenario or analysis.
-
-The output includes:
-
-1. **Project path**: `/tmp/codeyam/local-dev/{slug}/project`
-2. **Start command**: The exact `cd ... && pnpm dev` command to run
-3. **URL**: `http://localhost:3112/static/codeyam-sample`
-4. **Log path**: Where to watch for errors
-
----
-
-## Step 2: Manual Debugging in /tmp
-
-Work directly in the Tmp Project at `/tmp/codeyam/local-dev/{slug}/project`.
-
-### 2.1 Start the development server
-
-Copy the start command from the debug output and run it:
-
-```bash
-cd /tmp/codeyam/local-dev/{slug}/project && pnpm dev
-# Or the framework-specific command shown in the debug output
-```
-
-### 2.2 Verify the page loads with curl
-
-**CRITICAL: Server starting is NOT sufficient verification.**
-
-```bash
-curl -s http://localhost:3112/static/codeyam-sample | head -50
-```
-
-**What to look for:**
-
-- **Success**: HTML with `<div>` elements, no error messages
-- **Failure**: Look for `"statusCode":500` or `"err":` in the JSON
-
-### 2.3 Verification checklist
-
-Before declaring "it works", confirm ALL of these:
-
-- [ ] Server process started without crashing
-- [ ] `curl` returns clean HTML (no `statusCode:500` or error messages)
-- [ ] Browser shows the component rendering (not blank/error)
-- [ ] No errors in browser console (DevTools > Console)
-
-**If ANY of these fail, the bug is NOT fixed. Keep iterating.**
-
-### 2.4 Identify and fix the issue
-
-Common failure points:
-
-1. **Server fails to start**: JSON parse errors, missing dependencies, port in use
-2. **Page fails to compile**: Missing exports in mock files, import resolution failures
-3. **Page loads but component doesn't render**: ReferenceError, missing mock data
-
-**Fix the issue directly in the Tmp Project files.** Iterate until all verification checks pass.
-
----
-
-## Step 3: Document the Fix
-
-Once verified (all checklist items pass):
-
-1. **What file(s) did you edit?**
-2. **What was the change?**
-3. **Why was the original code wrong?**
-
-Categorize the fix:
-
-- **Mock content issue**: The generated mock had wrong exports or missing values
-- **Scenario file issue**: The scenario component file had incorrect structure
-- **Import rewriting issue**: An import was incorrectly rewritten or not rewritten
-- **Package.json corruption**: JSON files were incorrectly modified
-- **Missing dependency**: A required package wasn't installed
-
----
-
-## Step 4: Create a Failing Test (in CodeYam Repo)
-
-Write a test that fails without the fix:
-
-| Bug type                 | Test location                                                                      |
-| ------------------------ | ---------------------------------------------------------------------------------- |
-| Scenario file generation | `background/src/lib/virtualized/project/__tests__/writeScenarioComponents.test.ts` |
-| Universal mocks          | `background/src/lib/virtualized/project/__tests__/writeUniversalMocks.test.ts`     |
-| Mock generation          | `background/src/lib/virtualized/project/__tests__/constructMockCode.test.ts`       |
-| Entity analysis          | `packages/analyze/src/lib/files/__tests__/*.test.ts`                               |
-| Scope analysis           | `packages/ai/src/lib/astScopes/__tests__/*.test.ts`                                |
-
----
-
-## Step 5: Implement the Fix
-
-1. Edit the source file in the CodeYam Repo
-2. Run the test to confirm it passes
-3. Rebuild the CLI: `pnpm cli`
-4. Clear the cached project: `rm -rf /tmp/codeyam/local-dev/{slug}/project`
-5. Re-run debug: `codeyam debug ID`
-6. **Run the full verification checklist** - server starts, page loads, component renders
-
----
-
-## Key Source Files
-
-| Purpose               | File                                                                |
-| --------------------- | ------------------------------------------------------------------- |
-| Universal mocks       | `background/src/lib/virtualized/project/writeUniversalMocks.ts`     |
-| Scenario file writing | `background/src/lib/virtualized/project/writeScenarioComponents.ts` |
-| Mock code generation  | `background/src/lib/virtualized/project/constructMockCode.ts`       |
-| Entity analysis       | `packages/analyze/src/lib/files/analyzeEntity.ts`                   |
-| Data structure        | `packages/ai/src/lib/generateEntityDataStructure.ts`                |

package/packages/ai/src/lib/findMatchingAttribute.js

@@ -1,77 +0,0 @@
-import { normalizeKey } from "../../../../packages/utils/index.js";
-import { joinParenthesesAndArrays, splitOutsideParenthesesAndArrays, } from "./splitOutsideParentheses.js";
-function findEquivalent(path, equivalents) {
-    const pathParts = splitOutsideParenthesesAndArrays(path);
-    for (const equivalentKey in equivalents) {
-        const equivalentKeyParts = splitOutsideParenthesesAndArrays(equivalentKey);
-        if (equivalentKeyParts.some((part) => part.startsWith('signature['))) {
-            continue;
-        }
-        const relevantKey = joinParenthesesAndArrays(pathParts.slice(0, equivalentKeyParts.length));
-        if (equivalentKey === relevantKey) {
-            const equivalentValue = equivalents[equivalentKey];
-            return joinParenthesesAndArrays([
-                equivalentValue,
-                ...pathParts.slice(equivalentKeyParts.length),
-            ]);
-        }
-    }
-}
-function findReverseEquivalent(path, equivalents) {
-    const pathParts = splitOutsideParenthesesAndArrays(path);
-    for (const [equivalentKey, equivalentValue] of Object.entries(equivalents)) {
-        const equivalentKeyParts = splitOutsideParenthesesAndArrays(equivalentKey);
-        if (equivalentKeyParts.some((part) => part.startsWith('signature['))) {
-            continue;
-        }
-        const equivalentValueParts = splitOutsideParenthesesAndArrays(equivalentValue);
-        const relevantKey = joinParenthesesAndArrays(pathParts.slice(0, equivalentValueParts.length));
-        if (equivalentValue === relevantKey) {
-            return joinParenthesesAndArrays([
-                equivalentKey,
-                ...pathParts.slice(equivalentValueParts.length),
-            ]);
-        }
-    }
-}
-export default function findMatchingAttribute(attributePath, attributesList, equivalents) {
-    // console.log("CODEYAM DEBUG: findMatchingAttribute called with", JSON.stringify({
-    //   attributePath,
-    //   attributesList,
-    //   equivalents,
-    // }, null, 2));
-    const equivalent = findEquivalent(attributePath, equivalents);
-    const reverseEquivalent = findReverseEquivalent(attributePath, equivalents);
-    if (attributesList.includes(attributePath)) {
-        if (reverseEquivalent) {
-            return reverseEquivalent;
-        }
-        return attributePath;
-    }
-    else if (equivalent && attributesList.includes(equivalent)) {
-        return equivalent;
-    }
-    else {
-        const normalizedPath = normalizeKey(attributePath);
-        const matchingAttribute = attributesList.find((attr) => normalizeKey(attr) === normalizedPath);
-        // If no exact match find the attribute that matches the most characters starting from the beginning
-        if (!matchingAttribute) {
-            const options = attributesList;
-            const normalizedPathCharacters = normalizedPath.split('');
-            for (const attr of options) {
-                const attrCharacters = normalizeKey(attr).split('');
-                const matchLength = normalizedPathCharacters.findIndex((char, index) => char !== attrCharacters[index]);
-                if (matchLength !== -1) {
-                    const matchedPrefix = normalizedPathCharacters.slice(0, matchLength);
-                    if (matchedPrefix.length > 0) {
-                        return attr;
-                    }
-                }
-            }
-        }
-        if (matchingAttribute)
-            return matchingAttribute;
-        return null;
-    }
-}
-//# sourceMappingURL=findMatchingAttribute.js.map

package/packages/ai/src/lib/findMatchingAttribute.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"findMatchingAttribute.js","sourceRoot":"","sources":["../../../../../../packages/ai/src/lib/findMatchingAttribute.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,YAAY,EAAE,MAAM,gBAAgB,CAAC;AAC9C,OAAO,EACL,wBAAwB,EACxB,gCAAgC,GACjC,MAAM,2BAA2B,CAAC;AAEnC,SAAS,cAAc,CAAC,IAAY,EAAE,WAAmC;IACvE,MAAM,SAAS,GAAG,gCAAgC,CAAC,IAAI,CAAC,CAAC;IACzD,KAAK,MAAM,aAAa,IAAI,WAAW,EAAE,CAAC;QACxC,MAAM,kBAAkB,GAAG,gCAAgC,CAAC,aAAa,CAAC,CAAC;QAC3E,IAAI,kBAAkB,CAAC,IAAI,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,UAAU,CAAC,YAAY,CAAC,CAAC,EAAE,CAAC;YACrE,SAAS;QACX,CAAC;QAED,MAAM,WAAW,GAAG,wBAAwB,CAC1C,SAAS,CAAC,KAAK,CAAC,CAAC,EAAE,kBAAkB,CAAC,MAAM,CAAC,CAC9C,CAAC;QACF,IAAI,aAAa,KAAK,WAAW,EAAE,CAAC;YAClC,MAAM,eAAe,GAAG,WAAW,CAAC,aAAa,CAAC,CAAC;YACnD,OAAO,wBAAwB,CAAC;gBAC9B,eAAe;gBACf,GAAG,SAAS,CAAC,KAAK,CAAC,kBAAkB,CAAC,MAAM,CAAC;aAC9C,CAAC,CAAC;QACL,CAAC;IACH,CAAC;AACH,CAAC;AAED,SAAS,qBAAqB,CAC5B,IAAY,EACZ,WAAmC;IAEnC,MAAM,SAAS,GAAG,gCAAgC,CAAC,IAAI,CAAC,CAAC;IACzD,KAAK,MAAM,CAAC,aAAa,EAAE,eAAe,CAAC,IAAI,MAAM,CAAC,OAAO,CAAC,WAAW,CAAC,EAAE,CAAC;QAC3E,MAAM,kBAAkB,GAAG,gCAAgC,CAAC,aAAa,CAAC,CAAC;QAE3E,IAAI,kBAAkB,CAAC,IAAI,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,UAAU,CAAC,YAAY,CAAC,CAAC,EAAE,CAAC;YACrE,SAAS;QACX,CAAC;QAED,MAAM,oBAAoB,GACxB,gCAAgC,CAAC,eAAe,CAAC,CAAC;QAEpD,MAAM,WAAW,GAAG,wBAAwB,CAC1C,SAAS,CAAC,KAAK,CAAC,CAAC,EAAE,oBAAoB,CAAC,MAAM,CAAC,CAChD,CAAC;QACF,IAAI,eAAe,KAAK,WAAW,EAAE,CAAC;YACpC,OAAO,wBAAwB,CAAC;gBAC9B,aAAa;gBACb,GAAG,SAAS,CAAC,KAAK,CAAC,oBAAoB,CAAC,MAAM,CAAC;aAChD,CAAC,CAAC;QACL,CAAC;IACH,CAAC;AACH,CAAC;AAED,MAAM,CAAC,OAAO,UAAU,qBAAqB,CAC3C,aAAqB,EACrB,cAAwB,EACxB,WAAmC;IAEnC,mFAAmF;IACnF,mBAAmB;IACnB,oBAAoB;IACpB,iBAAiB;IACjB,gBAAgB;IAEhB,MAAM,UAAU,GAAG,cAAc,CAAC,aAAa,EAAE,WAAW,CAAC,CAAC;IAC9D,MAAM,iBAAiB,GAAG,qBAAqB,CAAC,aAAa,EAAE,WAAW,CAAC,CAAC;IAC5E,IAAI,cAAc,CAAC,QAAQ,CAAC,aAAa,CAAC,EAAE,CAAC;QAC3C,IAAI,iBAAiB,EAAE,CAAC;YACtB,OAAO,iBAAiB,CAAC;QAC3B,CAAC;QACD,OAAO,aAAa,CAAC;IACvB,CAAC;SAAM,IAAI,UAAU,IAAI,cAAc,CAAC,QAAQ,CAAC,UAAU,CAAC,EAAE,CAAC;QAC7D,OAAO,UAAU,CAAC;IACpB,CAAC;SAAM,CAAC;QACN,MAAM,cAAc,GAAG,YAAY,CAAC,aAAa,CAAC,CAAC;QACnD,MAAM,iBAAiB,GAAG,cAAc,CAAC,IAAI,CAC3C,CAAC,IAAI,EAAE,EAAE,CAAC,YAAY,CAAC,IAAI,CAAC,KAAK,cAAc,CAChD,CAAC;QAEF,oGAAoG;QACpG,IAAI,CAAC,iBAAiB,EAAE,CAAC;YACvB,MAAM,OAAO,GAAG,cAAc,CAAC;YAC/B,MAAM,wBAAwB,GAAG,cAAc,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC;YAC1D,KAAK,MAAM,IAAI,IAAI,OAAO,EAAE,CAAC;gBAC3B,MAAM,cAAc,GAAG,YAAY,CAAC,IAAI,CAAC,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC;gBACpD,MAAM,WAAW,GAAG,wBAAwB,CAAC,SAAS,CACpD,CAAC,IAAI,EAAE,KAAK,EAAE,EAAE,CAAC,IAAI,KAAK,cAAc,CAAC,KAAK,CAAC,CAChD,CAAC;gBACF,IAAI,WAAW,KAAK,CAAC,CAAC,EAAE,CAAC;oBACvB,MAAM,aAAa,GAAG,wBAAwB,CAAC,KAAK,CAAC,CAAC,EAAE,WAAW,CAAC,CAAC;oBACrE,IAAI,aAAa,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;wBAC7B,OAAO,IAAI,CAAC;oBACd,CAAC;gBACH,CAAC;YACH,CAAC;QACH,CAAC;QAED,IAAI,iBAAiB;YAAE,OAAO,iBAAiB,CAAC;QAChD,OAAO,IAAI,CAAC;IACd,CAAC;AACH,CAAC"}