@autobe/agent 0.28.0 → 0.28.1

package/lib/index.mjs

@@ -2201,8 +2201,9 @@ const collection$s = {
                         type: "string"
                     },
                     prefix: {
-                        description: "Prefix for file names and variable names. This will be used for\norganizing documentation files.\n\nDO: Use camelCase naming convention.\n\n\n@pattern ^[a-z][a-zA-Z0-9]*$",
-                        type: "string"
+                        description: "Prefix for file names and variable names. This will be used for\norganizing documentation files.\n\nDO: Use camelCase naming convention.",
+                        type: "string",
+                        pattern: "^[a-z][a-zA-Z0-9]*$"
                     },
                     actors: {
                         description: 'Actors to be assigned for the project.\n\nEach actor has:\n\n- `name`: Actor identifier (camelCase)\n- `kind`: "guest" | "member" | "admin"\n- `description`: Actor\'s permissions and capabilities',
@@ -2220,11 +2221,12 @@ const collection$s = {
                         type: "number"
                     },
                     files: {
-                        description: 'Array of document metadata objects defining files to be generated.\n\nEach array element is an AutoBeAnalyzeFile.Scenario object containing:\n- filename: The output file name (e.g., "01-service-overview.md")\n- reason: Why this document is being created\n- documentType, outline, constraints, etc.: Metadata guiding content generation\n\nThese documents represent business-focused planning documentation:\n- Business requirements and functional specifications in natural language\n- User journey mapping and use case scenarios\n- Business rules and workflow definitions\n- Service overview and business model description\n- User actors and permission requirements (described in natural language)\n- Business logic and validation rules\n- DO NOT: Include database schemas, ERD, or API specifications\n- DO: Write all requirements in natural language for clarity\n\nGenerate metadata objects based on actual requirements gathered from conversation.\nDo not create unnecessary documentation - only generate what is needed to\nproperly define the business requirements and system specifications.\n\n# Array Length Rules\n\nThe array length must match the user\'s requested page count plus one for ToC.\nFor example: user requests 3 pages → generate 4 objects (1 ToC + 3 content).\nIf user does not specify a number, generate sufficient objects to adequately\ndocument the service (typically 11+ objects including ToC).\n\n\n@minItems 1',
+                        description: 'Array of document metadata objects defining files to be generated.\n\nEach array element is an AutoBeAnalyzeFile.Scenario object containing:\n- filename: The output file name (e.g., "01-service-overview.md")\n- reason: Why this document is being created\n- documentType, outline, constraints, etc.: Metadata guiding content generation\n\nThese documents represent business-focused planning documentation:\n- Business requirements and functional specifications in natural language\n- User journey mapping and use case scenarios\n- Business rules and workflow definitions\n- Service overview and business model description\n- User actors and permission requirements (described in natural language)\n- Business logic and validation rules\n- DO NOT: Include database schemas, ERD, or API specifications\n- DO: Write all requirements in natural language for clarity\n\nGenerate metadata objects based on actual requirements gathered from conversation.\nDo not create unnecessary documentation - only generate what is needed to\nproperly define the business requirements and system specifications.\n\n# Array Length Rules\n\nThe array length must match the user\'s requested page count plus one for ToC.\nFor example: user requests 3 pages → generate 4 objects (1 ToC + 3 content).\nIf user does not specify a number, generate sufficient objects to adequately\ndocument the service (typically 11+ objects including ToC).',
                         type: "array",
                         items: {
                             $ref: "#/$defs/AutoBeAnalyzeFile.Scenario"
-                        }
+                        },
+                        minItems: 1
                     }
                 },
                 required: [ "reason", "prefix", "actors", "page", "files" ],
