@specverse/engines 5.2.0 → 6.0.1

package/assets/prompts/core/standard/default/analyse.prompt.yaml

@@ -1,5 +1,5 @@
 name: analyse
-version: "9.0.0"
+version: "9.2.0"
 description: Extract SpecVerse specifications from existing code with deployment policy recognition
 author: SpecVerse Team
 tags: [analysis, reverse-engineering, implementation, v9, deployment-policies, validate-fix-loop]
@@ -21,6 +21,15 @@ system:
     - a deployments section showing the logical instances with operational policies
     - a manifest section with the physical details about the deployment
 
+    OUTPUT FORMAT (critical):
+    - Emit the complete .specly content as YAML directly in your response,
+      wrapped in a single ```specly ... ``` code block.
+    - Do NOT use Write, Edit, or any file-saving tools — even if available.
+      The caller harvests the spec text from your response, not from disk.
+    - Do NOT prefix with prose, explanations, or status updates. Reply with
+      the code block as the primary output. Brief commentary AFTER the
+      block is OK.
+
   context: |
     Generate a FULL SpecVerse specification that represents the actual implementation
     - this specification will be validated so must be syntactically correct
@@ -388,7 +397,7 @@ user:
     - Use components: (plural) at top level
     - Use snake_case for lifecycle states (NOT kebab-case)
     - Include components, deployments (with policies), and manifest sections
-    - Write to: spec.specly
+    - Output the spec inside a ```specly``` code block in your response (do not write to disk)
 
     Step 2: VALIDATE
     - Run: spv validate spec.specly --json
@@ -419,7 +428,7 @@ user:
         - incorrect operation policy nesting
         - invalid policy property names or values
         - missing 'policies' wrapper in operations
-      * Fix the spec using Edit tool
+      * Update the spec inline in your response (do not edit a file on disk)
       * Go back to Step 2
 
     Continue the validate-fix loop until validation passes.

package/assets/prompts/core/standard/default/behavior.prompt.yaml

@@ -1,5 +1,5 @@
 name: behavior
-version: "9.1.0"
+version: "9.2.0"
 description: Generate pure TypeScript function bodies for SpecVerse behavior steps that don't match convention patterns
 author: SpecVerse Team
 tags: [behavior, code-generation, pure-function, typescript, realize]
@@ -10,58 +10,65 @@ system:
     function bodies for behavior steps that couldn't be matched by the realize
     engine's convention patterns.
 
+  minimalContext: |
     PURE FUNCTION RULES (critical — violating these breaks the architecture):
     1. NO database access (no prisma, no queries)
     2. NO event publishing (no eventBus)
     3. NO external services (no fetch, no email providers, no payment gateways)
     4. NO imports, no require, no fs, no process
-    5. All data you need comes in via the `input` object parameter
+    5. All data you need comes in via the `input` object parameter (already destructured — you have the fields directly)
     6. Return a plain result value (object, number, string) — the caller uses it
 
-    The controller (deterministic, convention-matched code) fetches all data,
-    calls your function, and then applies the result via convention code. Your
-    function is the PURE calculation or transformation in the middle.
+    OUTPUT RULES:
+    1. Output ONLY the function body code (between { and })
+    2. First line: short comment summarising what the function does
+    3. No markdown fences, no explanation before or after
+    4. Throw Error('...') for failure cases with descriptive messages
+    5. If a step fundamentally requires external side effects, throw an error indicating that — do not fake it
+
+  fullContext: |
+    # SpecVerse context (for LLMs that don't have the SpecVerse skill loaded)
+
+    SpecVerse is a declarative specification language. You describe WHAT a
+    system does in a .specly file, and the engines generate HOW — backend
+    (Fastify/Prisma), frontend (React/Tailwind), CLI, tools, diagrams. The
+    behavior-generation step you're being asked to perform plugs a
+    specific gap: the realize engine matches most spec behavior steps
+    against convention patterns ("Find {Model}", "Set {field}",
+    "Send {event}") and emits them directly; for the rest, you fill in
+    the pure-function body.
+
+    Where your function fits:
 
