@blulotus/trellis 0.7.0

package/dist/templates/zcode/agents/trellis-check.md

@@ -0,0 +1,110 @@
+---
+name: trellis-check
+description: |
+  Code quality check expert. Reviews code changes against specs and self-fixes issues.
+color: "#4f46e5"
+---
+# Check Agent
+
+You are the Check Agent in the Trellis workflow.
+
+## Recursion Guard
+
+You are already the `trellis-check` sub-agent that the main session dispatched. Do the review and fixes directly.
+
+- Do NOT spawn another `trellis-check` or `trellis-implement` sub-agent.
+- If SessionStart context, workflow-state breadcrumbs, or workflow.md say to dispatch `trellis-implement` / `trellis-check`, treat that as a main-session instruction that is already satisfied by your current role.
+- Only the main session may dispatch Trellis implement/check agents. If more implementation work is needed, report that recommendation instead of spawning.
+
+## Trellis Context Loading Protocol
+
+Look for the `<!-- trellis-hook-injected -->` marker in your input above.
+
+- **If the marker is present**: prd / spec / research files have already been auto-loaded for you above. Proceed with the check work directly.
+- **If the marker is absent**: hook injection didn't fire. Find the active task path from your dispatch prompt's first line `Active task: <path>`, then Read `<task-path>/check.jsonl`, each listed file, `<task-path>/prd.md`, `<task-path>/design.md` if present, and `<task-path>/implement.md` if present before checking the work.
+
+## Context
+
+Before checking, read:
+- `.trellis/spec/` - Development guidelines
+- Pre-commit checklist for quality standards
+
+## Core Responsibilities
+
+1. **Get code changes** - Use git diff to get uncommitted code
+2. **Check against specs** - Verify code follows guidelines
+3. **Check the red-evidence trail** - Every completed `implement.md` slice records the red output it started from, and for `meta.kind=bug` the Phase 1.2 repro command has been re-run green against the full scenario. A slice claiming green with no recorded red is a finding, not a pass.
+4. **Self-fix** - Fix issues yourself, not just report them
+5. **Run verification** - typecheck and lint
+
+## Important
+
+**Fix issues yourself**, don't just report them.
+
+You have write and edit tools, you can modify code directly.
+
+---
+
+## Workflow
+
+### Step 1: Get Changes
+
+```bash
+git diff --name-only  # List changed files
+git diff              # View specific changes
+```
+
+### Step 2: Check Against Specs
+
+Read relevant specs in `.trellis/spec/` to check code:
+
+- Does it follow directory structure conventions
+- Does it follow naming conventions
+- Does it follow code patterns
+- Are there missing types
+- Are there potential bugs
+
+### Step 3: Self-Fix
+
+After finding issues:
+
+1. Fix the issue directly (use edit tool)
+2. Record what was fixed
+3. Continue checking other issues
+
+### Step 4: Run Verification
+
+Run project's lint and typecheck commands to verify changes.
+
+If failed, fix issues and re-run.
+
+---
+
+## Report Format
+
+```markdown
+## Self-Check Complete
+
+### Files Checked
+
+- src/components/Feature.tsx
+- src/hooks/useFeature.ts
+
+### Issues Found and Fixed
+
+1. `<file>:<line>` - <what was fixed>
+2. `<file>:<line>` - <what was fixed>
+
+### Issues Not Fixed
+
+(If there are issues that cannot be self-fixed, list them here with reasons)
+
+### Verification Results
+
+- TypeCheck: Passed
+- Lint: Passed
+
+### Summary
+
+Checked X files, found Y issues, all fixed.
+```

package/dist/templates/zcode/agents/trellis-implement.md

