@autobe/agent 0.5.0 → 0.5.2

package/lib/index.mjs

@@ -5177,7 +5177,7 @@ const collection$3 = {
 
 const transformPrismaCorrectHistories = result => [ {
     type: "systemMessage",
-    text: '# AutoBePrismaSyntax Validation Error Fixing Agent\n\nYou are a world-class Prisma schema validation and error resolution specialist working with structured AutoBePrismaSyntax definitions. Your primary mission is to analyze validation errors in IAutoBePrismaValidation.IFailure responses and provide precise fixes while maintaining complete schema integrity and business logic.\n\n## Core Operating Principles\n\n### 🚫 ABSOLUTE PROHIBITIONS\n- **NEVER ask for clarification** - analyze and fix validation errors directly\n- **NEVER remove or modify existing business logic** unless it causes validation errors\n- **NEVER delete model descriptions or field descriptions** unless removing duplicate elements\n- **NEVER create new duplicate fields, relations, or models**\n- **NEVER ignore validation errors** - every error must be addressed\n- **NEVER break existing relationships** unless they\'re causing validation errors\n- **NEVER change data types** unless specifically required by validation errors\n\n### ✅ MANDATORY REQUIREMENTS\n- **Fix ALL validation errors** listed in the IAutoBePrismaValidation.IFailure.errors array\n- **Preserve business intent** and architectural patterns from original schema\n- **Return complete AutoBePrismaSyntax.IApplication** structure with all fixes applied\n- **Maintain referential integrity** across all models and relationships\n- **Preserve ALL model and field descriptions** (except for removed duplicates)\n- **Keep original naming conventions** unless they cause validation errors\n\n## Error Analysis & Resolution Strategy\n\n### 1. Validation Error Processing\n\n#### Error Structure Analysis\n```typescript\ninterface IError {\n  path: string;      // File path where error occurs\n  table: string;     // Model name with the error\n  column: string | null; // Field name (null for model-level errors)\n  message: string;   // Detailed error description\n}\n```\n\n#### Error Categorization\n- **Model-level errors** (column: null): Duplicate models, invalid model names, missing primary keys\n- **Field-level errors** (column: string): Duplicate fields, invalid types, missing foreign keys\n- **Relationship errors**: Invalid references, missing target models, circular dependencies\n- **Index errors**: Invalid field references, duplicate indexes\n- **Cross-file errors**: References to non-existent models across files\n\n### 2. Common Validation Errors & Solutions\n\n#### Duplication Errors\n- **Duplicate model names across files**\n  - Rename one model with domain-specific prefix/suffix\n  - Update all references to renamed model in foreign keys and relations\n- **Duplicate field names within model**\n  - Remove or rename duplicate field (preserve most appropriate one)\n  - Update any references or indexes that use the renamed field\n- **Duplicate relation names within model**\n  - Rename conflicting relation with descriptive suffix\n  - Ensure relation names don\'t conflict with field names\n\n#### Reference Errors\n- **Invalid target model in foreign field**\n  - Update targetModel to correct existing model name\n  - Verify model exists in the specified file\n- **Invalid target field in foreign field**\n  - Usually should be "id" - update targetfield property\n- **Missing foreign key for relation**\n  - Add required foreign key field to foreignFields array\n  - Ensure field name matches relation configuration\n\n#### Type Validation Errors\n- **Invalid field type**\n  - Update to valid AutoBePrismaSyntax type (boolean, int, double, string, uri, uuid, date, datetime)\n- **Foreign key type mismatch**\n  - Ensure all foreign keys use "uuid" type\n- **Primary key issues**\n  - Ensure primaryField has type "uuid" and name "id"\n\n#### Index Validation Errors\n- **Invalid field names in indexes**\n  - Update fieldNames array to reference existing fields only\n  - Remove references to non-existent fields\n- **Single foreign key in indexes**\n  - Remove single foreign key fields from plainIndexes and uniqueIndexes\n  - Keep composite indexes that include foreign keys with other fields\n\n#### Naming Convention Errors\n- **Non-plural model names**\n  - Update model name to plural form\n  - Update all references in other models\' foreign keys and relations\n- **Invalid field naming**\n  - Update to snake_case convention\n  - Update any references in indexes\n\n### 3. Fix Implementation Strategy\n\n#### Error Processing Order\n1. **Model-level duplications** - Fix duplicate model names first\n2. **Field-level duplications** - Fix duplicate fields within models\n3. **Reference errors** - Fix invalid model/field references\n4. **Type validation** - Fix invalid data types\n5. **Index validation** - Fix invalid index configurations\n6. **Cross-validation** - Ensure all fixes maintain integrity\n\n#### Reference Update Process\nWhen renaming models or fields:\n1. **Update foreign key field names** in other models\n2. **Update targetModel references** in foreign field relations\n3. **Update index field references** that use renamed fields\n4. **Verify bidirectional relationships** remain consistent\n\n#### Business Logic Preservation\n- **Keep original field purposes** when fixing naming/type issues\n- **Maintain relationship semantics** when fixing reference errors\n- **Preserve data integrity constraints** when fixing index issues\n- **Keep audit trail patterns** (snapshots, timestamps) intact\n\n### 4. Validation Rules Compliance\n\n#### Model Validation\n- All model names must be plural and unique across all files\n- Each model must have exactly one primaryField with type "uuid" and name "id"\n- Materialized views must have material: true and name starting with "mv_"\n\n#### Field Validation\n- No duplicate field names within the same model\n- All foreign key fields must have type "uuid" and follow "{target_model}_id" pattern\n- All foreign fields must have corresponding relation configuration\n\n#### Relationship Validation\n- All targetModel references must point to existing models\n- All targetfield references should be "id" (primary key)\n- Relation names must be unique within each model\n- Relation names must not conflict with field names\n\n#### Index Validation\n- No single foreign key fields in plainIndexes or uniqueIndexes arrays\n- All fieldNames in indexes must reference existing fields in the model\n- Composite indexes can include foreign keys with other fields\n\n## Error Resolution Workflow\n\n### 1. Error Analysis Phase\n1. **Parse IAutoBePrismaValidation.IFailure** structure\n2. **Categorize errors by type** (duplication, reference, type, index, naming)\n3. **Group related errors** that might be fixed together\n4. **Plan fix sequence** to avoid creating new errors\n\n### 2. Fix Planning Phase\n1. **Identify models/fields to rename** for duplication resolution\n2. **Plan reference updates** for all affected elements\n3. **Determine minimal changes** needed for each error\n4. **Check for fix conflicts** that might create new errors\n\n### 3. Fix Implementation Phase\n1. **Apply duplication fixes** (renames, removals)\n2. **Update all references** to renamed elements\n3. **Fix type and validation errors**\n4. **Update indexes** to reference correct fields\n5. **Verify relationship integrity**\n\n### 4. Validation Phase\n1. **Check all errors are addressed**\n2. **Verify no new validation issues**\n3. **Confirm business logic preservation**\n4. **Validate cross-file reference integrity**\n\n## Input/Output Format\n\n### Input Structure\n```typescript\n{\n  success: false,\n  application: AutoBePrismaSyntax.IApplication,\n  errors: IError[]\n}\n```\n\n### Output Requirement\nReturn corrected AutoBePrismaSyntax.IApplication structure:\n```typescript\nconst fixedApplication: AutoBePrismaSyntax.IApplication = {\n  files: [\n    // All files with errors fixed\n    // Complete model definitions preserved\n    // All descriptions and business logic maintained\n  ]\n};\n```\n\n## Critical Success Criteria\n\n### ✅ Must Achieve\n- [ ] All validation errors from IError[] array resolved\n- [ ] Original business logic and purpose preserved\n- [ ] All model and field descriptions maintained (except removed duplicates)\n- [ ] No new duplicate models, fields, or relations created\n- [ ] All cross-file references remain valid\n- [ ] Referential integrity maintained across all relationships\n- [ ] Naming conventions properly applied (plural models, snake_case fields)\n- [ ] Index configurations comply with rules (no single foreign keys)\n- [ ] Return complete AutoBePrismaSyntax.IApplication structure\n\n### 🚫 Must Avoid\n- [ ] Ignoring any validation errors\n- [ ] Creating new duplications during fixes\n- [ ] Breaking existing business relationships\n- [ ] Removing necessary business logic\n- [ ] Making unnecessary changes beyond error fixes\n- [ ] Creating circular dependencies\n- [ ] Introducing type mismatches\n- [ ] Breaking cross-file reference integrity\n\n## Quality Assurance Process\n\n### Pre-Output Validation\n1. **Error Resolution Check**: Verify every error in the original IError[] array is addressed\n2. **Duplication Prevention**: Ensure no new duplicates are introduced\n3. **Reference Integrity**: Validate all foreign key references point to existing models/fields\n4. **Business Logic Preservation**: Confirm original intent and descriptions are maintained\n5. **Type Consistency**: Verify all types comply with AutoBePrismaSyntax requirements\n6. **Index Compliance**: Ensure index configurations follow the established rules\n\n### Response Validation Questions\n- Are all validation errors from the input resolved?\n- Do all model names follow plural naming convention?\n- Are all foreign key types "uuid" and properly referenced?\n- Do all indexes avoid single foreign key fields?\n- Are all cross-file model references valid?\n- Is the business logic from original descriptions preserved?\n\nRemember: Your goal is to be a precise validation error resolver, not a schema redesigner. Fix only what validation errors require, preserve all business intent, and maintain the integrity of the AutoBePrismaSyntax structure.'
+    text: '# `AutoBePrisma` Targeted Validation Error Fixing Agent\n\nYou are a world-class Prisma schema validation and error resolution specialist working with structured `AutoBePrisma` definitions. Your primary mission is to analyze validation errors in `IAutoBePrismaValidation.IFailure` responses and provide precise fixes for **ONLY the affected tables/models** while maintaining complete schema integrity and business logic.\n\n## Core Operating Principles\n\n### 🚫 ABSOLUTE PROHIBITIONS\n- **NEVER ask for clarification** - analyze and fix validation errors directly\n- **NEVER remove or modify existing business logic** unless it causes validation errors\n- **NEVER delete model descriptions or field descriptions** unless removing duplicate elements\n- **NEVER create new duplicate fields, relations, or models**\n- **NEVER ignore validation errors** - every error must be addressed\n- **NEVER break existing relationships** unless they\'re causing validation errors\n- **NEVER change data types** unless specifically required by validation errors\n- **🔴 CRITICAL: NEVER delete fields or relationships to avoid compilation errors**\n- **🔴 CRITICAL: Only delete elements when they are EXACT DUPLICATES of existing elements**\n- **🔴 CRITICAL: Always FIX errors by correction, not by removal (unless duplicate)**\n- **🔴 CRITICAL: NEVER modify tables/models that are not mentioned in validation errors**\n\n### ✅ MANDATORY REQUIREMENTS\n- **Fix ONLY validation errors** listed in the IAutoBePrismaValidation.IFailure.errors array\n- **Return ONLY the corrected models/tables** that had validation errors\n- **Preserve business intent** and architectural patterns from original schema\n- **Maintain referential integrity** with unchanged models\n- **Preserve ALL model and field descriptions** (except for removed duplicates)\n- **Keep original naming conventions** unless they cause validation errors\n- **🟢 PRIORITY: Correct errors through proper fixes, not deletions**\n- **🟢 PRIORITY: Maintain ALL business functionality and data structure**\n- **🟢 PRIORITY: Minimize output scope to only affected models**\n\n## Targeted Fix Strategy\n\n### 1. Error Scope Analysis\n\n#### Error Filtering Process\n```typescript\ninterface IError {\n  path: string;      // File path where error occurs\n  table: string;     // Model name with the error - TARGET FOR FIX\n  column: string | null; // Field name (null for model-level errors)\n  message: string;   // Detailed error description\n}\n```\n\n#### Affected Model Identification\n1. **Extract unique table names** from all errors in IError[] array\n2. **Group errors by table** for efficient processing\n3. **Identify cross-table dependencies** that need consideration\n4. **Focus ONLY on models mentioned in errors** - ignore all others\n5. **Track relationship impacts** on non-error models (for reference validation only)\n\n### 2. Targeted Error Resolution\n\n#### Model-Level Fixes (Scope: Single Model)\n- **Duplicate model names**: Rename affected model only\n- **Invalid model names**: Update naming convention for specific model\n- **Missing primary keys**: Add/fix primary key in affected model only\n- **Materialized view issues**: Fix material flag and naming for specific model\n\n#### Field-Level Fixes (Scope: Specific Fields in Error Models)\n- **Duplicate field names**: Fix only within the affected model\n- **Invalid field types**: Update types for specific fields only\n- **Missing foreign keys**: Add required foreign keys to affected model only\n- **Foreign key reference errors**: Fix references in affected model only\n\n#### Relationship Fixes (Scope: Affected Model Relations)\n- **Invalid target model references**: Update references in error model only\n- **Missing relation configurations**: Add/fix relations in affected model only\n- **Relation naming conflicts**: Resolve conflicts within affected model only\n\n#### Index Fixes (Scope: Affected Model Indexes)\n- **Invalid field references**: Fix index fieldNames in affected model only\n- **Single foreign key indexes**: Restructure indexes in affected model only\n- **Duplicate indexes**: Remove duplicates within affected model only\n\n### 3. Cross-Model Impact Analysis\n\n#### Reference Validation (Read-Only for Non-Error Models)\n- **Verify target model existence** for foreign key references\n- **Check target field validity** (usually "id" primary key)\n- **Validate bidirectional relationship consistency**\n- **Ensure renamed model references are updated** in other models\n\n#### Dependency Tracking\n- **Identify models that reference** the corrected models\n- **Note potential cascade effects** of model/field renaming\n- **Flag models that may need reference updates** (for external handling)\n- **Maintain awareness of schema-wide implications**\n\n### 4. Minimal Output Strategy\n\n#### Output Scope Determination\n**Include in output ONLY:**\n1. **Models explicitly mentioned in validation errors**\n2. **Models with fields that reference renamed models** (if any)\n3. **Models that require relationship updates** due to fixes\n\n**Exclude from output:**\n1. **Models with no validation errors**\n2. **Models not affected by fixes**\n3. **Models that maintain valid references to corrected models**\n\n#### Fix Documentation\nFor each corrected model, provide:\n- **Original error description**\n- **Applied fix explanation**\n- **Impact on other models** (reference updates needed)\n- **Business logic preservation confirmation**\n\n## Error Resolution Workflow\n\n### 1. Error Parsing & Scope Definition\n1. **Parse IAutoBePrismaValidation.IFailure** structure\n2. **Extract unique table names** from error array\n3. **Group errors by affected model** for batch processing\n4. **Identify minimal fix scope** - only what\'s necessary\n5. **Plan cross-model reference updates** (if needed)\n\n### 2. Targeted Fix Planning\n1. **Analyze each error model individually**\n2. **Plan fixes for each affected model**\n3. **Check for inter-model dependency impacts**\n4. **Determine minimal output scope**\n5. **Validate fix feasibility without breaking references**\n\n### 3. Precision Fix Implementation\n1. **Apply fixes ONLY to error models**\n2. **Update cross-references ONLY if needed**\n3. **Preserve all unchanged model integrity**\n4. **Maintain business logic in fixed models**\n5. **Verify minimal scope compliance**\n\n### 4. Output Validation\n1. **Confirm all errors are addressed** in affected models\n2. **Verify no new validation issues** in fixed models\n3. **Check reference integrity** with unchanged models\n4. **Validate business logic preservation** in corrected models\n5. **Ensure minimal output scope** - no unnecessary models included\n\n## Input/Output Format\n\n### Input Structure\n```typescript\n{\n  success: false,\n  application: AutoBePrisma.IApplication, // Full schema for reference\n  errors: IError[] // Target models for fixing\n}\n```\n\n### Output Requirement\nReturn ONLY corrected models that had validation errors:\n```typescript\nconst correctedModels: AutoBePrisma.IModel[] = [\n  // ONLY models mentioned in IError[] array\n  // ONLY models affected by cross-reference updates\n  // All other models are preserved unchanged\n];\n\n// Include metadata about the fix scope\nconst fixSummary = {\n  correctedModels: string[], // Names of models that were fixed\n  crossReferenceUpdates: string[], // Models that needed reference updates\n  preservedModels: string[], // Models that remain unchanged\n  errorsCorrected: number // Count of resolved errors\n};\n```\n\n## Targeted Correction Examples\n\n### Example 1: Single Model Duplicate Field Error\n**Input Error:**\n```typescript\n{\n  path: "users.prisma",\n  table: "users",\n  column: "email",\n  message: "Duplicate field \'email\' in model \'users\'"\n}\n```\n\n**Output:** Only the `users` model with the duplicate field resolved\n- **Scope:** 1 model\n- **Change:** Rename one `email` field to `email_secondary` or merge if identical\n- **Excluded:** All other models remain unchanged\n\n### Example 2: Cross-Model Reference Error\n**Input Error:**\n```typescript\n{\n  path: "orders.prisma",\n  table: "orders",\n  column: "user_id",\n  message: "Invalid target model \'user\' for foreign key \'user_id\'"\n}\n```\n\n**Output:** Only the `orders` model with corrected reference\n- **Scope:** 1 model (orders)\n- **Change:** Update `targetModel` from "user" to "users"\n- **Excluded:** The `users` model remains unchanged (just referenced correctly)\n\n### Example 3: Model Name Duplication Across Files\n**Input Errors:**\n```typescript\n[\n  {\n    path: "auth/users.prisma",\n    table: "users",\n    column: null,\n    message: "Duplicate model name \'users\'"\n  },\n  {\n    path: "admin/users.prisma",\n    table: "users",\n    column: null,\n    message: "Duplicate model name \'users\'"\n  }\n]\n```\n\n**Output:** Both affected `users` models with one renamed\n- **Scope:** 2 models\n- **Change:** Rename one to `admin_users`, update all its references\n- **Excluded:** All other models that don\'t reference the renamed model\n\n## Critical Success Criteria\n\n### ✅ Must Achieve (Targeted Scope)\n- [ ] All validation errors resolved **for mentioned models only**\n- [ ] Original business logic preserved **in corrected models**\n- [ ] Cross-model references remain valid **through minimal updates**\n- [ ] Output contains **ONLY affected models** - no unnecessary inclusions\n- [ ] Referential integrity maintained **with unchanged models**\n- [ ] **🔴 MINIMAL SCOPE: Only error models + necessary reference updates**\n- [ ] **🔴 UNCHANGED MODELS: Preserved completely in original schema**\n\n### 🚫 Must Avoid (Scope Violations)\n- [ ] Including models without validation errors in output\n- [ ] Modifying models not mentioned in error array\n- [ ] Returning entire schema when only partial fixes needed\n- [ ] Making unnecessary changes beyond error resolution\n- [ ] Breaking references to unchanged models\n- [ ] **🔴 SCOPE CREEP: Fixing models that don\'t have errors**\n- [ ] **🔴 OUTPUT BLOAT: Including unchanged models in response**\n\n## Quality Assurance Process\n\n### Pre-Output Scope Validation\n1. **Error Coverage Check**: Every error in IError[] array addressed **in minimal scope**\n2. **Output Scope Audit**: Only affected models included in response\n3. **Reference Integrity**: Unchanged models maintain valid references\n4. **Business Logic Preservation**: Corrected models maintain original intent\n5. **Cross-Model Impact**: Necessary reference updates identified and applied\n6. ****🔴 Minimal Output Verification**: No unnecessary models in response**\n7. **🔴 Unchanged Model Preservation**: Non-error models completely preserved**\n\n### Targeted Response Validation Questions\n- Are all validation errors resolved **with minimal model changes**?\n- Does the output include **ONLY models that had errors** or needed reference updates?\n- Are **unchanged models completely preserved** in the original schema?\n- Do **cross-model references remain valid** after targeted fixes?\n- Is the **business logic maintained** in all corrected models?\n- **🔴 Is the output scope minimized** to only necessary corrections?\n- **🔴 Are non-error models excluded** from the response?\n\n## 🎯 CORE PRINCIPLE REMINDER\n\n**Your role is TARGETED ERROR CORRECTOR, not SCHEMA RECONSTRUCTOR**\n\n- Fix **ONLY the models with validation errors**\n- Preserve **ALL unchanged models** in their original state\n- Return **MINIMAL output scope** - only what was corrected\n- Maintain **referential integrity** with unchanged models\n- **Focus on precision fixes, not comprehensive rebuilds**\n\nRemember: Your goal is to be a surgical validation error resolver, fixing only what\'s broken while preserving the integrity of the unchanged schema components. **Minimize context usage by returning only the corrected models, not the entire schema.**'
 }, {
     type: "assistantMessage",
     text: [ "Here is the Prisma application data what you made:", "", "```json", JSON.stringify(result.data), "```" ].join("\n")
@@ -5190,6 +5190,13 @@ const transformPrismaCorrectHistories = result => [ {
 } ];
 
 function orchestratePrismaCorrect(ctx, application, retry = 8) {
+    const unique = new Set;
+    for (const file of application.files) file.models = file.models.filter((model => {
+        if (unique.has(model.name)) return false;
+        unique.add(model.name);
+        return true;
+    }));
+    application.files = application.files.filter((f => f.models.length !== 0));
     return step(ctx, application);
 }
 
@@ -5235,18 +5242,26 @@ async function step(ctx, application, life) {
         console.error("Unreachable error: PrismaCompilerAgent.pointer.value is null");
         return result;
     }
+    const correction = {
+        files: application.files.map((file => ({
+            filename: file.filename,
+            namespace: file.namespace,
+            models: file.models.map((model => {
+                const newbie = pointer.value.models.find((m => m.name === model.name));
+                return newbie ?? model;
+            }))
+        })))
+    };
     ctx.dispatch({
         type: "prismaCorrect",
         failure: result,
-        correction: {
-            files: pointer.value.files
-        },
+        correction,
         planning: pointer.value.planning,
         step: ctx.state().analyze?.step ?? 0,
         created_at: (new Date).toISOString()
     });
     return step(ctx, {
-        files: pointer.value.files
+        files: correction.files
     });
 }
 
@@ -5278,310 +5293,256 @@ const claude$2 = {
             type: "object",
             properties: {
                 planning: {
-                    title: "Detailed execution plan for fixing AutoBePrisma validation errors",
-                    description: "Detailed execution plan for fixing AutoBePrisma validation errors.\n\n🎯 Purpose: Enable systematic reasoning and step-by-step error resolution\napproach for structured schema validation issues\n\n📋 Required Planning Content:\n\n1. **Error Analysis Summary**\n\n   - List all validation errors from IAutoBePrismaValidation.IError[] array\n   - Categorize errors by type (duplications, references, types, indexes)\n   - Identify root causes and error interdependencies\n2. **Fix Strategy Overview**\n\n   - Prioritize fixes based on dependencies (fix duplications first)\n   - Outline minimal changes needed for each validation error\n   - Identify potential impact on other models/relationships\n3. **Step-by-Step Fix Plan**\n\n   - Model-by-model modification plan with specific changes\n   - Exact field additions, removals, or renames required\n   - Reference updates needed for renamed elements\n   - Index corrections to comply with validation rules\n4. **Preservation Checklist**\n\n   - Confirm which descriptions and business logic must be preserved\n   - List relationships and constraints to maintain unchanged\n   - Identify cross-model dependencies that must remain intact\n5. **Risk Assessment**\n\n   - Potential side effects of each planned fix\n   - Validation points to check after applying corrections\n   - Ensure no new validation errors are introduced\n\n💡 Example Planning Structure:\n\n    ## Error Analysis\n    - Error 1: Duplicate field 'name' in shopping_customers model\n    - Error 2: Invalid targetModel 'shopping_customer' should be 'shopping_customers'\n\n    ## Fix Strategy\n    1. Remove duplicate 'name' field (keep the more detailed one)\n    2. Update foreign key references to use correct plural model name\n\n    ## Detailed Steps\n    1. shopping_customers model: Remove second 'name' field from plainFields\n    2. shopping_orders model: Update targetModel from 'shopping_customer' to 'shopping_customers'\n\n    ## Preservation Notes\n    - Keep business descriptions for remaining 'name' field\n    - Maintain all relationship semantics\n    - Preserve all indexes and constraints",
+                    description: "Detailed execution plan for fixing `AutoBePrisma` validation errors in\nspecific models.\n\n🎯 Purpose: Enable systematic reasoning and step-by-step error resolution\napproach for targeted model validation issues\n\n📋 Required Planning Content:\n\n1. **Error Scope Analysis**\n\n   - List all validation errors from IAutoBePrismaValidation.IError[] array\n   - Extract unique table names from errors to identify affected models\n   - Categorize errors by type (field duplications, references, types, indexes)\n   - Identify which models need correction vs. which 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 (if any) without modifying non-error\n        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\n\n💡 Example Planning Structure:\n\n    ## Error Scope\n    - Target Models: shopping_customers, shopping_orders (2 models only)\n    - Unchanged Models: All others remain in original schema\n\n    ## Targeted Fixes\n    - shopping_customers: Remove duplicate 'email' field\n    - shopping_orders: Update targetModel reference to 'shopping_customers'\n\n    ## Output Scope\n    - Return: Only shopping_customers and shopping_orders models\n    - Preserve: All other models unchanged in original schema\n\n    ## Cross-Model Impact\n    - Verify: shopping_orders still references shopping_customers correctly\n    - No changes needed in other models referencing these",
                     type: "string"
                 },
-                files: {
-                    description: "Original AutoBePrisma.IApplication structure that contains validation\nerrors and needs correction.\n\n📥 Input Structure:\n\n- Complete IApplication with files array containing validation errors\n- Each file contains models with potential structural issues\n- Errors may include duplications, invalid references, or constraint\n  violations\n\n🔍 Expected Validation Issues:\n\n- Duplicate model names across files\n- Duplicate field/relation names within models\n- Invalid foreign key references to non-existent models\n- Single foreign key fields in index arrays\n- Non-plural model names or invalid naming conventions\n\n📝 Application Content Analysis:\n\n- All models with their complete field definitions\n- All relationships with targetModel and targetfield configurations\n- All indexes (unique, plain, GIN) with field references\n- All business descriptions and requirement mappings\n- Cross-file model references and dependencies\n\n⚠️ Processing Notes:\n\n- Structure may contain validation errors that prevent code generation\n- Some models might reference non-existent targets\n- Field names might violate naming conventions\n- Index configurations might include forbidden single foreign keys\n- Business logic and descriptions must be preserved during fixes",
+                models: {
+                    description: "ONLY the specific models that contain validation errors and need\ncorrection.\n\n📥 Input Structure:\n\n- Contains ONLY models mentioned in IAutoBePrismaValidation.IError[] array\n- Each model has specific validation errors that need targeted correction\n- Models not mentioned in errors are excluded from this input\n- Represents minimal scope for error correction\n\n🔍 Expected Validation Issues (Model-Specific):\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\n📝 Model Content Analysis (Targeted Scope):\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\n⚠️ Processing Notes (Focused Approach):\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\n\n🎯 Correction Scope:\n\n- Fix validation errors within these specific models\n- Update internal model structure (fields, relations, indexes)\n- Correct references to external models (without modifying targets)\n- Maintain compatibility with unchanged models in the full schema\n- Return corrected versions of ONLY these models",
                     type: "array",
                     items: {
-                        description: "Description of the current {@link AutoBePrisma.IFile} type:\n\n> Interface representing a single Prisma schema file within the application.\n> \n> Each file focuses on a specific business domain and contains related\n> models. File organization follows domain-driven design principles as seen\n> in the uploaded schemas.",
+                        description: "Description of the current {@link AutoBePrisma.IModel} type:\n\n> Interface representing a single Prisma model (database table).\n> \n> Based 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_)",
                         type: "object",
                         properties: {
-                            filename: {
-                                title: "Name of the schema file to be generated",
-                                description: 'Name of the schema file to be generated.\n\nShould follow the naming convention: "schema-{number}-{domain}.prisma"\nExamples: "schema-02-systematic.prisma", "schema-03-actors.prisma" The\nnumber indicates the dependency order for schema generation.',
+                            name: {
+                                title: "Name of the Prisma model (database table name)",
+                                description: 'Name of the Prisma model (database table name).\n\nShould follow snake_case convention with domain prefix. Examples:\n"shopping_customers", "shopping_sale_snapshots", "bbs_articles"\nMaterialized views use "mv_" prefix: "mv_shopping_sale_last_snapshots"',
                                 type: "string",
-                                pattern: "^[a-zA-Z0-9._-]+\\.prisma$"
+                                pattern: "^[a-z][a-z0-9_]*$"
                             },
-                            namespace: {
-                                title: "Business domain namespace that groups related models",
-                                description: 'Business domain namespace that groups related models.\n\nUsed in Prisma documentation comments as "@\\namespace directive".\nExamples from uploaded schemas: "Systematic", "Actors", "Sales", "Carts",\n"Orders", "Coupons", "Coins", "Inquiries", "Favorites", "Articles"',
+                            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 Example:\n  "Customer information, but not a person but a **connection** basis..."',
                                 type: "string"
                             },
-                            models: {
-                                title: "Array of Prisma models (database tables) within this domain",
-                                description: "Array of Prisma models (database tables) within this domain.\n\nEach model represents a business entity or concept within the namespace.\nModels can reference each other through foreign key relationships.",
+                            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',
+                                type: "boolean"
+                            },
+                            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.\n\n------------------------------\n\nDescription of the current {@link AutoBePrisma.IPrimaryField} type:\n\n> Interface representing the primary key field of a Prisma model.\n> \n> All models in the uploaded schemas use UUID as primary key for better\n> distributed system compatibility and security (no sequential ID exposure).',
+                                type: "object",
+                                properties: {
+                                    name: {
+                                        title: "Name of the primary key field",
+                                        description: 'Name of the primary key field.\n\nConsistently named "id" across all models in the uploaded schemas.\nRepresents the unique identifier for each record in the table.',
+                                        type: "string",
+                                        pattern: "^[a-z][a-z0-9_]*$"
+                                    },
+                                    type: {
+                                        title: "Data type of the primary key field",
+                                        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: {
+                                        title: "Description of the primary key field's purpose",
+                                        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.',
+                                        type: "string"
+                                    }
+                                },
+                                required: [ "name", "type", "description" ]
+                            },
+                            foreignFields: {
+                                title: "Array of foreign key fields that reference other models",
+                                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.",
                                 type: "array",
                                 items: {
-                                    description: "Description of the current {@link AutoBePrisma.IModel} type:\n\n> Interface representing a single Prisma model (database table).\n> \n> Based 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: "Description of the current {@link AutoBePrisma.IForeignField} type:\n\n> Interface representing a foreign key field that establishes relationships\n> between models.\n> \n> Foreign keys create associations between models, enabling relational data\n> modeling. They can represent 1:1, 1:N, or participate in M:N relationships\n> through junction tables.",
                                     type: "object",
                                     properties: {
                                         name: {
-                                            title: "Name of the Prisma model (database table name)",
-                                            description: 'Name of the Prisma model (database table name).\n\nShould follow snake_case convention with domain prefix. Examples:\n"shopping_customers", "shopping_sale_snapshots", "bbs_articles"\nMaterialized views use "mv_" prefix: "mv_shopping_sale_last_snapshots"',
+                                            title: "Name of the foreign key field",
+                                            description: 'Name of the foreign key field.\n\nFollows convention: "{target_model_name_without_prefix}_id" Examples:\n"shopping_customer_id", "bbs_article_id", "attachment_file_id" For\nself-references: "parent_id" (e.g., in hierarchical structures)',
                                             type: "string",
                                             pattern: "^[a-z][a-z0-9_]*$"
                                         },
+                                        type: {
+                                            title: "Data type of the foreign key field",
+                                            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: {
-                                            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 Example:\n  "Customer information, but not a person but a **connection** basis..."',
+                                            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.',
                                             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',
-                                            type: "boolean"
-                                        },
-                                        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.\n\n------------------------------\n\nDescription of the current {@link AutoBePrisma.IPrimaryField} type:\n\n> Interface representing the primary key field of a Prisma model.\n> \n> All models in the uploaded schemas use UUID as primary key for better\n> distributed system compatibility and security (no sequential ID exposure).',
+                                        relation: {
+                                            title: "Prisma relation configuration defining the association details",
+                                            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.",
                                             type: "object",
                                             properties: {
                                                 name: {
-                                                    title: "Name of the primary key field",
-                                                    description: 'Name of the primary key field.\n\nConsistently named "id" across all models in the uploaded schemas.\nRepresents the unique identifier for each record in the table.',
+                                                    title: "Name of the relation property in the Prisma model",
+                                                    description: 'Name of the relation property in the Prisma model.\n\nUsed to access the related model instance. Usually a descriptive name\nof the relationship. Examples: "customer", "channel", "parent",\n"snapshot"',
                                                     type: "string",
-                                                    pattern: "^[a-z][a-z0-9_]*$"
+                                                    pattern: "^[a-zA-Z_][a-zA-Z0-9_]*$"
                                                 },
-                                                type: {
-                                                    title: "Data type of the primary key field",
-                                                    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: {
-                                                    title: "Description of the primary key field's purpose",
-                                                    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.',
+                                                targetModel: {
+                                                    title: "Name of the target model being referenced",
+                                                    description: 'Name of the target model being referenced.\n\nMust match exactly with an existing model name in the schema. Examples:\n"shopping_customers", "shopping_channels", "bbs_articles"',
                                                     type: "string"
                                                 }
                                             },
-                                            required: [ "name", "type", "description" ]
+                                            required: [ "name", "targetModel" ]
                                         },
-                                        foreignFields: {
-                                            title: "Array of foreign key fields that reference other models",
-                                            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.",
-                                            type: "array",
-                                            items: {
-                                                description: "Description of the current {@link AutoBePrisma.IForeignField} type:\n\n> Interface representing a foreign key field that establishes relationships\n> between models.\n> \n> Foreign keys create associations between models, enabling relational data\n> modeling. They can represent 1:1, 1:N, or participate in M:N relationships\n> through junction tables.",
-                                                type: "object",
-                                                properties: {
-                                                    name: {
-                                                        title: "Name of the foreign key field",
-                                                        description: 'Name of the foreign key field.\n\nFollows convention: "{target_model_name_without_prefix}_id" Examples:\n"shopping_customer_id", "bbs_article_id", "attachment_file_id" For\nself-references: "parent_id" (e.g., in hierarchical structures)',
-                                                        type: "string",
-                                                        pattern: "^[a-z][a-z0-9_]*$"
-                                                    },
-                                                    type: {
-                                                        title: "Data type of the foreign key field",
-                                                        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: {
-                                                        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.',
-                                                        type: "string"
-                                                    },
-                                                    relation: {
-                                                        title: "Prisma relation configuration defining the association details",
-                                                        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.",
-                                                        type: "object",
-                                                        properties: {
-                                                            name: {
-                                                                title: "Name of the relation property in the Prisma model",
-                                                                description: 'Name of the relation property in the Prisma model.\n\nUsed to access the related model instance. Usually a descriptive name\nof the relationship. Examples: "customer", "channel", "parent",\n"snapshot"',
-                                                                type: "string",
-                                                                pattern: "^[a-zA-Z_][a-zA-Z0-9_]*$"
-                                                            },
-                                                            targetModel: {
-                                                                title: "Name of the target model being referenced",
-                                                                description: 'Name of the target model being referenced.\n\nMust match exactly with an existing model name in the schema. Examples:\n"shopping_customers", "shopping_channels", "bbs_articles"',
-                                                                type: "string"
-                                                            }
-                                                        },
-                                                        required: [ "name", "targetModel" ]
-                                                    },
-                                                    unique: {
-                                                        title: "Whether this foreign key has a unique constraint",
-                                                        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.",
-                                                        type: "boolean"
-                                                    },
-                                                    nullable: {
-                                                        title: "Whether this foreign key can be null (optional relationship)",
-                                                        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.",
-                                                        type: "boolean"
-                                                    }
-                                                },
-                                                required: [ "name", "type", "description", "relation", "unique", "nullable" ]
-                                            }
+                                        unique: {
+                                            title: "Whether this foreign key has a unique constraint",
+                                            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.",
+                                            type: "boolean"
                                         },
-                                        plainFields: {
-                                            title: "Array of regular data fields that don't reference other models",
-                                            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.",
-                                            type: "array",
-                                            items: {
-                                                description: "Description of the current {@link AutoBePrisma.IPlainField} type:\n\n> Interface representing a regular data field that stores business\n> information.\n> \n> These fields contain the actual business data like names, amounts,\n> timestamps, flags, descriptions, and other domain-specific information.",
-                                                type: "object",
-                                                properties: {
-                                                    name: {
-                                                        title: "Name of the field in the database table",
-                                                        description: "Name of the field in the database table.\n\nShould use snake_case convention. Common patterns from uploaded schemas:\n\n- Timestamps: created_at, updated_at, deleted_at, opened_at, closed_at\n- Identifiers: code, name, nickname, title\n- Business data: value, quantity, price, volume, balance\n- Flags: primary, required, exclusive, secret, multiplicative",
-                                                        type: "string",
-                                                        pattern: "^[a-z][a-z0-9_]*$"
-                                                    },
-                                                    type: {
-                                                        title: "Data type of the field for Prisma schema generation",
-                                                        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- Date: Date-only values (rare, mostly for business dates)\n- Datetime: Timestamp fields with date and time",
-                                                        oneOf: [ {
-                                                            const: "string"
-                                                        }, {
-                                                            const: "boolean"
-                                                        }, {
-                                                            const: "uuid"
-                                                        }, {
-                                                            const: "uri"
-                                                        }, {
-                                                            const: "int"
-                                                        }, {
-                                                            const: "double"
-                                                        }, {
-                                                            const: "datetime"
-                                                        } ]
-                                                    },
-                                                    description: {
-                                                        title: "Description explaining the business purpose and usage of this field",
-                                                        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 Example: "Amount of cash payment." or\n  "Whether the unit is required or not."',
-                                                        type: "string"
-                                                    },
-                                                    nullable: {
-                                                        title: "Whether this field can contain null values",
-                                                        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.",
-                                                        type: "boolean"
-                                                    }
-                                                },
-                                                required: [ "name", "type", "description", "nullable" ]
-                                            }
+                                        nullable: {
+                                            title: "Whether this foreign key can be null (optional relationship)",
+                                            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.",
+                                            type: "boolean"
+                                        }
+                                    },
+                                    required: [ "name", "type", "description", "relation", "unique", "nullable" ]
+                                }
+                            },
+                            plainFields: {
+                                title: "Array of regular data fields that don't reference other models",
+                                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.",
+                                type: "array",
+                                items: {
+                                    description: "Description of the current {@link AutoBePrisma.IPlainField} type:\n\n> Interface representing a regular data field that stores business\n> information.\n> \n> These fields contain the actual business data like names, amounts,\n> timestamps, flags, descriptions, and other domain-specific information.",
+                                    type: "object",
+                                    properties: {
+                                        name: {
+                                            title: "Name of the field in the database table",
+                                            description: "Name of the field in the database table.\n\nShould use snake_case convention. Common patterns from uploaded schemas:\n\n- Timestamps: created_at, updated_at, deleted_at, opened_at, closed_at\n- Identifiers: code, name, nickname, title\n- Business data: value, quantity, price, volume, balance\n- Flags: primary, required, exclusive, secret, multiplicative",
+                                            type: "string",
+                                            pattern: "^[a-z][a-z0-9_]*$"
                                         },
-                                        uniqueIndexes: {
-                                            title: "Array of unique indexes for enforcing data integrity constraints",
-                                            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).",
-                                            type: "array",
-                                            items: {
-                                                description: "Description of the current {@link AutoBePrisma.IUniqueIndex} type:\n\n> Interface representing a unique index constraint on one or more fields.\n> \n> Unique indexes enforce data integrity by ensuring no duplicate values exist\n> for the specified field combination. Essential for business rules that\n> require uniqueness like email addresses, codes, or composite keys.",
-                                                type: "object",
-                                                properties: {
-                                                    fieldNames: {
-                                                        title: "Array of field names that together form the unique constraint",
-                                                        description: 'Array of field names that together form the unique constraint.\n\nCan be single field (e.g., ["email"]) or composite (e.g., ["channel_id",\n"code"]). All field names must exist in the model. Order matters for\ncomposite indexes. Examples: ["code"], ["shopping_channel_id",\n"nickname"], ["email"]',
-                                                        type: "array",
-                                                        items: {
-                                                            type: "string"
-                                                        },
-                                                        minItems: 1,
-                                                        uniqueItems: true
-                                                    },
-                                                    unique: {
-                                                        title: "Explicit marker indicating this is a unique index",
-                                                        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".',
-                                                        const: true
-                                                    }
-                                                },
-                                                required: [ "fieldNames", "unique" ]
-                                            }
+                                        type: {
+                                            title: "Data type of the field for Prisma schema generation",
+                                            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- Date: Date-only values (rare, mostly for business dates)\n- Datetime: Timestamp fields with date and time",
+                                            oneOf: [ {
+                                                const: "string"
+                                            }, {
+                                                const: "boolean"
+                                            }, {
+                                                const: "uuid"
+                                            }, {
+                                                const: "uri"
+                                            }, {
+                                                const: "int"
+                                            }, {
+                                                const: "double"
+                                            }, {
+                                                const: "datetime"
+                                            } ]
                                         },
-                                        plainIndexes: {
-                                            title: "Array of regular indexes for query performance optimization",
-                                            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: {
+                                            title: "Description explaining the business purpose and usage of this field",
+                                            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 Example: "Amount of cash payment." or\n  "Whether the unit is required or not."',
+                                            type: "string"
+                                        },
+                                        nullable: {
+                                            title: "Whether this field can contain null values",
+                                            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.",
+                                            type: "boolean"
+                                        }
+                                    },
+                                    required: [ "name", "type", "description", "nullable" ]
+                                }
+                            },
+                            uniqueIndexes: {
+                                title: "Array of unique indexes for enforcing data integrity constraints",
+                                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).",
+                                type: "array",
+                                items: {
+                                    description: "Description of the current {@link AutoBePrisma.IUniqueIndex} type:\n\n> Interface representing a unique index constraint on one or more fields.\n> \n> Unique indexes enforce data integrity by ensuring no duplicate values exist\n> for the specified field combination. Essential for business rules that\n> require uniqueness like email addresses, codes, or composite keys.",
+                                    type: "object",
+                                    properties: {
+                                        fieldNames: {
+                                            title: "Array of field names that together form the unique constraint",
+                                            description: 'Array of field names that together form the unique constraint.\n\nCan be single field (e.g., ["email"]) or composite (e.g., ["channel_id",\n"code"]). All field names must exist in the model. Order matters for\ncomposite indexes. Examples: ["code"], ["shopping_channel_id",\n"nickname"], ["email"]',
                                             type: "array",
                                             items: {
-                                                description: "Description of the current {@link AutoBePrisma.IPlainIndex} type:\n\n> Interface representing a regular (non-unique) index for query performance.\n> \n> Regular indexes speed up database queries by creating optimized data\n> structures for common search patterns. Essential for foreign keys, date\n> ranges, and frequently filtered fields.",
-                                                type: "object",
-                                                properties: {
-                                                    fieldNames: {
-                                                        title: "Array of field names to include in the performance index",
-                                                        description: 'Array of field names to include in the performance index.\n\nCan be single field (e.g., ["created_at"]) or composite (e.g.,\n["customer_id", "created_at"]). All field names must exist in the model.\nOrder matters for composite indexes and should match common query\npatterns. Examples: ["created_at"], ["shopping_customer_id",\n"created_at"], ["ip"]',
-                                                        type: "array",
-                                                        items: {
-                                                            type: "string"
-                                                        },
-                                                        minItems: 1,
-                                                        uniqueItems: true
-                                                    }
-                                                },
-                                                required: [ "fieldNames" ]
-                                            }
+                                                type: "string"
+                                            },
+                                            minItems: 1,
+                                            uniqueItems: true
                                         },
-                                        ginIndexes: {
-                                            title: "Array of GIN (Generalized Inverted Index) indexes for full-text search",
-                                            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.",
+                                        unique: {
+                                            title: "Explicit marker indicating this is a unique index",
+                                            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".',
+                                            const: true
+                                        }
+                                    },
+                                    required: [ "fieldNames", "unique" ]
+                                }
+                            },
+                            plainIndexes: {
+                                title: "Array of regular indexes for query performance optimization",
+                                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.",
+                                type: "array",
+                                items: {
+                                    description: "Description of the current {@link AutoBePrisma.IPlainIndex} type:\n\n> Interface representing a regular (non-unique) index for query performance.\n> \n> Regular indexes speed up database queries by creating optimized data\n> structures for common search patterns. Essential for foreign keys, date\n> ranges, and frequently filtered fields.",
+                                    type: "object",
+                                    properties: {
+                                        fieldNames: {
+                                            title: "Array of field names to include in the performance index",
+                                            description: 'Array of field names to include in the performance index.\n\nCan be single field (e.g., ["created_at"]) or composite (e.g.,\n["customer_id", "created_at"]). All field names must exist in the model.\nOrder matters for composite indexes and should match common query\npatterns. Examples: ["created_at"], ["shopping_customer_id",\n"created_at"], ["ip"]',
                                             type: "array",
                                             items: {
-                                                description: "Description of the current {@link AutoBePrisma.IGinIndex} type:\n\n> Interface representing a GIN (Generalized Inverted Index) for full-text\n> search.\n> \n> GIN indexes enable advanced PostgreSQL text search capabilities including\n> fuzzy matching and partial text search using trigram operations. Essential\n> for user-facing search features on text content.",
-                                                type: "object",
-                                                properties: {
-                                                    fieldName: {
-                                                        title: "Name of the text field to index for full-text search capabilities",
-                                                        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.',
-                                                        type: "string"
-                                                    }
-                                                },
-                                                required: [ "fieldName" ]
-                                            }
+                                                type: "string"
+                                            },
+                                            minItems: 1,
+                                            uniqueItems: true
                                         }
                                     },
-                                    required: [ "name", "description", "material", "primaryField", "foreignFields", "plainFields", "uniqueIndexes", "plainIndexes", "ginIndexes" ]
+                                    required: [ "fieldNames" ]
+                                }
+                            },
+                            ginIndexes: {
+                                title: "Array of GIN (Generalized Inverted Index) indexes for full-text search",
+                                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.",
+                                type: "array",
+                                items: {
+                                    description: "Description of the current {@link AutoBePrisma.IGinIndex} type:\n\n> Interface representing a GIN (Generalized Inverted Index) for full-text\n> search.\n> \n> GIN indexes enable advanced PostgreSQL text search capabilities including\n> fuzzy matching and partial text search using trigram operations. Essential\n> for user-facing search features on text content.",
+                                    type: "object",
+                                    properties: {
+                                        fieldName: {
+                                            title: "Name of the text field to index for full-text search capabilities",
+                                            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.',
+                                            type: "string"
+                                        }
+                                    },
+                                    required: [ "fieldName" ]
                                 }
                             }
                         },
-                        required: [ "filename", "namespace", "models" ]
+                        required: [ "name", "description", "material", "primaryField", "foreignFields", "plainFields", "uniqueIndexes", "plainIndexes", "ginIndexes" ]
                     }
                 }
             },
-            required: [ "planning", "files" ],
+            required: [ "planning", "models" ],
             additionalProperties: false,
             $defs: {}
         },
-        description: "Fixes validation errors in AutoBePrisma.IApplication structure while\npreserving ALL existing business logic and model descriptions.\n\n## Core Rules\n\n1. Fix ONLY validation errors - never remove business descriptions\n2. Apply minimal changes - preserve original design intent\n3. Return COMPLETE corrected structure - no data loss allowed\n4. Maintain referential integrity across all models\n\n## Preservation Requirements\n\n- Keep ALL model and field descriptions\n- Keep business logic and architectural patterns\n- Maintain relationship semantics and cardinality\n- Remove descriptions only when removing duplicate elements\n\n## Fix Strategy\n\n- Resolve structural validation errors without changing business intent\n- Remove duplicate fields/relations while preserving most appropriate ones\n- Fix invalid references and type mismatches\n- Ensure naming conventions and index rules compliance",
+        description: "Fixes validation errors in specific AutoBePrisma models while preserving\nALL existing business logic and model descriptions.\n\n## Core Rules\n\n1. Fix ONLY validation errors in provided models - never remove business\n   descriptions\n2. Apply minimal changes to error models only - preserve original design\n   intent\n3. Return ONLY corrected models - unchanged models remain in original schema\n4. Maintain referential integrity with unchanged models\n\n## Targeted Scope\n\n- Process ONLY models with validation errors from IError[] array\n- Exclude models without errors from processing and output\n- Minimize context usage by returning corrected models only\n- Preserve unchanged models in their original state\n\n## Fix Strategy\n\n- Resolve validation errors within specific models only\n- Fix field duplications, invalid references, and type mismatches\n- Update cross-model references without modifying target models\n- Ensure naming conventions and index rules compliance in corrected models",
         validate: (() => {
-            const _io0 = input => "string" === typeof input.planning && (Array.isArray(input.files) && input.files.every((elem => "object" === typeof elem && null !== elem && _io1(elem))));
-            const _io1 = input => "string" === typeof input.filename && RegExp("^[a-zA-Z0-9._-]+\\.prisma$").test(input.filename) && "string" === typeof input.namespace && (Array.isArray(input.models) && input.models.every((elem => "object" === typeof elem && null !== elem && _io2(elem))));
-            const _io2 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "string" === typeof input.description && "boolean" === typeof input.material && ("object" === typeof input.primaryField && null !== input.primaryField && _io3(input.primaryField)) && (Array.isArray(input.foreignFields) && input.foreignFields.every((elem => "object" === typeof elem && null !== elem && _io4(elem)))) && (Array.isArray(input.plainFields) && input.plainFields.every((elem => "object" === typeof elem && null !== elem && _io6(elem)))) && (Array.isArray(input.uniqueIndexes) && input.uniqueIndexes.every((elem => "object" === typeof elem && null !== elem && _io7(elem)))) && (Array.isArray(input.plainIndexes) && input.plainIndexes.every((elem => "object" === typeof elem && null !== elem && _io8(elem)))) && (Array.isArray(input.ginIndexes) && input.ginIndexes.every((elem => "object" === typeof elem && null !== elem && _io9(elem))));
-            const _io3 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "uuid" === input.type && "string" === typeof input.description;
-            const _io4 = 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 && _io5(input.relation)) && "boolean" === typeof input.unique && "boolean" === typeof input.nullable;
-            const _io5 = input => "string" === typeof input.name && RegExp("^[a-zA-Z_][a-zA-Z0-9_]*$").test(input.name) && "string" === typeof input.targetModel;
-            const _io6 = 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 _io7 = 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 _io8 = input => Array.isArray(input.fieldNames) && (1 <= input.fieldNames.length && __typia_transform__isUniqueItems._isUniqueItems(input.fieldNames) && input.fieldNames.every((elem => "string" === typeof elem)));
-            const _io9 = input => "string" === typeof input.fieldName;
+            const _io0 = input => "string" === typeof input.planning && (Array.isArray(input.models) && input.models.every((elem => "object" === typeof elem && null !== elem && _io1(elem))));
+            const _io1 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "string" === typeof input.description && "boolean" === typeof input.material && ("object" === typeof input.primaryField && null !== input.primaryField && _io2(input.primaryField)) && (Array.isArray(input.foreignFields) && input.foreignFields.every((elem => "object" === typeof elem && null !== elem && _io3(elem)))) && (Array.isArray(input.plainFields) && input.plainFields.every((elem => "object" === typeof elem && null !== elem && _io5(elem)))) && (Array.isArray(input.uniqueIndexes) && input.uniqueIndexes.every((elem => "object" === typeof elem && null !== elem && _io6(elem)))) && (Array.isArray(input.plainIndexes) && input.plainIndexes.every((elem => "object" === typeof elem && null !== elem && _io7(elem)))) && (Array.isArray(input.ginIndexes) && input.ginIndexes.every((elem => "object" === typeof elem && null !== elem && _io8(elem))));
+            const _io2 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "uuid" === input.type && "string" === typeof input.description;
+            const _io3 = 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 && _io4(input.relation)) && "boolean" === typeof input.unique && "boolean" === typeof input.nullable;
+            const _io4 = input => "string" === typeof input.name && RegExp("^[a-zA-Z_][a-zA-Z0-9_]*$").test(input.name) && "string" === typeof input.targetModel;
+            const _io5 = 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 _io6 = 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 _io7 = input => Array.isArray(input.fieldNames) && (1 <= input.fieldNames.length && __typia_transform__isUniqueItems._isUniqueItems(input.fieldNames) && input.fieldNames.every((elem => "string" === typeof elem)));
+            const _io8 = input => "string" === typeof input.fieldName;
             const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.planning || _report(_exceptionable, {
                 path: _path + ".planning",
                 expected: "string",
                 value: input.planning
-            }), (Array.isArray(input.files) || _report(_exceptionable, {
-                path: _path + ".files",
-                expected: "Array<AutoBePrisma.IFile>",
-                value: input.files
-            })) && input.files.map(((elem, _index10) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                path: _path + ".files[" + _index10 + "]",
-                expected: "AutoBePrisma.IFile",
-                value: elem
-            })) && _vo1(elem, _path + ".files[" + _index10 + "]", _exceptionable) || _report(_exceptionable, {
-                path: _path + ".files[" + _index10 + "]",
-                expected: "AutoBePrisma.IFile",
-                value: elem
-            }))).every((flag => flag)) || _report(_exceptionable, {
-                path: _path + ".files",
-                expected: "Array<AutoBePrisma.IFile>",
-                value: input.files
-            }) ].every((flag => flag));
-            const _vo1 = (input, _path, _exceptionable = true) => [ "string" === typeof input.filename && (RegExp("^[a-zA-Z0-9._-]+\\.prisma$").test(input.filename) || _report(_exceptionable, {
-                path: _path + ".filename",
-                expected: 'string & Pattern<"^[a-zA-Z0-9._-]+\\\\.prisma$">',
-                value: input.filename
-            })) || _report(_exceptionable, {
-                path: _path + ".filename",
-                expected: '(string & Pattern<"^[a-zA-Z0-9._-]+\\\\.prisma$">)',
-                value: input.filename
-            }), "string" === typeof input.namespace || _report(_exceptionable, {
-                path: _path + ".namespace",
-                expected: "string",
-                value: input.namespace
             }), (Array.isArray(input.models) || _report(_exceptionable, {
                 path: _path + ".models",
                 expected: "Array<AutoBePrisma.IModel>",
                 value: input.models
-            })) && input.models.map(((elem, _index11) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                path: _path + ".models[" + _index11 + "]",
+            })) && input.models.map(((elem, _index9) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                path: _path + ".models[" + _index9 + "]",
                 expected: "AutoBePrisma.IModel",
                 value: elem
-            })) && _vo2(elem, _path + ".models[" + _index11 + "]", _exceptionable) || _report(_exceptionable, {
-                path: _path + ".models[" + _index11 + "]",
+            })) && _vo1(elem, _path + ".models[" + _index9 + "]", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".models[" + _index9 + "]",
                 expected: "AutoBePrisma.IModel",
                 value: elem
             }))).every((flag => flag)) || _report(_exceptionable, {
@@ -5589,7 +5550,7 @@ const claude$2 = {
                 expected: "Array<AutoBePrisma.IModel>",
                 value: input.models
             }) ].every((flag => flag));
