@autobe/agent 0.27.0 → 0.28.1

package/lib/orchestrate/interface/orchestrateInterfaceOperationsReview.js

@@ -456,7 +456,11 @@ function createReviewController(props) {
             };
         return result;
     };
-    const application = collection[props.model === "chatgpt" ? "chatgpt" : "claude"](validate);
+    const application = collection[props.model === "chatgpt"
+        ? "chatgpt"
+        : props.model === "gemini"
+            ? "gemini"
+            : "claude"](validate);
     return {
         protocol: "class",
         name: "review",
@@ -481,10 +485,11 @@ const collection = {
                 {
                     name: "reviewOperations",
                     parameters: {
-                        description: " Properties containing the thinking process (review & plan) and\nthe enhanced operations content\n\n------------------------------\n\nDescription of the current {@link IAutoBeInterfaceOperationsReviewApplication.IProps} type:\n\n> Properties for API operation review and improvement process.\n> \n> Contains both the input operations to be reviewed and the outputs generated\n> by the Interface Operations Review Agent, which will be published as part\n> of the AutoBeInterfaceOperationReviewEvent.\n\n### Description of {@link think} property:\n\n> Comprehensive thinking process for API operation review.\n> \n> Encapsulates the agent's analytical review findings and actionable\n> improvement plan. This structured thinking process ensures systematic\n> evaluation of API operations against AutoBE's quality standards before\n> generating the final enhanced operations.",
+                        description: " Properties containing the thinking process (review & plan) and\nthe enhanced operations content\n\n------------------------------\n\nDescription of the current {@link IAutoBeInterfaceOperationsReviewApplication.IProps} type:\n\n> Properties for API operation review and improvement process.\n> \n> Contains both the input operations to be reviewed and the outputs generated\n> by the Interface Operations Review Agent, which will be published as part\n> of the AutoBeInterfaceOperationReviewEvent.",
                         type: "object",
                         properties: {
                             think: {
+                                description: "Comprehensive thinking process for API operation review.\n\nEncapsulates the agent's analytical review findings and actionable\nimprovement plan. This structured thinking process ensures systematic\nevaluation of API operations against AutoBE's quality standards before\ngenerating the final enhanced operations.",
                                 $ref: "#/$defs/IAutoBeInterfaceOperationsReviewApplication.IThink"
                             },
                             content: {
@@ -843,10 +848,11 @@ const collection = {
                                 ]
                             },
                             "AutoBeOpenApi.IPrerequisite": {
-                                description: "Prerequisite API operation dependency.\n\n`IPrerequisite` defines a dependency relationship between API operations,\nspecifying that certain endpoints must be successfully called before the\ncurrent operation can proceed. This ensures proper resource validation,\nstate checking, and data availability in complex API workflows.\n\n## CRITICAL WARNING: Authentication is NOT a Prerequisite\n\n**NEVER use prerequisites for authentication or authorization checks!**\n\nPrerequisites are ONLY for business logic dependencies such as:\n\n- Checking if a resource exists\n- Verifying resource state\n- Loading required data\n\nDo NOT create prerequisites for:\n\n- Login/authentication endpoints\n- Token validation\n- Permission checks\n- User authorization verification\n\nAuthentication is handled separately via the `authorizationActor` field on\nthe operation itself. Mixing authentication with business prerequisites\ncreates confusion and incorrect test scenarios.\n\n## Core Concept\n\nPrerequisites create an execution dependency graph for API operations. They\nexplicitly declare which APIs must succeed before attempting the current\noperation, preventing invalid states and ensuring data consistency.\n\n## Structure\n\nEach prerequisite consists of:\n\n1. **endpoint**: The API endpoint that must be called first\n2. **description**: Clear explanation of why this prerequisite is required\n\n## Common Use Cases\n\n### 1. Resource Existence Validation\n\n```typescript\n{\n  \"endpoint\": { \"path\": \"/users/{userId}\", \"method\": \"get\" },\n  \"description\": \"User must exist before updating their profile\"\n}\n```\n\n### 2. Parent-Child Relationships\n\n```typescript\n{\n  \"endpoint\": { \"path\": \"/posts/{postId}\", \"method\": \"get\" },\n  \"description\": \"Post must exist before adding comments\"\n}\n```\n\n### 3. State Prerequisites\n\n```typescript\n{\n  \"endpoint\": { \"path\": \"/orders/{orderId}/status\", \"method\": \"get\" },\n  \"description\": \"Order must be in 'confirmed' state before shipping\"\n}\n```\n\n### 4. Business Logic Dependencies\n\n```typescript\n{\n  \"endpoint\": {\n    \"path\": \"/inventory/{productId}/stock\",\n    \"method\": \"get\"\n  },\n  \"description\": \"Product must have sufficient stock before creating order\"\n}\n```\n\n## Implementation Guidelines\n\n1. **Clear Descriptions**: Always explain WHY the prerequisite is needed\n2. **Minimal Dependencies**: Only include truly necessary prerequisites\n3. **Logical Order**: If multiple prerequisites exist, order them logically\n4. **Error Context**: Description should help understand failure scenarios\n5. **No Authentication**: Prerequisites must NEVER be authentication checks\n\n## Test Generation Usage\n\nThe Test Agent utilizes prerequisites to:\n\n- Set up test data in the correct sequence\n- Generate realistic test scenarios\n- Create both positive and negative test cases\n- Ensure proper cleanup in reverse dependency order\n\n## Best Practices\n\n- Keep prerequisite chains as short as possible for performance\n- Consider caching prerequisite results when safe to do so\n- Ensure prerequisite descriptions are specific, not generic\n- Validate that circular dependencies don't exist\n- Document any side effects of prerequisite calls\n- NEVER use for authentication/authorization validation\n\n### Description of {@link endpoint} property:\n\n> The API endpoint that must be called before the main operation.\n> \n> This specifies the exact HTTP method and path of the prerequisite API.\n> The endpoint must be a valid operation defined elsewhere in the API\n> specification. Path parameters in the prerequisite endpoint can reference\n> the same parameters available in the main operation.",
+                                description: "Prerequisite API operation dependency.\n\n`IPrerequisite` defines a dependency relationship between API operations,\nspecifying that certain endpoints must be successfully called before the\ncurrent operation can proceed. This ensures proper resource validation,\nstate checking, and data availability in complex API workflows.\n\n## CRITICAL WARNING: Authentication is NOT a Prerequisite\n\n**NEVER use prerequisites for authentication or authorization checks!**\n\nPrerequisites are ONLY for business logic dependencies such as:\n\n- Checking if a resource exists\n- Verifying resource state\n- Loading required data\n\nDo NOT create prerequisites for:\n\n- Login/authentication endpoints\n- Token validation\n- Permission checks\n- User authorization verification\n\nAuthentication is handled separately via the `authorizationActor` field on\nthe operation itself. Mixing authentication with business prerequisites\ncreates confusion and incorrect test scenarios.\n\n## Core Concept\n\nPrerequisites create an execution dependency graph for API operations. They\nexplicitly declare which APIs must succeed before attempting the current\noperation, preventing invalid states and ensuring data consistency.\n\n## Structure\n\nEach prerequisite consists of:\n\n1. **endpoint**: The API endpoint that must be called first\n2. **description**: Clear explanation of why this prerequisite is required\n\n## Common Use Cases\n\n### 1. Resource Existence Validation\n\n```typescript\n{\n  \"endpoint\": { \"path\": \"/users/{userId}\", \"method\": \"get\" },\n  \"description\": \"User must exist before updating their profile\"\n}\n```\n\n### 2. Parent-Child Relationships\n\n```typescript\n{\n  \"endpoint\": { \"path\": \"/posts/{postId}\", \"method\": \"get\" },\n  \"description\": \"Post must exist before adding comments\"\n}\n```\n\n### 3. State Prerequisites\n\n```typescript\n{\n  \"endpoint\": { \"path\": \"/orders/{orderId}/status\", \"method\": \"get\" },\n  \"description\": \"Order must be in 'confirmed' state before shipping\"\n}\n```\n\n### 4. Business Logic Dependencies\n\n```typescript\n{\n  \"endpoint\": {\n    \"path\": \"/inventory/{productId}/stock\",\n    \"method\": \"get\"\n  },\n  \"description\": \"Product must have sufficient stock before creating order\"\n}\n```\n\n## Implementation Guidelines\n\n1. **Clear Descriptions**: Always explain WHY the prerequisite is needed\n2. **Minimal Dependencies**: Only include truly necessary prerequisites\n3. **Logical Order**: If multiple prerequisites exist, order them logically\n4. **Error Context**: Description should help understand failure scenarios\n5. **No Authentication**: Prerequisites must NEVER be authentication checks\n\n## Test Generation Usage\n\nThe Test Agent utilizes prerequisites to:\n\n- Set up test data in the correct sequence\n- Generate realistic test scenarios\n- Create both positive and negative test cases\n- Ensure proper cleanup in reverse dependency order\n\n## Best Practices\n\n- Keep prerequisite chains as short as possible for performance\n- Consider caching prerequisite results when safe to do so\n- Ensure prerequisite descriptions are specific, not generic\n- Validate that circular dependencies don't exist\n- Document any side effects of prerequisite calls\n- NEVER use for authentication/authorization validation",
                                 type: "object",
                                 properties: {
                                     endpoint: {
+                                        description: "The API endpoint that must be called before the main operation.\n\nThis specifies the exact HTTP method and path of the prerequisite API.\nThe endpoint must be a valid operation defined elsewhere in the API\nspecification. Path parameters in the prerequisite endpoint can reference\nthe same parameters available in the main operation.",
                                         $ref: "#/$defs/AutoBeOpenApi.IEndpoint"
                                     },
                                     description: {
@@ -2062,5 +2068,781 @@ const collection = {
         }), { equals: false }));
         return application;
     })(),
+    gemini: (validate) => (() => {
+        const application = {
+            model: "gemini",
+            options: {
+                reference: true,
+                separate: null
+            },
+            functions: [
+                {
+                    name: "reviewOperations",
+                    parameters: {
+                        description: " Properties containing the thinking process (review & plan) and\nthe enhanced operations content\n\n------------------------------\n\nDescription of the current {@link IAutoBeInterfaceOperationsReviewApplication.IProps} type:\n\n> Properties for API operation review and improvement process.\n> \n> Contains both the input operations to be reviewed and the outputs generated\n> by the Interface Operations Review Agent, which will be published as part\n> of the AutoBeInterfaceOperationReviewEvent.",
+                        type: "object",
+                        properties: {
+                            think: {
+                                description: "Comprehensive thinking process for API operation review.\n\nEncapsulates the agent's analytical review findings and actionable\nimprovement plan. This structured thinking process ensures systematic\nevaluation of API operations against AutoBE's quality standards before\ngenerating the final enhanced operations.",
+                                $ref: "#/$defs/IAutoBeInterfaceOperationsReviewApplication.IThink"
+                            },
+                            content: {
+                                description: "Production-ready operations with all critical issues resolved.\n\nFinal API operations after systematic enhancement:\n\n- **Security Fixes Applied**: All authentication boundaries enforced,\n  sensitive data removed from responses, proper authorization\n  implemented\n- **Logic Corrections Made**: Return types match operation intent, HTTP\n  methods align with semantics, parameters properly utilized\n- **Schema Alignment Verified**: All fields exist in Prisma schema, types\n  correctly mapped, relationships properly defined\n- **Quality Improvements Added**: Enhanced documentation, format\n  specifications, validation rules, consistent naming patterns\n\nIf no issues were found during review, this contains the exact original\noperations unchanged. These operations are validated and ready for schema\ngeneration and subsequent implementation phases.",
+                                type: "array",
+                                items: {
+                                    $ref: "#/$defs/AutoBeOpenApi.IOperation"
+                                }
+                            }
+                        },
+                        required: [
+                            "think",
+                            "content"
+                        ],
+                        additionalProperties: false,
+                        $defs: {
+                            "IAutoBeInterfaceOperationsReviewApplication.IThink": {
+                                description: "Structured thinking process for comprehensive API operation review.\n\nCombines analytical review findings with actionable improvement planning to\nguide the systematic enhancement of API operations. This thinking structure\nensures all aspects of API quality are evaluated and addressed before\nproducing the final operations.",
+                                type: "object",
+                                properties: {
+                                    review: {
+                                        description: "Comprehensive review analysis with prioritized findings.\n\nSystematic assessment organized by severity levels (CRITICAL, HIGH,\nMEDIUM, LOW):\n\n- **Security Analysis**: Authentication boundary violations, exposed\n  passwords/tokens, unauthorized data access patterns, SQL injection\n  risks\n- **Logic Validation**: Return type consistency (list operations returning\n  arrays, single retrieval returning single items), HTTP method semantics\n  alignment, parameter usage verification\n- **Schema Compliance**: Field existence in Prisma schema, type accuracy,\n  relationship validity, required field handling\n- **Quality Assessment**: Documentation completeness, naming conventions,\n  error handling patterns, pagination standards\n\nEach finding includes specific examples, current vs expected behavior,\nand concrete fix recommendations. Critical security issues and logical\ncontradictions are highlighted for immediate attention.",
+                                        type: "string"
+                                    },
+                                    plan: {
+                                        description: "Prioritized action plan for identified issues.\n\nStructured improvement strategy categorized by severity:\n\n- **Immediate Actions (CRITICAL)**: Security vulnerabilities that must be\n  fixed before production (password exposure, missing authorization,\n  authentication bypass risks)\n- **Required Fixes (HIGH)**: Functional issues affecting API correctness\n  (wrong return types, missing required fields, schema mismatches)\n- **Recommended Improvements (MEDIUM)**: Quality enhancements for better\n  API design (validation rules, format specifications, consistency)\n- **Optional Enhancements (LOW)**: Documentation and usability improvements\n\nIf all operations pass review without issues, contains: \"No improvements\nrequired. All operations meet AutoBE standards.\"\n\nEach action item includes the specific operation path, the exact change\nneeded, and the rationale for the modification.",
+                                        type: "string"
+                                    }
+                                },
+                                required: [
+                                    "review",
+                                    "plan"
+                                ]
+                            },
+                            "AutoBeOpenApi.IOperation": {
+                                description: "Operation of the Restful API.\n\nThis interface defines a single API endpoint with its HTTP {@link method},\n{@link path}, {@link parameters path parameters},\n{@link requestBody request body}, and {@link responseBody} structure. It\ncorresponds to an individual operation in the paths section of an OpenAPI\ndocument.\n\nEach operation requires a detailed explanation of its purpose through the\nreason and description fields, making it clear why the API was designed and\nhow it should be used.\n\nAll request bodies and responses for this operation must be object types\nand must reference named types defined in the components section. The\ncontent-type is always `application/json`. For file upload/download\noperations, use `string & tags.Format<\"uri\">` in the appropriate schema\ninstead of binary data formats.\n\nIn OpenAPI, this might represent:\n\n```json\n{\n  \"/shoppings/customers/orders\": {\n    \"post\": {\n      \"description\": \"Create a new order application from shopping cart...\",\n      \"parameters\": [...],\n      \"requestBody\": {...},\n      \"responses\": {...},\n      ...\n    }\n  }\n}\n```",
+                                type: "object",
+                                properties: {
+                                    specification: {
+                                        description: "Specification of the API operation.\n\nBefore defining the API operation interface, please describe what you're\nplanning to write in this `specification` field.\n\nThe specification must be fully detailed and clear, so that anyone can\nunderstand the purpose and functionality of the API operation and its\nrelated components (e.g., {@link path}, {@link parameters},\n{@link requestBody}).\n\nIMPORTANT: The specification MUST identify which Prisma DB table this\noperation is associated with, helping ensure complete coverage of all\ndatabase entities.",
+                                        type: "string"
+                                    },
+                                    authorizationType: {
+                                        description: "Authorization type of the API operation.\n\n- `\"login\"`: User login operations that validate credentials\n- `\"join\"`: User registration operations that create accounts\n- `\"refresh\"`: Token refresh operations that renew access tokens\n- `null`: All other operations (CRUD, business logic, etc.)\n\nUse authentication values only for credential validation, user\nregistration, or token refresh operations. Use `null` for all other\nbusiness operations.\n\nExamples:\n\n- `/auth/login` \u2192 `\"login\"`\n- `/auth/register` \u2192 `\"join\"`\n- `/auth/refresh` \u2192 `\"refresh\"`\n- `/auth/validate` \u2192 `null`\n- `/users/{id}`, `/shoppings/customers/sales/cancel`, \u2192 `null`",
+                                        anyOf: [
+                                            {
+                                                type: "null"
+                                            },
+                                            {
+                                                type: "string",
+                                                "enum": [
+                                                    "login",
+                                                    "join",
+                                                    "refresh"
+                                                ]
+                                            }
+                                        ]
+                                    },
+                                    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 Prisma DB schema tables and\ncolumns. The description should be organized into MULTIPLE PARAGRAPHS\nseparated by line 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.",
+                                        type: "string"
+                                    },
+                                    summary: {
+                                        description: "Short summary of the API operation.\n\nThis should be a concise description of the API operation, typically one\nsentence long. It should provide a quick overview of what the API does\nwithout going into too much detail.\n\nThis summary will be used in the OpenAPI documentation to give users a\nquick understanding of the API operation's purpose.\n\nIMPORTANT: The summary should clearly indicate which Prisma DB table this\noperation relates to, helping to ensure all tables have API coverage.\n\n**CRITICAL WARNING about soft delete keywords**: DO NOT use terms like\n\"soft delete\", \"soft-delete\", or similar variations in this summary\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\n> MUST be written in English. Never use other languages",
+                                        type: "string"
+                                    },
+                                    parameters: {
+                                        description: "List of path parameters.\n\nNote that, the {@link AutoBeOpenApi.IParameter.name identifier name} of\npath parameter must be corresponded to the\n{@link path API operation path}.\n\nFor example, if there's an API operation which has {@link path} of\n`/shoppings/customers/sales/{saleId}/questions/${questionId}/comments/${commentId}`,\nits list of {@link AutoBeOpenApi.IParameter.name path parameters} must be\nlike:\n\n- `saleId`\n- `questionId`\n- `commentId`",
+                                        type: "array",
+                                        items: {
+                                            $ref: "#/$defs/AutoBeOpenApi.IParameter"
+                                        }
+                                    },
+                                    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.",
+                                        anyOf: [
+                                            {
+                                                type: "null"
+                                            },
+                                            {
+                                                $ref: "#/$defs/AutoBeOpenApi.IRequestBody"
+                                            }
+                                        ]
+                                    },
+                                    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.",
+                                        anyOf: [
+                                            {
+                                                type: "null"
+                                            },
+                                            {
+                                                $ref: "#/$defs/AutoBeOpenApi.IResponseBody"
+                                            }
+                                        ]
+                                    },
+                                    authorizationActor: {
+                                        description: "Authorization actor required to access this API operation.\n\nThis field specifies which user actor is allowed to access this endpoint.\nThe actor name must correspond exactly to the actual actors defined in\nyour system's Prisma schema.\n\n## Naming Convention\n\nActor names MUST use camelCase.\n\n## Actor-Based Path Convention\n\nWhen authorizationActor is specified, it should align with the path\nstructure:\n\n- If authorizationActor is \"admin\" \u2192 path might be \"/admin/resources/{id}\"\n- If authorizationActor is \"seller\" \u2192 path might be \"/seller/products\"\n- Special case: For user's own resources, use path prefix \"/my/\" regardless\n  of actor\n\n## Important Guidelines\n\n- Set to `null` for public endpoints that require no authentication\n- Set to specific actor string for actor-restricted endpoints\n- The actor name MUST match exactly with the user type/actor defined in the\n  database\n- This actor will be used by the Realize Agent to generate appropriate\n  decorator and authorization logic in the provider functions\n- The controller will apply the corresponding authentication decorator\n  based on this actor\n\n## Examples\n\n- `null` - Public endpoint, no authentication required\n- `\"user\"` - Any authenticated user can access\n- `\"admin\"` - Only admin users can access\n- `\"seller\"` - Only seller users can access\n- `\"moderator\"` - Only moderator users can access\n\nNote: The actual authentication/authorization implementation will be\nhandled by decorators at the controller level, and the provider function\nwill receive the authenticated user object with the appropriate type.",
+                                        anyOf: [
+                                            {
+                                                type: "null"
+                                            },
+                                            {
+                                                type: "string",
+                                                pattern: "^[a-z][a-zA-Z0-9]*$",
+                                                minLength: 1
+                                            }
+                                        ]
+                                    },
+                                    name: {
+                                        description: "Functional name of the API endpoint.\n\nThis is a semantic identifier that represents the primary function or\npurpose of the API endpoint. It serves as a canonical name that can be\nused for code generation, SDK method names, and internal references.\n\n## Reserved Word Restrictions\n\nCRITICAL: The name MUST NOT be a TypeScript/JavaScript reserved word, as\nit will be used as a class method name in generated code. Avoid names\nlike:\n\n- `delete`, `for`, `if`, `else`, `while`, `do`, `switch`, `case`, `break`\n- `continue`, `function`, `return`, `with`, `in`, `of`, `instanceof`\n- `typeof`, `void`, `var`, `let`, `const`, `class`, `extends`, `import`\n- `export`, `default`, `try`, `catch`, `finally`, `throw`, `new`\n- `super`, `this`, `null`, `true`, `false`, `async`, `await`\n- `yield`, `static`, `private`, `protected`, `public`, `implements`\n- `interface`, `package`, `enum`, `debugger`\n\nInstead, use alternative names for these operations:\n\n- Use `erase` instead of `delete`\n- Use `iterate` instead of `for`\n- Use `when` instead of `if`\n- Use `cls` instead of `class`\n\n## Standard Endpoint Names\n\nUse these conventional names based on the endpoint's primary function:\n\n- **`index`**: List/search operations that return multiple entities\n\n  - Typically used with PATCH method for complex queries\n  - Example: `PATCH /users` \u2192 `name: \"index\"`\n- **`at`**: Retrieve a specific entity by identifier\n\n  - Typically used with GET method on single resource\n  - Example: `GET /users/{userId}` \u2192 `name: \"at\"`\n- **`create`**: Create a new entity\n\n  - Typically used with POST method\n  - Example: `POST /users` \u2192 `name: \"create\"`\n- **`update`**: Update an existing entity\n\n  - Typically used with PUT method\n  - Example: `PUT /users/{userId}` \u2192 `name: \"update\"`\n- **`erase`**: Delete/remove an entity (NOT `delete` - reserved word!)\n\n  - Typically used with DELETE method\n  - Example: `DELETE /users/{userId}` \u2192 `name: \"erase\"`\n\n## Custom Endpoint Names\n\nFor specialized operations beyond basic CRUD, use descriptive verbs:\n\n- **`activate`**: Enable or turn on a feature/entity\n- **`deactivate`**: Disable or turn off a feature/entity\n- **`approve`**: Approve a request or entity\n- **`reject`**: Reject a request or entity\n- **`publish`**: Make content publicly available\n- **`archive`**: Move to archived state\n- **`restore`**: Restore from archived/deleted state\n- **`duplicate`**: Create a copy of an entity\n- **`transfer`**: Move ownership or change assignment\n- **`validate`**: Validate data or state\n- **`process`**: Execute a business process or workflow\n- **`export`**: Generate downloadable data\n- **`import`**: Process uploaded data\n\n## Naming Guidelines\n\n- MUST use camelCase naming convention\n- Use singular verb forms\n- Be concise but descriptive\n- Avoid abbreviations unless widely understood\n- Ensure the name clearly represents the endpoint's primary action\n- For nested resources, focus on the action rather than hierarchy\n- NEVER use JavaScript/TypeScript reserved words\n\nValid Examples:\n\n- `index`, `create`, `update`, `erase` (single word)\n- `updatePassword`, `cancelOrder`, `publishArticle` (camelCase)\n- `validateEmail`, `generateReport`, `exportData` (camelCase)\n\nInvalid Examples:\n\n- `update_password` (snake_case not allowed)\n- `UpdatePassword` (PascalCase not allowed)\n- `update-password` (kebab-case not allowed)\n\nPath to Name Examples:\n\n- `GET /shopping/orders/{orderId}/items` \u2192 `name: \"index\"` (lists items)\n- `POST /shopping/orders/{orderId}/cancel` \u2192 `name: \"cancel\"`\n- `PUT /users/{userId}/password` \u2192 `name: \"updatePassword\"`\n\n## Uniqueness Rule\n\nThe `name` must be unique within the API's accessor namespace. The\naccessor is formed by combining the path segments (excluding parameters)\nwith the operation name.\n\nAccessor formation:\n\n1. Extract non-parameter segments from the path (remove `{...}` parts)\n2. Join segments with dots\n3. Append the operation name\n\nExamples:\n\n- Path: `/shopping/sale/{saleId}/review/{reviewId}`, Name: `at` \u2192 Accessor:\n  `shopping.sale.review.at`\n- Path: `/users/{userId}/posts`, Name: `index` \u2192 Accessor:\n  `users.posts.index`\n- Path: `/auth/login`, Name: `signIn` \u2192 Accessor: `auth.login.signIn`\n\nEach accessor must be globally unique across the entire API. This ensures\noperations can be uniquely identified in generated SDKs and prevents\nnaming conflicts.",
+                                        type: "string",
+                                        pattern: "^[a-z][a-zA-Z0-9]*$"
+                                    },
+                                    prerequisites: {
+                                        description: "Prerequisites for this API operation.\n\nThe `prerequisites` field defines API operations that must be\nsuccessfully executed before this operation can be performed. This\ncreates an explicit dependency chain between API endpoints, ensuring\nproper execution order and data availability.\n\n## CRITICAL WARNING: Authentication Prerequisites\n\n**NEVER include authentication-related operations as prerequisites!**\nAuthentication is handled separately through the `authorizationActor`\nfield and should NOT be part of the prerequisite chain. Do NOT add\nprerequisites for:\n\n- Login endpoints\n- Token validation endpoints\n- User authentication checks\n- Permission verification endpoints\n\nPrerequisites are ONLY for business logic dependencies, NOT for\nauthentication/authorization.\n\n## Purpose and Use Cases\n\nPrerequisites are essential for operations that depend on:\n\n1. **Existence Validation**: Ensuring resources exist before manipulation\n2. **State Requirements**: Verifying resources are in the correct state\n3. **Data Dependencies**: Loading necessary data for the current operation\n4. **Business Logic Constraints**: Enforcing domain-specific rules\n\n## Execution Flow\n\nWhen an operation has prerequisites:\n\n1. Each prerequisite API must be called first in the specified order\n2. Prerequisites must return successful responses (2xx status codes)\n3. Only after all prerequisites succeed can the main operation proceed\n4. If any prerequisite fails, the operation should not be attempted\n\n## Common Patterns\n\n### Resource Existence Check\n\n```typescript\n// Before updating an order item, ensure the order exists\nprerequisites: [\n  {\n    endpoint: { path: \"/orders/{orderId}\", method: \"get\" },\n    description: \"Order must exist in the system\",\n  },\n];\n```\n\n### State Validation\n\n```typescript\n// Before processing payment, ensure order is in correct state\nprerequisites: [\n  {\n    endpoint: { path: \"/orders/{orderId}/status\", method: \"get\" },\n    description: \"Order must be in 'pending_payment' status\",\n  },\n];\n```\n\n### Hierarchical Dependencies\n\n```typescript\n// Before accessing a deeply nested resource\nprerequisites: [\n  {\n    endpoint: { path: \"/projects/{projectId}\", method: \"get\" },\n    description: \"Project must exist\",\n  },\n  {\n    endpoint: {\n      path: \"/projects/{projectId}/tasks/{taskId}\",\n      method: \"get\",\n    },\n    description: \"Task must exist within the project\",\n  },\n];\n```\n\n## Important Guidelines\n\n1. **Order Matters**: Prerequisites are executed in array order\n2. **Parameter Inheritance**: Path parameters from prerequisites can be used\n   in the main operation\n3. **Error Handling**: Failed prerequisites should prevent main operation\n4. **Performance**: Consider caching prerequisite results when appropriate\n5. **Documentation**: Each prerequisite must have a clear description\n   explaining why it's required\n6. **No Authentication**: NEVER use prerequisites for authentication checks\n\n## Test Generation Impact\n\nThe Test Agent uses prerequisites to:\n\n- Generate proper test setup sequences\n- Create valid test data in the correct order\n- Ensure test scenarios follow realistic workflows\n- Validate error handling when prerequisites fail",
+                                        type: "array",
+                                        items: {
+                                            $ref: "#/$defs/AutoBeOpenApi.IPrerequisite"
+                                        }
+                                    },
+                                    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)",
+                                        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",
+                                        type: "string",
+                                        "enum": [
+                                            "get",
+                                            "post",
+                                            "put",
+                                            "delete",
+                                            "patch"
+                                        ]
+                                    }
+                                },
+                                required: [
+                                    "specification",
+                                    "authorizationType",
+                                    "description",
+                                    "summary",
+                                    "parameters",
+                                    "requestBody",
+                                    "responseBody",
+                                    "authorizationActor",
+                                    "name",
+                                    "prerequisites",
+                                    "path",
+                                    "method"
+                                ]
+                            },
+                            "AutoBeOpenApi.IParameter": {
+                                description: "Path parameter information for API routes.\n\nThis interface defines a path parameter that appears in the URL of an API\nendpoint. Path parameters are enclosed in curly braces in the\n{@link AutoBeOpenApi.IOperation.path operation path} and must be defined\nwith their types and descriptions.\n\nFor example, if API operation path is\n`/shoppings/customers/sales/{saleId}/questions/${questionId}/comments/${commentId}`,\nthe path parameters should be like below:\n\n```json\n{\n  \"path\": \"/shoppings/customers/sales/{saleId}/questions/${questionId}/comments/${commentId}\",\n  \"method\": \"get\",\n  \"parameters\": [\n    {\n      \"name\": \"saleId\",\n      \"in\": \"path\",\n      \"schema\": { \"type\": \"string\", \"format\": \"uuid\" },\n      \"description\": \"Target sale's ID\"\n    },\n    {\n      \"name\": \"questionId\",\n      \"in\": \"path\",\n      \"schema\": { \"type\": \"string\", \"format\": \"uuid\" },\n      \"description\": \"Target question's ID\"\n    },\n    {\n      \"name\": \"commentId\",\n      \"in\": \"path\",\n      \"schema\": { \"type\": \"string\", \"format\": \"uuid\" },\n      \"description\": \"Target comment's ID\"\n    }\n  ]\n}\n```",
+                                type: "object",
+                                properties: {
+                                    name: {
+                                        description: "Identifier name of the path parameter.\n\nThis name must match exactly with the parameter name in the route path.\nIt must be corresponded to the\n{@link AutoBeOpenApi.IOperation.path API operation path}.\n\nMUST use camelCase naming convention.",
+                                        type: "string",
+                                        pattern: "^[a-z][a-zA-Z0-9]*$"
+                                    },
+                                    description: {
+                                        description: "Description about the path parameter.\n\nMake short, concise and clear description about the path parameter.\n\n> MUST be written in English. Never use other languages.",
+                                        type: "string"
+                                    },
+                                    schema: {
+                                        description: "Type schema of the path parameter.\n\nPath parameters are typically primitive types like\n{@link AutoBeOpenApi.IJsonSchema.IString strings},\n{@link AutoBeOpenApi.IJsonSchema.IInteger integers},\n{@link AutoBeOpenApi.IJsonSchema.INumber numbers}.\n\nIf you need other types, please use request body instead with object type\nencapsulation.",
+                                        anyOf: [
+                                            {
+                                                $ref: "#/$defs/AutoBeOpenApi.IJsonSchema.INumber"
+                                            },
+                                            {
+                                                $ref: "#/$defs/AutoBeOpenApi.IJsonSchema.IInteger"
+                                            },
+                                            {
+                                                $ref: "#/$defs/AutoBeOpenApi.IJsonSchema.IString"
+                                            }
+                                        ],
+                                        "x-discriminator": {
+                                            propertyName: "type",
+                                            mapping: {
+                                                number: "#/$defs/AutoBeOpenApi.IJsonSchema.INumber",
+                                                integer: "#/$defs/AutoBeOpenApi.IJsonSchema.IInteger",
+                                                string: "#/$defs/AutoBeOpenApi.IJsonSchema.IString"
+                                            }
+                                        }
+                                    }
+                                },
+                                required: [
+                                    "name",
+                                    "description",
+                                    "schema"
+                                ]
+                            },
+                            "AutoBeOpenApi.IJsonSchema.INumber": {
+                                description: "Number (double) type info.",
+                                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.",
+                                        type: "string",
+                                        "enum": [
+                                            "number"
+                                        ]
+                                    }
+                                },
+                                required: [
+                                    "type"
+                                ]
+                            },
+                            "AutoBeOpenApi.IJsonSchema.IInteger": {
+                                description: "Integer type info.",
+                                type: "object",
+                                properties: {
+                                    minimum: {
+                                        description: "Minimum value restriction.",
+                                        type: "integer"
+                                    },
+                                    maximum: {
+                                        description: "Maximum value restriction.",
+                                        type: "integer"
+                                    },
+                                    exclusiveMinimum: {
+                                        description: "Exclusive minimum value restriction.",
+                                        type: "number"
+                                    },
+                                    exclusiveMaximum: {
+                                        description: "Exclusive maximum value restriction.",
+                                        type: "number"
+                                    },
+                                    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.",
+                                        type: "string",
+                                        "enum": [
+                                            "integer"
+                                        ]
+                                    }
+                                },
+                                required: [
+                                    "type"
+                                ]
+                            },
+                            "AutoBeOpenApi.IJsonSchema.IString": {
+                                description: "String type info.",
+                                type: "object",
+                                properties: {
+                                    format: {
+                                        description: "Format restriction.",
+                                        type: "string",
+                                        "enum": [
+                                            "date-time",
+                                            "password",
+                                            "regex",
+                                            "uuid",
+                                            "email",
+                                            "hostname",
+                                            "idn-email",
+                                            "idn-hostname",
+                                            "iri",
+                                            "iri-reference",
+                                            "ipv4",
+                                            "ipv6",
+                                            "uri",
+                                            "uri-reference",
+                                            "uri-template",
+                                            "url",
+                                            "date",
+                                            "time",
+                                            "duration",
+                                            "json-pointer",
+                                            "relative-json-pointer"
+                                        ]
+                                    },
+                                    pattern: {
+                                        description: "Pattern restriction.",
+                                        type: "string"
+                                    },
+                                    contentMediaType: {
+                                        description: "Content media type restriction.",
+                                        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.",
+                                        type: "string",
+                                        "enum": [
+                                            "string"
+                                        ]
+                                    }
+                                },
+                                required: [
+                                    "type"
+                                ]
+                            },
+                            "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```",
+                                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.",
+                                        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```",
+                                        type: "string"
+                                    }
+                                },
+                                required: [
+                                    "description",
+                                    "typeName"
+                                ]
+                            },
+                            "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```",
+                                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.",
+                                        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```",
+                                        type: "string"
+                                    }
+                                },
+                                required: [
+                                    "description",
+                                    "typeName"
+                                ]
+                            },
+                            "AutoBeOpenApi.IPrerequisite": {
+                                description: "Prerequisite API operation dependency.\n\n`IPrerequisite` defines a dependency relationship between API operations,\nspecifying that certain endpoints must be successfully called before the\ncurrent operation can proceed. This ensures proper resource validation,\nstate checking, and data availability in complex API workflows.\n\n## CRITICAL WARNING: Authentication is NOT a Prerequisite\n\n**NEVER use prerequisites for authentication or authorization checks!**\n\nPrerequisites are ONLY for business logic dependencies such as:\n\n- Checking if a resource exists\n- Verifying resource state\n- Loading required data\n\nDo NOT create prerequisites for:\n\n- Login/authentication endpoints\n- Token validation\n- Permission checks\n- User authorization verification\n\nAuthentication is handled separately via the `authorizationActor` field on\nthe operation itself. Mixing authentication with business prerequisites\ncreates confusion and incorrect test scenarios.\n\n## Core Concept\n\nPrerequisites create an execution dependency graph for API operations. They\nexplicitly declare which APIs must succeed before attempting the current\noperation, preventing invalid states and ensuring data consistency.\n\n## Structure\n\nEach prerequisite consists of:\n\n1. **endpoint**: The API endpoint that must be called first\n2. **description**: Clear explanation of why this prerequisite is required\n\n## Common Use Cases\n\n### 1. Resource Existence Validation\n\n```typescript\n{\n  \"endpoint\": { \"path\": \"/users/{userId}\", \"method\": \"get\" },\n  \"description\": \"User must exist before updating their profile\"\n}\n```\n\n### 2. Parent-Child Relationships\n\n```typescript\n{\n  \"endpoint\": { \"path\": \"/posts/{postId}\", \"method\": \"get\" },\n  \"description\": \"Post must exist before adding comments\"\n}\n```\n\n### 3. State Prerequisites\n\n```typescript\n{\n  \"endpoint\": { \"path\": \"/orders/{orderId}/status\", \"method\": \"get\" },\n  \"description\": \"Order must be in 'confirmed' state before shipping\"\n}\n```\n\n### 4. Business Logic Dependencies\n\n```typescript\n{\n  \"endpoint\": {\n    \"path\": \"/inventory/{productId}/stock\",\n    \"method\": \"get\"\n  },\n  \"description\": \"Product must have sufficient stock before creating order\"\n}\n```\n\n## Implementation Guidelines\n\n1. **Clear Descriptions**: Always explain WHY the prerequisite is needed\n2. **Minimal Dependencies**: Only include truly necessary prerequisites\n3. **Logical Order**: If multiple prerequisites exist, order them logically\n4. **Error Context**: Description should help understand failure scenarios\n5. **No Authentication**: Prerequisites must NEVER be authentication checks\n\n## Test Generation Usage\n\nThe Test Agent utilizes prerequisites to:\n\n- Set up test data in the correct sequence\n- Generate realistic test scenarios\n- Create both positive and negative test cases\n- Ensure proper cleanup in reverse dependency order\n\n## Best Practices\n\n- Keep prerequisite chains as short as possible for performance\n- Consider caching prerequisite results when safe to do so\n- Ensure prerequisite descriptions are specific, not generic\n- Validate that circular dependencies don't exist\n- Document any side effects of prerequisite calls\n- NEVER use for authentication/authorization validation",
+                                type: "object",
+                                properties: {
+                                    endpoint: {
+                                        description: "The API endpoint that must be called before the main operation.\n\nThis specifies the exact HTTP method and path of the prerequisite API.\nThe endpoint must be a valid operation defined elsewhere in the API\nspecification. Path parameters in the prerequisite endpoint can reference\nthe same parameters available in the main operation.",
+                                        $ref: "#/$defs/AutoBeOpenApi.IEndpoint"
+                                    },
+                                    description: {
+                                        description: "Clear description of why this prerequisite is required.\n\nThis description should explain:\n\n- What validation or check this prerequisite performs\n- What state or condition must be satisfied\n- What happens if this prerequisite fails\n- Any specific data from the prerequisite used by the main operation\n\nThe description helps developers understand the dependency relationship\nand aids in debugging when prerequisites fail.\n\nGuidelines for good descriptions:\n\n- Be specific about the requirement (e.g., \"must be in 'active' state\")\n- Explain business logic constraints (e.g., \"budget must not be exceeded\")\n- Explain data dependencies (e.g., \"provides pricing information needed\")\n- Keep it concise but complete\n\n> MUST be written in English. Never use other languages.",
+                                        type: "string"
+                                    }
+                                },
+                                required: [
+                                    "endpoint",
+                                    "description"
+                                ]
+                            },
+                            "AutoBeOpenApi.IEndpoint": {
+                                description: "API endpoint information.",
+                                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)",
+                                        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",
+                                        type: "string",
+                                        "enum": [
+                                            "get",
+                                            "post",
+                                            "put",
+                                            "delete",
+                                            "patch"
+                                        ]
+                                    }
+                                },
+                                required: [
+                                    "path",
+                                    "method"
+                                ]
+                            }
+                        }
+                    },
+                    description: "Reviews a batch of API operations for quality and correctness.\n\nAnalyzes operations for security vulnerabilities, schema compliance,\nlogical consistency, and standard adherence. Outputs a structured thinking\nprocess containing review findings and improvement plans, plus the final\nproduction-ready operations with all critical issues resolved.",
+                    validate: (() => { const _iv4 = new Set(["date-time", "password", "regex", "uuid", "email", "hostname", "idn-email", "idn-hostname", "iri", "iri-reference", "ipv4", "ipv6", "uri", "uri-reference", "uri-template", "url", "date", "time", "duration", "json-pointer", "relative-json-pointer"]); const _vv8 = new Set(["date-time", "password", "regex", "uuid", "email", "hostname", "idn-email", "idn-hostname", "iri", "iri-reference", "ipv4", "ipv6", "uri", "uri-reference", "uri-template", "url", "date", "time", "duration", "json-pointer", "relative-json-pointer"]); const _io0 = input => "object" === typeof input.think && null !== input.think && _io1(input.think) && (Array.isArray(input.content) && input.content.every(elem => "object" === typeof elem && null !== elem && _io2(elem))); const _io1 = input => "string" === typeof input.review && "string" === typeof input.plan; const _io2 = input => "string" === typeof input.specification && (null === input.authorizationType || "login" === input.authorizationType || "join" === input.authorizationType || "refresh" === input.authorizationType) && "string" === typeof input.description && "string" === typeof input.summary && (Array.isArray(input.parameters) && input.parameters.every(elem => "object" === typeof elem && null !== elem && _io3(elem))) && (null === input.requestBody || "object" === typeof input.requestBody && null !== input.requestBody && _io7(input.requestBody)) && (null === input.responseBody || "object" === typeof input.responseBody && null !== input.responseBody && _io8(input.responseBody)) && (null === input.authorizationActor || "string" === typeof input.authorizationActor && (RegExp("^[a-z][a-zA-Z0-9]*$").test(input.authorizationActor) && 1 <= input.authorizationActor.length)) && ("string" === typeof input.name && RegExp("^[a-z][a-zA-Z0-9]*$").test(input.name)) && (Array.isArray(input.prerequisites) && input.prerequisites.every(elem => "object" === typeof elem && null !== elem && _io9(elem))) && ("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 _io3 = input => "string" === typeof input.name && RegExp("^[a-z][a-zA-Z0-9]*$").test(input.name) && "string" === typeof input.description && ("object" === typeof input.schema && null !== input.schema && _iu0(input.schema)); const _io4 = 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) && (undefined === input.exclusiveMaximum || "number" === typeof input.exclusiveMaximum) && (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 _io5 = 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 _io6 = input => (undefined === input.format || true === _iv4.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 _io7 = input => "string" === typeof input.description && "string" === typeof input.typeName; const _io8 = input => "string" === typeof input.description && "string" === typeof input.typeName; const _io9 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io10(input.endpoint) && "string" === typeof input.description; const _io10 = 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 _iu0 = input => (() => {
+                        if ("number" === input.type)
+                            return _io5(input);
+                        else if ("integer" === input.type)
+                            return _io4(input);
+                        else if ("string" === input.type)
+                            return _io6(input);
+                        else
+                            return false;
+                    })(); const _vo0 = (input, _path, _exceptionable = true) => [("object" === typeof input.think && null !== input.think || _report(_exceptionable, {
+                            path: _path + ".think",
+                            expected: "IAutoBeInterfaceOperationsReviewApplication.IThink",
+                            value: input.think
+                        })) && _vo1(input.think, _path + ".think", true && _exceptionable) || _report(_exceptionable, {
+                            path: _path + ".think",
+                            expected: "IAutoBeInterfaceOperationsReviewApplication.IThink",
+                            value: input.think
+                        }), (Array.isArray(input.content) || _report(_exceptionable, {
+                            path: _path + ".content",
+                            expected: "Array<AutoBeOpenApi.IOperation>",
+                            value: input.content
+                        })) && input.content.map((elem, _index5) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                            path: _path + ".content[" + _index5 + "]",
+                            expected: "AutoBeOpenApi.IOperation",
+                            value: elem
+                        })) && _vo2(elem, _path + ".content[" + _index5 + "]", true && _exceptionable) || _report(_exceptionable, {
+                            path: _path + ".content[" + _index5 + "]",
+                            expected: "AutoBeOpenApi.IOperation",
+                            value: elem
+                        })).every(flag => flag) || _report(_exceptionable, {
+                            path: _path + ".content",
+                            expected: "Array<AutoBeOpenApi.IOperation>",
+                            value: input.content
+                        })].every(flag => flag); const _vo1 = (input, _path, _exceptionable = true) => ["string" === typeof input.review || _report(_exceptionable, {
+                            path: _path + ".review",
+                            expected: "string",
+                            value: input.review
+                        }), "string" === typeof input.plan || _report(_exceptionable, {
+                            path: _path + ".plan",
+                            expected: "string",
+                            value: input.plan
+                        })].every(flag => flag); const _vo2 = (input, _path, _exceptionable = true) => ["string" === typeof input.specification || _report(_exceptionable, {
+                            path: _path + ".specification",
+                            expected: "string",
+                            value: input.specification
+                        }), null === input.authorizationType || "login" === input.authorizationType || "join" === input.authorizationType || "refresh" === input.authorizationType || _report(_exceptionable, {
+                            path: _path + ".authorizationType",
+                            expected: "(\"join\" | \"login\" | \"refresh\" | null)",
+                            value: input.authorizationType
+                        }), "string" === typeof input.description || _report(_exceptionable, {
+                            path: _path + ".description",
+                            expected: "string",
+                            value: input.description
+                        }), "string" === typeof input.summary || _report(_exceptionable, {
+                            path: _path + ".summary",
+                            expected: "string",
+                            value: input.summary
+                        }), (Array.isArray(input.parameters) || _report(_exceptionable, {
+                            path: _path + ".parameters",
+                            expected: "Array<AutoBeOpenApi.IParameter>",
+                            value: input.parameters
+                        })) && input.parameters.map((elem, _index6) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                            path: _path + ".parameters[" + _index6 + "]",
+                            expected: "AutoBeOpenApi.IParameter",
+                            value: elem
+                        })) && _vo3(elem, _path + ".parameters[" + _index6 + "]", true && _exceptionable) || _report(_exceptionable, {
+                            path: _path + ".parameters[" + _index6 + "]",
+                            expected: "AutoBeOpenApi.IParameter",
+                            value: elem
+                        })).every(flag => flag) || _report(_exceptionable, {
+                            path: _path + ".parameters",
+                            expected: "Array<AutoBeOpenApi.IParameter>",
+                            value: input.parameters
+                        }), null === input.requestBody || ("object" === typeof input.requestBody && null !== input.requestBody || _report(_exceptionable, {
+                            path: _path + ".requestBody",
+                            expected: "(AutoBeOpenApi.IRequestBody | null)",
+                            value: input.requestBody
+                        })) && _vo7(input.requestBody, _path + ".requestBody", true && _exceptionable) || _report(_exceptionable, {
+                            path: _path + ".requestBody",
+                            expected: "(AutoBeOpenApi.IRequestBody | null)",
+                            value: input.requestBody
+                        }), null === input.responseBody || ("object" === typeof input.responseBody && null !== input.responseBody || _report(_exceptionable, {
+                            path: _path + ".responseBody",
+                            expected: "(AutoBeOpenApi.IResponseBody | null)",
+                            value: input.responseBody
+                        })) && _vo8(input.responseBody, _path + ".responseBody", true && _exceptionable) || _report(_exceptionable, {
+                            path: _path + ".responseBody",
+                            expected: "(AutoBeOpenApi.IResponseBody | null)",
+                            value: input.responseBody
+                        }), null === input.authorizationActor || "string" === typeof input.authorizationActor && (RegExp("^[a-z][a-zA-Z0-9]*$").test(input.authorizationActor) || _report(_exceptionable, {
+                            path: _path + ".authorizationActor",
+                            expected: "string & CamelCasePattern",
+                            value: input.authorizationActor
+                        })) && (1 <= input.authorizationActor.length || _report(_exceptionable, {
+                            path: _path + ".authorizationActor",
+                            expected: "string & MinLength<1>",
+                            value: input.authorizationActor
+                        })) || _report(_exceptionable, {
+                            path: _path + ".authorizationActor",
+                            expected: "((string & CamelCasePattern & MinLength<1>) | null)",
+                            value: input.authorizationActor
+                        }), "string" === typeof input.name && (RegExp("^[a-z][a-zA-Z0-9]*$").test(input.name) || _report(_exceptionable, {
+                            path: _path + ".name",
+                            expected: "string & CamelCasePattern",
+                            value: input.name
+                        })) || _report(_exceptionable, {
+                            path: _path + ".name",
+                            expected: "(string & CamelCasePattern)",
+                            value: input.name
+                        }), (Array.isArray(input.prerequisites) || _report(_exceptionable, {
+                            path: _path + ".prerequisites",
+                            expected: "Array<AutoBeOpenApi.IPrerequisite>",
+                            value: input.prerequisites
+                        })) && input.prerequisites.map((elem, _index7) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                            path: _path + ".prerequisites[" + _index7 + "]",
+                            expected: "AutoBeOpenApi.IPrerequisite",
+                            value: elem
+                        })) && _vo9(elem, _path + ".prerequisites[" + _index7 + "]", true && _exceptionable) || _report(_exceptionable, {
+                            path: _path + ".prerequisites[" + _index7 + "]",
+                            expected: "AutoBeOpenApi.IPrerequisite",
+                            value: elem
+                        })).every(flag => flag) || _report(_exceptionable, {
+                            path: _path + ".prerequisites",
+                            expected: "Array<AutoBeOpenApi.IPrerequisite>",
+                            value: input.prerequisites
+                        }), "string" === typeof input.path && (RegExp("^\\/[a-zA-Z0-9\\/_{}.-]*$").test(input.path) || _report(_exceptionable, {
+                            path: _path + ".path",
+                            expected: "string & Pattern<\"^\\\\/[a-zA-Z0-9\\\\/_{}.-]*$\">",
+                            value: input.path
+                        })) || _report(_exceptionable, {
+                            path: _path + ".path",
+                            expected: "(string & Pattern<\"^\\\\/[a-zA-Z0-9\\\\/_{}.-]*$\">)",
+                            value: input.path
+                        }), "get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method || _report(_exceptionable, {
+                            path: _path + ".method",
+                            expected: "(\"delete\" | \"get\" | \"patch\" | \"post\" | \"put\")",
+                            value: input.method
+                        })].every(flag => flag); const _vo3 = (input, _path, _exceptionable = true) => ["string" === typeof input.name && (RegExp("^[a-z][a-zA-Z0-9]*$").test(input.name) || _report(_exceptionable, {
+                            path: _path + ".name",
+                            expected: "string & CamelCasePattern",
+                            value: input.name
+                        })) || _report(_exceptionable, {
+                            path: _path + ".name",
+                            expected: "(string & CamelCasePattern)",
+                            value: input.name
+                        }), "string" === typeof input.description || _report(_exceptionable, {
+                            path: _path + ".description",
+                            expected: "string",
+                            value: input.description
+                        }), ("object" === typeof input.schema && null !== input.schema || _report(_exceptionable, {
+                            path: _path + ".schema",
+                            expected: "(AutoBeOpenApi.IJsonSchema.IInteger | AutoBeOpenApi.IJsonSchema.INumber | AutoBeOpenApi.IJsonSchema.IString)",
+                            value: input.schema
+                        })) && _vu0(input.schema, _path + ".schema", true && _exceptionable) || _report(_exceptionable, {
+                            path: _path + ".schema",
+                            expected: "(AutoBeOpenApi.IJsonSchema.IInteger | AutoBeOpenApi.IJsonSchema.INumber | AutoBeOpenApi.IJsonSchema.IString)",
+                            value: input.schema
+                        })].every(flag => flag); const _vo4 = (input, _path, _exceptionable = true) => [undefined === input.minimum || "number" === typeof input.minimum && (Math.floor(input.minimum) === input.minimum && -9223372036854776000 <= input.minimum && input.minimum <= 9223372036854776000 || _report(_exceptionable, {
+                            path: _path + ".minimum",
+                            expected: "number & Type<\"int64\">",
+                            value: input.minimum
+                        })) || _report(_exceptionable, {
+                            path: _path + ".minimum",
+                            expected: "((number & Type<\"int64\">) | undefined)",
+                            value: input.minimum
+                        }), undefined === input.maximum || "number" === typeof input.maximum && (Math.floor(input.maximum) === input.maximum && -9223372036854776000 <= input.maximum && input.maximum <= 9223372036854776000 || _report(_exceptionable, {
+                            path: _path + ".maximum",
+                            expected: "number & Type<\"int64\">",
+                            value: input.maximum
+                        })) || _report(_exceptionable, {
+                            path: _path + ".maximum",
+                            expected: "((number & Type<\"int64\">) | undefined)",
+                            value: input.maximum
+                        }), undefined === input.exclusiveMinimum || "number" === typeof input.exclusiveMinimum || _report(_exceptionable, {
+                            path: _path + ".exclusiveMinimum",
+                            expected: "(number | undefined)",
+                            value: input.exclusiveMinimum
+                        }), undefined === input.exclusiveMaximum || "number" === typeof input.exclusiveMaximum || _report(_exceptionable, {
+                            path: _path + ".exclusiveMaximum",
+                            expected: "(number | undefined)",
+                            value: input.exclusiveMaximum
+                        }), undefined === input.multipleOf || "number" === typeof input.multipleOf && (Math.floor(input.multipleOf) === input.multipleOf && 0 <= input.multipleOf && input.multipleOf <= 18446744073709552000 || _report(_exceptionable, {
+                            path: _path + ".multipleOf",
+                            expected: "number & Type<\"uint64\">",
+                            value: input.multipleOf
+                        })) && (0 < input.multipleOf || _report(_exceptionable, {
+                            path: _path + ".multipleOf",
+                            expected: "number & ExclusiveMinimum<0>",
+                            value: input.multipleOf
+                        })) || _report(_exceptionable, {
+                            path: _path + ".multipleOf",
+                            expected: "((number & Type<\"uint64\"> & ExclusiveMinimum<0>) | undefined)",
+                            value: input.multipleOf
+                        }), "integer" === input.type || _report(_exceptionable, {
+                            path: _path + ".type",
+                            expected: "\"integer\"",
+                            value: input.type
+                        })].every(flag => flag); const _vo5 = (input, _path, _exceptionable = true) => [undefined === input.minimum || "number" === typeof input.minimum || _report(_exceptionable, {
+                            path: _path + ".minimum",
+                            expected: "(number | undefined)",
+                            value: input.minimum
+                        }), undefined === input.maximum || "number" === typeof input.maximum || _report(_exceptionable, {
+                            path: _path + ".maximum",
+                            expected: "(number | undefined)",
+                            value: input.maximum
+                        }), undefined === input.exclusiveMinimum || "number" === typeof input.exclusiveMinimum || _report(_exceptionable, {
+                            path: _path + ".exclusiveMinimum",
+                            expected: "(number | undefined)",
+                            value: input.exclusiveMinimum
+                        }), undefined === input.exclusiveMaximum || "number" === typeof input.exclusiveMaximum || _report(_exceptionable, {
+                            path: _path + ".exclusiveMaximum",
+                            expected: "(number | undefined)",
+                            value: input.exclusiveMaximum
+                        }), undefined === input.multipleOf || "number" === typeof input.multipleOf && (0 < input.multipleOf || _report(_exceptionable, {
+                            path: _path + ".multipleOf",
+                            expected: "number & ExclusiveMinimum<0>",
+                            value: input.multipleOf
+                        })) || _report(_exceptionable, {
+                            path: _path + ".multipleOf",
+                            expected: "((number & ExclusiveMinimum<0>) | undefined)",
+                            value: input.multipleOf
+                        }), "number" === input.type || _report(_exceptionable, {
+                            path: _path + ".type",
+                            expected: "\"number\"",
+                            value: input.type
+                        })].every(flag => flag); const _vo6 = (input, _path, _exceptionable = true) => [undefined === input.format || true === _vv8.has(input.format) || _report(_exceptionable, {
+                            path: _path + ".format",
+                            expected: "(\"date\" | \"date-time\" | \"duration\" | \"email\" | \"hostname\" | \"idn-email\" | \"idn-hostname\" | \"ipv4\" | \"ipv6\" | \"iri\" | \"iri-reference\" | \"json-pointer\" | \"password\" | \"regex\" | \"relative-json-pointer\" | \"time\" | \"uri\" | \"uri-reference\" | \"uri-template\" | \"url\" | \"uuid\" | undefined)",
+                            value: input.format
+                        }), undefined === input.pattern || "string" === typeof input.pattern || _report(_exceptionable, {
+                            path: _path + ".pattern",
+                            expected: "(string | undefined)",
+                            value: input.pattern
+                        }), undefined === input.contentMediaType || "string" === typeof input.contentMediaType || _report(_exceptionable, {
+                            path: _path + ".contentMediaType",
+                            expected: "(string | undefined)",
+                            value: input.contentMediaType
+                        }), undefined === input.minLength || "number" === typeof input.minLength && (Math.floor(input.minLength) === input.minLength && 0 <= input.minLength && input.minLength <= 18446744073709552000 || _report(_exceptionable, {
+                            path: _path + ".minLength",
+                            expected: "number & Type<\"uint64\">",
+                            value: input.minLength
+                        })) || _report(_exceptionable, {
+                            path: _path + ".minLength",
+                            expected: "((number & Type<\"uint64\">) | undefined)",
+                            value: input.minLength
+                        }), undefined === input.maxLength || "number" === typeof input.maxLength && (Math.floor(input.maxLength) === input.maxLength && 0 <= input.maxLength && input.maxLength <= 18446744073709552000 || _report(_exceptionable, {
+                            path: _path + ".maxLength",
+                            expected: "number & Type<\"uint64\">",
+                            value: input.maxLength
+                        })) || _report(_exceptionable, {
+                            path: _path + ".maxLength",
+                            expected: "((number & Type<\"uint64\">) | undefined)",
+                            value: input.maxLength
+                        }), "string" === input.type || _report(_exceptionable, {
+                            path: _path + ".type",
+                            expected: "\"string\"",
+                            value: input.type
+                        })].every(flag => flag); const _vo7 = (input, _path, _exceptionable = true) => ["string" === typeof input.description || _report(_exceptionable, {
+                            path: _path + ".description",
+                            expected: "string",
+                            value: input.description
+                        }), "string" === typeof input.typeName || _report(_exceptionable, {
+                            path: _path + ".typeName",
+                            expected: "string",
+                            value: input.typeName
+                        })].every(flag => flag); const _vo8 = (input, _path, _exceptionable = true) => ["string" === typeof input.description || _report(_exceptionable, {
+                            path: _path + ".description",
+                            expected: "string",
+                            value: input.description
+                        }), "string" === typeof input.typeName || _report(_exceptionable, {
+                            path: _path + ".typeName",
+                            expected: "string",
+                            value: input.typeName
+                        })].every(flag => flag); const _vo9 = (input, _path, _exceptionable = true) => [("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
+                            path: _path + ".endpoint",
+                            expected: "AutoBeOpenApi.IEndpoint",
+                            value: input.endpoint
+                        })) && _vo10(input.endpoint, _path + ".endpoint", true && _exceptionable) || _report(_exceptionable, {
+                            path: _path + ".endpoint",
+                            expected: "AutoBeOpenApi.IEndpoint",
+                            value: input.endpoint
+                        }), "string" === typeof input.description || _report(_exceptionable, {
+                            path: _path + ".description",
+                            expected: "string",
+                            value: input.description
+                        })].every(flag => flag); const _vo10 = (input, _path, _exceptionable = true) => ["string" === typeof input.path && (RegExp("^\\/[a-zA-Z0-9\\/_{}.-]*$").test(input.path) || _report(_exceptionable, {
+                            path: _path + ".path",
+                            expected: "string & Pattern<\"^\\\\/[a-zA-Z0-9\\\\/_{}.-]*$\">",
+                            value: input.path
+                        })) || _report(_exceptionable, {
+                            path: _path + ".path",
+                            expected: "(string & Pattern<\"^\\\\/[a-zA-Z0-9\\\\/_{}.-]*$\">)",
+                            value: input.path
+                        }), "get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method || _report(_exceptionable, {
+                            path: _path + ".method",
+                            expected: "(\"delete\" | \"get\" | \"patch\" | \"post\" | \"put\")",
+                            value: input.method
+                        })].every(flag => flag); const _vu0 = (input, _path, _exceptionable = true) => (() => {
+                        if ("number" === input.type)
+                            return _vo5(input, _path, true && _exceptionable);
+                        else if ("integer" === input.type)
+                            return _vo4(input, _path, true && _exceptionable);
+                        else if ("string" === input.type)
+                            return _vo6(input, _path, true && _exceptionable);
+                        else
+                            return _report(_exceptionable, {
+                                path: _path,
+                                expected: "(AutoBeOpenApi.IJsonSchema.INumber | AutoBeOpenApi.IJsonSchema.IInteger | AutoBeOpenApi.IJsonSchema.IString)",
+                                value: input
+                            });
+                    })(); const __is = input => "object" === typeof input && null !== input && _io0(input); let errors; let _report; return input => {
+                        if (false === __is(input)) {
+                            errors = [];
+                            _report = __typia_transform__validateReport._validateReport(errors);
+                            ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
+                                path: _path + "",
+                                expected: "IAutoBeInterfaceOperationsReviewApplication.IProps",
+                                value: input
+                            })) && _vo0(input, _path + "", true) || _report(true, {
+                                path: _path + "",
+                                expected: "IAutoBeInterfaceOperationsReviewApplication.IProps",
+                                value: input
+                            }))(input, "$input", true);
+                            const success = 0 === errors.length;
+                            return success ? {
+                                success,
+                                data: input
+                            } : {
+                                success,
+                                errors,
+                                data: input
+                            };
+                        }
+                        return {
+                            success: true,
+                            data: input
+                        };
+                    }; })()
+                }
+            ]
+        };
+        __typia_transform__llmApplicationFinalize._llmApplicationFinalize(application, Object.assign(Object.assign({}, {
+            validate: {
+                reviewOperations: validate,
+            },
+        }), { equals: false }));
+        return application;
+    })(),
 };
 //# sourceMappingURL=orchestrateInterfaceOperationsReview.js.map