crewly 1.20.153 → 1.20.154

package/config/task_starters/prompts/e2e_test_plan_step2_run_tests.md

@@ -1,240 +0,0 @@
-**E2E TEST PLAN GENERATION - STEP 2**
-
-**Role:** You are a Senior QA Architect & TestOps engineer. Using the artifacts from **STEP 1** (evaluation scripts under `{PROJECT_PATH}/e2e_tests/` and `e2e_evaluation_instructions.md`) and the plan from **STEP 2**, **execute** the evaluation scripts to cover all user journeys, capture results/artifacts, and produce an evidence-based report plus improvement tasks. Show your reasoning **only** via explicit criteria, tables, and bullet points (no hidden chain-of-thought).
-
-**Authoritative Inputs:**
-
--   **Project:** `{PROJECT_NAME}`
--   **Repo Path:** `{PROJECT_PATH}`
--   **Specs:** `{PROJECT_PATH}/.crewly/specs/` (incl. `project.md`, user journeys)
--   **Evaluation Harness:** `{PROJECT_PATH}/e2e_tests/` (scripts + `e2e_evaluation_instructions.md`)
--   **Envs/Secrets:** `.env` / CI variables referenced by the harness
-
-**Deliverables (must create all):**
-
-1.  `{PROJECT_PATH}/e2e_tests/e2e_evaluation_report.md`
-2.  `{PROJECT_PATH}/README.md` — **only if not exists**; include “How to run E2E evaluation” instructions
-3.  Improvement tasks under `{PROJECT_PATH}/.crewly/tasks/m*_e2e_tests_improvement/` with subfolders: `open/`, `in_progress/`, `blocked/`, `done/` (use the next milestone, e.g., `m1_e2e_tests_improvement`)
-
-**Hard Rules:**
-
--   **Execute** the scripts exactly as described by `e2e_evaluation_instructions.md`. If any command is missing/ambiguous, use safe defaults documented below and mark **Assumptions**.
--   Cover **all** user journeys defined in specs (primary + key alternates). If a journey has no script, record as **Missing Coverage**.
--   For every failure, store evidence (logs, traces, screenshots, videos) and add a **Finding** with **Expect vs. Actual**; create a matching **improvement task**.
--   Never overwrite existing README content; only append or update the E2E evaluation instruction.
-
----
-
-## Execution Plan
-
-### 1\) Pre-Run Validation
-
--   **Clean Slate:** Remove `{PROJECT_PATH}/e2e_tests/e2e_evaluation_report.md` if it exists to ensure a fresh report.
--   Verify presence of `{PROJECT_PATH}/e2e_tests/e2e_evaluation_instructions.md` and at least one `*_e2e_tests.*` script.
--   Load `.env` if present; resolve required envs from the instructions (`BASE_URL`, `API_BASE_URL`, credentials, `BROWSERS`, etc.).
--   Ensure services are reachable (e.g., `curl $BASE_URL/health` or framework health checks). If not, mark **Env Blocker** and continue to next runnable area.
-
-### 2\) Script Discovery & Command Matrix
-
-Read `e2e_evaluation_instructions.md`. When unspecified, use these **fallback commands**:
-
-| Script Pattern                         | Runner (fallback)                                  | Notes                                          |
-| -------------------------------------- | -------------------------------------------------- | ---------------------------------------------- |
-| `*.ts`                                 | `npx ts-node <script>`                             | Playwright/Web/API/desktop/terminal TS harness |
-| `*.js`                                 | `node <script>`                                    | Node harness                                   |
-| `*.py`                                 | `pytest <script>` **or** `python <script>`         | Prefer pytest if tests present                 |
-| `*.java`                               | `mvn -Dtest=<Class>#<method> test` / `gradle test` | Selenium/Playwright-Java                       |
-| Mobile wrapper (`mobile_e2e_tests.ts`) | `node <script>`                                    | Delegates to Appium/WDIO per env               |
-
-> Run **sequentially** by default; enable parallelism only if the harness supports it and artifacts remain traceable.
-
-### 3\) Run & Capture
-
--   For each script:
-    -   Start with **headless** (unless instructions say otherwise); set timeouts from instructions or sensible defaults.
-    -   Capture **stdout/stderr**, **exit code**, and collect artifacts to `e2e_tests/artifacts/`.
-    -   If JUnit/Allure/HTML reports are produced, index their paths for the report.
--   Map each executed check to **User Journey IDs** from specs; anything unmapped → flag and note.
-
-### 4\) Post-Run Analysis
-
--   Classify results per journey: **Pass / Fail / Skipped / Missing**.
--   For **Fail**: extract minimal reproducible evidence (error message, step name, screenshot/trace path) and fill **Expect vs. Actual**.
--   **Specifically identify UI/UX failures:**
-    -   **Visual Regression:** Look for artifacts like `*-diff.png` images or specific failure logs from the test runner (e.g., "Error: Screenshot comparison failed").
-    -   **Accessibility:** Look for test failures that output lists of violations (e.g., from Axe-core).
--   For **Missing**: confirm via specs/code that no script exists; propose coverage task.
-
----
-
-## Output 1 — `{PROJECT_PATH}/e2e_tests/e2e_evaluation_report.md`
-
-Populate exactly with this structure:
-
-```markdown
-# E2E Evaluation Report — {PROJECT_NAME}
-
-**Path:** {PROJECT_PATH}/e2e_tests/e2e_evaluation_report.md
-**Prepared By:** Senior QA Architect (Gemini)
-**Date:** <<YYYY-MM-DD>>
-
-## 0) Executive Summary
-
--   **Overall Status:** <<Green | Yellow | Red>> — rationale
--   **Scope:** Functional, **Visual, and Accessibility** checks across all user journeys from specs; scripts executed from `e2e_tests/`
--   **Environment:** <<env name/URL, versions>>
--   **Pass Rate:** <<x%>> (<<passed>> / <<total>>)
--   **Top Risks:** <<3–5 bullets, including any major visual regressions or critical a11y blockers>>
-
-## 1) Method & Evidence
-
--   **Instructions Used:** `e2e_tests/e2e_evaluation_instructions.md`
--   **Scripts Executed:** <<list with command used and exit code>>
--   **Artifacts Index:** <<paths to traces/screenshots/reports>>
--   **Assumptions:** <<only if commands/envs were inferred>>
-
-## 2) Results by User Journey
-
-| Journey ID  | Title    | Status                    |  Duration | Artifacts | Notes                                                           |
-| ----------- | -------- | ------------------------- | --------: | --------- | --------------------------------------------------------------- |
-| E2E-XXX-001 | <<name>> | Pass/Fail/Skipped/Missing | <<mm:ss>> | <<links>> | <<summary; **note if failure is Visual, A11y, or Functional**>> |
-
-## 3) Findings — Expect vs. Actual (Failures & Issues)
-
-### Finding F-00X — <<Concise Title>>
-
--   **Journey/Area:** <<ID & name>>
--   **Finding Type: Functional | Visual Regression | Accessibility**
--   **Expectation (specs):** <<what should happen, e.g., "UI matches baseline", "No WCAG violations">>
--   **Actual (run):** <<what happened. **For visual, describe the change. For a11y, list top 1-3 violations.**>>
--   **Impact:** <<user/system impact>>
--   **Evidence:** <<log excerpt + artifact paths to **diff images** or **full a11y reports**>>
--   **Root Cause Hypothesis:** <<brief>>
--   **Proposed Fix:** <<one-liner, e.g., "Fix CSS bug" or "**Approve visual change and update baseline**">>
--   **Linked Task:** `./../.crewly/tasks/m*/e2e_tests_improvement/open/IMPR-00X_<slug>.md`
-
-> Repeat for each failure or defect category (env/config, data, flakiness, docs).
-
-## 4) Coverage Gaps
-
-| Journey ID  | Expected Coverage | Actual  | Gap  | Recommendation          |
-| ----------- | ----------------- | ------- | ---- | ----------------------- |
-| E2E-YYY-002 | smoke+negative    | Missing | High | Add spec + data seeding |
-
-## 5) CI/CD & Data Observations
-
--   **CI Hooks:** <<present/absent, duration, sharding, retries>>
--   **Data/Fixtures:** <<seeding/masking status>>
--   **Env Parity:** <<dev/stage/prod differences>>
-
-## 6) Recommendations & Next Steps
-
--   **Immediate (≤ 1 sprint):** <<quick wins>>
--   **Near-Term:** <<architecture/coverage>>
--   **Longer-Term:** <<stability/device coverage>>
-
-## 7) Appendices
-
--   **Raw Logs Index**, **Assumptions**, **References (specs & configs)**
-```
-
----
-
-## Output 2 — `{PROJECT_PATH}/README.md`
-
-If a README does **not** exist, create one with a minimal project header and this section (otherwise update it):
-
-```markdown
-## E2E Evaluation — How to Run
-
-Scripts live in `e2e_tests/`. See `e2e_tests/e2e_evaluation_instructions.md` for required env vars and platform specifics.
-
-### Quick Commands (examples; prefer the instructions file if they differ)
-
--   Run all tests: `npx ts-node e2e_tests/web_e2e_tests.ts`
--   **Update visual baselines (after an intentional UI change):** `npx playwright test --update-snapshots`
-
-Artifacts (traces/screenshots/videos) are written to `e2e_tests/artifacts/`.
-```
-
-> If README exists, **ONLY modify the E2E evaluation part**.
-
----
-
-## Output 3 — Improvement Tasks
-
-Create a new milestone folder if none exists:
-`{PROJECT_PATH}/.crewly/tasks/m1_e2e_tests_improvement/` with subfolders `open/`, `in_progress/`, `blocked/`, `done/`.
-
-For **each Finding (F-00X)** in the report, create a matching task in `open/`:
-
-**Task file:** `{PROJECT_PATH}/.crewly/tasks/m1_e2e_tests_improvement/open/IMPR-00X_<kebab-title>.md`
-
-**Template (fill completely):**
-
-```markdown
-# IMPR-00X — <Concise Title>
-
-**Status:** Open
-**Severity:** P0 | P1 | P2 | P3
-**Category:** Missing Coverage | Functional Failure | **Visual Regression** | **Accessibility** | Flakiness | Env/Config | CI/CD | Data/Fixtures | Docs/DevEx
-**Related Finding:** F-00X (see `e2e_tests/e2e_evaluation_report.md`)
-**User Journey IDs:** E2E-...
-
-## Context
-
--   **Expectation (specs):** <quote/summary>
--   **Actual (run):** <error / behavior>
--   **Impact:** <user/system impact>
-
-## Repro Steps
-
-1.  Command used: `<exact command>`
-2.  Env vars: `<list>`
-3.  Preconditions: `<seed/state>`
-4.  Steps to observe failure
-
-## Detailed Fix Plan
-
--   [ ] Code/config changes (paths/files)
--   [ ] Test data/fixtures updates
--   [ ] Update visual baseline screenshots (if change is intentional)
--   [ ] Test spec(s) to add/update
--   [ ] CI: retries/sharding/timeout changes
--   [ ] Owner + estimate
-
-## Acceptance Criteria
-
--   [ ] Passing run for journey `<ID>` with artifacts attached
--   [ ] No regressions in related journeys
--   [ ] CI green on PR & nightly
-
-## Dependencies
-
--   `<blocked by / requires>`
-
-## References
-
--   Spec: `{PROJECT_PATH}/.crewly/specs/<file>.md`
--   Artifacts: `e2e_tests/artifacts/<files>`
-```
-
-> If **no failures** occurred but gaps exist, create **Missing Coverage** tasks accordingly.
-
----
-
-## Safe Defaults & Edge Handling
-
--   **Timeouts:** Default 60s per navigation/API call unless instructions specify otherwise.
--   **Headless:** `HEADLESS=true` by default; flip to debug locally.
--   **Retries:** If supported, `retries=1` for CI; always collect traces on retry.
--   **Secrets:** Never print secrets to logs; rely on CI masked vars.
--   **Partial Runs:** If a script fails early, continue with remaining scripts and record partial coverage.
-
----
-
-## What You Return
-
--   The **full content** for `e2e_evaluation_report.md`.
--   The **updated README.md** with instructions for user to start testing.
--   One **task file per finding** in the milestone folder with detailed fix plans.