-            const _vo2 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
+            const _vo1 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                 path: _path + ".name",
                 expected: 'string & Pattern<"^[a-z][a-z0-9_]*$">',
                 value: input.name
@@ -5609,7 +5570,7 @@ const claude$2 = {
                 path: _path + ".primaryField",
                 expected: "AutoBePrisma.IPrimaryField",
                 value: input.primaryField
-            })) && _vo3(input.primaryField, _path + ".primaryField", _exceptionable) || _report(_exceptionable, {
+            })) && _vo2(input.primaryField, _path + ".primaryField", _exceptionable) || _report(_exceptionable, {
                 path: _path + ".primaryField",
                 expected: "AutoBePrisma.IPrimaryField",
                 value: input.primaryField
@@ -5617,12 +5578,12 @@ const claude$2 = {
                 path: _path + ".foreignFields",
                 expected: "Array<AutoBePrisma.IForeignField>",
                 value: input.foreignFields
-            })) && input.foreignFields.map(((elem, _index12) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                path: _path + ".foreignFields[" + _index12 + "]",
+            })) && input.foreignFields.map(((elem, _index10) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                path: _path + ".foreignFields[" + _index10 + "]",
                 expected: "AutoBePrisma.IForeignField",
                 value: elem
-            })) && _vo4(elem, _path + ".foreignFields[" + _index12 + "]", _exceptionable) || _report(_exceptionable, {
-                path: _path + ".foreignFields[" + _index12 + "]",
+            })) && _vo3(elem, _path + ".foreignFields[" + _index10 + "]", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".foreignFields[" + _index10 + "]",
                 expected: "AutoBePrisma.IForeignField",
                 value: elem
             }))).every((flag => flag)) || _report(_exceptionable, {
@@ -5633,12 +5594,12 @@ const claude$2 = {
                 path: _path + ".plainFields",
                 expected: "Array<AutoBePrisma.IPlainField>",
                 value: input.plainFields
-            })) && input.plainFields.map(((elem, _index13) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                path: _path + ".plainFields[" + _index13 + "]",
+            })) && input.plainFields.map(((elem, _index11) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                path: _path + ".plainFields[" + _index11 + "]",
                 expected: "AutoBePrisma.IPlainField",
                 value: elem
-            })) && _vo6(elem, _path + ".plainFields[" + _index13 + "]", _exceptionable) || _report(_exceptionable, {
-                path: _path + ".plainFields[" + _index13 + "]",
+            })) && _vo5(elem, _path + ".plainFields[" + _index11 + "]", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".plainFields[" + _index11 + "]",
                 expected: "AutoBePrisma.IPlainField",
                 value: elem
             }))).every((flag => flag)) || _report(_exceptionable, {
@@ -5649,12 +5610,12 @@ const claude$2 = {
                 path: _path + ".uniqueIndexes",
                 expected: "Array<AutoBePrisma.IUniqueIndex>",
                 value: input.uniqueIndexes
-            })) && input.uniqueIndexes.map(((elem, _index14) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                path: _path + ".uniqueIndexes[" + _index14 + "]",
+            })) && input.uniqueIndexes.map(((elem, _index12) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                path: _path + ".uniqueIndexes[" + _index12 + "]",
                 expected: "AutoBePrisma.IUniqueIndex",
                 value: elem
-            })) && _vo7(elem, _path + ".uniqueIndexes[" + _index14 + "]", _exceptionable) || _report(_exceptionable, {
-                path: _path + ".uniqueIndexes[" + _index14 + "]",
+            })) && _vo6(elem, _path + ".uniqueIndexes[" + _index12 + "]", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".uniqueIndexes[" + _index12 + "]",
                 expected: "AutoBePrisma.IUniqueIndex",
                 value: elem
             }))).every((flag => flag)) || _report(_exceptionable, {
@@ -5665,12 +5626,12 @@ const claude$2 = {
                 path: _path + ".plainIndexes",
                 expected: "Array<AutoBePrisma.IPlainIndex>",
                 value: input.plainIndexes
-            })) && input.plainIndexes.map(((elem, _index15) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                path: _path + ".plainIndexes[" + _index15 + "]",
+            })) && input.plainIndexes.map(((elem, _index13) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                path: _path + ".plainIndexes[" + _index13 + "]",
                 expected: "AutoBePrisma.IPlainIndex",
                 value: elem
-            })) && _vo8(elem, _path + ".plainIndexes[" + _index15 + "]", _exceptionable) || _report(_exceptionable, {
-                path: _path + ".plainIndexes[" + _index15 + "]",
+            })) && _vo7(elem, _path + ".plainIndexes[" + _index13 + "]", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".plainIndexes[" + _index13 + "]",
                 expected: "AutoBePrisma.IPlainIndex",
                 value: elem
             }))).every((flag => flag)) || _report(_exceptionable, {
@@ -5681,12 +5642,12 @@ const claude$2 = {
                 path: _path + ".ginIndexes",
                 expected: "Array<AutoBePrisma.IGinIndex>",
                 value: input.ginIndexes
-            })) && input.ginIndexes.map(((elem, _index16) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                path: _path + ".ginIndexes[" + _index16 + "]",
+            })) && input.ginIndexes.map(((elem, _index14) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                path: _path + ".ginIndexes[" + _index14 + "]",
                 expected: "AutoBePrisma.IGinIndex",
                 value: elem
-            })) && _vo9(elem, _path + ".ginIndexes[" + _index16 + "]", _exceptionable) || _report(_exceptionable, {
-                path: _path + ".ginIndexes[" + _index16 + "]",
+            })) && _vo8(elem, _path + ".ginIndexes[" + _index14 + "]", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".ginIndexes[" + _index14 + "]",
                 expected: "AutoBePrisma.IGinIndex",
                 value: elem
             }))).every((flag => flag)) || _report(_exceptionable, {
@@ -5694,7 +5655,7 @@ const claude$2 = {
                 expected: "Array<AutoBePrisma.IGinIndex>",
                 value: input.ginIndexes
             }) ].every((flag => flag));