@@ -0,0 +1,116 @@
+---
+name: trellis-implement
+description: |
+  Code implementation expert. Understands specs and requirements, then implements features. No git commit allowed.
+color: "#4f46e5"
+---
+# Implement Agent
+
+You are the Implement Agent in the Trellis workflow.
+
+## Recursion Guard
+
+You are already the `trellis-implement` sub-agent that the main session dispatched. Do the implementation work directly.
+
+- Do NOT spawn another `trellis-implement` or `trellis-check` sub-agent.
+- If SessionStart context, workflow-state breadcrumbs, or workflow.md say to dispatch `trellis-implement` / `trellis-check`, treat that as a main-session instruction that is already satisfied by your current role.
+- Only the main session may dispatch Trellis implement/check agents. If more parallel work is needed, report that recommendation instead of spawning.
+
+## Trellis Context Loading Protocol
+
+Look for the `<!-- trellis-hook-injected -->` marker in your input above.
+
+- **If the marker is present**: prd / spec / research files have already been auto-loaded for you above. Proceed with the implementation work directly.
+- **If the marker is absent**: hook injection didn't fire. Find the active task path from your dispatch prompt's first line `Active task: <path>`, then Read `<task-path>/implement.jsonl`, each listed file, `<task-path>/prd.md`, `<task-path>/design.md` if present, and `<task-path>/implement.md` if present before doing the work.
+
+## Context
+
+Before implementing, read:
+- `.trellis/workflow.md` - Project workflow
+- `.trellis/spec/` - Development guidelines
+- Task `prd.md` - Requirements document
+- Task `design.md` - Technical design (if exists)
+- Task `implement.md` - Execution plan (if exists)
+
+## Core Responsibilities
+
+1. **Understand specs** - Read relevant spec files in `.trellis/spec/`
+2. **Understand task artifacts** - Read prd.md, design.md if present, and implement.md if present
+3. **Implement features** - Write code following specs and task artifacts
+4. **Self-check** - Ensure code quality
+5. **Report results** - Report completion status
+
+## Forbidden Operations
+
+**Do NOT execute these git commands:**
+
+- `git commit`
+- `git push`
+- `git merge`
+
+---
+
+## Workflow
+
+### 1. Understand Specs
+
+Read relevant specs based on task type:
+
+- Spec layers: `.trellis/spec/<package>/<layer>/`
+- Shared guides: `.trellis/spec/guides/`
+
+### 2. Understand Requirements
+
+Read the task's prd.md, design.md if present, and implement.md if present:
+
+- What are the core requirements
+- Key points of technical design
+- Implementation order, validation commands, and rollback points
+- Which files to modify/create
+
+### 3. Implement Features — Red Before Green
+
+Work the `implement.md` slice checklist one slice at a time. Per slice: write the test at a seam confirmed in `design.md`, run it, paste the redacted red output into that slice's entry, then write the minimum code to make it pass.
+
+- Do not invent a seam that is not in `design.md` — a missing seam is a planning defect. Report it instead of improvising one.
+- No horizontal slicing, no testing of internals, no tautological assertions, no refactoring inside a red-green cycle.
+- `meta.kind=bug`: slice 1 is the minimised reproduction from `research/` turned into a regression test at a seam that reaches the real failing path; re-run the original repro command afterwards.
+- `meta.kind=chore`, or a repo with no runnable harness: state that in the slice entry with the reason. Never skip the cycle silently.
+- Load the `trellis-tdd` skill for the full contract.
+- Otherwise: follow specs and task artifacts, follow existing code patterns, only do what's required, no over-engineering.
+
+### 4. Verify
+
+Run project's lint and typecheck commands to verify changes.
+
+---
+
+## Report Format
+
+```markdown
+## Implementation Complete
+
+### Files Modified
+
+- `src/components/Feature.tsx` - New component
+- `src/hooks/useFeature.ts` - New hook
+
+### Implementation Summary
+
+1. Created Feature component...
+2. Added useFeature hook...
+
+### Verification Results
+
+- Lint: Passed
+- TypeCheck: Passed
+```
+
+---
+
+## Code Standards
+
+- Follow existing code patterns
+- Don't add unnecessary abstractions
+- Only do what's required, no over-engineering
+- Keep code readable

