@autobe/agent 0.30.4 → 0.30.5

package/lib/orchestrate/prisma/orchestratePrismaCorrect.js

@@ -157,7 +157,7 @@ function execute(ctx, failure) {
                             properties: {
                                 thinking: {
                                     type: "string",
-                                    description: "Think before you act.\n\nBefore requesting preliminary data or completing your task, reflect on\nyour current state and explain your reasoning:\n\nFor preliminary requests (getAnalysisSections, getDatabaseSchemas, etc.):\n\n- What critical information is missing that you don't already have?\n- Why do you need it specifically right now?\n- Be brief - state the gap, don't list everything you have.\n\nFor completion (complete):\n\n- What key assets did you acquire?\n- What did you accomplish?\n- Why is it sufficient to complete?\n- Summarize - don't enumerate every single item.\n\nThis reflection helps you avoid duplicate requests and premature\ncompletion."
+                                    description: "Think before you act.\n\nFor preliminary requests: what critical information is missing and why?\nBe brief \u2014 state the gap, don't list everything you have.\n\nFor completion: what key assets did you acquire, what did you accomplish,\nwhy is it sufficient? Summarize \u2014 don't enumerate every single item."
                                 },
                                 request: {
                                     oneOf: [
@@ -187,7 +187,7 @@ function execute(ctx, failure) {
                                             complete: "#/components/schemas/IAutoBeDatabaseCorrectApplication.IComplete"
                                         }
                                     },
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval\n(getAnalysisSections, getPreviousAnalysisSections, getDatabaseSchemas,\ngetPreviousDatabaseSchemas) or final schema correction (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: [
@@ -200,7 +200,7 @@ function execute(ctx, failure) {
                             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",
@@ -210,21 +210,21 @@ function execute(ctx, failure) {
                                     },
                                     minItems: 1,
                                     maxItems: 100,
-                                    description: "List of section IDs to retrieve.\n\nThese are sequential integer IDs from the analysis sections catalog. Each\nID maps to a specific ### section in the requirements documents.\n\nCRITICAL: DO NOT request the same section IDs that you have already\nrequested in previous calls."
+                                    description: "Section IDs to retrieve. DO NOT request same IDs already requested in\nprevious calls."
                                 }
                             },
                             required: [
                                 "type",
                                 "sectionIds"
                             ],
-                            description: "Request to retrieve individual analysis sections by numeric ID.\n\nInstead of loading entire analysis files (~110-120KB each), this loads\nspecific ### sections (~200-600 words each) identified by integer IDs from\nthe section catalog."
+                            description: "Request to retrieve individual analysis sections by numeric ID."
                         },
                         IAutoBePreliminaryGetDatabaseSchemas: {
                             type: "object",
                             properties: {
                                 type: {
                                     "const": "getDatabaseSchemas",
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getDatabaseSchemas\" indicates this is a preliminary\ndata request for database schemas."
+                                    description: "Type discriminator."
                                 },
                                 schemaNames: {
                                     type: "array",
@@ -232,21 +232,21 @@ function execute(ctx, failure) {
                                         type: "string"
                                     },
                                     minItems: 1,
-                                    description: "List of database table names to retrieve.\n\nTable names from the database schema representing database entities (e.g.,\n\"user\", \"post\", \"comment\").\n\nCRITICAL: DO NOT request the same schema names that you have already\nrequested in previous calls."
+                                    description: "Database table names to retrieve. DO NOT request same names already\nrequested in previous calls."
                                 }
                             },
                             required: [
                                 "type",
                                 "schemaNames"
                             ],
-                            description: "Request to retrieve database schema definitions for context.\n\nThis type is used in the preliminary phase to request specific database table\nschemas needed for generating type-safe API operations."
+                            description: "Request to retrieve database schema definitions for context."
                         },
                         IAutoBePreliminaryGetPreviousAnalysisSections: {
                             type: "object",
                             properties: {
                                 type: {
                                     "const": "getPreviousAnalysisSections",
-                                    description: "Type discriminator for the request.\n\nValue \"getPreviousAnalysisSections\" indicates this is a preliminary data\nrequest for analysis sections from the previous iteration."
+                                    description: "Type discriminator."
                                 },
                                 sectionIds: {
                                     type: "array",
@@ -255,21 +255,21 @@ function execute(ctx, failure) {
                                         minimum: 0
                                     },
                                     minItems: 1,
-                                    description: "List of section IDs to retrieve from the previous iteration.\n\nCRITICAL: DO NOT request the same section IDs that you have already\nrequested in previous calls."
+                                    description: "Section IDs to retrieve from previous iteration. DO NOT request same IDs\nalready requested in previous calls."
                                 }
                             },
                             required: [
                                 "type",
                                 "sectionIds"
                             ],
-                            description: "Request to retrieve individual analysis sections from previous iteration by\nnumeric ID.\n\nSame as {@link IAutoBePreliminaryGetAnalysisSections} but for sections from\nthe previous generation cycle, enabling comparison and consistency checks."
+                            description: "Request to retrieve analysis sections from the previous iteration by numeric\nID."
                         },
                         IAutoBePreliminaryGetPreviousDatabaseSchemas: {
                             type: "object",
                             properties: {
                                 type: {
                                     "const": "getPreviousDatabaseSchemas",
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getPreviousDatabaseSchemas\" indicates this is a\npreliminary data request for database schemas from a previous version."
+                                    description: "Type discriminator."
                                 },
                                 schemaNames: {
                                     type: "array",
@@ -277,32 +277,32 @@ function execute(ctx, failure) {
                                         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."
                         },
                         "IAutoBeDatabaseCorrectApplication.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."
                                 },
                                 planning: {
                                     type: "string",
-                                    description: "Detailed execution plan for fixing validation errors.\n\nContains systematic reasoning and step-by-step error resolution approach\nfor targeted model validation issues.\n\nRequired planning content:\n\n1. Error scope analysis:\n\n   - List all validation errors from IAutoBeDatabaseValidation.IError[]\n   - Extract unique table names to identify affected models\n   - Categorize errors by type (field duplications, references, types,\n        indexes)\n   - Identify which models need correction vs. remain unchanged\n2. Targeted fix strategy:\n\n   - Focus ONLY on models mentioned in validation errors\n   - Outline minimal changes needed for each affected model\n   - Plan cross-model reference updates without modifying non-error models\n   - Ensure unchanged models maintain valid references to corrected models\n3. Model-specific fix plan:\n\n   - Model-by-model modification plan for ONLY affected models\n   - Exact field additions, renames, or type corrections required\n   - Reference updates within corrected models only\n   - Index corrections limited to affected models\n4. Minimal scope validation:\n\n   - Confirm which models will be included in output (error models only)\n   - List models that will remain unchanged in original schema\n   - Identify cross-model dependencies without including unchanged models\n   - Preserve all business logic within corrected models\n5. Targeted impact assessment:\n\n   - Potential effects of fixes on unchanged models (reference validation)\n   - Verification points for corrected models only\n   - Ensure no new validation errors in targeted models\n   - Confirm minimal output scope compliance"
+                                    description: "Execution plan for fixing validation errors. Required steps:\n\n1. Error scope analysis \u2014 list all validation errors, extract affected table\n   names, categorize by type (duplications, references, types, indexes)\n2. Targeted fix strategy \u2014 focus ONLY on models in errors, outline minimal\n   changes per model\n3. Model-specific fix plan \u2014 detail corrections per affected model\n4. Minimal scope validation \u2014 confirm which models are in/out of output\n5. Targeted impact assessment \u2014 verify fixes don't break references from\n   unchanged models\n\nPreserve all business logic and cross-model references."
                                 },
                                 models: {
                                     type: "array",
                                     items: {
                                         $ref: "#/components/schemas/AutoBeDatabase.IModel"
                                     },
-                                    description: "Models with validation errors that need correction.\n\nContains ONLY models mentioned in IAutoBeDatabaseValidation.IError[]\narray. Each model has specific validation errors requiring targeted\ncorrection. Models not mentioned in errors are excluded from this input.\n\nExpected validation issues:\n\n- Duplicate field/relation names within these specific models\n- Invalid foreign key references from these models to other models\n- Single foreign key fields in index arrays within these models\n- Invalid naming conventions within these specific models\n- Type validation errors in fields of these models\n\nModel content analysis:\n\n- Complete field definitions for each error model only\n- Relationships from these models (may reference unchanged models)\n- Indexes within these models that need correction\n- Business descriptions specific to these models\n- Cross-model references that need validation (read-only for targets)\n\nProcessing notes:\n\n- Input contains ONLY models with validation errors\n- May reference other models not included in this input\n- Cross-model references must be validated but target models won't be\n  modified\n- Output should return corrected versions of ONLY these input models\n- All business logic and descriptions within these models must be preserved\n- Corrections must not break references from unchanged models"
+                                    description: "Models with validation errors that need correction.\n\nContains ONLY models from IAutoBeDatabaseValidation.IError[]. Output\ncorrected versions of these models only. Cross-model references must stay\nvalid but target models are not modified."
                                 }
                             },
                             required: [
@@ -310,7 +310,7 @@ function execute(ctx, failure) {
                                 "planning",
                                 "models"
                             ],
-                            description: "Request to fix validation errors in database models.\n\nExecutes targeted error correction to resolve specific validation issues in\naffected models only. Applies minimal changes while preserving original\ndesign intent and business logic."
+                            description: "Fix validation errors in affected models only, preserving design intent and\nbusiness logic."
                         },
                         "AutoBeDatabase.IModel": {
                             type: "object",
@@ -318,15 +318,15 @@ function execute(ctx, failure) {
                                 name: {
                                     type: "string",
                                     pattern: "^[a-z][a-z0-9_]*$",
-                                    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\""
+                                    description: "MUST use snake_case. Materialized views use \"mv_\" prefix."
                                 },
                                 description: {
                                     type: "string",
-                                    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...\""
+                                    description: "Business purpose of this model. MUST be written in English. Reference\nrelated entities using \"{@\\link ModelName}\" syntax."
                                 },
                                 material: {
                                     type: "boolean",
-                                    description: "Indicates whether this model represents a materialized view for\nperformance optimization.\n\nMaterialized views are read-only computed tables that cache complex query\nresults. They're marked as \"@\\hidden\" in documentation and prefixed with\n\"mv_\" in naming. Examples: mv_shopping_sale_last_snapshots,\nmv_shopping_cart_commodity_prices"
+                                    description: "Whether this model is a materialized view (read-only cached query). If\ntrue, name must use \"mv_\" prefix."
                                 },
                                 stance: {
                                     oneOf: [
@@ -346,46 +346,46 @@ function execute(ctx, failure) {
                                             "const": "session"
                                         }
                                     ],
-                                    description: "Specifies the architectural stance of this model within the database\nsystem.\n\nThis property defines how the table positions itself in relation to other\ntables and what role it plays in the overall data architecture,\nparticularly for API endpoint generation and business logic\norganization.\n\n## Values:\n\n### `\"primary\"` - Main Business Entity\n\nTables that represent core business concepts and serve as the primary\nsubjects of user operations. These tables typically warrant independent\nCRUD API endpoints since users directly interact with these entities.\n\n**Key principle**: If users need to independently create, search, filter,\nor manage entities regardless of their parent context, the table should\nbe primary stance.\n\n**API Requirements:**\n\n- Independent creation endpoints (POST /articles, POST /comments)\n- Search and filtering capabilities across all instances\n- Direct update and delete operations\n- List/pagination endpoints for browsing\n\n**Why `bbs_article_comments` is primary, not subsidiary:**\n\nAlthough comments belong to articles, they require independent\nmanagement:\n\n- **Search across articles**: \"Find all comments by user X across all\n  articles\"\n- **Moderation workflows**: \"List all pending comments for review\"\n- **User activity**: \"Show all comments made by this user\"\n- **Independent operations**: Users edit/delete their comments directly\n- **Notification systems**: \"Alert when any comment is posted\"\n\nIf comments were subsidiary, these operations would be impossible or\nrequire inefficient nested queries through parent articles.\n\n**Characteristics:**\n\n- Represents tangible business concepts that users manage\n- Serves as reference points for other tables\n- Requires comprehensive API operations (CREATE, READ, UPDATE, DELETE)\n- Forms the backbone of the application's business logic\n\n**Examples:**\n\n- `bbs_articles` - Forum posts that users create, edit, and manage\n- `bbs_article_comments` - User comments that require independent\n  management\n\n### `\"actor\"` - Authenticated Actor Entity\n\nTables that represent a true actor in the system (a distinct user type\nwith its own authentication flow, table schema, and business logic).\nActor tables are the canonical identity records used across the system,\nand their sessions are recorded in a separate session table.\n\n**Key principle**: If the user type requires a distinct table and\nauthentication flow (not just an attribute), the table is an actor.\n\n**Characteristics:**\n\n- Serves as the primary identity record for that actor type\n- Owns credentials and actor-specific profile data\n- Has one-to-many sessions stored in a dedicated session table\n- Used as the root of permission and ownership relationships\n\n**Examples:**\n\n- `users` - Standard application users with authentication\n- `shopping_customers` - Customers with login and purchase history\n- `shopping_sellers` - Sellers with business credentials\n- `administrators` - Admins with elevated permissions\n\n### `\"session\"` - Actor Session Entity\n\nTables that represent login sessions for a specific actor. A session\ntable always belongs to exactly one actor type and contains connection\ncontext and temporal fields for auditing.\n\n**Key principle**: A session table exists only to track actor logins and\nmust reference exactly one actor table.\n\n**Characteristics:**\n\n- Child of a single actor table (many sessions per actor)\n- Stores connection metadata (IP, headers, referrer)\n- Append-only audit trail of login events\n- Managed through authentication flows, not direct user CRUD\n\n**Examples:**\n\n- `user_sessions` - Sessions for `users`\n- `shopping_customer_sessions` - Sessions for `shopping_customers`\n\n### `\"subsidiary\"` - Supporting/Dependent Entity\n\nTables that exist to support primary entities but are not independently\nmanaged by users. These tables are typically managed through their parent\nentities and may not need standalone API endpoints.\n\n**Characteristics:**\n\n- Depends on primary or snapshot entities for context\n- Often managed indirectly through parent entity operations\n- May have limited or no independent API operations\n- Provides supporting data or relationships\n\n**Examples:**\n\n- `bbs_article_snapshot_files` - Files attached to article snapshots\n- `bbs_article_snapshot_tags` - Tags associated with article snapshots\n- `bbs_article_comment_snapshot_files` - Files attached to comment\n  snapshots\n\n### `\"snapshot\"` - Historical/Versioning Entity\n\nTables that capture point-in-time states of primary entities for audit\ntrails, version control, or historical tracking. These tables record\nchanges but are rarely modified directly by users.\n\n**Characteristics:**\n\n- Captures historical states of primary entities\n- Typically append-only (rarely updated or deleted)\n- Referenced for audit trails and change tracking\n- Usually read-only from user perspective\n\n**Examples:**\n\n- `bbs_article_snapshots` - Historical states of articles\n- `bbs_article_comment_snapshots` - Comment modification history\n\n## API Generation Guidelines:\n\nThe stance property guides automatic API endpoint generation:\n\n- **`\"actor\"`** \u2192 Generate identity and authentication endpoints for the\n  actor type\n- **`\"session\"`** \u2192 Generate session lifecycle endpoints bound to actor\n  authentication flows\n- **`\"primary\"`** \u2192 Generate full CRUD endpoints based on business\n  requirements\n- **`\"subsidiary\"`** \u2192 Evaluate carefully; often managed through parent\n  entities\n- **`\"snapshot\"`** \u2192 Typically read-only endpoints for historical data\n  access"
+                                    description: "Architectural role of this model, guiding API endpoint generation.\n\n- \"primary\": Core entity users manage independently (full CRUD APIs). Use\n  when users need to create, search, or manage entities outside their\n  parent context.\n- \"actor\": Authenticated user type with its own identity, credentials, and\n  auth flow. Generates auth endpoints.\n- \"session\": Login session table belonging to exactly one actor.\n  Append-only audit trail, managed via auth flows.\n- \"subsidiary\": Supporting entity managed through its parent, rarely needs\n  standalone endpoints.\n- \"snapshot\": Point-in-time versioning record, typically append-only and\n  read-only from user perspective."
                                 },
                                 primaryField: {
                                     $ref: "#/components/schemas/AutoBeDatabase.IPrimaryField",
-                                    description: "The primary key field of the model.\n\nIn all uploaded schemas, primary keys are always UUID type with \"@\\id\"\ndirective. Usually named \"id\" and marked with \"@\\db.Uuid\" for PostgreSQL\nmapping."
+                                    description: "Primary key field (UUID)."
                                 },
                                 foreignFields: {
                                     type: "array",
                                     items: {
                                         $ref: "#/components/schemas/AutoBeDatabase.IForeignField"
                                     },
-                                    description: "Array of foreign key fields that reference other models.\n\nThese establish relationships between models and include Prisma relation\ndirectives. Can be nullable (optional relationships) or required\n(mandatory relationships). May have unique constraints for 1:1\nrelationships."
+                                    description: "Foreign key fields establishing relationships to other models."
                                 },
                                 plainFields: {
                                     type: "array",
                                     items: {
                                         $ref: "#/components/schemas/AutoBeDatabase.IPlainField"
                                     },
-                                    description: "Array of regular data fields that don't reference other models.\n\nInclude business data like names, descriptions, timestamps, flags,\namounts, etc. Common patterns: created_at, updated_at, deleted_at for\nsoft deletion and auditing."
+                                    description: "Regular data fields (names, timestamps, flags, amounts, etc.)."
                                 },
                                 uniqueIndexes: {
                                     type: "array",
                                     items: {
                                         $ref: "#/components/schemas/AutoBeDatabase.IUniqueIndex"
                                     },
-                                    description: "Array of unique indexes for enforcing data integrity constraints.\n\nEnsure uniqueness across single or multiple columns. Examples: unique\nemail addresses, unique codes within a channel, unique combinations like\n(channel_id, nickname)."
+                                    description: "Unique indexes for data integrity constraints."
                                 },
                                 plainIndexes: {
                                     type: "array",
                                     items: {
                                         $ref: "#/components/schemas/AutoBeDatabase.IPlainIndex"
                                     },
-                                    description: "Array of regular indexes for query performance optimization.\n\nSpeed up common query patterns like filtering by foreign keys, date\nranges, or frequently searched fields. Examples: indexes on created_at,\nforeign key fields, search fields."
+                                    description: "Regular indexes for query performance."
                                 },
                                 ginIndexes: {
                                     type: "array",
                                     items: {
                                         $ref: "#/components/schemas/AutoBeDatabase.IGinIndex"
                                     },
-                                    description: "Array of GIN (Generalized Inverted Index) indexes for full-text search.\n\nUsed specifically for PostgreSQL text search capabilities using trigram\noperations. Applied to text fields that need fuzzy matching or partial\ntext search. Examples: searching names, nicknames, titles, content\nbodies."
+                                    description: "GIN indexes for PostgreSQL full-text search (trigram)."
                                 }
                             },
                             required: [
@@ -400,7 +400,7 @@ function execute(ctx, failure) {
                                 "plainIndexes",
                                 "ginIndexes"
                             ],
-                            description: "Interface representing a single Prisma model (database table).\n\nBased on the uploaded schemas, models follow specific patterns:\n\n- Main business entities (e.g., shopping_sales, shopping_customers)\n- Snapshot/versioning entities for audit trails (e.g.,\n  shopping_sale_snapshots)\n- Junction tables for M:N relationships (e.g.,\n  shopping_cart_commodity_stocks)\n- Materialized views for performance (prefixed with mv_)"
+                            description: "A single Prisma model (database table)."
                         },
                         "AutoBeDatabase.IPrimaryField": {
                             type: "object",
@@ -408,15 +408,14 @@ function execute(ctx, failure) {
                                 name: {
                                     type: "string",
                                     pattern: "^[a-z][a-z0-9_]*$",
-                                    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."
+                                    description: "MUST use snake_case."
                                 },
                                 type: {
-                                    "const": "uuid",
-                                    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."
+                                    "const": "uuid"
                                 },
                                 description: {
                                     type: "string",
-                                    description: "Description of the primary key field's purpose.\n\nStandard description is \"Primary Key.\" across all models. Serves as the\nunique identifier for the model instance.\n\n**IMPORTANT**: Description must be written in English."
+                                    description: "Business purpose of this primary key. MUST be written in English."
                                 }
                             },
                             required: [
@@ -424,7 +423,7 @@ function execute(ctx, failure) {
                                 "type",
                                 "description"
                             ],
-                            description: "Interface representing the primary key field of a Prisma model.\n\nAll models in the uploaded schemas use UUID as primary key for better\ndistributed system compatibility and security (no sequential ID exposure)."
+                            description: "Primary key field of a model."
                         },
                         "AutoBeDatabase.IForeignField": {
                             type: "object",
@@ -432,27 +431,26 @@ function execute(ctx, failure) {
                                 name: {
                                     type: "string",
                                     pattern: "^[a-z][a-z0-9_]*$",
-                                    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)"
+                                    description: "MUST use snake_case. Convention: \"{target_model}_id\"."
                                 },
                                 type: {
-                                    "const": "uuid",
-                                    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."
+                                    "const": "uuid"
                                 },
                                 description: {
                                     type: "string",
-                                    description: "Description explaining the purpose and target of this foreign key\nrelationship.\n\nShould reference the target model using format: \"Target model's {@\\link\nModelName.id}\" Examples: \"Belonged customer's {@\\link\nshopping_customers.id}\" May include additional context about the\nrelationship's business meaning.\n\n**IMPORTANT**: Description must be written in English."
+                                    description: "Use format: \"Target's {@\\link ModelName.id}\". MUST be written in English."
                                 },
                                 relation: {
                                     $ref: "#/components/schemas/AutoBeDatabase.IRelation",
-                                    description: "Prisma relation configuration defining the association details.\n\nSpecifies how this foreign key connects to the target model, including\nrelation name, target model, and target field. This configuration is used\nto generate the appropriate Prisma relation directive in the schema."
+                                    description: "Prisma relation configuration."
                                 },
                                 unique: {
                                     type: "boolean",
-                                    description: "Whether this foreign key has a unique constraint.\n\nTrue: Creates a 1:1 relationship (e.g., user profile, order publish\ndetails) false: Allows 1:N relationship (e.g., customer to multiple\norders) Used for enforcing business rules about relationship\ncardinality."
+                                    description: "True for 1:1 relationships, false for 1:N."
                                 },
                                 nullable: {
                                     type: "boolean",
-                                    description: "Whether this foreign key can be null (optional relationship).\n\nTrue: Relationship is optional, foreign key can be null false:\nRelationship is required, foreign key cannot be null Reflects business\nrules about mandatory vs optional associations."
+                                    description: "True if the relationship is optional."
                                 }
                             },
                             required: [
@@ -463,7 +461,7 @@ function execute(ctx, failure) {
                                 "unique",
                                 "nullable"
                             ],
-                            description: "Interface representing a foreign key field that establishes relationships\nbetween models.\n\nForeign keys create associations between models, enabling relational data\nmodeling. They can represent 1:1, 1:N, or participate in M:N relationships\nthrough junction tables."
+                            description: "Foreign key field establishing a relationship to another model."
                         },
                         "AutoBeDatabase.IRelation": {
                             type: "object",
@@ -471,16 +469,16 @@ function execute(ctx, failure) {
                                 name: {
                                     type: "string",
                                     pattern: "^[a-z][a-zA-Z0-9]*$",
-                                    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"
+                                    description: "Relation property name in this model. MUST use camelCase."
                                 },
                                 targetModel: {
                                     type: "string",
-                                    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."
+                                    description: "Must match an existing model name in the schema."
                                 },
                                 oppositeName: {
                                     type: "string",
                                     pattern: "^[a-z][a-zA-Z0-9]*$",
-                                    description: "Name of the inverse relation property that will be generated in the\ntarget model.\n\nIn Prisma's bidirectional relationships, both sides need relation\nproperties. While {@link name} defines the property in the current model\n(the one with the foreign key), `oppositeName` defines the property that\nwill be generated in the target model for back-reference.\n\nFor 1:N relationships, the target model's property will be an array type.\nFor 1:1 relationships (when the foreign key has unique constraint), it\nwill be a singular reference.\n\nExamples (when this FK is defined in `bbs_article_comments` model):\n\n- Name: \"article\" \u2192 `comment.article` accesses the parent article\n- OppositeName: \"comments\" \u2192 `article.comments` accesses child comments\n\nMore examples:\n\n- \"sessions\" for `users` model to access `user_sessions[]`\n- \"snapshots\" for `bbs_articles` model to access `bbs_article_snapshots[]`\n- \"children\" for self-referential hierarchies via `parent` relation\n\nNaming convention: camelCase, typically plural for 1:N relationships,\nsingular for 1:1 relationships."
+                                    description: "Inverse relation property name generated in the target model. Typically\nplural for 1:N (e.g., \"comments\"), singular for 1:1."
                                 }
                             },
                             required: [
@@ -488,7 +486,7 @@ function execute(ctx, failure) {
                                 "targetModel",
                                 "oppositeName"
                             ],
-                            description: "Interface representing a Prisma relation configuration between models.\n\nThis interface defines how foreign key fields establish relationships with\ntheir target models. It provides the necessary information for Prisma to\ngenerate appropriate relation directives (@relation) in the schema,\nenabling proper relational data modeling and ORM functionality.\n\nThe relation configuration is essential for:\n\n- Generating correct Prisma relation syntax\n- Establishing bidirectional relationships between models\n- Enabling proper type-safe querying through Prisma client\n- Supporting complex relationship patterns (1:1, 1:N, M:N)"
+                            description: "Prisma"
                         },
                         "AutoBeDatabase.IPlainField": {
                             type: "object",
@@ -496,7 +494,7 @@ function execute(ctx, failure) {
                                 name: {
                                     type: "string",
                                     pattern: "^[a-z][a-z0-9_]*$",
-                                    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"
+                                    description: "MUST use snake_case."
                                 },
                                 type: {
                                     oneOf: [
@@ -522,15 +520,15 @@ function execute(ctx, failure) {
                                             "const": "datetime"
                                         }
                                     ],
-                                    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"
+                                    description: "Prisma/PostgreSQL type mapping: boolean, int, double, string, uri, uuid\n(non-FK), datetime."
                                 },
                                 description: {
                                     type: "string",
-                                    description: "Description explaining the business purpose and usage of this field.\n\nShould clearly explain:\n\n- What business concept this field represents\n- Valid values or constraints if applicable\n- How it relates to business processes\n- Any special behavioral notes\n\n**IMPORTANT**: Description must be written in English. Example: \"Amount\nof cash payment.\" or \"Whether the unit is required or not.\""
+                                    description: "Business purpose of this field. MUST be written in English."
                                 },
                                 nullable: {
                                     type: "boolean",
-                                    description: "Whether this field can contain null values.\n\nTrue: Field is optional and can be null (e.g., middle name, description)\nfalse: Field is required and cannot be null (e.g., creation timestamp,\nname) Reflects business rules about mandatory vs optional data."
+                                    description: "Whether this field can be null."
                                 }
                             },
                             required: [
@@ -539,7 +537,7 @@ function execute(ctx, failure) {
                                 "description",
                                 "nullable"
                             ],
-                            description: "Interface representing a regular data field that stores business\ninformation.\n\nThese fields contain the actual business data like names, amounts,\ntimestamps, flags, descriptions, and other domain-specific information."
+                            description: "A regular data field (not a primary or foreign key)."
                         },
                         "AutoBeDatabase.IUniqueIndex": {
                             type: "object",
@@ -551,18 +549,18 @@ function execute(ctx, failure) {
                                     },
                                     minItems: 1,
                                     uniqueItems: true,
-                                    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\"]"
+                                    description: "Field names forming the unique constraint. All must exist in the model."
                                 },
                                 unique: {
                                     "const": true,
-                                    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\"."
+                                    description: "Always true. Distinguishes from plain indexes."
                                 }
                             },
                             required: [
                                 "fieldNames",
                                 "unique"
                             ],
-                            description: "Interface representing a unique index constraint on one or more fields.\n\nUnique indexes enforce data integrity by ensuring no duplicate values exist\nfor the specified field combination. Essential for business rules that\nrequire uniqueness like email addresses, codes, or composite keys."
+                            description: "Unique index constraint (@@unique)."
                         },
                         "AutoBeDatabase.IPlainIndex": {
                             type: "object",
@@ -574,26 +572,26 @@ function execute(ctx, failure) {
                                     },
                                     minItems: 1,
                                     uniqueItems: true,
-                                    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\"]"
+                                    description: "Field names to index. Order matters for composite indexes."
                                 }
                             },
                             required: [
                                 "fieldNames"
                             ],
-                            description: "Interface representing a regular (non-unique) index for query performance.\n\nRegular indexes speed up database queries by creating optimized data\nstructures for common search patterns. Essential for foreign keys, date\nranges, and frequently filtered fields."
+                            description: "Regular index for query performance (@@index)."
                         },
                         "AutoBeDatabase.IGinIndex": {
                             type: "object",
                             properties: {
                                 fieldName: {
                                     type: "string",
-                                    description: "Name of the text field to index for full-text search capabilities.\n\nMust be a string field in the model that contains searchable text.\nExamples from uploaded schemas: \"nickname\", \"title\", \"body\", \"name\" Used\nwith PostgreSQL gin_trgm_ops for trigram-based fuzzy text search."
+                                    description: "Must be a string field containing searchable text."
                                 }
                             },
                             required: [
                                 "fieldName"
                             ],
-                            description: "Interface representing a GIN (Generalized Inverted Index) for full-text\nsearch.\n\nGIN indexes enable advanced PostgreSQL text search capabilities including\nfuzzy matching and partial text search using trigram operations. Essential\nfor user-facing search features on text content."
+                            description: "GIN index for PostgreSQL full-text search (gin_trgm_ops)."
                         }
                     }
                 },
@@ -611,7 +609,7 @@ function execute(ctx, failure) {
                                 }
                             }
                         ],
