@autobe/agent 0.30.4 → 0.30.5

package/lib/orchestrate/interface/orchestrateInterfaceOperationReview.js

@@ -121,7 +121,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: "Think before you act.\n\nFor preliminary requests: what critical information is missing and why?\nBe brief \u2014 state the gap, don't list everything you have.\n\nFor completion: what key assets did you acquire, what did you accomplish,\nwhy is it sufficient? Summarize \u2014 don't enumerate every single item."
                                 },
                                 request: {
                                     oneOf: [
@@ -155,7 +155,7 @@ function process(ctx, props) {
                                             complete: "#/components/schemas/IAutoBeInterfaceOperationReviewApplication.IComplete"
                                         }
                                     },
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval\n(getAnalysisSections, getDatabaseSchemas) or final operation review\n(complete). When preliminary returns empty array, that type is removed\nfrom the union, physically preventing repeated calls."
+                                    description: "Action to perform. Exhausted preliminary types are removed from the\nunion, physically preventing repeated calls."
                                 }
                             },
                             required: [
@@ -168,7 +168,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",
@@ -178,21 +178,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",
@@ -200,21 +200,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."
                         },
                         IAutoBePreliminaryGetPreviousAnalysisSections: {
                             type: "object",
                             properties: {
                                 type: {
                                     "const": "getPreviousAnalysisSections",
-                                    description: "Type discriminator for the request.\n\nValue \"getPreviousAnalysisSections\" indicates this is a preliminary data\nrequest for analysis sections from the previous iteration."
+                                    description: "Type discriminator."
                                 },
                                 sectionIds: {
                                     type: "array",
@@ -223,21 +223,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",
@@ -245,21 +245,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",
@@ -267,14 +267,14 @@ 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."
                         },
                         "AutoBeOpenApi.IEndpoint": {
                             type: "object",
@@ -282,7 +282,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: [
@@ -302,7 +302,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: [
@@ -316,15 +316,15 @@ function process(ctx, props) {
                             properties: {
                                 type: {
                                     "const": "complete",
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"complete\" indicates this is the final task\nexecution request."
+                                    description: "Type discriminator for completion request."
                                 },
                                 review: {
                                     type: "string",
-                                    description: "Comprehensive operation-level review findings.\n\nSystematic assessment of the operation organized by severity:\n\n- Authorization configuration issues\n- Path structure violations\n- Metadata consistency problems\n- Description accuracy issues\n\nDocuments what issues were found during review, with specific examples\nand current vs expected behavior."
+                                    description: "Operation-level review findings organized by severity."
                                 },
                                 plan: {
                                     type: "string",
-                                    description: "Action plan for identified issues.\n\nStructured improvement strategy explaining what corrections will be\napplied and why:\n\n- What specific changes are being made\n- Why each change is necessary\n- If rejecting (returning null), why the operation cannot be fixed\n\nIf no issues found: \"No improvements required. Operation meets\nstandards.\""
+                                    description: "Action plan for corrections, or \"No improvements required. Operation\nmeets standards.\""
                                 },
                                 content: {
                                     oneOf: [
@@ -335,7 +335,7 @@ function process(ctx, props) {
                                             $ref: "#/components/schemas/IAutoBeInterfaceOperationReviewApplication.IOperation"
                                         }
                                     ],
-                                    description: "Corrected operation with issues resolved, or null if operation rejected.\n\nThe agent can only modify fields present in IOperation type (description,\nrequestBody, responseBody).\n\nReturn values:\n\n- **Corrected operation**: If fixable issues were found and corrected in\n  the modifiable fields\n- **null**: If operation is perfect OR if issues exist in fields not\n  present in IOperation type\n\nWhen null is returned:\n\n- For perfect operations: means \"no changes needed, proceed\"\n- For failed validation: means \"reject this operation, remove from\n  pipeline\"\n\nThe orchestrator will filter out null operations from the final operation\nlist."
+                                    description: "Corrected operation with fixes applied. Null when no changes are needed.\nIf issues exist in non-modifiable fields, also set to null (the `plan`\nfield should explain why)."
                                 }
                             },
                             required: [
@@ -344,18 +344,18 @@ function process(ctx, props) {
                                 "plan",
                                 "content"
                             ],
-                            description: "Request to review and validate an API operation with minimal correction\npower.\n\nThis agent can ONLY modify fields present in the IOperation type. For\nissues in fields not present in IOperation, it must reject the operation by\nreturning null.\n\nThe IOperation type contains only:\n\n- Specification: Implementation guidance for Realize Agent - can fix\n  implementation details, algorithm descriptions, database query logic\n- Description: API documentation for consumers - can fix soft delete\n  mismatches, inappropriate security mentions, add schema references\n- RequestBody: Complete object - can modify both description and typeName to\n  fix clarity issues and naming convention violations\n- ResponseBody: Complete object - can modify both description and typeName to\n  fix clarity issues and naming convention violations\n\nFields not in IOperation cannot be modified - the agent must reject by\nreturning null if those fields have issues."
+                            description: "Review and validate an API operation. Can ONLY modify IOperation fields:\n\n- `specification`: Can fix implementation details, algorithm descriptions,\n  database query logic\n- `description`: Can fix soft delete mismatches, inappropriate security\n  mentions, add schema references\n- `requestBody`: Can modify both description and typeName\n- `responseBody`: Can modify both description and typeName\n\nReturn null to reject if issues exist in non-modifiable fields (path,\nmethod, parameters, etc.)."
                         },
                         "IAutoBeInterfaceOperationReviewApplication.IOperation": {
                             type: "object",
                             properties: {
                                 specification: {
                                     type: "string",
-                                    description: "Implementation specification for the API operation.\n\nThis is an AutoBE-internal field (not exposed in standard OpenAPI output)\nthat provides detailed implementation guidance for downstream agents\n(Realize Agent, Test Agent, etc.).\n\nInclude **HOW** this operation should be implemented:\n\n- Service layer logic and algorithm\n- Database queries and transactions involved\n- Business rules and validation logic\n- Edge cases and error handling\n- Integration with other services\n\nThis field complements the `description` field: while `description` is\nfor API consumers (Swagger UI, SDK docs), `specification` is for agents\nthat implement the operation.\n\n> MUST be written in English. Never use other languages."
+                                    description: "Internal implementation guidance for downstream agents (Realize, Test).\n\nDescribe HOW this operation should be implemented: service logic, DB\nqueries, business rules, edge cases, and error handling.\n\n> MUST be written in English. Never use other languages."
                                 },
                                 description: {
                                     type: "string",
-                                    description: "Detailed description about the API operation.\n\nIMPORTANT: This field MUST be extensively detailed and MUST reference the\ndescription comments from the related database schema tables and columns.\nThe description should be organized into MULTIPLE PARAGRAPHS separated by\nline breaks to improve readability and comprehension.\n\nFor example, include separate paragraphs for:\n\n- The purpose and overview of the API operation\n- Security considerations and user permissions\n- Relationship to underlying database entities\n- Validation rules and business logic\n- Related API operations that might be used together with this one\n- Expected behavior and error handling\n\nWhen writing the description, be sure to incorporate the corresponding DB\nschema's description comments, matching the level of detail and style of\nthose comments. This ensures consistency between the API documentation\nand database structure.\n\nIf there's a dependency to other APIs, please describe the dependency API\noperation in this field with detailed reason. For example, if this API\noperation needs a pre-execution of other API operation, it must be\nexplicitly described.\n\n- `GET /shoppings/customers/sales` must be pre-executed to get entire list\n  of summarized sales. Detailed sale information would be obtained by\n  specifying the sale ID in the path parameter.\n\n**CRITICAL WARNING about soft delete keywords**: DO NOT use terms like\n\"soft delete\", \"soft-delete\", or similar variations in this description\nUNLESS the operation actually implements soft deletion. These keywords\ntrigger validation logic that expects a corresponding soft_delete_column\nto be specified. Only use these terms when you intend to implement soft\ndeletion (marking records as deleted without removing them from the\ndatabase).\n\nExample of problematic description: \u274C \"This would normally be a\nsoft-delete, but we intentionally perform permanent deletion here\" - This\ntriggers soft delete validation despite being a hard delete operation.\n\n> MUST be written in English. Never use other languages."
+                                    description: "Multi-paragraph description of the API operation for consumers.\n\nReference and incorporate DB schema table/column description comments.\nOrganize into multiple paragraphs covering purpose, business logic,\nrelationships, and error handling.\n\nDo NOT use \"soft delete\" / \"soft-delete\" unless the operation actually\nimplements soft deletion (triggers validation expecting\nsoft_delete_column).\n\n> MUST be written in English. Never use other languages."
                                 },
                                 responseBody: {
                                     oneOf: [
@@ -366,7 +366,7 @@ function process(ctx, props) {
                                             $ref: "#/components/schemas/AutoBeOpenApi.IResponseBody"
                                         }
                                     ],
-                                    description: "Response body of the API operation.\n\nDefines the structure of the successful response data. Contains a\ndescription and schema reference for the returned data.\n\nShould be null for operations that don't return any data."
+                                    description: "Response body of the API operation, or `null` if none."
                                 },
                                 requestBody: {
                                     oneOf: [
@@ -377,7 +377,7 @@ function process(ctx, props) {
                                             $ref: "#/components/schemas/AutoBeOpenApi.IRequestBody"
                                         }
                                     ],
-                                    description: "Request body of the API operation.\n\nDefines the payload structure for the request. Contains a description and\nschema reference to define the expected input data.\n\nShould be `null` for operations that don't require a request body, such\nas most \"get\" operations."
+                                    description: "Request body of the API operation, or `null` if none."
                                 }
                             },
                             required: [
@@ -386,43 +386,43 @@ function process(ctx, props) {
                                 "responseBody",
                                 "requestBody"
                             ],
-                            description: "Operation with ONLY the fields that this agent can modify.\n\nThis type contains ONLY the modifiable fields. Fields not in this type\ncannot be modified - if they have issues, the agent must return null.\n\nFields in this type:\n\n- **specification**: Implementation guidance for Realize Agent - can fix\n  implementation details, algorithm descriptions, database query logic\n- **description**: API documentation for consumers - can fix soft delete\n  mismatches, remove inappropriate security mentions, add schema\n  references\n- **requestBody**: Complete request body object (or null) - can modify both\n  description and typeName to fix naming conventions or improve clarity\n- **responseBody**: Complete response body object (or null) - can modify both\n  description and typeName to fix naming conventions or improve clarity"
+                            description: "Operation subset containing only modifiable fields. Return null if\nnon-modifiable fields have issues."
                         },
                         "AutoBeOpenApi.IResponseBody": {
                             type: "object",
                             properties: {
                                 description: {
                                     type: "string",
-                                    description: "Description about the response body.\n\nMake short, concise and clear description about the response body.\n\n> MUST be written in English. Never use other languages."
+                                    description: "Description of the response body.\n\n> MUST be written in English. Never use other languages."
                                 },
                                 typeName: {
                                     type: "string",
-                                    description: "Response body's data type.\n\nSpecifies the structure of the returned data (response body), that will\nbe transformed to {@link AutoBeOpenApi.IJsonSchema.IReference} type in the\n{@link AutoBeOpenApi.IComponents.schemas components section} as an\n{@link AutoBeOpenApi.IJsonSchema.IObject object} type.\n\nHere is the naming convention for the response body type:\n\n- `IEntityName`: Main entity with detailed information (e.g.,\n  `IShoppingSale`)\n- `IEntityName.ISummary`: Simplified response version with essential\n  properties\n- `IEntityName.IInvert`: Alternative view of an entity from a different\n  perspective\n- `IPageIEntityName`: Paginated results container with `pagination` and\n  `data` properties\n\nWhat you write:\n\n```json\n{\n  \"typeName\": \"IShoppingOrder\"\n}\n```\n\nTransformed to:\n\n```json\n{\n  \"schema\": {\n    \"$ref\": \"#/components/schemas/IShoppingOrder\"\n  }\n}\n```"
+                                    description: "Type name referencing a component schema.\n\nNaming convention: `IEntityName` (full), `IEntityName.ISummary`,\n`IEntityName.IInvert`, `IPageIEntityName` (paginated)."
                                 }
                             },
                             required: [
                                 "description",
                                 "typeName"
                             ],
-                            description: "Response body information for OpenAPI operation.\n\nThis interface defines the structure of a successful response from an API\noperation. It provides a description of the response and a schema reference\nto define the returned data structure.\n\nThe content-type for all responses is always `application/json`. Even when\nfile downloading is required, don't use `application/octet-stream` or\n`multipart/form-data` content types. Instead, just define an URI string\nproperty in the response body schema.\n\nIn OpenAPI, this might represent:\n\n```json\n{\n  \"responses\": {\n    \"200\": {\n      \"description\": \"Order information\",\n      \"content\": {\n        \"application/json\": {\n          \"schema\": { \"$ref\": \"#/components/schemas/IShoppingOrder\" }\n        }\n      }\n    }\n  }\n}\n```"
+                            description: "Response body for an API operation.\n\nContent-type is always `application/json`. For file downloads, use a URI\nstring property instead of `application/octet-stream`."
                         },
                         "AutoBeOpenApi.IRequestBody": {
                             type: "object",
                             properties: {
                                 description: {
                                     type: "string",
-                                    description: "Description about the request body.\n\nMake short, concise and clear description about the request body.\n\n> MUST be written in English. Never use other languages."
+                                    description: "Description of the request body.\n\n> MUST be written in English. Never use other languages."
                                 },
                                 typeName: {
                                     type: "string",
-                                    description: "Request body type name.\n\nThis specifies the data structure expected in the request body, that will\nbe transformed to {@link AutoBeOpenApi.IJsonSchema.IReference reference}\ntype in the {@link AutoBeOpenApi.IComponents.schemas components section}\nas an {@link AutoBeOpenApi.IJsonSchema.Object object} type.\n\nHere is the naming convention for the request body type:\n\n- `IEntityName.ICreate`: Request body for creation operations (POST)\n- `IEntityName.IUpdate`: Request body for update operations (PUT)\n- `IEntityName.IRequest`: Request parameters for list operations (often\n  with search/pagination)\n\nWhat you write:\n\n```json\n{\n  \"typeName\": \"IShoppingOrder.ICreate\"\n}\n```\n\nTransformed to:\n\n```json\n{\n  \"schema\": {\n    \"$ref\": \"#/components/schemas/IShoppingOrder.ICreate\"\n  }\n}\n```"
+                                    description: "Type name referencing a component schema.\n\nNaming convention: `IEntityName.ICreate` (POST), `IEntityName.IUpdate`\n(PUT), `IEntityName.IRequest` (list/search)."
                                 }
                             },
                             required: [
                                 "description",
                                 "typeName"
                             ],
-                            description: "Request body information of OpenAPI operation.\n\nThis interface defines the structure for request bodies in API routes. It\ncorresponds to the requestBody section in OpenAPI specifications, providing\nboth a description and schema reference for the request payload.\n\nThe content-type for all request bodies is always `application/json`. Even\nwhen file uploading is required, don't use `multipart/form-data` or\n`application/x-www-form-urlencoded` content types. Instead, just define an\nURI string property in the request body schema.\n\nNote that, all body schemas must be transformable to a\n{@link AutoBeOpenApi.IJsonSchema.IReference reference} type defined in the\n{@link AutoBeOpenApi.IComponents.schemas components section} as an\n{@link AutoBeOpenApi.IJsonSchema.IObject object} type.\n\nIn OpenAPI, this might represent:\n\n```json\n{\n  \"requestBody\": {\n    \"description\": \"Creation info of the order\",\n    \"content\": {\n      \"application/json\": {\n        \"schema\": {\n          \"$ref\": \"#/components/schemas/IShoppingOrder.ICreate\"\n        }\n      }\n    }\n  }\n}\n```"
+                            description: "Request body for an API operation.\n\nContent-type is always `application/json`. For file uploads, use a URI\nstring property instead of `multipart/form-data`."
                         }
                     }
                 },
@@ -440,7 +440,7 @@ function process(ctx, props) {
                                 }
                             }
                         ],
-                        description: "Process operation review task or preliminary data requests.\n\nAnalyzes the operation for security vulnerabilities, schema compliance,\nlogical consistency, and standard adherence. Outputs structured thinking\nprocess and the production-ready operation."
+                        description: "Process operation review task or preliminary data requests."
                     }
                 ]
             },