package/config/templates/customer-loyalty-team.json

@@ -1,44 +0,0 @@
-{
-  "id": "customer-loyalty-team",
-  "name": "Customer Loyalty & Success Team",
-  "description": "Premium support team focused on turning tickets into loyalty. Uses radical empathy and proactive retention strategies.",
-  "version": "1.0.0",
-  "category": "support",
-  "targetVertical": "SaaS / Agencies",
-  "tags": ["support", "success", "loyalty", "retention"],
-  "hierarchical": true,
-  "roles": [
-    {
-      "role": "success-manager",
-      "label": "Customer Success Lead",
-      "expertId": "empathetic-resolver",
-      "domainSOP": "customer-onboarding",
-      "defaultName": "Hope",
-      "count": 1,
-      "hierarchyLevel": 1,
-      "canDelegate": true,
-      "defaultSkills": [
-        "delegate-task",
-        "verify-output",
-        "sentiment-analysis",
-        "retention-strategy",
-        "report-status"
-      ]
-    },
-    {
-      "role": "support-agent",
-      "label": "Support Specialist",
-      "defaultName": "Sam",
-      "count": 2,
-      "hierarchyLevel": 2,
-      "reportsTo": "success-manager",
-      "defaultSkills": [
-        "ticket-resolution",
-        "brand-voice-alignment",
-        "complete-task",
-        "request-help"
-      ]
-    }
-  ],
-  "mission": "Provide world-class support that reduces churn and increases customer lifetime value."
-}