-                        description: "Process schema correction task or preliminary data requests.\n\nFixes validation errors in specific database models while preserving all\nbusiness logic and model descriptions. Returns ONLY corrected models."
+                        description: "Process schema correction task or preliminary data requests."
                     }
                 ]
             },
@@ -1134,11 +1132,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, getDatabaseSchemas, etc.):\n\n- What critical information is missing that you don't already have?\n- Why do you need it specifically right now?\n- Be brief - state the gap, don't list everything you have.\n\nFor completion (complete):\n\n- What key assets did you acquire?\n- What did you accomplish?\n- Why is it sufficient to complete?\n- Summarize - don't enumerate every single item.\n\nThis reflection helps you avoid duplicate requests and premature\ncompletion.",
+                            description: "Think before you act.\n\nFor preliminary requests: what critical information is missing and why?\nBe brief \u2014 state the gap, don't list everything you have.\n\nFor completion: what key assets did you acquire, what did you accomplish,\nwhy is it sufficient? Summarize \u2014 don't enumerate every single item.",
                             type: "string"
                         },
                         request: {
-                            description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval\n(getAnalysisSections, getPreviousAnalysisSections, getDatabaseSchemas,\ngetPreviousDatabaseSchemas) or final schema correction (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/IAutoBePreliminaryGetAnalysisSections"
@@ -1175,18 +1173,18 @@ function createController(props) {
                     additionalProperties: false,
                     $defs: {
                         IAutoBePreliminaryGetAnalysisSections: {
-                            description: "Request to retrieve individual analysis sections by numeric ID.\n\nInstead of loading entire analysis files (~110-120KB each), this loads\nspecific ### sections (~200-600 words each) identified by integer IDs from\nthe section catalog.",
+                            description: "Request to retrieve individual analysis sections by numeric ID.",
                             type: "object",
                             properties: {
                                 type: {
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getAnalysisSections\" indicates this is a preliminary\ndata request for individual analysis sections.",
+                                    description: "Type discriminator.",
                                     type: "string",
                                     "enum": [
                                         "getAnalysisSections"
                                     ]
                                 },
                                 sectionIds: {
-                                    description: "List of section IDs to retrieve.\n\nThese are sequential integer IDs from the analysis sections catalog. Each\nID maps to a specific ### section in the requirements documents.\n\nCRITICAL: DO NOT request the same section IDs that you have already\nrequested in previous calls.",
+                                    description: "Section IDs to retrieve. DO NOT request same IDs already requested in\nprevious calls.",
                                     type: "array",
                                     items: {
                                         type: "integer",
@@ -1202,18 +1200,18 @@ function createController(props) {
                             ]
                         },
                         IAutoBePreliminaryGetDatabaseSchemas: {
-                            description: "Request to retrieve database schema definitions for context.\n\nThis type is used in the preliminary phase to request specific database table\nschemas needed for generating type-safe API operations.",
+                            description: "Request to retrieve database schema definitions for context.",
                             type: "object",
                             properties: {
                                 type: {
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getDatabaseSchemas\" indicates this is a preliminary\ndata request for database schemas.",
+                                    description: "Type discriminator.",
                                     type: "string",
                                     "enum": [
                                         "getDatabaseSchemas"
                                     ]
                                 },
                                 schemaNames: {
-                                    description: "List of database table names to retrieve.\n\nTable names from the database schema representing database entities (e.g.,\n\"user\", \"post\", \"comment\").\n\nCRITICAL: DO NOT request the same schema names that you have already\nrequested in previous calls.",
+                                    description: "Database table names to retrieve. DO NOT request same names already\nrequested in previous calls.",
                                     type: "array",
                                     items: {
                                         type: "string"
@@ -1227,18 +1225,18 @@ function createController(props) {
                             ]
                         },
                         IAutoBePreliminaryGetPreviousAnalysisSections: {
-                            description: "Request to retrieve individual analysis sections from previous iteration by\nnumeric ID.\n\nSame as {@link IAutoBePreliminaryGetAnalysisSections} but for sections from\nthe previous generation cycle, enabling comparison and consistency checks.",
+                            description: "Request to retrieve analysis sections from the previous iteration by numeric\nID.",
                             type: "object",
                             properties: {
                                 type: {
-                                    description: "Type discriminator for the request.\n\nValue \"getPreviousAnalysisSections\" indicates this is a preliminary data\nrequest for analysis sections from the previous iteration.",
+                                    description: "Type discriminator.",
                                     type: "string",
                                     "enum": [
                                         "getPreviousAnalysisSections"
                                     ]
                                 },
                                 sectionIds: {
-                                    description: "List of section IDs to retrieve from the previous iteration.\n\nCRITICAL: DO NOT request the same section IDs that you have already\nrequested in previous calls.",
+                                    description: "Section IDs to retrieve from previous iteration. DO NOT request same IDs\nalready requested in previous calls.",
                                     type: "array",
                                     items: {
                                         type: "integer",
@@ -1253,18 +1251,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"
@@ -1278,22 +1276,22 @@ function createController(props) {
                             ]
                         },
                         "IAutoBeDatabaseCorrectApplication.IComplete": {
-                            description: "Request to fix validation errors in database models.\n\nExecutes targeted error correction to resolve specific validation issues in\naffected models only. Applies minimal changes while preserving original\ndesign intent and business logic.",
+                            description: "Fix validation errors in affected models only, preserving design intent and\nbusiness logic.",
                             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"
                                     ]
                                 },
                                 planning: {
-                                    description: "Detailed execution plan for fixing validation errors.\n\nContains systematic reasoning and step-by-step error resolution approach\nfor targeted model validation issues.\n\nRequired planning content:\n\n1. Error scope analysis:\n\n   - List all validation errors from IAutoBeDatabaseValidation.IError[]\n   - Extract unique table names to identify affected models\n   - Categorize errors by type (field duplications, references, types,\n        indexes)\n   - Identify which models need correction vs. remain unchanged\n2. Targeted fix strategy:\n\n   - Focus ONLY on models mentioned in validation errors\n   - Outline minimal changes needed for each affected model\n   - Plan cross-model reference updates without modifying non-error models\n   - Ensure unchanged models maintain valid references to corrected models\n3. Model-specific fix plan:\n\n   - Model-by-model modification plan for ONLY affected models\n   - Exact field additions, renames, or type corrections required\n   - Reference updates within corrected models only\n   - Index corrections limited to affected models\n4. Minimal scope validation:\n\n   - Confirm which models will be included in output (error models only)\n   - List models that will remain unchanged in original schema\n   - Identify cross-model dependencies without including unchanged models\n   - Preserve all business logic within corrected models\n5. Targeted impact assessment:\n\n   - Potential effects of fixes on unchanged models (reference validation)\n   - Verification points for corrected models only\n   - Ensure no new validation errors in targeted models\n   - Confirm minimal output scope compliance",
+                                    description: "Execution plan for fixing validation errors. Required steps:\n\n1. Error scope analysis \u2014 list all validation errors, extract affected table\n   names, categorize by type (duplications, references, types, indexes)\n2. Targeted fix strategy \u2014 focus ONLY on models in errors, outline minimal\n   changes per model\n3. Model-specific fix plan \u2014 detail corrections per affected model\n4. Minimal scope validation \u2014 confirm which models are in/out of output\n5. Targeted impact assessment \u2014 verify fixes don't break references from\n   unchanged models\n\nPreserve all business logic and cross-model references.",
                                     type: "string"
                                 },
                                 models: {
-                                    description: "Models with validation errors that need correction.\n\nContains ONLY models mentioned in IAutoBeDatabaseValidation.IError[]\narray. Each model has specific validation errors requiring targeted\ncorrection. Models not mentioned in errors are excluded from this input.\n\nExpected validation issues:\n\n- Duplicate field/relation names within these specific models\n- Invalid foreign key references from these models to other models\n- Single foreign key fields in index arrays within these models\n- Invalid naming conventions within these specific models\n- Type validation errors in fields of these models\n\nModel content analysis:\n\n- Complete field definitions for each error model only\n- Relationships from these models (may reference unchanged models)\n- Indexes within these models that need correction\n- Business descriptions specific to these models\n- Cross-model references that need validation (read-only for targets)\n\nProcessing notes:\n\n- Input contains ONLY models with validation errors\n- May reference other models not included in this input\n- Cross-model references must be validated but target models won't be\n  modified\n- Output should return corrected versions of ONLY these input models\n- All business logic and descriptions within these models must be preserved\n- Corrections must not break references from unchanged models",
+                                    description: "Models with validation errors that need correction.\n\nContains ONLY models from IAutoBeDatabaseValidation.IError[]. Output\ncorrected versions of these models only. Cross-model references must stay\nvalid but target models are not modified.",
                                     type: "array",
                                     items: {
                                         $ref: "#/$defs/AutoBeDatabase.IModel"
@@ -1307,24 +1305,24 @@ function createController(props) {
                             ]
                         },
                         "AutoBeDatabase.IModel": {
-                            description: "Interface representing a single Prisma model (database table).\n\nBased on the uploaded schemas, models follow specific patterns:\n\n- Main business entities (e.g., shopping_sales, shopping_customers)\n- Snapshot/versioning entities for audit trails (e.g.,\n  shopping_sale_snapshots)\n- Junction tables for M:N relationships (e.g.,\n  shopping_cart_commodity_stocks)\n- Materialized views for performance (prefixed with mv_)",
+                            description: "A single Prisma model (database table).",
                             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\"",
+                                    description: "MUST use snake_case. Materialized views use \"mv_\" prefix.",
                                     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...\"",
+                                    description: "Business purpose of this model. MUST be written in English. Reference\nrelated entities using \"{@\\link ModelName}\" syntax.",
                                     type: "string"
                                 },
                                 material: {
-                                    description: "Indicates whether this model represents a materialized view for\nperformance optimization.\n\nMaterialized views are read-only computed tables that cache complex query\nresults. They're marked as \"@\\hidden\" in documentation and prefixed with\n\"mv_\" in naming. Examples: mv_shopping_sale_last_snapshots,\nmv_shopping_cart_commodity_prices",
+                                    description: "Whether this model is a materialized view (read-only cached query). If\ntrue, name must use \"mv_\" prefix.",
                                     type: "boolean"
                                 },
                                 stance: {
-                                    description: "Specifies the architectural stance of this model within the database\nsystem.\n\nThis property defines how the table positions itself in relation to other\ntables and what role it plays in the overall data architecture,\nparticularly for API endpoint generation and business logic\norganization.\n\n## Values:\n\n### `\"primary\"` - Main Business Entity\n\nTables that represent core business concepts and serve as the primary\nsubjects of user operations. These tables typically warrant independent\nCRUD API endpoints since users directly interact with these entities.\n\n**Key principle**: If users need to independently create, search, filter,\nor manage entities regardless of their parent context, the table should\nbe primary stance.\n\n**API Requirements:**\n\n- Independent creation endpoints (POST /articles, POST /comments)\n- Search and filtering capabilities across all instances\n- Direct update and delete operations\n- List/pagination endpoints for browsing\n\n**Why `bbs_article_comments` is primary, not subsidiary:**\n\nAlthough comments belong to articles, they require independent\nmanagement:\n\n- **Search across articles**: \"Find all comments by user X across all\n  articles\"\n- **Moderation workflows**: \"List all pending comments for review\"\n- **User activity**: \"Show all comments made by this user\"\n- **Independent operations**: Users edit/delete their comments directly\n- **Notification systems**: \"Alert when any comment is posted\"\n\nIf comments were subsidiary, these operations would be impossible or\nrequire inefficient nested queries through parent articles.\n\n**Characteristics:**\n\n- Represents tangible business concepts that users manage\n- Serves as reference points for other tables\n- Requires comprehensive API operations (CREATE, READ, UPDATE, DELETE)\n- Forms the backbone of the application's business logic\n\n**Examples:**\n\n- `bbs_articles` - Forum posts that users create, edit, and manage\n- `bbs_article_comments` - User comments that require independent\n  management\n\n### `\"actor\"` - Authenticated Actor Entity\n\nTables that represent a true actor in the system (a distinct user type\nwith its own authentication flow, table schema, and business logic).\nActor tables are the canonical identity records used across the system,\nand their sessions are recorded in a separate session table.\n\n**Key principle**: If the user type requires a distinct table and\nauthentication flow (not just an attribute), the table is an actor.\n\n**Characteristics:**\n\n- Serves as the primary identity record for that actor type\n- Owns credentials and actor-specific profile data\n- Has one-to-many sessions stored in a dedicated session table\n- Used as the root of permission and ownership relationships\n\n**Examples:**\n\n- `users` - Standard application users with authentication\n- `shopping_customers` - Customers with login and purchase history\n- `shopping_sellers` - Sellers with business credentials\n- `administrators` - Admins with elevated permissions\n\n### `\"session\"` - Actor Session Entity\n\nTables that represent login sessions for a specific actor. A session\ntable always belongs to exactly one actor type and contains connection\ncontext and temporal fields for auditing.\n\n**Key principle**: A session table exists only to track actor logins and\nmust reference exactly one actor table.\n\n**Characteristics:**\n\n- Child of a single actor table (many sessions per actor)\n- Stores connection metadata (IP, headers, referrer)\n- Append-only audit trail of login events\n- Managed through authentication flows, not direct user CRUD\n\n**Examples:**\n\n- `user_sessions` - Sessions for `users`\n- `shopping_customer_sessions` - Sessions for `shopping_customers`\n\n### `\"subsidiary\"` - Supporting/Dependent Entity\n\nTables that exist to support primary entities but are not independently\nmanaged by users. These tables are typically managed through their parent\nentities and may not need standalone API endpoints.\n\n**Characteristics:**\n\n- Depends on primary or snapshot entities for context\n- Often managed indirectly through parent entity operations\n- May have limited or no independent API operations\n- Provides supporting data or relationships\n\n**Examples:**\n\n- `bbs_article_snapshot_files` - Files attached to article snapshots\n- `bbs_article_snapshot_tags` - Tags associated with article snapshots\n- `bbs_article_comment_snapshot_files` - Files attached to comment\n  snapshots\n\n### `\"snapshot\"` - Historical/Versioning Entity\n\nTables that capture point-in-time states of primary entities for audit\ntrails, version control, or historical tracking. These tables record\nchanges but are rarely modified directly by users.\n\n**Characteristics:**\n\n- Captures historical states of primary entities\n- Typically append-only (rarely updated or deleted)\n- Referenced for audit trails and change tracking\n- Usually read-only from user perspective\n\n**Examples:**\n\n- `bbs_article_snapshots` - Historical states of articles\n- `bbs_article_comment_snapshots` - Comment modification history\n\n## API Generation Guidelines:\n\nThe stance property guides automatic API endpoint generation:\n\n- **`\"actor\"`** \u2192 Generate identity and authentication endpoints for the\n  actor type\n- **`\"session\"`** \u2192 Generate session lifecycle endpoints bound to actor\n  authentication flows\n- **`\"primary\"`** \u2192 Generate full CRUD endpoints based on business\n  requirements\n- **`\"subsidiary\"`** \u2192 Evaluate carefully; often managed through parent\n  entities\n- **`\"snapshot\"`** \u2192 Typically read-only endpoints for historical data\n  access",
+                                    description: "Architectural role of this model, guiding API endpoint generation.\n\n- \"primary\": Core entity users manage independently (full CRUD APIs). Use\n  when users need to create, search, or manage entities outside their\n  parent context.\n- \"actor\": Authenticated user type with its own identity, credentials, and\n  auth flow. Generates auth endpoints.\n- \"session\": Login session table belonging to exactly one actor.\n  Append-only audit trail, managed via auth flows.\n- \"subsidiary\": Supporting entity managed through its parent, rarely needs\n  standalone endpoints.\n- \"snapshot\": Point-in-time versioning record, typically append-only and\n  read-only from user perspective.",
                                     type: "string",
                                     "enum": [
                                         "primary",
@@ -1335,39 +1333,39 @@ function createController(props) {
                                     ]
                                 },
                                 primaryField: {
-                                    description: "The primary key field of the model.\n\nIn all uploaded schemas, primary keys are always UUID type with \"@\\id\"\ndirective. Usually named \"id\" and marked with \"@\\db.Uuid\" for PostgreSQL\nmapping.",
+                                    description: "Primary key field (UUID).",
                                     $ref: "#/$defs/AutoBeDatabase.IPrimaryField"
                                 },
                                 foreignFields: {
-                                    description: "Array of foreign key fields that reference other models.\n\nThese establish relationships between models and include Prisma relation\ndirectives. Can be nullable (optional relationships) or required\n(mandatory relationships). May have unique constraints for 1:1\nrelationships.",
+                                    description: "Foreign key fields establishing relationships to other models.",
                                     type: "array",
                                     items: {
                                         $ref: "#/$defs/AutoBeDatabase.IForeignField"
                                     }
                                 },
                                 plainFields: {
-                                    description: "Array of regular data fields that don't reference other models.\n\nInclude business data like names, descriptions, timestamps, flags,\namounts, etc. Common patterns: created_at, updated_at, deleted_at for\nsoft deletion and auditing.",
+                                    description: "Regular data fields (names, timestamps, flags, amounts, etc.).",
                                     type: "array",
                                     items: {
                                         $ref: "#/$defs/AutoBeDatabase.IPlainField"
                                     }
                                 },
                                 uniqueIndexes: {
-                                    description: "Array of unique indexes for enforcing data integrity constraints.\n\nEnsure uniqueness across single or multiple columns. Examples: unique\nemail addresses, unique codes within a channel, unique combinations like\n(channel_id, nickname).",
+                                    description: "Unique indexes for data integrity constraints.",
                                     type: "array",
                                     items: {
                                         $ref: "#/$defs/AutoBeDatabase.IUniqueIndex"
                                     }
                                 },
                                 plainIndexes: {
-                                    description: "Array of regular indexes for query performance optimization.\n\nSpeed up common query patterns like filtering by foreign keys, date\nranges, or frequently searched fields. Examples: indexes on created_at,\nforeign key fields, search fields.",
+                                    description: "Regular indexes for query performance.",
                                     type: "array",
                                     items: {
                                         $ref: "#/$defs/AutoBeDatabase.IPlainIndex"
                                     }
                                 },
                                 ginIndexes: {
-                                    description: "Array of GIN (Generalized Inverted Index) indexes for full-text search.\n\nUsed specifically for PostgreSQL text search capabilities using trigram\noperations. Applied to text fields that need fuzzy matching or partial\ntext search. Examples: searching names, nicknames, titles, content\nbodies.",
+                                    description: "GIN indexes for PostgreSQL full-text search (trigram).",
                                     type: "array",
                                     items: {
                                         $ref: "#/$defs/AutoBeDatabase.IGinIndex"
@@ -1388,23 +1386,22 @@ function createController(props) {
                             ]
                         },
                         "AutoBeDatabase.IPrimaryField": {
-                            description: "Interface representing the primary key field of a Prisma model.\n\nAll models in the uploaded schemas use UUID as primary key for better\ndistributed system compatibility and security (no sequential ID exposure).",
+                            description: "Primary key field of a model.",
                             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.",
+                                    description: "MUST use snake_case.",
                                     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.",
                                     type: "string",
                                     "enum": [
                                         "uuid"
                                     ]
                                 },
                                 description: {
-                                    description: "Description of the primary key field's purpose.\n\nStandard description is \"Primary Key.\" across all models. Serves as the\nunique identifier for the model instance.\n\n**IMPORTANT**: Description must be written in English.",
+                                    description: "Business purpose of this primary key. MUST be written in English.",
                                     type: "string"
                                 }
                             },
@@ -1415,35 +1412,34 @@ function createController(props) {
                             ]
                         },
                         "AutoBeDatabase.IForeignField": {
-                            description: "Interface representing a foreign key field that establishes relationships\nbetween models.\n\nForeign keys create associations between models, enabling relational data\nmodeling. They can represent 1:1, 1:N, or participate in M:N relationships\nthrough junction tables.",
+                            description: "Foreign key field establishing a relationship to another model.",
                             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)",
+                                    description: "MUST use snake_case. Convention: \"{target_model}_id\".",
                                     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.",
                                     type: "string",
                                     "enum": [
                                         "uuid"
                                     ]
                                 },
                                 description: {
-                                    description: "Description explaining the purpose and target of this foreign key\nrelationship.\n\nShould reference the target model using format: \"Target model's {@\\link\nModelName.id}\" Examples: \"Belonged customer's {@\\link\nshopping_customers.id}\" May include additional context about the\nrelationship's business meaning.\n\n**IMPORTANT**: Description must be written in English.",
+                                    description: "Use format: \"Target's {@\\link ModelName.id}\". MUST be written in English.",
                                     type: "string"
                                 },
                                 relation: {
-                                    description: "Prisma relation configuration defining the association details.\n\nSpecifies how this foreign key connects to the target model, including\nrelation name, target model, and target field. This configuration is used\nto generate the appropriate Prisma relation directive in the schema.",
+                                    description: "Prisma relation configuration.",
                                     $ref: "#/$defs/AutoBeDatabase.IRelation"
                                 },
                                 unique: {
-                                    description: "Whether this foreign key has a unique constraint.\n\nTrue: Creates a 1:1 relationship (e.g., user profile, order publish\ndetails) false: Allows 1:N relationship (e.g., customer to multiple\norders) Used for enforcing business rules about relationship\ncardinality.",
+                                    description: "True for 1:1 relationships, false for 1:N.",
                                     type: "boolean"
                                 },
                                 nullable: {
-                                    description: "Whether this foreign key can be null (optional relationship).\n\nTrue: Relationship is optional, foreign key can be null false:\nRelationship is required, foreign key cannot be null Reflects business\nrules about mandatory vs optional associations.",
+                                    description: "True if the relationship is optional.",
                                     type: "boolean"
                                 }
                             },
@@ -1457,20 +1453,20 @@ function createController(props) {
                             ]
                         },
                         "AutoBeDatabase.IRelation": {
-                            description: "Interface representing a Prisma relation configuration between models.\n\nThis interface defines how foreign key fields establish relationships with\ntheir target models. It provides the necessary information for Prisma to\ngenerate appropriate relation directives (@relation) in the schema,\nenabling proper relational data modeling and ORM functionality.\n\nThe relation configuration is essential for:\n\n- Generating correct Prisma relation syntax\n- Establishing bidirectional relationships between models\n- Enabling proper type-safe querying through Prisma client\n- Supporting complex relationship patterns (1:1, 1:N, M:N)",
+                            description: "Prisma",
                             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",
+                                    description: "Relation property name in this model. MUST use camelCase.",
                                     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.",
+                                    description: "Must match an existing model name in the schema.",
                                     type: "string"
                                 },
                                 oppositeName: {
-                                    description: "Name of the inverse relation property that will be generated in the\ntarget model.\n\nIn Prisma's bidirectional relationships, both sides need relation\nproperties. While {@link name} defines the property in the current model\n(the one with the foreign key), `oppositeName` defines the property that\nwill be generated in the target model for back-reference.\n\nFor 1:N relationships, the target model's property will be an array type.\nFor 1:1 relationships (when the foreign key has unique constraint), it\nwill be a singular reference.\n\nExamples (when this FK is defined in `bbs_article_comments` model):\n\n- Name: \"article\" \u2192 `comment.article` accesses the parent article\n- OppositeName: \"comments\" \u2192 `article.comments` accesses child comments\n\nMore examples:\n\n- \"sessions\" for `users` model to access `user_sessions[]`\n- \"snapshots\" for `bbs_articles` model to access `bbs_article_snapshots[]`\n- \"children\" for self-referential hierarchies via `parent` relation\n\nNaming convention: camelCase, typically plural for 1:N relationships,\nsingular for 1:1 relationships.",
+                                    description: "Inverse relation property name generated in the target model. Typically\nplural for 1:N (e.g., \"comments\"), singular for 1:1.",
                                     type: "string",
                                     pattern: "^[a-z][a-zA-Z0-9]*$"
                                 }
@@ -1482,16 +1478,16 @@ function createController(props) {
                             ]
                         },
                         "AutoBeDatabase.IPlainField": {
-                            description: "Interface representing a regular data field that stores business\ninformation.\n\nThese fields contain the actual business data like names, amounts,\ntimestamps, flags, descriptions, and other domain-specific information.",
+                            description: "A regular data field (not a primary or foreign key).",
                             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",
+                                    description: "MUST use snake_case.",
                                     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",
+                                    description: "Prisma/PostgreSQL type mapping: boolean, int, double, string, uri, uuid\n(non-FK), datetime.",
                                     type: "string",
                                     "enum": [
                                         "string",
@@ -1504,11 +1500,11 @@ function createController(props) {
                                     ]
                                 },
                                 description: {
-                                    description: "Description explaining the business purpose and usage of this field.\n\nShould clearly explain:\n\n- What business concept this field represents\n- Valid values or constraints if applicable\n- How it relates to business processes\n- Any special behavioral notes\n\n**IMPORTANT**: Description must be written in English. Example: \"Amount\nof cash payment.\" or \"Whether the unit is required or not.\"",
+                                    description: "Business purpose of this field. MUST be written in English.",
                                     type: "string"
                                 },
                                 nullable: {
-                                    description: "Whether this field can contain null values.\n\nTrue: Field is optional and can be null (e.g., middle name, description)\nfalse: Field is required and cannot be null (e.g., creation timestamp,\nname) Reflects business rules about mandatory vs optional data.",
+                                    description: "Whether this field can be null.",
                                     type: "boolean"
                                 }
                             },
@@ -1520,11 +1516,11 @@ function createController(props) {
                             ]
                         },
                         "AutoBeDatabase.IUniqueIndex": {
-                            description: "Interface representing a unique index constraint on one or more fields.\n\nUnique indexes enforce data integrity by ensuring no duplicate values exist\nfor the specified field combination. Essential for business rules that\nrequire uniqueness like email addresses, codes, or composite keys.",
+                            description: "Unique index constraint (@@unique).",
                             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\"]",
+                                    description: "Field names forming the unique constraint. All must exist in the model.",
                                     type: "array",
                                     items: {
                                         type: "string"
@@ -1533,7 +1529,7 @@ function createController(props) {
                                     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\".",
+                                    description: "Always true. Distinguishes from plain indexes.",
                                     type: "boolean",
                                     "enum": [
                                         true
@@ -1546,11 +1542,11 @@ function createController(props) {
                             ]
                         },
                         "AutoBeDatabase.IPlainIndex": {
-                            description: "Interface representing a regular (non-unique) index for query performance.\n\nRegular indexes speed up database queries by creating optimized data\nstructures for common search patterns. Essential for foreign keys, date\nranges, and frequently filtered fields.",
+                            description: "Regular index for query performance (@@index).",
                             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\"]",
+                                    description: "Field names to index. Order matters for composite indexes.",
                                     type: "array",
                                     items: {
                                         type: "string"
@@ -1564,11 +1560,11 @@ function createController(props) {
                             ]
                         },
                         "AutoBeDatabase.IGinIndex": {
-                            description: "Interface representing a GIN (Generalized Inverted Index) for full-text\nsearch.\n\nGIN indexes enable advanced PostgreSQL text search capabilities including\nfuzzy matching and partial text search using trigram operations. Essential\nfor user-facing search features on text content.",
+                            description: "GIN index for PostgreSQL full-text search (gin_trgm_ops).",
                             type: "object",
                             properties: {
                                 fieldName: {
-                                    description: "Name of the text field to index for full-text search capabilities.\n\nMust be a string field in the model that contains searchable text.\nExamples from uploaded schemas: \"nickname\", \"title\", \"body\", \"name\" Used\nwith PostgreSQL gin_trgm_ops for trigram-based fuzzy text search.",
+                                    description: "Must be a string field containing searchable text.",
                                     type: "string"
                                 }
                             },
@@ -1578,7 +1574,7 @@ function createController(props) {
                         }
                     }
                 },
-                description: "Process schema correction task or preliminary data requests.\n\nFixes validation errors in specific database models while preserving all\nbusiness logic and model descriptions. Returns ONLY corrected models.",
+                description: "Process schema correction task or preliminary data requests.",
                 validate: (() => { const _io0 = input => "string" === typeof input.thinking && ("object" === typeof input.request && null !== input.request && _iu0(input.request)); const _io1 = input => "getAnalysisSections" === input.type && (Array.isArray(input.sectionIds) && (1 <= input.sectionIds.length && input.sectionIds.length <= 100 && input.sectionIds.every(elem => "number" === typeof elem && __typia_transform__isTypeUint32._isTypeUint32(elem)))); const _io2 = input => "getDatabaseSchemas" === input.type && (Array.isArray(input.schemaNames) && (1 <= input.schemaNames.length && input.schemaNames.every(elem => "string" === typeof elem))); const _io3 = input => "getPreviousAnalysisSections" === input.type && (Array.isArray(input.sectionIds) && (1 <= input.sectionIds.length && input.sectionIds.every(elem => "number" === typeof elem && __typia_transform__isTypeUint32._isTypeUint32(elem)))); const _io4 = input => "getPreviousDatabaseSchemas" === input.type && (Array.isArray(input.schemaNames) && (1 <= input.schemaNames.length && input.schemaNames.every(elem => "string" === typeof elem))); const _io5 = input => "complete" === input.type && "string" === typeof input.planning && (Array.isArray(input.models) && input.models.every(elem => "object" === typeof elem && null !== elem && _io6(elem))); const _io6 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "string" === typeof input.description && "boolean" === typeof input.material && ("primary" === input.stance || "subsidiary" === input.stance || "snapshot" === input.stance || "actor" === input.stance || "session" === input.stance) && ("object" === typeof input.primaryField && null !== input.primaryField && _io7(input.primaryField)) && (Array.isArray(input.foreignFields) && input.foreignFields.every(elem => "object" === typeof elem && null !== elem && _io8(elem))) && (Array.isArray(input.plainFields) && input.plainFields.every(elem => "object" === typeof elem && null !== elem && _io10(elem))) && (Array.isArray(input.uniqueIndexes) && input.uniqueIndexes.every(elem => "object" === typeof elem && null !== elem && _io11(elem))) && (Array.isArray(input.plainIndexes) && input.plainIndexes.every(elem => "object" === typeof elem && null !== elem && _io12(elem))) && (Array.isArray(input.ginIndexes) && input.ginIndexes.every(elem => "object" === typeof elem && null !== elem && _io13(elem))); const _io7 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "uuid" === input.type && "string" === typeof input.description; const _io8 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "uuid" === input.type && "string" === typeof input.description && ("object" === typeof input.relation && null !== input.relation && _io9(input.relation)) && "boolean" === typeof input.unique && "boolean" === typeof input.nullable; const _io9 = input => "string" === typeof input.name && RegExp("^[a-z][a-zA-Z0-9]*$").test(input.name) && "string" === typeof input.targetModel && ("string" === typeof input.oppositeName && RegExp("^[a-z][a-zA-Z0-9]*$").test(input.oppositeName)); const _io10 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && ("string" === input.type || "boolean" === input.type || "uuid" === input.type || "uri" === input.type || "int" === input.type || "double" === input.type || "datetime" === input.type) && "string" === typeof input.description && "boolean" === typeof input.nullable; const _io11 = input => Array.isArray(input.fieldNames) && (1 <= input.fieldNames.length && __typia_transform__isUniqueItems._isUniqueItems(input.fieldNames) && input.fieldNames.every(elem => "string" === typeof elem)) && true === input.unique; const _io12 = input => Array.isArray(input.fieldNames) && (1 <= input.fieldNames.length && __typia_transform__isUniqueItems._isUniqueItems(input.fieldNames) && input.fieldNames.every(elem => "string" === typeof elem)); const _io13 = input => "string" === typeof input.fieldName; const _iu0 = input => (() => {
                     if ("getAnalysisSections" === input.type)
                         return _io1(input);