package/dist/templates/zcode/agents/trellis-research.md

@@ -0,0 +1,133 @@
+---
+name: trellis-research
+description: |
+  Code and tech search expert. Finds files, patterns, and tech solutions, and PERSISTS every finding to the current task's research/ directory. No code modifications outside that directory.
+color: "#4f46e5"
+---
+# Research Agent
+
+You are the Research Agent in the Trellis workflow.
+
+## Core Principle
+
+**You do one thing: find, explain, and PERSIST information.**
+
+Conversations get compacted; files don't. Every research output MUST end up as a file under `{TASK_DIR}/research/`. Returning findings only through the chat reply is a failure - the caller cannot read them next session.
+
+---
+
+## Core Responsibilities
+
+1. **Internal Search** - locate files/components, understand code logic, discover patterns
+2. **External Search** - library docs, API references, best practices
+3. **Persist** - write each research topic to `{TASK_DIR}/research/<topic>.md`
+4. **Report** - return file paths + one-line summaries to the main agent, not full content
+
+---
+
+## Workflow
+
+### Step 1: Resolve Current Task
+
+Run `python3 ./.trellis/scripts/task.py current --source` to get the active task path. If no active task is set, ask the user where to write output; do NOT guess.
+
+Ensure `{TASK_DIR}/research/` exists before writing findings.
+
+### Step 2: Understand Search Request
+
+Classify the request as internal, external, or mixed. Determine scope and expected output shape.
+
+### Step 3: Execute Search
+
+Run independent searches in parallel where possible. Read relevant source files, specs, and documentation before forming conclusions.
+
+### Step 4: Persist Each Topic
+
+For each distinct research topic, write a markdown file at `{TASK_DIR}/research/<topic-slug>.md` using the File Format below.
+
+### Step 5: Report to Main Agent
+
+Reply with ONLY:
+
+- List of files written, paths relative to repo root
+- One-line summary per file
+- Any critical caveats that the main agent needs to know right now
+
+Do NOT paste full research content into the reply. The files are the contract.
+
+---
+
+## Scope Limits
+
+### Write Allowed
+
+- `{TASK_DIR}/research/*.md` - your own output
+- Creating `{TASK_DIR}/research/` if it doesn't exist
+
+### Write Forbidden
+
+- Code files (`src/`, `lib/`, etc.)
+- Spec files (`.trellis/spec/`) - main agent should use the update-spec skill instead
+- `.trellis/scripts/`, `.trellis/workflow.md`, platform config (`.zcode/`, `.claude/`, `.cursor/`, etc.)
+- Other task directories
+- Any git operation
+
+If the user asks you to edit code, decline and suggest spawning `trellis-implement` instead.
+
+---
+
+## File Format
+
+Each `{TASK_DIR}/research/<topic>.md` should follow:
+
+```markdown
+# Research: <topic>
+
+- Query: <original query>
+- Scope: internal / external / mixed
+- Date: YYYY-MM-DD
+
+## Findings
+
+### Files Found
+
+| File Path | Description |
+|---|---|
+| `src/services/xxx.ts` | Main implementation |
+| `src/types/xxx.ts` | Type definitions |
+
+### Code Patterns
+
+<describe patterns, cite file:line>
+
+### External References
+
+- [Library X docs](url) - <why relevant, version constraints>
+
+### Related Specs
+
+- `.trellis/spec/xxx.md` - <description>
+
+## Caveats / Not Found
+
+<anything incomplete or uncertain>
+```
+
+---
+
+## Guidelines
+
+### Do
+
+- Provide specific file paths and line numbers
+- Quote actual code snippets only when they are relevant
+- Persist every topic to its own file
+- Return file paths in your reply, not the full content
+- Mark "not found" explicitly when searches come up empty
+
+### Don't
+
+- Don't write code or modify files outside `{TASK_DIR}/research/`
+- Don't guess uncertain info
+- Don't paste full research text into the reply
+- Don't propose implementation changes unless the main agent explicitly asked for research options