package/config/templates/dtc-viral-content-team.json

@@ -1,58 +0,0 @@
-{
-  "id": "dtc-viral-content-team",
-  "name": "DTC Viral Content Team",
-  "description": "High-conversion content team for solopreneurs and Shopify brands. Focused on viral hooks, scroll-stopping creative, and performance data.",
-  "version": "1.0.0",
-  "category": "marketing",
-  "targetVertical": "E-commerce / DTC",
-  "tags": ["dtc", "viral", "content", "shopify", "tiktok"],
-  "hierarchical": true,
-  "roles": [
-    {
-      "role": "content-lead",
-      "label": "Content Strategy Lead",
-      "expertId": "viral-alchemist",
-      "domainSOP": "content-production-pipeline",
-      "defaultName": "Vee",
-      "count": 1,
-      "hierarchyLevel": 1,
-      "canDelegate": true,
-      "defaultSkills": [
-        "decompose-goal",
-        "delegate-task",
-        "verify-output",
-        "content-calendar",
-        "report-status"
-      ]
-    },
-    {
-      "role": "writer",
-      "label": "Viral Copywriter",
-      "defaultName": "Ace",
-      "count": 1,
-      "hierarchyLevel": 2,
-      "reportsTo": "content-lead",
-      "defaultSkills": [
-        "social-media-post",
-        "conversion-copy",
-        "complete-task",
-        "request-help"
-      ]
-    },
-    {
-      "role": "creator",
-      "label": "UGC Content Creator",
-      "defaultName": "Coco",
-      "count": 1,
-      "hierarchyLevel": 2,
-      "reportsTo": "content-lead",
-      "defaultSkills": [
-        "image-generation",
-        "video-scripting",
-        "complete-task",
-        "request-help"
-      ]
-    }
-  ],
-  "mission": "Generate high-conversion viral content that drives traffic and sales for DTC brands."
-}