@@ -2235,8 +2237,10 @@ const collection$s = {
                         type: "object",
                         properties: {
                             name: {
-                                description: "Unique identifier for the user actor.\n\nThis name will be used as a reference throughout the generated codebase,\nincluding Prisma schema model names, authorization decorator parameters,\nand API documentation.\n\nMUST use camelCase naming convention.\n\n\n@minLength 1\n@pattern ^[a-z][a-zA-Z0-9]*$",
-                                type: "string"
+                                description: "Unique identifier for the user actor.\n\nThis name will be used as a reference throughout the generated codebase,\nincluding Prisma schema model names, authorization decorator parameters,\nand API documentation.\n\nMUST use camelCase naming convention.",
+                                type: "string",
+                                pattern: "^[a-z][a-zA-Z0-9]*$",
+                                minLength: 1
                             },
                             kind: {
                                 description: 'Actor category classification for system-wide permission hierarchy.\n\nThis property categorizes actors into three fundamental permission levels,\nestablishing a clear hierarchy for authorization decisions throughout the\napplication. The kind determines baseline access patterns and security\nboundaries:\n\n- "guest": Unauthenticated users or those with minimal permissions. Typically\n  limited to public resources and registration/login endpoints.\n- "member": Authenticated users with standard access permissions. Can access\n  personal resources and participate in core application features.\n- "admin": System administrators with elevated permissions. Can manage other\n  users, access administrative functions, and modify system-wide settings.',
@@ -2258,8 +2262,9 @@ const collection$s = {
                                 type: "string"
                             },
                             filename: {
-                                description: 'Filename to generate or overwrite. Should be descriptive and follow a\nconsistent naming convention. Examples: "01-service-overview.md",\n"02-user-requirements.md", "03-business-model.md"\n\n\n@pattern ((.*)\\.md)$',
-                                type: "string"
+                                description: 'Filename to generate or overwrite. Should be descriptive and follow a\nconsistent naming convention. Examples: "01-service-overview.md",\n"02-user-requirements.md", "03-business-model.md"',
+                                type: "string",
+                                pattern: "((.*)\\.md)$"
                             },
                             documentType: {
                                 description: 'Document type that determines the structure and content guidelines. This\nhelps the AI understand what kind of document to create and what sections\nor information should be included. Examples:\n\n- "requirement": Functional/non-functional requirements, acceptance\n  criteria\n- "user-story": User personas, scenarios, and journey descriptions\n- "user-flow": Step-by-step user interactions and decision points\n- "business-model": Revenue streams, cost structure, value propositions\n- "service-overview": High-level service description, goals, and scope',
@@ -4859,11 +4864,12 @@ const collection$q = {
                     type: "object",
                     properties: {
                         operations: {
-                            description: 'Array of API operations to generate authorization operation for.\n\nEach operation in this array must include:\n\n- Specification: Detailed API specification with clear purpose and\n  functionality\n- Path: Resource-centric URL path (e.g., "/resources/{resourceId}")\n- Method: HTTP method (get, post, put, delete, patch)\n- Description: Extremely detailed multi-paragraph description referencing\n  Prisma schema comments\n- Summary: Concise one-sentence summary of the endpoint\n- Parameters: Array of all necessary parameters with descriptions and\n  schema definitions\n- RequestBody: For POST/PUT/PATCH methods, with typeName referencing\n  components.schemas\n- ResponseBody: With typeName referencing appropriate response type\n\nAll operations must follow strict quality standards:\n\n1. Detailed descriptions referencing Prisma schema comments\n2. Accurate parameter definitions matching path parameters\n3. Appropriate request/response body type references\n4. Consistent patterns for CRUD operations\n\nFor list retrievals (typically PATCH), include pagination, search, and\nsorting. For detail retrieval (GET), return a single resource. For\ncreation (POST), use .ICreate request body. For modification (PUT), use\n.IUpdate request body.\n\n\n@minItems 1',
+                            description: 'Array of API operations to generate authorization operation for.\n\nEach operation in this array must include:\n\n- Specification: Detailed API specification with clear purpose and\n  functionality\n- Path: Resource-centric URL path (e.g., "/resources/{resourceId}")\n- Method: HTTP method (get, post, put, delete, patch)\n- Description: Extremely detailed multi-paragraph description referencing\n  Prisma schema comments\n- Summary: Concise one-sentence summary of the endpoint\n- Parameters: Array of all necessary parameters with descriptions and\n  schema definitions\n- RequestBody: For POST/PUT/PATCH methods, with typeName referencing\n  components.schemas\n- ResponseBody: With typeName referencing appropriate response type\n\nAll operations must follow strict quality standards:\n\n1. Detailed descriptions referencing Prisma schema comments\n2. Accurate parameter definitions matching path parameters\n3. Appropriate request/response body type references\n4. Consistent patterns for CRUD operations\n\nFor list retrievals (typically PATCH), include pagination, search, and\nsorting. For detail retrieval (GET), return a single resource. For\ncreation (POST), use .ICreate request body. For modification (PUT), use\n.IUpdate request body.',
                             type: "array",
                             items: {
                                 $ref: "#/$defs/AutoBeOpenApi.IOperation"
-                            }
+                            },
+                            minItems: 1
                         }
                     },
                     required: [ "operations" ],
@@ -4923,12 +4929,14 @@ const collection$q = {
                                         type: "null"
                                     }, {
                                         type: "string",
-                                        description: "@minLength 1\n@pattern ^[a-z][a-zA-Z0-9]*$"
+                                        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` → `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}` → `name: "at"`\n- **`create`**: Create a new entity\n\n  - Typically used with POST method\n  - Example: `POST /users` → `name: "create"`\n- **`update`**: Update an existing entity\n\n  - Typically used with PUT method\n  - Example: `PUT /users/{userId}` → `name: "update"`\n- **`erase`**: Delete/remove an entity (NOT `delete` - reserved word!)\n\n  - Typically used with DELETE method\n  - Example: `DELETE /users/{userId}` → `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` → `name: "index"` (lists items)\n- `POST /shopping/orders/{orderId}/cancel` → `name: "cancel"`\n- `PUT /users/{userId}/password` → `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` → Accessor:\n  `shopping.sale.review.at`\n- Path: `/users/{userId}/posts`, Name: `index` → Accessor:\n  `users.posts.index`\n- Path: `/auth/login`, Name: `signIn` → 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.\n\n\n@pattern ^[a-z][a-zA-Z0-9]*$',
-                                    type: "string"
+                                    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` → `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}` → `name: "at"`\n- **`create`**: Create a new entity\n\n  - Typically used with POST method\n  - Example: `POST /users` → `name: "create"`\n- **`update`**: Update an existing entity\n\n  - Typically used with PUT method\n  - Example: `PUT /users/{userId}` → `name: "update"`\n- **`erase`**: Delete/remove an entity (NOT `delete` - reserved word!)\n\n  - Typically used with DELETE method\n  - Example: `DELETE /users/{userId}` → `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` → `name: "index"` (lists items)\n- `POST /shopping/orders/{orderId}/cancel` → `name: "cancel"`\n- `PUT /users/{userId}/password` → `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` → Accessor:\n  `shopping.sale.review.at`\n- Path: `/users/{userId}/posts`, Name: `index` → Accessor:\n  `users.posts.index`\n- Path: `/auth/login`, Name: `signIn` → 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',
@@ -4938,8 +4946,9 @@ const collection$q = {
                                     }
                                 },
                                 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)\n\n\n@pattern ^\\/[a-zA-Z0-9\\/_{}.-]*$',
-                                    type: "string"
+                                    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',
@@ -4954,8 +4963,9 @@ const collection$q = {
                             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.\n\n\n@pattern ^[a-z][a-zA-Z0-9]*$",
-                                    type: "string"
+                                    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.",
@@ -5003,8 +5013,9 @@ const collection$q = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "number"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -5035,8 +5046,9 @@ const collection$q = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -5064,12 +5076,14 @@ const collection$q = {
                                     type: "string"
                                 },
                                 minLength: {
-                                    description: "Minimum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Minimum length restriction.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 maxLength: {
-                                    description: "Maximum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -5129,8 +5143,9 @@ const collection$q = {
                             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)\n\n\n@pattern ^\\/[a-zA-Z0-9\\/_{}.-]*$',
-                                    type: "string"
+                                    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',
@@ -10726,8 +10741,9 @@ const collection$p = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -10762,8 +10778,9 @@ const collection$p = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "number"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -10795,12 +10812,14 @@ const collection$p = {
                                     type: "string"
                                 },
                                 minLength: {
-                                    description: "Minimum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Minimum length restriction.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 maxLength: {
-                                    description: "Maximum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -10827,12 +10846,14 @@ const collection$p = {
                                     type: "boolean"
                                 },
                                 minItems: {
-                                    description: "Minimum items restriction.\n\nRestriction of minimum number of items in the array.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Minimum items restriction.\n\nRestriction of minimum number of items in the array.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 maxItems: {
-                                    description: "Maximum items restriction.\n\nRestriction of maximum number of items in the array.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Maximum items restriction.\n\nRestriction of maximum number of items in the array.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 type: {
                                     description: 'Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n"boolean", "integer", "number", "string", "array", "object", or\n"null".\n\n❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -10891,8 +10912,9 @@ const collection$p = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -10923,8 +10945,9 @@ const collection$p = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "number"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -10952,12 +10975,14 @@ const collection$p = {
                                     type: "string"
                                 },
                                 minLength: {
-                                    description: "Minimum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Minimum length restriction.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 maxLength: {
-                                    description: "Maximum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -11009,12 +11034,14 @@ const collection$p = {
                                     type: "boolean"
                                 },
                                 minItems: {
-                                    description: "Minimum items restriction.\n\nRestriction of minimum number of items in the array.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Minimum items restriction.\n\nRestriction of minimum number of items in the array.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 maxItems: {
-                                    description: "Maximum items restriction.\n\nRestriction of maximum number of items in the array.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Maximum items restriction.\n\nRestriction of maximum number of items in the array.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 type: {
                                     description: 'Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n"boolean", "integer", "number", "string", "array", "object", or\n"null".\n\n❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -12336,8 +12363,9 @@ const collection$o = {
                         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)\n\n\n@pattern ^\\/[a-zA-Z0-9\\/_{}.-]*$',
-                                type: "string"
+                                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',
@@ -12747,11 +12775,12 @@ const collection$n = {
                 type: "object",
                 properties: {
                     endpoints: {
-                        description: "The endpoints to generate.\n\n\n@minItems 1",
+                        description: "The endpoints to generate.",
                         type: "array",
                         items: {
                             $ref: "#/$defs/AutoBeOpenApi.IEndpoint"
-                        }
+                        },
+                        minItems: 1
                     }
                 },
                 required: [ "endpoints" ],
@@ -12762,8 +12791,9 @@ const collection$n = {
                         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)\n\n\n@pattern ^\\/[a-zA-Z0-9\\/_{}.-]*$',
-                                type: "string"
+                                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',
@@ -13209,11 +13239,12 @@ const collection$m = {
                 type: "object",
                 properties: {
                     groups: {
-                        description: "Array of API endpoint groups for organizing development.\n\nDO: Organize groups around existing Prisma schema structure.\nDO: Provide complete coverage of all entities and requirements without\noverlap.\n\n\n@minItems 1",
+                        description: "Array of API endpoint groups for organizing development.\n\nDO: Organize groups around existing Prisma schema structure.\nDO: Provide complete coverage of all entities and requirements without\noverlap.",
                         type: "array",
                         items: {
                             $ref: "#/$defs/IAutoBeInterfaceGroupApplication.IGroup"
-                        }
+                        },
+                        minItems: 1
                     }
                 },
                 required: [ "groups" ],
@@ -13224,12 +13255,14 @@ const collection$m = {
                         type: "object",
                         properties: {
                             name: {
-                                description: "Unique identifier name derived from Prisma schema structure.\n\nDO: Correspond to schema namespaces, file names, table prefixes, or\norganizational annotations rather than arbitrary business domain names.\n\n\n@minLength 1",
-                                type: "string"
+                                description: "Unique identifier name derived from Prisma schema structure.\n\nDO: Correspond to schema namespaces, file names, table prefixes, or\norganizational annotations rather than arbitrary business domain names.",
+                                type: "string",
+                                minLength: 1
                             },
                             description: {
-                                description: 'Concise description of the group\'s core purpose.\n\n**Requirements:**\n- Keep it brief and focused (50-200 characters)\n- State the main purpose and key entities\n- Avoid detailed explanations or mappings\n\nExample: "Handles shopping-related entities and operations"\n\n\n@minLength 1',
-                                type: "string"
+                                description: 'Concise description of the group\'s core purpose.\n\n**Requirements:**\n- Keep it brief and focused (50-200 characters)\n- State the main purpose and key entities\n- Avoid detailed explanations or mappings\n\nExample: "Handles shopping-related entities and operations"',
+                                type: "string",
+                                minLength: 1
                             }
                         },
                         required: [ "name", "description" ]
@@ -15467,12 +15500,14 @@ const collection$l = {
                                         type: "null"
                                     }, {
                                         type: "string",
-                                        description: "@minLength 1\n@pattern ^[a-z][a-zA-Z0-9]*$"
+                                        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` → `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}` → `name: "at"`\n- **`create`**: Create a new entity\n\n  - Typically used with POST method\n  - Example: `POST /users` → `name: "create"`\n- **`update`**: Update an existing entity\n\n  - Typically used with PUT method\n  - Example: `PUT /users/{userId}` → `name: "update"`\n- **`erase`**: Delete/remove an entity (NOT `delete` - reserved word!)\n\n  - Typically used with DELETE method\n  - Example: `DELETE /users/{userId}` → `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` → `name: "index"` (lists items)\n- `POST /shopping/orders/{orderId}/cancel` → `name: "cancel"`\n- `PUT /users/{userId}/password` → `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` → Accessor:\n  `shopping.sale.review.at`\n- Path: `/users/{userId}/posts`, Name: `index` → Accessor:\n  `users.posts.index`\n- Path: `/auth/login`, Name: `signIn` → 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.\n\n\n@pattern ^[a-z][a-zA-Z0-9]*$',
-                                    type: "string"
+                                    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` → `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}` → `name: "at"`\n- **`create`**: Create a new entity\n\n  - Typically used with POST method\n  - Example: `POST /users` → `name: "create"`\n- **`update`**: Update an existing entity\n\n  - Typically used with PUT method\n  - Example: `PUT /users/{userId}` → `name: "update"`\n- **`erase`**: Delete/remove an entity (NOT `delete` - reserved word!)\n\n  - Typically used with DELETE method\n  - Example: `DELETE /users/{userId}` → `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` → `name: "index"` (lists items)\n- `POST /shopping/orders/{orderId}/cancel` → `name: "cancel"`\n- `PUT /users/{userId}/password` → `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` → Accessor:\n  `shopping.sale.review.at`\n- Path: `/users/{userId}/posts`, Name: `index` → Accessor:\n  `users.posts.index`\n- Path: `/auth/login`, Name: `signIn` → 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',
@@ -15482,8 +15517,9 @@ const collection$l = {
                                     }
                                 },
                                 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)\n\n\n@pattern ^\\/[a-zA-Z0-9\\/_{}.-]*$',
-                                    type: "string"
+                                    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',
@@ -15498,8 +15534,9 @@ const collection$l = {
                             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.\n\n\n@pattern ^[a-z][a-zA-Z0-9]*$",
-                                    type: "string"
+                                    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.",
@@ -15547,8 +15584,9 @@ const collection$l = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "number"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -15579,8 +15617,9 @@ const collection$l = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -15608,12 +15647,14 @@ const collection$l = {
                                     type: "string"
                                 },
                                 minLength: {
-                                    description: "Minimum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Minimum length restriction.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 maxLength: {
-                                    description: "Maximum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -15673,8 +15714,9 @@ const collection$l = {
                             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)\n\n\n@pattern ^\\/[a-zA-Z0-9\\/_{}.-]*$',
-                                    type: "string"
+                                    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',
@@ -17745,20 +17787,23 @@ const collection$k = {
                                     } ]
                                 },
                                 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` → `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}` → `name: "at"`\n- **`create`**: Create a new entity\n\n  - Typically used with POST method\n  - Example: `POST /users` → `name: "create"`\n- **`update`**: Update an existing entity\n\n  - Typically used with PUT method\n  - Example: `PUT /users/{userId}` → `name: "update"`\n- **`erase`**: Delete/remove an entity (NOT `delete` - reserved word!)\n\n  - Typically used with DELETE method\n  - Example: `DELETE /users/{userId}` → `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` → `name: "index"` (lists items)\n- `POST /shopping/orders/{orderId}/cancel` → `name: "cancel"`\n- `PUT /users/{userId}/password` → `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` → Accessor:\n  `shopping.sale.review.at`\n- Path: `/users/{userId}/posts`, Name: `index` → Accessor:\n  `users.posts.index`\n- Path: `/auth/login`, Name: `signIn` → 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.\n\n\n@pattern ^[a-z][a-zA-Z0-9]*$',
-                                    type: "string"
+                                    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` → `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}` → `name: "at"`\n- **`create`**: Create a new entity\n\n  - Typically used with POST method\n  - Example: `POST /users` → `name: "create"`\n- **`update`**: Update an existing entity\n\n  - Typically used with PUT method\n  - Example: `PUT /users/{userId}` → `name: "update"`\n- **`erase`**: Delete/remove an entity (NOT `delete` - reserved word!)\n\n  - Typically used with DELETE method\n  - Example: `DELETE /users/{userId}` → `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` → `name: "index"` (lists items)\n- `POST /shopping/orders/{orderId}/cancel` → `name: "cancel"`\n- `PUT /users/{userId}/password` → `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` → Accessor:\n  `shopping.sale.review.at`\n- Path: `/users/{userId}/posts`, Name: `index` → Accessor:\n  `users.posts.index`\n- Path: `/auth/login`, Name: `signIn` → 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]*$"
                                 },
                                 authorizationActors: {
                                     description: 'Authorization actors required to access this API operation.\n\nThis field specifies which user actors are allowed to access this\nendpoint. Multiple actors can be specified to allow different types of\nusers to access the same endpoint.\n\n## ⚠️ CRITICAL: Actor Multiplication Effect\n\n**EACH ACTOR IN THIS ARRAY GENERATES A SEPARATE ENDPOINT**\n\n- If you specify `["admin", "moderator", "member"]`, this creates 3\n  separate endpoints\n- Total generated endpoints = operations × average actors.length\n- Example: 100 operations with 3 actors each = 300 actual endpoints\n\n## 🔴 AVOID OVER-GENERATION\n\n**DO NOT create actor-specific endpoints when a public endpoint would\nsuffice:**\n\n- ❌ BAD: Separate GET endpoints for admin, member, moderator to view the\n  same public data\n- ✅ GOOD: Single public endpoint `[]` with actor-based filtering in business\n  logic\n\n**DO NOT enumerate all possible actors when the Prisma schema uses a\nsingle User table:**\n\n- If Prisma has a User table with role/permission fields, you likely only\n  need `["user"]`\n- Avoid listing `["admin", "seller", "buyer", "moderator", ...]`\n  unnecessarily\n- The actual actor checking happens in business logic, not at the endpoint\n  level\n\n## Naming Convention\n\nDO: Use camelCase for all actor names.\n\n## Important Guidelines\n\n- Set to empty array `[]` for public endpoints that require no\n  authentication\n- Set to array with actor strings for actor-restricted endpoints\n- **MINIMIZE the number of actors per endpoint to prevent explosion**\n- Consider if the endpoint can be public with actor-based filtering instead\n- The actor names match exactly with the user type/actor defined in the\n  database\n- This will be used by the Realize Agent to generate appropriate decorator\n  and authorization logic in the provider functions\n- The controller will apply the corresponding authentication decorator\n  based on these actors\n\n## Examples\n\n- `[]` - Public endpoint, no authentication required (PREFERRED for read\n  operations)\n- `["user"]` - Any authenticated user can access (PREFERRED for\n  user-specific operations)\n- `["admin"]` - Only admin users can access (USE SPARINGLY)\n- `["admin", "moderator"]` - Both admin and moderator users can access\n  (AVOID if possible)\n- `["seller"]` - Only seller users can access (ONLY if Seller is a separate\n  table)\n\n## Best Practices\n\n1. **Start with public `[]` for all read operations** unless sensitive data\n   is involved\n2. **Use single actor `["user"]` for authenticated operations** and handle\n   permissions in business logic\n3. **Only use multiple actors when absolutely necessary** for different\n   business logic paths\n4. **Remember: Fewer actors = Fewer endpoints = Better performance and\n   maintainability**\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.',
                                     type: "array",
                                     items: {
-                                        description: "@minLength 1\n@pattern ^[a-z][a-zA-Z0-9]*$",
-                                        type: "string"
+                                        type: "string",
+                                        pattern: "^[a-z][a-zA-Z0-9]*$",
+                                        minLength: 1
                                     }
                                 },
                                 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)\n\n\n@pattern ^\\/[a-zA-Z0-9\\/_{}.-]*$',