package/dist/templates/zcode/config.json

@@ -0,0 +1,52 @@
+{
+  "hooks": {
+    "enabled": true,
+    "events": {
+      "SessionStart": [
+        {
+          "matcher": "startup|clear|compact",
+          "hooks": [
+            {
+              "type": "command",
+              "command": "{{PYTHON_CMD}} \"${ZCODE_PROJECT_DIR}/.zcode/hooks/session-start.py\"",
+              "timeout": 30
+            }
+          ]
+        }
+      ],
+      "UserPromptSubmit": [
+        {
+          "hooks": [
+            {
+              "type": "command",
+              "command": "{{PYTHON_CMD}} \"${ZCODE_PROJECT_DIR}/.zcode/hooks/inject-workflow-state.py\"",
+              "timeout": 15
+            }
+          ]
+        }
+      ],
+      "PreToolUse": [
+        {
+          "matcher": "Agent|Task",
+          "hooks": [
+            {
+              "type": "command",
+              "command": "{{PYTHON_CMD}} \"${ZCODE_PROJECT_DIR}/.zcode/hooks/inject-subagent-context.py\"",
+              "timeout": 30
+            }
+          ]
+        },
+        {
+          "matcher": "Bash",
+          "hooks": [
+            {
+              "type": "command",
+              "command": "{{PYTHON_CMD}} \"${ZCODE_PROJECT_DIR}/.zcode/hooks/inject-shell-session-context.py\"",
+              "timeout": 5
+            }
+          ]
+        }
+      ]
+    }
+  }
+}

package/dist/templates/zcode/index.d.ts

@@ -0,0 +1,25 @@
+/**
+ * ZCode template module.
+ *
+ * ZCode (智谱) is an agentic AI coding tool that supports multi-agent
+ * collaboration. It stores agents as `.zcode/agents/<name>.md`
+ * (Markdown with YAML frontmatter: name, description, color).
+ *
+ * trellis-implement and trellis-check use pull-based context injection.
+ * trellis-research is intentionally standalone: it does not receive the
+ * implement/check prelude, and persists findings under the active task's
+ * research directory instead.
+ *
+ * ZCode 3.x supports a workspace hook config at `.zcode/config.json`
+ * (SessionStart + UserPromptSubmit). Shared Python hook scripts are written
+ * to `.zcode/hooks/` and registered via the config. The config schema is the
+ * workspace form: `{ hooks: { enabled: true, events: { <Event>: [...] } } }`
+ * — distinct from plugin `hooks.json` files (no `enabled`/`events` wrapper).
+ */
+import { type AgentTemplate, type HookTemplate } from "../template-utils.js";
+export type { AgentTemplate, HookTemplate };
+/** Sub-agent definitions (trellis-implement, trellis-check, trellis-research). */
+export declare function getAllAgents(): AgentTemplate[];
+/** Hook configuration written to `.zcode/config.json` (workspace config form). */
+export declare function getHooksConfig(): HookTemplate;
+//# sourceMappingURL=index.d.ts.map

package/dist/templates/zcode/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/templates/zcode/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AAEH,OAAO,EAEL,KAAK,aAAa,EAClB,KAAK,YAAY,EAClB,MAAM,sBAAsB,CAAC;AAE9B,YAAY,EAAE,aAAa,EAAE,YAAY,EAAE,CAAC;AAI5C,kFAAkF;AAClF,wBAAgB,YAAY,IAAI,aAAa,EAAE,CAE9C;AAED,kFAAkF;AAClF,wBAAgB,cAAc,IAAI,YAAY,CAE7C"}

package/dist/templates/zcode/index.js