package/config/templates/expert-innovation-team.json

@@ -1,60 +0,0 @@
-{
-  "id": "expert-innovation-team",
-  "name": "Expert Innovation Team (Pro)",
-  "description": "High-performance team guided by the world's greatest thinkers. Combines visionary design with radical engineering first principles.",
-  "version": "1.0.0",
-  "category": "innovation",
-  "targetVertical": "R&D / New Product Development",
-  "tags": ["innovation", "strategy", "engineering", "first-principles"],
-  "hierarchical": true,
-  "roles": [
-    {
-      "role": "strategist",
-      "label": "Visionary Strategist",
-      "expertId": "steve-jobs",
-      "domainSOP": "innovation-strategy",
-      "defaultName": "Steve",
-      "count": 1,
-      "hierarchyLevel": 1,
-      "canDelegate": true,
-      "defaultSkills": [
-        "decompose-goal",
-        "delegate-task",
-        "design-review",
-        "market-analysis",
-        "report-status"
-      ]
-    },
-    {
-      "role": "engineer",
-      "label": "Radical Engineer",
-      "expertId": "elon-musk",
-      "reportsTo": "strategist",
-      "defaultName": "Elon",
-      "count": 1,
-      "hierarchyLevel": 2,
-      "defaultSkills": [
-        "first-principles-analysis",
-        "technical-optimization",
-        "automation-scripting",
-        "complete-task"
-      ]
-    },
-    {
-      "role": "allocator",
-      "label": "Capital Allocator",
-      "expertId": "charlie-munger",
-      "reportsTo": "strategist",
-      "defaultName": "Charlie",
-      "count": 1,
-      "hierarchyLevel": 2,
-      "defaultSkills": [
-        "risk-assessment",
-        "mental-model-audit",
-        "inverted-problem-solving",
-        "complete-task"
-      ]
-    }
-  ],
-  "mission": "Apply world-class mental models to solve impossible problems and build insanely great products."
-}

