@winspan/claude-forge 8.41.0 → 8.50.6

package/dist/engine/conventions/react-best-practices.yaml

@@ -1,96 +0,0 @@
-id: "react-best-practices"
-name: "React 最佳实践"
-version: "1.0.0"
-description: "React/前端开发规范，覆盖组件设计、状态管理、性能优化和安全性"
-triggers: ["react", "jsx", "tsx", "component", "hook", "useState", "useEffect", "组件", "前端"]
-
-variables:
-  react_file_patterns: [".jsx", ".tsx"]
-  hook_names: ["useState", "useEffect", "useCallback", "useMemo", "useRef", "useContext", "useReducer"]
-  dangerous_html_props: ["dangerouslySetInnerHTML", "innerHTML"]
-  max_component_lines: 300
-  max_useEffect_deps: 5
-
-forbidden:
-  - id: "no-dangerously-set-inner-html"
-    when: |
-      tool.in(["Write", "Edit"])
-      && file_ext.in(vars.react_file_patterns)
-      && (args.content ?? args.new_string ?? "").match(/dangerouslySetInnerHTML/).ok()
-    level: warn
-    message: "检测到 dangerouslySetInnerHTML，存在 XSS 风险"
-    suggestion: "使用 React 的默认转义机制，或使用 DOMPurify 清理 HTML"
-    operator_guidance: "dangerouslySetInnerHTML 绕过了 React 的 XSS 防护；如必须使用，需先用 DOMPurify.sanitize() 清理内容。"
-    doc_ref: "https://react.dev/reference/react-dom/components/common#dangerously-setting-the-inner-html"
-    tags: ["react", "xss", "security"]
-
-  - id: "no-inline-function-in-jsx"
-    when: |
-      tool.in(["Write", "Edit"])
-      && file_ext.in(vars.react_file_patterns)
-      && (args.content ?? args.new_string ?? "").match(/onClick=\{(?:\(\)|function)/).ok()
-    level: warn
-    message: "检测到 JSX 中的内联函数，可能导致不必要的重渲染"
-    suggestion: "使用 useCallback 包裹函数，或将函数提取到组件外"
-    operator_guidance: "每次渲染都会创建新函数引用，导致子组件不必要的重渲染；用 useCallback 缓存函数引用。"
-    tags: ["react", "performance"]
-
-  - id: "warn-missing-key-prop"
-    when: |
-      tool.in(["Write", "Edit"])
-      && file_ext.in(vars.react_file_patterns)
-      && (args.content ?? args.new_string ?? "").match(/\.map\([^)]*=>\s*<[A-Z]/).ok()
-      && !(args.content ?? args.new_string ?? "").match(/key=/).ok()
-    level: warn
-    message: "检测到 map 渲染列表但可能缺少 key 属性"
-    suggestion: "为列表项添加唯一的 key 属性，避免使用数组索引"
-    operator_guidance: "key 帮助 React 识别哪些元素改变了；使用稳定的唯一标识符（如 id），不要用数组索引。"
-    doc_ref: "https://react.dev/learn/rendering-lists#keeping-list-items-in-order-with-key"
-    tags: ["react", "performance", "correctness"]
-
-  - id: "warn-useEffect-missing-deps"
-    when: |
-      tool.in(["Write", "Edit"])
-      && file_ext.in(vars.react_file_patterns)
-      && (args.content ?? args.new_string ?? "").match(/useEffect\([^,]+,\s*\[\s*\]\s*\)/).ok()
-    level: warn
-    message: "检测到 useEffect 使用空依赖数组，可能遗漏依赖"
-    suggestion: "检查 effect 中使用的所有外部变量是否都在依赖数组中"
-    operator_guidance: "空依赖数组意味着 effect 只在挂载时运行一次；如果 effect 内部使用了 props/state，应添加到依赖数组。"
-    doc_ref: "https://react.dev/reference/react/useEffect#specifying-reactive-dependencies"
-    tags: ["react", "hooks", "correctness"]
-
-  - id: "no-direct-state-mutation"
-    when: |
-      tool.in(["Write", "Edit"])
-      && file_ext.in(vars.react_file_patterns)
-      && (args.content ?? args.new_string ?? "").match(/\bstate\.[a-zA-Z_]+\s*=/).ok()
-    level: block
-    message: "禁止直接修改 state，必须使用 setState"
-    suggestion: "使用 setState 或 useState 返回的 setter 函数更新状态"
-    operator_guidance: "直接修改 state 不会触发重渲染，且违反 React 的不可变性原则；始终通过 setState 更新。"
-    doc_ref: "https://react.dev/learn/updating-objects-in-state"
-    tags: ["react", "state", "correctness"]
-
-escalation:
-  - id: "large-component-warning"
-    when: |
-      tool == "Write"
-      && file_ext.in(vars.react_file_patterns)
-      && (args.content ?? "").split("\n").length > vars.max_component_lines
-    action: warn
-    message: "组件超过 {{vars.max_component_lines}} 行，建议拆分"
-    suggestion: "将大组件拆分为多个小组件，提升可维护性"
-    operator_guidance: "大组件难以理解和测试；按功能或 UI 区域拆分，每个组件专注单一职责。"
-    tags: ["react", "maintainability"]
-
-deliverables: []
-
-principles: |
-  ## React 最佳实践
-  - 禁止使用 dangerouslySetInnerHTML，防止 XSS 攻击
-  - 避免 JSX 中的内联函数，使用 useCallback 优化性能
-  - 列表渲染必须添加唯一 key，不使用数组索引
-  - useEffect 依赖数组必须完整，避免遗漏依赖
-  - 禁止直接修改 state，必须通过 setState 更新
-  - 组件超过 300 行时建议拆分

package/dist/engine/conventions/routing.yaml

@@ -1,378 +0,0 @@
-# Claude Forge — Optimized Agent Routing Rules
-# Schema version 1.4 (Methodology-aware: 6 fine-grained BMAD + Harness presets)
-#
-# Evaluated top-down, first match wins. User override at
-# ~/.claude-forge/routing.yaml can replace this entire rule set.
-#
-# V2 axes (action / domain / artifact) are OPTIONAL on every rule. When set,
-# they tighten the match — the input must carry the corresponding V2 field
-# AND it must match the rule's enum/list. V1 rules (taskType + complexity)
-# keep working unchanged because the new axes are additive.
-#
-# Methodology agents (since v1.4, 6 fine-grained presets):
-#   - bmad-feature-full     (5 phase: analyze → design → implement → test → review)
-#   - bmad-feature-quick    (3 phase: implement → test → review)
-#   - bmad-spec-only        (2 phase: analyze → design — spec/design only, no code)
-#   - harness-debug-full    (5 phase: reproduce → safety-net → root-cause → fix → verify)
-#   - harness-hotfix        (3 phase: safety-net → fix → verify — MANUAL only, see below)
-#   - harness-investigate   (2 phase: reproduce → root-cause — investigation only)
-#
-# Optimization goals:
-# 1. Add more specific task types for better classification
-# 2. Reduce agent overlap by clarifying boundaries
-# 3. Add complexity-based routing for better agent selection
-# 4. Leverage V2 action + artifact when available (e.g. investigate+build)
-# 5. Methodology-driven routing for non-trivial features and bug hunts
-
-schemaVersion: "1.4"
-rules:
-  # -- V2-precision rules (action + artifact / domain) ----------------------
-  #
-  # These come first because they are the MOST specific matches: both V2 axes
-  # (action AND artifact) must align. Methodology rules below match on less
-  # specific criteria (taskType + complexity), so giving V2-precision rules
-  # priority preserves the original "specific beats general" ordering AND
-  # prevents the new methodology rules from accidentally shadowing the
-  # build-flavoured investigation router.
-  #
-  # When the classifier returns action=investigate AND target.artifact=build,
-  # we have strong evidence the user is debugging build / packaging issues
-  # ("npm 打包后为什么还有方法论"). Route directly to researcher who is
-  # equipped to dive into build pipelines.
-  - when:
-      action: investigate
-      artifact: build
-    action: { type: route_to_agent, name: researcher }
-
-  - when:
-      action: fix
-      artifact: build
-    action: { type: route_to_agent, name: refactor-specialist }
-
-  # explain + complex code/doc topics → researcher even if v1 would skip
-  - when:
-      action: explain
-      complexity: complex
-    action: { type: route_to_agent, name: researcher }
-
-  # -- Methodology Agents (priority above generic implementers) -------------
-  #
-  # Since schema 1.4 the two coarse methodology agents (`bmad-feature` and
-  # `harness-debug`) have been split into 6 fine-grained presets. The routing
-  # rules below pick the right preset by (taskType, complexity) so the agent
-  # template doing the work matches the size of the task.
-  #
-  # These rules MUST appear before the generic add_feature / fix_bug /
-  # investigate rules below — they shadow them for non-trivial complexity
-  # so the methodology agents take over from the generic implementers.
-  #
-  # They appear AFTER the V2-precision build/explain rules above, because
-  # `action=investigate + artifact=build` is a *more specific* signal than
-  # `taskType=investigate + complexity=moderate|complex`. Build-flavoured
-  # investigations should still go to the researcher.
-  #
-  # If the target methodology agent is missing from the AgentRegistry at
-  # runtime, the daemon downgrades the routing decision (see distributor),
-  # so writing the rule is safe even before the agent template is registered.
-  #
-  # Routing matrix (since v1.4):
-  #   add_feature       + complex  → bmad-feature-full
-  #   add_feature       + moderate → bmad-feature-quick
-  #   add_feature       + simple   → feature-developer (fallback, below)
-  #   analyze_requirement / design_* + (moderate|complex) → bmad-spec-only
-  #   fix_bug           + complex  → harness-debug-full
-  #   fix_bug           + moderate → (no auto-route — falls through to coder/feature-developer)
-  #   fix_bug           + simple   → coder (fallback, below)
-  #   investigate       + complex  → harness-debug-full
-  #   investigate       + moderate → harness-investigate
-  #   investigate       + simple   → researcher (fallback, below)
-  #   V2 action=investigate + artifact=code + complex  → harness-debug-full
-  #   V2 action=investigate + artifact=code + moderate → harness-investigate
-  #
-  # Note on `harness-hotfix`: this preset targets KNOWN-CAUSE emergency fixes
-  # (safety-net → fix → verify). The intent classifier has no way to
-  # distinguish "emergency fix with known cause" from a regular complex bug,
-  # so we deliberately leave `harness-hotfix` off the auto-routing table.
-  # Users invoke it manually via CLI / web UI. A future iteration may detect
-  # urgency keywords (e.g. 紧急/hotfix/线上) in the reason and add a rule.
-
-  # 1) BMAD Feature Full — complex new feature work
-  # Reason: 复杂新功能任务使用 BMAD 完整方法论：分析→设计→实现→测试→审核
-  - name: "bmad-feature-full"
-    description: "复杂新增功能任务使用 BMAD 完整 5 phase 方法论 Agent"
-    when:
-      taskType: add_feature
-      complexity: complex
-    action: { type: route_to_agent, name: bmad-feature-full }
-
-  # 2) BMAD Feature Quick — moderate new feature work (implementation plan known)
-  # Reason: 中等复杂度的新功能使用 BMAD 精简方法论：实现→测试→审核
-  - name: "bmad-feature-quick"
-    description: "中等复杂度新增功能使用 BMAD 精简 3 phase 方法论 Agent"
-    when:
-      taskType: add_feature
-      complexity: moderate
-    action: { type: route_to_agent, name: bmad-feature-quick }
-
-  # 3) BMAD Spec Only — spec/design documents without code
-  # Reason: 需求澄清和架构 / API / Schema 设计只需要产规格，不写代码
-  - name: "bmad-spec-only-from-requirement"
-    description: "需求分析任务只产规格使用 BMAD analyze + design 方法论 Agent"
-    when:
-      taskType: analyze_requirement
-      complexity: [moderate, complex]
-    action: { type: route_to_agent, name: bmad-spec-only }
-
-  - name: "bmad-spec-only-from-design-architecture"
-    description: "架构设计任务只产规格使用 BMAD analyze + design 方法论 Agent"
-    when:
-      taskType: design_architecture
-      complexity: [moderate, complex]
-    action: { type: route_to_agent, name: bmad-spec-only }
-
-  - name: "bmad-spec-only-from-design-api"
-    description: "API 设计任务只产规格使用 BMAD analyze + design 方法论 Agent"
-    when:
-      taskType: design_api
-      complexity: [moderate, complex]
-    action: { type: route_to_agent, name: bmad-spec-only }
-
-  - name: "bmad-spec-only-from-design-schema"
-    description: "Schema 设计任务只产规格使用 BMAD analyze + design 方法论 Agent"
-    when:
-      taskType: design_schema
-      complexity: [moderate, complex]
-    action: { type: route_to_agent, name: bmad-spec-only }
-
-  # 4) Harness Debug Full — complex bug fixes and investigations
-  # Reason: 复杂的 bug 排查使用 Harness 完整方法论：复现→防护网→根因→修复→验证
-  - name: "harness-debug-full-fix-bug"
-    description: "复杂 bug 修复使用 Harness 完整 5 phase 方法论 Agent"
-    when:
-      taskType: fix_bug
-      complexity: complex
-    action: { type: route_to_agent, name: harness-debug-full }
-
-  - name: "harness-debug-full-investigate"
-    description: "复杂问题调查使用 Harness 完整 5 phase 方法论 Agent"
-    when:
-      taskType: investigate
-      complexity: complex
-    action: { type: route_to_agent, name: harness-debug-full }
-
-  # 5) Harness Investigate — moderate investigation, no fix
-  # Reason: 中等复杂度的调查任务只定位问题，不修复
-  - name: "harness-investigate"
-    description: "中等复杂度问题调查使用 Harness reproduce + root-cause 方法论 Agent"
-    when:
-      taskType: investigate
-      complexity: moderate
-    action: { type: route_to_agent, name: harness-investigate }
-
-  # 6) V2 axes: code-level investigations missed by V1 taskType
-  # When the classifier returns taskType=other/explain but action=investigate
-  # and artifact=code, we still know it's code-level debugging. Split by
-  # complexity so complex cases go to the full Harness flow, moderate cases
-  # to the investigate-only preset.
-  - name: "harness-debug-full-v2"
-    description: "V2 维度识别的复杂代码级调查使用 Harness 完整方法论 Agent"
-    when:
-      action: investigate
-      artifact: code
-      complexity: complex
-    action: { type: route_to_agent, name: harness-debug-full }
-
-  - name: "harness-investigate-v2"
-    description: "V2 维度识别的中等代码级调查使用 Harness investigate 方法论 Agent"
-    when:
-      action: investigate
-      artifact: code
-      complexity: moderate
-    action: { type: route_to_agent, name: harness-investigate }
-
-  # 7) Harness Hotfix — DELIBERATELY NOT AUTO-ROUTED
-  # Reserved for manual invocation only (CLI / Web UI). See the matrix comment
-  # above. To enable auto-routing in the future, add a rule that matches a
-  # specific urgency signal in the input (e.g. reason keyword "hotfix" or
-  # a dedicated taskType once classifier is extended).
-
-  # -- Concurrent Agent Group (parallel execution) ---------------------------
-
-  - when:
-      taskType: multi_domain
-      complexity: complex
-    action:
-      type: route_to_agent_group
-      agents:
-        - name: feature-developer
-          focus: "核心功能实现"
-        - name: tester
-          focus: "单元测试编写"
-        - name: doc-reviewer
-          focus: "文档审校"
-
-  # -- Planning & Design (no code) -------------------------------------------
-
-  - when:
-      taskType: analyze_requirement
-    action: { type: route_to_agent, name: planner }
-  - when:
-      taskType: design_architecture
-    action: { type: route_to_agent, name: planner }
-  - when:
-      taskType: design_api
-    action: { type: route_to_agent, name: planner }
-  - when:
-      taskType: design_schema
-    action: { type: route_to_agent, name: planner }
-
-  # -- Meta / Forge maintenance ----------------------------------------------
-
-  - when:
-      taskType: analyze_codebase
-    action: { type: route_to_agent, name: general-purpose }
-  - when:
-      taskType: multi_domain
-    action: { type: route_to_agent, name: general-purpose }
-  - when:
-      taskType: check_quality
-    action: { type: route_to_agent, name: reviewer }
-  - when:
-      taskType: cleanup_code
-    action: { type: route_to_agent, name: refactor-specialist }
-  - when:
-      taskType: upgrade_dependency
-    action: { type: route_to_agent, name: migration-planner }
-  - when:
-      taskType: improve_coverage
-    action: { type: route_to_agent, name: tester }
-  - when:
-      taskType: write_doc
-    action: { type: route_to_agent, name: spec-writer }
-  - when:
-      taskType: setup_project
-    action: { type: route_to_agent, name: full-system-builder }
-
-  # -- Code Implementation ---------------------------------------------------
-
-  - when:
-      taskType: write_code
-      complexity: simple
-    action: { type: route_to_agent, name: coder }
-  - when:
-      taskType: fix_bug
-      complexity: simple
-    action: { type: route_to_agent, name: coder }
-  - when:
-      taskType: optimize_perf
-    action: { type: route_to_agent, name: coder }
-
-  - when:
-      taskType: write_code
-      complexity: complex
-    action: { type: route_to_agent, name: feature-developer }
-  - when:
-      taskType: add_feature
-    action: { type: route_to_agent, name: feature-developer }
-  - when:
-      taskType: fix_bug
-      complexity: complex
-    action: { type: route_to_agent, name: feature-developer }
-
-  - when:
-      taskType: write_code
-    action: { type: route_to_agent, name: coder }
-  - when:
-      taskType: fix_bug
-    action: { type: route_to_agent, name: coder }
-
-  # -- System Building -------------------------------------------------------
-
-  - when:
-      taskType: build_system
-    action: { type: route_to_agent, name: full-system-builder }
-
-  # -- Refactoring -----------------------------------------------------------
-
-  - when:
-      taskType: refactor
-      complexity: complex
-    action: { type: route_to_agent, name: refactor-specialist }
-  - when:
-      taskType: refactor
-    action: { type: route_to_agent, name: coder }
-
-  # -- Migration & Upgrade ---------------------------------------------------
-
-  - when:
-      taskType: migrate
-    action: { type: route_to_agent, name: migration-planner }
-
-  # -- Testing ---------------------------------------------------------------
-
-  - when:
-      taskType: write_test
-    action: { type: route_to_agent, name: tester }
-
-  # -- Code Review & Quality -------------------------------------------------
-
-  - when:
-      taskType: review
-    action: { type: route_to_agent, name: reviewer }
-  - when:
-      taskType: audit_security
-    action: { type: route_to_agent, name: reviewer }
-  - when:
-      taskType: check_quality
-    action: { type: route_to_agent, name: reviewer }
-
-  # -- Research & Investigation ----------------------------------------------
-
-  - when:
-      taskType: research
-    action: { type: route_to_agent, name: researcher }
-  - when:
-      taskType: investigate
-    action: { type: route_to_agent, name: researcher }
-  - when:
-      taskType: compare_solutions
-    action: { type: route_to_agent, name: researcher }
-  # Only route "explain" when the topic is complex enough to warrant a
-  # researcher dive. Plain clarification questions ("what does X mean",
-  # "does this work?") should stay with the main Claude — routing them out
-  # just produces disobey events since the main session will answer inline.
-  - when:
-      taskType: explain
-      complexity: complex
-    action: { type: route_to_agent, name: researcher }
-
-  # -- Documentation ---------------------------------------------------------
-
-  - when:
-      taskType: write_spec
-    action: { type: route_to_agent, name: spec-writer }
-  - when:
-      taskType: review_doc
-    action: { type: route_to_agent, name: doc-reviewer }
-
-  # -- Git & PR Operations ---------------------------------------------------
-
-  - when:
-      taskType: create_pr
-    action: { type: route_to_agent, name: pr-creator }
-
-  # -- Other: unclassified tasks → general-purpose agent -------------------
-
-  - name: "other-fallback"
-    description: "兜底：未分类对话路由到 general-purpose agent"
-    when:
-      taskType: other
-    action:
-      type: route_to_agent
-      name: general-purpose
-      forced: false
-
-  # -- Fallback: no agent match → Claude default flow ------------------------
-
-  - when: { default: true }
-    action: { type: none }

package/dist/engine/conventions/strict-security.yaml

@@ -1,30 +0,0 @@
-id: "strict-security"
-name: "严格安全规范"
-version: "1.0.0"
-description: "继承基础安全规范，升级部分规则为更严格的级别"
-extends: ["basic-security"]
-
-overrides:
-  - rule_id: "warn-sensitive-file-write"
-    level: block
-    message: "严格模式：禁止修改敏感文件"
-
-  - rule_id: "warn-hardcoded-secret"
-    level: confirm
-    message: "严格模式：检测到疑似硬编码密钥，必须确认"
-
-forbidden:
-  - id: "no-console-log-in-production"
-    when: |
-      tool.in(["Write", "Edit"])
-      && file_path != null
-      && !file_path.includes("test")
-      && (args.content ?? args.new_string ?? "").includes("console.log")
-    level: warn
-    message: "生产代码中包含 console.log，建议使用日志库"
-
-principles: |
-  ## 严格安全规范（继承自基础安全规范）
-  - 敏感文件修改直接阻断（升级为 block）
-  - 硬编码密钥必须确认（升级为 confirm）
-  - 生产代码禁止 console.log

package/dist/engine/conventions/ts-quality.yaml

@@ -1,49 +0,0 @@
-id: "ts-quality"
-name: "TypeScript 质量规范"
-version: "1.0.0"
-description: "TypeScript 项目的代码质量规则"
-
-variables:
-  max_file_lines: 300
-  max_consecutive_edits_same_file: 4
-
-forbidden:
-  - id: "no-any-type"
-    when: |
-      tool.in(["Write", "Edit"])
-      && file_ext == ".ts"
-      && (args.content ?? args.new_string ?? "").match(/:\s*any\b/).ok()
-    level: warn
-    message: "检测到 TypeScript any 类型，建议使用具体类型"
-
-  - id: "large-file-needs-test"
-    when: |
-      tool == "Write"
-      && file_ext.in([".ts", ".tsx"])
-      && !file_path.includes("test")
-      && !file_path.includes("spec")
-      && (args.content ?? "").split("\n").length >= vars.max_file_lines
-      && history.file_changes.filter(f => f.includes("test")).length == 0
-    level: warn
-    message: "写入了超过 {{vars.max_file_lines}} 行的代码文件，建议同步编写测试"
-
-escalation:
-  - id: "edit-loop-detection"
-    when: |
-      history.last(6).filter(e => e.tool == "Edit" && e.args.file_path == file_path).length >= vars.max_consecutive_edits_same_file
-    action: confirm
-    message: "检测到对同一文件的反复编辑，可能陷入循环"
-    suggestion: "建议退一步重新审视方案"
-
-deliverables:
-  - name: "类型检查通过"
-    command: "npx tsc --noEmit"
-    required: true
-    check_at: "before_commit"
-
-principles: |
-  ## TypeScript 质量规范
-  - 禁止使用 any 类型
-  - 超过 300 行的代码文件必须有对应测试
-  - 反复编辑同一文件时触发循环检测
-  - 提交前必须通过类型检查

package/dist/engine/dsl/compiler.d.ts

@@ -1,34 +0,0 @@
-/**
- * Convention DSL Expression Compiler
- *
- * Compiles chain-call expressions to TypeScript closures.
- *
- * Supported syntax:
- * - Comparison: ==, !=, >, <, >=, <=
- * - Logical: &&, ||, !
- * - Chain calls: obj.method(args)
- * - Property access: obj.prop
- * - Arrow functions: (x => x.prop)
- * - Regex: /pattern/flags
- * - Null coalescing: ??
- * - Template strings: {{expr}} (in messages)
- */
-import type { CompiledExpression, RuleContext } from './types.js';
-export declare class CompileError extends Error {
-    pos: number;
-    constructor(message: string, pos: number);
-}
-export declare class ExpressionCompiler {
-    compile(expr: string): CompiledExpression;
-    validate(expr: string): {
-        ok: boolean;
-        error?: string;
-    };
-}
-export declare class TemplateRenderer {
-    /**
-     * Render template strings with {{expr}} interpolation
-     */
-    render(template: string, ctx: RuleContext): string;
-}
-//# sourceMappingURL=compiler.d.ts.map

package/dist/engine/dsl/compiler.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"compiler.d.ts","sourceRoot":"","sources":["../../../src/engine/dsl/compiler.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAEH,OAAO,KAAK,EAAE,kBAAkB,EAAE,WAAW,EAAE,MAAM,YAAY,CAAC;AA4RlE,qBAAa,YAAa,SAAQ,KAAK;IACD,GAAG,EAAE,MAAM;gBAAnC,OAAO,EAAE,MAAM,EAAS,GAAG,EAAE,MAAM;CAIhD;AAwbD,qBAAa,kBAAkB;IAC7B,OAAO,CAAC,IAAI,EAAE,MAAM,GAAG,kBAAkB;IA2BzC,QAAQ,CAAC,IAAI,EAAE,MAAM,GAAG;QAAE,EAAE,EAAE,OAAO,CAAC;QAAC,KAAK,CAAC,EAAE,MAAM,CAAA;KAAE;CAWxD;AAID,qBAAa,gBAAgB;IAC3B;;OAEG;IACH,MAAM,CAAC,QAAQ,EAAE,MAAM,EAAE,GAAG,EAAE,WAAW,GAAG,MAAM;CAYnD"}