@autobe/agent 0.30.4 → 0.30.5

package/lib/orchestrate/prisma/orchestratePrismaAuthorization.js

@@ -87,7 +87,7 @@ function process(ctx, props) {
                             properties: {
                                 thinking: {
                                     type: "string",
-                                    description: "Think before you act.\n\nBefore requesting preliminary data or completing your task, reflect on\nyour current state and explain your reasoning:\n\nFor preliminary requests (getAnalysisSections,\ngetPreviousAnalysisSections, getPreviousDatabaseSchemas):\n\n- What critical information is missing for designing auth tables?\n- Why do you need it specifically right now?\n- Be brief - state the gap, don't list everything you have.\n\nFor completion (complete):\n\n- What tables did you design for this actor?\n- How does the design support authentication workflows?\n- Summarize - don't enumerate every single item.\n\nThis reflection helps you avoid duplicate requests and premature\ncompletion."
+                                    description: "Think before you act.\n\nFor preliminary requests: what critical information is missing and why?\nBe brief \u2014 state the gap, don't list everything you have.\n\nFor completion: what key assets did you acquire, what did you accomplish,\nwhy is it sufficient? Summarize \u2014 don't enumerate every single item."
                                 },
                                 request: {
                                     oneOf: [
@@ -113,7 +113,7 @@ function process(ctx, props) {
                                             complete: "#/components/schemas/IAutoBeDatabaseAuthorizationApplication.IComplete"
                                         }
                                     },
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval\n(getAnalysisSections, getPreviousAnalysisSections,\ngetPreviousDatabaseSchemas) or final table design (complete). When\npreliminary returns empty array, that type is removed from the union,\nphysically preventing repeated calls."
+                                    description: "Action to perform. Exhausted preliminary types are removed from the\nunion, physically preventing repeated calls."
                                 }
                             },
                             required: [
@@ -126,7 +126,7 @@ function process(ctx, props) {
                             properties: {
                                 type: {
                                     "const": "getPreviousAnalysisSections",
-                                    description: "Type discriminator for the request.\n\nValue \"getPreviousAnalysisSections\" indicates this is a preliminary data\nrequest for analysis sections from the previous iteration."
+                                    description: "Type discriminator."
                                 },
                                 sectionIds: {
                                     type: "array",
@@ -135,21 +135,21 @@ function process(ctx, props) {
                                         minimum: 0
                                     },
                                     minItems: 1,
-                                    description: "List of section IDs to retrieve from the previous iteration.\n\nCRITICAL: DO NOT request the same section IDs that you have already\nrequested in previous calls."
+                                    description: "Section IDs to retrieve from previous iteration. DO NOT request same IDs\nalready requested in previous calls."
                                 }
                             },
                             required: [
                                 "type",
                                 "sectionIds"
                             ],
-                            description: "Request to retrieve individual analysis sections from previous iteration by\nnumeric ID.\n\nSame as {@link IAutoBePreliminaryGetAnalysisSections} but for sections from\nthe previous generation cycle, enabling comparison and consistency checks."
+                            description: "Request to retrieve analysis sections from the previous iteration by numeric\nID."
                         },
                         IAutoBePreliminaryGetAnalysisSections: {
                             type: "object",
                             properties: {
                                 type: {
                                     "const": "getAnalysisSections",
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getAnalysisSections\" indicates this is a preliminary\ndata request for individual analysis sections."
+                                    description: "Type discriminator."
                                 },
                                 sectionIds: {
                                     type: "array",
@@ -159,21 +159,21 @@ function process(ctx, props) {
                                     },
                                     minItems: 1,
                                     maxItems: 100,
-                                    description: "List of section IDs to retrieve.\n\nThese are sequential integer IDs from the analysis sections catalog. Each\nID maps to a specific ### section in the requirements documents.\n\nCRITICAL: DO NOT request the same section IDs that you have already\nrequested in previous calls."
+                                    description: "Section IDs to retrieve. DO NOT request same IDs already requested in\nprevious calls."
                                 }
                             },
                             required: [
                                 "type",
                                 "sectionIds"
                             ],
-                            description: "Request to retrieve individual analysis sections by numeric ID.\n\nInstead of loading entire analysis files (~110-120KB each), this loads\nspecific ### sections (~200-600 words each) identified by integer IDs from\nthe section catalog."
+                            description: "Request to retrieve individual analysis sections by numeric ID."
                         },
                         IAutoBePreliminaryGetPreviousDatabaseSchemas: {
                             type: "object",
                             properties: {
                                 type: {
                                     "const": "getPreviousDatabaseSchemas",
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getPreviousDatabaseSchemas\" indicates this is a\npreliminary data request for database schemas from a previous version."
+                                    description: "Type discriminator."
                                 },
                                 schemaNames: {
                                     type: "array",
@@ -181,29 +181,29 @@ function process(ctx, props) {
                                         type: "string"
                                     },
                                     minItems: 1,
-                                    description: "List of database table names to retrieve from the previous version.\n\nThese are table schema names that were generated in a previous version and\nare needed as reference context for the current regeneration.\n\n**Important Notes:**\n\n- These schemas MUST exist in the previous version\n- This function is only available when a previous version exists\n- Used for reference/comparison, not for re-requesting within same execution\n- Table names are in snake_case (e.g., \"shopping_sale\", \"bbs_article\")\n\n**When This Function is Available:**\n\n- When a previous version exists\n- When user requests modifications to existing database schema\n- During correction/regeneration cycles that need previous schema context\n\n**When This Function is NOT Available:**\n\n- During initial generation (no previous version exists)\n- No previous database schemas available for this orchestration task\n\n**Example Table Names:**\n\n- \"users\", \"posts\", \"comments\"\n- \"shopping_sales\", \"shopping_orders\", \"shopping_products\"\n- \"bbs_articles\", \"bbs_article_files\""
+                                    description: "Table names to retrieve from previous iteration. DO NOT request same names\nalready requested in previous calls."
                                 }
                             },
                             required: [
                                 "type",
                                 "schemaNames"
                             ],
-                            description: "Request to retrieve database schemas from a previous version.\n\nThis type is used to load database schema definitions that were generated in\na **previous version** of the AutoBE generation pipeline. This is NOT about\nre-requesting schemas within the same execution, but rather accessing\nartifacts from an earlier version.\n\n**Use Case:** When regenerating or modifying the database schema based on\nuser change requests, agents need to reference the previously generated\ndatabase schemas to understand the existing database structure and what needs\nto be modified.\n\n**Key Difference from `getDatabaseSchemas`:**\n\n- `getDatabaseSchemas`: Fetches schemas from the **current version** (the\n  version being generated right now)\n- `getPreviousDatabaseSchemas`: Fetches schemas from the **previous version**\n  (the last successfully generated version)\n\n**Example Scenario:**\n\n    Initial generation:\n    - DATABASE phase creates: users, posts, comments tables\n    - Generation completes successfully\n\n    User: \"Add email verification status to users\"\n\n    Regeneration:\n    - DATABASE phase starts regeneration\n    - Calls getPreviousDatabaseSchemas([\"users\"])\n      \u2192 Loads the previous version of users table schema\n    - Creates new version with emailVerified field added\n\n**Waterfall + Spiral Pattern:**\n\nThis aligns with AutoBE's regeneration cycles where:\n\n- Compilation failures trigger regeneration with corrections\n- User modifications trigger new versions\n- Previous schemas serve as reference for incremental changes"
+                            description: "Request to retrieve database schemas from the previous iteration.\n\nLoads database table definitions from the last successfully generated\nversion, used as reference context during regeneration or modification\ncycles."
                         },
                         "IAutoBeDatabaseAuthorizationApplication.IComplete": {
                             type: "object",
                             properties: {
                                 type: {
                                     "const": "complete",
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"complete\" indicates this is the final task\nexecution request."
+                                    description: "Type discriminator for completion request."
                                 },
                                 analysis: {
                                     type: "string",
-                                    description: "Analysis of all actors' authentication requirements.\n\nDocuments the agent's understanding of each actor's authentication needs:\n\n- What actors exist and their kinds (guest/member/admin)?\n- What authentication patterns apply to each actor kind?\n- What authentication features are required (login, registration, etc.)?\n- What are the session management requirements for each actor?\n- Are there any special authentication mechanisms (2FA, OAuth, etc.)?"
+                                    description: "Analysis of all actors' authentication requirements and patterns."
                                 },
                                 rationale: {
                                     type: "string",
-                                    description: "Rationale for the authorization table design decisions.\n\nExplains why tables were designed this way:\n\n- Why was each table created for each actor?\n- What is the relationship between actor and session tables?\n- How do tables support the authentication workflow for all actors?\n- What normalization decisions were made for auth-related data?"
+                                    description: "Rationale for the authorization table design decisions."
                                 },
                                 tables: {
                                     type: "array",
@@ -211,7 +211,7 @@ function process(ctx, props) {
                                         $ref: "#/components/schemas/AutoBeDatabaseComponentTableDesign"
                                     },
                                     minItems: 1,
-                                    description: "Array of table designs for ALL ACTORS' authentication domains.\n\nContains all database tables required for every actor's authentication\nand authorization needs. Each table design includes table name\n(snake_case, plural) and description explaining the table's purpose.\n\nThe AI agent must design tables based on:\n\n- Each actor's kind (guest/member/admin) and its authentication patterns\n- Authentication requirements from analysis sections\n- Session management requirements (JWT, refresh tokens)\n- Security requirements (password policies, 2FA)\n\nMUST include for EACH actor:\n\n- Main actor table (e.g., `users`, `administrators`, `guests`)\n- Session table (e.g., `user_sessions`, `administrator_sessions`)\n\nMAY include (based on requirements):\n\n- Password reset tokens table\n- Email verification tokens table\n- OAuth connections table\n- Two-factor authentication tokens table"
+                                    description: "Table designs for all actors' authentication domains (snake_case, plural\nnames).\n\nMUST include for each actor: main actor table + session table. MAY\ninclude: password reset, email verification, OAuth, 2FA tables."
                                 }
                             },
                             required: [
@@ -220,26 +220,26 @@ function process(ctx, props) {
                                 "rationale",
                                 "tables"
                             ],
-                            description: "Request to complete the authorization table design for all actors.\n\nTakes all actor definitions (name, kind, description for each) and\ngenerates all database tables required for every actor's authentication and\nauthorization needs, including main actor tables, session tables, and any\nauthentication support tables for each actor.\n\nThis is about creating tables for ALL actors in a single call. Each actor\nmust have at minimum a main actor table and a session table."
+                            description: "Complete authorization table design for all actors. Each actor must have a\nmain actor table and a session table."
                         },
                         AutoBeDatabaseComponentTableDesign: {
                             type: "object",
                             properties: {
                                 description: {
                                     type: "string",
-                                    description: "Brief, concise description of what this table stores and why it's needed.\n\nShould explain:\n\n- What business concept this table represents\n- What data it stores\n- Why this table is necessary for the component's domain\n\n**IMPORTANT**:\n\n- Keep it **concise** - one or two sentences maximum\n- Description must be written in English"
+                                    description: "Business purpose of this table. One or two sentences maximum. MUST be\nwritten in English."
                                 },
                                 name: {
                                     type: "string",
                                     pattern: "^[a-z][a-z0-9_]*$",
-                                    description: "Name of the database table.\n\nMust follow snake_case naming convention with appropriate domain prefix.\nExamples: `shopping_customers`, `bbs_articles`, `order_items`"
+                                    description: "Table name in snake_case with domain prefix (e.g., \"shopping_customers\")."
                                 }
                             },
                             required: [
                                 "description",
                                 "name"
                             ],
-                            description: "Table design with name and description.\n\nRepresents a single table identified during the component extraction phase,\npairing the table name with a description of its purpose. This type\nformalizes the table design structure for database schema generation.\n\nThe description provides business context that helps:\n\n- Review agents validate that the table fulfills actual requirements\n- Schema generation create appropriate models with proper documentation\n- Future developers understand the table's role in the system"
+                            description: "Table design with name and description."
                         }
                     }
                 },
@@ -250,14 +250,14 @@ function process(ctx, props) {
                         parameters: [
                             {
                                 name: "props",
-                                description: " Request containing either preliminary data request or complete\ntable design for all actors",
+                                description: " Request containing either preliminary data request or complete\ntask",
                                 required: true,
                                 schema: {
                                     $ref: "#/components/schemas/IAutoBeDatabaseAuthorizationApplication.IProps"
                                 }
                             }
                         ],
-                        description: "Process authorization table design task for all actors or preliminary data\nrequests.\n\nReceives all actor definitions (name, kind, description for each) and\ngenerates all authentication and authorization related tables for every\nactor type (guest/member/admin) in a single call. This includes for each\nactor:\n\n- The main actor table (e.g., users, administrators, guests)\n- Session tables for JWT token management\n- Authentication support tables (password reset, email verification, etc.)\n\nThis agent is responsible for ALL actor-related tables. The Database\nComponent agent will NOT create any actor or authentication tables."
+                        description: "Process authorization table design task or preliminary data requests."
                     }
                 ]
             },