package/config/templates/pragmatic-mvp-dev-team.json

@@ -1,58 +0,0 @@
-{
-  "id": "pragmatic-mvp-dev-team",
-  "name": "Pragmatic MVP Development Team",
-  "description": "Lean development team for founders building MVPs. Prioritizes maintainability, speed, and 'YAGNI' principles.",
-  "version": "1.0.0",
-  "category": "development",
-  "targetVertical": "Startup MVP",
-  "tags": ["mvp", "lean", "startup", "dev"],
-  "hierarchical": true,
-  "roles": [
-    {
-      "role": "architect",
-      "label": "Pragmatic Architect",
-      "expertId": "pragmatic-architect",
-      "defaultName": "Archie",
-      "count": 1,
-      "hierarchyLevel": 1,
-      "canDelegate": true,
-      "defaultSkills": [
-        "decompose-goal",
-        "delegate-task",
-        "architecture-review",
-        "tech-stack-selection",
-        "report-status"
-      ]
-    },
-    {
-      "role": "fullstack",
-      "label": "Fullstack Developer",
-      "defaultName": "Devin",
-      "count": 1,
-      "hierarchyLevel": 2,
-      "reportsTo": "architect",
-      "defaultSkills": [
-        "frontend-dev",
-        "backend-dev",
-        "unit-testing",
-        "complete-task",
-        "request-help"
-      ]
-    },
-    {
-      "role": "qa",
-      "label": "QA & Automation",
-      "defaultName": "Quinn",
-      "count": 1,
-      "hierarchyLevel": 2,
-      "reportsTo": "architect",
-      "defaultSkills": [
-        "e2e-testing",
-        "bug-reporting",
-        "performance-audit",
-        "complete-task"
-      ]
-    }
-  ],
-  "mission": "Build a robust, scalable MVP quickly by focusing only on what matters most."
-}

package/config/templates/pro-sops/norms/content-production-pipeline.md