-                                    type: "string"
+                                    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',
@@ -17773,8 +17818,9 @@ const collection$k = {
                             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.\n\n\n@pattern ^[a-z][a-zA-Z0-9]*$",
-                                    type: "string"
+                                    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.",
@@ -17822,8 +17868,9 @@ const collection$k = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "number"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -17854,8 +17901,9 @@ const collection$k = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -17883,12 +17931,14 @@ const collection$k = {
                                     type: "string"
                                 },
                                 minLength: {
-                                    description: "Minimum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Minimum length restriction.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 maxLength: {
-                                    description: "Maximum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -19056,8 +19106,9 @@ const collection$j = {
                             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)\n\n\n@pattern ^\\/[a-zA-Z0-9\\/_{}.-]*$',
-                                    type: "string"
+                                    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',
@@ -23468,8 +23519,9 @@ const collection$h = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -23504,8 +23556,9 @@ const collection$h = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "number"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -23537,12 +23590,14 @@ const collection$h = {
                                     type: "string"
                                 },
                                 minLength: {
-                                    description: "Minimum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Minimum length restriction.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 maxLength: {
-                                    description: "Maximum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -23569,12 +23624,14 @@ const collection$h = {
                                     type: "boolean"
                                 },
                                 minItems: {
-                                    description: "Minimum items restriction.\n\nRestriction of minimum number of items in the array.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Minimum items restriction.\n\nRestriction of minimum number of items in the array.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 maxItems: {
-                                    description: "Maximum items restriction.\n\nRestriction of maximum number of items in the array.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Maximum items restriction.\n\nRestriction of maximum number of items in the array.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 type: {
                                     description: 'Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n"boolean", "integer", "number", "string", "array", "object", or\n"null".\n\n❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -23633,8 +23690,9 @@ const collection$h = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -23665,8 +23723,9 @@ const collection$h = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "number"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -23694,12 +23753,14 @@ const collection$h = {
                                     type: "string"
                                 },
                                 minLength: {
-                                    description: "Minimum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Minimum length restriction.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 maxLength: {
-                                    description: "Maximum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -23751,12 +23812,14 @@ const collection$h = {
                                     type: "boolean"
                                 },
                                 minItems: {
-                                    description: "Minimum items restriction.\n\nRestriction of minimum number of items in the array.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Minimum items restriction.\n\nRestriction of minimum number of items in the array.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 maxItems: {
-                                    description: "Maximum items restriction.\n\nRestriction of maximum number of items in the array.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Maximum items restriction.\n\nRestriction of maximum number of items in the array.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 type: {
                                     description: 'Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n"boolean", "integer", "number", "string", "array", "object", or\n"null".\n\n❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -28384,8 +28447,9 @@ const collection$g = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -28420,8 +28484,9 @@ const collection$g = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "number"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -28453,12 +28518,14 @@ const collection$g = {
                                     type: "string"
                                 },
                                 minLength: {
-                                    description: "Minimum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Minimum length restriction.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 maxLength: {
-                                    description: "Maximum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -28485,12 +28552,14 @@ const collection$g = {
                                     type: "boolean"
                                 },
                                 minItems: {
-                                    description: "Minimum items restriction.\n\nRestriction of minimum number of items in the array.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Minimum items restriction.\n\nRestriction of minimum number of items in the array.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 maxItems: {
-                                    description: "Maximum items restriction.\n\nRestriction of maximum number of items in the array.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Maximum items restriction.\n\nRestriction of maximum number of items in the array.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 type: {
                                     description: 'Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n"boolean", "integer", "number", "string", "array", "object", or\n"null".\n\n❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -28549,8 +28618,9 @@ const collection$g = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -28581,8 +28651,9 @@ const collection$g = {
                                     type: "number"
                                 },
                                 multipleOf: {
-                                    description: "Multiple of value restriction.\n\n\n@exclusiveMinimum 0",
-                                    type: "number"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -28610,12 +28681,14 @@ const collection$g = {
                                     type: "string"
                                 },
                                 minLength: {
-                                    description: "Minimum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Minimum length restriction.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 maxLength: {
-                                    description: "Maximum length restriction.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    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❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -28667,12 +28740,14 @@ const collection$g = {
                                     type: "boolean"
                                 },
                                 minItems: {
-                                    description: "Minimum items restriction.\n\nRestriction of minimum number of items in the array.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Minimum items restriction.\n\nRestriction of minimum number of items in the array.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 maxItems: {
-                                    description: "Maximum items restriction.\n\nRestriction of maximum number of items in the array.\n\n\n@minimum 0",
-                                    type: "integer"
+                                    description: "Maximum items restriction.\n\nRestriction of maximum number of items in the array.",
+                                    type: "integer",
+                                    minimum: 0
                                 },
                                 type: {
                                     description: 'Discriminator value of the type.\n\nCRITICAL: This MUST be a SINGLE string value, NOT an array. The type\nfield identifies the JSON Schema type and must be exactly one of:\n"boolean", "integer", "number", "string", "array", "object", or\n"null".\n\n❌ INCORRECT: type: ["string", "null"] // This is WRONG! ✅ 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.',
@@ -30229,11 +30304,12 @@ const collection$f = {
                         type: "string"
                     },
                     components: {
-                        description: 'Array of domain components that group related database tables.\n\nEach component represents a business domain and becomes one Prisma schema\nfile. Common domains include: Actors (users), Sales (products), Orders,\nCarts, etc.\n\n**Example:**\n\n```typescript\n{\n  "components": [\n    {\n      "filename": "schema-02-systematic.prisma",\n      "namespace": "Systematic",\n      "thinking": "These tables all relate to system configuration and channel management. They form the foundation of the platform.",\n      "review": "Considering the relationships, shopping_channel_categories connects channels and sales, but it fundamentally defines channel structure.",\n      "rationale": "Grouping all system configuration tables together provides a clear foundation layer that other domains can reference.",\n      "tables": [\n        "shopping_channels",\n        "shopping_sections",\n        "shopping_channel_categories"\n      ]\n    },\n    {\n      "filename": "schema-03-actors.prisma",\n      "namespace": "Actors",\n      "thinking": "All user-related entities should be grouped together as they share authentication and identity patterns.",\n      "review": "While customers interact with sales, the customer entity itself is about identity, not transactions.",\n      "rationale": "This component groups all actor-related tables to maintain separation between identity management and business transactions.",\n      "tables": [\n        "shopping_customers",\n        "shopping_citizens",\n        "shopping_administrators"\n      ]\n    },\n    {\n      "filename": "schema-04-sales.prisma",\n      "namespace": "Sales",\n      "thinking": "Product catalog and sales-related tables belong together as they form the core commerce functionality.",\n      "review": "Sales snapshots are integral to the sales domain for tracking product history and price changes.",\n      "rationale": "Consolidating all sales-related tables enables coherent management of the entire product lifecycle.",\n      "tables": [\n        "shopping_sales",\n        "shopping_sale_snapshots",\n        "shopping_sale_units",\n        "shopping_sale_unit_options"\n      ]\n    }\n  ]\n}\n```\n\n**Notes:**\n\n- Table names must follow snake_case convention with domain prefix (e.g.,\n  `shopping_customers`)\n- Each component becomes one `.prisma` file containing related models\n- Filename numbering indicates dependency order for schema generation\n- Namespace is used for documentation organization and domain grouping\n\n\n@minItems 1',
+                        description: 'Array of domain components that group related database tables.\n\nEach component represents a business domain and becomes one Prisma schema\nfile. Common domains include: Actors (users), Sales (products), Orders,\nCarts, etc.\n\n**Example:**\n\n```typescript\n{\n  "components": [\n    {\n      "filename": "schema-02-systematic.prisma",\n      "namespace": "Systematic",\n      "thinking": "These tables all relate to system configuration and channel management. They form the foundation of the platform.",\n      "review": "Considering the relationships, shopping_channel_categories connects channels and sales, but it fundamentally defines channel structure.",\n      "rationale": "Grouping all system configuration tables together provides a clear foundation layer that other domains can reference.",\n      "tables": [\n        "shopping_channels",\n        "shopping_sections",\n        "shopping_channel_categories"\n      ]\n    },\n    {\n      "filename": "schema-03-actors.prisma",\n      "namespace": "Actors",\n      "thinking": "All user-related entities should be grouped together as they share authentication and identity patterns.",\n      "review": "While customers interact with sales, the customer entity itself is about identity, not transactions.",\n      "rationale": "This component groups all actor-related tables to maintain separation between identity management and business transactions.",\n      "tables": [\n        "shopping_customers",\n        "shopping_citizens",\n        "shopping_administrators"\n      ]\n    },\n    {\n      "filename": "schema-04-sales.prisma",\n      "namespace": "Sales",\n      "thinking": "Product catalog and sales-related tables belong together as they form the core commerce functionality.",\n      "review": "Sales snapshots are integral to the sales domain for tracking product history and price changes.",\n      "rationale": "Consolidating all sales-related tables enables coherent management of the entire product lifecycle.",\n      "tables": [\n        "shopping_sales",\n        "shopping_sale_snapshots",\n        "shopping_sale_units",\n        "shopping_sale_unit_options"\n      ]\n    }\n  ]\n}\n```\n\n**Notes:**\n\n- Table names must follow snake_case convention with domain prefix (e.g.,\n  `shopping_customers`)\n- Each component becomes one `.prisma` file containing related models\n- Filename numbering indicates dependency order for schema generation\n- Namespace is used for documentation organization and domain grouping',
                         type: "array",
                         items: {
                             $ref: "#/$defs/AutoBePrisma.IComponent"
-                        }
+                        },
+                        minItems: 1
                     }
                 },
                 required: [ "thinking", "review", "decision", "components" ],
@@ -30244,8 +30320,9 @@ const collection$f = {
                         type: "object",
                         properties: {
                             filename: {
-                                description: "Target filename for the Prisma schema file containing this component's\ntables.\n\nFollows the naming convention `schema-{number}-{domain}.prisma` where the\nnumber indicates dependency order and domain represents the business\narea.\n\n\n@pattern ^[a-zA-Z0-9._-]+\\.prisma$",
-                                type: "string"
+                                description: "Target filename for the Prisma schema file containing this component's\ntables.\n\nFollows the naming convention `schema-{number}-{domain}.prisma` where the\nnumber indicates dependency order and domain represents the business\narea.",
+                                type: "string",
+                                pattern: "^[a-zA-Z0-9._-]+\\.prisma$"
                             },
                             namespace: {
                                 description: 'Business domain namespace that groups related models.\n\nUsed in Prisma documentation comments as "@\\namespace directive".\nExamples from uploaded schemas: "Systematic", "Actors", "Sales", "Carts",\n"Orders", "Coupons", "Coins", "Inquiries", "Favorites", "Articles"',
@@ -30264,12 +30341,13 @@ const collection$f = {
                                 type: "string"
                             },
                             tables: {
-                                description: "Array of table names that will be included in this component's schema\nfile.\n\nContains all database table names that belong to this business domain,\nensuring logical grouping and proper organization of related data\nstructures.\n\n\n@minItems 1",
+                                description: "Array of table names that will be included in this component's schema\nfile.\n\nContains all database table names that belong to this business domain,\nensuring logical grouping and proper organization of related data\nstructures.",
                                 type: "array",
                                 items: {
-                                    description: "@pattern ^[a-z][a-z0-9_]*$",
-                                    type: "string"
-                                }
+                                    type: "string",
+                                    pattern: "^[a-z][a-z0-9_]*$"
+                                },
+                                minItems: 1
                             }
                         },
                         required: [ "filename", "namespace", "thinking", "review", "rationale", "tables" ]
@@ -31685,8 +31763,9 @@ const collection$e = {
                         type: "object",
                         properties: {
                             name: {
-                                description: 'Name of the Prisma model (database table name).\n\nMUST use snake_case naming convention. Examples: "shopping_customers",\n"shopping_sale_snapshots", "bbs_articles" Materialized views use "mv_"\nprefix: "mv_shopping_sale_last_snapshots"\n\n\n@pattern ^[a-z][a-z0-9_]*$',
-                                type: "string"
+                                description: 'Name of the Prisma model (database table name).\n\nMUST use snake_case naming convention. Examples: "shopping_customers",\n"shopping_sale_snapshots", "bbs_articles" Materialized views use "mv_"\nprefix: "mv_shopping_sale_last_snapshots"',
+                                type: "string",
+                                pattern: "^[a-z][a-z0-9_]*$"
                             },
                             description: {
                                 description: 'Detailed description explaining the business purpose and usage of the\nmodel.\n\nShould include:\n\n- Business context and purpose\n- Key relationships with other models\n- Important behavioral notes or constraints\n- References to related entities using "{@\\link ModelName}" syntax\n\n**IMPORTANT**: Description must be written in English. Example: "Customer\ninformation, but not a person but a **connection** basis..."',
@@ -31748,8 +31827,9 @@ const collection$e = {
                         type: "object",
                         properties: {
                             name: {
-                                description: 'Name of the primary key field.\n\nMUST use snake_case naming convention. Consistently named "id" across all\nmodels in the uploaded schemas. Represents the unique identifier for each\nrecord in the table.\n\n\n@pattern ^[a-z][a-z0-9_]*$',
-                                type: "string"
+                                description: 'Name of the primary key field.\n\nMUST use snake_case naming convention. Consistently named "id" across all\nmodels in the uploaded schemas. Represents the unique identifier for each\nrecord in the table.',
+                                type: "string",
+                                pattern: "^[a-z][a-z0-9_]*$"
                             },
                             type: {
                                 description: 'Data type of the primary key field.\n\nAlways "uuid" in the uploaded schemas for better distributed system\nsupport and to avoid exposing sequential IDs that could reveal business\ninformation.',
@@ -31768,8 +31848,9 @@ const collection$e = {
                         type: "object",
                         properties: {
                             name: {
-                                description: 'Name of the foreign key field.\n\nMUST use snake_case naming convention. Follows convention:\n"{target_model_name_without_prefix}_id" Examples: "shopping_customer_id",\n"bbs_article_id", "attachment_file_id" For self-references: "parent_id"\n(e.g., in hierarchical structures)\n\n\n@pattern ^[a-z][a-z0-9_]*$',
-                                type: "string"
+                                description: 'Name of the foreign key field.\n\nMUST use snake_case naming convention. Follows convention:\n"{target_model_name_without_prefix}_id" Examples: "shopping_customer_id",\n"bbs_article_id", "attachment_file_id" For self-references: "parent_id"\n(e.g., in hierarchical structures)',
+                                type: "string",
+                                pattern: "^[a-z][a-z0-9_]*$"
                             },
                             type: {
                                 description: 'Data type of the foreign key field.\n\nAlways "uuid" to match the primary key type of referenced models. Ensures\nreferential integrity and consistency across the schema.',
@@ -31800,8 +31881,9 @@ const collection$e = {
                         type: "object",
                         properties: {
                             name: {
-                                description: 'Name of the relation property in the Prisma model.\n\nThis becomes the property name used to access the related model instance\nthrough the Prisma client. Should be descriptive and reflect the business\nrelationship being modeled.\n\nExamples:\n\n- "customer" for shopping_customer_id field\n- "channel" for shopping_channel_id field\n- "parent" for parent_id field in hierarchical structures\n- "snapshot" for versioning relationships\n- "article" for bbs_article_id field\n\nNaming convention: camelCase, descriptive of the relationship\'s business\nmeaning\n\n\n@pattern ^[a-z][a-zA-Z0-9]*$',
-                                type: "string"
+                                description: 'Name of the relation property in the Prisma model.\n\nThis becomes the property name used to access the related model instance\nthrough the Prisma client. Should be descriptive and reflect the business\nrelationship being modeled.\n\nExamples:\n\n- "customer" for shopping_customer_id field\n- "channel" for shopping_channel_id field\n- "parent" for parent_id field in hierarchical structures\n- "snapshot" for versioning relationships\n- "article" for bbs_article_id field\n\nNaming convention: camelCase, descriptive of the relationship\'s business\nmeaning',
+                                type: "string",
+                                pattern: "^[a-z][a-zA-Z0-9]*$"
                             },
                             targetModel: {
                                 description: 'Name of the target model being referenced by this relation.\n\nMust exactly match an existing model name in the schema. This is used by\nPrisma to establish the foreign key constraint and generate the\nappropriate relation mapping.\n\nExamples:\n\n- "shopping_customers" for customer relationships\n- "shopping_channels" for channel relationships\n- "bbs_articles" for article relationships\n- "attachment_files" for file attachments\n\nThe target model should exist in the same schema or be accessible through\nthe Prisma schema configuration.',
@@ -31815,8 +31897,9 @@ const collection$e = {
                         type: "object",
                         properties: {
                             name: {
-                                description: "Name of the field in the database table.\n\nMUST use snake_case naming convention. Common patterns from uploaded\nschemas:\n\n- Timestamps: created_at, updated_at, deleted_at, opened_at, closed_at\n- Identifiers: code, name, nickname, title\n- Business data: value, quantity, price, volume, balance\n- Flags: primary, required, exclusive, secret, multiplicative\n\n\n@pattern ^[a-z][a-z0-9_]*$",
-                                type: "string"
+                                description: "Name of the field in the database table.\n\nMUST use snake_case naming convention. Common patterns from uploaded\nschemas:\n\n- Timestamps: created_at, updated_at, deleted_at, opened_at, closed_at\n- Identifiers: code, name, nickname, title\n- Business data: value, quantity, price, volume, balance\n- Flags: primary, required, exclusive, secret, multiplicative",
+                                type: "string",
+                                pattern: "^[a-z][a-z0-9_]*$"
                             },
                             type: {
                                 description: "Data type of the field for Prisma schema generation.\n\nMaps to appropriate Prisma/PostgreSQL types:\n\n- Boolean: Boolean flags and yes/no values\n- Int: Integer numbers, quantities, sequences\n- Double: Decimal numbers, prices, monetary values, percentages\n- String: Text data, names, descriptions, codes\n- Uri: URL/URI fields for links and references\n- Uuid: UUID fields (for non-foreign-key UUIDs)\n- Datetime: Timestamp fields with date and time",
@@ -31839,11 +31922,13 @@ const collection$e = {
                         type: "object",
                         properties: {
                             fieldNames: {
-                                description: 'Array of field names that together form the unique constraint.\n\nCan be single field (e.g., ["email"]) or composite (e.g., ["channel_id",\n"code"]). All field names must exist in the model. Order matters for\ncomposite indexes. Examples: ["code"], ["shopping_channel_id",\n"nickname"], ["email"]\n\n\n@minItems 1\n@uniqueItems',
+                                description: 'Array of field names that together form the unique constraint.\n\nCan be single field (e.g., ["email"]) or composite (e.g., ["channel_id",\n"code"]). All field names must exist in the model. Order matters for\ncomposite indexes. Examples: ["code"], ["shopping_channel_id",\n"nickname"], ["email"]',
                                 type: "array",
                                 items: {
                                     type: "string"
-                                }
+                                },
+                                minItems: 1,
+                                uniqueItems: true
                             },
                             unique: {
                                 description: 'Explicit marker indicating this is a unique index.\n\nAlways true to distinguish from regular indexes. Used by code generator\nto emit "@@unique" directive in Prisma schema instead of "@@index".',
@@ -31858,11 +31943,13 @@ const collection$e = {
                         type: "object",
                         properties: {
                             fieldNames: {
-                                description: 'Array of field names to include in the performance index.\n\nCan be single field (e.g., ["created_at"]) or composite (e.g.,\n["customer_id", "created_at"]). All field names must exist in the model.\nOrder matters for composite indexes and should match common query\npatterns. Examples: ["created_at"], ["shopping_customer_id",\n"created_at"], ["ip"]\n\n\n@minItems 1\n@uniqueItems',
+                                description: 'Array of field names to include in the performance index.\n\nCan be single field (e.g., ["created_at"]) or composite (e.g.,\n["customer_id", "created_at"]). All field names must exist in the model.\nOrder matters for composite indexes and should match common query\npatterns. Examples: ["created_at"], ["shopping_customer_id",\n"created_at"], ["ip"]',
                                 type: "array",
                                 items: {
                                     type: "string"
-                                }
+                                },
+                                minItems: 1,
+                                uniqueItems: true
                             }
                         },
                         required: [ "fieldNames" ]
@@ -33472,8 +33559,9 @@ const collection$d = {
                         type: "object",
                         properties: {
                             name: {
-                                description: 'Name of the Prisma model (database table name).\n\nMUST use snake_case naming convention. Examples: "shopping_customers",\n"shopping_sale_snapshots", "bbs_articles" Materialized views use "mv_"\nprefix: "mv_shopping_sale_last_snapshots"\n\n\n@pattern ^[a-z][a-z0-9_]*$',
-                                type: "string"
+                                description: 'Name of the Prisma model (database table name).\n\nMUST use snake_case naming convention. Examples: "shopping_customers",\n"shopping_sale_snapshots", "bbs_articles" Materialized views use "mv_"\nprefix: "mv_shopping_sale_last_snapshots"',
+                                type: "string",
+                                pattern: "^[a-z][a-z0-9_]*$"
                             },
                             description: {
                                 description: 'Detailed description explaining the business purpose and usage of the\nmodel.\n\nShould include:\n\n- Business context and purpose\n- Key relationships with other models\n- Important behavioral notes or constraints\n- References to related entities using "{@\\link ModelName}" syntax\n\n**IMPORTANT**: Description must be written in English. Example: "Customer\ninformation, but not a person but a **connection** basis..."',
@@ -33535,8 +33623,9 @@ const collection$d = {
                         type: "object",
                         properties: {
                             name: {
-                                description: 'Name of the primary key field.\n\nMUST use snake_case naming convention. Consistently named "id" across all\nmodels in the uploaded schemas. Represents the unique identifier for each\nrecord in the table.\n\n\n@pattern ^[a-z][a-z0-9_]*$',
-                                type: "string"
+                                description: 'Name of the primary key field.\n\nMUST use snake_case naming convention. Consistently named "id" across all\nmodels in the uploaded schemas. Represents the unique identifier for each\nrecord in the table.',
+                                type: "string",
+                                pattern: "^[a-z][a-z0-9_]*$"
                             },
                             type: {
                                 description: 'Data type of the primary key field.\n\nAlways "uuid" in the uploaded schemas for better distributed system\nsupport and to avoid exposing sequential IDs that could reveal business\ninformation.',
@@ -33555,8 +33644,9 @@ const collection$d = {
                         type: "object",
                         properties: {
                             name: {
-                                description: 'Name of the foreign key field.\n\nMUST use snake_case naming convention. Follows convention:\n"{target_model_name_without_prefix}_id" Examples: "shopping_customer_id",\n"bbs_article_id", "attachment_file_id" For self-references: "parent_id"\n(e.g., in hierarchical structures)\n\n\n@pattern ^[a-z][a-z0-9_]*$',
-                                type: "string"
+                                description: 'Name of the foreign key field.\n\nMUST use snake_case naming convention. Follows convention:\n"{target_model_name_without_prefix}_id" Examples: "shopping_customer_id",\n"bbs_article_id", "attachment_file_id" For self-references: "parent_id"\n(e.g., in hierarchical structures)',
+                                type: "string",
+                                pattern: "^[a-z][a-z0-9_]*$"
                             },
                             type: {
                                 description: 'Data type of the foreign key field.\n\nAlways "uuid" to match the primary key type of referenced models. Ensures\nreferential integrity and consistency across the schema.',
@@ -33587,8 +33677,9 @@ const collection$d = {
                         type: "object",
                         properties: {
                             name: {
-                                description: 'Name of the relation property in the Prisma model.\n\nThis becomes the property name used to access the related model instance\nthrough the Prisma client. Should be descriptive and reflect the business\nrelationship being modeled.\n\nExamples:\n\n- "customer" for shopping_customer_id field\n- "channel" for shopping_channel_id field\n- "parent" for parent_id field in hierarchical structures\n- "snapshot" for versioning relationships\n- "article" for bbs_article_id field\n\nNaming convention: camelCase, descriptive of the relationship\'s business\nmeaning\n\n\n@pattern ^[a-z][a-zA-Z0-9]*$',
-                                type: "string"
+                                description: 'Name of the relation property in the Prisma model.\n\nThis becomes the property name used to access the related model instance\nthrough the Prisma client. Should be descriptive and reflect the business\nrelationship being modeled.\n\nExamples:\n\n- "customer" for shopping_customer_id field\n- "channel" for shopping_channel_id field\n- "parent" for parent_id field in hierarchical structures\n- "snapshot" for versioning relationships\n- "article" for bbs_article_id field\n\nNaming convention: camelCase, descriptive of the relationship\'s business\nmeaning',
+                                type: "string",
+                                pattern: "^[a-z][a-zA-Z0-9]*$"
                             },
                             targetModel: {
                                 description: 'Name of the target model being referenced by this relation.\n\nMust exactly match an existing model name in the schema. This is used by\nPrisma to establish the foreign key constraint and generate the\nappropriate relation mapping.\n\nExamples:\n\n- "shopping_customers" for customer relationships\n- "shopping_channels" for channel relationships\n- "bbs_articles" for article relationships\n- "attachment_files" for file attachments\n\nThe target model should exist in the same schema or be accessible through\nthe Prisma schema configuration.',
@@ -33602,8 +33693,9 @@ const collection$d = {
                         type: "object",
                         properties: {
                             name: {
-                                description: "Name of the field in the database table.\n\nMUST use snake_case naming convention. Common patterns from uploaded\nschemas:\n\n- Timestamps: created_at, updated_at, deleted_at, opened_at, closed_at\n- Identifiers: code, name, nickname, title\n- Business data: value, quantity, price, volume, balance\n- Flags: primary, required, exclusive, secret, multiplicative\n\n\n@pattern ^[a-z][a-z0-9_]*$",
-                                type: "string"
+                                description: "Name of the field in the database table.\n\nMUST use snake_case naming convention. Common patterns from uploaded\nschemas:\n\n- Timestamps: created_at, updated_at, deleted_at, opened_at, closed_at\n- Identifiers: code, name, nickname, title\n- Business data: value, quantity, price, volume, balance\n- Flags: primary, required, exclusive, secret, multiplicative",
+                                type: "string",
+                                pattern: "^[a-z][a-z0-9_]*$"
                             },
                             type: {
                                 description: "Data type of the field for Prisma schema generation.\n\nMaps to appropriate Prisma/PostgreSQL types:\n\n- Boolean: Boolean flags and yes/no values\n- Int: Integer numbers, quantities, sequences\n- Double: Decimal numbers, prices, monetary values, percentages\n- String: Text data, names, descriptions, codes\n- Uri: URL/URI fields for links and references\n- Uuid: UUID fields (for non-foreign-key UUIDs)\n- Datetime: Timestamp fields with date and time",
@@ -33626,11 +33718,13 @@ const collection$d = {
                         type: "object",
                         properties: {
                             fieldNames: {
-                                description: 'Array of field names that together form the unique constraint.\n\nCan be single field (e.g., ["email"]) or composite (e.g., ["channel_id",\n"code"]). All field names must exist in the model. Order matters for\ncomposite indexes. Examples: ["code"], ["shopping_channel_id",\n"nickname"], ["email"]\n\n\n@minItems 1\n@uniqueItems',
+                                description: 'Array of field names that together form the unique constraint.\n\nCan be single field (e.g., ["email"]) or composite (e.g., ["channel_id",\n"code"]). All field names must exist in the model. Order matters for\ncomposite indexes. Examples: ["code"], ["shopping_channel_id",\n"nickname"], ["email"]',
                                 type: "array",
                                 items: {
                                     type: "string"
-                                }
+                                },
+                                minItems: 1,
+                                uniqueItems: true
                             },
                             unique: {
                                 description: 'Explicit marker indicating this is a unique index.\n\nAlways true to distinguish from regular indexes. Used by code generator\nto emit "@@unique" directive in Prisma schema instead of "@@index".',
@@ -33645,11 +33739,13 @@ const collection$d = {
                         type: "object",
                         properties: {
                             fieldNames: {
-                                description: 'Array of field names to include in the performance index.\n\nCan be single field (e.g., ["created_at"]) or composite (e.g.,\n["customer_id", "created_at"]). All field names must exist in the model.\nOrder matters for composite indexes and should match common query\npatterns. Examples: ["created_at"], ["shopping_customer_id",\n"created_at"], ["ip"]\n\n\n@minItems 1\n@uniqueItems',
+                                description: 'Array of field names to include in the performance index.\n\nCan be single field (e.g., ["created_at"]) or composite (e.g.,\n["customer_id", "created_at"]). All field names must exist in the model.\nOrder matters for composite indexes and should match common query\npatterns. Examples: ["created_at"], ["shopping_customer_id",\n"created_at"], ["ip"]',
                                 type: "array",
                                 items: {
                                     type: "string"
-                                }
+                                },
+                                minItems: 1,
+                                uniqueItems: true
                             }
                         },
                         required: [ "fieldNames" ]
@@ -36357,8 +36453,9 @@ const collection$b = {
                         type: "object",
                         properties: {
                             name: {
-                                description: "The name of the authentication Provider function in {role}Authorize\nformat (e.g., adminAuthorize, userAuthorize). This function will be\ncalled by the decorator to verify JWT tokens and return authenticated\nuser information for the specified role.\n\nDO: Use camelCase naming convention.\n\n\n@pattern ^[a-z][a-zA-Z0-9]*$",
-                                type: "string"
+                                description: "The name of the authentication Provider function in {role}Authorize\nformat (e.g., adminAuthorize, userAuthorize). This function will be\ncalled by the decorator to verify JWT tokens and return authenticated\nuser information for the specified role.\n\nDO: Use camelCase naming convention.",
+                                type: "string",
+                                pattern: "^[a-z][a-zA-Z0-9]*$"
                             },
                             content: {
                                 description: "Complete TypeScript code for the authentication Provider function. Must\ninclude: JWT token verification using jwtAuthorize function, role type\nchecking against payload.type, database query using\nMyGlobal.prisma.{tableName} pattern to verify user existence, and proper\nerror handling with ForbiddenException and UnauthorizedException. The\nfunction should return the authenticated user payload data.",
@@ -36371,8 +36468,9 @@ const collection$b = {
                         type: "object",
                         properties: {
                             name: {
-                                description: "The name of the Decorator to be generated in {Actor}Auth format (e.g.,\nAdminAuth, UserAuth). This decorator will be used as a parameter\ndecorator in Controller methods to automatically authenticate and\nauthorize users for the specific role, injecting the authenticated user\npayload as a method parameter.\n\nDO: Use PascalCase naming convention.\n\n\n@pattern ^[A-Z][a-zA-Z0-9]*$",
-                                type: "string"
+                                description: "The name of the Decorator to be generated in {Actor}Auth format (e.g.,\nAdminAuth, UserAuth). This decorator will be used as a parameter\ndecorator in Controller methods to automatically authenticate and\nauthorize users for the specific role, injecting the authenticated user\npayload as a method parameter.\n\nDO: Use PascalCase naming convention.",
+                                type: "string",
+                                pattern: "^[A-Z][a-zA-Z0-9]*$"
                             },
                             content: {
                                 description: "Complete TypeScript code for the authentication Decorator implementation.\nMust include: SwaggerCustomizer integration to add bearer token security\nschema to API documentation, createParamDecorator implementation that\ncalls the corresponding Provider function for authentication, Singleton\npattern using tstl library for efficient decorator instance management,\nand proper TypeScript typing for the ParameterDecorator interface.",
@@ -36385,8 +36483,9 @@ const collection$b = {
                         type: "object",
                         properties: {
                             name: {
-                                description: "The name of the Payload type to be generated in {Actor}Payload format\n(e.g., AdminPayload, UserPayload). This type defines the structure of the\nauthenticated user data that will be injected into Controller methods\nwhen using the decorator.\n\nDO: Use PascalCase naming convention.\n\n\n@pattern ^[A-Z][a-zA-Z0-9]*$",
-                                type: "string"
+                                description: "The name of the Payload type to be generated in {Actor}Payload format\n(e.g., AdminPayload, UserPayload). This type defines the structure of the\nauthenticated user data that will be injected into Controller methods\nwhen using the decorator.\n\nDO: Use PascalCase naming convention.",
+                                type: "string",
+                                pattern: "^[A-Z][a-zA-Z0-9]*$"
                             },
                             content: {
                                 description: "Complete TypeScript code for the Payload type interface in {Actor}Payload\nformat (e.g., AdminPayload, UserPayload). Must include: id field with\nUUID format validation, type field as role discriminator, and proper\ntypia tags for validation. This interface defines the structure of the\nauthenticated user data that will be injected into Controller methods\nwhen using the decorator and serves as the TypeScript type for the\nparameter in Controller method signatures.",
@@ -37001,8 +37100,9 @@ const collection$a = {
                         type: "object",
                         properties: {
                             name: {
-                                description: "The name of the authentication Provider function in {role}Authorize\nformat (e.g., adminAuthorize, userAuthorize). This function will be\ncalled by the decorator to verify JWT tokens and return authenticated\nuser information for the specified role.\n\nDO: Use camelCase naming convention.\n\n\n@pattern ^[a-z][a-zA-Z0-9]*$",
-                                type: "string"
+                                description: "The name of the authentication Provider function in {role}Authorize\nformat (e.g., adminAuthorize, userAuthorize). This function will be\ncalled by the decorator to verify JWT tokens and return authenticated\nuser information for the specified role.\n\nDO: Use camelCase naming convention.",
+                                type: "string",
+                                pattern: "^[a-z][a-zA-Z0-9]*$"
                             },
                             content: {
                                 description: "Complete TypeScript code for the authentication Provider function. Must\ninclude: JWT token verification using jwtAuthorize function, role type\nchecking against payload.type, database query using\nMyGlobal.prisma.{tableName} pattern to verify user existence, and proper\nerror handling with ForbiddenException and UnauthorizedException. The\nfunction should return the authenticated user payload data.",
@@ -37015,8 +37115,9 @@ const collection$a = {
                         type: "object",
                         properties: {
                             name: {
-                                description: "The name of the Decorator to be generated in {Actor}Auth format (e.g.,\nAdminAuth, UserAuth). This decorator will be used as a parameter\ndecorator in Controller methods to automatically authenticate and\nauthorize users for the specific role, injecting the authenticated user\npayload as a method parameter.\n\nDO: Use PascalCase naming convention.\n\n\n@pattern ^[A-Z][a-zA-Z0-9]*$",
-                                type: "string"
+                                description: "The name of the Decorator to be generated in {Actor}Auth format (e.g.,\nAdminAuth, UserAuth). This decorator will be used as a parameter\ndecorator in Controller methods to automatically authenticate and\nauthorize users for the specific role, injecting the authenticated user\npayload as a method parameter.\n\nDO: Use PascalCase naming convention.",
+                                type: "string",
+                                pattern: "^[A-Z][a-zA-Z0-9]*$"
                             },
                             content: {
                                 description: "Complete TypeScript code for the authentication Decorator implementation.\nMust include: SwaggerCustomizer integration to add bearer token security\nschema to API documentation, createParamDecorator implementation that\ncalls the corresponding Provider function for authentication, Singleton\npattern using tstl library for efficient decorator instance management,\nand proper TypeScript typing for the ParameterDecorator interface.",
@@ -37029,8 +37130,9 @@ const collection$a = {
                         type: "object",
                         properties: {
                             name: {
-                                description: "The name of the Payload type to be generated in {Actor}Payload format\n(e.g., AdminPayload, UserPayload). This type defines the structure of the\nauthenticated user data that will be injected into Controller methods\nwhen using the decorator.\n\nDO: Use PascalCase naming convention.\n\n\n@pattern ^[A-Z][a-zA-Z0-9]*$",
-                                type: "string"
+                                description: "The name of the Payload type to be generated in {Actor}Payload format\n(e.g., AdminPayload, UserPayload). This type defines the structure of the\nauthenticated user data that will be injected into Controller methods\nwhen using the decorator.\n\nDO: Use PascalCase naming convention.",
+                                type: "string",
+                                pattern: "^[A-Z][a-zA-Z0-9]*$"
                             },
                             content: {
                                 description: "Complete TypeScript code for the Payload type interface in {Actor}Payload\nformat (e.g., AdminPayload, UserPayload). Must include: id field with\nUUID format validation, type field as role discriminator, and proper\ntypia tags for validation. This interface defines the structure of the\nauthenticated user data that will be injected into Controller methods\nwhen using the decorator and serves as the TypeScript type for the\nparameter in Controller method signatures.",
@@ -42627,11 +42729,12 @@ const collection$3 = {
                                     $ref: "#/$defs/AutoBeOpenApi.IEndpoint"
                                 },
                                 scenarios: {
-                                    description: "An array of test scenarios associated with the given endpoint.\n\nEach scenario represents a specific test case for the same `path` and\n`method`.\n\nIMPORTANT: Each scenario must be actually implementable. A scenario's\nimplementability is determined by the existence of ALL APIs (endpoints)\nrequired to test it. This includes not only the primary endpoint being\ntested, but also ALL dependency endpoints needed for setup,\nauthentication, and data preparation. If even one required dependency API\nis missing from the available operations, the scenario cannot be\nimplemented and should not be generated.\n\nExample: A \"test banned user login\" scenario requires both a login API\nAND a ban user API. If the ban API doesn't exist, this scenario is not\nimplementable regardless of database schema fields.\n\n\n@minItems 1",
+                                    description: "An array of test scenarios associated with the given endpoint.\n\nEach scenario represents a specific test case for the same `path` and\n`method`.\n\nIMPORTANT: Each scenario must be actually implementable. A scenario's\nimplementability is determined by the existence of ALL APIs (endpoints)\nrequired to test it. This includes not only the primary endpoint being\ntested, but also ALL dependency endpoints needed for setup,\nauthentication, and data preparation. If even one required dependency API\nis missing from the available operations, the scenario cannot be\nimplemented and should not be generated.\n\nExample: A \"test banned user login\" scenario requires both a login API\nAND a ban user API. If the ban API doesn't exist, this scenario is not\nimplementable regardless of database schema fields.",
                                     type: "array",
                                     items: {
                                         $ref: "#/$defs/IAutoBeTestScenarioApplication.IScenario"
-                                    }
+                                    },
+                                    minItems: 1
                                 }
                             },
                             required: [ "endpoint", "scenarios" ]
@@ -42641,8 +42744,9 @@ const collection$3 = {
                             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)\n\n\n@pattern ^\\/[a-zA-Z0-9\\/_{}.-]*$',
-                                    type: "string"
+                                    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',
@@ -43776,11 +43880,12 @@ const collection$2 = {
                                     $ref: "#/$defs/AutoBeOpenApi.IEndpoint"
                                 },
                                 scenarios: {
-                                    description: "An array of test scenarios associated with the given endpoint.\n\nEach scenario represents a specific test case for the same `path` and\n`method`.\n\nIMPORTANT: Each scenario must be actually implementable. A scenario's\nimplementability is determined by the existence of ALL APIs (endpoints)\nrequired to test it. This includes not only the primary endpoint being\ntested, but also ALL dependency endpoints needed for setup,\nauthentication, and data preparation. If even one required dependency API\nis missing from the available operations, the scenario cannot be\nimplemented and should not be generated.\n\nExample: A \"test banned user login\" scenario requires both a login API\nAND a ban user API. If the ban API doesn't exist, this scenario is not\nimplementable regardless of database schema fields.\n\n\n@minItems 1",
+                                    description: "An array of test scenarios associated with the given endpoint.\n\nEach scenario represents a specific test case for the same `path` and\n`method`.\n\nIMPORTANT: Each scenario must be actually implementable. A scenario's\nimplementability is determined by the existence of ALL APIs (endpoints)\nrequired to test it. This includes not only the primary endpoint being\ntested, but also ALL dependency endpoints needed for setup,\nauthentication, and data preparation. If even one required dependency API\nis missing from the available operations, the scenario cannot be\nimplemented and should not be generated.\n\nExample: A \"test banned user login\" scenario requires both a login API\nAND a ban user API. If the ban API doesn't exist, this scenario is not\nimplementable regardless of database schema fields.",
                                     type: "array",
                                     items: {
                                         $ref: "#/$defs/IAutoBeTestScenarioApplication.IScenario"
-                                    }
+                                    },
+                                    minItems: 1
                                 }
                             },
                             required: [ "endpoint", "scenarios" ]
@@ -43790,8 +43895,9 @@ const collection$2 = {
                             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)\n\n\n@pattern ^\\/[a-zA-Z0-9\\/_{}.-]*$',
-                                    type: "string"
+                                    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',