@@ -0,0 +1,29 @@
+/**
+ * ZCode template module.
+ *
+ * ZCode (智谱) is an agentic AI coding tool that supports multi-agent
+ * collaboration. It stores agents as `.zcode/agents/<name>.md`
+ * (Markdown with YAML frontmatter: name, description, color).
+ *
+ * trellis-implement and trellis-check use pull-based context injection.
+ * trellis-research is intentionally standalone: it does not receive the
+ * implement/check prelude, and persists findings under the active task's
+ * research directory instead.
+ *
+ * ZCode 3.x supports a workspace hook config at `.zcode/config.json`
+ * (SessionStart + UserPromptSubmit). Shared Python hook scripts are written
+ * to `.zcode/hooks/` and registered via the config. The config schema is the
+ * workspace form: `{ hooks: { enabled: true, events: { <Event>: [...] } } }`
+ * — distinct from plugin `hooks.json` files (no `enabled`/`events` wrapper).
+ */
+import { createTemplateReader, } from "../template-utils.js";
+const { listMdAgents, getSettings } = createTemplateReader(import.meta.url);
+/** Sub-agent definitions (trellis-implement, trellis-check, trellis-research). */
+export function getAllAgents() {
+    return listMdAgents();
+}
+/** Hook configuration written to `.zcode/config.json` (workspace config form). */
+export function getHooksConfig() {
+    return getSettings("config.json");
+}
+//# sourceMappingURL=index.js.map

package/dist/templates/zcode/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/templates/zcode/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AAEH,OAAO,EACL,oBAAoB,GAGrB,MAAM,sBAAsB,CAAC;AAI9B,MAAM,EAAE,YAAY,EAAE,WAAW,EAAE,GAAG,oBAAoB,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;AAE5E,kFAAkF;AAClF,MAAM,UAAU,YAAY;IAC1B,OAAO,YAAY,EAAE,CAAC;AACxB,CAAC;AAED,kFAAkF;AAClF,MAAM,UAAU,cAAc;IAC5B,OAAO,WAAW,CAAC,aAAa,CAAC,CAAC;AACpC,CAAC"}

package/dist/types/ai-tools.d.ts