@@ -793,11 +793,11 @@ function createReviewController(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: "Think before you act.\n\nFor preliminary requests: what critical information is missing and why?\nBe brief \u2014 state the gap, don't list everything you have.\n\nFor completion: what key assets did you acquire, what did you accomplish,\nwhy is it sufficient? Summarize \u2014 don't enumerate every single item.",
                             type: "string"
                         },
                         request: {
-                            description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval\n(getAnalysisSections, getDatabaseSchemas) or final operation review\n(complete). When preliminary returns empty array, that type is removed\nfrom the union, physically preventing repeated calls.",
+                            description: "Action to perform. Exhausted preliminary types are removed from the\nunion, physically preventing repeated calls.",
                             anyOf: [
                                 {
                                     $ref: "#/$defs/IAutoBePreliminaryGetAnalysisSections"
@@ -838,18 +838,18 @@ function createReviewController(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",
@@ -865,18 +865,18 @@ function createReviewController(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"
@@ -890,18 +890,18 @@ function createReviewController(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",
@@ -916,18 +916,18 @@ function createReviewController(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"
@@ -941,18 +941,18 @@ function createReviewController(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"
@@ -970,12 +970,12 @@ function createReviewController(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",
@@ -992,26 +992,26 @@ function createReviewController(props) {
                             ]
                         },
                         "IAutoBeInterfaceOperationReviewApplication.IComplete": {
-                            description: "Request to review and validate an API operation with minimal correction\npower.\n\nThis agent can ONLY modify fields present in the IOperation type. For\nissues in fields not present in IOperation, it must reject the operation by\nreturning null.\n\nThe IOperation type contains only:\n\n- Specification: Implementation guidance for Realize Agent - can fix\n  implementation details, algorithm descriptions, database query logic\n- Description: API documentation for consumers - can fix soft delete\n  mismatches, inappropriate security mentions, add schema references\n- RequestBody: Complete object - can modify both description and typeName to\n  fix clarity issues and naming convention violations\n- ResponseBody: Complete object - can modify both description and typeName to\n  fix clarity issues and naming convention violations\n\nFields not in IOperation cannot be modified - the agent must reject by\nreturning null if those fields have issues.",
+                            description: "Review and validate an API operation. Can ONLY modify IOperation fields:\n\n- `specification`: Can fix implementation details, algorithm descriptions,\n  database query logic\n- `description`: Can fix soft delete mismatches, inappropriate security\n  mentions, add schema references\n- `requestBody`: Can modify both description and typeName\n- `responseBody`: Can modify both description and typeName\n\nReturn null to reject if issues exist in non-modifiable fields (path,\nmethod, parameters, etc.).",
                             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"
                                     ]
                                 },
                                 review: {
-                                    description: "Comprehensive operation-level review findings.\n\nSystematic assessment of the operation organized by severity:\n\n- Authorization configuration issues\n- Path structure violations\n- Metadata consistency problems\n- Description accuracy issues\n\nDocuments what issues were found during review, with specific examples\nand current vs expected behavior.",
+                                    description: "Operation-level review findings organized by severity.",
                                     type: "string"
                                 },
                                 plan: {
-                                    description: "Action plan for identified issues.\n\nStructured improvement strategy explaining what corrections will be\napplied and why:\n\n- What specific changes are being made\n- Why each change is necessary\n- If rejecting (returning null), why the operation cannot be fixed\n\nIf no issues found: \"No improvements required. Operation meets\nstandards.\"",
+                                    description: "Action plan for corrections, or \"No improvements required. Operation\nmeets standards.\"",
                                     type: "string"
                                 },
                                 content: {
-                                    description: "Corrected operation with issues resolved, or null if operation rejected.\n\nThe agent can only modify fields present in IOperation type (description,\nrequestBody, responseBody).\n\nReturn values:\n\n- **Corrected operation**: If fixable issues were found and corrected in\n  the modifiable fields\n- **null**: If operation is perfect OR if issues exist in fields not\n  present in IOperation type\n\nWhen null is returned:\n\n- For perfect operations: means \"no changes needed, proceed\"\n- For failed validation: means \"reject this operation, remove from\n  pipeline\"\n\nThe orchestrator will filter out null operations from the final operation\nlist.",
+                                    description: "Corrected operation with fixes applied. Null when no changes are needed.\nIf issues exist in non-modifiable fields, also set to null (the `plan`\nfield should explain why).",
                                     anyOf: [
                                         {
                                             type: "null"
@@ -1030,19 +1030,19 @@ function createReviewController(props) {
                             ]
                         },
                         "IAutoBeInterfaceOperationReviewApplication.IOperation": {
-                            description: "Operation with ONLY the fields that this agent can modify.\n\nThis type contains ONLY the modifiable fields. Fields not in this type\ncannot be modified - if they have issues, the agent must return null.\n\nFields in this type:\n\n- **specification**: Implementation guidance for Realize Agent - can fix\n  implementation details, algorithm descriptions, database query logic\n- **description**: API documentation for consumers - can fix soft delete\n  mismatches, remove inappropriate security mentions, add schema\n  references\n- **requestBody**: Complete request body object (or null) - can modify both\n  description and typeName to fix naming conventions or improve clarity\n- **responseBody**: Complete response body object (or null) - can modify both\n  description and typeName to fix naming conventions or improve clarity",
+                            description: "Operation subset containing only modifiable fields. Return null if\nnon-modifiable fields have issues.",
                             type: "object",
                             properties: {
                                 specification: {
-                                    description: "Implementation specification for the API operation.\n\nThis is an AutoBE-internal field (not exposed in standard OpenAPI output)\nthat provides detailed implementation guidance for downstream agents\n(Realize Agent, Test Agent, etc.).\n\nInclude **HOW** this operation should be implemented:\n\n- Service layer logic and algorithm\n- Database queries and transactions involved\n- Business rules and validation logic\n- Edge cases and error handling\n- Integration with other services\n\nThis field complements the `description` field: while `description` is\nfor API consumers (Swagger UI, SDK docs), `specification` is for agents\nthat implement the operation.\n\n> MUST be written in English. Never use other languages.",
+                                    description: "Internal implementation guidance for downstream agents (Realize, Test).\n\nDescribe HOW this operation should be implemented: service logic, DB\nqueries, business rules, edge cases, and error handling.\n\n> MUST be written in English. Never use other languages.",
                                     type: "string"
                                 },
                                 description: {
-                                    description: "Detailed description about the API operation.\n\nIMPORTANT: This field MUST be extensively detailed and MUST reference the\ndescription comments from the related database schema tables and columns.\nThe description should be organized into MULTIPLE PARAGRAPHS separated by\nline breaks to improve readability and comprehension.\n\nFor example, include separate paragraphs for:\n\n- The purpose and overview of the API operation\n- Security considerations and user permissions\n- Relationship to underlying database entities\n- Validation rules and business logic\n- Related API operations that might be used together with this one\n- Expected behavior and error handling\n\nWhen writing the description, be sure to incorporate the corresponding DB\nschema's description comments, matching the level of detail and style of\nthose comments. This ensures consistency between the API documentation\nand database structure.\n\nIf there's a dependency to other APIs, please describe the dependency API\noperation in this field with detailed reason. For example, if this API\noperation needs a pre-execution of other API operation, it must be\nexplicitly described.\n\n- `GET /shoppings/customers/sales` must be pre-executed to get entire list\n  of summarized sales. Detailed sale information would be obtained by\n  specifying the sale ID in the path parameter.\n\n**CRITICAL WARNING about soft delete keywords**: DO NOT use terms like\n\"soft delete\", \"soft-delete\", or similar variations in this description\nUNLESS the operation actually implements soft deletion. These keywords\ntrigger validation logic that expects a corresponding soft_delete_column\nto be specified. Only use these terms when you intend to implement soft\ndeletion (marking records as deleted without removing them from the\ndatabase).\n\nExample of problematic description: \u274C \"This would normally be a\nsoft-delete, but we intentionally perform permanent deletion here\" - This\ntriggers soft delete validation despite being a hard delete operation.\n\n> MUST be written in English. Never use other languages.",
+                                    description: "Multi-paragraph description of the API operation for consumers.\n\nReference and incorporate DB schema table/column description comments.\nOrganize into multiple paragraphs covering purpose, business logic,\nrelationships, and error handling.\n\nDo NOT use \"soft delete\" / \"soft-delete\" unless the operation actually\nimplements soft deletion (triggers validation expecting\nsoft_delete_column).\n\n> MUST be written in English. Never use other languages.",
                                     type: "string"
                                 },
                                 responseBody: {
-                                    description: "Response body of the API operation.\n\nDefines the structure of the successful response data. Contains a\ndescription and schema reference for the returned data.\n\nShould be null for operations that don't return any data.",
+                                    description: "Response body of the API operation, or `null` if none.",
                                     anyOf: [
                                         {
                                             type: "null"
@@ -1053,7 +1053,7 @@ function createReviewController(props) {
                                     ]
                                 },
                                 requestBody: {
-                                    description: "Request body of the API operation.\n\nDefines the payload structure for the request. Contains a description and\nschema reference to define the expected input data.\n\nShould be `null` for operations that don't require a request body, such\nas most \"get\" operations.",
+                                    description: "Request body of the API operation, or `null` if none.",
                                     anyOf: [
                                         {
                                             type: "null"
@@ -1072,15 +1072,15 @@ function createReviewController(props) {
                             ]
                         },
                         "AutoBeOpenApi.IResponseBody": {
-                            description: "Response body information for OpenAPI operation.\n\nThis interface defines the structure of a successful response from an API\noperation. It provides a description of the response and a schema reference\nto define the returned data structure.\n\nThe content-type for all responses is always `application/json`. Even when\nfile downloading is required, don't use `application/octet-stream` or\n`multipart/form-data` content types. Instead, just define an URI string\nproperty in the response body schema.\n\nIn OpenAPI, this might represent:\n\n```json\n{\n  \"responses\": {\n    \"200\": {\n      \"description\": \"Order information\",\n      \"content\": {\n        \"application/json\": {\n          \"schema\": { \"$ref\": \"#/components/schemas/IShoppingOrder\" }\n        }\n      }\n    }\n  }\n}\n```",
+                            description: "Response body for an API operation.\n\nContent-type is always `application/json`. For file downloads, use a URI\nstring property instead of `application/octet-stream`.",
                             type: "object",
                             properties: {
                                 description: {
-                                    description: "Description about the response body.\n\nMake short, concise and clear description about the response body.\n\n> MUST be written in English. Never use other languages.",
+                                    description: "Description of the response body.\n\n> MUST be written in English. Never use other languages.",
                                     type: "string"
                                 },
                                 typeName: {
-                                    description: "Response body's data type.\n\nSpecifies the structure of the returned data (response body), that will\nbe transformed to {@link AutoBeOpenApi.IJsonSchema.IReference} type in the\n{@link AutoBeOpenApi.IComponents.schemas components section} as an\n{@link AutoBeOpenApi.IJsonSchema.IObject object} type.\n\nHere is the naming convention for the response body type:\n\n- `IEntityName`: Main entity with detailed information (e.g.,\n  `IShoppingSale`)\n- `IEntityName.ISummary`: Simplified response version with essential\n  properties\n- `IEntityName.IInvert`: Alternative view of an entity from a different\n  perspective\n- `IPageIEntityName`: Paginated results container with `pagination` and\n  `data` properties\n\nWhat you write:\n\n```json\n{\n  \"typeName\": \"IShoppingOrder\"\n}\n```\n\nTransformed to:\n\n```json\n{\n  \"schema\": {\n    \"$ref\": \"#/components/schemas/IShoppingOrder\"\n  }\n}\n```",
+                                    description: "Type name referencing a component schema.\n\nNaming convention: `IEntityName` (full), `IEntityName.ISummary`,\n`IEntityName.IInvert`, `IPageIEntityName` (paginated).",
                                     type: "string"
                                 }
                             },
@@ -1090,15 +1090,15 @@ function createReviewController(props) {
                             ]
                         },
                         "AutoBeOpenApi.IRequestBody": {
-                            description: "Request body information of OpenAPI operation.\n\nThis interface defines the structure for request bodies in API routes. It\ncorresponds to the requestBody section in OpenAPI specifications, providing\nboth a description and schema reference for the request payload.\n\nThe content-type for all request bodies is always `application/json`. Even\nwhen file uploading is required, don't use `multipart/form-data` or\n`application/x-www-form-urlencoded` content types. Instead, just define an\nURI string property in the request body schema.\n\nNote that, all body schemas must be transformable to a\n{@link AutoBeOpenApi.IJsonSchema.IReference reference} type defined in the\n{@link AutoBeOpenApi.IComponents.schemas components section} as an\n{@link AutoBeOpenApi.IJsonSchema.IObject object} type.\n\nIn OpenAPI, this might represent:\n\n```json\n{\n  \"requestBody\": {\n    \"description\": \"Creation info of the order\",\n    \"content\": {\n      \"application/json\": {\n        \"schema\": {\n          \"$ref\": \"#/components/schemas/IShoppingOrder.ICreate\"\n        }\n      }\n    }\n  }\n}\n```",
+                            description: "Request body for an API operation.\n\nContent-type is always `application/json`. For file uploads, use a URI\nstring property instead of `multipart/form-data`.",
                             type: "object",
                             properties: {
                                 description: {
-                                    description: "Description about the request body.\n\nMake short, concise and clear description about the request body.\n\n> MUST be written in English. Never use other languages.",
+                                    description: "Description of the request body.\n\n> MUST be written in English. Never use other languages.",
                                     type: "string"
                                 },
                                 typeName: {
-                                    description: "Request body type name.\n\nThis specifies the data structure expected in the request body, that will\nbe transformed to {@link AutoBeOpenApi.IJsonSchema.IReference reference}\ntype in the {@link AutoBeOpenApi.IComponents.schemas components section}\nas an {@link AutoBeOpenApi.IJsonSchema.Object object} type.\n\nHere is the naming convention for the request body type:\n\n- `IEntityName.ICreate`: Request body for creation operations (POST)\n- `IEntityName.IUpdate`: Request body for update operations (PUT)\n- `IEntityName.IRequest`: Request parameters for list operations (often\n  with search/pagination)\n\nWhat you write:\n\n```json\n{\n  \"typeName\": \"IShoppingOrder.ICreate\"\n}\n```\n\nTransformed to:\n\n```json\n{\n  \"schema\": {\n    \"$ref\": \"#/components/schemas/IShoppingOrder.ICreate\"\n  }\n}\n```",
+                                    description: "Type name referencing a component schema.\n\nNaming convention: `IEntityName.ICreate` (POST), `IEntityName.IUpdate`\n(PUT), `IEntityName.IRequest` (list/search).",
                                     type: "string"
                                 }
                             },
@@ -1109,7 +1109,7 @@ function createReviewController(props) {
                         }
                     }
                 },
-                description: "Process operation review task or preliminary data requests.\n\nAnalyzes the operation for security vulnerabilities, schema compliance,\nlogical consistency, and standard adherence. Outputs structured thinking\nprocess and the production-ready operation.",
+                description: "Process operation review task or preliminary data requests.",
                 validate: (() => { const _io0 = input => "string" === typeof input.thinking && ("object" === typeof input.request && null !== input.request && _iu0(input.request)); const _io1 = input => "getAnalysisSections" === input.type && (Array.isArray(input.sectionIds) && (1 <= input.sectionIds.length && input.sectionIds.length <= 100 && input.sectionIds.every(elem => "number" === typeof elem && __typia_transform__isTypeUint32._isTypeUint32(elem)))); const _io2 = input => "getDatabaseSchemas" === input.type && (Array.isArray(input.schemaNames) && (1 <= input.schemaNames.length && input.schemaNames.every(elem => "string" === typeof elem))); const _io3 = input => "getPreviousAnalysisSections" === input.type && (Array.isArray(input.sectionIds) && (1 <= input.sectionIds.length && input.sectionIds.every(elem => "number" === typeof elem && __typia_transform__isTypeUint32._isTypeUint32(elem)))); const _io4 = input => "getPreviousDatabaseSchemas" === input.type && (Array.isArray(input.schemaNames) && (1 <= input.schemaNames.length && input.schemaNames.every(elem => "string" === typeof elem))); const _io5 = input => "getPreviousInterfaceOperations" === input.type && (Array.isArray(input.endpoints) && (1 <= input.endpoints.length && input.endpoints.every(elem => "object" === typeof elem && null !== elem && _io6(elem)))); const _io6 = input => "string" === typeof input.path && RegExp("^\\/[a-zA-Z0-9\\/_{}.-]*$").test(input.path) && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method); const _io7 = input => "complete" === input.type && "string" === typeof input.review && "string" === typeof input.plan && (null === input.content || "object" === typeof input.content && null !== input.content && _io8(input.content)); const _io8 = input => "string" === typeof input.specification && "string" === typeof input.description && (null === input.responseBody || "object" === typeof input.responseBody && null !== input.responseBody && _io9(input.responseBody)) && (null === input.requestBody || "object" === typeof input.requestBody && null !== input.requestBody && _io10(input.requestBody)); const _io9 = input => "string" === typeof input.description && "string" === typeof input.typeName; const _io10 = input => "string" === typeof input.description && "string" === typeof input.typeName; const _iu0 = input => (() => {
                     if ("getAnalysisSections" === input.type)
                         return _io1(input);