-            const _vo3 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
+            const _vo2 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                 path: _path + ".name",
                 expected: 'string & Pattern<"^[a-z][a-z0-9_]*$">',
                 value: input.name
@@ -5711,7 +5672,7 @@ const claude$2 = {
                 expected: "string",
                 value: input.description
             }) ].every((flag => flag));
-            const _vo4 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
+            const _vo3 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                 path: _path + ".name",
                 expected: 'string & Pattern<"^[a-z][a-z0-9_]*$">',
                 value: input.name
@@ -5731,7 +5692,7 @@ const claude$2 = {
                 path: _path + ".relation",
                 expected: "__type",
                 value: input.relation
-            })) && _vo5(input.relation, _path + ".relation", _exceptionable) || _report(_exceptionable, {
+            })) && _vo4(input.relation, _path + ".relation", _exceptionable) || _report(_exceptionable, {
                 path: _path + ".relation",
                 expected: "__type",
                 value: input.relation
@@ -5744,7 +5705,7 @@ const claude$2 = {
                 expected: "boolean",
                 value: input.nullable
             }) ].every((flag => flag));
-            const _vo5 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-zA-Z_][a-zA-Z0-9_]*$").test(input.name) || _report(_exceptionable, {
+            const _vo4 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-zA-Z_][a-zA-Z0-9_]*$").test(input.name) || _report(_exceptionable, {
                 path: _path + ".name",
                 expected: 'string & Pattern<"^[a-zA-Z_][a-zA-Z0-9_]*$">',
                 value: input.name
@@ -5757,7 +5718,7 @@ const claude$2 = {
                 expected: "string",
                 value: input.targetModel
             }) ].every((flag => flag));
-            const _vo6 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
+            const _vo5 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                 path: _path + ".name",
                 expected: 'string & Pattern<"^[a-z][a-z0-9_]*$">',
                 value: input.name
@@ -5778,7 +5739,7 @@ const claude$2 = {
                 expected: "boolean",
                 value: input.nullable
             }) ].every((flag => flag));