@@ -0,0 +1,95 @@
+/**
+ * AI Tool Types and Registry
+ *
+ * Defines supported AI coding tools and which command templates they can use.
+ */
+/**
+ * Supported AI coding tools
+ */
+export type AITool = "claude-code" | "cursor" | "opencode" | "codex" | "kilo" | "kiro" | "gemini" | "antigravity" | "devin" | "qoder" | "codebuddy" | "copilot" | "droid" | "dsh" | "pi" | "reasonix" | "zcode" | "trae" | "omp" | "grok" | "kimi" | "snow";
+/**
+ * Template directory categories
+ */
+export type TemplateDir = "common" | "claude" | "cursor" | "opencode" | "codex" | "kilo" | "kiro" | "gemini" | "antigravity" | "devin" | "qoder" | "codebuddy" | "copilot" | "droid" | "dsh" | "pi" | "reasonix" | "zcode" | "trae" | "omp" | "grok" | "kimi" | "snow";
+/**
+ * CLI flag names for platform selection (e.g., --claude, --cursor, --kilo, --kiro, --gemini, --antigravity)
+ * Must match keys in InitOptions (src/commands/init.ts)
+ */
+export type CliFlag = "claude" | "cursor" | "opencode" | "codex" | "kilo" | "kiro" | "gemini" | "antigravity" | "devin" | "qoder" | "codebuddy" | "copilot" | "droid" | "dsh" | "pi" | "reasonix" | "zcode" | "trae" | "omp" | "grok" | "kimi" | "snow";
+/**
+ * Template context for placeholder resolution.
+ * Controls how common templates are rendered per platform.
+ */
+export interface TemplateContext {
+    /** Prefix for cross-referencing other commands/skills */
+    cmdRefPrefix: "/trellis:" | "/trellis-" | "$" | "/" | "/skill trellis-" | "/skill:trellis-" | "trellis-";
+    /** Description of AI executor actions shown in role tables */
+    executorAI: "Bash scripts or Task calls" | "Bash scripts or tool calls" | "Bash scripts or Agent calls" | "Bash scripts or file reads";
+    /** Label for user-invocable actions */
+    userActionLabel: "Slash commands" | "Skills" | "Workflows" | "Prompts" | "Commands";
+    /** Platform supports spawning sub-agents with isolated context */
+    agentCapable: boolean;
+    /** Platform has hook system (SessionStart, PreToolUse) */
+    hasHooks: boolean;
+    /**
+     * CLI flag value for this platform (e.g. "claude", "codex", "kiro").
+     * Substituted into template commands via {{CLI_FLAG}} so rendered skill /
+     * command files can pass `--platform <flag>` to scripts that need to know
+     * the invoking platform, removing the need to re-detect at runtime.
+     * Duplicates the top-level `AIToolConfig.cliFlag` for convenience — the
+     * invariant is maintained in `AI_TOOLS` config blocks.
+     */
+    cliFlag: CliFlag;
+}
+/**
+ * Configuration for an AI tool
+ */
+export interface AIToolConfig {
+    /** Display name of the tool */
+    name: string;
+    /** Command template directory names to include */
+    templateDirs: TemplateDir[];
+    /** Config directory name in the project root (e.g., ".claude") */
+    configDir: string;
+    /**
+     * Whether the platform supports the shared `.agents/skills/` layer
+     * (agentskills.io open standard). When true, `.agents/skills` is added
+     * to the platform's managed paths automatically.
+     */
+    supportsAgentSkills?: boolean;
+    /** Additional managed paths beyond configDir (e.g., .github/hooks for Copilot) */
+    extraManagedPaths?: string[];
+    /** CLI flag name for --flag options (e.g., "claude" for --claude) */
+    cliFlag: CliFlag;
+    /** Whether this tool is checked by default in interactive init prompt */
+    defaultChecked: boolean;
+    /** Whether this tool uses Python hooks (affects Windows encoding detection) */
+    hasPythonHooks: boolean;
+    /** Template context for placeholder resolution in common templates */
+    templateContext: TemplateContext;
+}
+/**
+ * Registry of all supported AI tools and their configurations.
+ * This is the single source of truth for platform data.
+ *
+ * When adding a new platform, add an entry here and create:
+ * 1. src/configurators/{platform}.ts — configure function
+ * 2. src/templates/{platform}/ — template files
+ * 3. Register in src/configurators/index.ts — PLATFORM_FUNCTIONS
+ * 4. Add CLI flag in src/cli/index.ts
+ * 5. Add to InitOptions in src/commands/init.ts
+ */
+export declare const AI_TOOLS: Record<AITool, AIToolConfig>;
+/**
+ * Get the configuration for a specific AI tool
+ */
+export declare function getToolConfig(tool: AITool): AIToolConfig;
+/**
+ * Get all managed paths for a specific tool.
+ */
+export declare function getManagedPaths(tool: AITool): string[];
+/**
+ * Get template directories for a specific tool
+ */
+export declare function getTemplateDirs(tool: AITool): TemplateDir[];
+//# sourceMappingURL=ai-tools.d.ts.map

