@autobe/agent 0.30.4 → 0.30.5

package/lib/orchestrate/interface/orchestrateInterfaceGroup.js

@@ -68,7 +68,7 @@ function orchestrateInterfaceGroup(ctx, props) {
                             properties: {
                                 thinking: {
                                     type: "string",
-                                    description: "Think before you act.\n\nBefore requesting preliminary data or completing your task, reflect on\nyour current state and explain your reasoning:\n\nFor preliminary requests (getAnalysisSections,\ngetPreviousAnalysisSections, getDatabaseSchemas,\ngetPreviousDatabaseSchemas):\n\n- What critical information is missing that you don't already have?\n- Why do you need it specifically right now?\n- Be brief - state the gap, don't list everything you have.\n\nFor completion (complete):\n\n- What key assets did you acquire?\n- What did you accomplish?\n- Why is it sufficient to complete?\n- Summarize - don't enumerate every single item.\n\nThis reflection helps you avoid duplicate requests and premature\ncompletion."
+                                    description: "Reasoning about your current state: what's missing (preliminary) or what\nyou accomplished (completion)."
                                 },
                                 request: {
                                     oneOf: [
@@ -102,7 +102,7 @@ function orchestrateInterfaceGroup(ctx, props) {
                                             complete: "#/components/schemas/IAutoBeInterfaceGroupApplication.IComplete"
                                         }
                                     },
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval\n(getAnalysisSections, getPreviousAnalysisSections, getDatabaseSchemas,\ngetPreviousDatabaseSchemas) or final group generation (complete). When\npreliminary returns empty array, that type is removed from the union,\nphysically preventing repeated calls."
+                                    description: "Action to perform. Exhausted preliminary types are removed from the\nunion."
                                 }
                             },
                             required: [
@@ -115,7 +115,7 @@ function orchestrateInterfaceGroup(ctx, props) {
                             properties: {
                                 type: {
                                     "const": "getAnalysisSections",
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getAnalysisSections\" indicates this is a preliminary\ndata request for individual analysis sections."
+                                    description: "Type discriminator."
                                 },
                                 sectionIds: {
                                     type: "array",
@@ -125,21 +125,21 @@ function orchestrateInterfaceGroup(ctx, props) {
                                     },
                                     minItems: 1,
                                     maxItems: 100,
-                                    description: "List of section IDs to retrieve.\n\nThese are sequential integer IDs from the analysis sections catalog. Each\nID maps to a specific ### section in the requirements documents.\n\nCRITICAL: DO NOT request the same section IDs that you have already\nrequested in previous calls."
+                                    description: "Section IDs to retrieve. DO NOT request same IDs already requested in\nprevious calls."
                                 }
                             },
                             required: [
                                 "type",
                                 "sectionIds"
                             ],
-                            description: "Request to retrieve individual analysis sections by numeric ID.\n\nInstead of loading entire analysis files (~110-120KB each), this loads\nspecific ### sections (~200-600 words each) identified by integer IDs from\nthe section catalog."
+                            description: "Request to retrieve individual analysis sections by numeric ID."
                         },
                         IAutoBePreliminaryGetDatabaseSchemas: {
                             type: "object",
                             properties: {
                                 type: {
                                     "const": "getDatabaseSchemas",
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getDatabaseSchemas\" indicates this is a preliminary\ndata request for database schemas."
+                                    description: "Type discriminator."
                                 },
                                 schemaNames: {
                                     type: "array",
@@ -147,21 +147,21 @@ function orchestrateInterfaceGroup(ctx, props) {
                                         type: "string"
                                     },
                                     minItems: 1,
-                                    description: "List of database table names to retrieve.\n\nTable names from the database schema representing database entities (e.g.,\n\"user\", \"post\", \"comment\").\n\nCRITICAL: DO NOT request the same schema names that you have already\nrequested in previous calls."
+                                    description: "Database table names to retrieve. DO NOT request same names already\nrequested in previous calls."
                                 }
                             },
                             required: [
                                 "type",
                                 "schemaNames"
                             ],
-                            description: "Request to retrieve database schema definitions for context.\n\nThis type is used in the preliminary phase to request specific database table\nschemas needed for generating type-safe API operations."
+                            description: "Request to retrieve database schema definitions for context."
                         },
                         IAutoBePreliminaryGetPreviousAnalysisSections: {
                             type: "object",
                             properties: {
                                 type: {
                                     "const": "getPreviousAnalysisSections",
-                                    description: "Type discriminator for the request.\n\nValue \"getPreviousAnalysisSections\" indicates this is a preliminary data\nrequest for analysis sections from the previous iteration."
+                                    description: "Type discriminator."
                                 },
                                 sectionIds: {
                                     type: "array",
@@ -170,21 +170,21 @@ function orchestrateInterfaceGroup(ctx, props) {
                                         minimum: 0
                                     },
                                     minItems: 1,
-                                    description: "List of section IDs to retrieve from the previous iteration.\n\nCRITICAL: DO NOT request the same section IDs that you have already\nrequested in previous calls."
+                                    description: "Section IDs to retrieve from previous iteration. DO NOT request same IDs\nalready requested in previous calls."
                                 }
                             },
                             required: [
                                 "type",
                                 "sectionIds"
                             ],
-                            description: "Request to retrieve individual analysis sections from previous iteration by\nnumeric ID.\n\nSame as {@link IAutoBePreliminaryGetAnalysisSections} but for sections from\nthe previous generation cycle, enabling comparison and consistency checks."
+                            description: "Request to retrieve analysis sections from the previous iteration by numeric\nID."
                         },
                         IAutoBePreliminaryGetPreviousDatabaseSchemas: {
                             type: "object",
                             properties: {
                                 type: {
                                     "const": "getPreviousDatabaseSchemas",
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getPreviousDatabaseSchemas\" indicates this is a\npreliminary data request for database schemas from a previous version."
+                                    description: "Type discriminator."
                                 },
                                 schemaNames: {
                                     type: "array",
@@ -192,21 +192,21 @@ function orchestrateInterfaceGroup(ctx, props) {
                                         type: "string"
                                     },
                                     minItems: 1,
-                                    description: "List of database table names to retrieve from the previous version.\n\nThese are table schema names that were generated in a previous version and\nare needed as reference context for the current regeneration.\n\n**Important Notes:**\n\n- These schemas MUST exist in the previous version\n- This function is only available when a previous version exists\n- Used for reference/comparison, not for re-requesting within same execution\n- Table names are in snake_case (e.g., \"shopping_sale\", \"bbs_article\")\n\n**When This Function is Available:**\n\n- When a previous version exists\n- When user requests modifications to existing database schema\n- During correction/regeneration cycles that need previous schema context\n\n**When This Function is NOT Available:**\n\n- During initial generation (no previous version exists)\n- No previous database schemas available for this orchestration task\n\n**Example Table Names:**\n\n- \"users\", \"posts\", \"comments\"\n- \"shopping_sales\", \"shopping_orders\", \"shopping_products\"\n- \"bbs_articles\", \"bbs_article_files\""
+                                    description: "Table names to retrieve from previous iteration. DO NOT request same names\nalready requested in previous calls."
                                 }
                             },
                             required: [
                                 "type",
                                 "schemaNames"
                             ],
-                            description: "Request to retrieve database schemas from a previous version.\n\nThis type is used to load database schema definitions that were generated in\na **previous version** of the AutoBE generation pipeline. This is NOT about\nre-requesting schemas within the same execution, but rather accessing\nartifacts from an earlier version.\n\n**Use Case:** When regenerating or modifying the database schema based on\nuser change requests, agents need to reference the previously generated\ndatabase schemas to understand the existing database structure and what needs\nto be modified.\n\n**Key Difference from `getDatabaseSchemas`:**\n\n- `getDatabaseSchemas`: Fetches schemas from the **current version** (the\n  version being generated right now)\n- `getPreviousDatabaseSchemas`: Fetches schemas from the **previous version**\n  (the last successfully generated version)\n\n**Example Scenario:**\n\n    Initial generation:\n    - DATABASE phase creates: users, posts, comments tables\n    - Generation completes successfully\n\n    User: \"Add email verification status to users\"\n\n    Regeneration:\n    - DATABASE phase starts regeneration\n    - Calls getPreviousDatabaseSchemas([\"users\"])\n      \u2192 Loads the previous version of users table schema\n    - Creates new version with emailVerified field added\n\n**Waterfall + Spiral Pattern:**\n\nThis aligns with AutoBE's regeneration cycles where:\n\n- Compilation failures trigger regeneration with corrections\n- User modifications trigger new versions\n- Previous schemas serve as reference for incremental changes"
+                            description: "Request to retrieve database schemas from the previous iteration.\n\nLoads database table definitions from the last successfully generated\nversion, used as reference context during regeneration or modification\ncycles."
                         },
                         IAutoBePreliminaryGetPreviousInterfaceOperations: {
                             type: "object",
                             properties: {
                                 type: {
                                     "const": "getPreviousInterfaceOperations",
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getPreviousInterfaceOperations\" indicates this is a\npreliminary data request for interface operations from a previous version."
+                                    description: "Type discriminator."
                                 },
                                 endpoints: {
                                     type: "array",
@@ -214,14 +214,14 @@ function orchestrateInterfaceGroup(ctx, props) {
                                         $ref: "#/components/schemas/AutoBeOpenApi.IEndpoint"
                                     },
                                     minItems: 1,
-                                    description: "List of API operation endpoints to retrieve from the previous version.\n\nThese are endpoint identifiers (method + path) that were generated in a\nprevious version and are needed as reference context for the current\nregeneration.\n\n**Important Notes:**\n\n- These endpoints MUST exist in the previous version\n- This function is only available when a previous version exists\n- Used for reference/comparison, not for re-requesting within same execution\n- Each endpoint is identified by: `{method: \"GET|POST|PUT|DELETE|PATCH\",\n  path: \"/api/path\"}`\n\n**When This Function is Available:**\n\n- When a previous version exists\n- When user requests modifications to existing API operations\n- During correction/regeneration cycles that need previous operation context\n\n**When This Function is NOT Available:**\n\n- During initial generation (no previous version exists)\n- No previous interface operations available for this orchestration task\n\n**Endpoint Format:**\n\n- Method: HTTP verb in uppercase (e.g., \"GET\", \"POST\", \"PUT\", \"DELETE\",\n  \"PATCH\")\n- Path: OpenAPI path with parameters (e.g., \"/users/{id}\", \"/posts\")\n\n**Example Endpoints:**\n\n- `{method: \"GET\", path: \"/users/{id}\"}`\n- `{method: \"POST\", path: \"/shoppings/orders\"}`\n- `{method: \"PATCH\", path: \"/bbs/articles\"}`"
+                                    description: "Endpoints to retrieve from previous iteration. DO NOT request same\nendpoints already requested in previous calls."
                                 }
                             },
                             required: [
                                 "type",
                                 "endpoints"
                             ],
-                            description: "Request to retrieve interface operations from a previous version.\n\nThis type is used to load API operation definitions that were generated in a\n**previous version** of the AutoBE generation pipeline. This is NOT about\nre-requesting operations within the same execution, but rather accessing\nartifacts from an earlier version.\n\n**Use Case:** When regenerating or modifying API operations based on user\nchange requests, agents need to reference the previously generated operations\nto understand the existing API design and what needs to be modified.\n\n**Key Difference from `getInterfaceOperations`:**\n\n- `getInterfaceOperations`: Fetches operations from the **current version**\n  (the version being generated right now)\n- `getPreviousInterfaceOperations`: Fetches operations from the **previous\n  version** (the last successfully generated version)\n\n**Example Scenario:**\n\n    Initial generation:\n    - INTERFACE phase creates: GET /users, POST /users, GET /users/{id}\n    - Generation completes successfully\n\n    User: \"Change user creation to require email verification\"\n\n    Regeneration:\n    - INTERFACE phase starts regeneration\n    - Calls getPreviousInterfaceOperations([{method: \"POST\", path: \"/users\"}])\n      \u2192 Loads the previous version of POST /users operation\n    - Creates new version with emailVerification requirement in request body\n\n**Automatic Schema Loading:**\n\nWhen operations are loaded from the previous version, their associated\nrequest/response body schemas are also referenced, providing complete context\nfor understanding the operation's data structures.\n\n**Waterfall + Spiral Pattern:**\n\nThis aligns with AutoBE's regeneration cycles where:\n\n- Compilation failures trigger regeneration with corrections\n- User modifications trigger new versions\n- Previous operations serve as reference for incremental API changes"
+                            description: "Request to retrieve interface operations from the previous iteration.\n\nLoads API operation definitions from the last successfully generated version,\nused as reference context during regeneration or modification cycles."
                         },
                         "AutoBeOpenApi.IEndpoint": {
                             type: "object",
@@ -229,7 +229,7 @@ function orchestrateInterfaceGroup(ctx, props) {
                                 path: {
                                     type: "string",
                                     pattern: "^\\/[a-zA-Z0-9\\/_{}.-]*$",
-                                    description: "HTTP path of the API operation.\n\nThe URL path for accessing this API operation, using path parameters\nenclosed in curly braces (e.g., `/shoppings/customers/sales/{saleId}`).\n\nIt must be corresponded to the {@link parameters path parameters}.\n\nThe path structure should clearly indicate which database entity this\noperation is manipulating, helping to ensure all entities have\nappropriate API coverage.\n\nPath validation rules:\n\n- Must start with a forward slash (/)\n- Can contain only: letters (a-z, A-Z), numbers (0-9), forward slashes (/),\n  curly braces for parameters ({paramName}), hyphens (-), and underscores\n  (_)\n- Parameters must be enclosed in curly braces: {paramName}\n- Resource names should be in camelCase\n- No quotes, spaces, or invalid special characters allowed\n- No domain or role-based prefixes\n\nValid examples:\n\n- \"/users\"\n- \"/users/{userId}\"\n- \"/articles/{articleId}/comments\"\n- \"/attachmentFiles\"\n- \"/orders/{orderId}/items/{itemId}\"\n\nInvalid examples:\n\n- \"'/users'\" (contains quotes)\n- \"/user profile\" (contains space)\n- \"/users/[userId]\" (wrong bracket format)\n- \"/admin/users\" (role prefix)\n- \"/api/v1/users\" (API prefix)"
+                                    description: "HTTP path of the API operation.\n\nMust start with `/`. Parameters use curly braces: `{paramName}`. Resource\nnames in camelCase. No quotes, spaces, role prefixes (`/admin/`), or API\nversion prefixes (`/api/v1/`).\n\nAllowed characters: letters, digits, `/`, `{`, `}`, `-`, `_`, `.`"
                                 },
                                 method: {
                                     oneOf: [
@@ -249,7 +249,7 @@ function orchestrateInterfaceGroup(ctx, props) {
                                             "const": "patch"
                                         }
                                     ],
-                                    description: "HTTP method of the API operation.\n\n**IMPORTANT**: Methods must be written in lowercase only (e.g., \"get\",\nnot \"GET\").\n\nNote that, if the API operation has {@link requestBody}, method must not\nbe `get`.\n\nAlso, even though the API operation has been designed to only get\ninformation, but it needs complicated request information, it must be\ndefined as `patch` method with {@link requestBody} data specification.\n\n- `get`: get information\n- `patch`: get information with complicated request data\n  ({@link requestBody})\n- `post`: create new record\n- `put`: update existing record\n- `delete`: remove record"
+                                    description: "HTTP method (lowercase only).\n\nUse `patch` (not `get`) when a read operation needs a complex\n{@link requestBody}. `get` cannot have a request body."
                                 }
                             },
                             required: [
@@ -263,15 +263,15 @@ function orchestrateInterfaceGroup(ctx, props) {
                             properties: {
                                 type: {
                                     "const": "complete",
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"complete\" indicates this is the final task\nexecution request."
+                                    description: "Type discriminator for completion request."
                                 },
                                 analysis: {
                                     type: "string",
-                                    description: "Analysis of the database schema structure and grouping needs.\n\nBefore designing groups, analyze what you know:\n\n- What namespaces, prefixes, or organizational patterns exist in the DB?\n- Which entities naturally belong together based on table relationships?\n- What business domains or functional areas can be identified?\n- Are there existing interface operations that suggest grouping patterns?"
+                                    description: "Analysis of the database schema structure and grouping needs."
                                 },
                                 rationale: {
                                     type: "string",
-                                    description: "Rationale for the group design decisions.\n\nExplain why you organized groups this way:\n\n- Why did you create each group?\n- What entities are included in each group and why?\n- How does this grouping reflect the database schema structure?\n- What coverage does this provide for all requirements?"
+                                    description: "Rationale for the group design decisions."
                                 },
                                 groups: {
                                     type: "array",
@@ -279,7 +279,7 @@ function orchestrateInterfaceGroup(ctx, props) {
                                         $ref: "#/components/schemas/AutoBeInterfaceGroup"
                                     },
                                     minItems: 1,
-                                    description: "Array of API endpoint groups for organizing development.\n\nDO: Derive groups from database schema organization (namespaces, file\nstructure, table prefixes) rather than arbitrary business domains. DO:\nCreate new groups only when existing schema structure cannot adequately\ncover all requirements. DO: Organize groups around existing database\nschema structure. DO: Provide complete coverage of all entities and\nrequirements without overlap."
+                                    description: "Array of API endpoint groups. Derive from database schema organization\n(namespaces, table prefixes), not arbitrary business domains. Provide\ncomplete coverage without overlap."
                                 }
                             },
                             required: [
@@ -288,25 +288,25 @@ function orchestrateInterfaceGroup(ctx, props) {
                                 "rationale",
                                 "groups"
                             ],
-                            description: "Request to generate API endpoint groups.\n\nExecutes group generation to organize API endpoints based on database\nschema structure."
+                            description: "Request to generate API endpoint groups."
                         },
                         AutoBeInterfaceGroup: {
                             type: "object",
                             properties: {
                                 name: {
                                     type: "string",
-                                    description: "Name identifier for the API endpoint group.\n\nThis name must be derived from the Prisma schema structure following these\npriorities:\n\n1. Prisma namespace names (e.g., `namespace Shopping` \u2192 \"Shopping\")\n2. Schema file names (e.g., `shopping.prisma` \u2192 \"Shopping\")\n3. Table prefix patterns (e.g., `shopping_*` tables \u2192 \"Shopping\")\n\nNames should use PascalCase format and range from 3-50 characters.\nExamples: \"Shopping\", \"BBS\", \"UserManagement\", \"PaymentProcessing\""
+                                    description: "Group name derived from Prisma schema structure (PascalCase).\n\nPriority: 1) namespace names, 2) schema file names, 3) table prefix\npatterns. Examples: \"Shopping\", \"BBS\", \"UserManagement\"."
                                 },
                                 description: {
                                     type: "string",
-                                    description: "Comprehensive description of the API endpoint group's scope and purpose.\n\nThe description must include:\n\n- Schema foundation (namespace, file, or prefix pattern)\n- Specific database entities (table names) covered by this group\n- Functional operations and workflows supported\n- Relationships between entities within the group\n- How requirements map to these schema entities\n\nDescriptions should be 100-2000 characters and focus on concrete schema\nelements rather than abstract business concepts."
+                                    description: "Scope and purpose of this group. Include: schema foundation\n(namespace/file/prefix), specific table names covered, functional\noperations, and entity relationships. 100-2000 characters."
                                 },
                                 databaseSchemas: {
                                     type: "array",
                                     items: {
                                         type: "string"
                                     },
-                                    description: "List of Prisma schema model names required for implementing endpoints in\nthis group.\n\nThis field pre-identifies all database models that are relevant to this\nendpoint group, reducing the cognitive load on the endpoint generation\nagent and enabling more comprehensive endpoint coverage.\n\nThe AI analyzes requirements during group definition phase to determine\nwhich Prisma models are needed for complete API functionality within this\ngroup's domain.\n\nSelection Guidelines:\n\n- Include ALL models that users directly interact with in this domain\n- Include related models needed for complete CRUD operations\n- Include parent/child models for nested endpoint support\n- Include snapshot models if the domain handles versioned data\n- Be thorough - better to include extra models than miss required ones\n\nWhat NOT to Include:\n\n- System-internal tables (audit_logs, system_metrics)\n- Pure cache tables (temporary_cache, session_cache)\n- Framework tables (migrations, schema_versions)"
+                                    description: "Prisma model names needed for this group's endpoints.\n\nInclude ALL models users interact with, related CRUD models, parent/child\nmodels, and snapshot models. Exclude system-internal, cache, and framework\ntables. Be thorough \u2014 include extra rather than miss required ones."
                                 }
                             },
                             required: [
@@ -314,7 +314,7 @@ function orchestrateInterfaceGroup(ctx, props) {
                                 "description",
                                 "databaseSchemas"
                             ],
-                            description: "Interface representing a logical grouping of API endpoints based on Prisma\nschema structure.\n\nThis interface defines organizational units used by the Interface agent to\nmanage API endpoint generation for large-scale projects. Each group\nrepresents a cohesive collection of database entities and their associated\nAPI operations, derived directly from the Prisma schema organization rather\nthan arbitrary business domains.\n\nGroups serve as the foundational organizing principle for:\n\n- Dividing large API specifications into manageable generation cycles\n- Maintaining alignment between API structure and database schema\n- Ensuring complete coverage of all database entities\n- Facilitating modular and scalable API development\n\nThe group structure must strictly follow Prisma schema organization patterns\nsuch as namespaces, file boundaries, or table prefix conventions to ensure\nconsistency between the data model and API design."
+                            description: "Logical grouping of API endpoints based on Prisma schema structure.\n\nGroups divide large API specifications into manageable generation cycles,\nmaintaining alignment between API structure and database schema."
                         }
                     }
                 },
@@ -325,14 +325,13 @@ function orchestrateInterfaceGroup(ctx, props) {
                         parameters: [
                             {
                                 name: "props",
-                                description: " Request containing either preliminary data request or complete\ntask",
                                 required: true,
                                 schema: {
                                     $ref: "#/components/schemas/IAutoBeInterfaceGroupApplication.IProps"
                                 }
                             }
                         ],
-                        description: "Process group generation task or preliminary data requests.\n\nGenerate logical groups for organizing API endpoint creation based on\ndatabase schema structure. Processes group generation with incremental\ncontext loading to ensure comprehensive organization."
+                        description: "Process task or retrieve preliminary data."
                     }
                 ]
             },
@@ -689,11 +688,11 @@ function createController(props) {
                     type: "object",
                     properties: {
                         thinking: {
-                            description: "Think before you act.\n\nBefore requesting preliminary data or completing your task, reflect on\nyour current state and explain your reasoning:\n\nFor preliminary requests (getAnalysisSections,\ngetPreviousAnalysisSections, getDatabaseSchemas,\ngetPreviousDatabaseSchemas):\n\n- What critical information is missing that you don't already have?\n- Why do you need it specifically right now?\n- Be brief - state the gap, don't list everything you have.\n\nFor completion (complete):\n\n- What key assets did you acquire?\n- What did you accomplish?\n- Why is it sufficient to complete?\n- Summarize - don't enumerate every single item.\n\nThis reflection helps you avoid duplicate requests and premature\ncompletion.",
+                            description: "Reasoning about your current state: what's missing (preliminary) or what\nyou accomplished (completion).",
                             type: "string"
                         },
                         request: {
-                            description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval\n(getAnalysisSections, getPreviousAnalysisSections, getDatabaseSchemas,\ngetPreviousDatabaseSchemas) or final group generation (complete). When\npreliminary returns empty array, that type is removed from the union,\nphysically preventing repeated calls.",
+                            description: "Action to perform. Exhausted preliminary types are removed from the\nunion.",
                             anyOf: [
                                 {
                                     $ref: "#/$defs/IAutoBePreliminaryGetAnalysisSections"
@@ -734,18 +733,18 @@ function createController(props) {
                     additionalProperties: false,
                     $defs: {
                         IAutoBePreliminaryGetAnalysisSections: {
-                            description: "Request to retrieve individual analysis sections by numeric ID.\n\nInstead of loading entire analysis files (~110-120KB each), this loads\nspecific ### sections (~200-600 words each) identified by integer IDs from\nthe section catalog.",
+                            description: "Request to retrieve individual analysis sections by numeric ID.",
                             type: "object",
                             properties: {
                                 type: {
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getAnalysisSections\" indicates this is a preliminary\ndata request for individual analysis sections.",
+                                    description: "Type discriminator.",
                                     type: "string",
                                     "enum": [
                                         "getAnalysisSections"
                                     ]
                                 },
                                 sectionIds: {
-                                    description: "List of section IDs to retrieve.\n\nThese are sequential integer IDs from the analysis sections catalog. Each\nID maps to a specific ### section in the requirements documents.\n\nCRITICAL: DO NOT request the same section IDs that you have already\nrequested in previous calls.",
+                                    description: "Section IDs to retrieve. DO NOT request same IDs already requested in\nprevious calls.",
                                     type: "array",
                                     items: {
                                         type: "integer",
@@ -761,18 +760,18 @@ function createController(props) {
                             ]
                         },
                         IAutoBePreliminaryGetDatabaseSchemas: {
-                            description: "Request to retrieve database schema definitions for context.\n\nThis type is used in the preliminary phase to request specific database table\nschemas needed for generating type-safe API operations.",
+                            description: "Request to retrieve database schema definitions for context.",
                             type: "object",
                             properties: {
                                 type: {
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getDatabaseSchemas\" indicates this is a preliminary\ndata request for database schemas.",
+                                    description: "Type discriminator.",
                                     type: "string",
                                     "enum": [
                                         "getDatabaseSchemas"
                                     ]
                                 },
                                 schemaNames: {
-                                    description: "List of database table names to retrieve.\n\nTable names from the database schema representing database entities (e.g.,\n\"user\", \"post\", \"comment\").\n\nCRITICAL: DO NOT request the same schema names that you have already\nrequested in previous calls.",
+                                    description: "Database table names to retrieve. DO NOT request same names already\nrequested in previous calls.",
                                     type: "array",
                                     items: {
                                         type: "string"
@@ -786,18 +785,18 @@ function createController(props) {
                             ]
                         },
                         IAutoBePreliminaryGetPreviousAnalysisSections: {
-                            description: "Request to retrieve individual analysis sections from previous iteration by\nnumeric ID.\n\nSame as {@link IAutoBePreliminaryGetAnalysisSections} but for sections from\nthe previous generation cycle, enabling comparison and consistency checks.",
+                            description: "Request to retrieve analysis sections from the previous iteration by numeric\nID.",
                             type: "object",
                             properties: {
                                 type: {
-                                    description: "Type discriminator for the request.\n\nValue \"getPreviousAnalysisSections\" indicates this is a preliminary data\nrequest for analysis sections from the previous iteration.",
+                                    description: "Type discriminator.",
                                     type: "string",
                                     "enum": [
                                         "getPreviousAnalysisSections"
                                     ]
                                 },
                                 sectionIds: {
-                                    description: "List of section IDs to retrieve from the previous iteration.\n\nCRITICAL: DO NOT request the same section IDs that you have already\nrequested in previous calls.",
+                                    description: "Section IDs to retrieve from previous iteration. DO NOT request same IDs\nalready requested in previous calls.",
                                     type: "array",
                                     items: {
                                         type: "integer",
@@ -812,18 +811,18 @@ function createController(props) {
                             ]
                         },
                         IAutoBePreliminaryGetPreviousDatabaseSchemas: {
-                            description: "Request to retrieve database schemas from a previous version.\n\nThis type is used to load database schema definitions that were generated in\na **previous version** of the AutoBE generation pipeline. This is NOT about\nre-requesting schemas within the same execution, but rather accessing\nartifacts from an earlier version.\n\n**Use Case:** When regenerating or modifying the database schema based on\nuser change requests, agents need to reference the previously generated\ndatabase schemas to understand the existing database structure and what needs\nto be modified.\n\n**Key Difference from `getDatabaseSchemas`:**\n\n- `getDatabaseSchemas`: Fetches schemas from the **current version** (the\n  version being generated right now)\n- `getPreviousDatabaseSchemas`: Fetches schemas from the **previous version**\n  (the last successfully generated version)\n\n**Example Scenario:**\n\n    Initial generation:\n    - DATABASE phase creates: users, posts, comments tables\n    - Generation completes successfully\n\n    User: \"Add email verification status to users\"\n\n    Regeneration:\n    - DATABASE phase starts regeneration\n    - Calls getPreviousDatabaseSchemas([\"users\"])\n      \u2192 Loads the previous version of users table schema\n    - Creates new version with emailVerified field added\n\n**Waterfall + Spiral Pattern:**\n\nThis aligns with AutoBE's regeneration cycles where:\n\n- Compilation failures trigger regeneration with corrections\n- User modifications trigger new versions\n- Previous schemas serve as reference for incremental changes",
+                            description: "Request to retrieve database schemas from the previous iteration.\n\nLoads database table definitions from the last successfully generated\nversion, used as reference context during regeneration or modification\ncycles.",
                             type: "object",
                             properties: {
                                 type: {
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getPreviousDatabaseSchemas\" indicates this is a\npreliminary data request for database schemas from a previous version.",
+                                    description: "Type discriminator.",
                                     type: "string",
                                     "enum": [
                                         "getPreviousDatabaseSchemas"
                                     ]
                                 },
                                 schemaNames: {
-                                    description: "List of database table names to retrieve from the previous version.\n\nThese are table schema names that were generated in a previous version and\nare needed as reference context for the current regeneration.\n\n**Important Notes:**\n\n- These schemas MUST exist in the previous version\n- This function is only available when a previous version exists\n- Used for reference/comparison, not for re-requesting within same execution\n- Table names are in snake_case (e.g., \"shopping_sale\", \"bbs_article\")\n\n**When This Function is Available:**\n\n- When a previous version exists\n- When user requests modifications to existing database schema\n- During correction/regeneration cycles that need previous schema context\n\n**When This Function is NOT Available:**\n\n- During initial generation (no previous version exists)\n- No previous database schemas available for this orchestration task\n\n**Example Table Names:**\n\n- \"users\", \"posts\", \"comments\"\n- \"shopping_sales\", \"shopping_orders\", \"shopping_products\"\n- \"bbs_articles\", \"bbs_article_files\"",
+                                    description: "Table names to retrieve from previous iteration. DO NOT request same names\nalready requested in previous calls.",
                                     type: "array",
                                     items: {
                                         type: "string"
@@ -837,18 +836,18 @@ function createController(props) {
                             ]
                         },
                         IAutoBePreliminaryGetPreviousInterfaceOperations: {
-                            description: "Request to retrieve interface operations from a previous version.\n\nThis type is used to load API operation definitions that were generated in a\n**previous version** of the AutoBE generation pipeline. This is NOT about\nre-requesting operations within the same execution, but rather accessing\nartifacts from an earlier version.\n\n**Use Case:** When regenerating or modifying API operations based on user\nchange requests, agents need to reference the previously generated operations\nto understand the existing API design and what needs to be modified.\n\n**Key Difference from `getInterfaceOperations`:**\n\n- `getInterfaceOperations`: Fetches operations from the **current version**\n  (the version being generated right now)\n- `getPreviousInterfaceOperations`: Fetches operations from the **previous\n  version** (the last successfully generated version)\n\n**Example Scenario:**\n\n    Initial generation:\n    - INTERFACE phase creates: GET /users, POST /users, GET /users/{id}\n    - Generation completes successfully\n\n    User: \"Change user creation to require email verification\"\n\n    Regeneration:\n    - INTERFACE phase starts regeneration\n    - Calls getPreviousInterfaceOperations([{method: \"POST\", path: \"/users\"}])\n      \u2192 Loads the previous version of POST /users operation\n    - Creates new version with emailVerification requirement in request body\n\n**Automatic Schema Loading:**\n\nWhen operations are loaded from the previous version, their associated\nrequest/response body schemas are also referenced, providing complete context\nfor understanding the operation's data structures.\n\n**Waterfall + Spiral Pattern:**\n\nThis aligns with AutoBE's regeneration cycles where:\n\n- Compilation failures trigger regeneration with corrections\n- User modifications trigger new versions\n- Previous operations serve as reference for incremental API changes",
+                            description: "Request to retrieve interface operations from the previous iteration.\n\nLoads API operation definitions from the last successfully generated version,\nused as reference context during regeneration or modification cycles.",
                             type: "object",
                             properties: {
                                 type: {
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getPreviousInterfaceOperations\" indicates this is a\npreliminary data request for interface operations from a previous version.",
+                                    description: "Type discriminator.",
                                     type: "string",
                                     "enum": [
                                         "getPreviousInterfaceOperations"
                                     ]
                                 },
                                 endpoints: {
-                                    description: "List of API operation endpoints to retrieve from the previous version.\n\nThese are endpoint identifiers (method + path) that were generated in a\nprevious version and are needed as reference context for the current\nregeneration.\n\n**Important Notes:**\n\n- These endpoints MUST exist in the previous version\n- This function is only available when a previous version exists\n- Used for reference/comparison, not for re-requesting within same execution\n- Each endpoint is identified by: `{method: \"GET|POST|PUT|DELETE|PATCH\",\n  path: \"/api/path\"}`\n\n**When This Function is Available:**\n\n- When a previous version exists\n- When user requests modifications to existing API operations\n- During correction/regeneration cycles that need previous operation context\n\n**When This Function is NOT Available:**\n\n- During initial generation (no previous version exists)\n- No previous interface operations available for this orchestration task\n\n**Endpoint Format:**\n\n- Method: HTTP verb in uppercase (e.g., \"GET\", \"POST\", \"PUT\", \"DELETE\",\n  \"PATCH\")\n- Path: OpenAPI path with parameters (e.g., \"/users/{id}\", \"/posts\")\n\n**Example Endpoints:**\n\n- `{method: \"GET\", path: \"/users/{id}\"}`\n- `{method: \"POST\", path: \"/shoppings/orders\"}`\n- `{method: \"PATCH\", path: \"/bbs/articles\"}`",
+                                    description: "Endpoints to retrieve from previous iteration. DO NOT request same\nendpoints already requested in previous calls.",
                                     type: "array",
                                     items: {
                                         $ref: "#/$defs/AutoBeOpenApi.IEndpoint"
@@ -866,12 +865,12 @@ function createController(props) {
                             type: "object",
                             properties: {
                                 path: {
-                                    description: "HTTP path of the API operation.\n\nThe URL path for accessing this API operation, using path parameters\nenclosed in curly braces (e.g., `/shoppings/customers/sales/{saleId}`).\n\nIt must be corresponded to the {@link parameters path parameters}.\n\nThe path structure should clearly indicate which database entity this\noperation is manipulating, helping to ensure all entities have\nappropriate API coverage.\n\nPath validation rules:\n\n- Must start with a forward slash (/)\n- Can contain only: letters (a-z, A-Z), numbers (0-9), forward slashes (/),\n  curly braces for parameters ({paramName}), hyphens (-), and underscores\n  (_)\n- Parameters must be enclosed in curly braces: {paramName}\n- Resource names should be in camelCase\n- No quotes, spaces, or invalid special characters allowed\n- No domain or role-based prefixes\n\nValid examples:\n\n- \"/users\"\n- \"/users/{userId}\"\n- \"/articles/{articleId}/comments\"\n- \"/attachmentFiles\"\n- \"/orders/{orderId}/items/{itemId}\"\n\nInvalid examples:\n\n- \"'/users'\" (contains quotes)\n- \"/user profile\" (contains space)\n- \"/users/[userId]\" (wrong bracket format)\n- \"/admin/users\" (role prefix)\n- \"/api/v1/users\" (API prefix)",
+                                    description: "HTTP path of the API operation.\n\nMust start with `/`. Parameters use curly braces: `{paramName}`. Resource\nnames in camelCase. No quotes, spaces, role prefixes (`/admin/`), or API\nversion prefixes (`/api/v1/`).\n\nAllowed characters: letters, digits, `/`, `{`, `}`, `-`, `_`, `.`",
                                     type: "string",
                                     pattern: "^\\/[a-zA-Z0-9\\/_{}.-]*$"
                                 },
                                 method: {
-                                    description: "HTTP method of the API operation.\n\n**IMPORTANT**: Methods must be written in lowercase only (e.g., \"get\",\nnot \"GET\").\n\nNote that, if the API operation has {@link requestBody}, method must not\nbe `get`.\n\nAlso, even though the API operation has been designed to only get\ninformation, but it needs complicated request information, it must be\ndefined as `patch` method with {@link requestBody} data specification.\n\n- `get`: get information\n- `patch`: get information with complicated request data\n  ({@link requestBody})\n- `post`: create new record\n- `put`: update existing record\n- `delete`: remove record",
+                                    description: "HTTP method (lowercase only).\n\nUse `patch` (not `get`) when a read operation needs a complex\n{@link requestBody}. `get` cannot have a request body.",
                                     type: "string",
                                     "enum": [
                                         "get",
@@ -888,26 +887,26 @@ function createController(props) {
                             ]
                         },
                         "IAutoBeInterfaceGroupApplication.IComplete": {
-                            description: "Request to generate API endpoint groups.\n\nExecutes group generation to organize API endpoints based on database\nschema structure.",
+                            description: "Request to generate API endpoint groups.",
                             type: "object",
                             properties: {
                                 type: {
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"complete\" indicates this is the final task\nexecution request.",
+                                    description: "Type discriminator for completion request.",
                                     type: "string",
                                     "enum": [
                                         "complete"
                                     ]
                                 },
                                 analysis: {
-                                    description: "Analysis of the database schema structure and grouping needs.\n\nBefore designing groups, analyze what you know:\n\n- What namespaces, prefixes, or organizational patterns exist in the DB?\n- Which entities naturally belong together based on table relationships?\n- What business domains or functional areas can be identified?\n- Are there existing interface operations that suggest grouping patterns?",
+                                    description: "Analysis of the database schema structure and grouping needs.",
                                     type: "string"
                                 },
                                 rationale: {
-                                    description: "Rationale for the group design decisions.\n\nExplain why you organized groups this way:\n\n- Why did you create each group?\n- What entities are included in each group and why?\n- How does this grouping reflect the database schema structure?\n- What coverage does this provide for all requirements?",
+                                    description: "Rationale for the group design decisions.",
                                     type: "string"
                                 },
                                 groups: {
-                                    description: "Array of API endpoint groups for organizing development.\n\nDO: Derive groups from database schema organization (namespaces, file\nstructure, table prefixes) rather than arbitrary business domains. DO:\nCreate new groups only when existing schema structure cannot adequately\ncover all requirements. DO: Organize groups around existing database\nschema structure. DO: Provide complete coverage of all entities and\nrequirements without overlap.",
+                                    description: "Array of API endpoint groups. Derive from database schema organization\n(namespaces, table prefixes), not arbitrary business domains. Provide\ncomplete coverage without overlap.",
                                     type: "array",
                                     items: {
                                         $ref: "#/$defs/AutoBeInterfaceGroup"
@@ -923,19 +922,19 @@ function createController(props) {
                             ]
                         },
                         AutoBeInterfaceGroup: {
-                            description: "Interface representing a logical grouping of API endpoints based on Prisma\nschema structure.\n\nThis interface defines organizational units used by the Interface agent to\nmanage API endpoint generation for large-scale projects. Each group\nrepresents a cohesive collection of database entities and their associated\nAPI operations, derived directly from the Prisma schema organization rather\nthan arbitrary business domains.\n\nGroups serve as the foundational organizing principle for:\n\n- Dividing large API specifications into manageable generation cycles\n- Maintaining alignment between API structure and database schema\n- Ensuring complete coverage of all database entities\n- Facilitating modular and scalable API development\n\nThe group structure must strictly follow Prisma schema organization patterns\nsuch as namespaces, file boundaries, or table prefix conventions to ensure\nconsistency between the data model and API design.",
+                            description: "Logical grouping of API endpoints based on Prisma schema structure.\n\nGroups divide large API specifications into manageable generation cycles,\nmaintaining alignment between API structure and database schema.",
                             type: "object",
                             properties: {
                                 name: {
-                                    description: "Name identifier for the API endpoint group.\n\nThis name must be derived from the Prisma schema structure following these\npriorities:\n\n1. Prisma namespace names (e.g., `namespace Shopping` \u2192 \"Shopping\")\n2. Schema file names (e.g., `shopping.prisma` \u2192 \"Shopping\")\n3. Table prefix patterns (e.g., `shopping_*` tables \u2192 \"Shopping\")\n\nNames should use PascalCase format and range from 3-50 characters.\nExamples: \"Shopping\", \"BBS\", \"UserManagement\", \"PaymentProcessing\"",
+                                    description: "Group name derived from Prisma schema structure (PascalCase).\n\nPriority: 1) namespace names, 2) schema file names, 3) table prefix\npatterns. Examples: \"Shopping\", \"BBS\", \"UserManagement\".",
                                     type: "string"
                                 },
                                 description: {
-                                    description: "Comprehensive description of the API endpoint group's scope and purpose.\n\nThe description must include:\n\n- Schema foundation (namespace, file, or prefix pattern)\n- Specific database entities (table names) covered by this group\n- Functional operations and workflows supported\n- Relationships between entities within the group\n- How requirements map to these schema entities\n\nDescriptions should be 100-2000 characters and focus on concrete schema\nelements rather than abstract business concepts.",
+                                    description: "Scope and purpose of this group. Include: schema foundation\n(namespace/file/prefix), specific table names covered, functional\noperations, and entity relationships. 100-2000 characters.",
                                     type: "string"
                                 },
                                 databaseSchemas: {
-                                    description: "List of Prisma schema model names required for implementing endpoints in\nthis group.\n\nThis field pre-identifies all database models that are relevant to this\nendpoint group, reducing the cognitive load on the endpoint generation\nagent and enabling more comprehensive endpoint coverage.\n\nThe AI analyzes requirements during group definition phase to determine\nwhich Prisma models are needed for complete API functionality within this\ngroup's domain.\n\nSelection Guidelines:\n\n- Include ALL models that users directly interact with in this domain\n- Include related models needed for complete CRUD operations\n- Include parent/child models for nested endpoint support\n- Include snapshot models if the domain handles versioned data\n- Be thorough - better to include extra models than miss required ones\n\nWhat NOT to Include:\n\n- System-internal tables (audit_logs, system_metrics)\n- Pure cache tables (temporary_cache, session_cache)\n- Framework tables (migrations, schema_versions)",
+                                    description: "Prisma model names needed for this group's endpoints.\n\nInclude ALL models users interact with, related CRUD models, parent/child\nmodels, and snapshot models. Exclude system-internal, cache, and framework\ntables. Be thorough \u2014 include extra rather than miss required ones.",
                                     type: "array",
                                     items: {
                                         type: "string"
@@ -950,7 +949,7 @@ function createController(props) {
                         }
                     }
                 },
-                description: "Process group generation task or preliminary data requests.\n\nGenerate logical groups for organizing API endpoint creation based on\ndatabase schema structure. Processes group generation with incremental\ncontext loading to ensure comprehensive organization.",
+                description: "Process task or retrieve preliminary data.",
                 validate: (() => { const _io0 = input => "string" === typeof input.thinking && ("object" === typeof input.request && null !== input.request && _iu0(input.request)); const _io1 = input => "getAnalysisSections" === input.type && (Array.isArray(input.sectionIds) && (1 <= input.sectionIds.length && input.sectionIds.length <= 100 && input.sectionIds.every(elem => "number" === typeof elem && __typia_transform__isTypeUint32._isTypeUint32(elem)))); const _io2 = input => "getDatabaseSchemas" === input.type && (Array.isArray(input.schemaNames) && (1 <= input.schemaNames.length && input.schemaNames.every(elem => "string" === typeof elem))); const _io3 = input => "getPreviousAnalysisSections" === input.type && (Array.isArray(input.sectionIds) && (1 <= input.sectionIds.length && input.sectionIds.every(elem => "number" === typeof elem && __typia_transform__isTypeUint32._isTypeUint32(elem)))); const _io4 = input => "getPreviousDatabaseSchemas" === input.type && (Array.isArray(input.schemaNames) && (1 <= input.schemaNames.length && input.schemaNames.every(elem => "string" === typeof elem))); const _io5 = input => "getPreviousInterfaceOperations" === input.type && (Array.isArray(input.endpoints) && (1 <= input.endpoints.length && input.endpoints.every(elem => "object" === typeof elem && null !== elem && _io6(elem)))); const _io6 = input => "string" === typeof input.path && RegExp("^\\/[a-zA-Z0-9\\/_{}.-]*$").test(input.path) && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method); const _io7 = input => "complete" === input.type && "string" === typeof input.analysis && "string" === typeof input.rationale && (Array.isArray(input.groups) && (1 <= input.groups.length && input.groups.every(elem => "object" === typeof elem && null !== elem && _io8(elem)))); const _io8 = input => "string" === typeof input.name && "string" === typeof input.description && (Array.isArray(input.databaseSchemas) && input.databaseSchemas.every(elem => "string" === typeof elem)); const _iu0 = input => (() => {
                     if ("getAnalysisSections" === input.type)
                         return _io1(input);

package/lib/orchestrate/interface/orchestrateInterfaceGroup.js.map

@@ -1 +1 @@
-{"version":3,"file":"orchestrateInterfaceGroup.js","sourceRoot":"","sources":["../../../src/orchestrate/interface/orchestrateInterfaceGroup.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAgBA,8DAoEC;;;;AA9ED,yCAA2C;AAE3C,kDAA4D;AAC5D,+BAA0B;AAG1B,uFAAoF;AACpF,+FAA4F;AAG5F,SAAsB,yBAAyB,CAC7C,GAAkB,EAClB,KAEC;;QAED,MAAM,KAAK,GAAS,IAAI,IAAI,EAAE,CAAC;QAC/B,MAAM,MAAM,GAAiC,GAAG,CAAC,KAAK,EAAE,CAAC,QAAQ,CAAC;QAClE,MAAM,WAAW,GAMb,IAAI,yDAA2B,CAAC;YAClC,WAAW;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;aAA4D;YACvE,MAAM,EAAE,MAAM;YACd,KAAK,EAAE;gBACL,kBAAkB;gBAClB,iBAAiB;gBACjB,0BAA0B;gBAC1B,yBAAyB;gBACzB,6BAA6B;aAC9B;YACD,KAAK,EAAE,GAAG,CAAC,KAAK,EAAE;SACnB,CAAC,CAAC;QACH,OAAO,MAAM,WAAW,CAAC,WAAW,CAAC,GAAG,EAAE,CAAO,GAAG,EAAE,EAAE;;YACtD,MAAM,OAAO,GACX;gBACE,KAAK,EAAE,IAAI;aACZ,CAAC;YACJ,MAAM,MAAM,GAA0B,MAAM,GAAG,CAAC,UAAU,iBACxD,MAAM,EAAE,MAAM,EACd,UAAU,EAAE,gBAAgB,CAAC;oBAC3B,OAAO;oBACP,WAAW;oBACX,eAAe,EAAE,IAAI,GAAG,CACtB,MAAM,KAAK,IAAI;wBACb,CAAC,CAAC,MAAM,CAAC,MAAM,CAAC,IAAI,CAAC,KAAK;6BACrB,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC;6BACpB,IAAI,EAAE;6BACN,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC;wBACvB,CAAC,CAAC,EAAE,CACP;iBACF,CAAC,EACF,mBAAmB,EAAE,IAAI,IACtB,IAAA,+DAA8B,EAAC;gBAChC,KAAK,EAAE,GAAG,CAAC,KAAK,EAAE;gBAClB,WAAW,EAAE,KAAK,CAAC,WAAW;gBAC9B,WAAW;aACZ,CAAC,EACF,CAAC;YACH,IAAI,OAAO,CAAC,KAAK,KAAK,IAAI;gBAAE,OAAO,GAAG,CAAC,MAAM,CAAC,CAAC,IAAI,CAAC,CAAC;YAErD,MAAM,KAAK,GAA8B;gBACvC,IAAI,EAAE,MAAM;gBACZ,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,QAAQ,EAAE,OAAO,CAAC,KAAK,CAAC,QAAQ;gBAChC,SAAS,EAAE,OAAO,CAAC,KAAK,CAAC,SAAS;gBAClC,UAAU,EAAE,KAAK,CAAC,WAAW,EAAE;gBAC/B,MAAM,EAAE,OAAO,CAAC,KAAK,CAAC,MAAM;gBAC5B,WAAW,EAAE,WAAW,CAAC,cAAc,EAAE;gBACzC,MAAM,EAAE,MAAM,CAAC,MAAM;gBACrB,UAAU,EAAE,MAAM,CAAC,UAAU;gBAC7B,IAAI,EAAE,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC;aACrC,CAAC;YACF,OAAO,GAAG,CAAC,MAAM,CAAC,CAAC,KAAK,CAAC,CAAC;QAC5B,CAAC,CAAA,CAAC,CAAC;IACL,CAAC;CAAA;AAED,SAAS,gBAAgB,CAAC,KAUzB;IACC,MAAM,QAAQ,GAAG,CACf,KAAc,EACwC,EAAE;QACxD,MAAM,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;gBAC8C,KAAK,CAAC,CAAC;QACjE,IAAI,MAAM,CAAC,OAAO,KAAK,KAAK;YAAE,OAAO,MAAM,CAAC;QAE5C,iCAAiC;QACjC,IAAI,MAAM,CAAC,IAAI,CAAC,OAAO,CAAC,IAAI,KAAK,UAAU;YACzC,OAAO,KAAK,CAAC,WAAW,CAAC,QAAQ,CAAC;gBAChC,QAAQ,EAAE,MAAM,CAAC,IAAI,CAAC,QAAQ;gBAC9B,OAAO,EAAE,MAAM,CAAC,IAAI,CAAC,OAAO;aAC7B,CAAC,CAAC;QAEL,sDAAsD;QACtD,MAAM,MAAM,GAAyB,EAAE,CAAC;QACxC,MAAM,CAAC,IAAI,CAAC,OAAO,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC,KAAK,EAAE,CAAC,EAAE,EAAE;YAC9C,KAAK,CAAC,eAAe,CAAC,OAAO,CAAC,CAAC,GAAG,EAAE,CAAC,EAAE,EAAE;gBACvC,IAAI,KAAK,CAAC,eAAe,CAAC,GAAG,CAAC,GAAG,CAAC,KAAK,KAAK;oBAC1C,MAAM,CAAC,IAAI,CAAC;wBACV,QAAQ,EAAE,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,eAAe,CAAC;6BACxC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,IAAI,CAAC,SAAS,CAAC,CAAC,CAAC,CAAC;6BAC7B,IAAI,CAAC,KAAK,CAAC;wBACd,KAAK,EAAE,GAAG;wBACV,IAAI,EAAE,kBAAkB,CAAC,qBAAqB,CAAC,GAAG;wBAClD,WAAW,EAAE,kBAAU,CAAC,IAAI,CAAA;qCACH,GAAG;;;;;;gBAMxB,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,eAAe,CAAC;6BAChC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,KAAK,CAAC,EAAE,CAAC;6BACpB,IAAI,CAAC,IAAI,CAAC;aACd;qBACF,CAAC,CAAC;YACP,CAAC,CAAC,CAAC;QACL,CAAC,CAAC,CAAC;QACH,OAAO,MAAM,CAAC,MAAM,KAAK,CAAC;YACxB,CAAC,CAAC,MAAM;YACR,CAAC,CAAC;gBACE,OAAO,EAAE,KAAK;gBACd,IAAI,EAAE,MAAM,CAAC,IAAI;gBACjB,MAAM;aACP,CAAC;IACR,CAAC,CAAC;IAEF,MAAM,WAAW,GAAoB,KAAK,CAAC,WAAW,CAAC,cAAc;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OACX;QACtD,QAAQ,EAAE;YACR,OAAO,EAAE,QAAQ;SAClB;KACF,EACF,CAAC;IACF,OAAO;QACL,QAAQ,EAAE,OAAO;QACjB,IAAI,EAAE,MAAM;QACZ,WAAW;QACX,OAAO,EAAE;YACP,OAAO,EAAE,CAAC,KAAK,EAAE,EAAE;gBACjB,IAAI,KAAK,CAAC,OAAO,CAAC,IAAI,KAAK,UAAU;oBACnC,KAAK,CAAC,OAAO,CAAC,KAAK,GAAG,KAAK,CAAC,OAAO,CAAC;YACxC,CAAC;SACyC;KAC7C,CAAC;AACJ,CAAC;AAED,MAAM,MAAM,GAAG,gBAA4C,CAAC"}
+{"version":3,"file":"orchestrateInterfaceGroup.js","sourceRoot":"","sources":["../../../src/orchestrate/interface/orchestrateInterfaceGroup.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAgBA,8DAoEC;;;;AA9ED,yCAA2C;AAE3C,kDAA4D;AAC5D,+BAA0B;AAG1B,uFAAoF;AACpF,+FAA4F;AAG5F,SAAsB,yBAAyB,CAC7C,GAAkB,EAClB,KAEC;;QAED,MAAM,KAAK,GAAS,IAAI,IAAI,EAAE,CAAC;QAC/B,MAAM,MAAM,GAAiC,GAAG,CAAC,KAAK,EAAE,CAAC,QAAQ,CAAC;QAClE,MAAM,WAAW,GAMb,IAAI,yDAA2B,CAAC;YAClC,WAAW;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;aAA4D;YACvE,MAAM,EAAE,MAAM;YACd,KAAK,EAAE;gBACL,kBAAkB;gBAClB,iBAAiB;gBACjB,0BAA0B;gBAC1B,yBAAyB;gBACzB,6BAA6B;aAC9B;YACD,KAAK,EAAE,GAAG,CAAC,KAAK,EAAE;SACnB,CAAC,CAAC;QACH,OAAO,MAAM,WAAW,CAAC,WAAW,CAAC,GAAG,EAAE,CAAO,GAAG,EAAE,EAAE;;YACtD,MAAM,OAAO,GACX;gBACE,KAAK,EAAE,IAAI;aACZ,CAAC;YACJ,MAAM,MAAM,GAA0B,MAAM,GAAG,CAAC,UAAU,iBACxD,MAAM,EAAE,MAAM,EACd,UAAU,EAAE,gBAAgB,CAAC;oBAC3B,OAAO;oBACP,WAAW;oBACX,eAAe,EAAE,IAAI,GAAG,CACtB,MAAM,KAAK,IAAI;wBACb,CAAC,CAAC,MAAM,CAAC,MAAM,CAAC,IAAI,CAAC,KAAK;6BACrB,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC;6BACpB,IAAI,EAAE;6BACN,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC;wBACvB,CAAC,CAAC,EAAE,CACP;iBACF,CAAC,EACF,mBAAmB,EAAE,IAAI,IACtB,IAAA,+DAA8B,EAAC;gBAChC,KAAK,EAAE,GAAG,CAAC,KAAK,EAAE;gBAClB,WAAW,EAAE,KAAK,CAAC,WAAW;gBAC9B,WAAW;aACZ,CAAC,EACF,CAAC;YACH,IAAI,OAAO,CAAC,KAAK,KAAK,IAAI;gBAAE,OAAO,GAAG,CAAC,MAAM,CAAC,CAAC,IAAI,CAAC,CAAC;YAErD,MAAM,KAAK,GAA8B;gBACvC,IAAI,EAAE,MAAM;gBACZ,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,QAAQ,EAAE,OAAO,CAAC,KAAK,CAAC,QAAQ;gBAChC,SAAS,EAAE,OAAO,CAAC,KAAK,CAAC,SAAS;gBAClC,UAAU,EAAE,KAAK,CAAC,WAAW,EAAE;gBAC/B,MAAM,EAAE,OAAO,CAAC,KAAK,CAAC,MAAM;gBAC5B,WAAW,EAAE,WAAW,CAAC,cAAc,EAAE;gBACzC,MAAM,EAAE,MAAM,CAAC,MAAM;gBACrB,UAAU,EAAE,MAAM,CAAC,UAAU;gBAC7B,IAAI,EAAE,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC;aACrC,CAAC;YACF,OAAO,GAAG,CAAC,MAAM,CAAC,CAAC,KAAK,CAAC,CAAC;QAC5B,CAAC,CAAA,CAAC,CAAC;IACL,CAAC;CAAA;AAED,SAAS,gBAAgB,CAAC,KAUzB;IACC,MAAM,QAAQ,GAAG,CACf,KAAc,EACwC,EAAE;QACxD,MAAM,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;gBAC8C,KAAK,CAAC,CAAC;QACjE,IAAI,MAAM,CAAC,OAAO,KAAK,KAAK;YAAE,OAAO,MAAM,CAAC;QAE5C,iCAAiC;QACjC,IAAI,MAAM,CAAC,IAAI,CAAC,OAAO,CAAC,IAAI,KAAK,UAAU;YACzC,OAAO,KAAK,CAAC,WAAW,CAAC,QAAQ,CAAC;gBAChC,QAAQ,EAAE,MAAM,CAAC,IAAI,CAAC,QAAQ;gBAC9B,OAAO,EAAE,MAAM,CAAC,IAAI,CAAC,OAAO;aAC7B,CAAC,CAAC;QAEL,sDAAsD;QACtD,MAAM,MAAM,GAAyB,EAAE,CAAC;QACxC,MAAM,CAAC,IAAI,CAAC,OAAO,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC,KAAK,EAAE,CAAC,EAAE,EAAE;YAC9C,KAAK,CAAC,eAAe,CAAC,OAAO,CAAC,CAAC,GAAG,EAAE,CAAC,EAAE,EAAE;gBACvC,IAAI,KAAK,CAAC,eAAe,CAAC,GAAG,CAAC,GAAG,CAAC,KAAK,KAAK;oBAC1C,MAAM,CAAC,IAAI,CAAC;wBACV,QAAQ,EAAE,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,eAAe,CAAC;6BACxC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,IAAI,CAAC,SAAS,CAAC,CAAC,CAAC,CAAC;6BAC7B,IAAI,CAAC,KAAK,CAAC;wBACd,KAAK,EAAE,GAAG;wBACV,IAAI,EAAE,kBAAkB,CAAC,qBAAqB,CAAC,GAAG;wBAClD,WAAW,EAAE,kBAAU,CAAC,IAAI,CAAA;qCACH,GAAG;;;;;;gBAMxB,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,eAAe,CAAC;6BAChC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,KAAK,CAAC,EAAE,CAAC;6BACpB,IAAI,CAAC,IAAI,CAAC;aACd;qBACF,CAAC,CAAC;YACP,CAAC,CAAC,CAAC;QACL,CAAC,CAAC,CAAC;QACH,OAAO,MAAM,CAAC,MAAM,KAAK,CAAC;YACxB,CAAC,CAAC,MAAM;YACR,CAAC,CAAC;gBACE,OAAO,EAAE,KAAK;gBACd,IAAI,EAAE,MAAM,CAAC,IAAI;gBACjB,MAAM;aACP,CAAC;IACR,CAAC,CAAC;IAEF,MAAM,WAAW,GAAoB,KAAK,CAAC,WAAW,CAAC,cAAc;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OACX;QACtD,QAAQ,EAAE;YACR,OAAO,EAAE,QAAQ;SAClB;KACF,EACF,CAAC;IACF,OAAO;QACL,QAAQ,EAAE,OAAO;QACjB,IAAI,EAAE,MAAM;QACZ,WAAW;QACX,OAAO,EAAE;YACP,OAAO,EAAE,CAAC,KAAK,EAAE,EAAE;gBACjB,IAAI,KAAK,CAAC,OAAO,CAAC,IAAI,KAAK,UAAU;oBACnC,KAAK,CAAC,OAAO,CAAC,KAAK,GAAG,KAAK,CAAC,OAAO,CAAC;YACxC,CAAC;SACyC;KAC7C,CAAC;AACJ,CAAC;AAED,MAAM,MAAM,GAAG,gBAA4C,CAAC"}