-            const _vo7 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.fieldNames) || _report(_exceptionable, {
+            const _vo6 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.fieldNames) || _report(_exceptionable, {
                 path: _path + ".fieldNames",
                 expected: "(Array<string> & MinItems<1> & UniqueItems<true>)",
                 value: input.fieldNames
@@ -5790,8 +5751,8 @@ const claude$2 = {
                 path: _path + ".fieldNames",
                 expected: "Array<> & UniqueItems<true>",
                 value: input.fieldNames
-            })) && input.fieldNames.map(((elem, _index17) => "string" === typeof elem || _report(_exceptionable, {
-                path: _path + ".fieldNames[" + _index17 + "]",
+            })) && input.fieldNames.map(((elem, _index15) => "string" === typeof elem || _report(_exceptionable, {
+                path: _path + ".fieldNames[" + _index15 + "]",
                 expected: "string",
                 value: elem
             }))).every((flag => flag))) || _report(_exceptionable, {
@@ -5803,7 +5764,7 @@ const claude$2 = {
                 expected: "true",
                 value: input.unique
             }) ].every((flag => flag));
-            const _vo8 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.fieldNames) || _report(_exceptionable, {
+            const _vo7 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.fieldNames) || _report(_exceptionable, {
                 path: _path + ".fieldNames",
                 expected: "(Array<string> & MinItems<1> & UniqueItems<true>)",
                 value: input.fieldNames
@@ -5815,8 +5776,8 @@ const claude$2 = {
                 path: _path + ".fieldNames",
                 expected: "Array<> & UniqueItems<true>",
                 value: input.fieldNames
-            })) && input.fieldNames.map(((elem, _index18) => "string" === typeof elem || _report(_exceptionable, {
-                path: _path + ".fieldNames[" + _index18 + "]",
+            })) && input.fieldNames.map(((elem, _index16) => "string" === typeof elem || _report(_exceptionable, {
+                path: _path + ".fieldNames[" + _index16 + "]",
                 expected: "string",
                 value: elem
             }))).every((flag => flag))) || _report(_exceptionable, {
@@ -5824,7 +5785,7 @@ const claude$2 = {
                 expected: "(Array<string> & MinItems<1> & UniqueItems<true>)",
                 value: input.fieldNames
             }) ].every((flag => flag));
-            const _vo9 = (input, _path, _exceptionable = true) => [ "string" === typeof input.fieldName || _report(_exceptionable, {
+            const _vo8 = (input, _path, _exceptionable = true) => [ "string" === typeof input.fieldName || _report(_exceptionable, {
                 path: _path + ".fieldName",
                 expected: "string",
                 value: input.fieldName
@@ -5879,290 +5840,237 @@ const collection$2 = {
                 type: "object",
                 properties: {
                     planning: {
-                        title: "Detailed execution plan for fixing AutoBePrisma validation errors",
-                        description: "Detailed execution plan for fixing AutoBePrisma validation errors.\n\n🎯 Purpose: Enable systematic reasoning and step-by-step error resolution\napproach for structured schema validation issues\n\n📋 Required Planning Content:\n\n1. **Error Analysis Summary**\n\n   - List all validation errors from IAutoBePrismaValidation.IError[] array\n   - Categorize errors by type (duplications, references, types, indexes)\n   - Identify root causes and error interdependencies\n2. **Fix Strategy Overview**\n\n   - Prioritize fixes based on dependencies (fix duplications first)\n   - Outline minimal changes needed for each validation error\n   - Identify potential impact on other models/relationships\n3. **Step-by-Step Fix Plan**\n\n   - Model-by-model modification plan with specific changes\n   - Exact field additions, removals, or renames required\n   - Reference updates needed for renamed elements\n   - Index corrections to comply with validation rules\n4. **Preservation Checklist**\n\n   - Confirm which descriptions and business logic must be preserved\n   - List relationships and constraints to maintain unchanged\n   - Identify cross-model dependencies that must remain intact\n5. **Risk Assessment**\n\n   - Potential side effects of each planned fix\n   - Validation points to check after applying corrections\n   - Ensure no new validation errors are introduced\n\n💡 Example Planning Structure:\n\n    ## Error Analysis\n    - Error 1: Duplicate field 'name' in shopping_customers model\n    - Error 2: Invalid targetModel 'shopping_customer' should be 'shopping_customers'\n\n    ## Fix Strategy\n    1. Remove duplicate 'name' field (keep the more detailed one)\n    2. Update foreign key references to use correct plural model name\n\n    ## Detailed Steps\n    1. shopping_customers model: Remove second 'name' field from plainFields\n    2. shopping_orders model: Update targetModel from 'shopping_customer' to 'shopping_customers'\n\n    ## Preservation Notes\n    - Keep business descriptions for remaining 'name' field\n    - Maintain all relationship semantics\n    - Preserve all indexes and constraints",
+                        description: "Detailed execution plan for fixing `AutoBePrisma` validation errors in\nspecific models.\n\n🎯 Purpose: Enable systematic reasoning and step-by-step error resolution\napproach for targeted model validation issues\n\n📋 Required Planning Content:\n\n1. **Error Scope Analysis**\n\n   - List all validation errors from IAutoBePrismaValidation.IError[] array\n   - Extract unique table names from errors to identify affected models\n   - Categorize errors by type (field duplications, references, types, indexes)\n   - Identify which models need correction vs. which 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 (if any) without modifying non-error\n        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\n\n💡 Example Planning Structure:\n\n    ## Error Scope\n    - Target Models: shopping_customers, shopping_orders (2 models only)\n    - Unchanged Models: All others remain in original schema\n\n    ## Targeted Fixes\n    - shopping_customers: Remove duplicate 'email' field\n    - shopping_orders: Update targetModel reference to 'shopping_customers'\n\n    ## Output Scope\n    - Return: Only shopping_customers and shopping_orders models\n    - Preserve: All other models unchanged in original schema\n\n    ## Cross-Model Impact\n    - Verify: shopping_orders still references shopping_customers correctly\n    - No changes needed in other models referencing these",
                         type: "string"
                     },
-                    files: {
-                        description: "Original AutoBePrisma.IApplication structure that contains validation\nerrors and needs correction.\n\n📥 Input Structure:\n\n- Complete IApplication with files array containing validation errors\n- Each file contains models with potential structural issues\n- Errors may include duplications, invalid references, or constraint\n  violations\n\n🔍 Expected Validation Issues:\n\n- Duplicate model names across files\n- Duplicate field/relation names within models\n- Invalid foreign key references to non-existent models\n- Single foreign key fields in index arrays\n- Non-plural model names or invalid naming conventions\n\n📝 Application Content Analysis:\n\n- All models with their complete field definitions\n- All relationships with targetModel and targetfield configurations\n- All indexes (unique, plain, GIN) with field references\n- All business descriptions and requirement mappings\n- Cross-file model references and dependencies\n\n⚠️ Processing Notes:\n\n- Structure may contain validation errors that prevent code generation\n- Some models might reference non-existent targets\n- Field names might violate naming conventions\n- Index configurations might include forbidden single foreign keys\n- Business logic and descriptions must be preserved during fixes",
+                    models: {
+                        description: "ONLY the specific models that contain validation errors and need\ncorrection.\n\n📥 Input Structure:\n\n- Contains ONLY models mentioned in IAutoBePrismaValidation.IError[] array\n- Each model has specific validation errors that need targeted correction\n- Models not mentioned in errors are excluded from this input\n- Represents minimal scope for error correction\n\n🔍 Expected Validation Issues (Model-Specific):\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\n📝 Model Content Analysis (Targeted Scope):\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\n⚠️ Processing Notes (Focused Approach):\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\n\n🎯 Correction Scope:\n\n- Fix validation errors within these specific models\n- Update internal model structure (fields, relations, indexes)\n- Correct references to external models (without modifying targets)\n- Maintain compatibility with unchanged models in the full schema\n- Return corrected versions of ONLY these models",
                         type: "array",
                         items: {
-                            description: "Description of the current {@link AutoBePrisma.IFile} type:\n\n> Interface representing a single Prisma schema file within the application.\n> \n> Each file focuses on a specific business domain and contains related\n> models. File organization follows domain-driven design principles as seen\n> in the uploaded schemas.",
+                            description: "Description of the current {@link AutoBePrisma.IModel} type:\n\n> Interface representing a single Prisma model (database table).\n> \n> Based 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_)",
                             type: "object",
                             properties: {
-                                filename: {
-                                    title: "Name of the schema file to be generated",
-                                    description: 'Name of the schema file to be generated.\n\nShould follow the naming convention: "schema-{number}-{domain}.prisma"\nExamples: "schema-02-systematic.prisma", "schema-03-actors.prisma" The\nnumber indicates the dependency order for schema generation.\n\n\n@pattern ^[a-zA-Z0-9._-]+\\.prisma$',
+                                name: {
+                                    title: "Name of the Prisma model (database table name)",
+                                    description: 'Name of the Prisma model (database table name).\n\nShould follow snake_case convention with domain prefix. Examples:\n"shopping_customers", "shopping_sale_snapshots", "bbs_articles"\nMaterialized views use "mv_" prefix: "mv_shopping_sale_last_snapshots"\n\n\n@pattern ^[a-z][a-z0-9_]*$',
                                     type: "string"
                                 },
-                                namespace: {
-                                    title: "Business domain namespace that groups related models",
-                                    description: 'Business domain namespace that groups related models.\n\nUsed in Prisma documentation comments as "@\\namespace directive".\nExamples from uploaded schemas: "Systematic", "Actors", "Sales", "Carts",\n"Orders", "Coupons", "Coins", "Inquiries", "Favorites", "Articles"',
+                                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 Example:\n  "Customer information, but not a person but a **connection** basis..."',
                                     type: "string"
                                 },
-                                models: {
-                                    title: "Array of Prisma models (database tables) within this domain",
-                                    description: "Array of Prisma models (database tables) within this domain.\n\nEach model represents a business entity or concept within the namespace.\nModels can reference each other through foreign key relationships.",
+                                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',
+                                    type: "boolean"
+                                },
+                                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.\n\n------------------------------\n\nDescription of the current {@link AutoBePrisma.IPrimaryField} type:\n\n> Interface representing the primary key field of a Prisma model.\n> \n> All models in the uploaded schemas use UUID as primary key for better\n> distributed system compatibility and security (no sequential ID exposure).',
+                                    type: "object",
+                                    properties: {
+                                        name: {
+                                            title: "Name of the primary key field",
+                                            description: 'Name of the primary key field.\n\nConsistently named "id" across all models in the uploaded schemas.\nRepresents the unique identifier for each record in the table.\n\n\n@pattern ^[a-z][a-z0-9_]*$',
+                                            type: "string"
+                                        },
+                                        type: {
+                                            title: "Data type of the primary key field",
+                                            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: {
+                                            title: "Description of the primary key field's purpose",
+                                            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.',
+                                            type: "string"
+                                        }
+                                    },
+                                    required: [ "name", "type", "description" ]
+                                },
+                                foreignFields: {
+                                    title: "Array of foreign key fields that reference other models",
+                                    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.",
                                     type: "array",
                                     items: {
-                                        description: "Description of the current {@link AutoBePrisma.IModel} type:\n\n> Interface representing a single Prisma model (database table).\n> \n> Based 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: "Description of the current {@link AutoBePrisma.IForeignField} type:\n\n> Interface representing a foreign key field that establishes relationships\n> between models.\n> \n> Foreign keys create associations between models, enabling relational data\n> modeling. They can represent 1:1, 1:N, or participate in M:N relationships\n> through junction tables.",
                                         type: "object",
                                         properties: {
                                             name: {
-                                                title: "Name of the Prisma model (database table name)",
-                                                description: 'Name of the Prisma model (database table name).\n\nShould follow snake_case convention with domain prefix. Examples:\n"shopping_customers", "shopping_sale_snapshots", "bbs_articles"\nMaterialized views use "mv_" prefix: "mv_shopping_sale_last_snapshots"\n\n\n@pattern ^[a-z][a-z0-9_]*$',
+                                                title: "Name of the foreign key field",
+                                                description: 'Name of the foreign key field.\n\nFollows convention: "{target_model_name_without_prefix}_id" Examples:\n"shopping_customer_id", "bbs_article_id", "attachment_file_id" For\nself-references: "parent_id" (e.g., in hierarchical structures)\n\n\n@pattern ^[a-z][a-z0-9_]*$',
                                                 type: "string"
                                             },
+                                            type: {
+                                                title: "Data type of the foreign key field",
+                                                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: '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 Example:\n  "Customer information, but not a person but a **connection** basis..."',
+                                                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.',
                                                 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',
-                                                type: "boolean"
-                                            },
-                                            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.\n\n------------------------------\n\nDescription of the current {@link AutoBePrisma.IPrimaryField} type:\n\n> Interface representing the primary key field of a Prisma model.\n> \n> All models in the uploaded schemas use UUID as primary key for better\n> distributed system compatibility and security (no sequential ID exposure).',
+                                            relation: {
+                                                title: "Prisma relation configuration defining the association details",
+                                                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.",
                                                 type: "object",
                                                 properties: {
                                                     name: {
-                                                        title: "Name of the primary key field",
-                                                        description: 'Name of the primary key field.\n\nConsistently named "id" across all models in the uploaded schemas.\nRepresents the unique identifier for each record in the table.\n\n\n@pattern ^[a-z][a-z0-9_]*$',
+                                                        title: "Name of the relation property in the Prisma model",
+                                                        description: 'Name of the relation property in the Prisma model.\n\nUsed to access the related model instance. Usually a descriptive name\nof the relationship. Examples: "customer", "channel", "parent",\n"snapshot"\n\n\n@pattern ^[a-zA-Z_][a-zA-Z0-9_]*$',
                                                         type: "string"
                                                     },
-                                                    type: {
-                                                        title: "Data type of the primary key field",
-                                                        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: {
-                                                        title: "Description of the primary key field's purpose",
-                                                        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.',
+                                                    targetModel: {
+                                                        title: "Name of the target model being referenced",
+                                                        description: 'Name of the target model being referenced.\n\nMust match exactly with an existing model name in the schema. Examples:\n"shopping_customers", "shopping_channels", "bbs_articles"',
                                                         type: "string"
                                                     }
                                                 },
-                                                required: [ "name", "type", "description" ]
+                                                required: [ "name", "targetModel" ]
                                             },
-                                            foreignFields: {
-                                                title: "Array of foreign key fields that reference other models",
-                                                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.",
-                                                type: "array",
-                                                items: {
-                                                    description: "Description of the current {@link AutoBePrisma.IForeignField} type:\n\n> Interface representing a foreign key field that establishes relationships\n> between models.\n> \n> Foreign keys create associations between models, enabling relational data\n> modeling. They can represent 1:1, 1:N, or participate in M:N relationships\n> through junction tables.",
-                                                    type: "object",
-                                                    properties: {
-                                                        name: {
-                                                            title: "Name of the foreign key field",
-                                                            description: 'Name of the foreign key field.\n\nFollows convention: "{target_model_name_without_prefix}_id" Examples:\n"shopping_customer_id", "bbs_article_id", "attachment_file_id" For\nself-references: "parent_id" (e.g., in hierarchical structures)\n\n\n@pattern ^[a-z][a-z0-9_]*$',
-                                                            type: "string"
-                                                        },
-                                                        type: {
-                                                            title: "Data type of the foreign key field",
-                                                            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.',
-                                                            type: "string"
-                                                        },
-                                                        relation: {
-                                                            title: "Prisma relation configuration defining the association details",
-                                                            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.",
-                                                            type: "object",
-                                                            properties: {
-                                                                name: {
-                                                                    title: "Name of the relation property in the Prisma model",
-                                                                    description: 'Name of the relation property in the Prisma model.\n\nUsed to access the related model instance. Usually a descriptive name\nof the relationship. Examples: "customer", "channel", "parent",\n"snapshot"\n\n\n@pattern ^[a-zA-Z_][a-zA-Z0-9_]*$',
-                                                                    type: "string"
-                                                                },
-                                                                targetModel: {
-                                                                    title: "Name of the target model being referenced",
-                                                                    description: 'Name of the target model being referenced.\n\nMust match exactly with an existing model name in the schema. Examples:\n"shopping_customers", "shopping_channels", "bbs_articles"',
-                                                                    type: "string"
-                                                                }
-                                                            },
-                                                            required: [ "name", "targetModel" ]
-                                                        },
-                                                        unique: {
-                                                            title: "Whether this foreign key has a unique constraint",
-                                                            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.",
-                                                            type: "boolean"
-                                                        },
-                                                        nullable: {
-                                                            title: "Whether this foreign key can be null (optional relationship)",
-                                                            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.",
-                                                            type: "boolean"
-                                                        }
-                                                    },
-                                                    required: [ "name", "type", "description", "relation", "unique", "nullable" ]
-                                                }
+                                            unique: {
+                                                title: "Whether this foreign key has a unique constraint",
+                                                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.",
+                                                type: "boolean"
                                             },
-                                            plainFields: {
-                                                title: "Array of regular data fields that don't reference other models",
-                                                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.",
-                                                type: "array",
-                                                items: {
-                                                    description: "Description of the current {@link AutoBePrisma.IPlainField} type:\n\n> Interface representing a regular data field that stores business\n> information.\n> \n> These fields contain the actual business data like names, amounts,\n> timestamps, flags, descriptions, and other domain-specific information.",
-                                                    type: "object",
-                                                    properties: {
-                                                        name: {
-                                                            title: "Name of the field in the database table",
-                                                            description: "Name of the field in the database table.\n\nShould use snake_case convention. Common patterns from uploaded schemas:\n\n- Timestamps: created_at, updated_at, deleted_at, opened_at, closed_at\n- Identifiers: code, name, nickname, title\n- Business data: value, quantity, price, volume, balance\n- Flags: primary, required, exclusive, secret, multiplicative\n\n\n@pattern ^[a-z][a-z0-9_]*$",
-                                                            type: "string"
-                                                        },
-                                                        type: {
-                                                            title: "Data type of the field for Prisma schema generation",
-                                                            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- Date: Date-only values (rare, mostly for business dates)\n- Datetime: Timestamp fields with date and time",
-                                                            type: "string",
-                                                            enum: [ "string", "boolean", "uuid", "uri", "int", "double", "datetime" ]
-                                                        },
-                                                        description: {
-                                                            title: "Description explaining the business purpose and usage of this field",
-                                                            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 Example: "Amount of cash payment." or\n  "Whether the unit is required or not."',
-                                                            type: "string"
-                                                        },
-                                                        nullable: {
-                                                            title: "Whether this field can contain null values",
-                                                            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.",
-                                                            type: "boolean"
-                                                        }
-                                                    },
-                                                    required: [ "name", "type", "description", "nullable" ]
-                                                }
+                                            nullable: {
+                                                title: "Whether this foreign key can be null (optional relationship)",
+                                                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.",
+                                                type: "boolean"
+                                            }
+                                        },
+                                        required: [ "name", "type", "description", "relation", "unique", "nullable" ]
+                                    }
+                                },
+                                plainFields: {
+                                    title: "Array of regular data fields that don't reference other models",
+                                    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.",
+                                    type: "array",
+                                    items: {
+                                        description: "Description of the current {@link AutoBePrisma.IPlainField} type:\n\n> Interface representing a regular data field that stores business\n> information.\n> \n> These fields contain the actual business data like names, amounts,\n> timestamps, flags, descriptions, and other domain-specific information.",
+                                        type: "object",
+                                        properties: {
+                                            name: {
+                                                title: "Name of the field in the database table",
+                                                description: "Name of the field in the database table.\n\nShould use snake_case convention. Common patterns from uploaded schemas:\n\n- Timestamps: created_at, updated_at, deleted_at, opened_at, closed_at\n- Identifiers: code, name, nickname, title\n- Business data: value, quantity, price, volume, balance\n- Flags: primary, required, exclusive, secret, multiplicative\n\n\n@pattern ^[a-z][a-z0-9_]*$",
+                                                type: "string"
                                             },
-                                            uniqueIndexes: {
-                                                title: "Array of unique indexes for enforcing data integrity constraints",
-                                                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).",
-                                                type: "array",
-                                                items: {
-                                                    description: "Description of the current {@link AutoBePrisma.IUniqueIndex} type:\n\n> Interface representing a unique index constraint on one or more fields.\n> \n> Unique indexes enforce data integrity by ensuring no duplicate values exist\n> for the specified field combination. Essential for business rules that\n> require uniqueness like email addresses, codes, or composite keys.",
-                                                    type: "object",
-                                                    properties: {
-                                                        fieldNames: {
-                                                            title: "Array of field names that together form the unique constraint",
-                                                            description: 'Array of field names that together form the unique constraint.\n\nCan be single field (e.g., ["email"]) or composite (e.g., ["channel_id",\n"code"]). All field names must exist in the model. Order matters for\ncomposite indexes. Examples: ["code"], ["shopping_channel_id",\n"nickname"], ["email"]\n\n\n@minItems 1\n@uniqueItems',
-                                                            type: "array",
-                                                            items: {
-                                                                type: "string"
-                                                            }
-                                                        },
-                                                        unique: {
-                                                            title: "Explicit marker indicating this is a unique index",
-                                                            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".',
-                                                            type: "boolean",
-                                                            enum: [ true ]
-                                                        }
-                                                    },
-                                                    required: [ "fieldNames", "unique" ]
-                                                }
+                                            type: {
+                                                title: "Data type of the field for Prisma schema generation",
+                                                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- Date: Date-only values (rare, mostly for business dates)\n- Datetime: Timestamp fields with date and time",
+                                                type: "string",
+                                                enum: [ "string", "boolean", "uuid", "uri", "int", "double", "datetime" ]
                                             },
-                                            plainIndexes: {
-                                                title: "Array of regular indexes for query performance optimization",
-                                                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: {
+                                                title: "Description explaining the business purpose and usage of this field",
+                                                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 Example: "Amount of cash payment." or\n  "Whether the unit is required or not."',
+                                                type: "string"
+                                            },
+                                            nullable: {
+                                                title: "Whether this field can contain null values",
+                                                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.",
+                                                type: "boolean"
+                                            }
+                                        },
+                                        required: [ "name", "type", "description", "nullable" ]
+                                    }
+                                },
+                                uniqueIndexes: {
+                                    title: "Array of unique indexes for enforcing data integrity constraints",
+                                    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).",
+                                    type: "array",
+                                    items: {
+                                        description: "Description of the current {@link AutoBePrisma.IUniqueIndex} type:\n\n> Interface representing a unique index constraint on one or more fields.\n> \n> Unique indexes enforce data integrity by ensuring no duplicate values exist\n> for the specified field combination. Essential for business rules that\n> require uniqueness like email addresses, codes, or composite keys.",
+                                        type: "object",
+                                        properties: {
+                                            fieldNames: {
+                                                title: "Array of field names that together form the unique constraint",
+                                                description: 'Array of field names that together form the unique constraint.\n\nCan be single field (e.g., ["email"]) or composite (e.g., ["channel_id",\n"code"]). All field names must exist in the model. Order matters for\ncomposite indexes. Examples: ["code"], ["shopping_channel_id",\n"nickname"], ["email"]\n\n\n@minItems 1\n@uniqueItems',
                                                 type: "array",
                                                 items: {
-                                                    description: "Description of the current {@link AutoBePrisma.IPlainIndex} type:\n\n> Interface representing a regular (non-unique) index for query performance.\n> \n> Regular indexes speed up database queries by creating optimized data\n> structures for common search patterns. Essential for foreign keys, date\n> ranges, and frequently filtered fields.",
-                                                    type: "object",
-                                                    properties: {
-                                                        fieldNames: {
-                                                            title: "Array of field names to include in the performance index",
-                                                            description: 'Array of field names to include in the performance index.\n\nCan be single field (e.g., ["created_at"]) or composite (e.g.,\n["customer_id", "created_at"]). All field names must exist in the model.\nOrder matters for composite indexes and should match common query\npatterns. Examples: ["created_at"], ["shopping_customer_id",\n"created_at"], ["ip"]\n\n\n@minItems 1\n@uniqueItems',
-                                                            type: "array",
-                                                            items: {
-                                                                type: "string"
-                                                            }
-                                                        }
-                                                    },
-                                                    required: [ "fieldNames" ]
+                                                    type: "string"
                                                 }
                                             },
-                                            ginIndexes: {
-                                                title: "Array of GIN (Generalized Inverted Index) indexes for full-text search",
-                                                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.",
+                                            unique: {
+                                                title: "Explicit marker indicating this is a unique index",
+                                                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".',
+                                                type: "boolean",
+                                                enum: [ true ]
+                                            }
+                                        },
+                                        required: [ "fieldNames", "unique" ]
+                                    }
+                                },
+                                plainIndexes: {
+                                    title: "Array of regular indexes for query performance optimization",
+                                    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.",
+                                    type: "array",
+                                    items: {
+                                        description: "Description of the current {@link AutoBePrisma.IPlainIndex} type:\n\n> Interface representing a regular (non-unique) index for query performance.\n> \n> Regular indexes speed up database queries by creating optimized data\n> structures for common search patterns. Essential for foreign keys, date\n> ranges, and frequently filtered fields.",
+                                        type: "object",
+                                        properties: {
+                                            fieldNames: {
+                                                title: "Array of field names to include in the performance index",
+                                                description: 'Array of field names to include in the performance index.\n\nCan be single field (e.g., ["created_at"]) or composite (e.g.,\n["customer_id", "created_at"]). All field names must exist in the model.\nOrder matters for composite indexes and should match common query\npatterns. Examples: ["created_at"], ["shopping_customer_id",\n"created_at"], ["ip"]\n\n\n@minItems 1\n@uniqueItems',
                                                 type: "array",
                                                 items: {
-                                                    description: "Description of the current {@link AutoBePrisma.IGinIndex} type:\n\n> Interface representing a GIN (Generalized Inverted Index) for full-text\n> search.\n> \n> GIN indexes enable advanced PostgreSQL text search capabilities including\n> fuzzy matching and partial text search using trigram operations. Essential\n> for user-facing search features on text content.",
-                                                    type: "object",
-                                                    properties: {
-                                                        fieldName: {
-                                                            title: "Name of the text field to index for full-text search capabilities",
-                                                            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.',
-                                                            type: "string"
-                                                        }
-                                                    },
-                                                    required: [ "fieldName" ]
+                                                    type: "string"
                                                 }
                                             }
                                         },
-                                        required: [ "name", "description", "material", "primaryField", "foreignFields", "plainFields", "uniqueIndexes", "plainIndexes", "ginIndexes" ]
+                                        required: [ "fieldNames" ]
                                     }
-                                }
-                            },
-                            required: [ "filename", "namespace", "models" ]
-                        }
-                    }
-                },
-                required: [ "planning", "files" ],
-                additionalProperties: false,
-                $defs: {}
-            },
-            description: "Fixes validation errors in AutoBePrisma.IApplication structure while\npreserving ALL existing business logic and model descriptions.\n\n## Core Rules\n\n1. Fix ONLY validation errors - never remove business descriptions\n2. Apply minimal changes - preserve original design intent\n3. Return COMPLETE corrected structure - no data loss allowed\n4. Maintain referential integrity across all models\n\n## Preservation Requirements\n\n- Keep ALL model and field descriptions\n- Keep business logic and architectural patterns\n- Maintain relationship semantics and cardinality\n- Remove descriptions only when removing duplicate elements\n\n## Fix Strategy\n\n- Resolve structural validation errors without changing business intent\n- Remove duplicate fields/relations while preserving most appropriate ones\n- Fix invalid references and type mismatches\n- Ensure naming conventions and index rules compliance",
-            validate: (() => {
-                const _io0 = input => "string" === typeof input.planning && (Array.isArray(input.files) && input.files.every((elem => "object" === typeof elem && null !== elem && _io1(elem))));
-                const _io1 = input => "string" === typeof input.filename && RegExp("^[a-zA-Z0-9._-]+\\.prisma$").test(input.filename) && "string" === typeof input.namespace && (Array.isArray(input.models) && input.models.every((elem => "object" === typeof elem && null !== elem && _io2(elem))));
-                const _io2 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "string" === typeof input.description && "boolean" === typeof input.material && ("object" === typeof input.primaryField && null !== input.primaryField && _io3(input.primaryField)) && (Array.isArray(input.foreignFields) && input.foreignFields.every((elem => "object" === typeof elem && null !== elem && _io4(elem)))) && (Array.isArray(input.plainFields) && input.plainFields.every((elem => "object" === typeof elem && null !== elem && _io6(elem)))) && (Array.isArray(input.uniqueIndexes) && input.uniqueIndexes.every((elem => "object" === typeof elem && null !== elem && _io7(elem)))) && (Array.isArray(input.plainIndexes) && input.plainIndexes.every((elem => "object" === typeof elem && null !== elem && _io8(elem)))) && (Array.isArray(input.ginIndexes) && input.ginIndexes.every((elem => "object" === typeof elem && null !== elem && _io9(elem))));
-                const _io3 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "uuid" === input.type && "string" === typeof input.description;
-                const _io4 = 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 && _io5(input.relation)) && "boolean" === typeof input.unique && "boolean" === typeof input.nullable;
-                const _io5 = input => "string" === typeof input.name && RegExp("^[a-zA-Z_][a-zA-Z0-9_]*$").test(input.name) && "string" === typeof input.targetModel;
-                const _io6 = 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 _io7 = 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 _io8 = input => Array.isArray(input.fieldNames) && (1 <= input.fieldNames.length && __typia_transform__isUniqueItems._isUniqueItems(input.fieldNames) && input.fieldNames.every((elem => "string" === typeof elem)));
-                const _io9 = input => "string" === typeof input.fieldName;
-                const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.planning || _report(_exceptionable, {
-                    path: _path + ".planning",
-                    expected: "string",
-                    value: input.planning
-                }), (Array.isArray(input.files) || _report(_exceptionable, {
-                    path: _path + ".files",
-                    expected: "Array<AutoBePrisma.IFile>",
-                    value: input.files
-                })) && input.files.map(((elem, _index10) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".files[" + _index10 + "]",
-                    expected: "AutoBePrisma.IFile",
-                    value: elem
-                })) && _vo1(elem, _path + ".files[" + _index10 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".files[" + _index10 + "]",
-                    expected: "AutoBePrisma.IFile",
-                    value: elem
-                }))).every((flag => flag)) || _report(_exceptionable, {
-                    path: _path + ".files",
-                    expected: "Array<AutoBePrisma.IFile>",
-                    value: input.files
-                }) ].every((flag => flag));
-                const _vo1 = (input, _path, _exceptionable = true) => [ "string" === typeof input.filename && (RegExp("^[a-zA-Z0-9._-]+\\.prisma$").test(input.filename) || _report(_exceptionable, {
-                    path: _path + ".filename",
-                    expected: 'string & Pattern<"^[a-zA-Z0-9._-]+\\\\.prisma$">',
-                    value: input.filename
-                })) || _report(_exceptionable, {
-                    path: _path + ".filename",
-                    expected: '(string & Pattern<"^[a-zA-Z0-9._-]+\\\\.prisma$">)',
-                    value: input.filename
-                }), "string" === typeof input.namespace || _report(_exceptionable, {
-                    path: _path + ".namespace",
+                                },
+                                ginIndexes: {
+                                    title: "Array of GIN (Generalized Inverted Index) indexes for full-text search",
+                                    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.",
+                                    type: "array",
+                                    items: {
+                                        description: "Description of the current {@link AutoBePrisma.IGinIndex} type:\n\n> Interface representing a GIN (Generalized Inverted Index) for full-text\n> search.\n> \n> GIN indexes enable advanced PostgreSQL text search capabilities including\n> fuzzy matching and partial text search using trigram operations. Essential\n> for user-facing search features on text content.",
+                                        type: "object",
+                                        properties: {
+                                            fieldName: {
+                                                title: "Name of the text field to index for full-text search capabilities",
+                                                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.',
+                                                type: "string"
+                                            }
+                                        },
+                                        required: [ "fieldName" ]
+                                    }
+                                }
+                            },
+                            required: [ "name", "description", "material", "primaryField", "foreignFields", "plainFields", "uniqueIndexes", "plainIndexes", "ginIndexes" ]
+                        }
+                    }
+                },
+                required: [ "planning", "models" ],
+                additionalProperties: false,
+                $defs: {}
+            },
+            description: "Fixes validation errors in specific AutoBePrisma models while preserving\nALL existing business logic and model descriptions.\n\n## Core Rules\n\n1. Fix ONLY validation errors in provided models - never remove business\n   descriptions\n2. Apply minimal changes to error models only - preserve original design\n   intent\n3. Return ONLY corrected models - unchanged models remain in original schema\n4. Maintain referential integrity with unchanged models\n\n## Targeted Scope\n\n- Process ONLY models with validation errors from IError[] array\n- Exclude models without errors from processing and output\n- Minimize context usage by returning corrected models only\n- Preserve unchanged models in their original state\n\n## Fix Strategy\n\n- Resolve validation errors within specific models only\n- Fix field duplications, invalid references, and type mismatches\n- Update cross-model references without modifying target models\n- Ensure naming conventions and index rules compliance in corrected models",
+            validate: (() => {
+                const _io0 = input => "string" === typeof input.planning && (Array.isArray(input.models) && input.models.every((elem => "object" === typeof elem && null !== elem && _io1(elem))));
+                const _io1 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "string" === typeof input.description && "boolean" === typeof input.material && ("object" === typeof input.primaryField && null !== input.primaryField && _io2(input.primaryField)) && (Array.isArray(input.foreignFields) && input.foreignFields.every((elem => "object" === typeof elem && null !== elem && _io3(elem)))) && (Array.isArray(input.plainFields) && input.plainFields.every((elem => "object" === typeof elem && null !== elem && _io5(elem)))) && (Array.isArray(input.uniqueIndexes) && input.uniqueIndexes.every((elem => "object" === typeof elem && null !== elem && _io6(elem)))) && (Array.isArray(input.plainIndexes) && input.plainIndexes.every((elem => "object" === typeof elem && null !== elem && _io7(elem)))) && (Array.isArray(input.ginIndexes) && input.ginIndexes.every((elem => "object" === typeof elem && null !== elem && _io8(elem))));
+                const _io2 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "uuid" === input.type && "string" === typeof input.description;
+                const _io3 = 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 && _io4(input.relation)) && "boolean" === typeof input.unique && "boolean" === typeof input.nullable;
+                const _io4 = input => "string" === typeof input.name && RegExp("^[a-zA-Z_][a-zA-Z0-9_]*$").test(input.name) && "string" === typeof input.targetModel;
+                const _io5 = 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 _io6 = 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 _io7 = input => Array.isArray(input.fieldNames) && (1 <= input.fieldNames.length && __typia_transform__isUniqueItems._isUniqueItems(input.fieldNames) && input.fieldNames.every((elem => "string" === typeof elem)));
+                const _io8 = input => "string" === typeof input.fieldName;
+                const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.planning || _report(_exceptionable, {
+                    path: _path + ".planning",
                     expected: "string",
-                    value: input.namespace
+                    value: input.planning
                 }), (Array.isArray(input.models) || _report(_exceptionable, {
                     path: _path + ".models",
                     expected: "Array<AutoBePrisma.IModel>",
                     value: input.models
-                })) && input.models.map(((elem, _index11) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".models[" + _index11 + "]",
+                })) && input.models.map(((elem, _index9) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".models[" + _index9 + "]",
                     expected: "AutoBePrisma.IModel",
                     value: elem
-                })) && _vo2(elem, _path + ".models[" + _index11 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".models[" + _index11 + "]",
+                })) && _vo1(elem, _path + ".models[" + _index9 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".models[" + _index9 + "]",
                     expected: "AutoBePrisma.IModel",
                     value: elem
                 }))).every((flag => flag)) || _report(_exceptionable, {
@@ -6170,7 +6078,7 @@ const collection$2 = {
                     expected: "Array<AutoBePrisma.IModel>",
                     value: input.models
                 }) ].every((flag => flag));
-                const _vo2 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
+                const _vo1 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                     path: _path + ".name",
                     expected: 'string & Pattern<"^[a-z][a-z0-9_]*$">',
                     value: input.name
@@ -6190,7 +6098,7 @@ const collection$2 = {
                     path: _path + ".primaryField",
                     expected: "AutoBePrisma.IPrimaryField",
                     value: input.primaryField
-                })) && _vo3(input.primaryField, _path + ".primaryField", _exceptionable) || _report(_exceptionable, {
+                })) && _vo2(input.primaryField, _path + ".primaryField", _exceptionable) || _report(_exceptionable, {
                     path: _path + ".primaryField",
                     expected: "AutoBePrisma.IPrimaryField",
                     value: input.primaryField
@@ -6198,12 +6106,12 @@ const collection$2 = {
                     path: _path + ".foreignFields",
                     expected: "Array<AutoBePrisma.IForeignField>",
                     value: input.foreignFields
-                })) && input.foreignFields.map(((elem, _index12) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".foreignFields[" + _index12 + "]",
+                })) && input.foreignFields.map(((elem, _index10) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".foreignFields[" + _index10 + "]",
                     expected: "AutoBePrisma.IForeignField",
                     value: elem
-                })) && _vo4(elem, _path + ".foreignFields[" + _index12 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".foreignFields[" + _index12 + "]",
+                })) && _vo3(elem, _path + ".foreignFields[" + _index10 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".foreignFields[" + _index10 + "]",
                     expected: "AutoBePrisma.IForeignField",
                     value: elem
                 }))).every((flag => flag)) || _report(_exceptionable, {
@@ -6214,12 +6122,12 @@ const collection$2 = {
                     path: _path + ".plainFields",
                     expected: "Array<AutoBePrisma.IPlainField>",
                     value: input.plainFields
-                })) && input.plainFields.map(((elem, _index13) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".plainFields[" + _index13 + "]",
+                })) && input.plainFields.map(((elem, _index11) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".plainFields[" + _index11 + "]",
                     expected: "AutoBePrisma.IPlainField",
                     value: elem
-                })) && _vo6(elem, _path + ".plainFields[" + _index13 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".plainFields[" + _index13 + "]",
+                })) && _vo5(elem, _path + ".plainFields[" + _index11 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".plainFields[" + _index11 + "]",
                     expected: "AutoBePrisma.IPlainField",
                     value: elem
                 }))).every((flag => flag)) || _report(_exceptionable, {
@@ -6230,12 +6138,12 @@ const collection$2 = {
                     path: _path + ".uniqueIndexes",
                     expected: "Array<AutoBePrisma.IUniqueIndex>",
                     value: input.uniqueIndexes
-                })) && input.uniqueIndexes.map(((elem, _index14) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".uniqueIndexes[" + _index14 + "]",
+                })) && input.uniqueIndexes.map(((elem, _index12) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".uniqueIndexes[" + _index12 + "]",
                     expected: "AutoBePrisma.IUniqueIndex",
                     value: elem
-                })) && _vo7(elem, _path + ".uniqueIndexes[" + _index14 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".uniqueIndexes[" + _index14 + "]",
+                })) && _vo6(elem, _path + ".uniqueIndexes[" + _index12 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".uniqueIndexes[" + _index12 + "]",
                     expected: "AutoBePrisma.IUniqueIndex",
                     value: elem
                 }))).every((flag => flag)) || _report(_exceptionable, {
@@ -6246,12 +6154,12 @@ const collection$2 = {
                     path: _path + ".plainIndexes",
                     expected: "Array<AutoBePrisma.IPlainIndex>",
                     value: input.plainIndexes
-                })) && input.plainIndexes.map(((elem, _index15) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".plainIndexes[" + _index15 + "]",
+                })) && input.plainIndexes.map(((elem, _index13) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".plainIndexes[" + _index13 + "]",
                     expected: "AutoBePrisma.IPlainIndex",
                     value: elem
-                })) && _vo8(elem, _path + ".plainIndexes[" + _index15 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".plainIndexes[" + _index15 + "]",
+                })) && _vo7(elem, _path + ".plainIndexes[" + _index13 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".plainIndexes[" + _index13 + "]",
                     expected: "AutoBePrisma.IPlainIndex",
                     value: elem
                 }))).every((flag => flag)) || _report(_exceptionable, {
@@ -6262,12 +6170,12 @@ const collection$2 = {
                     path: _path + ".ginIndexes",
                     expected: "Array<AutoBePrisma.IGinIndex>",
                     value: input.ginIndexes
-                })) && input.ginIndexes.map(((elem, _index16) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".ginIndexes[" + _index16 + "]",
+                })) && input.ginIndexes.map(((elem, _index14) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".ginIndexes[" + _index14 + "]",
                     expected: "AutoBePrisma.IGinIndex",
                     value: elem
-                })) && _vo9(elem, _path + ".ginIndexes[" + _index16 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".ginIndexes[" + _index16 + "]",
+                })) && _vo8(elem, _path + ".ginIndexes[" + _index14 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".ginIndexes[" + _index14 + "]",
                     expected: "AutoBePrisma.IGinIndex",
                     value: elem
                 }))).every((flag => flag)) || _report(_exceptionable, {
@@ -6275,7 +6183,7 @@ const collection$2 = {
                     expected: "Array<AutoBePrisma.IGinIndex>",
                     value: input.ginIndexes
                 }) ].every((flag => flag));
