@autobe/agent 0.30.4-dev.20260324 → 0.30.5

package/lib/orchestrate/interface/orchestrateInterfaceSchemaWrite.js

@@ -119,7 +119,7 @@ function process(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, getDatabaseSchemas, etc.):\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: [
@@ -161,7 +161,7 @@ function process(ctx, props) {
                                             complete: "#/components/schemas/IAutoBeInterfaceSchemaApplication.IComplete"
                                         }
                                     },
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval\n(getAnalysisSections, getDatabaseSchemas, getInterfaceOperations) or\nfinal schema generation (complete). When preliminary returns empty array,\nthat type is removed from the union, physically preventing repeated\ncalls."
+                                    description: "Action to perform. Exhausted preliminary types are removed from the\nunion."
                                 }
                             },
                             required: [
@@ -174,7 +174,7 @@ function process(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",
@@ -184,21 +184,21 @@ function process(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",
@@ -206,21 +206,21 @@ function process(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."
                         },
                         IAutoBePreliminaryGetInterfaceOperations: {
                             type: "object",
                             properties: {
                                 type: {
                                     "const": "getInterfaceOperations",
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getInterfaceOperations\" indicates this is a\npreliminary data request for interface operations."
+                                    description: "Type discriminator."
                                 },
                                 endpoints: {
                                     type: "array",
@@ -228,14 +228,14 @@ function process(ctx, props) {
                                         $ref: "#/components/schemas/AutoBeOpenApi.IEndpoint"
                                     },
                                     minItems: 1,
-                                    description: "List of existing API operation endpoints to retrieve.\n\nOperations that have been generated in previous phases, containing paths,\nmethods, parameters, and request/response bodies.\n\nCRITICAL: DO NOT request the same endpoints that you have already requested\nin previous calls."
+                                    description: "API operation endpoints to retrieve. DO NOT request same endpoints already\nrequested in previous calls."
                                 }
                             },
                             required: [
                                 "type",
                                 "endpoints"
                             ],
-                            description: "Request to retrieve existing interface operations for context.\n\nThis type is used in the preliminary phase to request already-generated API\noperations for review, validation, or complementary generation tasks."
+                            description: "Request to retrieve existing interface operations for context."
                         },
                         "AutoBeOpenApi.IEndpoint": {
                             type: "object",
@@ -243,7 +243,7 @@ function process(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: [
@@ -263,7 +263,7 @@ function process(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: [
@@ -277,7 +277,7 @@ function process(ctx, props) {
                             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",
@@ -286,21 +286,21 @@ function process(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",
@@ -308,21 +308,21 @@ function process(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",
@@ -330,21 +330,21 @@ function process(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."
                         },
                         IAutoBePreliminaryGetPreviousInterfaceSchemas: {
                             type: "object",
                             properties: {
                                 type: {
                                     "const": "getPreviousInterfaceSchemas",
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getPreviousInterfaceSchemas\" indicates this is a\npreliminary data request for interface schemas from a previous version."
+                                    description: "Type discriminator."
                                 },
                                 typeNames: {
                                     type: "array",
@@ -352,33 +352,33 @@ function process(ctx, props) {
                                         type: "string"
                                     },
                                     minItems: 1,
-                                    description: "List of schema type names to retrieve from the previous version.\n\nThese are type names from the OpenAPI components.schemas section that were\ngenerated in a previous version and are needed as reference context for the\ncurrent regeneration.\n\n**Important Notes:**\n\n- These type names 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- Type names follow TypeScript interface naming (e.g., \"IUser\",\n  \"IUser.ICreate\")\n\n**When This Function is Available:**\n\n- When a previous version exists\n- When user requests modifications to existing API schemas\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 interface schemas available for this orchestration task\n\n**Type Name Examples:**\n\n- Base entity: \"IShoppingSale\", \"IBbsArticle\", \"IUser\"\n- Create DTO: \"IShoppingSale.ICreate\", \"IBbsArticle.ICreate\"\n- Update DTO: \"IShoppingSale.IUpdate\", \"IUser.IUpdate\"\n- Paginated: \"IPageIShoppingSale\", \"IPageIBbsArticle\"\n- Summary: \"IShoppingSale.ISummary\", \"IBbsArticle.ISummary\""
+                                    description: "Schema type names to retrieve from previous iteration. DO NOT request same\nnames already requested in previous calls."
                                 }
                             },
                             required: [
                                 "type",
                                 "typeNames"
                             ],
-                            description: "Request to retrieve interface schemas from a previous version.\n\nThis type is used to load OpenAPI schema definitions (DTOs from\ncomponents.schemas) that were generated in a **previous version** of the\nAutoBE generation pipeline. This is NOT about re-requesting schemas within\nthe same execution, but rather accessing artifacts from an earlier version.\n\n**Use Case:** When regenerating or modifying API schemas based on user change\nrequests, agents need to reference the previously generated schemas to\nunderstand the existing DTO structure and what needs to be modified.\n\n**Key Difference from `getInterfaceSchemas`:**\n\n- `getInterfaceSchemas`: Fetches schemas from the **current version** (the\n  version being generated right now)\n- `getPreviousInterfaceSchemas`: Fetches schemas from the **previous version**\n  (the last successfully generated version)\n\n**Example Scenario:**\n\n    Initial generation:\n    - INTERFACE phase creates: IUser, IUser.ICreate, IUser.IUpdate, IPost\n    - Generation completes successfully\n\n    User: \"Add phone number to user profile\"\n\n    Regeneration:\n    - INTERFACE phase starts regeneration\n    - Calls getPreviousInterfaceSchemas([\"IUser\", \"IUser.IUpdate\"])\n      \u2192 Loads the previous versions of these schemas\n    - Creates new versions with phoneNumber property added\n\n**Automatic Dependency Loading:**\n\nWhen schemas are loaded from the previous version, their referenced schemas\n(via `$ref`) are also available, providing complete type dependency context\nfor understanding the schema structure.\n\n**Schema Type Naming Convention:**\n\n- Entity schemas: `IEntityName` (e.g., \"IUser\", \"IPost\", \"IShoppingSale\")\n- Nested DTOs: `IEntityName.ISubType` (e.g., \"IUser.ICreate\", \"IPost.IUpdate\")\n- Response wrappers: `IPage<IEntityName>` (e.g., \"IPageIUser\", \"IPageIPost\")\n- Summary types: `IEntityName.ISummary` (e.g., \"IBbsArticle.ISummary\")\n- Authorized types: `IEntityName.IAuthorized` (e.g., \"IUser.IAuthorized\")\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 DTO changes"
+                            description: "Request to retrieve interface schemas from the previous iteration.\n\nLoads OpenAPI schema definitions (DTOs) from the last successfully generated\nversion, used as reference context during regeneration or modification\ncycles."
                         },
                         "IAutoBeInterfaceSchemaApplication.IComplete": {
                             type: "object",
                             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 type's purpose and context.\n\nBefore designing the schema, analyze what you know:\n\n- What is this type for? (e.g., IProduct.ICreate is a creation request)\n- What database entities or operations inform its structure?\n- What fields should be included based on the variant type?\n- Are there related types that provide structural hints?"
+                                    description: "Analysis of the type's purpose and context."
                                 },
                                 rationale: {
                                     type: "string",
-                                    description: "Rationale for the schema design decisions.\n\nExplain why you designed the schema this way:\n\n- Which properties did you include and why?\n- What is required vs optional, and why?\n- Which types use $ref and why?\n- What was excluded and why? (e.g., auto-generated fields for ICreate)"
+                                    description: "Rationale for the schema design decisions."
                                 },
                                 design: {
                                     $ref: "#/components/schemas/AutoBeInterfaceSchemaDesign",
-                                    description: "Design structure for the schema being generated.\n\nContains `databaseSchema`, `specification`, `description`, and `schema`\nfields that together define a complete DTO type component."
+                                    description: "Schema design: database mapping, specification, description, and JSON\nSchema."
                                 }
                             },
                             required: [
@@ -387,7 +387,7 @@ function process(ctx, props) {
                                 "rationale",
                                 "design"
                             ],
-                            description: "Request to generate a single OpenAPI schema component.\n\nExecutes schema generation to create a type definition for a specific DTO\ntype. Each invocation handles one schema component to ensure accuracy and\nclear responsibility."
+                            description: "Request to generate a single OpenAPI schema component."
                         },
                         AutoBeInterfaceSchemaDesign: {
                             type: "object",
@@ -401,19 +401,19 @@ function process(ctx, props) {
                                             type: "string"
                                         }
                                     ],
-                                    description: "Database model name that this schema maps to.\n\nSpecifies which database table/model this DTO type corresponds to. Creates\na traceable link between API types and database entities.\n\n- Set to the exact model name (e.g., `\"shopping_customers\"`,\n  `\"bbs_articles\"`) when this schema directly represents or derives from a\n  database entity\n- Set to `null` for:\n\n  - Computed/aggregated types (e.g., statistics, summaries from multiple\n      tables)\n  - Types composed purely by business logic (e.g., search filters, pagination)\n  - Embedded JSON structures without dedicated tables\n\nWhen `null`, the `specification` field becomes critical for downstream\nagents to understand how to implement data retrieval or computation."
+                                    description: "Database model name this schema maps to, or `null` for computed/aggregated\ntypes.\n\nWhen `null`, `specification` becomes critical for downstream agents."
                                 },
                                 specification: {
                                     type: "string",
-                                    description: "Implementation specification for downstream agents.\n\nDetailed guidance on HOW to implement data retrieval, transformation, or\ncomputation for this type. Internal documentation for Realize Agent, Test\nAgent, and other implementation agents - NOT exposed in public API docs.\n\n**When `databaseSchema` is set** (direct mapping):\n\n- Can be brief for simple cases\n- Focus on any non-obvious mapping details\n\n**When `databaseSchema` is `null`** (computed/aggregated types):\n\nThis field is CRITICAL. Must include:\n\n- Source tables and columns involved\n- JOIN conditions between tables\n- Aggregation formulas (SUM, COUNT, AVG, etc.)\n- Business rules and transformation logic\n- Edge cases (nulls, empty sets, defaults)\n\nMust be precise enough for downstream agents to implement the actual data\nretrieval or computation. Vague specifications are unacceptable."
+                                    description: "Implementation guidance for downstream agents (Realize, Test). NOT exposed\nin public API docs.\n\nWhen `databaseSchema` is set: brief mapping details. When `null`: MUST\ninclude source tables, JOINs, aggregation formulas, business rules, and\nedge cases."
                                 },
                                 description: {
                                     type: "string",
-                                    description: "API documentation for consumers.\n\nStandard OpenAPI description displayed in Swagger UI, SDK documentation,\nand other API documentation tools. Focus on explaining WHAT the type\nrepresents and WHY it exists from an API consumer's perspective.\n\nGuidelines:\n\n- Reference corresponding database schema documentation for consistency\n- Organize into multiple paragraphs for complex types\n- Focus on business meaning, relationships, and constraints\n- Keep accessible to API consumers (no implementation details)\n- MUST be written in English"
+                                    description: "API documentation for consumers (Swagger UI). Focus on WHAT the type\nrepresents. Reference DB schema documentation for consistency.\n\n- MUST be written in English"
                                 },
                                 schema: {
                                     $ref: "#/components/schemas/AutoBeOpenApi.IJsonSchema",
-                                    description: "JSON Schema definition for the type.\n\nThe actual type structure following OpenAPI v3.1 JSON Schema specification.\nCan be any valid JSON Schema type: object, array, string, number, integer,\nboolean, oneOf, or $ref.\n\nImportant:\n\n- For union types, use `oneOf` - NEVER use array notation in `type` field\n- For nullable types, use `oneOf: [{ type: \"...\" }, { type: \"null\" }]`\n- Object properties should have clear, descriptive names in camelCase\n- Use `$ref` for referencing other named schemas"
+                                    description: "JSON Schema definition.\n\nFor union/nullable types, use `oneOf` \u2014 NEVER array in `type` field. Use\n`$ref` for referencing named schemas. Object property names in camelCase."
                                 }
                             },
                             required: [
@@ -422,7 +422,7 @@ function process(ctx, props) {
                                 "description",
                                 "schema"
                             ],
-                            description: "Design structure for creating OpenAPI schema components.\n\nSeparates schema metadata from the actual JSON Schema definition, allowing\nclear organization of implementation details (`specification`), API\ndocumentation (`description`), and the type structure (`schema`).\n\nThe `specification` and `description` fields are documented at the design\nlevel, separate from the `schema` field which holds the pure type structure."
+                            description: "Design structure for creating an OpenAPI schema component.\n\nSeparates schema metadata (specification, description) from the JSON Schema\ndefinition (schema)."
                         },
                         "AutoBeOpenApi.IJsonSchema": {
                             oneOf: [
@@ -457,35 +457,30 @@ function process(ctx, props) {
                                     $ref: "#/components/schemas/AutoBeOpenApi.IJsonSchema.INull"
                                 }
                             ],
-                            description: "Type schema info.\n\n`AutoBeOpenApi.IJsonSchema` is a type schema info of the OpenAPI\nGenerative.\n\n`AutoBeOpenApi.IJsonSchema` basically follows the JSON schema specification\nof OpenAPI v3.1, but a little bit shrunk to remove ambiguous and duplicated\nexpressions of OpenAPI v3.1 for the convenience, clarity, and AI\ngeneration.\n\n## CRITICAL: Union Type Expression\n\nIn this type system, union types (including nullable types) MUST be\nexpressed using the `IOneOf` structure. NEVER use array notation in the\n`type` field.\n\n\u274C **FORBIDDEN** - Array notation in type field:\n\n```typescript\n{\n  \"type\": [\"string\", \"null\"] // NEVER DO THIS!\n}\n```\n\n\u2705 **CORRECT** - Using IOneOf for unions:\n\n```typescript\n// For nullable string:\n{\n  oneOf: [{ type: \"string\" }, { type: \"null\" }];\n}\n\n// For string | number union:\n{\n  oneOf: [{ type: \"string\" }, { type: \"number\" }];\n}\n```\n\nThe `type` field in any schema object is a discriminator that identifies\nthe schema type and MUST contain exactly one string value."
+                            description: "JSON Schema type following OpenAPI v3.1 (simplified).\n\nCRITICAL: Union types MUST use `IOneOf`. NEVER use array in `type` field.\n\nWrong: `{ type: [\"string\", \"null\"] }` Correct: `{ oneOf: [{ type: \"string\"\n}, { type: \"null\" }] }`\n\nThe `type` field is a discriminator and MUST be a single string value."
                         },
                         "AutoBeOpenApi.IJsonSchema.IInteger": {
                             type: "object",
                             properties: {
                                 minimum: {
-                                    type: "integer",
-                                    description: "Minimum value restriction."
+                                    type: "integer"
                                 },
                                 maximum: {
-                                    type: "integer",
-                                    description: "Maximum value restriction."
+                                    type: "integer"
                                 },
                                 exclusiveMinimum: {
-                                    type: "integer",
-                                    description: "Exclusive minimum value restriction."
+                                    type: "integer"
                                 },
                                 exclusiveMaximum: {
-                                    type: "integer",
-                                    description: "Exclusive maximum value restriction."
+                                    type: "integer"
                                 },
                                 multipleOf: {
                                     type: "integer",
-                                    exclusiveMinimum: 0,
-                                    description: "Multiple of value restriction."
+                                    exclusiveMinimum: 0
                                 },
                                 type: {
                                     "const": "integer",
-                                    description: "Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n\"boolean\", \"integer\", \"number\", \"string\", \"array\", \"object\", or\n\"null\".\n\n\u274C INCORRECT: type: [\"string\", \"null\"] // This is WRONG! \u2705 CORRECT:\ntype: \"string\" // For nullable string, use oneOf instead\n\nIf you need to express a nullable type (e.g., string | null), you MUST\nuse the `IOneOf` structure:\n\n```typescript\n{\n  \"oneOf\": [{ \"type\": \"string\" }, { \"type\": \"null\" }]\n}\n```\n\nNEVER use array notation in the type field. The type field is a\ndiscriminator that accepts only a single string value."
+                                    description: "Discriminator value. MUST be a single string, NEVER an array.\n\nFor nullable types, use `IOneOf` instead: `{ oneOf: [{ type: \"string\"\n}, { type: \"null\" }] }`"
                                 }
                             },
                             required: [
@@ -497,29 +492,24 @@ function process(ctx, props) {
                             type: "object",
                             properties: {
                                 minimum: {
-                                    type: "number",
-                                    description: "Minimum value restriction."
+                                    type: "number"
                                 },
                                 maximum: {
-                                    type: "number",
-                                    description: "Maximum value restriction."
+                                    type: "number"
                                 },
                                 exclusiveMinimum: {
-                                    type: "number",
-                                    description: "Exclusive minimum value restriction."
+                                    type: "number"
                                 },
                                 exclusiveMaximum: {
-                                    type: "number",
-                                    description: "Exclusive maximum value restriction."
+                                    type: "number"
                                 },
                                 multipleOf: {
                                     type: "number",
-                                    exclusiveMinimum: 0,
-                                    description: "Multiple of value restriction."
+                                    exclusiveMinimum: 0
                                 },
                                 type: {
                                     "const": "number",
-                                    description: "Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n\"boolean\", \"integer\", \"number\", \"string\", \"array\", \"object\", or\n\"null\".\n\n\u274C INCORRECT: type: [\"string\", \"null\"] // This is WRONG! \u2705 CORRECT:\ntype: \"string\" // For nullable string, use oneOf instead\n\nIf you need to express a nullable type (e.g., string | null), you MUST\nuse the `IOneOf` structure:\n\n```typescript\n{\n  \"oneOf\": [{ \"type\": \"string\" }, { \"type\": \"null\" }]\n}\n```\n\nNEVER use array notation in the type field. The type field is a\ndiscriminator that accepts only a single string value."
+                                    description: "Discriminator value. MUST be a single string, NEVER an array.\n\nFor nullable types, use `IOneOf` instead: `{ oneOf: [{ type: \"string\"\n}, { type: \"null\" }] }`"
                                 }
                             },
                             required: [
@@ -604,21 +594,19 @@ function process(ctx, props) {
                                 },
                                 contentMediaType: {
                                     type: "string",
-                                    description: "Content media type restriction.\n\nIf you want to accept multiple contentMediaType values simultaneously\n(e.g., `text/plain` and `text/html`), you MUST NOT violate the type by\nusing an array. Instead, use `oneOf` to define multiple `string`\nschemas with different `contentMediaType` values.\n\nExample for accepting both text/plain and text/html:\n\n```typescript\n{\n  \"oneOf\": [\n    { \"type\": \"string\", \"contentMediaType\": \"text/plain\" },\n    { \"type\": \"string\", \"contentMediaType\": \"text/html\" }\n  ]\n}\n```\n\nThis is the CORRECT approach. Never use array notation or modify the\nsingle string type to accept arrays."
+                                    description: "Content media type restriction.\n\nFor multiple media types, use `oneOf` with separate string schemas per\n`contentMediaType` value. Never use an array here."
                                 },
                                 minLength: {
                                     type: "integer",
-                                    minimum: 0,
-                                    description: "Minimum length restriction."
+                                    minimum: 0
                                 },
                                 maxLength: {
                                     type: "integer",
-                                    minimum: 0,
-                                    description: "Maximum length restriction."
+                                    minimum: 0
                                 },
                                 type: {
                                     "const": "string",
-                                    description: "Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n\"boolean\", \"integer\", \"number\", \"string\", \"array\", \"object\", or\n\"null\".\n\n\u274C INCORRECT: type: [\"string\", \"null\"] // This is WRONG! \u2705 CORRECT:\ntype: \"string\" // For nullable string, use oneOf instead\n\nIf you need to express a nullable type (e.g., string | null), you MUST\nuse the `IOneOf` structure:\n\n```typescript\n{\n  \"oneOf\": [{ \"type\": \"string\" }, { \"type\": \"null\" }]\n}\n```\n\nNEVER use array notation in the type field. The type field is a\ndiscriminator that accepts only a single string value."
+                                    description: "Discriminator value. MUST be a single string, NEVER an array.\n\nFor nullable types, use `IOneOf` instead: `{ oneOf: [{ type: \"string\"\n}, { type: \"null\" }] }`"
                                 }
                             },
                             required: [
@@ -654,7 +642,7 @@ function process(ctx, props) {
                             properties: {
                                 type: {
                                     "const": "boolean",
-                                    description: "Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n\"boolean\", \"integer\", \"number\", \"string\", \"array\", \"object\", or\n\"null\".\n\n\u274C INCORRECT: type: [\"string\", \"null\"] // This is WRONG! \u2705 CORRECT:\ntype: \"string\" // For nullable string, use oneOf instead\n\nIf you need to express a nullable type (e.g., string | null), you MUST\nuse the `IOneOf` structure:\n\n```typescript\n{\n  \"oneOf\": [{ \"type\": \"string\" }, { \"type\": \"null\" }]\n}\n```\n\nNEVER use array notation in the type field. The type field is a\ndiscriminator that accepts only a single string value."
+                                    description: "Discriminator value. MUST be a single string, NEVER an array.\n\nFor nullable types, use `IOneOf` instead: `{ oneOf: [{ type: \"string\"\n}, { type: \"null\" }] }`"
                                 }
                             },
                             required: [
@@ -695,25 +683,23 @@ function process(ctx, props) {
                                             $ref: "#/components/schemas/AutoBeOpenApi.IJsonSchema.IOneOf"
                                         }
                                     ],
-                                    description: "Items type info.\n\nThe `items` means the type of the array elements. In other words, it is\nthe type schema info of the `T` in the TypeScript array type\n`Array<T>`."
+                                    description: "Type schema of array elements."
                                 },
                                 uniqueItems: {
                                     type: "boolean",
-                                    description: "Unique items restriction.\n\nIf this property value is `true`, target array must have unique items."
+                                    description: "If `true`, array elements must be unique."
                                 },
                                 minItems: {
                                     type: "integer",
-                                    minimum: 0,
-                                    description: "Minimum items restriction.\n\nRestriction of minimum number of items in the array."
+                                    minimum: 0
                                 },
                                 maxItems: {
                                     type: "integer",
-                                    minimum: 0,
-                                    description: "Maximum items restriction.\n\nRestriction of maximum number of items in the array."
+                                    minimum: 0
                                 },
                                 type: {
                                     "const": "array",
-                                    description: "Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n\"boolean\", \"integer\", \"number\", \"string\", \"array\", \"object\", or\n\"null\".\n\n\u274C INCORRECT: type: [\"string\", \"null\"] // This is WRONG! \u2705 CORRECT:\ntype: \"string\" // For nullable string, use oneOf instead\n\nIf you need to express a nullable type (e.g., string | null), you MUST\nuse the `IOneOf` structure:\n\n```typescript\n{\n  \"oneOf\": [{ \"type\": \"string\" }, { \"type\": \"null\" }]\n}\n```\n\nNEVER use array notation in the type field. The type field is a\ndiscriminator that accepts only a single string value."
+                                    description: "Discriminator value. MUST be a single string, NEVER an array.\n\nFor nullable types, use `IOneOf` instead: `{ oneOf: [{ type: \"string\"\n}, { type: \"null\" }] }`"
                                 }
                             },
                             required: [
@@ -727,7 +713,7 @@ function process(ctx, props) {
                             properties: {
                                 type: {
                                     "const": "null",
-                                    description: "Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n\"boolean\", \"integer\", \"number\", \"string\", \"array\", \"object\", or\n\"null\".\n\n\u274C INCORRECT: type: [\"string\", \"null\"] // This is WRONG! \u2705 CORRECT:\ntype: \"string\" // For nullable string, use oneOf instead\n\nIf you need to express a nullable type (e.g., string | null), you MUST\nuse the `IOneOf` structure:\n\n```typescript\n{\n  \"oneOf\": [{ \"type\": \"string\" }, { \"type\": \"null\" }]\n}\n```\n\nNEVER use array notation in the type field. The type field is a\ndiscriminator that accepts only a single string value."
+                                    description: "Discriminator value. MUST be a single string, NEVER an array.\n\nFor nullable types, use `IOneOf` instead: `{ oneOf: [{ type: \"string\"\n}, { type: \"null\" }] }`"
                                 }
                             },
                             required: [
@@ -740,7 +726,7 @@ function process(ctx, props) {
                             properties: {
                                 $ref: {
                                     type: "string",
-                                    description: "Reference to the named schema.\n\nThe `ref` is a reference to the named schema. Format of the `$ref` is\nfollowing the JSON Pointer specification. In the OpenAPI, the `$ref`\nstarts with `#/components/schemas/` which means the type is stored in\nthe {@link AutoBeOpenApi.IComponents.schemas} object.\n\n- `#/components/schemas/SomeObject`\n- `#/components/schemas/AnotherObject`"
+                                    description: "JSON Pointer reference to a named schema (e.g.,\n`#/components/schemas/SomeObject`)."
                                 }
                             },
                             required: [
@@ -791,7 +777,7 @@ function process(ctx, props) {
                             required: [
                                 "oneOf"
                             ],
-                            description: "Union type.\n\n`IOneOf` represents an union type of the TypeScript (`A | B | C`).\n\nFor reference, even though your Swagger (or OpenAPI) document has defined\n`anyOf` instead of the `oneOf`, {@link AutoBeOpenApi} forcibly converts it\nto `oneOf` type."
+                            description: "Union type.\n\n`IOneOf` represents a union type in TypeScript (`A | B | C`).\n\nFor reference, even though your Swagger (or OpenAPI) document has defined\n`anyOf` instead of the `oneOf`, {@link AutoBeOpenApi} forcibly converts it\nto `oneOf` type."
                         },
                         "AutoBeOpenApi.IJsonSchema.IOneOf.IDiscriminator": {
                             type: "object",
@@ -802,7 +788,7 @@ function process(ctx, props) {
                                 },
                                 mapping: {
                                     $ref: "#/components/schemas/Recordstringstring",
-                                    description: "Mapping of the discriminator value to the schema name.\n\nThis property is valid only for {@link IReference} typed\n{@link IOneOf.oneof} elements. Therefore, `key` of `mapping` is the\ndiscriminator value, and `value` of `mapping` is the schema name like\n`#/components/schemas/SomeObject`."
+                                    description: "Mapping of the discriminator value to the schema name.\n\nThis property is valid only for {@link IReference} typed\n{@link IOneOf.oneOf} elements. Therefore, `key` of `mapping` is the\ndiscriminator value, and `value` of `mapping` is the schema name like\n`#/components/schemas/SomeObject`."
                                 }
                             },
                             required: [
@@ -824,7 +810,7 @@ function process(ctx, props) {
                             properties: {
                                 properties: {
                                     $ref: "#/components/schemas/RecordstringAutoBeOpenApi.IJsonSchema",
-                                    description: "Properties of the object.\n\nThe `properties` means a list of key-value pairs of the object's\nregular properties. The key is the name of the regular property, and\nthe value is the type schema info.\n\nIf you need additional properties that is represented by dynamic key,\nyou can use the {@link additionalProperties} instead."
+                                    description: "Key-value pairs of the object's named properties."
                                 },
                                 additionalProperties: {
                                     oneOf: [
@@ -859,18 +845,18 @@ function process(ctx, props) {
                                             $ref: "#/components/schemas/AutoBeOpenApi.IJsonSchema.IOneOf"
                                         }
                                     ],
-                                    description: "Additional properties' info.\n\nThe `additionalProperties` means the type schema info of the additional\nproperties that are not listed in the {@link properties}.\n\nIf the value is `false`, it means that the additional properties are\nnot specified. Otherwise, if the value is {@link IJsonSchema} type, it\nmeans that the additional properties must follow the type schema info.\n\n- `false`: No additional properties\n- `IJsonSchema`: `Record<string, T>`"
+                                    description: "Schema for dynamic keys (`Record<string, T>`), or `false` if no\nadditional properties are allowed."
                                 },
                                 required: {
                                     type: "array",
                                     items: {
                                         type: "string"
                                     },
-                                    description: "List of key values of the required properties.\n\nThe `required` means a list of the key values of the required\n{@link properties}. If some property key is not listed in the `required`\nlist, it means that property is optional. Otherwise some property key\nexists in the `required` list, it means that the property must be\nfilled.\n\nBelow is an example of the {@link properties} and `required`.\n\n```typescript\ninterface SomeObject {\n  id: string;\n  email: string;\n  name?: string;\n}\n```\n\nAs you can see, `id` and `email` {@link properties} are {@link required},\nso that they are listed in the `required` list.\n\n```json\n{\n  \"type\": \"object\",\n  \"properties\": {\n    \"id\": { \"type\": \"string\" },\n    \"email\": { \"type\": \"string\" },\n    \"name\": { \"type\": \"string\" }\n  },\n  \"required\": [\"id\", \"email\"]\n}\n```"
+                                    description: "Property keys that must be present. Properties not listed here are\noptional."
                                 },
                                 type: {
                                     "const": "object",
-                                    description: "Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n\"boolean\", \"integer\", \"number\", \"string\", \"array\", \"object\", or\n\"null\".\n\n\u274C INCORRECT: type: [\"string\", \"null\"] // This is WRONG! \u2705 CORRECT:\ntype: \"string\" // For nullable string, use oneOf instead\n\nIf you need to express a nullable type (e.g., string | null), you MUST\nuse the `IOneOf` structure:\n\n```typescript\n{\n  \"oneOf\": [{ \"type\": \"string\" }, { \"type\": \"null\" }]\n}\n```\n\nNEVER use array notation in the type field. The type field is a\ndiscriminator that accepts only a single string value."
+                                    description: "Discriminator value. MUST be a single string, NEVER an array.\n\nFor nullable types, use `IOneOf` instead: `{ oneOf: [{ type: \"string\"\n}, { type: \"null\" }] }`"
                                 }
                             },
                             required: [
@@ -898,14 +884,13 @@ function process(ctx, props) {
                         parameters: [
                             {
                                 name: "props",
-                                description: " Request containing either preliminary data request or complete\ntask",
                                 required: true,
                                 schema: {
                                     $ref: "#/components/schemas/IAutoBeInterfaceSchemaApplication.IProps"
                                 }
                             }
                         ],
-                        description: "Process schema generation task or preliminary data requests.\n\nGenerates OpenAPI components containing named schema types and integrates\nthem into the final OpenAPI specification. Processes all entity schemas,\ntheir variants, and related type definitions to ensure comprehensive and\nconsistent API design."
+                        description: "Process task or retrieve preliminary data."
                     }
                 ]
             },
@@ -1718,11 +1703,11 @@ function createController(ctx, 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, getDatabaseSchemas, etc.):\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, getDatabaseSchemas, getInterfaceOperations) or\nfinal schema generation (complete). When preliminary returns empty array,\nthat type is removed from the union, physically preventing repeated\ncalls.",
+                            description: "Action to perform. Exhausted preliminary types are removed from the\nunion.",
                             anyOf: [
                                 {
                                     $ref: "#/$defs/IAutoBePreliminaryGetAnalysisSections"
@@ -1771,18 +1756,18 @@ function createController(ctx, 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",
@@ -1798,18 +1783,18 @@ function createController(ctx, 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"
@@ -1823,18 +1808,18 @@ function createController(ctx, props) {
                             ]
                         },
                         IAutoBePreliminaryGetInterfaceOperations: {
-                            description: "Request to retrieve existing interface operations for context.\n\nThis type is used in the preliminary phase to request already-generated API\noperations for review, validation, or complementary generation tasks.",
+                            description: "Request to retrieve existing interface operations 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 \"getInterfaceOperations\" indicates this is a\npreliminary data request for interface operations.",
+                                    description: "Type discriminator.",
                                     type: "string",
                                     "enum": [
                                         "getInterfaceOperations"
                                     ]
                                 },
                                 endpoints: {
-                                    description: "List of existing API operation endpoints to retrieve.\n\nOperations that have been generated in previous phases, containing paths,\nmethods, parameters, and request/response bodies.\n\nCRITICAL: DO NOT request the same endpoints that you have already requested\nin previous calls.",
+                                    description: "API operation endpoints to retrieve. DO NOT request same endpoints already\nrequested in previous calls.",
                                     type: "array",
                                     items: {
                                         $ref: "#/$defs/AutoBeOpenApi.IEndpoint"
@@ -1852,12 +1837,12 @@ function createController(ctx, 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",
@@ -1874,18 +1859,18 @@ function createController(ctx, 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",
@@ -1900,18 +1885,18 @@ function createController(ctx, 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"
@@ -1925,18 +1910,18 @@ function createController(ctx, 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"
@@ -1950,18 +1935,18 @@ function createController(ctx, props) {
                             ]
                         },
                         IAutoBePreliminaryGetPreviousInterfaceSchemas: {
-                            description: "Request to retrieve interface schemas from a previous version.\n\nThis type is used to load OpenAPI schema definitions (DTOs from\ncomponents.schemas) that were generated in a **previous version** of the\nAutoBE generation pipeline. This is NOT about re-requesting schemas within\nthe same execution, but rather accessing artifacts from an earlier version.\n\n**Use Case:** When regenerating or modifying API schemas based on user change\nrequests, agents need to reference the previously generated schemas to\nunderstand the existing DTO structure and what needs to be modified.\n\n**Key Difference from `getInterfaceSchemas`:**\n\n- `getInterfaceSchemas`: Fetches schemas from the **current version** (the\n  version being generated right now)\n- `getPreviousInterfaceSchemas`: Fetches schemas from the **previous version**\n  (the last successfully generated version)\n\n**Example Scenario:**\n\n    Initial generation:\n    - INTERFACE phase creates: IUser, IUser.ICreate, IUser.IUpdate, IPost\n    - Generation completes successfully\n\n    User: \"Add phone number to user profile\"\n\n    Regeneration:\n    - INTERFACE phase starts regeneration\n    - Calls getPreviousInterfaceSchemas([\"IUser\", \"IUser.IUpdate\"])\n      \u2192 Loads the previous versions of these schemas\n    - Creates new versions with phoneNumber property added\n\n**Automatic Dependency Loading:**\n\nWhen schemas are loaded from the previous version, their referenced schemas\n(via `$ref`) are also available, providing complete type dependency context\nfor understanding the schema structure.\n\n**Schema Type Naming Convention:**\n\n- Entity schemas: `IEntityName` (e.g., \"IUser\", \"IPost\", \"IShoppingSale\")\n- Nested DTOs: `IEntityName.ISubType` (e.g., \"IUser.ICreate\", \"IPost.IUpdate\")\n- Response wrappers: `IPage<IEntityName>` (e.g., \"IPageIUser\", \"IPageIPost\")\n- Summary types: `IEntityName.ISummary` (e.g., \"IBbsArticle.ISummary\")\n- Authorized types: `IEntityName.IAuthorized` (e.g., \"IUser.IAuthorized\")\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 DTO changes",
+                            description: "Request to retrieve interface schemas from the previous iteration.\n\nLoads OpenAPI schema definitions (DTOs) 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 \"getPreviousInterfaceSchemas\" indicates this is a\npreliminary data request for interface schemas from a previous version.",
+                                    description: "Type discriminator.",
                                     type: "string",
                                     "enum": [
                                         "getPreviousInterfaceSchemas"
                                     ]
                                 },
                                 typeNames: {
-                                    description: "List of schema type names to retrieve from the previous version.\n\nThese are type names from the OpenAPI components.schemas section that were\ngenerated in a previous version and are needed as reference context for the\ncurrent regeneration.\n\n**Important Notes:**\n\n- These type names 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- Type names follow TypeScript interface naming (e.g., \"IUser\",\n  \"IUser.ICreate\")\n\n**When This Function is Available:**\n\n- When a previous version exists\n- When user requests modifications to existing API schemas\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 interface schemas available for this orchestration task\n\n**Type Name Examples:**\n\n- Base entity: \"IShoppingSale\", \"IBbsArticle\", \"IUser\"\n- Create DTO: \"IShoppingSale.ICreate\", \"IBbsArticle.ICreate\"\n- Update DTO: \"IShoppingSale.IUpdate\", \"IUser.IUpdate\"\n- Paginated: \"IPageIShoppingSale\", \"IPageIBbsArticle\"\n- Summary: \"IShoppingSale.ISummary\", \"IBbsArticle.ISummary\"",
+                                    description: "Schema type names to retrieve from previous iteration. DO NOT request same\nnames already requested in previous calls.",
                                     type: "array",
                                     items: {
                                         type: "string"
@@ -1975,26 +1960,26 @@ function createController(ctx, props) {
                             ]
                         },
                         "IAutoBeInterfaceSchemaApplication.IComplete": {
-                            description: "Request to generate a single OpenAPI schema component.\n\nExecutes schema generation to create a type definition for a specific DTO\ntype. Each invocation handles one schema component to ensure accuracy and\nclear responsibility.",
+                            description: "Request to generate a single OpenAPI schema component.",
                             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 type's purpose and context.\n\nBefore designing the schema, analyze what you know:\n\n- What is this type for? (e.g., IProduct.ICreate is a creation request)\n- What database entities or operations inform its structure?\n- What fields should be included based on the variant type?\n- Are there related types that provide structural hints?",
+                                    description: "Analysis of the type's purpose and context.",
                                     type: "string"
                                 },
                                 rationale: {
-                                    description: "Rationale for the schema design decisions.\n\nExplain why you designed the schema this way:\n\n- Which properties did you include and why?\n- What is required vs optional, and why?\n- Which types use $ref and why?\n- What was excluded and why? (e.g., auto-generated fields for ICreate)",
+                                    description: "Rationale for the schema design decisions.",
                                     type: "string"
                                 },
                                 design: {
-                                    description: "Design structure for the schema being generated.\n\nContains `databaseSchema`, `specification`, `description`, and `schema`\nfields that together define a complete DTO type component.",
+                                    description: "Schema design: database mapping, specification, description, and JSON\nSchema.",
                                     $ref: "#/$defs/AutoBeInterfaceSchemaDesign"
                                 }
                             },
@@ -2006,11 +1991,11 @@ function createController(ctx, props) {
                             ]
                         },
                         AutoBeInterfaceSchemaDesign: {
-                            description: "Design structure for creating OpenAPI schema components.\n\nSeparates schema metadata from the actual JSON Schema definition, allowing\nclear organization of implementation details (`specification`), API\ndocumentation (`description`), and the type structure (`schema`).\n\nThe `specification` and `description` fields are documented at the design\nlevel, separate from the `schema` field which holds the pure type structure.",
+                            description: "Design structure for creating an OpenAPI schema component.\n\nSeparates schema metadata (specification, description) from the JSON Schema\ndefinition (schema).",
                             type: "object",
                             properties: {
                                 databaseSchema: {
-                                    description: "Database model name that this schema maps to.\n\nSpecifies which database table/model this DTO type corresponds to. Creates\na traceable link between API types and database entities.\n\n- Set to the exact model name (e.g., `\"shopping_customers\"`,\n  `\"bbs_articles\"`) when this schema directly represents or derives from a\n  database entity\n- Set to `null` for:\n\n  - Computed/aggregated types (e.g., statistics, summaries from multiple\n      tables)\n  - Types composed purely by business logic (e.g., search filters, pagination)\n  - Embedded JSON structures without dedicated tables\n\nWhen `null`, the `specification` field becomes critical for downstream\nagents to understand how to implement data retrieval or computation.",
+                                    description: "Database model name this schema maps to, or `null` for computed/aggregated\ntypes.\n\nWhen `null`, `specification` becomes critical for downstream agents.",
                                     anyOf: [
                                         {
                                             type: "null"
@@ -2021,15 +2006,15 @@ function createController(ctx, props) {
                                     ]
                                 },
                                 specification: {
-                                    description: "Implementation specification for downstream agents.\n\nDetailed guidance on HOW to implement data retrieval, transformation, or\ncomputation for this type. Internal documentation for Realize Agent, Test\nAgent, and other implementation agents - NOT exposed in public API docs.\n\n**When `databaseSchema` is set** (direct mapping):\n\n- Can be brief for simple cases\n- Focus on any non-obvious mapping details\n\n**When `databaseSchema` is `null`** (computed/aggregated types):\n\nThis field is CRITICAL. Must include:\n\n- Source tables and columns involved\n- JOIN conditions between tables\n- Aggregation formulas (SUM, COUNT, AVG, etc.)\n- Business rules and transformation logic\n- Edge cases (nulls, empty sets, defaults)\n\nMust be precise enough for downstream agents to implement the actual data\nretrieval or computation. Vague specifications are unacceptable.",
+                                    description: "Implementation guidance for downstream agents (Realize, Test). NOT exposed\nin public API docs.\n\nWhen `databaseSchema` is set: brief mapping details. When `null`: MUST\ninclude source tables, JOINs, aggregation formulas, business rules, and\nedge cases.",
                                     type: "string"
                                 },
                                 description: {
-                                    description: "API documentation for consumers.\n\nStandard OpenAPI description displayed in Swagger UI, SDK documentation,\nand other API documentation tools. Focus on explaining WHAT the type\nrepresents and WHY it exists from an API consumer's perspective.\n\nGuidelines:\n\n- Reference corresponding database schema documentation for consistency\n- Organize into multiple paragraphs for complex types\n- Focus on business meaning, relationships, and constraints\n- Keep accessible to API consumers (no implementation details)\n- MUST be written in English",
+                                    description: "API documentation for consumers (Swagger UI). Focus on WHAT the type\nrepresents. Reference DB schema documentation for consistency.\n\n- MUST be written in English",
                                     type: "string"
                                 },
                                 schema: {
-                                    description: "JSON Schema definition for the type.\n\nThe actual type structure following OpenAPI v3.1 JSON Schema specification.\nCan be any valid JSON Schema type: object, array, string, number, integer,\nboolean, oneOf, or $ref.\n\nImportant:\n\n- For union types, use `oneOf` - NEVER use array notation in `type` field\n- For nullable types, use `oneOf: [{ type: \"...\" }, { type: \"null\" }]`\n- Object properties should have clear, descriptive names in camelCase\n- Use `$ref` for referencing other named schemas",
+                                    description: "JSON Schema definition.\n\nFor union/nullable types, use `oneOf` \u2014 NEVER array in `type` field. Use\n`$ref` for referencing named schemas. Object property names in camelCase.",
                                     $ref: "#/$defs/AutoBeOpenApi.IJsonSchema"
                                 }
                             },
@@ -2041,7 +2026,7 @@ function createController(ctx, props) {
                             ]
                         },
                         "AutoBeOpenApi.IJsonSchema": {
-                            description: "Type schema info.\n\n`AutoBeOpenApi.IJsonSchema` is a type schema info of the OpenAPI\nGenerative.\n\n`AutoBeOpenApi.IJsonSchema` basically follows the JSON schema specification\nof OpenAPI v3.1, but a little bit shrunk to remove ambiguous and duplicated\nexpressions of OpenAPI v3.1 for the convenience, clarity, and AI\ngeneration.\n\n## CRITICAL: Union Type Expression\n\nIn this type system, union types (including nullable types) MUST be\nexpressed using the `IOneOf` structure. NEVER use array notation in the\n`type` field.\n\n\u274C **FORBIDDEN** - Array notation in type field:\n\n```typescript\n{\n  \"type\": [\"string\", \"null\"] // NEVER DO THIS!\n}\n```\n\n\u2705 **CORRECT** - Using IOneOf for unions:\n\n```typescript\n// For nullable string:\n{\n  oneOf: [{ type: \"string\" }, { type: \"null\" }];\n}\n\n// For string | number union:\n{\n  oneOf: [{ type: \"string\" }, { type: \"number\" }];\n}\n```\n\nThe `type` field in any schema object is a discriminator that identifies\nthe schema type and MUST contain exactly one string value.",
+                            description: "JSON Schema type following OpenAPI v3.1 (simplified).\n\nCRITICAL: Union types MUST use `IOneOf`. NEVER use array in `type` field.\n\nWrong: `{ type: [\"string\", \"null\"] }` Correct: `{ oneOf: [{ type: \"string\"\n}, { type: \"null\" }] }`\n\nThe `type` field is a discriminator and MUST be a single string value.",
                             anyOf: [
                                 {
                                     $ref: "#/$defs/AutoBeOpenApi.IJsonSchema.IInteger"
@@ -2080,28 +2065,23 @@ function createController(ctx, props) {
                             type: "object",
                             properties: {
                                 minimum: {
-                                    description: "Minimum value restriction.",
                                     type: "integer"
                                 },
                                 maximum: {
-                                    description: "Maximum value restriction.",
                                     type: "integer"
                                 },
                                 exclusiveMinimum: {
-                                    description: "Exclusive minimum value restriction.",
                                     type: "integer"
                                 },
                                 exclusiveMaximum: {
-                                    description: "Exclusive maximum value restriction.",
                                     type: "integer"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.",
                                     type: "integer",
                                     exclusiveMinimum: 0
                                 },
                                 type: {
-                                    description: "Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n\"boolean\", \"integer\", \"number\", \"string\", \"array\", \"object\", or\n\"null\".\n\n\u274C INCORRECT: type: [\"string\", \"null\"] // This is WRONG! \u2705 CORRECT:\ntype: \"string\" // For nullable string, use oneOf instead\n\nIf you need to express a nullable type (e.g., string | null), you MUST\nuse the `IOneOf` structure:\n\n```typescript\n{\n  \"oneOf\": [{ \"type\": \"string\" }, { \"type\": \"null\" }]\n}\n```\n\nNEVER use array notation in the type field. The type field is a\ndiscriminator that accepts only a single string value.",
+                                    description: "Discriminator value. MUST be a single string, NEVER an array.\n\nFor nullable types, use `IOneOf` instead: `{ oneOf: [{ type: \"string\"\n}, { type: \"null\" }] }`",
                                     type: "string",
                                     "enum": [
                                         "integer"
@@ -2117,28 +2097,23 @@ function createController(ctx, props) {
                             type: "object",
                             properties: {
                                 minimum: {
-                                    description: "Minimum value restriction.",
                                     type: "number"
                                 },
                                 maximum: {
-                                    description: "Maximum value restriction.",
                                     type: "number"
                                 },
                                 exclusiveMinimum: {
-                                    description: "Exclusive minimum value restriction.",
                                     type: "number"
                                 },
                                 exclusiveMaximum: {
-                                    description: "Exclusive maximum value restriction.",
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.",
                                     type: "number",
                                     exclusiveMinimum: 0
                                 },
                                 type: {
-                                    description: "Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n\"boolean\", \"integer\", \"number\", \"string\", \"array\", \"object\", or\n\"null\".\n\n\u274C INCORRECT: type: [\"string\", \"null\"] // This is WRONG! \u2705 CORRECT:\ntype: \"string\" // For nullable string, use oneOf instead\n\nIf you need to express a nullable type (e.g., string | null), you MUST\nuse the `IOneOf` structure:\n\n```typescript\n{\n  \"oneOf\": [{ \"type\": \"string\" }, { \"type\": \"null\" }]\n}\n```\n\nNEVER use array notation in the type field. The type field is a\ndiscriminator that accepts only a single string value.",
+                                    description: "Discriminator value. MUST be a single string, NEVER an array.\n\nFor nullable types, use `IOneOf` instead: `{ oneOf: [{ type: \"string\"\n}, { type: \"null\" }] }`",
                                     type: "string",
                                     "enum": [
                                         "number"
@@ -2185,21 +2160,19 @@ function createController(ctx, props) {
                                     type: "string"
                                 },
                                 contentMediaType: {
-                                    description: "Content media type restriction.\n\nIf you want to accept multiple contentMediaType values simultaneously\n(e.g., `text/plain` and `text/html`), you MUST NOT violate the type by\nusing an array. Instead, use `oneOf` to define multiple `string`\nschemas with different `contentMediaType` values.\n\nExample for accepting both text/plain and text/html:\n\n```typescript\n{\n  \"oneOf\": [\n    { \"type\": \"string\", \"contentMediaType\": \"text/plain\" },\n    { \"type\": \"string\", \"contentMediaType\": \"text/html\" }\n  ]\n}\n```\n\nThis is the CORRECT approach. Never use array notation or modify the\nsingle string type to accept arrays.",
+                                    description: "Content media type restriction.\n\nFor multiple media types, use `oneOf` with separate string schemas per\n`contentMediaType` value. Never use an array here.",
                                     type: "string"
                                 },
                                 minLength: {
-                                    description: "Minimum length restriction.",
                                     type: "integer",
                                     minimum: 0
                                 },
                                 maxLength: {
-                                    description: "Maximum length restriction.",
                                     type: "integer",
                                     minimum: 0
                                 },
                                 type: {
-                                    description: "Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n\"boolean\", \"integer\", \"number\", \"string\", \"array\", \"object\", or\n\"null\".\n\n\u274C INCORRECT: type: [\"string\", \"null\"] // This is WRONG! \u2705 CORRECT:\ntype: \"string\" // For nullable string, use oneOf instead\n\nIf you need to express a nullable type (e.g., string | null), you MUST\nuse the `IOneOf` structure:\n\n```typescript\n{\n  \"oneOf\": [{ \"type\": \"string\" }, { \"type\": \"null\" }]\n}\n```\n\nNEVER use array notation in the type field. The type field is a\ndiscriminator that accepts only a single string value.",
+                                    description: "Discriminator value. MUST be a single string, NEVER an array.\n\nFor nullable types, use `IOneOf` instead: `{ oneOf: [{ type: \"string\"\n}, { type: \"null\" }] }`",
                                     type: "string",
                                     "enum": [
                                         "string"
@@ -2238,7 +2211,7 @@ function createController(ctx, props) {
                             type: "object",
                             properties: {
                                 type: {
-                                    description: "Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n\"boolean\", \"integer\", \"number\", \"string\", \"array\", \"object\", or\n\"null\".\n\n\u274C INCORRECT: type: [\"string\", \"null\"] // This is WRONG! \u2705 CORRECT:\ntype: \"string\" // For nullable string, use oneOf instead\n\nIf you need to express a nullable type (e.g., string | null), you MUST\nuse the `IOneOf` structure:\n\n```typescript\n{\n  \"oneOf\": [{ \"type\": \"string\" }, { \"type\": \"null\" }]\n}\n```\n\nNEVER use array notation in the type field. The type field is a\ndiscriminator that accepts only a single string value.",
+                                    description: "Discriminator value. MUST be a single string, NEVER an array.\n\nFor nullable types, use `IOneOf` instead: `{ oneOf: [{ type: \"string\"\n}, { type: \"null\" }] }`",
                                     type: "string",
                                     "enum": [
                                         "boolean"
@@ -2254,7 +2227,7 @@ function createController(ctx, props) {
                             type: "object",
                             properties: {
                                 items: {
-                                    description: "Items type info.\n\nThe `items` means the type of the array elements. In other words, it is\nthe type schema info of the `T` in the TypeScript array type\n`Array<T>`.",
+                                    description: "Type schema of array elements.",
                                     anyOf: [
                                         {
                                             $ref: "#/$defs/AutoBeOpenApi.IJsonSchema.INumber"
@@ -2286,21 +2259,19 @@ function createController(ctx, props) {
                                     ]
                                 },
                                 uniqueItems: {
-                                    description: "Unique items restriction.\n\nIf this property value is `true`, target array must have unique items.",
+                                    description: "If `true`, array elements must be unique.",
                                     type: "boolean"
                                 },
                                 minItems: {
-                                    description: "Minimum items restriction.\n\nRestriction of minimum number of items in the array.",
                                     type: "integer",
                                     minimum: 0
                                 },
                                 maxItems: {
-                                    description: "Maximum items restriction.\n\nRestriction of maximum number of items in the array.",
                                     type: "integer",
                                     minimum: 0
                                 },
                                 type: {
-                                    description: "Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n\"boolean\", \"integer\", \"number\", \"string\", \"array\", \"object\", or\n\"null\".\n\n\u274C INCORRECT: type: [\"string\", \"null\"] // This is WRONG! \u2705 CORRECT:\ntype: \"string\" // For nullable string, use oneOf instead\n\nIf you need to express a nullable type (e.g., string | null), you MUST\nuse the `IOneOf` structure:\n\n```typescript\n{\n  \"oneOf\": [{ \"type\": \"string\" }, { \"type\": \"null\" }]\n}\n```\n\nNEVER use array notation in the type field. The type field is a\ndiscriminator that accepts only a single string value.",
+                                    description: "Discriminator value. MUST be a single string, NEVER an array.\n\nFor nullable types, use `IOneOf` instead: `{ oneOf: [{ type: \"string\"\n}, { type: \"null\" }] }`",
                                     type: "string",
                                     "enum": [
                                         "array"
@@ -2317,7 +2288,7 @@ function createController(ctx, props) {
                             type: "object",
                             properties: {
                                 type: {
-                                    description: "Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n\"boolean\", \"integer\", \"number\", \"string\", \"array\", \"object\", or\n\"null\".\n\n\u274C INCORRECT: type: [\"string\", \"null\"] // This is WRONG! \u2705 CORRECT:\ntype: \"string\" // For nullable string, use oneOf instead\n\nIf you need to express a nullable type (e.g., string | null), you MUST\nuse the `IOneOf` structure:\n\n```typescript\n{\n  \"oneOf\": [{ \"type\": \"string\" }, { \"type\": \"null\" }]\n}\n```\n\nNEVER use array notation in the type field. The type field is a\ndiscriminator that accepts only a single string value.",
+                                    description: "Discriminator value. MUST be a single string, NEVER an array.\n\nFor nullable types, use `IOneOf` instead: `{ oneOf: [{ type: \"string\"\n}, { type: \"null\" }] }`",
                                     type: "string",
                                     "enum": [
                                         "null"
@@ -2333,7 +2304,7 @@ function createController(ctx, props) {
                             type: "object",
                             properties: {
                                 $ref: {
-                                    description: "Reference to the named schema.\n\nThe `ref` is a reference to the named schema. Format of the `$ref` is\nfollowing the JSON Pointer specification. In the OpenAPI, the `$ref`\nstarts with `#/components/schemas/` which means the type is stored in\nthe {@link AutoBeOpenApi.IComponents.schemas} object.\n\n- `#/components/schemas/SomeObject`\n- `#/components/schemas/AnotherObject`",
+                                    description: "JSON Pointer reference to a named schema (e.g.,\n`#/components/schemas/SomeObject`).",
                                     type: "string"
                                 }
                             },
@@ -2342,7 +2313,7 @@ function createController(ctx, props) {
                             ]
                         },
                         "AutoBeOpenApi.IJsonSchema.IOneOf": {
-                            description: "Union type.\n\n`IOneOf` represents an union type of the TypeScript (`A | B | C`).\n\nFor reference, even though your Swagger (or OpenAPI) document has defined\n`anyOf` instead of the `oneOf`, {@link AutoBeOpenApi} forcibly converts it\nto `oneOf` type.",
+                            description: "Union type.\n\n`IOneOf` represents a union type in TypeScript (`A | B | C`).\n\nFor reference, even though your Swagger (or OpenAPI) document has defined\n`anyOf` instead of the `oneOf`, {@link AutoBeOpenApi} forcibly converts it\nto `oneOf` type.",
                             type: "object",
                             properties: {
                                 oneOf: {
@@ -2395,7 +2366,7 @@ function createController(ctx, props) {
                                     type: "string"
                                 },
                                 mapping: {
-                                    description: "Mapping of the discriminator value to the schema name.\n\nThis property is valid only for {@link IReference} typed\n{@link IOneOf.oneof} elements. Therefore, `key` of `mapping` is the\ndiscriminator value, and `value` of `mapping` is the schema name like\n`#/components/schemas/SomeObject`.",
+                                    description: "Mapping of the discriminator value to the schema name.\n\nThis property is valid only for {@link IReference} typed\n{@link IOneOf.oneOf} elements. Therefore, `key` of `mapping` is the\ndiscriminator value, and `value` of `mapping` is the schema name like\n`#/components/schemas/SomeObject`.",
                                     $ref: "#/$defs/Recordstringstring"
                                 }
                             },
@@ -2417,11 +2388,11 @@ function createController(ctx, props) {
                             type: "object",
                             properties: {
                                 properties: {
-                                    description: "Properties of the object.\n\nThe `properties` means a list of key-value pairs of the object's\nregular properties. The key is the name of the regular property, and\nthe value is the type schema info.\n\nIf you need additional properties that is represented by dynamic key,\nyou can use the {@link additionalProperties} instead.",
+                                    description: "Key-value pairs of the object's named properties.",
                                     $ref: "#/$defs/RecordstringAutoBeOpenApi.IJsonSchema"
                                 },
                                 additionalProperties: {
-                                    description: "Additional properties' info.\n\nThe `additionalProperties` means the type schema info of the additional\nproperties that are not listed in the {@link properties}.\n\nIf the value is `false`, it means that the additional properties are\nnot specified. Otherwise, if the value is {@link IJsonSchema} type, it\nmeans that the additional properties must follow the type schema info.\n\n- `false`: No additional properties\n- `IJsonSchema`: `Record<string, T>`",
+                                    description: "Schema for dynamic keys (`Record<string, T>`), or `false` if no\nadditional properties are allowed.",
                                     anyOf: [
                                         {
                                             type: "boolean",
@@ -2459,14 +2430,14 @@ function createController(ctx, props) {
                                     ]
                                 },
                                 required: {
-                                    description: "List of key values of the required properties.\n\nThe `required` means a list of the key values of the required\n{@link properties}. If some property key is not listed in the `required`\nlist, it means that property is optional. Otherwise some property key\nexists in the `required` list, it means that the property must be\nfilled.\n\nBelow is an example of the {@link properties} and `required`.\n\n```typescript\ninterface SomeObject {\n  id: string;\n  email: string;\n  name?: string;\n}\n```\n\nAs you can see, `id` and `email` {@link properties} are {@link required},\nso that they are listed in the `required` list.\n\n```json\n{\n  \"type\": \"object\",\n  \"properties\": {\n    \"id\": { \"type\": \"string\" },\n    \"email\": { \"type\": \"string\" },\n    \"name\": { \"type\": \"string\" }\n  },\n  \"required\": [\"id\", \"email\"]\n}\n```",
+                                    description: "Property keys that must be present. Properties not listed here are\noptional.",
                                     type: "array",
                                     items: {
                                         type: "string"
                                     }
                                 },
                                 type: {
-                                    description: "Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n\"boolean\", \"integer\", \"number\", \"string\", \"array\", \"object\", or\n\"null\".\n\n\u274C INCORRECT: type: [\"string\", \"null\"] // This is WRONG! \u2705 CORRECT:\ntype: \"string\" // For nullable string, use oneOf instead\n\nIf you need to express a nullable type (e.g., string | null), you MUST\nuse the `IOneOf` structure:\n\n```typescript\n{\n  \"oneOf\": [{ \"type\": \"string\" }, { \"type\": \"null\" }]\n}\n```\n\nNEVER use array notation in the type field. The type field is a\ndiscriminator that accepts only a single string value.",
+                                    description: "Discriminator value. MUST be a single string, NEVER an array.\n\nFor nullable types, use `IOneOf` instead: `{ oneOf: [{ type: \"string\"\n}, { type: \"null\" }] }`",
                                     type: "string",
                                     "enum": [
                                         "object"
@@ -2490,7 +2461,7 @@ function createController(ctx, props) {
                         }
                     }
                 },
-                description: "Process schema generation task or preliminary data requests.\n\nGenerates OpenAPI components containing named schema types and integrates\nthem into the final OpenAPI specification. Processes all entity schemas,\ntheir variants, and related type definitions to ensure comprehensive and\nconsistent API design.",
+                description: "Process task or retrieve preliminary data.",
                 validate: (() => { const _iv8 = new Set(["password", "regex", "uuid", "email", "hostname", "idn-email", "idn-hostname", "iri", "iri-reference", "ipv4", "ipv6", "uri", "uri-reference", "uri-template", "url", "date-time", "date", "time", "duration", "json-pointer", "relative-json-pointer"]); const _vv18 = new Set(["password", "regex", "uuid", "email", "hostname", "idn-email", "idn-hostname", "iri", "iri-reference", "ipv4", "ipv6", "uri", "uri-reference", "uri-template", "url", "date-time", "date", "time", "duration", "json-pointer", "relative-json-pointer"]); const _io0 = input => "string" === typeof input.thinking && ("object" === typeof input.request && null !== input.request && _iu1(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 => "getInterfaceOperations" === input.type && (Array.isArray(input.endpoints) && (1 <= input.endpoints.length && input.endpoints.every(elem => "object" === typeof elem && null !== elem && _io4(elem)))); const _io4 = 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 _io5 = 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 _io6 = input => "getPreviousDatabaseSchemas" === input.type && (Array.isArray(input.schemaNames) && (1 <= input.schemaNames.length && input.schemaNames.every(elem => "string" === typeof elem))); const _io7 = input => "getPreviousInterfaceOperations" === input.type && (Array.isArray(input.endpoints) && (1 <= input.endpoints.length && input.endpoints.every(elem => "object" === typeof elem && null !== elem && _io4(elem)))); const _io8 = input => "getPreviousInterfaceSchemas" === input.type && (Array.isArray(input.typeNames) && (1 <= input.typeNames.length && input.typeNames.every(elem => "string" === typeof elem))); const _io9 = input => "complete" === input.type && "string" === typeof input.analysis && "string" === typeof input.rationale && ("object" === typeof input.design && null !== input.design && _io10(input.design)); const _io10 = input => (null === input.databaseSchema || "string" === typeof input.databaseSchema) && "string" === typeof input.specification && "string" === typeof input.description && ("object" === typeof input.schema && null !== input.schema && _iu2(input.schema)); const _io11 = input => (undefined === input.minimum || "number" === typeof input.minimum && (Math.floor(input.minimum) === input.minimum && -9223372036854776000 <= input.minimum && input.minimum <= 9223372036854776000)) && (undefined === input.maximum || "number" === typeof input.maximum && (Math.floor(input.maximum) === input.maximum && -9223372036854776000 <= input.maximum && input.maximum <= 9223372036854776000)) && (undefined === input.exclusiveMinimum || "number" === typeof input.exclusiveMinimum && (Math.floor(input.exclusiveMinimum) === input.exclusiveMinimum && -9223372036854776000 <= input.exclusiveMinimum && input.exclusiveMinimum <= 9223372036854776000)) && (undefined === input.exclusiveMaximum || "number" === typeof input.exclusiveMaximum && (Math.floor(input.exclusiveMaximum) === input.exclusiveMaximum && -9223372036854776000 <= input.exclusiveMaximum && input.exclusiveMaximum <= 9223372036854776000)) && (undefined === input.multipleOf || "number" === typeof input.multipleOf && (Math.floor(input.multipleOf) === input.multipleOf && 0 <= input.multipleOf && input.multipleOf <= 18446744073709552000 && 0 < input.multipleOf)) && "integer" === input.type; const _io12 = input => (undefined === input.minimum || "number" === typeof input.minimum) && (undefined === input.maximum || "number" === typeof input.maximum) && (undefined === input.exclusiveMinimum || "number" === typeof input.exclusiveMinimum) && (undefined === input.exclusiveMaximum || "number" === typeof input.exclusiveMaximum) && (undefined === input.multipleOf || "number" === typeof input.multipleOf && 0 < input.multipleOf) && "number" === input.type; const _io13 = input => (undefined === input.format || true === _iv8.has(input.format)) && (undefined === input.pattern || "string" === typeof input.pattern) && (undefined === input.contentMediaType || "string" === typeof input.contentMediaType) && (undefined === input.minLength || "number" === typeof input.minLength && (Math.floor(input.minLength) === input.minLength && 0 <= input.minLength && input.minLength <= 18446744073709552000)) && (undefined === input.maxLength || "number" === typeof input.maxLength && (Math.floor(input.maxLength) === input.maxLength && 0 <= input.maxLength && input.maxLength <= 18446744073709552000)) && "string" === input.type; const _io14 = input => "string" === typeof input["const"] || "number" === typeof input["const"] || "boolean" === typeof input["const"]; const _io15 = input => "boolean" === input.type; const _io16 = input => "object" === typeof input.items && null !== input.items && _iu3(input.items) && (undefined === input.uniqueItems || "boolean" === typeof input.uniqueItems) && (undefined === input.minItems || "number" === typeof input.minItems && (Math.floor(input.minItems) === input.minItems && 0 <= input.minItems && input.minItems <= 18446744073709552000)) && (undefined === input.maxItems || "number" === typeof input.maxItems && (Math.floor(input.maxItems) === input.maxItems && 0 <= input.maxItems && input.maxItems <= 18446744073709552000)) && "array" === input.type; const _io17 = input => "string" === typeof input.$ref; const _io18 = input => Array.isArray(input.oneOf) && input.oneOf.every(elem => "object" === typeof elem && null !== elem && _iu0(elem)) && (undefined === input.discriminator || "object" === typeof input.discriminator && null !== input.discriminator && _io20(input.discriminator)); const _io19 = input => "null" === input.type; const _io20 = input => "string" === typeof input.propertyName && (undefined === input.mapping || "object" === typeof input.mapping && null !== input.mapping && false === Array.isArray(input.mapping) && _io21(input.mapping)); const _io21 = input => Object.keys(input).every(key => {
                     const value = input[key];
                     if (undefined === value)