@@ -1,39 +0,0 @@
-# SOP: Content Production Pipeline
-
-This SOP defines the end-to-end workflow for AI-driven content creation, from trend analysis to final distribution.
-
-## Mandatory Procedures
-
-### 1. Trend & Insight Gathering
-- Use the `trend-monitor` skill to identify top 3 viral hooks in the target niche (e.g., AI, SaaS, E-commerce).
-- Verify hook relevance against current Brand Voice guidelines.
-
-### 2. Briefing & Strategy
-- Generate a platform-optimized brief using the `content-writer` skill.
-- For Xiaohongshu (XHS), ensure the "Raw-is-Real" strategy is explicitly mentioned in the brief.
-
-### 3. Drafting & Optimization
-- Produce initial draft (600-1200 words for long-form posts).
-- Include heavy emoji usage as per platform conventions (especially for XHS/TikTok).
-- Perform "AI-Cliche Check": Remove terms like "Unlock," "Revolutionize," or "Digital Landscape."
-
-### 4. Visual Asset Alignment
-- Ensure visuals (stills or Remotion videos) match the specific UI improvement points mentioned in the text.
-- High-contrast covers are mandatory for XHS posts.
-
-### 5. Multi-Layer Quality Review
-- **AI Pass**: Verify tone, forbidden words, and hashtag relevance.
-- **Human Pass**: Submit to the user/TL via Slack for final sign-off before publication.
-
-### 6. Scheduling & Distribution
-- Post during the identified "Golden Hours" (specific to the platform's region).
-- Monitor engagement for the first 60 minutes and trigger auto-replies to top-tier comments.
-
-## Quality Gate (Pass/Fail)
-- **Approved**: Passes all 6 phases and receives Human HITL sign-off.
-- **Revise**: Missing specific hooks or fails AI-Cliche check.
-- **Reject**: Fails brand voice alignment or lacks clear CTA.
-
-## Escalation Rules
-- Escalate to Team Lead if a post receives >5% negative engagement in the first 2 hours.
-- Escalate to Orchestrator if visual generation skills (Remotion/Nano-Banana) fail more than twice.

package/config/templates/pro-sops/norms/customer-onboarding-sop.md

@@ -1,40 +0,0 @@
-# SOP: Customer Onboarding (Crewly Pro)
-
-This SOP outlines the standardized steps to onboard new Crewly Pro customers, ensuring a seamless transition from sales to active operations.
-
-## Mandatory Procedures
-
-### 1. Initiation & Welcome (T+0 Hours)
-- Auto-generate and send the "Welcome Kit" via email/Slack.
-- Synchronize with the customer's calendar to propose a Kickoff call.
-
-### 2. Discovery & Brand Alignment (T+24 Hours)
-- Trigger the `brand-onboarding` questionnaire to collect business objectives and tone preferences.
-- Perform a manual audit of the customer's existing social handles and content assets.
-
-### 3. Team & Infrastructure Provisioning (T+48 Hours)
-- Setup a dedicated Crewly project directory.
-- Deploy the "Expert Innovation Team" or "AI Video Social Team" templates based on the customer's tier.
-- Configure API keys and Slack integrations for the new workspace.
-
-### 4. First Value Delivery (T+7 Days)
-- Deliver the first "Quick Win" (e.g., a 7-day content roadmap or initial competitor audit).
-- Request feedback on the initial output quality via the `customer-feedback-analyzer`.
-
-### 5. Transition to Steady-State (T+14 Days)
-- Lock the 90-day Roadmap (OKR alignment).
-- Establish recurring weekly status meetings (automated through Orchestrator).
-
-## Quality Checks
-1. **Response Time**: Onboarding initiation must happen within 4 hours of contract signing.
-2. **Data Integrity**: All customer credentials must be stored in encrypted vaults.
-3. **Engagement**: Customer must have completed the `brand-onboarding` by Day 3.
-
-## Quality Score
-- **Seamless**: 100% completion of Day 1-7 milestones within the first week.
-- **Delayed**: Day 3 milestones completed after Day 5 (Requires TL check).
-- **At Risk**: No customer response by Day 7 (Escalate to Sales/Victor).
-
-## Escalation Rules
-- Escalate to Sales (Steve) if onboarding data contradicts initial contract terms.
-- Escalate to TL (Victor) if provisioning errors block the team setup for >24h.

package/dist/backend/backend/src/controllers/task-management/tickets.controller.d.ts

@@ -1,13 +0,0 @@
-import { Request, Response } from 'express';
-import type { ApiContext } from '../types.js';
-export declare function createTicket(this: ApiContext, req: Request, res: Response): Promise<void>;
-export declare function getTickets(this: ApiContext, req: Request, res: Response): Promise<void>;
-export declare function getTicket(this: ApiContext, req: Request, res: Response): Promise<void>;
-export declare function updateTicket(this: ApiContext, req: Request, res: Response): Promise<void>;
-export declare function deleteTicket(this: ApiContext, req: Request, res: Response): Promise<void>;
-export declare function addSubtask(this: ApiContext, req: Request, res: Response): Promise<void>;
-export declare function toggleSubtask(this: ApiContext, req: Request, res: Response): Promise<void>;
-export declare function createTicketTemplate(this: ApiContext, req: Request, res: Response): Promise<void>;
-export declare function getTicketTemplates(this: ApiContext, req: Request, res: Response): Promise<void>;
-export declare function getTicketTemplate(this: ApiContext, req: Request, res: Response): Promise<void>;
-//# sourceMappingURL=tickets.controller.d.ts.map

package/dist/backend/backend/src/controllers/task-management/tickets.controller.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"tickets.controller.d.ts","sourceRoot":"","sources":["../../../../../../backend/src/controllers/task-management/tickets.controller.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,QAAQ,EAAE,MAAM,SAAS,CAAC;AAC5C,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,aAAa,CAAC;AAO9C,wBAAsB,YAAY,CAAC,IAAI,EAAE,UAAU,EAAE,GAAG,EAAE,OAAO,EAAE,GAAG,EAAE,QAAQ,GAAG,OAAO,CAAC,IAAI,CAAC,CAc/F;AAED,wBAAsB,UAAU,CAAC,IAAI,EAAE,UAAU,EAAE,GAAG,EAAE,OAAO,EAAE,GAAG,EAAE,QAAQ,GAAG,OAAO,CAAC,IAAI,CAAC,CAe7F;AAED,wBAAsB,SAAS,CAAC,IAAI,EAAE,UAAU,EAAE,GAAG,EAAE,OAAO,EAAE,GAAG,EAAE,QAAQ,GAAG,OAAO,CAAC,IAAI,CAAC,CAc5F;AAED,wBAAsB,YAAY,CAAC,IAAI,EAAE,UAAU,EAAE,GAAG,EAAE,OAAO,EAAE,GAAG,EAAE,QAAQ,GAAG,OAAO,CAAC,IAAI,CAAC,CAe/F;AAED,wBAAsB,YAAY,CAAC,IAAI,EAAE,UAAU,EAAE,GAAG,EAAE,OAAO,EAAE,GAAG,EAAE,QAAQ,GAAG,OAAO,CAAC,IAAI,CAAC,CAc/F;AAED,wBAAsB,UAAU,CAAC,IAAI,EAAE,UAAU,EAAE,GAAG,EAAE,OAAO,EAAE,GAAG,EAAE,QAAQ,GAAG,OAAO,CAAC,IAAI,CAAC,CAe7F;AAED,wBAAsB,aAAa,CAAC,IAAI,EAAE,UAAU,EAAE,GAAG,EAAE,OAAO,EAAE,GAAG,EAAE,QAAQ,GAAG,OAAO,CAAC,IAAI,CAAC,CAchG;AAED,wBAAsB,oBAAoB,CAAC,IAAI,EAAE,UAAU,EAAE,GAAG,EAAE,OAAO,EAAE,GAAG,EAAE,QAAQ,GAAG,OAAO,CAAC,IAAI,CAAC,CAcvG;AAED,wBAAsB,kBAAkB,CAAC,IAAI,EAAE,UAAU,EAAE,GAAG,EAAE,OAAO,EAAE,GAAG,EAAE,QAAQ,GAAG,OAAO,CAAC,IAAI,CAAC,CAarG;AAED,wBAAsB,iBAAiB,CAAC,IAAI,EAAE,UAAU,EAAE,GAAG,EAAE,OAAO,EAAE,GAAG,EAAE,QAAQ,GAAG,OAAO,CAAC,IAAI,CAAC,CAcpG"}