-                const _vo3 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
+                const _vo2 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                     path: _path + ".name",
                     expected: 'string & Pattern<"^[a-z][a-z0-9_]*$">',
                     value: input.name
@@ -6292,7 +6200,7 @@ const collection$2 = {
                     expected: "string",
                     value: input.description
                 }) ].every((flag => flag));
-                const _vo4 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
+                const _vo3 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                     path: _path + ".name",
                     expected: 'string & Pattern<"^[a-z][a-z0-9_]*$">',
                     value: input.name
@@ -6312,7 +6220,7 @@ const collection$2 = {
                     path: _path + ".relation",
                     expected: "__type",
                     value: input.relation
-                })) && _vo5(input.relation, _path + ".relation", _exceptionable) || _report(_exceptionable, {
+                })) && _vo4(input.relation, _path + ".relation", _exceptionable) || _report(_exceptionable, {
                     path: _path + ".relation",
                     expected: "__type",
                     value: input.relation
@@ -6325,7 +6233,7 @@ const collection$2 = {
                     expected: "boolean",
                     value: input.nullable
                 }) ].every((flag => flag));
-                const _vo5 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-zA-Z_][a-zA-Z0-9_]*$").test(input.name) || _report(_exceptionable, {
+                const _vo4 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-zA-Z_][a-zA-Z0-9_]*$").test(input.name) || _report(_exceptionable, {
                     path: _path + ".name",
                     expected: 'string & Pattern<"^[a-zA-Z_][a-zA-Z0-9_]*$">',
                     value: input.name
@@ -6338,7 +6246,7 @@ const collection$2 = {
                     expected: "string",
                     value: input.targetModel
                 }) ].every((flag => flag));
-                const _vo6 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
+                const _vo5 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                     path: _path + ".name",
                     expected: 'string & Pattern<"^[a-z][a-z0-9_]*$">',
                     value: input.name
@@ -6359,7 +6267,7 @@ const collection$2 = {
                     expected: "boolean",
                     value: input.nullable
                 }) ].every((flag => flag));
