@codeyam/codeyam-cli 0.1.0-staging.15d0f46 → 0.1.0-staging.1669d45

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

@@ -1,527 +0,0 @@
-# Debug Scenario or Analysis
-
-When a user asks to debug a scenario or analysis (e.g., `/debug-codeyam [ID]`), use this systematic process.
-
-## CRITICAL: Definition of Done
-
-**Debugging is NOT complete until one of these conditions is met:**
-
-1. **SUCCESS**: **ALL** scenarios have screenshot files that exist on disk and render correctly
-2. **ENGINE BUG**: You've identified a bug that CANNOT be fixed locally (requires CodeYam engine changes) AND you've documented the bug clearly
-
-**Common mistakes to avoid:**
-
-- Stopping after curl returns 200 (this only verifies one scenario loads, not that screenshots were captured)
-- Trusting database `screenshotPaths` without verifying files exist on disk
-- Fixing one scenario but not checking if other scenarios in the same analysis also need fixes
-- Declaring success when only some scenarios have screenshots
-
-If you fix an issue locally (database fix, universal mock, etc.), you MUST recapture screenshots AND verify ALL scenario screenshot files exist on disk.
-
-### Debug Flow Summary
-
-```
-┌─────────────────────────────────────────────────────────────────────┐
-│  Step 0: Query database for scenario status (DO THIS FIRST!)        │
-│          Check ALL scenarios in the analysis for failures           │
-│          Ask user: fix ONE scenario or ALL failing scenarios?       │
-│                    │                                                │
-│                    ▼                                                │
-│  Step 1: codeyam debug ID  (use scenario ID or analysis ID based   │
-│          on user's choice from Step 0)                              │
-│  Step 2: Identify error type                                        │
-│  Step 3-4: Fix (database edit or universal mock)                    │
-│  Step 5: Verify locally (curl returns 200)                          │
-│                    │                                                │
-│                    ▼                                                │
-│  Step 6: Recapture screenshots  ◄──────────── REQUIRED!             │
-│          codeyam recapture SCENARIO_ID                              │
-│                    │                                                │
-│                    ▼                                                │
-│  Verify ALL screenshot files exist on disk:                         │
-│  find .codeyam/captures -name "*.png" -path "*ANALYSIS_ID*"         │
-│                    │                                                │
-│         ┌─────────┴─────────┐                                       │
-│         ▼                   ▼                                       │
-│   ALL screenshots      Missing screenshots                          │
-│   exist on disk        or new errors                                │
-│         │                   │                                       │
-│         ▼                   ▼                                       │
-│      ✅ DONE         Go back to Step 2                              │
-│                      (fix ALL scenarios)                            │
-│                                                                     │
-│  Only skip Step 6 if bug CANNOT be fixed locally (engine bug)      │
-└─────────────────────────────────────────────────────────────────────┘
-```
-
----
-
-## CRITICAL: What You Can and Cannot Modify
-
-**NEVER modify the client's original source code.** The client code in `/tmp/codeyam/local-dev/{slug}/project` is a checkout of the user's repository. We do not fix bugs in their code.
-
-**You can ONLY modify:**
-
-- CodeYam-generated files (with `// This file is auto-generated by CodeYam` header)
-- Mock data files in `__codeyamMocks__/` directories
-- Data in the local SQLite database (to fix incorrect analysis data)
-- Universal mocks in `.codeyam/config.json`
-
----
-
-## Part 1: Debugging for All Projects
-
-### Step 0: Check for Other Failing Scenarios (MANDATORY FIRST STEP)
-
-**⚠️ DO NOT run `codeyam debug` yet!** First, query the database to check if other scenarios in the same analysis are also failing. This saves time by fixing all issues at once instead of debugging one scenario at a time.
-
-**You must complete this step and ask the user before proceeding to Step 1.**
-
-#### Query for Failing Scenarios
-
-```bash
-# First, get the analysis ID (if you have a scenario ID)
-sqlite3 .codeyam/db.sqlite3 "SELECT analysis_id FROM scenarios WHERE id = 'SCENARIO_ID'"
-
-# Then check ALL scenarios for that analysis
-sqlite3 .codeyam/db.sqlite3 "
-SELECT
-  s.id,
-  s.name,
-  json_extract(s.metadata, '$.screenshotPaths') as screenshots,
-  json_extract(a.status, '$.scenarios') as scenario_statuses
-FROM scenarios s
-JOIN analyses a ON s.analysis_id = a.id
-WHERE s.analysis_id = 'ANALYSIS_ID'
-"
-```
-
-#### Identify Failing Scenarios
-
-Look for scenarios that:
-
-1. Have no `screenshotPaths` (null or empty)
-2. Have `error` in their status
-3. Have `finishedAt` but no screenshot file on disk
-
-```bash
-# Check scenario status for errors
-sqlite3 .codeyam/db.sqlite3 "
-SELECT json_extract(status, '$.scenarios') FROM analyses WHERE id = 'ANALYSIS_ID'
-" | python3 -c "
-import json, sys
-scenarios = json.loads(sys.stdin.read())
-for s in scenarios:
-    status = '❌ ERROR' if s.get('error') else ('✅ OK' if s.get('finishedAt') else '⏳ PENDING')
-    print(f\"{status}: {s['name']}\")
-"
-```
-
-#### Ask User: Fix One or All?
-
-**If multiple scenarios are failing, ASK THE USER:**
-
-> I found X scenarios in this analysis, and Y of them appear to be failing:
->
-> - Scenario A: [error type]
-> - Scenario B: [error type]
-> - Scenario C: [error type]
->
-> Would you like me to:
->
-> 1. Fix just the requested scenario (SCENARIO_NAME)
-> 2. Fix ALL failing scenarios for this analysis
->
-> Fixing all at once is usually faster since they often share the same root cause (missing mock, bad data, etc.)
-
-**After the user responds, proceed to Step 1:**
-
-- **If fixing just one scenario:** Run `codeyam debug SCENARIO_ID` with the specific scenario ID
-- **If fixing all scenarios:** Run `codeyam debug ANALYSIS_ID` with the analysis ID
-
-**If the user chooses to fix all:**
-
-- Debug each failing scenario in sequence
-- Look for common patterns (same missing mock, same data issue)
-- Apply fixes that work across all scenarios when possible
-
----
-
-### Step 1: Run Debug Command
-
-**Only proceed to this step after completing Step 0 and getting the user's choice.**
-
-```bash
-# Use the scenario ID if fixing just one scenario
-codeyam debug SCENARIO_ID
-
-# OR use the analysis ID if fixing all scenarios
-codeyam debug ANALYSIS_ID
-```
-
-The command auto-detects whether the ID is a scenario or analysis. Output includes:
-
-1. **Project path**: `/tmp/codeyam/local-dev/{slug}/project`
-2. **Start command**: The exact command to run the dev server
-3. **URL**: Where to access the scenario
-4. **Log path**: Where to watch for errors
-
----
-
-### Step 2: Identify the Error Type
-
-Read the log file or error output to categorize the issue:
-
-| Error Type          | Symptoms                                         | Solution Path                          |
-| ------------------- | ------------------------------------------------ | -------------------------------------- |
-| **Runtime error**   | `TypeError`, `ReferenceError`, component crashes | Check mock data, may need database fix |
-| **Missing mock**    | `Cannot read property of undefined`              | Add universal mock                     |
-| **Wrong mock type** | `X is not a function` or `Cannot call X`         | Fix data in database                   |
-| **Import error**    | `Cannot find module`                             | Check universal mocks or entity name   |
-
----
-
-### Step 3: Database Debugging (Fix Analysis Data)
-
-Sometimes the analysis engine generates incorrect data. You can fix it directly in the database.
-
-#### Database Location
-
-The database is in the **project's `.codeyam/` directory**, not in `/tmp`:
-
-```
-{project-root}/.codeyam/db.sqlite3
-```
-
-For example: `/Users/you/myproject/.codeyam/db.sqlite3`
-
-#### Key Tables
-
-| Table       | Purpose             | Key Columns                              |
-| ----------- | ------------------- | ---------------------------------------- |
-| `entities`  | Detected entities   | `sha`, `name`, `file_path`, `metadata`   |
-| `analyses`  | Analysis results    | `id`, `entity_sha`, `status`, `metadata` |
-| `scenarios` | Generated scenarios | `id`, `analysis_id`, `name`, `metadata`  |
-
-#### Useful Queries
-
-**Find entity by name:**
-
-```bash
-sqlite3 .codeyam/db.sqlite3 \
-  "SELECT sha, name, file_path FROM entities WHERE name LIKE '%EntityName%'"
-```
-
-**Find analysis for entity:**
-
-```bash
-sqlite3 .codeyam/db.sqlite3 \
-  "SELECT id, status FROM analyses WHERE entity_sha = 'ENTITY_SHA'"
-```
-
-**View scenario mock data:**
-
-```bash
-sqlite3 .codeyam/db.sqlite3 \
-  "SELECT name, json_extract(metadata, '$.data.mockData') FROM scenarios WHERE analysis_id = 'ANALYSIS_ID'" | python3 -m json.tool
-```
-
-**List all keys in mockData:**
-
-```bash
-sqlite3 .codeyam/db.sqlite3 \
-  "SELECT json_each.key FROM scenarios, json_each(json_extract(metadata, '$.data.mockData')) WHERE id = 'SCENARIO_ID'"
-```
-
-#### Common Data Issues
-
-**1. Wrong mock type (function vs object)**
-
-The generated mock may treat a function as an object or vice versa. Check the generated scenario file in `/tmp/codeyam/local-dev/{slug}/project/` to see how the mock is structured. Compare it to how the code actually uses the value.
-
-**2. Malformed keys in mockData**
-
-Sometimes keys contain full function call expressions (with arguments) instead of simple identifiers. This causes a mismatch between how mockData is stored and how the mock code accesses it.
-
-```bash
-# View all keys - look for ones with complex parentheses and arguments
-sqlite3 .codeyam/db.sqlite3 \
-  "SELECT json_each.key FROM scenarios, json_each(json_extract(metadata, '$.data.mockData')) WHERE id = 'SCENARIO_ID'"
-```
-
-Example of problematic key:
-
-```
-"useQuery(undefined, { enabled: isSignedIn })"
-```
-
-The mock code may look for `["useQuery"]` or `["useQuery()"]` but the data is at `["useQuery(undefined, {...})"]`.
-
-**3. Missing mock data for a dependency**
-
-If a property access chain isn't mocked, the mock data may be missing or keyed incorrectly.
-
-#### Fixing Data
-
-**Update mockData in a scenario:**
-
-```bash
-# Get current metadata
-sqlite3 .codeyam/db.sqlite3 "SELECT metadata FROM scenarios WHERE id = 'SCENARIO_ID'"
-
-# Update a specific key in mockData (use json_set for simple changes)
-sqlite3 .codeyam/db.sqlite3 \
-  "UPDATE scenarios SET metadata = json_set(metadata, '\$.data.mockData.\"correctedKey\"', json('{\"fixed\": \"value\"}')) WHERE id = 'SCENARIO_ID'"
-```
-
-**For complex mockData fixes**, it's often easier to:
-
-1. Export the metadata to a file
-2. Edit the JSON with Python
-3. Update the database with the corrected JSON
-
-```bash
-# Export to file
-sqlite3 .codeyam/db.sqlite3 "SELECT metadata FROM scenarios WHERE id = 'SCENARIO_ID'" > /tmp/metadata.json
-
-# Edit with Python (add/modify keys as needed)
-cat /tmp/metadata.json | python3 -c "
-import json, sys
-data = json.loads(sys.stdin.read())
-# Example: Add a missing mock key
-data['data']['mockData']['myKey <- useHook'] = {'myKey': 'value'}
-print(json.dumps(data))
-" > /tmp/metadata_fixed.json
-
-# Update the database - use shell substitution with proper escaping
-# IMPORTANT: Do NOT use readfile() - it stores data as BLOB instead of TEXT
-sqlite3 .codeyam/db.sqlite3 "UPDATE scenarios SET metadata = '$(cat /tmp/metadata_fixed.json | sed \"s/'/''/g\")' WHERE id = 'SCENARIO_ID'"
-```
-
-> **⚠️ WARNING: Never use `readfile()`**
->
-> SQLite's `readfile()` function returns a BLOB, not TEXT. This will corrupt the metadata
-> and cause "JSON cannot hold BLOB values" errors. Always use shell substitution with
-> `$(cat file | sed "s/'/''/g")` to properly escape single quotes and insert as TEXT.
-
-**After fixing the database, regenerate scenario files by re-running analysis:**
-
-```bash
-codeyam analyze --entity EntityName path/to/file.tsx
-```
-
-Or, if you only need to regenerate the scenario files from existing data, you may be able to trigger a recapture from the CodeYam dashboard.
-
----
-
-### Step 4: Universal Mocks (Infrastructure Dependencies)
-
-For errors caused by infrastructure code that doesn't work in simulation (database clients, filesystem, etc.), add universal mocks.
-
-#### When to Use Universal Mocks
-
-Only use for functions that:
-
-1. Are called by MANY entities across ALL scenarios
-2. Don't work in simulation (need real database, filesystem, etc.)
-3. Return simple, scenario-independent values
-
-#### Adding a Universal Mock
-
-Edit `.codeyam/config.json`:
-
-```json
-{
-  "universalMocks": [
-    {
-      "entityName": "getProjectRoot",
-      "filePath": "lib/state.ts",
-      "content": "export function getProjectRoot() { return '/mock/project/root'; }"
-    }
-  ]
-}
-```
-
-Then rebuild: `pnpm build` (or your build command)
-
----
-
-### Step 5: Verify the Fix Locally
-
-After making changes:
-
-1. **Re-run `codeyam debug ID`** to regenerate scenario files with the updated data
-2. **Restart the dev server** in `/tmp/codeyam/local-dev/{slug}/project`
-3. **Curl the URL** to check for errors:
-   ```bash
-   curl -s http://localhost:3112/static/... | head -50
-   ```
-4. **Check for 200 response** (no `statusCode:500`)
-
-**Quick verification checklist:**
-
-- [ ] Server starts without crashing
-- [ ] `curl` returns HTML (no `statusCode:500`)
-- [ ] No runtime errors in server logs
-
-**If verification fails:** Go back to Step 2 and debug the next error.
-
-**If verification passes:** Proceed to Step 6 to recapture screenshots.
-
----
-
-### Step 6: Recapture Screenshots (REQUIRED)
-
-**This step is MANDATORY after any local fix.** A 200 response is not sufficient - you must recapture screenshots to confirm the scenario renders correctly end-to-end.
-
-#### Option A: Via Recapture Command (Recommended)
-
-Use the `codeyam recapture` command with the scenario ID:
-
-```bash
-codeyam recapture SCENARIO_ID
-```
-
-This will:
-
-1. Reset the scenario's capture status
-2. Re-run the screenshot capture
-3. Save the new screenshot to `.codeyam/captures/`
-
-**To recapture multiple scenarios:** Run `codeyam recapture` for each failing scenario ID.
-
-#### Option B: Via Web Dashboard
-
-1. Open the CodeYam dashboard at `http://localhost:3111`
-2. Navigate to the analysis or scenario
-3. Click "Recapture" or trigger a new capture for the scenario
-
-#### Option C: Via Re-running Analysis
-
-If you need to regenerate everything from scratch:
-
-```bash
-codeyam analyze --entity EntityName path/to/file.tsx
-```
-
-This will re-analyze the entity and capture new screenshots.
-
-**After capture completes:**
-
-1. **Verify ALL scenarios have screenshots** - not just some:
-
-   ```bash
-   # Check which scenarios have screenshot paths in metadata
-   sqlite3 .codeyam/db.sqlite3 "SELECT name, json_extract(metadata, '$.screenshotPaths') FROM scenarios WHERE analysis_id = 'ANALYSIS_ID'"
-
-   # IMPORTANT: Also verify the files actually exist on disk!
-   find .codeyam/captures -name "*.png" -path "*ANALYSIS_ID*"
-   ```
-
-2. If ANY scenario is missing screenshots, investigate why and fix it
-3. If screenshots exist, view them to confirm the components render correctly
-4. If capture failed with errors, go back to Step 2
-
-**CRITICAL: Do not trust database metadata alone.** A scenario may have a `screenshotPaths` value in the database but the file may not actually exist. Always verify files exist on disk.
-
-**Debugging is complete ONLY when ALL scenarios have screenshot files that exist and render correctly.**
-
----
-
-### Step 7: Document the Bug (for Engine Fixes)
-
-After fixing the data locally, document the issue so CodeYam can fix the underlying bug in the analysis engine.
-
-**Create a bug report with:**
-
-1. What the incorrect data looked like (copy the relevant JSON)
-2. What it should have been
-3. How you fixed it (the SQL command or manual edit)
-4. Any patterns you noticed (e.g., "happens with property access chains")
-5. The entity name and file path
-
-**For CodeYam project:** Create an issue or note in the codebase describing the bug.
-
-**For client projects:** Share the bug report with the CodeYam team so they can fix the analysis engine.
-
----
-
-### When to Stop WITHOUT Recapturing
-
-Only skip screenshot recapture if you've identified a bug that **cannot be fixed locally**:
-
-- The bug is in the CodeYam analysis engine itself
-- Fixing it requires changes to CodeYam source code (not just database/config changes)
-- You've documented the bug clearly in Step 7
-
-In this case, report the bug and stop. The user will need to wait for an engine fix.
-
----
-
-## Part 2: CodeYam Engine Debugging
-
-**This section is only relevant when working on the CodeYam project itself.**
-
-If you're debugging a client project, you can stop at Part 1. Report the bug and move on.
-
-### Identifying Engine Bugs
-
-When the error is in how CodeYam generates data or mocks (not in client code), you need to fix the engine.
-
-Signs of an engine bug:
-
-- Same pattern fails across multiple projects
-- Mock data structure doesn't match code patterns
-- Generated mock code has wrong syntax
-
-### Key Source Files
-
-| Purpose                  | File                                                                |
-| ------------------------ | ------------------------------------------------------------------- |
-| Scenario file generation | `background/src/lib/virtualized/project/writeScenarioComponents.ts` |
-| Mock code construction   | `packages/analyze/src/lib/files/analyze/constructMockCode.ts`       |
-| Data structure merging   | `background/src/lib/analyze/mergeDataStructure.ts`                  |
-| Entity analysis          | `packages/analyze/src/lib/files/analyzeEntity.ts`                   |
-
-### Debugging Workflow
-
-**1. Write a failing test first**
-
-| Bug type            | Test location                                                                      |
-| ------------------- | ---------------------------------------------------------------------------------- |
-| Scenario generation | `background/src/lib/virtualized/project/__tests__/writeScenarioComponents.test.ts` |
-| Mock generation     | `packages/analyze/src/lib/files/analyze/__tests__/constructMockCode.test.ts`       |
-| Entity analysis     | `packages/analyze/src/lib/files/__tests__/*.test.ts`                               |
-
-**2. Add debug logging to trace the issue**
-
-```typescript
-console.log('=== DEBUG ===');
-console.log('input:', JSON.stringify(input, null, 2));
-console.log('output:', result);
-```
-
-**3. Run tests**
-
-```bash
-pnpm test:unit -- --grep "relevant test pattern"
-```
-
-**4. Implement the fix**
-
-Fix the source file, ensure tests pass, then:
-
-```bash
-pnpm cli                                    # Rebuild CLI
-rm -rf /tmp/codeyam/local-dev/{slug}/project  # Clear cache
-codeyam debug ID                            # Re-test
-```
-
-### Common Bug Patterns
-
-| Pattern                      | Symptom                     | Likely Location                                   |
-| ---------------------------- | --------------------------- | ------------------------------------------------- |
-| Object vs function confusion | `X is not a function`       | `constructMockCode.ts` - entityType handling      |
-| Variable-qualified keys      | Wrong variable name in mock | `writeScenarioComponents.ts` - key parsing        |
-| Schema inference             | Wrong mock structure        | `mergeDataStructure.ts`                           |
-| Property chain issues        | Nested property undefined   | `constructMockCode.ts` - nested object generation |

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"}