@@ -524,11 +524,11 @@ function createController(props) {
                     type: "object",
                     properties: {
                         thinking: {
-                            description: "Think before you act.\n\nBefore requesting preliminary data or completing your task, reflect on\nyour current state and explain your reasoning:\n\nFor preliminary requests (getAnalysisSections,\ngetPreviousAnalysisSections, getPreviousDatabaseSchemas):\n\n- What critical information is missing for designing auth tables?\n- Why do you need it specifically right now?\n- Be brief - state the gap, don't list everything you have.\n\nFor completion (complete):\n\n- What tables did you design for this actor?\n- How does the design support authentication workflows?\n- Summarize - don't enumerate every single item.\n\nThis reflection helps you avoid duplicate requests and premature\ncompletion.",
+                            description: "Think before you act.\n\nFor preliminary requests: what critical information is missing and why?\nBe brief \u2014 state the gap, don't list everything you have.\n\nFor completion: what key assets did you acquire, what did you accomplish,\nwhy is it sufficient? Summarize \u2014 don't enumerate every single item.",
                             type: "string"
                         },
                         request: {
-                            description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval\n(getAnalysisSections, getPreviousAnalysisSections,\ngetPreviousDatabaseSchemas) or final table design (complete). When\npreliminary returns empty array, that type is removed from the union,\nphysically preventing repeated calls.",
+                            description: "Action to perform. Exhausted preliminary types are removed from the\nunion, physically preventing repeated calls.",
                             anyOf: [
                                 {
                                     $ref: "#/$defs/IAutoBePreliminaryGetPreviousAnalysisSections"
@@ -561,18 +561,18 @@ function createController(props) {
                     additionalProperties: false,
                     $defs: {
                         IAutoBePreliminaryGetPreviousAnalysisSections: {
-                            description: "Request to retrieve individual analysis sections from previous iteration by\nnumeric ID.\n\nSame as {@link IAutoBePreliminaryGetAnalysisSections} but for sections from\nthe previous generation cycle, enabling comparison and consistency checks.",
+                            description: "Request to retrieve analysis sections from the previous iteration by numeric\nID.",
                             type: "object",
                             properties: {
                                 type: {
-                                    description: "Type discriminator for the request.\n\nValue \"getPreviousAnalysisSections\" indicates this is a preliminary data\nrequest for analysis sections from the previous iteration.",
+                                    description: "Type discriminator.",
                                     type: "string",
                                     "enum": [
                                         "getPreviousAnalysisSections"
                                     ]
                                 },
                                 sectionIds: {
-                                    description: "List of section IDs to retrieve from the previous iteration.\n\nCRITICAL: DO NOT request the same section IDs that you have already\nrequested in previous calls.",
+                                    description: "Section IDs to retrieve from previous iteration. DO NOT request same IDs\nalready requested in previous calls.",
                                     type: "array",
                                     items: {
                                         type: "integer",
@@ -587,18 +587,18 @@ function createController(props) {
                             ]
                         },
                         IAutoBePreliminaryGetAnalysisSections: {
-                            description: "Request to retrieve individual analysis sections by numeric ID.\n\nInstead of loading entire analysis files (~110-120KB each), this loads\nspecific ### sections (~200-600 words each) identified by integer IDs from\nthe section catalog.",
+                            description: "Request to retrieve individual analysis sections by numeric ID.",
                             type: "object",
                             properties: {
                                 type: {
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getAnalysisSections\" indicates this is a preliminary\ndata request for individual analysis sections.",
+                                    description: "Type discriminator.",
                                     type: "string",
                                     "enum": [
                                         "getAnalysisSections"
                                     ]
                                 },
                                 sectionIds: {
-                                    description: "List of section IDs to retrieve.\n\nThese are sequential integer IDs from the analysis sections catalog. Each\nID maps to a specific ### section in the requirements documents.\n\nCRITICAL: DO NOT request the same section IDs that you have already\nrequested in previous calls.",
+                                    description: "Section IDs to retrieve. DO NOT request same IDs already requested in\nprevious calls.",
                                     type: "array",
                                     items: {
                                         type: "integer",
@@ -614,18 +614,18 @@ function createController(props) {
                             ]
                         },
                         IAutoBePreliminaryGetPreviousDatabaseSchemas: {
-                            description: "Request to retrieve database schemas from a previous version.\n\nThis type is used to load database schema definitions that were generated in\na **previous version** of the AutoBE generation pipeline. This is NOT about\nre-requesting schemas within the same execution, but rather accessing\nartifacts from an earlier version.\n\n**Use Case:** When regenerating or modifying the database schema based on\nuser change requests, agents need to reference the previously generated\ndatabase schemas to understand the existing database structure and what needs\nto be modified.\n\n**Key Difference from `getDatabaseSchemas`:**\n\n- `getDatabaseSchemas`: Fetches schemas from the **current version** (the\n  version being generated right now)\n- `getPreviousDatabaseSchemas`: Fetches schemas from the **previous version**\n  (the last successfully generated version)\n\n**Example Scenario:**\n\n    Initial generation:\n    - DATABASE phase creates: users, posts, comments tables\n    - Generation completes successfully\n\n    User: \"Add email verification status to users\"\n\n    Regeneration:\n    - DATABASE phase starts regeneration\n    - Calls getPreviousDatabaseSchemas([\"users\"])\n      \u2192 Loads the previous version of users table schema\n    - Creates new version with emailVerified field added\n\n**Waterfall + Spiral Pattern:**\n\nThis aligns with AutoBE's regeneration cycles where:\n\n- Compilation failures trigger regeneration with corrections\n- User modifications trigger new versions\n- Previous schemas serve as reference for incremental changes",
+                            description: "Request to retrieve database schemas from the previous iteration.\n\nLoads database table definitions from the last successfully generated\nversion, used as reference context during regeneration or modification\ncycles.",
                             type: "object",
                             properties: {
                                 type: {
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getPreviousDatabaseSchemas\" indicates this is a\npreliminary data request for database schemas from a previous version.",
+                                    description: "Type discriminator.",
                                     type: "string",
                                     "enum": [
                                         "getPreviousDatabaseSchemas"
                                     ]
                                 },
                                 schemaNames: {
-                                    description: "List of database table names to retrieve from the previous version.\n\nThese are table schema names that were generated in a previous version and\nare needed as reference context for the current regeneration.\n\n**Important Notes:**\n\n- These schemas MUST exist in the previous version\n- This function is only available when a previous version exists\n- Used for reference/comparison, not for re-requesting within same execution\n- Table names are in snake_case (e.g., \"shopping_sale\", \"bbs_article\")\n\n**When This Function is Available:**\n\n- When a previous version exists\n- When user requests modifications to existing database schema\n- During correction/regeneration cycles that need previous schema context\n\n**When This Function is NOT Available:**\n\n- During initial generation (no previous version exists)\n- No previous database schemas available for this orchestration task\n\n**Example Table Names:**\n\n- \"users\", \"posts\", \"comments\"\n- \"shopping_sales\", \"shopping_orders\", \"shopping_products\"\n- \"bbs_articles\", \"bbs_article_files\"",
+                                    description: "Table names to retrieve from previous iteration. DO NOT request same names\nalready requested in previous calls.",
                                     type: "array",
                                     items: {
                                         type: "string"
@@ -639,26 +639,26 @@ function createController(props) {
                             ]
                         },
                         "IAutoBeDatabaseAuthorizationApplication.IComplete": {
-                            description: "Request to complete the authorization table design for all actors.\n\nTakes all actor definitions (name, kind, description for each) and\ngenerates all database tables required for every actor's authentication and\nauthorization needs, including main actor tables, session tables, and any\nauthentication support tables for each actor.\n\nThis is about creating tables for ALL actors in a single call. Each actor\nmust have at minimum a main actor table and a session table.",
+                            description: "Complete authorization table design for all actors. Each actor must have a\nmain actor table and a session table.",
                             type: "object",
                             properties: {
                                 type: {
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"complete\" indicates this is the final task\nexecution request.",
+                                    description: "Type discriminator for completion request.",
                                     type: "string",
                                     "enum": [
                                         "complete"
                                     ]
                                 },
                                 analysis: {
-                                    description: "Analysis of all actors' authentication requirements.\n\nDocuments the agent's understanding of each actor's authentication needs:\n\n- What actors exist and their kinds (guest/member/admin)?\n- What authentication patterns apply to each actor kind?\n- What authentication features are required (login, registration, etc.)?\n- What are the session management requirements for each actor?\n- Are there any special authentication mechanisms (2FA, OAuth, etc.)?",
+                                    description: "Analysis of all actors' authentication requirements and patterns.",
                                     type: "string"
                                 },
                                 rationale: {
-                                    description: "Rationale for the authorization table design decisions.\n\nExplains why tables were designed this way:\n\n- Why was each table created for each actor?\n- What is the relationship between actor and session tables?\n- How do tables support the authentication workflow for all actors?\n- What normalization decisions were made for auth-related data?",
+                                    description: "Rationale for the authorization table design decisions.",
                                     type: "string"
                                 },
                                 tables: {
-                                    description: "Array of table designs for ALL ACTORS' authentication domains.\n\nContains all database tables required for every actor's authentication\nand authorization needs. Each table design includes table name\n(snake_case, plural) and description explaining the table's purpose.\n\nThe AI agent must design tables based on:\n\n- Each actor's kind (guest/member/admin) and its authentication patterns\n- Authentication requirements from analysis sections\n- Session management requirements (JWT, refresh tokens)\n- Security requirements (password policies, 2FA)\n\nMUST include for EACH actor:\n\n- Main actor table (e.g., `users`, `administrators`, `guests`)\n- Session table (e.g., `user_sessions`, `administrator_sessions`)\n\nMAY include (based on requirements):\n\n- Password reset tokens table\n- Email verification tokens table\n- OAuth connections table\n- Two-factor authentication tokens table",
+                                    description: "Table designs for all actors' authentication domains (snake_case, plural\nnames).\n\nMUST include for each actor: main actor table + session table. MAY\ninclude: password reset, email verification, OAuth, 2FA tables.",
                                     type: "array",
                                     items: {
                                         $ref: "#/$defs/AutoBeDatabaseComponentTableDesign"
@@ -674,15 +674,15 @@ function createController(props) {
                             ]
                         },
                         AutoBeDatabaseComponentTableDesign: {
-                            description: "Table design with name and description.\n\nRepresents a single table identified during the component extraction phase,\npairing the table name with a description of its purpose. This type\nformalizes the table design structure for database schema generation.\n\nThe description provides business context that helps:\n\n- Review agents validate that the table fulfills actual requirements\n- Schema generation create appropriate models with proper documentation\n- Future developers understand the table's role in the system",
+                            description: "Table design with name and description.",
                             type: "object",
                             properties: {
                                 description: {
-                                    description: "Brief, concise description of what this table stores and why it's needed.\n\nShould explain:\n\n- What business concept this table represents\n- What data it stores\n- Why this table is necessary for the component's domain\n\n**IMPORTANT**:\n\n- Keep it **concise** - one or two sentences maximum\n- Description must be written in English",
+                                    description: "Business purpose of this table. One or two sentences maximum. MUST be\nwritten in English.",
                                     type: "string"
                                 },
                                 name: {
-                                    description: "Name of the database table.\n\nMust follow snake_case naming convention with appropriate domain prefix.\nExamples: `shopping_customers`, `bbs_articles`, `order_items`",
+                                    description: "Table name in snake_case with domain prefix (e.g., \"shopping_customers\").",
                                     type: "string",
                                     pattern: "^[a-z][a-z0-9_]*$"
                                 }
@@ -694,7 +694,7 @@ function createController(props) {
                         }
                     }
                 },
-                description: "Process authorization table design task for all actors or preliminary data\nrequests.\n\nReceives all actor definitions (name, kind, description for each) and\ngenerates all authentication and authorization related tables for every\nactor type (guest/member/admin) in a single call. This includes for each\nactor:\n\n- The main actor table (e.g., users, administrators, guests)\n- Session tables for JWT token management\n- Authentication support tables (password reset, email verification, etc.)\n\nThis agent is responsible for ALL actor-related tables. The Database\nComponent agent will NOT create any actor or authentication tables.",
+                description: "Process authorization table design task or preliminary data requests.",
                 validate: (() => { const _io0 = input => "string" === typeof input.thinking && ("object" === typeof input.request && null !== input.request && _iu0(input.request)); const _io1 = input => "getAnalysisSections" === input.type && (Array.isArray(input.sectionIds) && (1 <= input.sectionIds.length && input.sectionIds.length <= 100 && input.sectionIds.every(elem => "number" === typeof elem && __typia_transform__isTypeUint32._isTypeUint32(elem)))); const _io2 = input => "getPreviousAnalysisSections" === input.type && (Array.isArray(input.sectionIds) && (1 <= input.sectionIds.length && input.sectionIds.every(elem => "number" === typeof elem && __typia_transform__isTypeUint32._isTypeUint32(elem)))); const _io3 = input => "getPreviousDatabaseSchemas" === input.type && (Array.isArray(input.schemaNames) && (1 <= input.schemaNames.length && input.schemaNames.every(elem => "string" === typeof elem))); const _io4 = input => "complete" === input.type && "string" === typeof input.analysis && "string" === typeof input.rationale && (Array.isArray(input.tables) && (1 <= input.tables.length && input.tables.every(elem => "object" === typeof elem && null !== elem && _io5(elem)))); const _io5 = input => "string" === typeof input.description && ("string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name)); const _iu0 = input => (() => {
                     if ("getPreviousAnalysisSections" === input.type)
                         return _io2(input);