-                const _vo7 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.fieldNames) || _report(_exceptionable, {
+                const _vo6 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.fieldNames) || _report(_exceptionable, {
                     path: _path + ".fieldNames",
                     expected: "(Array<string> & MinItems<1> & UniqueItems<true>)",
                     value: input.fieldNames
@@ -6371,8 +6279,8 @@ const collection$2 = {
                     path: _path + ".fieldNames",
                     expected: "Array<> & UniqueItems<true>",
                     value: input.fieldNames
-                })) && input.fieldNames.map(((elem, _index17) => "string" === typeof elem || _report(_exceptionable, {
-                    path: _path + ".fieldNames[" + _index17 + "]",
+                })) && input.fieldNames.map(((elem, _index15) => "string" === typeof elem || _report(_exceptionable, {
+                    path: _path + ".fieldNames[" + _index15 + "]",
                     expected: "string",
                     value: elem
                 }))).every((flag => flag))) || _report(_exceptionable, {
@@ -6384,7 +6292,7 @@ const collection$2 = {
                     expected: "true",
                     value: input.unique
                 }) ].every((flag => flag));
-                const _vo8 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.fieldNames) || _report(_exceptionable, {
+                const _vo7 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.fieldNames) || _report(_exceptionable, {
                     path: _path + ".fieldNames",
                     expected: "(Array<string> & MinItems<1> & UniqueItems<true>)",
                     value: input.fieldNames
@@ -6396,8 +6304,8 @@ const collection$2 = {
                     path: _path + ".fieldNames",
                     expected: "Array<> & UniqueItems<true>",
                     value: input.fieldNames
-                })) && input.fieldNames.map(((elem, _index18) => "string" === typeof elem || _report(_exceptionable, {
-                    path: _path + ".fieldNames[" + _index18 + "]",
+                })) && input.fieldNames.map(((elem, _index16) => "string" === typeof elem || _report(_exceptionable, {
+                    path: _path + ".fieldNames[" + _index16 + "]",
                     expected: "string",
                     value: elem
                 }))).every((flag => flag))) || _report(_exceptionable, {
@@ -6405,7 +6313,7 @@ const collection$2 = {
                     expected: "(Array<string> & MinItems<1> & UniqueItems<true>)",
                     value: input.fieldNames
                 }) ].every((flag => flag));
-                const _vo9 = (input, _path, _exceptionable = true) => [ "string" === typeof input.fieldName || _report(_exceptionable, {
+                const _vo8 = (input, _path, _exceptionable = true) => [ "string" === typeof input.fieldName || _report(_exceptionable, {
                     path: _path + ".fieldName",
                     expected: "string",
                     value: input.fieldName
@@ -6462,26 +6370,53 @@ const collection$2 = {
                 properties: {
                     planning: {
                         type: "string",
-                        title: "Detailed execution plan for fixing AutoBePrisma validation errors",
-                        description: "Detailed execution plan for fixing AutoBePrisma validation errors.\n\n🎯 Purpose: Enable systematic reasoning and step-by-step error resolution\napproach for structured schema validation issues\n\n📋 Required Planning Content:\n\n1. **Error Analysis Summary**\n\n   - List all validation errors from IAutoBePrismaValidation.IError[] array\n   - Categorize errors by type (duplications, references, types, indexes)\n   - Identify root causes and error interdependencies\n2. **Fix Strategy Overview**\n\n   - Prioritize fixes based on dependencies (fix duplications first)\n   - Outline minimal changes needed for each validation error\n   - Identify potential impact on other models/relationships\n3. **Step-by-Step Fix Plan**\n\n   - Model-by-model modification plan with specific changes\n   - Exact field additions, removals, or renames required\n   - Reference updates needed for renamed elements\n   - Index corrections to comply with validation rules\n4. **Preservation Checklist**\n\n   - Confirm which descriptions and business logic must be preserved\n   - List relationships and constraints to maintain unchanged\n   - Identify cross-model dependencies that must remain intact\n5. **Risk Assessment**\n\n   - Potential side effects of each planned fix\n   - Validation points to check after applying corrections\n   - Ensure no new validation errors are introduced\n\n💡 Example Planning Structure:\n\n    ## Error Analysis\n    - Error 1: Duplicate field 'name' in shopping_customers model\n    - Error 2: Invalid targetModel 'shopping_customer' should be 'shopping_customers'\n\n    ## Fix Strategy\n    1. Remove duplicate 'name' field (keep the more detailed one)\n    2. Update foreign key references to use correct plural model name\n\n    ## Detailed Steps\n    1. shopping_customers model: Remove second 'name' field from plainFields\n    2. shopping_orders model: Update targetModel from 'shopping_customer' to 'shopping_customers'\n\n    ## Preservation Notes\n    - Keep business descriptions for remaining 'name' field\n    - Maintain all relationship semantics\n    - Preserve all indexes and constraints"
+                        description: "Detailed execution plan for fixing `AutoBePrisma` validation errors in\nspecific models.\n\n🎯 Purpose: Enable systematic reasoning and step-by-step error resolution\napproach for targeted model validation issues\n\n📋 Required Planning Content:\n\n1. **Error Scope Analysis**\n\n   - List all validation errors from IAutoBePrismaValidation.IError[] array\n   - Extract unique table names from errors to identify affected models\n   - Categorize errors by type (field duplications, references, types, indexes)\n   - Identify which models need correction vs. which 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 (if any) without modifying non-error\n        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\n\n💡 Example Planning Structure:\n\n    ## Error Scope\n    - Target Models: shopping_customers, shopping_orders (2 models only)\n    - Unchanged Models: All others remain in original schema\n\n    ## Targeted Fixes\n    - shopping_customers: Remove duplicate 'email' field\n    - shopping_orders: Update targetModel reference to 'shopping_customers'\n\n    ## Output Scope\n    - Return: Only shopping_customers and shopping_orders models\n    - Preserve: All other models unchanged in original schema\n\n    ## Cross-Model Impact\n    - Verify: shopping_orders still references shopping_customers correctly\n    - No changes needed in other models referencing these"
                     },
-                    files: {
+                    models: {
                         type: "array",
                         items: {
                             type: "object",
                             properties: {
-                                filename: {
+                                name: {
                                     type: "string",
-                                    pattern: "^[a-zA-Z0-9._-]+\\.prisma$",
-                                    title: "Name of the schema file to be generated",
-                                    description: 'Name of the schema file to be generated.\n\nShould follow the naming convention: "schema-{number}-{domain}.prisma"\nExamples: "schema-02-systematic.prisma", "schema-03-actors.prisma" The\nnumber indicates the dependency order for schema generation.'
+                                    pattern: "^[a-z][a-z0-9_]*$",
+                                    title: "Name of the Prisma model (database table name)",
+                                    description: 'Name of the Prisma model (database table name).\n\nShould follow snake_case convention with domain prefix. Examples:\n"shopping_customers", "shopping_sale_snapshots", "bbs_articles"\nMaterialized views use "mv_" prefix: "mv_shopping_sale_last_snapshots"'
                                 },
-                                namespace: {
+                                description: {
                                     type: "string",
-                                    title: "Business domain namespace that groups related models",
-                                    description: 'Business domain namespace that groups related models.\n\nUsed in Prisma documentation comments as "@\\namespace directive".\nExamples from uploaded schemas: "Systematic", "Actors", "Sales", "Carts",\n"Orders", "Coupons", "Coins", "Inquiries", "Favorites", "Articles"'
+                                    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 Example:\n  "Customer information, but not a person but a **connection** basis..."'
+                                },
+                                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'
+                                },
+                                primaryField: {
+                                    type: "object",
+                                    properties: {
+                                        name: {
+                                            type: "string",
+                                            pattern: "^[a-z][a-z0-9_]*$",
+                                            title: "Name of the primary key field",
+                                            description: 'Name of the primary key field.\n\nConsistently named "id" across all models in the uploaded schemas.\nRepresents the unique identifier for each record in the table.'
+                                        },
+                                        type: {
+                                            type: "string",
+                                            enum: [ "uuid" ],
+                                            title: "Data type of the primary key field",
+                                            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.'
+                                        },
+                                        description: {
+                                            type: "string",
+                                            title: "Description of the primary key field's purpose",
+                                            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.'
+                                        }
+                                    },
+                                    required: [ "name", "type", "description" ],
+                                    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.\n\n------------------------------\n\nDescription of the current {@link AutoBePrisma.IPrimaryField} type:\n\n> Interface representing the primary key field of a Prisma model.\n> \n> All models in the uploaded schemas use UUID as primary key for better\n> distributed system compatibility and security (no sequential ID exposure).',
+                                    additionalProperties: false
                                 },
-                                models: {
+                                foreignFields: {
                                     type: "array",
                                     items: {
                                         type: "object",
@@ -6489,281 +6424,199 @@ const collection$2 = {
                                             name: {
                                                 type: "string",
                                                 pattern: "^[a-z][a-z0-9_]*$",
-                                                title: "Name of the Prisma model (database table name)",
-                                                description: 'Name of the Prisma model (database table name).\n\nShould follow snake_case convention with domain prefix. Examples:\n"shopping_customers", "shopping_sale_snapshots", "bbs_articles"\nMaterialized views use "mv_" prefix: "mv_shopping_sale_last_snapshots"'
+                                                title: "Name of the foreign key field",
+                                                description: 'Name of the foreign key field.\n\nFollows convention: "{target_model_name_without_prefix}_id" Examples:\n"shopping_customer_id", "bbs_article_id", "attachment_file_id" For\nself-references: "parent_id" (e.g., in hierarchical structures)'
                                             },
-                                            description: {
+                                            type: {
                                                 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 Example:\n  "Customer information, but not a person but a **connection** basis..."'
+                                                enum: [ "uuid" ],
+                                                title: "Data type of the foreign key field",
+                                                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.'
                                             },
-                                            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: {
+                                                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.'
                                             },
-                                            primaryField: {
+                                            relation: {
                                                 type: "object",
                                                 properties: {
                                                     name: {
                                                         type: "string",
-                                                        pattern: "^[a-z][a-z0-9_]*$",
-                                                        title: "Name of the primary key field",
-                                                        description: 'Name of the primary key field.\n\nConsistently named "id" across all models in the uploaded schemas.\nRepresents the unique identifier for each record in the table.'
-                                                    },
-                                                    type: {
-                                                        type: "string",
-                                                        enum: [ "uuid" ],
-                                                        title: "Data type of the primary key field",
-                                                        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.'
+                                                        pattern: "^[a-zA-Z_][a-zA-Z0-9_]*$",
+                                                        title: "Name of the relation property in the Prisma model",
+                                                        description: 'Name of the relation property in the Prisma model.\n\nUsed to access the related model instance. Usually a descriptive name\nof the relationship. Examples: "customer", "channel", "parent",\n"snapshot"'
                                                     },
-                                                    description: {
+                                                    targetModel: {
                                                         type: "string",
-                                                        title: "Description of the primary key field's purpose",
-                                                        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.'
+                                                        title: "Name of the target model being referenced",
+                                                        description: 'Name of the target model being referenced.\n\nMust match exactly with an existing model name in the schema. Examples:\n"shopping_customers", "shopping_channels", "bbs_articles"'
                                                     }
                                                 },
-                                                required: [ "name", "type", "description" ],
-                                                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.\n\n------------------------------\n\nDescription of the current {@link AutoBePrisma.IPrimaryField} type:\n\n> Interface representing the primary key field of a Prisma model.\n> \n> All models in the uploaded schemas use UUID as primary key for better\n> distributed system compatibility and security (no sequential ID exposure).',
+                                                required: [ "name", "targetModel" ],
+                                                title: "Prisma relation configuration defining the association details",
+                                                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.",
                                                 additionalProperties: false
                                             },
-                                            foreignFields: {
-                                                type: "array",
-                                                items: {
-                                                    type: "object",
-                                                    properties: {
-                                                        name: {
-                                                            type: "string",
-                                                            pattern: "^[a-z][a-z0-9_]*$",
-                                                            title: "Name of the foreign key field",
-                                                            description: 'Name of the foreign key field.\n\nFollows convention: "{target_model_name_without_prefix}_id" Examples:\n"shopping_customer_id", "bbs_article_id", "attachment_file_id" For\nself-references: "parent_id" (e.g., in hierarchical structures)'
-                                                        },
-                                                        type: {
-                                                            type: "string",
-                                                            enum: [ "uuid" ],
-                                                            title: "Data type of the foreign key field",
-                                                            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.'
-                                                        },
-                                                        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.'
-                                                        },
-                                                        relation: {
-                                                            type: "object",
-                                                            properties: {
-                                                                name: {
-                                                                    type: "string",
-                                                                    pattern: "^[a-zA-Z_][a-zA-Z0-9_]*$",
-                                                                    title: "Name of the relation property in the Prisma model",
-                                                                    description: 'Name of the relation property in the Prisma model.\n\nUsed to access the related model instance. Usually a descriptive name\nof the relationship. Examples: "customer", "channel", "parent",\n"snapshot"'
-                                                                },
-                                                                targetModel: {
-                                                                    type: "string",
-                                                                    title: "Name of the target model being referenced",
-                                                                    description: 'Name of the target model being referenced.\n\nMust match exactly with an existing model name in the schema. Examples:\n"shopping_customers", "shopping_channels", "bbs_articles"'
-                                                                }
-                                                            },
-                                                            required: [ "name", "targetModel" ],
-                                                            title: "Prisma relation configuration defining the association details",
-                                                            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.",
-                                                            additionalProperties: false
-                                                        },
-                                                        unique: {
-                                                            type: "boolean",
-                                                            title: "Whether this foreign key has a unique constraint",
-                                                            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."
-                                                        },
-                                                        nullable: {
-                                                            type: "boolean",
-                                                            title: "Whether this foreign key can be null (optional relationship)",
-                                                            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."
-                                                        }
-                                                    },
-                                                    required: [ "name", "type", "description", "relation", "unique", "nullable" ],
-                                                    description: "Description of the current {@link AutoBePrisma.IForeignField} type:\n\n> Interface representing a foreign key field that establishes relationships\n> between models.\n> \n> Foreign keys create associations between models, enabling relational data\n> modeling. They can represent 1:1, 1:N, or participate in M:N relationships\n> through junction tables.",
-                                                    additionalProperties: false
-                                                },
-                                                title: "Array of foreign key fields that reference other models",
-                                                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."
+                                            unique: {
+                                                type: "boolean",
+                                                title: "Whether this foreign key has a unique constraint",
+                                                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."
                                             },
-                                            plainFields: {
-                                                type: "array",
-                                                items: {
-                                                    type: "object",
-                                                    properties: {
-                                                        name: {
-                                                            type: "string",
-                                                            pattern: "^[a-z][a-z0-9_]*$",
-                                                            title: "Name of the field in the database table",
-                                                            description: "Name of the field in the database table.\n\nShould use snake_case convention. Common patterns from uploaded schemas:\n\n- Timestamps: created_at, updated_at, deleted_at, opened_at, closed_at\n- Identifiers: code, name, nickname, title\n- Business data: value, quantity, price, volume, balance\n- Flags: primary, required, exclusive, secret, multiplicative"
-                                                        },
-                                                        type: {
-                                                            type: "string",
-                                                            enum: [ "string", "boolean", "uuid", "uri", "int", "double", "datetime" ],
-                                                            title: "Data type of the field for Prisma schema generation",
-                                                            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- Date: Date-only values (rare, mostly for business dates)\n- Datetime: Timestamp fields with date and time"
-                                                        },
-                                                        description: {
-                                                            type: "string",
-                                                            title: "Description explaining the business purpose and usage of this field",
-                                                            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 Example: "Amount of cash payment." or\n  "Whether the unit is required or not."'
-                                                        },
-                                                        nullable: {
-                                                            type: "boolean",
-                                                            title: "Whether this field can contain null values",
-                                                            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."
-                                                        }
-                                                    },
-                                                    required: [ "name", "type", "description", "nullable" ],
-                                                    description: "Description of the current {@link AutoBePrisma.IPlainField} type:\n\n> Interface representing a regular data field that stores business\n> information.\n> \n> These fields contain the actual business data like names, amounts,\n> timestamps, flags, descriptions, and other domain-specific information.",
-                                                    additionalProperties: false
-                                                },
-                                                title: "Array of regular data fields that don't reference other models",
-                                                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."
+                                            nullable: {
+                                                type: "boolean",
+                                                title: "Whether this foreign key can be null (optional relationship)",
+                                                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."
+                                            }
+                                        },
+                                        required: [ "name", "type", "description", "relation", "unique", "nullable" ],
+                                        description: "Description of the current {@link AutoBePrisma.IForeignField} type:\n\n> Interface representing a foreign key field that establishes relationships\n> between models.\n> \n> Foreign keys create associations between models, enabling relational data\n> modeling. They can represent 1:1, 1:N, or participate in M:N relationships\n> through junction tables.",
+                                        additionalProperties: false
+                                    },
+                                    title: "Array of foreign key fields that reference other models",
+                                    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."
+                                },
+                                plainFields: {
+                                    type: "array",
+                                    items: {
+                                        type: "object",
+                                        properties: {
+                                            name: {
+                                                type: "string",
+                                                pattern: "^[a-z][a-z0-9_]*$",
+                                                title: "Name of the field in the database table",
+                                                description: "Name of the field in the database table.\n\nShould use snake_case convention. Common patterns from uploaded schemas:\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"
                                             },
-                                            uniqueIndexes: {
-                                                type: "array",
-                                                items: {
-                                                    type: "object",
-                                                    properties: {
-                                                        fieldNames: {
-                                                            type: "array",
-                                                            items: {
-                                                                type: "string"
-                                                            },
-                                                            minItems: 1,
-                                                            uniqueItems: true,
-                                                            title: "Array of field names that together form the unique constraint",
-                                                            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"]'
-                                                        },
-                                                        unique: {
-                                                            type: "boolean",
-                                                            enum: [ true ],
-                                                            title: "Explicit marker indicating this is a unique index",
-                                                            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".'
-                                                        }
-                                                    },
-                                                    required: [ "fieldNames", "unique" ],
-                                                    description: "Description of the current {@link AutoBePrisma.IUniqueIndex} type:\n\n> Interface representing a unique index constraint on one or more fields.\n> \n> Unique indexes enforce data integrity by ensuring no duplicate values exist\n> for the specified field combination. Essential for business rules that\n> require uniqueness like email addresses, codes, or composite keys.",
-                                                    additionalProperties: false
-                                                },
-                                                title: "Array of unique indexes for enforcing data integrity constraints",
-                                                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)."
+                                            type: {
+                                                type: "string",
+                                                enum: [ "string", "boolean", "uuid", "uri", "int", "double", "datetime" ],
+                                                title: "Data type of the field for Prisma schema generation",
+                                                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- Date: Date-only values (rare, mostly for business dates)\n- Datetime: Timestamp fields with date and time"
+                                            },
+                                            description: {
+                                                type: "string",
+                                                title: "Description explaining the business purpose and usage of this field",
+                                                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 Example: "Amount of cash payment." or\n  "Whether the unit is required or not."'
                                             },
-                                            plainIndexes: {
+                                            nullable: {
+                                                type: "boolean",
+                                                title: "Whether this field can contain null values",
+                                                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."
+                                            }
+                                        },
+                                        required: [ "name", "type", "description", "nullable" ],
+                                        description: "Description of the current {@link AutoBePrisma.IPlainField} type:\n\n> Interface representing a regular data field that stores business\n> information.\n> \n> These fields contain the actual business data like names, amounts,\n> timestamps, flags, descriptions, and other domain-specific information.",
+                                        additionalProperties: false
+                                    },
+                                    title: "Array of regular data fields that don't reference other models",
+                                    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."
+                                },
+                                uniqueIndexes: {
+                                    type: "array",
+                                    items: {
+                                        type: "object",
+                                        properties: {
+                                            fieldNames: {
                                                 type: "array",
                                                 items: {
-                                                    type: "object",
-                                                    properties: {
-                                                        fieldNames: {
-                                                            type: "array",
-                                                            items: {
-                                                                type: "string"
-                                                            },
-                                                            minItems: 1,
-                                                            uniqueItems: true,
-                                                            title: "Array of field names to include in the performance index",
-                                                            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"]'
-                                                        }
-                                                    },
-                                                    required: [ "fieldNames" ],
-                                                    description: "Description of the current {@link AutoBePrisma.IPlainIndex} type:\n\n> Interface representing a regular (non-unique) index for query performance.\n> \n> Regular indexes speed up database queries by creating optimized data\n> structures for common search patterns. Essential for foreign keys, date\n> ranges, and frequently filtered fields.",
-                                                    additionalProperties: false
+                                                    type: "string"
                                                 },
-                                                title: "Array of regular indexes for query performance optimization",
-                                                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."
+                                                minItems: 1,
+                                                uniqueItems: true,
+                                                title: "Array of field names that together form the unique constraint",
+                                                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"]'
                                             },
-                                            ginIndexes: {
+                                            unique: {
+                                                type: "boolean",
+                                                enum: [ true ],
+                                                title: "Explicit marker indicating this is a unique index",
+                                                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".'
+                                            }
+                                        },
+                                        required: [ "fieldNames", "unique" ],
+                                        description: "Description of the current {@link AutoBePrisma.IUniqueIndex} type:\n\n> Interface representing a unique index constraint on one or more fields.\n> \n> Unique indexes enforce data integrity by ensuring no duplicate values exist\n> for the specified field combination. Essential for business rules that\n> require uniqueness like email addresses, codes, or composite keys.",
+                                        additionalProperties: false
+                                    },
+                                    title: "Array of unique indexes for enforcing data integrity constraints",
+                                    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)."
+                                },
+                                plainIndexes: {
+                                    type: "array",
+                                    items: {
+                                        type: "object",
+                                        properties: {
+                                            fieldNames: {
                                                 type: "array",
                                                 items: {
-                                                    type: "object",
-                                                    properties: {
-                                                        fieldName: {
-                                                            type: "string",
-                                                            title: "Name of the text field to index for full-text search capabilities",
-                                                            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.'
-                                                        }
-                                                    },
-                                                    required: [ "fieldName" ],
-                                                    description: "Description of the current {@link AutoBePrisma.IGinIndex} type:\n\n> Interface representing a GIN (Generalized Inverted Index) for full-text\n> search.\n> \n> GIN indexes enable advanced PostgreSQL text search capabilities including\n> fuzzy matching and partial text search using trigram operations. Essential\n> for user-facing search features on text content.",
-                                                    additionalProperties: false
+                                                    type: "string"
                                                 },
-                                                title: "Array of GIN (Generalized Inverted Index) indexes for full-text search",
-                                                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."
+                                                minItems: 1,
+                                                uniqueItems: true,
+                                                title: "Array of field names to include in the performance index",
+                                                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"]'
+                                            }
+                                        },
+                                        required: [ "fieldNames" ],
+                                        description: "Description of the current {@link AutoBePrisma.IPlainIndex} type:\n\n> Interface representing a regular (non-unique) index for query performance.\n> \n> Regular indexes speed up database queries by creating optimized data\n> structures for common search patterns. Essential for foreign keys, date\n> ranges, and frequently filtered fields.",
+                                        additionalProperties: false
+                                    },
+                                    title: "Array of regular indexes for query performance optimization",
+                                    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."
+                                },
+                                ginIndexes: {
+                                    type: "array",
+                                    items: {
+                                        type: "object",
+                                        properties: {
+                                            fieldName: {
+                                                type: "string",
+                                                title: "Name of the text field to index for full-text search capabilities",
+                                                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.'
                                             }
                                         },
-                                        required: [ "name", "description", "material", "primaryField", "foreignFields", "plainFields", "uniqueIndexes", "plainIndexes", "ginIndexes" ],
-                                        description: "Description of the current {@link AutoBePrisma.IModel} type:\n\n> Interface representing a single Prisma model (database table).\n> \n> Based 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_)",
+                                        required: [ "fieldName" ],
+                                        description: "Description of the current {@link AutoBePrisma.IGinIndex} type:\n\n> Interface representing a GIN (Generalized Inverted Index) for full-text\n> search.\n> \n> GIN indexes enable advanced PostgreSQL text search capabilities including\n> fuzzy matching and partial text search using trigram operations. Essential\n> for user-facing search features on text content.",
                                         additionalProperties: false
                                     },
-                                    title: "Array of Prisma models (database tables) within this domain",
-                                    description: "Array of Prisma models (database tables) within this domain.\n\nEach model represents a business entity or concept within the namespace.\nModels can reference each other through foreign key relationships."
+                                    title: "Array of GIN (Generalized Inverted Index) indexes for full-text search",
+                                    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."
                                 }
                             },
-                            required: [ "filename", "namespace", "models" ],
-                            description: "Description of the current {@link AutoBePrisma.IFile} type:\n\n> Interface representing a single Prisma schema file within the application.\n> \n> Each file focuses on a specific business domain and contains related\n> models. File organization follows domain-driven design principles as seen\n> in the uploaded schemas.",
+                            required: [ "name", "description", "material", "primaryField", "foreignFields", "plainFields", "uniqueIndexes", "plainIndexes", "ginIndexes" ],
+                            description: "Description of the current {@link AutoBePrisma.IModel} type:\n\n> Interface representing a single Prisma model (database table).\n> \n> Based 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_)",
                             additionalProperties: false
                         },
-                        description: "Original AutoBePrisma.IApplication structure that contains validation\nerrors and needs correction.\n\n📥 Input Structure:\n\n- Complete IApplication with files array containing validation errors\n- Each file contains models with potential structural issues\n- Errors may include duplications, invalid references, or constraint\n  violations\n\n🔍 Expected Validation Issues:\n\n- Duplicate model names across files\n- Duplicate field/relation names within models\n- Invalid foreign key references to non-existent models\n- Single foreign key fields in index arrays\n- Non-plural model names or invalid naming conventions\n\n📝 Application Content Analysis:\n\n- All models with their complete field definitions\n- All relationships with targetModel and targetfield configurations\n- All indexes (unique, plain, GIN) with field references\n- All business descriptions and requirement mappings\n- Cross-file model references and dependencies\n\n⚠️ Processing Notes:\n\n- Structure may contain validation errors that prevent code generation\n- Some models might reference non-existent targets\n- Field names might violate naming conventions\n- Index configurations might include forbidden single foreign keys\n- Business logic and descriptions must be preserved during fixes"
+                        description: "ONLY the specific models that contain validation errors and need\ncorrection.\n\n📥 Input Structure:\n\n- Contains ONLY models mentioned in IAutoBePrismaValidation.IError[] array\n- Each model has specific validation errors that need targeted correction\n- Models not mentioned in errors are excluded from this input\n- Represents minimal scope for error correction\n\n🔍 Expected Validation Issues (Model-Specific):\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\n📝 Model Content Analysis (Targeted Scope):\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\n⚠️ Processing Notes (Focused Approach):\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\n\n🎯 Correction Scope:\n\n- Fix validation errors within these specific models\n- Update internal model structure (fields, relations, indexes)\n- Correct references to external models (without modifying targets)\n- Maintain compatibility with unchanged models in the full schema\n- Return corrected versions of ONLY these models"
                     }
                 },
-                required: [ "planning", "files" ],
+                required: [ "planning", "models" ],
                 description: "Current Type: {@link IModifyPrismaSchemaFilesProps}",
                 additionalProperties: false
             },
-            description: "Fixes validation errors in AutoBePrisma.IApplication structure while\npreserving ALL existing business logic and model descriptions.\n\n## Core Rules\n\n1. Fix ONLY validation errors - never remove business descriptions\n2. Apply minimal changes - preserve original design intent\n3. Return COMPLETE corrected structure - no data loss allowed\n4. Maintain referential integrity across all models\n\n## Preservation Requirements\n\n- Keep ALL model and field descriptions\n- Keep business logic and architectural patterns\n- Maintain relationship semantics and cardinality\n- Remove descriptions only when removing duplicate elements\n\n## Fix Strategy\n\n- Resolve structural validation errors without changing business intent\n- Remove duplicate fields/relations while preserving most appropriate ones\n- Fix invalid references and type mismatches\n- Ensure naming conventions and index rules compliance",
+            description: "Fixes validation errors in specific AutoBePrisma models while preserving\nALL existing business logic and model descriptions.\n\n## Core Rules\n\n1. Fix ONLY validation errors in provided models - never remove business\n   descriptions\n2. Apply minimal changes to error models only - preserve original design\n   intent\n3. Return ONLY corrected models - unchanged models remain in original schema\n4. Maintain referential integrity with unchanged models\n\n## Targeted Scope\n\n- Process ONLY models with validation errors from IError[] array\n- Exclude models without errors from processing and output\n- Minimize context usage by returning corrected models only\n- Preserve unchanged models in their original state\n\n## Fix Strategy\n\n- Resolve validation errors within specific models only\n- Fix field duplications, invalid references, and type mismatches\n- Update cross-model references without modifying target models\n- Ensure naming conventions and index rules compliance in corrected models",
             validate: (() => {
-                const _io0 = input => "string" === typeof input.planning && (Array.isArray(input.files) && input.files.every((elem => "object" === typeof elem && null !== elem && _io1(elem))));
-                const _io1 = input => "string" === typeof input.filename && RegExp("^[a-zA-Z0-9._-]+\\.prisma$").test(input.filename) && "string" === typeof input.namespace && (Array.isArray(input.models) && input.models.every((elem => "object" === typeof elem && null !== elem && _io2(elem))));
-                const _io2 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "string" === typeof input.description && "boolean" === typeof input.material && ("object" === typeof input.primaryField && null !== input.primaryField && _io3(input.primaryField)) && (Array.isArray(input.foreignFields) && input.foreignFields.every((elem => "object" === typeof elem && null !== elem && _io4(elem)))) && (Array.isArray(input.plainFields) && input.plainFields.every((elem => "object" === typeof elem && null !== elem && _io6(elem)))) && (Array.isArray(input.uniqueIndexes) && input.uniqueIndexes.every((elem => "object" === typeof elem && null !== elem && _io7(elem)))) && (Array.isArray(input.plainIndexes) && input.plainIndexes.every((elem => "object" === typeof elem && null !== elem && _io8(elem)))) && (Array.isArray(input.ginIndexes) && input.ginIndexes.every((elem => "object" === typeof elem && null !== elem && _io9(elem))));
-                const _io3 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "uuid" === input.type && "string" === typeof input.description;
-                const _io4 = 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 && _io5(input.relation)) && "boolean" === typeof input.unique && "boolean" === typeof input.nullable;
-                const _io5 = input => "string" === typeof input.name && RegExp("^[a-zA-Z_][a-zA-Z0-9_]*$").test(input.name) && "string" === typeof input.targetModel;
-                const _io6 = 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 _io7 = 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 _io8 = input => Array.isArray(input.fieldNames) && (1 <= input.fieldNames.length && __typia_transform__isUniqueItems._isUniqueItems(input.fieldNames) && input.fieldNames.every((elem => "string" === typeof elem)));
-                const _io9 = input => "string" === typeof input.fieldName;
+                const _io0 = input => "string" === typeof input.planning && (Array.isArray(input.models) && input.models.every((elem => "object" === typeof elem && null !== elem && _io1(elem))));
+                const _io1 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "string" === typeof input.description && "boolean" === typeof input.material && ("object" === typeof input.primaryField && null !== input.primaryField && _io2(input.primaryField)) && (Array.isArray(input.foreignFields) && input.foreignFields.every((elem => "object" === typeof elem && null !== elem && _io3(elem)))) && (Array.isArray(input.plainFields) && input.plainFields.every((elem => "object" === typeof elem && null !== elem && _io5(elem)))) && (Array.isArray(input.uniqueIndexes) && input.uniqueIndexes.every((elem => "object" === typeof elem && null !== elem && _io6(elem)))) && (Array.isArray(input.plainIndexes) && input.plainIndexes.every((elem => "object" === typeof elem && null !== elem && _io7(elem)))) && (Array.isArray(input.ginIndexes) && input.ginIndexes.every((elem => "object" === typeof elem && null !== elem && _io8(elem))));
+                const _io2 = input => "string" === typeof input.name && RegExp("^[a-z][a-z0-9_]*$").test(input.name) && "uuid" === input.type && "string" === typeof input.description;
+                const _io3 = 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 && _io4(input.relation)) && "boolean" === typeof input.unique && "boolean" === typeof input.nullable;
+                const _io4 = input => "string" === typeof input.name && RegExp("^[a-zA-Z_][a-zA-Z0-9_]*$").test(input.name) && "string" === typeof input.targetModel;
+                const _io5 = 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 _io6 = 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 _io7 = input => Array.isArray(input.fieldNames) && (1 <= input.fieldNames.length && __typia_transform__isUniqueItems._isUniqueItems(input.fieldNames) && input.fieldNames.every((elem => "string" === typeof elem)));
+                const _io8 = input => "string" === typeof input.fieldName;
                 const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.planning || _report(_exceptionable, {
                     path: _path + ".planning",
                     expected: "string",
                     value: input.planning
-                }), (Array.isArray(input.files) || _report(_exceptionable, {
-                    path: _path + ".files",
-                    expected: "Array<AutoBePrisma.IFile>",
-                    value: input.files
-                })) && input.files.map(((elem, _index10) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".files[" + _index10 + "]",
-                    expected: "AutoBePrisma.IFile",
-                    value: elem
-                })) && _vo1(elem, _path + ".files[" + _index10 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".files[" + _index10 + "]",
-                    expected: "AutoBePrisma.IFile",
-                    value: elem
-                }))).every((flag => flag)) || _report(_exceptionable, {
-                    path: _path + ".files",
-                    expected: "Array<AutoBePrisma.IFile>",
-                    value: input.files
-                }) ].every((flag => flag));
-                const _vo1 = (input, _path, _exceptionable = true) => [ "string" === typeof input.filename && (RegExp("^[a-zA-Z0-9._-]+\\.prisma$").test(input.filename) || _report(_exceptionable, {
-                    path: _path + ".filename",
-                    expected: 'string & Pattern<"^[a-zA-Z0-9._-]+\\\\.prisma$">',
-                    value: input.filename
-                })) || _report(_exceptionable, {
-                    path: _path + ".filename",
-                    expected: '(string & Pattern<"^[a-zA-Z0-9._-]+\\\\.prisma$">)',
-                    value: input.filename
-                }), "string" === typeof input.namespace || _report(_exceptionable, {
-                    path: _path + ".namespace",
-                    expected: "string",
-                    value: input.namespace
                 }), (Array.isArray(input.models) || _report(_exceptionable, {
                     path: _path + ".models",
                     expected: "Array<AutoBePrisma.IModel>",
                     value: input.models
-                })) && input.models.map(((elem, _index11) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".models[" + _index11 + "]",
+                })) && input.models.map(((elem, _index9) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".models[" + _index9 + "]",
                     expected: "AutoBePrisma.IModel",
                     value: elem
-                })) && _vo2(elem, _path + ".models[" + _index11 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".models[" + _index11 + "]",
+                })) && _vo1(elem, _path + ".models[" + _index9 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".models[" + _index9 + "]",
                     expected: "AutoBePrisma.IModel",
                     value: elem
                 }))).every((flag => flag)) || _report(_exceptionable, {
@@ -6771,7 +6624,7 @@ const collection$2 = {
                     expected: "Array<AutoBePrisma.IModel>",
                     value: input.models
                 }) ].every((flag => flag));
-                const _vo2 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
+                const _vo1 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                     path: _path + ".name",
                     expected: 'string & Pattern<"^[a-z][a-z0-9_]*$">',
                     value: input.name
@@ -6791,7 +6644,7 @@ const collection$2 = {
                     path: _path + ".primaryField",
                     expected: "AutoBePrisma.IPrimaryField",
                     value: input.primaryField
-                })) && _vo3(input.primaryField, _path + ".primaryField", _exceptionable) || _report(_exceptionable, {
+                })) && _vo2(input.primaryField, _path + ".primaryField", _exceptionable) || _report(_exceptionable, {
                     path: _path + ".primaryField",
                     expected: "AutoBePrisma.IPrimaryField",
                     value: input.primaryField
@@ -6799,12 +6652,12 @@ const collection$2 = {
                     path: _path + ".foreignFields",
                     expected: "Array<AutoBePrisma.IForeignField>",
                     value: input.foreignFields
-                })) && input.foreignFields.map(((elem, _index12) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".foreignFields[" + _index12 + "]",
+                })) && input.foreignFields.map(((elem, _index10) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".foreignFields[" + _index10 + "]",
                     expected: "AutoBePrisma.IForeignField",
                     value: elem
-                })) && _vo4(elem, _path + ".foreignFields[" + _index12 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".foreignFields[" + _index12 + "]",
+                })) && _vo3(elem, _path + ".foreignFields[" + _index10 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".foreignFields[" + _index10 + "]",
                     expected: "AutoBePrisma.IForeignField",
                     value: elem
                 }))).every((flag => flag)) || _report(_exceptionable, {
@@ -6815,12 +6668,12 @@ const collection$2 = {
                     path: _path + ".plainFields",
                     expected: "Array<AutoBePrisma.IPlainField>",
                     value: input.plainFields
-                })) && input.plainFields.map(((elem, _index13) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".plainFields[" + _index13 + "]",
+                })) && input.plainFields.map(((elem, _index11) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".plainFields[" + _index11 + "]",
                     expected: "AutoBePrisma.IPlainField",
                     value: elem
-                })) && _vo6(elem, _path + ".plainFields[" + _index13 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".plainFields[" + _index13 + "]",
+                })) && _vo5(elem, _path + ".plainFields[" + _index11 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".plainFields[" + _index11 + "]",
                     expected: "AutoBePrisma.IPlainField",
                     value: elem
                 }))).every((flag => flag)) || _report(_exceptionable, {
@@ -6831,12 +6684,12 @@ const collection$2 = {
                     path: _path + ".uniqueIndexes",
                     expected: "Array<AutoBePrisma.IUniqueIndex>",
                     value: input.uniqueIndexes
-                })) && input.uniqueIndexes.map(((elem, _index14) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".uniqueIndexes[" + _index14 + "]",
+                })) && input.uniqueIndexes.map(((elem, _index12) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".uniqueIndexes[" + _index12 + "]",
                     expected: "AutoBePrisma.IUniqueIndex",
                     value: elem
-                })) && _vo7(elem, _path + ".uniqueIndexes[" + _index14 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".uniqueIndexes[" + _index14 + "]",
+                })) && _vo6(elem, _path + ".uniqueIndexes[" + _index12 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".uniqueIndexes[" + _index12 + "]",
                     expected: "AutoBePrisma.IUniqueIndex",
                     value: elem
                 }))).every((flag => flag)) || _report(_exceptionable, {
@@ -6847,12 +6700,12 @@ const collection$2 = {
                     path: _path + ".plainIndexes",
                     expected: "Array<AutoBePrisma.IPlainIndex>",
                     value: input.plainIndexes
-                })) && input.plainIndexes.map(((elem, _index15) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".plainIndexes[" + _index15 + "]",
+                })) && input.plainIndexes.map(((elem, _index13) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".plainIndexes[" + _index13 + "]",
                     expected: "AutoBePrisma.IPlainIndex",
                     value: elem
-                })) && _vo8(elem, _path + ".plainIndexes[" + _index15 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".plainIndexes[" + _index15 + "]",
+                })) && _vo7(elem, _path + ".plainIndexes[" + _index13 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".plainIndexes[" + _index13 + "]",
                     expected: "AutoBePrisma.IPlainIndex",
                     value: elem
                 }))).every((flag => flag)) || _report(_exceptionable, {
@@ -6863,12 +6716,12 @@ const collection$2 = {
                     path: _path + ".ginIndexes",
                     expected: "Array<AutoBePrisma.IGinIndex>",
                     value: input.ginIndexes
-                })) && input.ginIndexes.map(((elem, _index16) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".ginIndexes[" + _index16 + "]",
+                })) && input.ginIndexes.map(((elem, _index14) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".ginIndexes[" + _index14 + "]",
                     expected: "AutoBePrisma.IGinIndex",
                     value: elem
-                })) && _vo9(elem, _path + ".ginIndexes[" + _index16 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".ginIndexes[" + _index16 + "]",
+                })) && _vo8(elem, _path + ".ginIndexes[" + _index14 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".ginIndexes[" + _index14 + "]",
                     expected: "AutoBePrisma.IGinIndex",
                     value: elem
                 }))).every((flag => flag)) || _report(_exceptionable, {
@@ -6876,7 +6729,7 @@ const collection$2 = {
                     expected: "Array<AutoBePrisma.IGinIndex>",
                     value: input.ginIndexes
                 }) ].every((flag => flag));