-    Example flow:
     ```
-    // Controller (convention code)
+    // Controller (convention-generated code — NOT your job)
     const order = await prisma.order.findUniqueOrThrow(...);
     const customer = await prisma.customer.findUniqueOrThrow(...);
 
-    // Your function (pure)
+    // Your function — PURE calculation or transformation
     const discount = await applyDiscountBasedOnLoyaltyTier({ order, customer });
     // discount = { amount: 42, rate: 0.10 }
 
-    // Controller (convention code)
+    // Controller (convention-generated code — NOT your job)
     await prisma.order.update({ where: { id }, data: { total: order.total - discount.amount } });
     await eventBus.publish('OrderDiscounted', { orderId, discount });
     ```
 
-    Convention patterns that are ALREADY auto-generated (you don't handle these):
+    Convention patterns ALREADY auto-generated (don't re-implement these):
     - "Find {Model} by {field}", "Create {Model}", "Update {Model}..."
     - "Delete {Model}", "Transition {Model} to {state}"
     - "Set/Increment/Decrement {field}", "Send {event} event"
 
-    You handle domain-specific logic: calculations, transformations, rules,
-    scoring, categorisation, validation.
+    You handle: domain-specific calculations, transformations, rules,
+    scoring, categorisation, validation logic. Anything where the behavior
+    step text doesn't match a convention pattern.
 
-  context: |
-    OUTPUT RULES:
-    1. Output ONLY the function body code (between { and })
-    2. Destructure `input` at the top: `const { order, customer } = input;`
-       (actually this is done for you — skip the destructure)
-    3. Perform the calculation/transformation
-    4. Return a meaningful result object
-    5. Throw Error('...') for failure cases with descriptive messages
-    6. NO await prisma.*, NO await eventBus.*, NO fetch, NO external calls
-    7. If the step fundamentally requires external side effects, throw an
-       error indicating that — do not fake it
-
-    OUTPUT FORMAT:
-    - No markdown fences
-    - No explanation before or after
-    - Just the function body code
-    - First line should be a comment summarizing what the function does
+    SpecVerse uses CURVED operations (Create, Update, Retrieve, Validate,
+    Evolve, Delete) on controllers. Validate is dry-run; Evolve handles
+    lifecycle state transitions. Models declare attributes, relationships,
+    and lifecycles. Full reference lives in the SpecVerse canonical guide
+    (`specverse://guide` resource, or `~/.claude/skills/specverse/reference/guide.md`
+    if the skill is installed).
 
   examples:
     - step: "Apply discount based on loyalty tier"
@@ -107,7 +114,7 @@ user:
 
     The function MUST return {{returnType}}. If that's `any`, return a
     reasonable result object describing what was computed. If it's a specific
-    type (e.g., { cost: number; days: number }), return an object matching
+    type (e.g., "{ cost: number; days: number }"), return an object matching
     that shape exactly — the caller depends on those field names.
 
     Output ONLY the function body (the code that goes between { and }).

package/assets/prompts/core/standard/default/create.prompt.yaml

@@ -1,5 +1,5 @@
 name: create
-version: "9.0.0"
+version: "9.2.0"
 description: Generate minimal SpecVerse specifications from natural language requirements with deployment policies
 author: SpecVerse Team
 tags: [creation, requirements, minimal-spec, v9, deployment-policies, validate-fix-loop]
@@ -15,6 +15,14 @@ system:
     Your task: Analyze requirements and generate the smallest possible valid specification that captures core business logic.
     The SpecVerse inference engine will later expand these minimal specs into complete architectures.
 
+    OUTPUT FORMAT (critical):
+    - Emit the complete .specly content as YAML directly in your response,
+      wrapped in a single ```specly ... ``` code block.
+    - Do NOT use Write, Edit, or any file-saving tools — even if available.
+      The caller harvests the spec text from your response, not from disk.
+    - Do NOT prefix with prose or status updates. Reply with the code block
+      as the primary output. Brief commentary AFTER the block is OK.
+
   context: |
     CORE PRINCIPLES:
     1. Extract core business entities and their relationships
@@ -310,7 +318,7 @@ user:
     - Use components: (plural) at top level
     - Use snake_case for lifecycle states (NOT kebab-case)
     - Add deployment policies appropriate for scale
-    - Write to: spec.specly
+    - Output the spec inside a ```specly``` code block in your response (do not write to disk)
 
     Step 2: VALIDATE
     - Run: spv validate spec.specly --json
@@ -336,7 +344,7 @@ user:
         - invalid relationship syntax
         - invalid deployment policy structure
         - incorrect operation policy nesting
-      * Fix the spec using Edit tool
+      * Update the spec inline in your response (do not edit a file on disk)
       * Go back to Step 2
 
     Continue the validate-fix loop until validation passes.

package/assets/prompts/core/standard/v9/analyse.prompt.yaml

@@ -1,5 +1,5 @@
 name: analyse
-version: "9.0.0"
+version: "9.2.0"
 description: Extract SpecVerse specifications from existing code with deployment policy recognition
 author: SpecVerse Team
 tags: [analysis, reverse-engineering, implementation, v9, deployment-policies, validate-fix-loop]
@@ -21,6 +21,15 @@ system:
     - a deployments section showing the logical instances with operational policies
     - a manifest section with the physical details about the deployment
 
+    OUTPUT FORMAT (critical):
+    - Emit the complete .specly content as YAML directly in your response,
+      wrapped in a single ```specly ... ``` code block.
+    - Do NOT use Write, Edit, or any file-saving tools — even if available.
+      The caller harvests the spec text from your response, not from disk.
+    - Do NOT prefix with prose, explanations, or status updates. Reply with
+      the code block as the primary output. Brief commentary AFTER the
+      block is OK.
+
   context: |
     Generate a FULL SpecVerse specification that represents the actual implementation
     - this specification will be validated so must be syntactically correct
@@ -388,7 +397,7 @@ user:
     - Use components: (plural) at top level
     - Use snake_case for lifecycle states (NOT kebab-case)
     - Include components, deployments (with policies), and manifest sections
-    - Write to: spec.specly
+    - Output the spec inside a ```specly``` code block in your response (do not write to disk)
 
     Step 2: VALIDATE
     - Run: spv validate spec.specly --json
@@ -419,7 +428,7 @@ user:
         - incorrect operation policy nesting
         - invalid policy property names or values
         - missing 'policies' wrapper in operations
-      * Fix the spec using Edit tool
+      * Update the spec inline in your response (do not edit a file on disk)
       * Go back to Step 2
 
     Continue the validate-fix loop until validation passes.

package/assets/prompts/core/standard/v9/behavior.prompt.yaml

@@ -1,5 +1,5 @@
 name: behavior
-version: "9.1.0"
+version: "9.2.0"
 description: Generate pure TypeScript function bodies for SpecVerse behavior steps that don't match convention patterns
 author: SpecVerse Team
 tags: [behavior, code-generation, pure-function, typescript, realize]
@@ -10,58 +10,65 @@ system:
     function bodies for behavior steps that couldn't be matched by the realize
     engine's convention patterns.
 
+  minimalContext: |
     PURE FUNCTION RULES (critical — violating these breaks the architecture):
     1. NO database access (no prisma, no queries)
     2. NO event publishing (no eventBus)
     3. NO external services (no fetch, no email providers, no payment gateways)
     4. NO imports, no require, no fs, no process
-    5. All data you need comes in via the `input` object parameter
+    5. All data you need comes in via the `input` object parameter (already destructured — you have the fields directly)
     6. Return a plain result value (object, number, string) — the caller uses it
 
-    The controller (deterministic, convention-matched code) fetches all data,
-    calls your function, and then applies the result via convention code. Your
-    function is the PURE calculation or transformation in the middle.
+    OUTPUT RULES:
+    1. Output ONLY the function body code (between { and })
+    2. First line: short comment summarising what the function does
+    3. No markdown fences, no explanation before or after
+    4. Throw Error('...') for failure cases with descriptive messages
+    5. If a step fundamentally requires external side effects, throw an error indicating that — do not fake it
+
+  fullContext: |
+    # SpecVerse context (for LLMs that don't have the SpecVerse skill loaded)
+
+    SpecVerse is a declarative specification language. You describe WHAT a
+    system does in a .specly file, and the engines generate HOW — backend
+    (Fastify/Prisma), frontend (React/Tailwind), CLI, tools, diagrams. The
+    behavior-generation step you're being asked to perform plugs a
+    specific gap: the realize engine matches most spec behavior steps
+    against convention patterns ("Find {Model}", "Set {field}",
+    "Send {event}") and emits them directly; for the rest, you fill in
+    the pure-function body.
+
+    Where your function fits:
 
-    Example flow:
     ```
-    // Controller (convention code)
+    // Controller (convention-generated code — NOT your job)
     const order = await prisma.order.findUniqueOrThrow(...);
     const customer = await prisma.customer.findUniqueOrThrow(...);
 
-    // Your function (pure)
+    // Your function — PURE calculation or transformation
     const discount = await applyDiscountBasedOnLoyaltyTier({ order, customer });
     // discount = { amount: 42, rate: 0.10 }
 
-    // Controller (convention code)
+    // Controller (convention-generated code — NOT your job)
     await prisma.order.update({ where: { id }, data: { total: order.total - discount.amount } });
     await eventBus.publish('OrderDiscounted', { orderId, discount });
     ```
 
-    Convention patterns that are ALREADY auto-generated (you don't handle these):
+    Convention patterns ALREADY auto-generated (don't re-implement these):
     - "Find {Model} by {field}", "Create {Model}", "Update {Model}..."
     - "Delete {Model}", "Transition {Model} to {state}"
     - "Set/Increment/Decrement {field}", "Send {event} event"
 
-    You handle domain-specific logic: calculations, transformations, rules,
-    scoring, categorisation, validation.
+    You handle: domain-specific calculations, transformations, rules,
+    scoring, categorisation, validation logic. Anything where the behavior
+    step text doesn't match a convention pattern.
 
-  context: |
-    OUTPUT RULES:
-    1. Output ONLY the function body code (between { and })
-    2. Destructure `input` at the top: `const { order, customer } = input;`
-       (actually this is done for you — skip the destructure)
-    3. Perform the calculation/transformation
-    4. Return a meaningful result object
-    5. Throw Error('...') for failure cases with descriptive messages
-    6. NO await prisma.*, NO await eventBus.*, NO fetch, NO external calls
-    7. If the step fundamentally requires external side effects, throw an
-       error indicating that — do not fake it
-
-    OUTPUT FORMAT:
-    - No markdown fences
-    - No explanation before or after
-    - Just the function body code
-    - First line should be a comment summarizing what the function does
+    SpecVerse uses CURVED operations (Create, Update, Retrieve, Validate,
+    Evolve, Delete) on controllers. Validate is dry-run; Evolve handles
+    lifecycle state transitions. Models declare attributes, relationships,
+    and lifecycles. Full reference lives in the SpecVerse canonical guide
+    (`specverse://guide` resource, or `~/.claude/skills/specverse/reference/guide.md`
+    if the skill is installed).
 
   examples:
     - step: "Apply discount based on loyalty tier"
@@ -107,7 +114,7 @@ user:
 
     The function MUST return {{returnType}}. If that's `any`, return a
     reasonable result object describing what was computed. If it's a specific
-    type (e.g., { cost: number; days: number }), return an object matching
+    type (e.g., "{ cost: number; days: number }"), return an object matching
     that shape exactly — the caller depends on those field names.
 
     Output ONLY the function body (the code that goes between { and }).

package/assets/prompts/core/standard/v9/create.prompt.yaml

@@ -1,5 +1,5 @@
 name: create
-version: "9.0.0"
+version: "9.2.0"
 description: Generate minimal SpecVerse specifications from natural language requirements with deployment policies
 author: SpecVerse Team
 tags: [creation, requirements, minimal-spec, v9, deployment-policies, validate-fix-loop]
@@ -15,6 +15,14 @@ system:
     Your task: Analyze requirements and generate the smallest possible valid specification that captures core business logic.
     The SpecVerse inference engine will later expand these minimal specs into complete architectures.
 
+    OUTPUT FORMAT (critical):
+    - Emit the complete .specly content as YAML directly in your response,
+      wrapped in a single ```specly ... ``` code block.
+    - Do NOT use Write, Edit, or any file-saving tools — even if available.
+      The caller harvests the spec text from your response, not from disk.
+    - Do NOT prefix with prose or status updates. Reply with the code block
+      as the primary output. Brief commentary AFTER the block is OK.
+
   context: |
     CORE PRINCIPLES:
     1. Extract core business entities and their relationships
@@ -310,7 +318,7 @@ user:
     - Use components: (plural) at top level
     - Use snake_case for lifecycle states (NOT kebab-case)
     - Add deployment policies appropriate for scale
-    - Write to: spec.specly
+    - Output the spec inside a ```specly``` code block in your response (do not write to disk)
 
     Step 2: VALIDATE
     - Run: spv validate spec.specly --json
@@ -336,7 +344,7 @@ user:
         - invalid relationship syntax
         - invalid deployment policy structure
         - incorrect operation policy nesting
-      * Fix the spec using Edit tool
+      * Update the spec inline in your response (do not edit a file on disk)
       * Go back to Step 2
 
     Continue the validate-fix loop until validation passes.

package/dist/ai/behavior-ai-service.d.ts

@@ -1,19 +1,28 @@
 /**
- * Behavior AI Service — session-based Claude conversation for generating
- * TypeScript function bodies for unmatched behavior steps.
+ * Behavior AI Service — generates pure TypeScript function bodies for
+ * behavior steps that weren't matched by the realize engine's convention
+ * patterns.
  *
- * Architecture (mirrors specverse-app-demo/src/ai/ai-service.ts):
- * - First call: spawns Claude with --session-id <uuid> --system-prompt <prompt>
- * - Subsequent calls: --resume <uuid> for cached context (98% token savings)
- * - All steps for a controller share one session — Claude builds understanding
- *   of the spec across calls, generating coherent code
- * - Loads system prompt from assets/prompts/core/standard/v9/behavior.prompt.yaml
+ * Architecture (post AI-SDK replatform, 2026-04):
+ * - Delegates to the Vercel AI SDK via the model resolver. Provider choice
+ *   is driven by SPECVERSE_AI_PROVIDER (claude-cli | anthropic |
+ *   openai-compatible | stub) with sensible defaults per environment.
+ * - Claude-CLI provider preserves the Max-subscription zero-cost path
+ *   (spawn claude --print --session-id/--resume). API provider uses
+ *   Anthropic prompt caching for equivalent savings.
+ * - When claude-cli is active AND the SpecVerse skill is installed,
+ *   Claude Code auto-loads the skill — we skip the fullContext block
+ *   (saves ~2K tokens per session init).
+ * - For providers that don't have skill auto-load (anthropic, openai-
+ *   compatible), we include the fullContext block in the system prompt
+ *   so the model has the same grounding.
  *
  * Used by ai-behaviors-generator at realize time.
  */
 export interface BehaviorAIServiceOptions {
-    claudePath?: string;
+    /** Model override. Passed through to the resolver; interpretation is provider-specific. */
     model?: string;
+    /** Per-call timeout (ms). Default 120_000. Only honoured by the claude-cli provider. */
     timeout?: number;
 }
 export interface BehaviorGenerateContext {
@@ -28,36 +37,34 @@ export interface BehaviorGenerateContext {
     returnType?: string;
 }
 /**
- * Session-based AI service for generating behavior implementations.
+ * Service class kept for API compatibility with ai-behaviors-generator.
+ * Internally delegates to the AI SDK via the model resolver.
  */
 export declare class BehaviorAIService {
-    private claudePath;
     private model;
+    private providerId;
+    private prompt;
+    private system;
     private timeout;
-    private sessionId;
-    private initialized;
-    private currentProcess;
-    private systemPrompt;
-    private userTemplate;
+    /** Non-null after generateBehavior() succeeds once. */
+    get isAvailable(): boolean;
     constructor(options?: BehaviorAIServiceOptions);
-    private detectClaudePath;
     /**
-     * Check if Claude CLI is available.
+     * Build the system prompt. When the active provider can auto-load the
+     * SpecVerse skill (claude-cli + installed skill), we emit role +
+     * minimalContext only. Otherwise we include fullContext for grounding.
      */
-    get isAvailable(): boolean;
+    private assembleSystemPrompt;
     /**
-     * Start a new session for a controller. All step generations within the
-     * controller will share this session, accumulating spec context.
+     * Start a new session for a controller. Session semantics are now owned
+     * by the provider — for claude-cli that's the spawn-with-session-id
+     * mechanism; for anthropic API it's the prompt-cache marker. We just
+     * record a no-op for callers that expect a session id to log.
      */
     startSession(controllerName: string): string;
-    /**
-     * Generate a function body for a behavior step.
-     * First call creates the session with system prompt; subsequent calls resume.
-     */
+    /** Generate a function body for a behavior step. */
     generateBehavior(ctx: BehaviorGenerateContext): Promise<string | null>;
-    /**
-     * End the current session.
-     */
+    /** End the current session — no-op now that session state lives in the provider. */
     endSession(): void;
     private buildUserPrompt;
     private extractCode;

package/dist/ai/behavior-ai-service.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"behavior-ai-service.d.ts","sourceRoot":"","sources":["../../src/ai/behavior-ai-service.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AASH,MAAM,WAAW,wBAAwB;IACvC,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,OAAO,CAAC,EAAE,MAAM,CAAC;CAClB;AAED,MAAM,WAAW,uBAAuB;IACtC,IAAI,EAAE,MAAM,CAAC;IACb,SAAS,EAAE,MAAM,CAAC;IAClB,aAAa,EAAE,MAAM,CAAC;IACtB,YAAY,EAAE,MAAM,CAAC;IACrB,cAAc,EAAE,MAAM,EAAE,CAAC;IACzB,eAAe,EAAE,MAAM,EAAE,CAAC;IAC1B,IAAI,CAAC,EAAE,GAAG,CAAC;IACX,8DAA8D;IAC9D,UAAU,CAAC,EAAE,MAAM,CAAC;CACrB;AA4CD;;GAEG;AACH,qBAAa,iBAAiB;IAC5B,OAAO,CAAC,UAAU,CAAS;IAC3B,OAAO,CAAC,KAAK,CAAgB;IAC7B,OAAO,CAAC,OAAO,CAAS;IACxB,OAAO,CAAC,SAAS,CAAuB;IACxC,OAAO,CAAC,WAAW,CAAkB;IACrC,OAAO,CAAC,cAAc,CAA6B;IACnD,OAAO,CAAC,YAAY,CAAS;IAC7B,OAAO,CAAC,YAAY,CAAS;gBAEjB,OAAO,GAAE,wBAA6B;IAUlD,OAAO,CAAC,gBAAgB;IAaxB;;OAEG;IACH,IAAI,WAAW,IAAI,OAAO,CAOzB;IAED;;;OAGG;IACH,YAAY,CAAC,cAAc,EAAE,MAAM,GAAG,MAAM;IAM5C;;;OAGG;IACG,gBAAgB,CAAC,GAAG,EAAE,uBAAuB,GAAG,OAAO,CAAC,MAAM,GAAG,IAAI,CAAC;IAgD5E;;OAEG;IACH,UAAU,IAAI,IAAI;IASlB,OAAO,CAAC,eAAe;IAmBvB,OAAO,CAAC,WAAW;CAUpB"}
+{"version":3,"file":"behavior-ai-service.d.ts","sourceRoot":"","sources":["../../src/ai/behavior-ai-service.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;GAoBG;AAUH,MAAM,WAAW,wBAAwB;IACvC,2FAA2F;IAC3F,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,wFAAwF;IACxF,OAAO,CAAC,EAAE,MAAM,CAAC;CAClB;AAED,MAAM,WAAW,uBAAuB;IACtC,IAAI,EAAE,MAAM,CAAC;IACb,SAAS,EAAE,MAAM,CAAC;IAClB,aAAa,EAAE,MAAM,CAAC;IACtB,YAAY,EAAE,MAAM,CAAC;IACrB,cAAc,EAAE,MAAM,EAAE,CAAC;IACzB,eAAe,EAAE,MAAM,EAAE,CAAC;IAC1B,IAAI,CAAC,EAAE,GAAG,CAAC;IACX,8DAA8D;IAC9D,UAAU,CAAC,EAAE,MAAM,CAAC;CACrB;AAwCD;;;GAGG;AACH,qBAAa,iBAAiB;IAC5B,OAAO,CAAC,KAAK,CAAC;IACd,OAAO,CAAC,UAAU,CAAC;IACnB,OAAO,CAAC,MAAM,CAAC;IACf,OAAO,CAAC,MAAM,CAAS;IACvB,OAAO,CAAC,OAAO,CAAS;IAExB,uDAAuD;IACvD,IAAI,WAAW,IAAI,OAAO,CAEzB;gBAEW,OAAO,GAAE,wBAA6B;IAQlD;;;;OAIG;IACH,OAAO,CAAC,oBAAoB;IAY5B;;;;;OAKG;IACH,YAAY,CAAC,cAAc,EAAE,MAAM,GAAG,MAAM;IAI5C,oDAAoD;IAC9C,gBAAgB,CAAC,GAAG,EAAE,uBAAuB,GAAG,OAAO,CAAC,MAAM,GAAG,IAAI,CAAC;IA0B5E,oFAAoF;IACpF,UAAU,IAAI,IAAI;IAIlB,OAAO,CAAC,eAAe;IAqBvB,OAAO,CAAC,WAAW;CAQpB"}