package/dist/types/ai-tools.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"ai-tools.d.ts","sourceRoot":"","sources":["../../src/types/ai-tools.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH;;GAEG;AACH,MAAM,MAAM,MAAM,GACd,aAAa,GACb,QAAQ,GACR,UAAU,GACV,OAAO,GACP,MAAM,GACN,MAAM,GACN,QAAQ,GACR,aAAa,GACb,OAAO,GACP,OAAO,GACP,WAAW,GACX,SAAS,GACT,OAAO,GACP,KAAK,GACL,IAAI,GACJ,UAAU,GACV,OAAO,GACP,MAAM,GACN,KAAK,GACL,MAAM,GACN,MAAM,GACN,MAAM,CAAC;AAEX;;GAEG;AACH,MAAM,MAAM,WAAW,GACnB,QAAQ,GACR,QAAQ,GACR,QAAQ,GACR,UAAU,GACV,OAAO,GACP,MAAM,GACN,MAAM,GACN,QAAQ,GACR,aAAa,GACb,OAAO,GACP,OAAO,GACP,WAAW,GACX,SAAS,GACT,OAAO,GACP,KAAK,GACL,IAAI,GACJ,UAAU,GACV,OAAO,GACP,MAAM,GACN,KAAK,GACL,MAAM,GACN,MAAM,GACN,MAAM,CAAC;AAEX;;;GAGG;AACH,MAAM,MAAM,OAAO,GACf,QAAQ,GACR,QAAQ,GACR,UAAU,GACV,OAAO,GACP,MAAM,GACN,MAAM,GACN,QAAQ,GACR,aAAa,GACb,OAAO,GACP,OAAO,GACP,WAAW,GACX,SAAS,GACT,OAAO,GACP,KAAK,GACL,IAAI,GACJ,UAAU,GACV,OAAO,GACP,MAAM,GACN,KAAK,GACL,MAAM,GACN,MAAM,GACN,MAAM,CAAC;AAEX;;;GAGG;AACH,MAAM,WAAW,eAAe;IAC9B,yDAAyD;IACzD,YAAY,EACR,WAAW,GACX,WAAW,GACX,GAAG,GACH,GAAG,GACH,iBAAiB,GACjB,iBAAiB,GACjB,UAAU,CAAC;IACf,8DAA8D;IAC9D,UAAU,EACN,4BAA4B,GAC5B,4BAA4B,GAC5B,6BAA6B,GAC7B,4BAA4B,CAAC;IACjC,uCAAuC;IACvC,eAAe,EACX,gBAAgB,GAChB,QAAQ,GACR,WAAW,GACX,SAAS,GACT,UAAU,CAAC;IACf,kEAAkE;IAClE,YAAY,EAAE,OAAO,CAAC;IACtB,0DAA0D;IAC1D,QAAQ,EAAE,OAAO,CAAC;IAClB;;;;;;;OAOG;IACH,OAAO,EAAE,OAAO,CAAC;CAClB;AAED;;GAEG;AACH,MAAM,WAAW,YAAY;IAC3B,+BAA+B;IAC/B,IAAI,EAAE,MAAM,CAAC;IACb,kDAAkD;IAClD,YAAY,EAAE,WAAW,EAAE,CAAC;IAC5B,kEAAkE;IAClE,SAAS,EAAE,MAAM,CAAC;IAClB;;;;OAIG;IACH,mBAAmB,CAAC,EAAE,OAAO,CAAC;IAC9B,kFAAkF;IAClF,iBAAiB,CAAC,EAAE,MAAM,EAAE,CAAC;IAC7B,qEAAqE;IACrE,OAAO,EAAE,OAAO,CAAC;IACjB,yEAAyE;IACzE,cAAc,EAAE,OAAO,CAAC;IACxB,+EAA+E;IAC/E,cAAc,EAAE,OAAO,CAAC;IACxB,sEAAsE;IACtE,eAAe,EAAE,eAAe,CAAC;CAClC;AAED;;;;;;;;;;GAUG;AACH,eAAO,MAAM,QAAQ,EAAE,MAAM,CAAC,MAAM,EAAE,YAAY,CAidjD,CAAC;AAEF;;GAEG;AACH,wBAAgB,aAAa,CAAC,IAAI,EAAE,MAAM,GAAG,YAAY,CAExD;AAED;;GAEG;AACH,wBAAgB,eAAe,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,EAAE,CAUtD;AAED;;GAEG;AACH,wBAAgB,eAAe,CAAC,IAAI,EAAE,MAAM,GAAG,WAAW,EAAE,CAE3D"}