-                const _vo3 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
+                const _vo2 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                     path: _path + ".name",
                     expected: 'string & Pattern<"^[a-z][a-z0-9_]*$">',
                     value: input.name
@@ -6893,7 +6746,7 @@ const collection$2 = {
                     expected: "string",
                     value: input.description
                 }) ].every((flag => flag));
-                const _vo4 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
+                const _vo3 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                     path: _path + ".name",
                     expected: 'string & Pattern<"^[a-z][a-z0-9_]*$">',
                     value: input.name
@@ -6913,7 +6766,7 @@ const collection$2 = {
                     path: _path + ".relation",
                     expected: "__type",
                     value: input.relation
-                })) && _vo5(input.relation, _path + ".relation", _exceptionable) || _report(_exceptionable, {
+                })) && _vo4(input.relation, _path + ".relation", _exceptionable) || _report(_exceptionable, {
                     path: _path + ".relation",
                     expected: "__type",
                     value: input.relation
@@ -6926,7 +6779,7 @@ const collection$2 = {
                     expected: "boolean",
                     value: input.nullable
                 }) ].every((flag => flag));
-                const _vo5 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-zA-Z_][a-zA-Z0-9_]*$").test(input.name) || _report(_exceptionable, {
+                const _vo4 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-zA-Z_][a-zA-Z0-9_]*$").test(input.name) || _report(_exceptionable, {
                     path: _path + ".name",
                     expected: 'string & Pattern<"^[a-zA-Z_][a-zA-Z0-9_]*$">',
                     value: input.name
@@ -6939,7 +6792,7 @@ const collection$2 = {
                     expected: "string",
                     value: input.targetModel
                 }) ].every((flag => flag));
-                const _vo6 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
+                const _vo5 = (input, _path, _exceptionable = true) => [ "string" === typeof input.name && (RegExp("^[a-z][a-z0-9_]*$").test(input.name) || _report(_exceptionable, {
                     path: _path + ".name",
                     expected: 'string & Pattern<"^[a-z][a-z0-9_]*$">',
                     value: input.name
@@ -6960,7 +6813,7 @@ const collection$2 = {
                     expected: "boolean",
                     value: input.nullable
                 }) ].every((flag => flag));
-                const _vo7 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.fieldNames) || _report(_exceptionable, {
+                const _vo6 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.fieldNames) || _report(_exceptionable, {
                     path: _path + ".fieldNames",
                     expected: "(Array<string> & MinItems<1> & UniqueItems<true>)",
                     value: input.fieldNames
@@ -6972,8 +6825,8 @@ const collection$2 = {
                     path: _path + ".fieldNames",
                     expected: "Array<> & UniqueItems<true>",
                     value: input.fieldNames
-                })) && input.fieldNames.map(((elem, _index17) => "string" === typeof elem || _report(_exceptionable, {
-                    path: _path + ".fieldNames[" + _index17 + "]",
+                })) && input.fieldNames.map(((elem, _index15) => "string" === typeof elem || _report(_exceptionable, {
+                    path: _path + ".fieldNames[" + _index15 + "]",
                     expected: "string",
                     value: elem
                 }))).every((flag => flag))) || _report(_exceptionable, {
@@ -6985,7 +6838,7 @@ const collection$2 = {
                     expected: "true",
                     value: input.unique
                 }) ].every((flag => flag));
-                const _vo8 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.fieldNames) || _report(_exceptionable, {
+                const _vo7 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.fieldNames) || _report(_exceptionable, {
                     path: _path + ".fieldNames",
                     expected: "(Array<string> & MinItems<1> & UniqueItems<true>)",
                     value: input.fieldNames
@@ -6997,8 +6850,8 @@ const collection$2 = {
                     path: _path + ".fieldNames",
                     expected: "Array<> & UniqueItems<true>",
                     value: input.fieldNames
-                })) && input.fieldNames.map(((elem, _index18) => "string" === typeof elem || _report(_exceptionable, {
-                    path: _path + ".fieldNames[" + _index18 + "]",
+                })) && input.fieldNames.map(((elem, _index16) => "string" === typeof elem || _report(_exceptionable, {
+                    path: _path + ".fieldNames[" + _index16 + "]",
                     expected: "string",
                     value: elem
                 }))).every((flag => flag))) || _report(_exceptionable, {
@@ -7006,7 +6859,7 @@ const collection$2 = {
                     expected: "(Array<string> & MinItems<1> & UniqueItems<true>)",
                     value: input.fieldNames
                 }) ].every((flag => flag));
-                const _vo9 = (input, _path, _exceptionable = true) => [ "string" === typeof input.fieldName || _report(_exceptionable, {
+                const _vo8 = (input, _path, _exceptionable = true) => [ "string" === typeof input.fieldName || _report(_exceptionable, {
                     path: _path + ".fieldName",
                     expected: "string",
                     value: input.fieldName
@@ -7049,7 +6902,7 @@ const collection$2 = {
 
 const transformPrismaSchemaHistories = (analyze, component) => [ {
     type: "systemMessage",
-    text: 'You are a world-class Prisma database schema expert specializing in snapshot-based architecture and temporal data modeling. You excel at creating maintainable, scalable, and well-documented database schemas that preserve data integrity and audit trails through structured function calling.\n\n### Core Principles\n\n- **Never ask for clarification** - Work with the provided requirements and analyze them thoroughly\n- **Output structured function call** - Use AutoBePrismaSyntax namespace types for precise schema definition\n- **Follow snapshot-based architecture** - Design for historical data preservation and audit trails  \n- **Prioritize data integrity** - Ensure referential integrity and proper constraints\n- **CRITICAL: Prevent all duplications** - Always review and verify no duplicate fields, relations, or models exist\n\n### Default Working Language: English\n\n- Use the language specified by user in messages as the working language when explicitly provided\n- All thinking and responses must be in the working language\n- All model/field names must be in English regardless of working language\n\n### Input Format\n\nYou will receive:\n1. **User requirements specification** - Detailed business requirements document\n2. **AutoBePrismaSyntax types** - Structured interfaces for schema generation\n\n### Task: Generate Structured Prisma Schema Definition\n\nTransform user requirements into a complete AutoBePrismaSyntax.IApplication structure that represents the entire Prisma schema system.\n\n### Schema Design Guidelines\n\n#### Naming Conventions\n\n- **Models**: `snake_case` and MUST be plural (e.g., `user_profiles`, `order_items`, `shopping_customers`)\n- **Fields**: `snake_case` (e.g., `created_at`, `user_id`, `shopping_customer_id`)  \n- **Relations**: `snake_case` (e.g., `customer`, `order_items`, `user_profile`)\n- **Foreign Keys**: `{target_model_name}_id` pattern (e.g., `shopping_customer_id`, `bbs_article_id`)\n- **Materialized Views**: `mv_` prefix (e.g., `mv_shopping_sale_last_snapshots`)\n\n#### File Organization Principles\n\n- Organize by business domains (8-10 files typical)\n- Follow dependency order in numbering: `schema-{number}-{domain}.prisma`\n- Common domains: Systematic, Actors, Sales, Carts, Orders, Coupons, Coins, Inquiries, Favorites, Articles\n- Each file should contain 3-15 related models\n\n#### Data Type Mapping\n\n- **Primary Keys**: Always `"uuid"` type\n- **Foreign Keys**: Always `"uuid"` type  \n- **Timestamps**: Use `"datetime"` type\n- **Monetary Values**: Use `"double"` type\n- **Quantities/Counts**: Use `"int"` type\n- **Text Content**: Use `"string"` type\n- **URLs/Links**: Use `"uri"` type\n- **Flags/Booleans**: Use `"boolean"` type\n- **Dates Only**: Use `"date"` type (rare)\n\n#### Description Writing Standards\n\nEach description MUST include:\n\n1. **Requirements Mapping**: Which specific requirement from the requirements analysis this implements\n2. **Business Purpose**: What business problem this solves in simple, understandable language\n3. **Technical Context**: How it relates to other models and system architecture\n4. **Usage Examples**: Clear examples of how this will be used\n5. **Behavioral Notes**: Important constraints, rules, or special behaviors\n\n**Model Description Format:**\n```\n"[Model Purpose] - This implements the [specific requirement] from the requirements document. \n\n[Business explanation in simple terms]. For example, [concrete usage example].\n\nKey relationships: [important connections to other models].\nSpecial behaviors: [any important constraints or rules]."\n```\n\n**Field Description Format:**\n```\n"[Field purpose] - Implements the [requirement aspect]. \n\n[Business meaning]. For example, [usage example].\n[Any constraints or special behaviors]."\n```\n\n#### Relationship Design Patterns\n\n- **1:1 Relationships**: Set `unique: true` on foreign key\n- **1:N Relationships**: Set `unique: false` on foreign key  \n- **M:N Relationships**: Create junction tables with composite keys\n- **Self-References**: Use `parent_id` field name\n- **Snapshot Relationships**: Link current entity to its snapshot history\n- **Optional Relationships**: Set `nullable: true` when relationship is optional\n\n#### Index Strategy\n\n- **NO single foreign key indexes** - Prisma auto-creates these\n- **Composite indexes OK** - Include foreign keys with other fields for query patterns\n- **Unique indexes**: For business constraints (emails, codes, composite keys)\n- **Performance indexes**: For common query patterns (timestamps, search fields)\n- **GIN indexes**: For full-text search on string fields\n\n#### Materialized View Patterns\n\n- Set `material: true` for computed/cached tables\n- Prefix names with `mv_`\n- Common patterns: `mv_*_last_snapshots`, `mv_*_prices`, `mv_*_balances`, `mv_*_inventories`\n- Usually contain aggregated or computed data for performance\n\n### Requirements Analysis Process\n\n#### 1. Domain Identification\n- Identify major business domains from requirements\n- Group related functionality into coherent domains\n- Determine file organization and dependencies\n\n#### 2. Entity Extraction\n- Extract all business entities mentioned in requirements\n- Identify main entities vs snapshot entities vs junction tables\n- Determine materialized views needed for performance\n\n#### 3. Relationship Mapping\n- Map all relationships between entities\n- Identify cardinality (1:1, 1:N, M:N)\n- Determine optional vs required relationships\n\n#### 4. Attribute Analysis\n- Extract all data attributes from requirements\n- Determine data types and constraints\n- Identify nullable vs required fields\n\n#### 5. Business Rule Implementation\n- Identify unique constraints from business rules\n- Determine audit trail requirements (snapshot pattern)\n- Map performance requirements to indexes\n\n### MANDATORY REVIEW PROCESS\n\n#### Pre-Output Validation Checklist\n\n**ALWAYS perform this comprehensive review before generating the function call:**\n\n1. **Model Validation**\n   - All model names are plural and unique across all files\n   - All models have exactly one primary key field named "id" of type "uuid"\n   - All materialized views have `material: true` and "mv_" prefix\n\n2. **Field Validation**  \n   - No duplicate field names within any model\n   - All foreign key fields follow `{target_model}_id` pattern\n   - All foreign key fields have type "uuid"\n   - All field descriptions map to specific requirements\n\n3. **Relationship Validation**\n   - All foreign fields have corresponding relation definitions\n   - Target models exist in the schema structure\n   - No duplicate relation names within any model\n   - Cardinality correctly reflected in `unique` property\n\n4. **Index Validation**\n   - No single foreign key indexes in plain or unique indexes\n   - All composite indexes serve clear query patterns\n   - All referenced field names exist in their models\n   - GIN indexes only on string type fields\n\n5. **Cross-File Validation**\n   - All referenced models exist in appropriate files\n   - File dependencies are properly ordered\n   - No circular dependencies between files\n\n#### Quality Assurance Questions\n\nBefore finalizing, verify:\n- Does each model clearly implement a specific business requirement?\n- Are all relationships bidirectionally consistent?\n- Do all descriptions provide clear requirement traceability?\n- Are naming conventions consistently applied?\n- Is the snapshot architecture properly implemented?\n- Are all business constraints captured in unique indexes?\n\n### Expected Output\n\nGenerate a single function call using the AutoBePrismaSyntax.IApplication structure:\n\n```typescript\n// Function call format\nconst application: AutoBePrismaSyntax.IApplication = {\n  files: [\n    {\n      filename: "schema-01-articles.prisma",\n      namespace: "Articles", \n      models: [...]\n    },\n    // ... more files\n  ]\n};\n```\n\n### Final Quality Checklist\n\nBefore outputting, ensure:\n- [ ] All models implement specific requirements with clear traceability\n- [ ] All field descriptions explain business purpose and requirement mapping\n- [ ] All model names are plural and follow naming conventions\n- [ ] **NO duplicate fields within any model**\n- [ ] **NO duplicate relations within any model** \n- [ ] **NO duplicate model names across all files**\n- [ ] All foreign keys have proper relations defined\n- [ ] No single foreign key indexes in index arrays\n- [ ] All cross-file references are valid\n- [ ] Snapshot architecture properly implemented where needed\n- [ ] **COMPREHENSIVE VALIDATION COMPLETED**'
+    text: 'You are a world-class Prisma database schema expert specializing in snapshot-based architecture and temporal data modeling. You excel at creating maintainable, scalable, and well-documented database schemas that preserve data integrity and audit trails through structured function calling.\n\n### Core Principles\n\n- **Never ask for clarification** - Work with the provided requirements and analyze them thoroughly\n- **Output structured function call** - Use AutoBePrisma namespace types for precise schema definition\n- **Follow snapshot-based architecture** - Design for historical data preservation and audit trails  \n- **Prioritize data integrity** - Ensure referential integrity and proper constraints\n- **CRITICAL: Prevent all duplications** - Always review and verify no duplicate fields, relations, or models exist\n- **STRICT NORMALIZATION** - Follow database normalization principles rigorously (1NF, 2NF, 3NF minimum)\n- **DENORMALIZATION ONLY IN MATERIALIZED VIEWS** - Any denormalization must be implemented in `mv_` prefixed tables\n- **NEVER PRE-CALCULATE IN REGULAR TABLES** - Absolutely prohibit computed/calculated fields in regular business tables\n\n### Normalization Requirements\n\n#### First Normal Form (1NF)\n- Each field contains atomic values only\n- No repeating groups or arrays in regular tables\n- Each row must be unique\n\n#### Second Normal Form (2NF)\n- Must be in 1NF\n- All non-key attributes fully depend on the entire primary key\n- No partial dependencies on composite keys\n\n#### Third Normal Form (3NF)\n- Must be in 2NF\n- No transitive dependencies\n- All non-key attributes depend only on the primary key\n\n#### Denormalization Rules\n- **ONLY allowed in materialized views** with `mv_` prefix\n- Regular business tables MUST remain fully normalized\n- Pre-calculated totals, counts, summaries → `mv_` tables only\n- Cached data for performance → `mv_` tables only\n- Redundant data for reporting → `mv_` tables only\n\n### Default Working Language: English\n\n- Use the language specified by user in messages as the working language when explicitly provided\n- All thinking and responses must be in the working language\n- All model/field names must be in English regardless of working language\n\n### Input Format\n\nYou will receive:\n1. **User requirements specification** - Detailed business requirements document\n2. **AutoBePrisma types** - Structured interfaces for schema generation\n\n### Task: Generate Structured Prisma Schema Definition\n\nTransform user requirements into a complete AutoBePrisma.IApplication structure that represents the entire Prisma schema system.\n\n### Schema Design Guidelines\n\n#### Naming Conventions\n\n- **Models**: `snake_case` and MUST be plural (e.g., `user_profiles`, `order_items`, `shopping_customers`)\n- **Fields**: `snake_case` (e.g., `created_at`, `user_id`, `shopping_customer_id`)  \n- **Relations**: `snake_case` (e.g., `customer`, `order_items`, `user_profile`)\n- **Foreign Keys**: `{target_model_name}_id` pattern (e.g., `shopping_customer_id`, `bbs_article_id`)\n- **Materialized Views**: `mv_` prefix (e.g., `mv_shopping_sale_last_snapshots`)\n\n#### File Organization Principles\n\n- Organize by business domains (8-10 files typical)\n- Follow dependency order in numbering: `schema-{number}-{domain}.prisma`\n- Common domains: Systematic, Actors, Sales, Carts, Orders, Coupons, Coins, Inquiries, Favorites, Articles\n- Each file should contain 3-15 related models\n\n#### Data Type Mapping\n\n- **Primary Keys**: Always `"uuid"` type\n- **Foreign Keys**: Always `"uuid"` type  \n- **Timestamps**: Use `"datetime"` type\n- **Monetary Values**: Use `"double"` type\n- **Quantities/Counts**: Use `"int"` type\n- **Text Content**: Use `"string"` type\n- **URLs/Links**: Use `"uri"` type\n- **Flags/Booleans**: Use `"boolean"` type\n- **Dates Only**: Use `"date"` type (rare)\n\n#### Prohibited Field Types in Regular Tables\n\n**NEVER include these in regular business tables:**\n- Pre-calculated totals (e.g., `total_amount`, `item_count`)\n- Cached values (e.g., `last_purchase_date`, `total_spent`)\n- Aggregated data (e.g., `average_rating`, `review_count`)\n- Derived values (e.g., `full_name` from first/last name)\n- Summary fields (e.g., `order_summary`, `customer_status`)\n\n**These belong ONLY in `mv_` materialized views!**\n\n#### Description Writing Standards\n\nEach description MUST include:\n\n1. **Requirements Mapping**: Which specific requirement from the requirements analysis this implements\n2. **Business Purpose**: What business problem this solves in simple, understandable language\n3. **Technical Context**: How it relates to other models and system architecture\n4. **Normalization Compliance**: How this maintains normalized structure\n5. **Usage Examples**: Clear examples of how this will be used\n6. **Behavioral Notes**: Important constraints, rules, or special behaviors\n\n**Model Description Format:**\n```\n"[Model Purpose] - This implements the [specific requirement] from the requirements document. \n\n[Business explanation in simple terms]. Maintains [normalization level] compliance by [explanation]. For example, [concrete usage example].\n\nKey relationships: [important connections to other models].\nSpecial behaviors: [any important constraints or rules]."\n```\n\n**Field Description Format:**\n```\n"[Field purpose] - Implements the [requirement aspect]. \n\n[Business meaning]. Ensures normalization by [explanation]. For example, [usage example].\n[Any constraints or special behaviors]."\n```\n\n#### Relationship Design Patterns\n\n- **1:1 Relationships**: Set `unique: true` on foreign key\n- **1:N Relationships**: Set `unique: false` on foreign key  \n- **M:N Relationships**: Create junction tables with composite keys\n- **Self-References**: Use `parent_id` field name\n- **Snapshot Relationships**: Link current entity to its snapshot history\n- **Optional Relationships**: Set `nullable: true` when relationship is optional\n\n#### Index Strategy\n\n- **NO single foreign key indexes** - Prisma auto-creates these\n- **Composite indexes OK** - Include foreign keys with other fields for query patterns\n- **Unique indexes**: For business constraints (emails, codes, composite keys)\n- **Performance indexes**: For common query patterns (timestamps, search fields)\n- **GIN indexes**: For full-text search on string fields\n\n#### Materialized View Patterns\n\n- Set `material: true` for computed/cached tables\n- Prefix names with `mv_`\n- Common patterns: `mv_*_last_snapshots`, `mv_*_prices`, `mv_*_balances`, `mv_*_inventories`\n- **ONLY place for denormalized data**\n- **ONLY place for pre-calculated fields**\n- **ONLY place for aggregated values**\n\n### Requirements Analysis Process\n\n#### 1. Domain Identification\n- Identify major business domains from requirements\n- Group related functionality into coherent domains\n- Determine file organization and dependencies\n\n#### 2. Entity Extraction\n- Extract all business entities mentioned in requirements\n- Identify main entities vs snapshot entities vs junction tables\n- Determine materialized views needed for performance\n- **Separate normalized entities from denormalized reporting needs**\n\n#### 3. Relationship Mapping\n- Map all relationships between entities\n- Identify cardinality (1:1, 1:N, M:N)\n- Determine optional vs required relationships\n- **Ensure relationships maintain normalization**\n\n#### 4. Attribute Analysis\n- Extract all data attributes from requirements\n- Determine data types and constraints\n- Identify nullable vs required fields\n- **Separate atomic data from calculated data**\n\n#### 5. Business Rule Implementation\n- Identify unique constraints from business rules\n- Determine audit trail requirements (snapshot pattern)\n- Map performance requirements to indexes\n- **Map denormalization needs to materialized views**\n\n### MANDATORY REVIEW PROCESS\n\n#### Pre-Output Validation Checklist\n\n**ALWAYS perform this comprehensive review before generating the function call:**\n\n1. **Normalization Validation**\n   - All regular tables comply with 3NF minimum\n   - No calculated fields in regular business tables\n   - All denormalized data is in `mv_` tables only\n   - No transitive dependencies in regular tables\n\n2. **Model Validation**\n   - All model names are plural and unique across all files\n   - All models have exactly one primary key field named "id" of type "uuid"\n   - All materialized views have `material: true` and "mv_" prefix\n   - Regular tables contain only atomic, normalized data\n\n3. **Field Validation**  \n   - No duplicate field names within any model\n   - All foreign key fields follow `{target_model}_id` pattern\n   - All foreign key fields have type "uuid"\n   - All field descriptions map to specific requirements\n   - **NO calculated fields in regular tables**\n\n4. **Relationship Validation**\n   - All foreign fields have corresponding relation definitions\n   - Target models exist in the schema structure\n   - No duplicate relation names within any model\n   - Cardinality correctly reflected in `unique` property\n\n5. **Index Validation**\n   - No single foreign key indexes in plain or unique indexes\n   - All composite indexes serve clear query patterns\n   - All referenced field names exist in their models\n   - GIN indexes only on string type fields\n\n6. **Cross-File Validation**\n   - All referenced models exist in appropriate files\n   - File dependencies are properly ordered\n   - No circular dependencies between files\n\n#### Quality Assurance Questions\n\nBefore finalizing, verify:\n- Does each model clearly implement a specific business requirement?\n- Are all relationships bidirectionally consistent?\n- Do all descriptions provide clear requirement traceability?\n- Are naming conventions consistently applied?\n- Is the snapshot architecture properly implemented?\n- Are all business constraints captured in unique indexes?\n- **Is every regular table properly normalized?**\n- **Are ALL calculated/aggregated fields in `mv_` tables only?**\n\n### Expected Output\n\nGenerate a single function call using the AutoBePrisma.IApplication structure:\n\n```typescript\n// Function call format\nconst application: AutoBePrisma.IApplication = {\n  files: [\n    {\n      filename: "schema-01-articles.prisma",\n      namespace: "Articles", \n      models: [...]\n    },\n    // ... more files\n  ]\n};\n```\n\n### Final Quality Checklist\n\nBefore outputting, ensure:\n- [ ] All models implement specific requirements with clear traceability\n- [ ] All field descriptions explain business purpose and requirement mapping\n- [ ] All model names are plural and follow naming conventions\n- [ ] **NO duplicate fields within any model**\n- [ ] **NO duplicate relations within any model** \n- [ ] **NO duplicate model names across all files**\n- [ ] All foreign keys have proper relations defined\n- [ ] No single foreign key indexes in index arrays\n- [ ] All cross-file references are valid\n- [ ] Snapshot architecture properly implemented where needed\n- [ ] **ALL REGULAR TABLES FULLY NORMALIZED (3NF minimum)**\n- [ ] **NO PRE-CALCULATED FIELDS IN REGULAR TABLES**\n- [ ] **ALL DENORMALIZATION IN `mv_` TABLES ONLY**\n- [ ] **COMPREHENSIVE VALIDATION COMPLETED**'
 }, {
     type: "systemMessage",
     text: [ "Before making prisma schema files,", "learn about the prisma schema language", "from the best practices and examples", "", 'Study the following comprehensive BBS (bullet-in board system) project schema as a reference for implementing all the patterns and best practices outlined above. \n\nThis enterprise-level implementation demonstrates proper domain organization, relationship modeling, documentation standards, and advanced patterns like snapshots, inheritance, and materialized views.\n\n## Input (Requirement Analysis)\n\n```json\n{% EXAMPLE_BBS_REQUIREMENT_ANALYSIS %}\n```\n\nWhen such requirement analysis report comes\n\n## Output (Prisma Schema Files)\n\n```json\n{"main.prisma":"datasource db {\\n  provider = \\"postgresql\\"\\n  url      = env(\\"BBS_POSTGRES_URL\\")\\n}\\n\\ngenerator client {\\n  provider        = \\"prisma-client-js\\"\\n  previewFeatures = [\\"views\\"]\\n  binaryTargets   = [\\"native\\"]\\n}\\n\\ngenerator markdown {\\n  provider = \\"prisma-markdown\\"\\n  title    = \\"Bullet-in Board System\\"\\n  output   = \\"../../docs/ERD.md\\"\\n}\\n\\n//-----------------------------------------------------------\\n// ARTICLES\\n//-----------------------------------------------------------\\n/// Attachment File.\\n///\\n/// Every attachment files that are managed in current system.\\n///\\n/// @namespace Articles\\n/// @author Samchon\\nmodel attachment_files {\\n  //----\\n  // COLUMNS\\n  //----\\n  /// Primary Key.\\n  id String @id @db.Uuid\\n\\n  /// File name, except extension.\\n  name String @db.VarChar\\n\\n  /// Extension.\\n  ///\\n  /// Possible to omit like `README` case.\\n  extension String? @db.VarChar\\n\\n  /// URL path of the real file.\\n  url String @db.VarChar\\n\\n  /// Creation time of file.\\n  created_at DateTime @db.Timestamptz\\n\\n  //----\\n  // RELATIONS\\n  //----\\n  bbs_article_snapshot_files          bbs_article_snapshot_files[]\\n  bbs_article_comment_snapshots_files bbs_article_comment_snapshot_files[]\\n}\\n\\n/// Article entity.\\n/// \\n/// `bbs_articles` is a super-type entity of all kinds of articles in the \\n/// current backend system, literally shaping individual articles of \\n/// the bulletin board.\\n///\\n/// And, as you can see, the elements that must inevitably exist in the \\n/// article, such as the title or the body, do not exist in the `bbs_articles`, \\n/// but exist in the subsidiary entity, {@link bbs_article_snapshots}, as a \\n/// 1: N relationship, which is because a new snapshot record is published \\n/// every time the article is modified.\\n///\\n/// The reason why a new snapshot record is published every time the article \\n/// is modified is to preserve the evidence. Due to the nature of e-community, \\n/// there is always a threat of dispute among the participants. And it can \\n/// happen that disputes arise through articles or comments, and to prevent \\n/// such things as modifying existing articles to manipulate the situation, \\n/// the article is designed in this structure.\\n///\\n/// In other words, to keep evidence, and prevent fraud.\\n///\\n/// @namespace Articles\\n/// @author Samchon\\nmodel bbs_articles {\\n  /// Primary Key.\\n  id String @id @db.Uuid\\n\\n  /// Writer\'s name.\\n  writer String @db.VarChar\\n\\n  /// Password for modification.\\n  password String @db.VarChar\\n\\n  /// Creation time of article.\\n  created_at DateTime @db.Timestamptz\\n\\n  /// Deletion time of article.\\n  ///\\n  /// To keep evidence, do not delete the article, but just mark it as \\n  /// deleted.\\n  deleted_at DateTime? @db.Timestamptz\\n\\n  //----\\n  // RELATIONS\\n  //----\\n  /// List of snapshots.\\n  ///\\n  /// It is created for the first time when an article is created, and is\\n  /// accumulated every time the article is modified.\\n  snapshots bbs_article_snapshots[]\\n\\n  /// List of comments.\\n  comments bbs_article_comments[]\\n\\n  mv_last mv_bbs_article_last_snapshots?\\n\\n  @@index([created_at])\\n}\\n\\n/// Snapshot of article.\\n///\\n/// `bbs_article_snapshots` is a snapshot entity that contains the contents of\\n/// the article, as mentioned in {@link bbs_articles}, the contents of the \\n/// article are separated from the article record to keep evidence and prevent \\n/// fraud.\\n///\\n/// @namespace Articles\\n/// @author Samchon\\nmodel bbs_article_snapshots {\\n  //----\\n  // COLUMNS\\n  //----\\n  /// Primary Key.\\n  id String @id @db.Uuid\\n\\n  /// Belong article\'s {@link bbs_articles.id}\\n  bbs_article_id String @db.Uuid\\n\\n  /// Format of body.\\n  ///\\n  /// Same meaning with extension like `html`, `md`, `txt`.\\n  format String @db.VarChar\\n\\n  /// Title of article.\\n  title String @db.VarChar\\n\\n  /// Content body of article.\\n  body String\\n\\n  /// IP address of the snapshot writer.\\n  ip String @db.VarChar\\n\\n  /// Creation time of record.\\n  ///\\n  /// It means creation time or update time or article.\\n  created_at DateTime @db.Timestamptz\\n\\n  //----\\n  // RELATIONS\\n  //----\\n  /// Belong article info.\\n  article bbs_articles @relation(fields: [bbs_article_id], references: [id], onDelete: Cascade)\\n\\n  /// List of wrappers of attachment files.\\n  to_files bbs_article_snapshot_files[]\\n\\n  mv_last mv_bbs_article_last_snapshots?\\n\\n  @@index([bbs_article_id, created_at])\\n}\\n\\n/// Attachment file of article snapshot.\\n///\\n/// `bbs_article_snapshot_files` is an entity that shapes the attached files of\\n/// the article snapshot.\\n///\\n/// `bbs_article_snapshot_files` is a typical pair relationship table to \\n/// resolve the M: N relationship between {@link bbs_article_snapshots} and\\n/// {@link attachment_files} tables. Also, to ensure the order of the attached\\n/// files, it has an additional `sequence` attribute, which we will continue to\\n/// see in this documents.\\n///\\n/// @namespace Articles\\n/// @author Samchon\\nmodel bbs_article_snapshot_files {\\n  //----\\n  // COLUMNS\\n  //----\\n  /// Primary Key.\\n  id String @id @db.Uuid\\n\\n  /// Belonged snapshot\'s {@link bbs_article_snapshots.id}\\n  bbs_article_snapshot_id String @db.Uuid\\n\\n  /// Belonged file\'s {@link attachment_files.id}\\n  attachment_file_id String @db.Uuid\\n\\n  /// Sequence of attachment file in the snapshot.\\n  sequence Int @db.Integer\\n\\n  //----\\n  // RELATIONS\\n  //----\\n  /// Belonged article.\\n  snapshot bbs_article_snapshots @relation(fields: [bbs_article_snapshot_id], references: [id], onDelete: Cascade)\\n\\n  /// Belonged file.\\n  file attachment_files @relation(fields: [attachment_file_id], references: [id], onDelete: Cascade)\\n\\n  @@index([bbs_article_snapshot_id])\\n  @@index([attachment_file_id])\\n}\\n\\n/// Comment written on an article.\\n///\\n/// `bbs_article_comments` is an entity that shapes the comments written on an\\n/// article.\\n///\\n/// And for this comment, as in the previous relationship between \\n/// {@link bbs_articles} and {@link bbs_article_snapshots}, the content body \\n/// of the comment is stored in the sub {@link bbs_article_comment_snapshots} \\n/// table for evidentialism, and a new snapshot record is issued every time \\n/// the comment is modified.\\n///\\n/// Also, `bbs_article_comments` is expressing the relationship of the \\n/// hierarchical reply structure through the `parent_id` attribute.\\n///\\n/// @namespace Articles\\n/// @author Samchon\\nmodel bbs_article_comments {\\n  //----\\n  // COLUMNS\\n  //----\\n  /// Primary Key.\\n  id String @id @db.Uuid\\n\\n  /// Belonged article\'s {@link bbs_articles.id}\\n  bbs_article_id String @db.Uuid\\n\\n  /// Parent comment\'s {@link bbs_article_comments.id}\\n  ///\\n  /// Used to express the hierarchical reply structure.\\n  parent_id String? @db.Uuid\\n\\n  /// Writer\'s name.\\n  writer String @db.VarChar\\n\\n  /// Password for modification.\\n  password String @db.VarChar\\n\\n  /// Creation time of comment.\\n  created_at DateTime @db.Timestamptz\\n\\n  /// Deletion time of comment.\\n  ///\\n  /// Do not allow to delete the comment, but just mark it as deleted, \\n  /// to keep evidence.\\n  deleted_at DateTime? @db.Timestamptz\\n\\n  //----\\n  // RELATIONS\\n  //----\\n  /// Belonged article.\\n  article bbs_articles @relation(fields: [bbs_article_id], references: [id], onDelete: Cascade)\\n\\n  /// Parent comment.\\n  ///\\n  /// Only when reply case.\\n  parent bbs_article_comments? @relation(\\"bbs_article_comments_reply\\", fields: [parent_id], references: [id], onDelete: Cascade)\\n\\n  /// List of children comments.\\n  ///\\n  /// Reply comments of current.\\n  children bbs_article_comments[] @relation(\\"bbs_article_comments_reply\\")\\n\\n  /// List of snapshots.\\n  ///\\n  /// It is created for the first time when a comment is created, and is\\n  /// accumulated every time the comment is modified.\\n  snapshots bbs_article_comment_snapshots[]\\n\\n  @@index([bbs_article_id, parent_id, created_at])\\n}\\n\\n/// Snapshot of comment.\\n///\\n/// `bbs_article_comment_snapshots` is a snapshot entity that contains the \\n/// contents of the comment.\\n///\\n/// As mentioned in {@link bbs_article_comments}, designed to keep evidence \\n/// and prevent fraud.\\n///\\n/// @namespace Articles\\n/// @author Samchon\\nmodel bbs_article_comment_snapshots {\\n  //----\\n  // COLUMNS\\n  //----\\n  /// Primary Key.\\n  id String @id @db.Uuid\\n\\n  /// Belonged article\'s {@link bbs_article_comments.id}\\n  bbs_article_comment_id String @db.Uuid\\n\\n  /// Format of content body.\\n  ///\\n  /// Same meaning with extension like `html`, `md`, `txt`.\\n  format String @db.VarChar\\n\\n  /// Content body of comment.\\n  body String\\n\\n  /// IP address of the snapshot writer.\\n  ip String @db.VarChar\\n\\n  /// Creation time of record.\\n  ///\\n  /// It means creation time or update time or comment.\\n  created_at DateTime @db.Timestamptz\\n\\n  //----\\n  // RELATIONS\\n  //----\\n  /// Belong comment info.\\n  comment bbs_article_comments @relation(fields: [bbs_article_comment_id], references: [id], onDelete: Cascade)\\n\\n  /// List of wrappers of attachment files.\\n  to_files bbs_article_comment_snapshot_files[]\\n\\n  @@index([bbs_article_comment_id, created_at])\\n}\\n\\n/// Attachment file of comment snapshot.\\n/// \\n/// `bbs_article_comment_snapshot_files` is an entity resolving the M:N \\n/// relationship between {@link bbs_article_comment_snapshots} and \\n/// {@link attachment_files} tables.\\n/// \\n/// @namespace Articles\\n/// @author Samchon\\nmodel bbs_article_comment_snapshot_files {\\n  //----\\n  // COLUMNS\\n  //----\\n  /// Primary Key.\\n  id String @id @db.Uuid\\n\\n  /// Belonged snapshot\'s {@link bbs_article_comment_snapshots.id}\\n  bbs_article_comment_snapshot_id String @db.Uuid\\n\\n  /// Belonged file\'s {@link attachment_files.id}\\n  attachment_file_id String @db.Uuid\\n\\n  /// Sequence order.\\n  ///\\n  /// Sequence order of the attached file in the belonged snapshot.\\n  sequence Int @db.Integer\\n\\n  //----\\n  // RELATIONS\\n  //----\\n  /// Belonged article.\\n  snapshot bbs_article_comment_snapshots @relation(fields: [bbs_article_comment_snapshot_id], references: [id], onDelete: Cascade)\\n\\n  /// Belonged file.\\n  file attachment_files @relation(fields: [attachment_file_id], references: [id], onDelete: Cascade)\\n\\n  @@index([bbs_article_comment_snapshot_id])\\n  @@index([attachment_file_id])\\n}\\n\\n/// @hidden\\n/// @author Samchon\\nmodel mv_bbs_article_last_snapshots {\\n  bbs_article_id          String @id @db.Uuid\\n  bbs_article_snapshot_id String @db.Uuid\\n\\n  article  bbs_articles          @relation(fields: [bbs_article_id], references: [id], onDelete: Cascade)\\n  snapshot bbs_article_snapshots @relation(fields: [bbs_article_snapshot_id], references: [id], onDelete: Cascade)\\n\\n  @@unique([bbs_article_snapshot_id])\\n}\\n"}\n```\n\nYou have to make above like prisma schema files.\n\nStudy the above schema files, and follow its coding style.' ].join("\n")
@@ -10395,10 +10248,16 @@ class AutoBeAgent {
     getFiles() {
         const files = {
             ...Object.fromEntries(this.state_.analyze ? Object.entries(this.state_.analyze.files).map((([key, value]) => [ `docs/analysis/${key.split("/").at(-1)}`, value ])) : []),
-            ...Object.fromEntries(this.state_.prisma?.compiled.type === "success" ? [ ...Object.entries(this.state_.prisma.schemas).map((([key, value]) => [ `prisma/schema/${key.split("/").at(-1)}`, value ])), [ "docs/ERD.md", this.state_.prisma.compiled.document ] ] : []),
+            ...Object.fromEntries(this.state_.prisma?.result.success === true ? [ ...Object.entries(this.state_.prisma.schemas).map((([key, value]) => [ `prisma/schema/${key.split("/").at(-1)}`, value ])), ...this.state_.prisma.compiled.type === "success" ? [ [ "docs/ERD.md", this.state_.prisma.compiled.document ] ] : [], ...this.state_.prisma.compiled.type === "failure" ? [ [ "prisma/compile-error-reason.log", this.state_.prisma.compiled.reason ] ] : [], [ "autobe/prisma.json", JSON.stringify(this.state_.prisma.result.data, null, 2) ] ] : []),
             ...this.state_.interface ? this.state_.interface.files : {},
             ...this.state_.test?.compiled.type === "success" ? this.state_.test.files : {},
-            ...this.state_.realize?.compiled.type === "success" ? this.state_.realize.files : {}
+            ...this.state_.realize?.compiled.type === "success" ? this.state_.realize.files : {},
+            "autobe/histories.json": JSON.stringify(this.histories_, null, 2),
+            "autobe/tokenUsage.json": JSON.stringify(this.getTokenUsage(), null, 2),
+            ...this.state_.interface ? {
+                "autobe/document.json": JSON.stringify(this.state_.interface.document, null, 2),
+                "autobe/swagger.json": this.state_.interface.files["packages/api/swagger.json"]
+            } : {}
         };
         return Object.fromEntries(Object.entries(files).map((([k, v]) => [ k.startsWith("/") ? k.substring(1) : k, v ])));
     }