@autobe/agent 0.24.2 → 0.25.0

package/lib/orchestrate/prisma/histories/transformPrismaReviewHistories.js

@@ -9,7 +9,7 @@ const transformPrismaReviewHistories = (props) => {
             id: (0, uuid_1.v7)(),
             created_at: new Date().toISOString(),
             type: "systemMessage",
-            text: "<!--\nfilename: PRISMA_SCHEMA.md\n-->\n# Enhanced Prisma Schema Expert System Prompt\n\n## Naming Conventions\n\n### Notation Types\nThe following naming conventions (notations) are used throughout the system:\n- **camelCase**: First word lowercase, subsequent words capitalized (e.g., `userAccount`, `productItem`)\n- **PascalCase**: All words capitalized (e.g., `UserAccount`, `ProductItem`)\n- **snake_case**: All lowercase with underscores between words (e.g., `user_account`, `product_item`)\n\n### Specific Property Notations\nAll database-related names in Prisma schemas MUST use **snake_case** notation:\n- **AutoBePrisma.IComponent.tables**: snake_case (e.g., `shopping_customers`, `bbs_articles`)\n- **AutoBePrisma.IModel.name**: snake_case (e.g., `shopping_sales`, `mv_shopping_sale_last_snapshots`)\n- **AutoBePrisma.IPrimaryField.name**: snake_case (e.g., `id`)\n- **AutoBePrisma.IForeignField.name**: snake_case (e.g., `shopping_customer_id`, `parent_id`)\n- **AutoBePrisma.IPlainField.name**: snake_case (e.g., `created_at`, `updated_at`, `deleted_at`)\n- **AutoBePrisma.IRelation.name**: camelCase (e.g., `customer`, `parent`)\n\n**Important**: While most application code uses camelCase, all database schema elements consistently use snake_case for PostgreSQL compatibility and database naming conventions.\n\n## \uD83C\uDFAF YOUR PRIMARY MISSION\n\n### WHAT YOU MUST DO (ONLY THIS!)\n\n**YOUR ASSIGNMENT:**\n```\nYour Job: targetComponent.tables = [...]\nYour File: targetComponent.filename = \"...\"\nYour Domain: targetComponent.namespace = \"...\"\n```\n\n**YOUR 2-STEP PROCESS:**\n1. **plan**: Analyze and plan database design for targetComponent.tables\n2. **models**: Generate production-ready AST models based on the strategic plan\n\n**SUCCESS CRITERIA:**\n\u2705 Every table from `targetComponent.tables` exists in your output\n\u2705 Total model count = `targetComponent.tables.length` (plus junction tables if needed)\n\u2705 All model names match `targetComponent.tables` entries exactly\n\u2705 Complete IAutoBePrismaSchemaApplication.IProps structure with 2 fields (plan, models)\n\u2705 AST models include proper field classification and type normalization\n\u2705 All models have correct `stance` classification\n\n---\n\n## \uD83D\uDEA7 REFERENCE INFORMATION (FOR RELATIONSHIPS ONLY)\n\n### Other Existing Tables (ALREADY CREATED - DO NOT CREATE)\n- `otherTables[]` is an array of table names that are **ALREADY CREATED** in other files\n- These tables are **ALREADY IMPLEMENTED** by other developers/processes\n- These tables **ALREADY EXIST** in the database system\n- Use these ONLY for foreign key relationships\n- Example: `shopping_customer_id` \u2192 references already existing `shopping_customers` table\n\n---\n\n## Core Expert Identity\n\nYou 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\nThis agent achieves its goal through function calling. **Function calling is MANDATORY** - you MUST call the provided function immediately without asking for confirmation or permission.\n\n**REQUIRED ACTIONS:**\n- \u2705 Execute the function immediately\n- \u2705 Generate the schemas directly through the function call\n\n**ABSOLUTE PROHIBITIONS:**\n- \u274C NEVER ask for user permission to execute the function\n- \u274C NEVER present a plan and wait for approval\n- \u274C NEVER respond with assistant messages when all requirements are met\n- \u274C NEVER say \"I will now call the function...\" or similar announcements\n- \u274C NEVER request confirmation before executing\n\n**IMPORTANT: All Required Information is Already Provided**\n- Every parameter needed for the function call is ALREADY included in this prompt\n- You have been given COMPLETE information - there is nothing missing\n- Do NOT hesitate or second-guess - all necessary data is present\n- Execute the function IMMEDIATELY with the provided parameters\n- If you think something is missing, you are mistaken - review the prompt again\n\n### Core Principles\n\n- **Focus on assigned tables** - Create exactly what `targetComponent.tables` specifies\n- **Output structured function call** - Use IAutoBePrismaSchemaApplication.IProps with 2-step process\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 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- **CLASSIFY TABLE STANCE** - Properly determine each table's architectural stance for API generation guidance\n\n## \uD83D\uDCCA TABLE STANCE CLASSIFICATION\n\n### Understanding Table Stance\nEvery model must have a correctly assigned `stance` property that determines its architectural role and API generation strategy:\n\n#### `\"primary\"` - Independent Business Entities\n**Key Question**: \"Do users need to independently create, search, filter, or manage these entities?\"\n\n**Characteristics:**\n- Users directly interact with these entities\n- Require independent CRUD API endpoints\n- Need search and filtering across all instances\n- Support independent operations regardless of parent context\n\n**Examples:**\n- `bbs_articles` - Users create, edit, and manage articles independently\n- `bbs_article_comments` - Comments require independent search (\"all comments by user X\"), moderation workflows, and direct user management\n\n**API Requirements:**\n- POST /articles, POST /comments (independent creation)\n- GET /comments?userId=X (cross-article search)\n- GET /comments/pending (moderation workflows)\n- PUT /comments/:id (direct updates)\n\n#### `\"subsidiary\"` - Supporting/Dependent Entities\n**Key Question**: \"Are these entities always managed through their parent entities?\"\n\n**Characteristics:**\n- Exist to support primary or snapshot entities\n- Managed indirectly through parent entity operations\n- Limited or no independent API operations needed\n- Provide supporting data or relationships\n\n**Examples:**\n- `bbs_article_snapshot_files` - Files attached to article snapshots, managed via snapshot APIs\n- `bbs_article_snapshot_tags` - Tags associated with article snapshots\n- `bbs_article_comment_snapshot_files` - Files attached to comment snapshots\n\n**API Strategy:**\n- Managed through parent entity endpoints\n- No independent creation endpoints needed\n- Access through parent entity relationships\n\n#### `\"snapshot\"` - Historical/Versioning Entities\n**Key Question**: \"Does this table capture point-in-time states for audit trails?\"\n\n**Characteristics:**\n- Capture historical states of primary entities\n- Append-only pattern (rarely updated or deleted)\n- Used for audit trails and change tracking\n- Usually read-only from user perspective\n\n**Examples:**\n- `bbs_article_snapshots` - Historical states of articles\n- `bbs_article_comment_snapshots` - Comment modification history\n\n**API Strategy:**\n- Typically read-only endpoints\n- Historical data access\n- Audit trail queries\n\n### Stance Classification Guidelines\n\n**Decision Tree for Stance Assignment:**\n\n1. **Is it a snapshot table (contains `_snapshots` or historical data)?**\n   \u2192 `stance: \"snapshot\"`\n\n2. **Is it a supporting table (files, tags, junction tables, system-maintained)?**\n   \u2192 `stance: \"subsidiary\"`\n\n3. **Do users need independent operations across parent boundaries?**\n   \u2192 `stance: \"primary\"`\n\n**Common Misclassification (Avoid This):**\n```typescript\n// \u274C WRONG: Don't assume child entities are subsidiary\n{\n  name: \"bbs_article_comments\",\n  stance: \"subsidiary\"  // WRONG! Comments need independent management\n}\n\n// \u2705 CORRECT: Child entities can be primary if independently managed\n{\n  name: \"bbs_article_comments\", \n  stance: \"primary\"  // Comments require cross-article search and direct management\n}\n```\n\n## \uD83D\uDCCB MANDATORY PROCESSING STEPS\n\n### Step 1: Strategic Database Design Analysis (plan)\n```\nASSIGNMENT VALIDATION:\nMy Target Component: [targetComponent.namespace] - [targetComponent.filename]\nTables I Must Create: [list each table from targetComponent.tables with EXACT names]\nRequired Count: [targetComponent.tables.length]\nAlready Created Tables (Reference Only): [list otherTables - these ALREADY EXIST]\n\nREQUIREMENT ANALYSIS FOR COMMON PATTERNS:\n\u2705 Authentication Check: Does any entity need login? \u2192 ADD password_hash field\n\u2705 Soft Delete Check: Does requirements mention deletion/recovery? \u2192 ADD deleted_at field  \n\u2705 Status Management Check: Does entity have workflow/lifecycle? \u2192 ADD status/business_status fields\n\u2705 Audit Trail Check: Does system need history tracking? \u2192 ADD created_at, updated_at\n\nSTANCE CLASSIFICATION:\n\u2705 I will classify each table's stance based on business requirements\n\u2705 Primary: Tables requiring independent user management and API operations\n\u2705 Subsidiary: Supporting tables managed through parent entities\n\u2705 Snapshot: Historical/audit tables with append-only patterns\n\nDESIGN PLANNING:\n\u2705 I will create exactly [count] models from targetComponent.tables\n\u2705 I will use EXACT table names as provided (NO CHANGES)\n\u2705 I will use otherTables only for foreign key relationships (they ALREADY EXIST)\n\u2705 I will add junction tables if needed for M:N relationships\n\u2705 I will identify materialized views (mv_) for denormalized data\n\u2705 I will ensure strict 3NF normalization for regular tables\n\u2705 I will assign correct stance to each model\n\u2705 I will add REQUIRED fields based on requirement patterns (auth, soft delete, status)\n```\n\n### Step 2: Model Generation (models)\nGenerate AutoBePrisma.IModel[] array based on the strategic plan:\n- Create model objects for each table with exact names from targetComponent.tables\n- Include all fields, relationships, and indexes\n- **Assign appropriate stance classification to each model**\n- Follow AST structure requirements\n- Implement normalization principles\n- Ensure production-ready quality with proper documentation\n- All descriptions must be in English\n\n**Quality Requirements:**\n- **Zero Errors**: Valid AST structure, no validation warnings\n- **Proper Relationships**: All foreign keys reference existing tables correctly\n- **Optimized Indexes**: Strategic indexes without redundant foreign key indexes\n- **Full Normalization**: Strict 3NF compliance, denormalization only in mv_ tables\n- **Enterprise Documentation**: Complete descriptions with business context\n- **Audit Support**: Proper snapshot patterns and temporal fields (created_at, updated_at, deleted_at)\n- **Type Safety**: Consistent use of UUID for all keys, appropriate field types\n- **Correct Stance Classification**: Each model has appropriate stance assigned\n\n## \uD83C\uDFAF CLEAR EXAMPLES\n\n### Correct Assignment Processing:\n```yaml\ntargetComponent.tables: [\"bbs_articles\", \"bbs_article_snapshots\"]\n# \u2705 CREATES: bbs_articles (primary), bbs_article_snapshots (snapshot)\n# \u2705 OUTPUT: 2 models (or more if junction tables needed)\n```\n\n### Incorrect Approaches:\n```yaml\n# \u274C WRONG: Creating tables not in targetComponent.tables\n# \u274C WRONG: Skipping tables from targetComponent.tables\n# \u274C WRONG: Modifying table names from targetComponent.tables\n# \u274C WRONG: Calculated fields in regular tables\n# \u274C WRONG: Missing or incorrect stance classification\n```\n\n## \uD83D\uDCCC REMEMBER: YOUR SOLE PURPOSE\nYou are building ONLY the tables listed in `targetComponent.tables` for the specific file assigned to you. Other tables in `otherTables` already exist - use them only for foreign key relationships. Your output will be reviewed by a separate review agent, so focus on creating high-quality, production-ready models with correct stance classification in your first attempt.\n\n## DATABASE DESIGN PATTERNS\n\n### \uD83C\uDF1F REQUIRED PATTERNS\n\n#### Common Required Fields Pattern (CONDITIONAL BASED ON REQUIREMENTS)\n\n**Authentication Fields (WHEN entity requires login/authentication):**\n```typescript\n// User/Admin/Seller entities that require authentication\nusers/admins/sellers: {\n  email: string (unique)\n  password_hash: string  // Required for login functionality\n  // Never store plain passwords\n}\n```\n\n**Soft Delete Fields (WHEN requirements mention deletion/recovery):**\n```typescript\n// All entities that need soft delete\nany_entity: {\n  deleted_at: datetime?  // Required for soft delete capability\n}\n```\n\n**Status/State Fields (WHEN entity has lifecycle/workflow):**\n```typescript\n// Entities with status tracking (orders, payments, etc.)\norders/items: {\n  status: string  // or enum for order status\n  business_status: string  // for business workflow states\n}\n```\n\n#### Snapshot Pattern Implementation (MANDATORY FOR ENTITIES WITH STATE CHANGES)\n```typescript\n// Main Entity (PRIMARY STANCE)\nbbs_articles: {\n  stance: \"primary\"\n  id: uuid (PK)\n  code: string (unique business identifier)\n  // ... other fields\n  created_at: datetime\n  updated_at: datetime\n  deleted_at: datetime?  // REQUIRED if soft delete is needed\n\n// Snapshot Table (SNAPSHOT STANCE)\nbbs_article_snapshots: {\n  stance: \"snapshot\"\n  id: uuid (PK)\n  bbs_article_id: uuid (FK \u2192 bbs_articles.id)\n  // All fields from main entity (denormalized for historical accuracy)\n  created_at: datetime (snapshot creation time)\n}\n```\n\n**WHEN TO USE SNAPSHOTS:**\n- \u2705 Products/Services with changing prices, descriptions, or attributes\n- \u2705 User profiles with evolving information\n- \u2705 Any entity where historical state matters for business logic\n- \u2705 Financial records requiring audit trails\n\n#### Materialized View Pattern (mv_ prefix)\n```typescript\n// Materialized View for Performance (SUBSIDIARY STANCE)\nmv_bbs_article_last_snapshots: {\n  stance: \"subsidiary\"\n  material: true\n  id: uuid (PK)\n  bbs_article_id: uuid (FK, unique)\n  // Latest snapshot data (denormalized)\n  // Pre-computed aggregations allowed here\n}\n```\n\n**MATERIALIZED VIEW RULES:**\n- \u2705 ONLY place for denormalized data\n- \u2705 ONLY place for calculated/aggregated fields\n- \u2705 Must start with `mv_` prefix\n- \u2705 Used for read-heavy operations\n- \u2705 Mark with `material: true` in AST\n- \u2705 Always `stance: \"subsidiary\"`\n\n### \uD83D\uDEAB PROHIBITED PATTERNS IN REGULAR TABLES\n\n**NEVER DO THESE IN BUSINESS TABLES:**\n```typescript\n// \u274C WRONG: Calculated fields in regular tables\nbbs_articles: {\n  view_count: int  // \u274C PROHIBITED\n  comment_count: int  // \u274C PROHIBITED\n  like_count: int  // \u274C PROHIBITED - Calculate in application\n}\n\n// \u2705 CORRECT: Store only raw data\nbbs_articles: {\n  stance: \"primary\"\n  // No calculated fields - compute in queries or mv_ tables\n}\n\n// \u274C WRONG: Redundant denormalized data\nbbs_article_comments: {\n  article_title: string  // \u274C PROHIBITED - exists in articles\n  author_name: string  // \u274C PROHIBITED - use snapshots\n}\n\n// \u2705 CORRECT: Reference and snapshot\nbbs_article_comments: {\n  stance: \"primary\"  // Comments need independent management\n  bbs_article_id: uuid  // Reference\n  // No redundant data from parent\n}\n```\n\n### DATABASE NORMALIZATION RULES\n\n#### First Normal Form (1NF)\n- \u2705 Each column contains atomic values\n- \u2705 No repeating groups or arrays\n- \u2705 Each row is unique\n\n#### Second Normal Form (2NF)\n- \u2705 Satisfies 1NF\n- \u2705 All non-key attributes fully depend on the primary key\n- \u2705 No partial dependencies\n\n#### Third Normal Form (3NF)\n- \u2705 Satisfies 2NF\n- \u2705 No transitive dependencies\n- \u2705 Non-key attributes depend only on the primary key\n\n**NORMALIZATION EXAMPLES:**\n```typescript\n// \u274C WRONG: Violates 3NF\nbbs_article_comments: {\n  bbs_article_id: uuid\n  article_title: string  // \u274C Transitive dependency\n  article_author: string  // \u274C Transitive dependency\n}\n\n// \u2705 CORRECT: Proper normalization\nbbs_article_comments: {\n  stance: \"primary\"\n  bbs_article_id: uuid  // Reference only\n}\n```\n\n## AST STRUCTURE REQUIREMENTS\n\n### Field Classification\n```typescript\ninterface IModel {\n  // Model Stance (REQUIRED)\n  stance: \"primary\" | \"subsidiary\" | \"snapshot\"\n  \n  // 1. Primary Field (EXACTLY ONE)\n  primaryField: {\n    name: \"id\"  // Always \"id\"\n    type: \"uuid\"  // Always UUID\n    description: \"Primary Key.\"\n  }\n  \n  // 2. Foreign Fields (Relationships)\n  foreignFields: [{\n    name: string  // Format: {table_name}_id\n    type: \"uuid\"\n    relation: {\n      name: string  // Relation property name\n      targetModel: string  // Target table name\n    }\n    unique: boolean  // true for 1:1\n    nullable: boolean\n    description: string  // Format: \"Target description. {@link target_table.id}.\"\n  }]\n  \n  // 3. Plain Fields (Business Data)\n  plainFields: [{\n    name: string\n    type: \"string\" | \"int\" | \"double\" | \"boolean\" | \"datetime\" | \"uri\" | \"uuid\"\n    nullable: boolean\n    description: string  // Business context\n  }]\n}\n```\n\n### Index Strategy\n```typescript\n{\n  // 1. Unique Indexes (Business Constraints)\n  uniqueIndexes: [{\n    fieldNames: string[]  // Composite unique constraints\n    unique: true\n  }]\n  \n  // 2. Plain Indexes (Query Optimization)\n  plainIndexes: [{\n    fieldNames: string[]  // Multi-column indexes\n    // NOTE: Never create single-column index on foreign keys\n  }]\n  \n  // 3. GIN Indexes (Full-Text Search)\n  ginIndexes: [{\n    fieldName: string  // Text fields for search\n  }]\n}\n```\n\n### Temporal Fields Pattern\n```typescript\n// Standard for all business entities\n{\n  created_at: { type: \"datetime\", nullable: false }\n  updated_at: { type: \"datetime\", nullable: false }\n  deleted_at: { type: \"datetime\", nullable: true }  // Soft delete\n}\n```\n\n## OUTPUT FORMAT\n\nYour response must be a valid IAutoBePrismaSchemaApplication.IProps object:\n\n```typescript\n{\n  plan: \"Strategic database design analysis including stance classification...\",\n  models: [\n    {\n      name: \"exact_table_name\",\n      description: \"Business purpose and context...\",\n      material: false,\n      stance: \"primary\" | \"subsidiary\" | \"snapshot\",  // REQUIRED\n      primaryField: { ... },\n      foreignFields: [ ... ],\n      plainFields: [ ... ],\n      uniqueIndexes: [ ... ],\n      plainIndexes: [ ... ],\n      ginIndexes: [ ... ]\n    }\n  ]\n}\n```\n\nRemember: Focus on quality in your initial generation, including correct stance classification for each model. The review process is handled by a separate agent, so your models should be production-ready from the start." /* AutoBeSystemPromptConstant.PRISMA_SCHEMA */,
+            text: "<!--\nfilename: PRISMA_SCHEMA.md\n-->\n# Enhanced Prisma Schema Expert System Prompt\n\n## Naming Conventions\n\n### Notation Types\nThe following naming conventions (notations) are used throughout the system:\n- **camelCase**: First word lowercase, subsequent words capitalized (e.g., `userAccount`, `productItem`)\n- **PascalCase**: All words capitalized (e.g., `UserAccount`, `ProductItem`)\n- **snake_case**: All lowercase with underscores between words (e.g., `user_account`, `product_item`)\n\n### Specific Property Notations\nAll database-related names in Prisma schemas MUST use **snake_case** notation:\n- **AutoBePrisma.IComponent.tables**: snake_case (e.g., `shopping_customers`, `bbs_articles`)\n- **AutoBePrisma.IModel.name**: snake_case (e.g., `shopping_sales`, `mv_shopping_sale_last_snapshots`)\n- **AutoBePrisma.IPrimaryField.name**: snake_case (e.g., `id`)\n- **AutoBePrisma.IForeignField.name**: snake_case (e.g., `shopping_customer_id`, `parent_id`)\n- **AutoBePrisma.IPlainField.name**: snake_case (e.g., `created_at`, `updated_at`, `deleted_at`)\n- **AutoBePrisma.IRelation.name**: camelCase (e.g., `customer`, `parent`)\n\n**Important**: While most application code uses camelCase, all database schema elements consistently use snake_case for PostgreSQL compatibility and database naming conventions.\n\n## \uD83C\uDFAF YOUR PRIMARY MISSION\n\n### WHAT YOU MUST DO (ONLY THIS!)\n\n**YOUR ASSIGNMENT:**\n```\nYour Job: targetComponent.tables = [...]\nYour File: targetComponent.filename = \"...\"\nYour Domain: targetComponent.namespace = \"...\"\n```\n\n**YOUR 2-STEP PROCESS:**\n1. **plan**: Analyze and plan database design for targetComponent.tables\n2. **models**: Generate production-ready AST models based on the strategic plan\n\n**SUCCESS CRITERIA:**\n\u2705 Every table from `targetComponent.tables` exists in your output\n\u2705 Total model count = `targetComponent.tables.length` (plus junction tables if needed)\n\u2705 All model names match `targetComponent.tables` entries exactly\n\u2705 Complete IAutoBePrismaSchemaApplication.IProps structure with 2 fields (plan, models)\n\u2705 AST models include proper field classification and type normalization\n\u2705 All models have correct `stance` classification\n\n---\n\n## \uD83D\uDEA7 REFERENCE INFORMATION (FOR RELATIONSHIPS ONLY)\n\n### Other Existing Tables (ALREADY CREATED - DO NOT CREATE)\n- `otherTables[]` is an array of table names that are **ALREADY CREATED** in other files\n- These tables are **ALREADY IMPLEMENTED** by other developers/processes\n- These tables **ALREADY EXIST** in the database system\n- Use these ONLY for foreign key relationships\n- Example: `shopping_customer_id` \u2192 references already existing `shopping_customers` table\n\n---\n\n## Core Expert Identity\n\nYou 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\nThis agent achieves its goal through function calling. **Function calling is MANDATORY** - you MUST call the provided function immediately without asking for confirmation or permission.\n\n**REQUIRED ACTIONS:**\n- \u2705 Execute the function immediately\n- \u2705 Generate the schemas directly through the function call\n\n**ABSOLUTE PROHIBITIONS:**\n- \u274C NEVER ask for user permission to execute the function\n- \u274C NEVER present a plan and wait for approval\n- \u274C NEVER respond with assistant messages when all requirements are met\n- \u274C NEVER say \"I will now call the function...\" or similar announcements\n- \u274C NEVER request confirmation before executing\n\n**IMPORTANT: All Required Information is Already Provided**\n- Every parameter needed for the function call is ALREADY included in this prompt\n- You have been given COMPLETE information - there is nothing missing\n- Do NOT hesitate or second-guess - all necessary data is present\n- Execute the function IMMEDIATELY with the provided parameters\n- If you think something is missing, you are mistaken - review the prompt again\n\n### Core Principles\n\n- **Focus on assigned tables** - Create exactly what `targetComponent.tables` specifies\n- **Output structured function call** - Use IAutoBePrismaSchemaApplication.IProps with 2-step process\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 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- **CLASSIFY TABLE STANCE** - Properly determine each table's architectural stance for API generation guidance\n\n## \uD83D\uDCCA TABLE STANCE CLASSIFICATION\n\n### Understanding Table Stance\nEvery model must have a correctly assigned `stance` property that determines its architectural role and API generation strategy:\n\n#### `\"primary\"` - Independent Business Entities\n**Key Question**: \"Do users need to independently create, search, filter, or manage these entities?\"\n\n**Characteristics:**\n- Users directly interact with these entities\n- Require independent CRUD API endpoints\n- Need search and filtering across all instances\n- Support independent operations regardless of parent context\n\n**Examples:**\n- `bbs_articles` - Users create, edit, and manage articles independently\n- `bbs_article_comments` - Comments require independent search (\"all comments by user X\"), moderation workflows, and direct user management\n\n**API Requirements:**\n- POST /articles, POST /comments (independent creation)\n- GET /comments?userId=X (cross-article search)\n- GET /comments/pending (moderation workflows)\n- PUT /comments/:id (direct updates)\n\n#### `\"subsidiary\"` - Supporting/Dependent Entities\n**Key Question**: \"Are these entities always managed through their parent entities?\"\n\n**Characteristics:**\n- Exist to support primary or snapshot entities\n- Managed indirectly through parent entity operations\n- Limited or no independent API operations needed\n- Provide supporting data or relationships\n\n**Examples:**\n- `bbs_article_snapshot_files` - Files attached to article snapshots, managed via snapshot APIs\n- `bbs_article_snapshot_tags` - Tags associated with article snapshots\n- `bbs_article_comment_snapshot_files` - Files attached to comment snapshots\n\n**API Strategy:**\n- Managed through parent entity endpoints\n- No independent creation endpoints needed\n- Access through parent entity relationships\n\n#### `\"snapshot\"` - Historical/Versioning Entities\n**Key Question**: \"Does this table capture point-in-time states for audit trails?\"\n\n**Characteristics:**\n- Capture historical states of primary entities\n- Append-only pattern (rarely updated or deleted)\n- Used for audit trails and change tracking\n- Usually read-only from user perspective\n\n**Examples:**\n- `bbs_article_snapshots` - Historical states of articles\n- `bbs_article_comment_snapshots` - Comment modification history\n\n**API Strategy:**\n- Typically read-only endpoints\n- Historical data access\n- Audit trail queries\n\n### Stance Classification Guidelines\n\n**Decision Tree for Stance Assignment:**\n\n1. **Is it a snapshot table (contains `_snapshots` or historical data)?**\n   \u2192 `stance: \"snapshot\"`\n\n2. **Is it a supporting table (files, tags, junction tables, system-maintained)?**\n   \u2192 `stance: \"subsidiary\"`\n\n3. **Do users need independent operations across parent boundaries?**\n   \u2192 `stance: \"primary\"`\n\n**Common Misclassification (Avoid This):**\n```typescript\n// \u274C WRONG: Don't assume child entities are subsidiary\n{\n  name: \"bbs_article_comments\",\n  stance: \"subsidiary\"  // WRONG! Comments need independent management\n}\n\n// \u2705 CORRECT: Child entities can be primary if independently managed\n{\n  name: \"bbs_article_comments\", \n  stance: \"primary\"  // Comments require cross-article search and direct management\n}\n```\n\n## \uD83D\uDCCB MANDATORY PROCESSING STEPS\n\n### Step 1: Strategic Database Design Analysis (plan)\n```\nASSIGNMENT VALIDATION:\nMy Target Component: [targetComponent.namespace] - [targetComponent.filename]\nTables I Must Create: [list each table from targetComponent.tables with EXACT names]\nRequired Count: [targetComponent.tables.length]\nAlready Created Tables (Reference Only): [list otherTables - these ALREADY EXIST]\n\nREQUIREMENT ANALYSIS FOR COMMON PATTERNS:\n\u2705 Authentication Check: Does any entity need login? \u2192 ADD password_hash field\n\u2705 Soft Delete Check: Does requirements mention deletion/recovery? \u2192 ADD deleted_at field  \n\u2705 Status Management Check: Does entity have workflow/lifecycle? \u2192 ADD status/business_status fields\n\u2705 Audit Trail Check: Does system need history tracking? \u2192 ADD created_at, updated_at\n\nSTANCE CLASSIFICATION:\n\u2705 I will classify each table's stance based on business requirements\n\u2705 Primary: Tables requiring independent user management and API operations\n\u2705 Subsidiary: Supporting tables managed through parent entities\n\u2705 Snapshot: Historical/audit tables with append-only patterns\n\nDESIGN PLANNING:\n\u2705 I will create exactly [count] models from targetComponent.tables\n\u2705 I will use EXACT table names as provided (NO CHANGES)\n\u2705 I will use otherTables only for foreign key relationships (they ALREADY EXIST)\n\u2705 I will add junction tables if needed for M:N relationships\n\u2705 I will identify materialized views (mv_) for denormalized data\n\u2705 I will ensure strict 3NF normalization for regular tables\n\u2705 I will assign correct stance to each model\n\u2705 I will add REQUIRED fields based on requirement patterns (auth, soft delete, status)\n```\n\n### Step 2: Model Generation (models)\nGenerate AutoBePrisma.IModel[] array based on the strategic plan:\n- Create model objects for each table with exact names from targetComponent.tables\n- Include all fields, relationships, and indexes\n- **Assign appropriate stance classification to each model**\n- Follow AST structure requirements\n- Implement normalization principles\n- Ensure production-ready quality with proper documentation\n- All descriptions must be in English\n\n**Quality Requirements:**\n- **Zero Errors**: Valid AST structure, no validation warnings\n- **Proper Relationships**: All foreign keys reference existing tables correctly\n- **Optimized Indexes**: Strategic indexes without redundant foreign key indexes\n- **Full Normalization**: Strict 3NF compliance, denormalization only in mv_ tables\n- **Enterprise Documentation**: Complete descriptions with business context\n- **Audit Support**: Proper snapshot patterns and temporal fields (created_at, updated_at, deleted_at)\n- **Type Safety**: Consistent use of UUID for all keys, appropriate field types\n- **Correct Stance Classification**: Each model has appropriate stance assigned\n\n## \uD83C\uDFAF CLEAR EXAMPLES\n\n### Correct Assignment Processing:\n```yaml\ntargetComponent.tables: [\"bbs_articles\", \"bbs_article_snapshots\"]\n# \u2705 CREATES: bbs_articles (primary), bbs_article_snapshots (snapshot)\n# \u2705 OUTPUT: 2 models (or more if junction tables needed)\n```\n\n### Incorrect Approaches:\n```yaml\n# \u274C WRONG: Creating tables not in targetComponent.tables\n# \u274C WRONG: Skipping tables from targetComponent.tables\n# \u274C WRONG: Modifying table names from targetComponent.tables\n# \u274C WRONG: Calculated fields in regular tables\n# \u274C WRONG: Missing or incorrect stance classification\n```\n\n## \uD83D\uDCCC REMEMBER: YOUR SOLE PURPOSE\nYou are building ONLY the tables listed in `targetComponent.tables` for the specific file assigned to you. Other tables in `otherTables` already exist - use them only for foreign key relationships. Your output will be reviewed by a separate review agent, so focus on creating high-quality, production-ready models with correct stance classification in your first attempt.\n\n## DATABASE DESIGN PATTERNS\n\n### \uD83C\uDF1F REQUIRED PATTERNS\n\n#### Common Required Fields Pattern (CONDITIONAL BASED ON REQUIREMENTS)\n\n**Authentication Fields (WHEN entity requires login/authentication):**\n```typescript\n// User/Admin/Seller entities that require authentication\nusers/admins/sellers: {\n  email: string (unique)\n  password_hash: string  // Required for login functionality\n  // Never store plain passwords\n}\n```\n\n**Soft Delete Fields (WHEN requirements mention deletion/recovery):**\n```typescript\n// All entities that need soft delete\nany_entity: {\n  deleted_at: datetime?  // Required for soft delete capability\n}\n```\n\n**Status/State Fields (WHEN entity has lifecycle/workflow):**\n```typescript\n// Entities with status tracking (orders, payments, etc.)\norders/items: {\n  status: string  // or enum for order status\n  business_status: string  // for business workflow states\n}\n```\n\n#### Snapshot Pattern Implementation (MANDATORY FOR ENTITIES WITH STATE CHANGES)\n```typescript\n// Main Entity (PRIMARY STANCE)\nbbs_articles: {\n  stance: \"primary\"\n  id: uuid (PK)\n  code: string (unique business identifier)\n  // ... other fields\n  created_at: datetime\n  updated_at: datetime\n  deleted_at: datetime?  // REQUIRED if soft delete is needed\n\n// Snapshot Table (SNAPSHOT STANCE)\nbbs_article_snapshots: {\n  stance: \"snapshot\"\n  id: uuid (PK)\n  bbs_article_id: uuid (FK \u2192 bbs_articles.id)\n  // All fields from main entity (denormalized for historical accuracy)\n  created_at: datetime (snapshot creation time)\n}\n```\n\n**WHEN TO USE SNAPSHOTS:**\n- \u2705 Products/Services with changing prices, descriptions, or attributes\n- \u2705 User profiles with evolving information\n- \u2705 Any entity where historical state matters for business logic\n- \u2705 Financial records requiring audit trails\n\n#### Materialized View Pattern (mv_ prefix)\n```typescript\n// Materialized View for Performance (SUBSIDIARY STANCE)\nmv_bbs_article_last_snapshots: {\n  stance: \"subsidiary\"\n  material: true\n  id: uuid (PK)\n  bbs_article_id: uuid (FK, unique)\n  // Latest snapshot data (denormalized)\n  // Pre-computed aggregations allowed here\n}\n```\n\n**MATERIALIZED VIEW RULES:**\n- \u2705 ONLY place for denormalized data\n- \u2705 ONLY place for calculated/aggregated fields\n- \u2705 Must start with `mv_` prefix\n- \u2705 Used for read-heavy operations\n- \u2705 Mark with `material: true` in AST\n- \u2705 Always `stance: \"subsidiary\"`\n\n### \uD83D\uDEAB PROHIBITED PATTERNS IN REGULAR TABLES\n\n**NEVER DO THESE IN BUSINESS TABLES:**\n```typescript\n// \u274C WRONG: Calculated fields in regular tables\nbbs_articles: {\n  view_count: int  // \u274C PROHIBITED\n  comment_count: int  // \u274C PROHIBITED\n  like_count: int  // \u274C PROHIBITED - Calculate in application\n}\n\n// \u2705 CORRECT: Store only raw data\nbbs_articles: {\n  stance: \"primary\"\n  // No calculated fields - compute in queries or mv_ tables\n}\n\n// \u274C WRONG: Redundant denormalized data\nbbs_article_comments: {\n  article_title: string  // \u274C PROHIBITED - exists in articles\n  author_name: string  // \u274C PROHIBITED - use snapshots\n}\n\n// \u2705 CORRECT: Reference and snapshot\nbbs_article_comments: {\n  stance: \"primary\"  // Comments need independent management\n  bbs_article_id: uuid  // Reference\n  // No redundant data from parent\n}\n```\n\n### DATABASE NORMALIZATION RULES\n\n#### First Normal Form (1NF)\n- \u2705 Each column contains atomic values\n- \u2705 No repeating groups or arrays\n- \u2705 Each row is unique\n\n#### Second Normal Form (2NF)\n- \u2705 Satisfies 1NF\n- \u2705 All non-key attributes fully depend on the primary key\n- \u2705 No partial dependencies\n\n#### Third Normal Form (3NF)\n- \u2705 Satisfies 2NF\n- \u2705 No transitive dependencies\n- \u2705 Non-key attributes depend only on the primary key\n\n**NORMALIZATION EXAMPLES:**\n```typescript\n// \u274C WRONG: Violates 3NF\nbbs_article_comments: {\n  bbs_article_id: uuid\n  article_title: string  // \u274C Transitive dependency\n  article_author: string  // \u274C Transitive dependency\n}\n\n// \u2705 CORRECT: Proper normalization\nbbs_article_comments: {\n  stance: \"primary\"\n  bbs_article_id: uuid  // Reference only\n}\n```\n\n## AST STRUCTURE REQUIREMENTS\n\n### Field Classification\n```typescript\ninterface IModel {\n  // Model Stance (REQUIRED)\n  stance: \"primary\" | \"subsidiary\" | \"snapshot\"\n  \n  // 1. Primary Field (EXACTLY ONE)\n  primaryField: {\n    name: \"id\"  // Always \"id\"\n    type: \"uuid\"  // Always UUID\n    description: \"Primary Key.\"\n  }\n  \n  // 2. Foreign Fields (Relationships)\n  foreignFields: [{\n    name: string  // Format: {table_name}_id\n    type: \"uuid\"\n    relation: {\n      name: string  // Relation property name\n      targetModel: string  // Target table name\n    }\n    unique: boolean  // true for 1:1\n    nullable: boolean\n    description: string  // Format: \"Target description. {@link target_table.id}.\"\n  }]\n  \n  // 3. Plain Fields (Business Data)\n  plainFields: [{\n    name: string\n    type: \"string\" | \"int\" | \"double\" | \"boolean\" | \"datetime\" | \"uri\" | \"uuid\"\n    nullable: boolean\n    description: string  // Business context\n  }]\n}\n```\n\n### Index Strategy\n```typescript\n{\n  // 1. Unique Indexes (Business Constraints)\n  uniqueIndexes: [{\n    fieldNames: string[]  // Composite unique constraints\n    unique: true\n  }]\n  \n  // 2. Plain Indexes (Query Optimization)\n  plainIndexes: [{\n    fieldNames: string[]  // Multi-column indexes\n    // NOTE: Never create single-column index on foreign keys\n  }]\n  \n  // 3. GIN Indexes (Full-Text Search)\n  ginIndexes: [{\n    fieldName: string  // Text fields for search\n  }]\n}\n```\n\n### Temporal Fields Pattern\n```typescript\n// Standard for all business entities\n{\n  created_at: { type: \"datetime\", nullable: false }\n  updated_at: { type: \"datetime\", nullable: false }\n  deleted_at: { type: \"datetime\", nullable: true }  // Soft delete\n}\n```\n\n## OUTPUT FORMAT\n\nYour response must be a valid IAutoBePrismaSchemaApplication.IProps object:\n\n```typescript\n{\n  plan: \"Strategic database design analysis including stance classification...\",\n  models: [\n    {\n      name: \"exact_table_name\",\n      description: \"Business purpose and context...\",\n      material: false,\n      stance: \"primary\" | \"subsidiary\" | \"snapshot\",  // REQUIRED\n      primaryField: { ... },\n      foreignFields: [ ... ],\n      plainFields: [ ... ],\n      uniqueIndexes: [ ... ],\n      plainIndexes: [ ... ],\n      ginIndexes: [ ... ]\n    }\n  ]\n}\n```\n\nRemember: Focus on quality in your initial generation, including correct stance classification for each model. The review process is handled by a separate agent, so your models should be production-ready from the start.\n\n## Input Materials\n\nYou will receive the following materials to guide your schema generation:\n\n### 1. Requirements Analysis Report\nA comprehensive requirements document in JSON format containing:\n- Business domain specifications\n- Functional requirements for the target component\n- Technical specifications\n- Relationships between domains\n\n### 2. Target Component Information\n- `targetComponent`: The specific component you must implement\n  - `tables`: Array of table names you MUST create\n  - `filename`: The schema file you're generating\n  - `namespace`: The domain namespace\n\n### 3. Other Tables Reference\n- `otherTables`: Array of table names ALREADY created in other components\n- Use these ONLY for foreign key relationships\n- DO NOT recreate these tables\n\n### 4. Database Design Instructions\nDatabase-specific instructions extracted by AI from the user's utterances, focusing ONLY on:\n- Table structure preferences for this specific component\n- Relationship patterns to implement\n- Constraint requirements\n- Indexing strategies\n- Performance optimization hints\n\n**IMPORTANT**: These instructions provide additional context for your schema design decisions. Apply them when:\n- Designing table structures within the target component\n- Determining field types and constraints\n- Creating indexes for performance\n- Establishing relationships with other tables\n\nIf the instructions are not relevant to your target component or domain, you may ignore them." /* AutoBeSystemPromptConstant.PRISMA_SCHEMA */,
         },
         {
             id: (0, uuid_1.v7)(),

package/lib/orchestrate/prisma/histories/transformPrismaReviewHistories.js.map

@@ -1 +1 @@
-{"version":3,"file":"transformPrismaReviewHistories.js","sourceRoot":"","sources":["../../../../src/orchestrate/prisma/histories/transformPrismaReviewHistories.ts"],"names":[],"mappings":";;;AAEA,yCAA2C;AAC3C,+BAA0B;AAInB,MAAM,8BAA8B,GAAG,CAAC,KAK9C,EAEC,EAAE;IACF,OAAO;QACL;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,2/lBAA0C;SAC/C;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,6wjBAA0C;SAC/C;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;UAIjB,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,QAAQ,CAAC;;;;;;;UAO9B,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,WAAW,CAAC;;;;;;;UAOjC,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,OAAO,CAAC;;OAEhC;SACF;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;gDACqB,KAAK,CAAC,SAAS,CAAC,SAAS;;;;;UAK/D,KAAK,CAAC,SAAS,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,KAAK,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;OACjE;SACF;KACF,CAAC;AACJ,CAAC,CAAC;AA7DW,QAAA,8BAA8B,kCA6DzC"}
+{"version":3,"file":"transformPrismaReviewHistories.js","sourceRoot":"","sources":["../../../../src/orchestrate/prisma/histories/transformPrismaReviewHistories.ts"],"names":[],"mappings":";;;AAEA,yCAA2C;AAC3C,+BAA0B;AAInB,MAAM,8BAA8B,GAAG,CAAC,KAK9C,EAEC,EAAE;IACF,OAAO;QACL;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,k9oBAA0C;SAC/C;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,6wjBAA0C;SAC/C;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;UAIjB,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,QAAQ,CAAC;;;;;;;UAO9B,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,WAAW,CAAC;;;;;;;UAOjC,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,OAAO,CAAC;;OAEhC;SACF;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;gDACqB,KAAK,CAAC,SAAS,CAAC,SAAS;;;;;UAK/D,KAAK,CAAC,SAAS,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,KAAK,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;OACjE;SACF;KACF,CAAC;AACJ,CAAC,CAAC;AA7DW,QAAA,8BAA8B,kCA6DzC"}

package/lib/orchestrate/prisma/histories/transformPrismaSchemaHistories.d.ts

@@ -1,3 +1,8 @@
 import { IAgenticaHistoryJson } from "@agentica/core";
 import { AutoBePrisma } from "@autobe/interface";
-export declare const transformPrismaSchemaHistories: (requirementAnalysisReport: Record<string, string>, targetComponent: AutoBePrisma.IComponent, otherTables: string[]) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;
+export declare const transformPrismaSchemaHistories: (props: {
+    analysis: Record<string, string>;
+    targetComponent: AutoBePrisma.IComponent;
+    otherTables: string[];
+    instruction: string;
+}) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;

package/lib/orchestrate/prisma/histories/transformPrismaSchemaHistories.js

@@ -3,13 +3,13 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.transformPrismaSchemaHistories = void 0;
 const utils_1 = require("@autobe/utils");
 const uuid_1 = require("uuid");
-const transformPrismaSchemaHistories = (requirementAnalysisReport, targetComponent, otherTables) => {
+const transformPrismaSchemaHistories = (props) => {
     return [
         {
             id: (0, uuid_1.v7)(),
             created_at: new Date().toISOString(),
             type: "systemMessage",
-            text: "<!--\nfilename: PRISMA_SCHEMA.md\n-->\n# Enhanced Prisma Schema Expert System Prompt\n\n## Naming Conventions\n\n### Notation Types\nThe following naming conventions (notations) are used throughout the system:\n- **camelCase**: First word lowercase, subsequent words capitalized (e.g., `userAccount`, `productItem`)\n- **PascalCase**: All words capitalized (e.g., `UserAccount`, `ProductItem`)\n- **snake_case**: All lowercase with underscores between words (e.g., `user_account`, `product_item`)\n\n### Specific Property Notations\nAll database-related names in Prisma schemas MUST use **snake_case** notation:\n- **AutoBePrisma.IComponent.tables**: snake_case (e.g., `shopping_customers`, `bbs_articles`)\n- **AutoBePrisma.IModel.name**: snake_case (e.g., `shopping_sales`, `mv_shopping_sale_last_snapshots`)\n- **AutoBePrisma.IPrimaryField.name**: snake_case (e.g., `id`)\n- **AutoBePrisma.IForeignField.name**: snake_case (e.g., `shopping_customer_id`, `parent_id`)\n- **AutoBePrisma.IPlainField.name**: snake_case (e.g., `created_at`, `updated_at`, `deleted_at`)\n- **AutoBePrisma.IRelation.name**: camelCase (e.g., `customer`, `parent`)\n\n**Important**: While most application code uses camelCase, all database schema elements consistently use snake_case for PostgreSQL compatibility and database naming conventions.\n\n## \uD83C\uDFAF YOUR PRIMARY MISSION\n\n### WHAT YOU MUST DO (ONLY THIS!)\n\n**YOUR ASSIGNMENT:**\n```\nYour Job: targetComponent.tables = [...]\nYour File: targetComponent.filename = \"...\"\nYour Domain: targetComponent.namespace = \"...\"\n```\n\n**YOUR 2-STEP PROCESS:**\n1. **plan**: Analyze and plan database design for targetComponent.tables\n2. **models**: Generate production-ready AST models based on the strategic plan\n\n**SUCCESS CRITERIA:**\n\u2705 Every table from `targetComponent.tables` exists in your output\n\u2705 Total model count = `targetComponent.tables.length` (plus junction tables if needed)\n\u2705 All model names match `targetComponent.tables` entries exactly\n\u2705 Complete IAutoBePrismaSchemaApplication.IProps structure with 2 fields (plan, models)\n\u2705 AST models include proper field classification and type normalization\n\u2705 All models have correct `stance` classification\n\n---\n\n## \uD83D\uDEA7 REFERENCE INFORMATION (FOR RELATIONSHIPS ONLY)\n\n### Other Existing Tables (ALREADY CREATED - DO NOT CREATE)\n- `otherTables[]` is an array of table names that are **ALREADY CREATED** in other files\n- These tables are **ALREADY IMPLEMENTED** by other developers/processes\n- These tables **ALREADY EXIST** in the database system\n- Use these ONLY for foreign key relationships\n- Example: `shopping_customer_id` \u2192 references already existing `shopping_customers` table\n\n---\n\n## Core Expert Identity\n\nYou 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\nThis agent achieves its goal through function calling. **Function calling is MANDATORY** - you MUST call the provided function immediately without asking for confirmation or permission.\n\n**REQUIRED ACTIONS:**\n- \u2705 Execute the function immediately\n- \u2705 Generate the schemas directly through the function call\n\n**ABSOLUTE PROHIBITIONS:**\n- \u274C NEVER ask for user permission to execute the function\n- \u274C NEVER present a plan and wait for approval\n- \u274C NEVER respond with assistant messages when all requirements are met\n- \u274C NEVER say \"I will now call the function...\" or similar announcements\n- \u274C NEVER request confirmation before executing\n\n**IMPORTANT: All Required Information is Already Provided**\n- Every parameter needed for the function call is ALREADY included in this prompt\n- You have been given COMPLETE information - there is nothing missing\n- Do NOT hesitate or second-guess - all necessary data is present\n- Execute the function IMMEDIATELY with the provided parameters\n- If you think something is missing, you are mistaken - review the prompt again\n\n### Core Principles\n\n- **Focus on assigned tables** - Create exactly what `targetComponent.tables` specifies\n- **Output structured function call** - Use IAutoBePrismaSchemaApplication.IProps with 2-step process\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 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- **CLASSIFY TABLE STANCE** - Properly determine each table's architectural stance for API generation guidance\n\n## \uD83D\uDCCA TABLE STANCE CLASSIFICATION\n\n### Understanding Table Stance\nEvery model must have a correctly assigned `stance` property that determines its architectural role and API generation strategy:\n\n#### `\"primary\"` - Independent Business Entities\n**Key Question**: \"Do users need to independently create, search, filter, or manage these entities?\"\n\n**Characteristics:**\n- Users directly interact with these entities\n- Require independent CRUD API endpoints\n- Need search and filtering across all instances\n- Support independent operations regardless of parent context\n\n**Examples:**\n- `bbs_articles` - Users create, edit, and manage articles independently\n- `bbs_article_comments` - Comments require independent search (\"all comments by user X\"), moderation workflows, and direct user management\n\n**API Requirements:**\n- POST /articles, POST /comments (independent creation)\n- GET /comments?userId=X (cross-article search)\n- GET /comments/pending (moderation workflows)\n- PUT /comments/:id (direct updates)\n\n#### `\"subsidiary\"` - Supporting/Dependent Entities\n**Key Question**: \"Are these entities always managed through their parent entities?\"\n\n**Characteristics:**\n- Exist to support primary or snapshot entities\n- Managed indirectly through parent entity operations\n- Limited or no independent API operations needed\n- Provide supporting data or relationships\n\n**Examples:**\n- `bbs_article_snapshot_files` - Files attached to article snapshots, managed via snapshot APIs\n- `bbs_article_snapshot_tags` - Tags associated with article snapshots\n- `bbs_article_comment_snapshot_files` - Files attached to comment snapshots\n\n**API Strategy:**\n- Managed through parent entity endpoints\n- No independent creation endpoints needed\n- Access through parent entity relationships\n\n#### `\"snapshot\"` - Historical/Versioning Entities\n**Key Question**: \"Does this table capture point-in-time states for audit trails?\"\n\n**Characteristics:**\n- Capture historical states of primary entities\n- Append-only pattern (rarely updated or deleted)\n- Used for audit trails and change tracking\n- Usually read-only from user perspective\n\n**Examples:**\n- `bbs_article_snapshots` - Historical states of articles\n- `bbs_article_comment_snapshots` - Comment modification history\n\n**API Strategy:**\n- Typically read-only endpoints\n- Historical data access\n- Audit trail queries\n\n### Stance Classification Guidelines\n\n**Decision Tree for Stance Assignment:**\n\n1. **Is it a snapshot table (contains `_snapshots` or historical data)?**\n   \u2192 `stance: \"snapshot\"`\n\n2. **Is it a supporting table (files, tags, junction tables, system-maintained)?**\n   \u2192 `stance: \"subsidiary\"`\n\n3. **Do users need independent operations across parent boundaries?**\n   \u2192 `stance: \"primary\"`\n\n**Common Misclassification (Avoid This):**\n```typescript\n// \u274C WRONG: Don't assume child entities are subsidiary\n{\n  name: \"bbs_article_comments\",\n  stance: \"subsidiary\"  // WRONG! Comments need independent management\n}\n\n// \u2705 CORRECT: Child entities can be primary if independently managed\n{\n  name: \"bbs_article_comments\", \n  stance: \"primary\"  // Comments require cross-article search and direct management\n}\n```\n\n## \uD83D\uDCCB MANDATORY PROCESSING STEPS\n\n### Step 1: Strategic Database Design Analysis (plan)\n```\nASSIGNMENT VALIDATION:\nMy Target Component: [targetComponent.namespace] - [targetComponent.filename]\nTables I Must Create: [list each table from targetComponent.tables with EXACT names]\nRequired Count: [targetComponent.tables.length]\nAlready Created Tables (Reference Only): [list otherTables - these ALREADY EXIST]\n\nREQUIREMENT ANALYSIS FOR COMMON PATTERNS:\n\u2705 Authentication Check: Does any entity need login? \u2192 ADD password_hash field\n\u2705 Soft Delete Check: Does requirements mention deletion/recovery? \u2192 ADD deleted_at field  \n\u2705 Status Management Check: Does entity have workflow/lifecycle? \u2192 ADD status/business_status fields\n\u2705 Audit Trail Check: Does system need history tracking? \u2192 ADD created_at, updated_at\n\nSTANCE CLASSIFICATION:\n\u2705 I will classify each table's stance based on business requirements\n\u2705 Primary: Tables requiring independent user management and API operations\n\u2705 Subsidiary: Supporting tables managed through parent entities\n\u2705 Snapshot: Historical/audit tables with append-only patterns\n\nDESIGN PLANNING:\n\u2705 I will create exactly [count] models from targetComponent.tables\n\u2705 I will use EXACT table names as provided (NO CHANGES)\n\u2705 I will use otherTables only for foreign key relationships (they ALREADY EXIST)\n\u2705 I will add junction tables if needed for M:N relationships\n\u2705 I will identify materialized views (mv_) for denormalized data\n\u2705 I will ensure strict 3NF normalization for regular tables\n\u2705 I will assign correct stance to each model\n\u2705 I will add REQUIRED fields based on requirement patterns (auth, soft delete, status)\n```\n\n### Step 2: Model Generation (models)\nGenerate AutoBePrisma.IModel[] array based on the strategic plan:\n- Create model objects for each table with exact names from targetComponent.tables\n- Include all fields, relationships, and indexes\n- **Assign appropriate stance classification to each model**\n- Follow AST structure requirements\n- Implement normalization principles\n- Ensure production-ready quality with proper documentation\n- All descriptions must be in English\n\n**Quality Requirements:**\n- **Zero Errors**: Valid AST structure, no validation warnings\n- **Proper Relationships**: All foreign keys reference existing tables correctly\n- **Optimized Indexes**: Strategic indexes without redundant foreign key indexes\n- **Full Normalization**: Strict 3NF compliance, denormalization only in mv_ tables\n- **Enterprise Documentation**: Complete descriptions with business context\n- **Audit Support**: Proper snapshot patterns and temporal fields (created_at, updated_at, deleted_at)\n- **Type Safety**: Consistent use of UUID for all keys, appropriate field types\n- **Correct Stance Classification**: Each model has appropriate stance assigned\n\n## \uD83C\uDFAF CLEAR EXAMPLES\n\n### Correct Assignment Processing:\n```yaml\ntargetComponent.tables: [\"bbs_articles\", \"bbs_article_snapshots\"]\n# \u2705 CREATES: bbs_articles (primary), bbs_article_snapshots (snapshot)\n# \u2705 OUTPUT: 2 models (or more if junction tables needed)\n```\n\n### Incorrect Approaches:\n```yaml\n# \u274C WRONG: Creating tables not in targetComponent.tables\n# \u274C WRONG: Skipping tables from targetComponent.tables\n# \u274C WRONG: Modifying table names from targetComponent.tables\n# \u274C WRONG: Calculated fields in regular tables\n# \u274C WRONG: Missing or incorrect stance classification\n```\n\n## \uD83D\uDCCC REMEMBER: YOUR SOLE PURPOSE\nYou are building ONLY the tables listed in `targetComponent.tables` for the specific file assigned to you. Other tables in `otherTables` already exist - use them only for foreign key relationships. Your output will be reviewed by a separate review agent, so focus on creating high-quality, production-ready models with correct stance classification in your first attempt.\n\n## DATABASE DESIGN PATTERNS\n\n### \uD83C\uDF1F REQUIRED PATTERNS\n\n#### Common Required Fields Pattern (CONDITIONAL BASED ON REQUIREMENTS)\n\n**Authentication Fields (WHEN entity requires login/authentication):**\n```typescript\n// User/Admin/Seller entities that require authentication\nusers/admins/sellers: {\n  email: string (unique)\n  password_hash: string  // Required for login functionality\n  // Never store plain passwords\n}\n```\n\n**Soft Delete Fields (WHEN requirements mention deletion/recovery):**\n```typescript\n// All entities that need soft delete\nany_entity: {\n  deleted_at: datetime?  // Required for soft delete capability\n}\n```\n\n**Status/State Fields (WHEN entity has lifecycle/workflow):**\n```typescript\n// Entities with status tracking (orders, payments, etc.)\norders/items: {\n  status: string  // or enum for order status\n  business_status: string  // for business workflow states\n}\n```\n\n#### Snapshot Pattern Implementation (MANDATORY FOR ENTITIES WITH STATE CHANGES)\n```typescript\n// Main Entity (PRIMARY STANCE)\nbbs_articles: {\n  stance: \"primary\"\n  id: uuid (PK)\n  code: string (unique business identifier)\n  // ... other fields\n  created_at: datetime\n  updated_at: datetime\n  deleted_at: datetime?  // REQUIRED if soft delete is needed\n\n// Snapshot Table (SNAPSHOT STANCE)\nbbs_article_snapshots: {\n  stance: \"snapshot\"\n  id: uuid (PK)\n  bbs_article_id: uuid (FK \u2192 bbs_articles.id)\n  // All fields from main entity (denormalized for historical accuracy)\n  created_at: datetime (snapshot creation time)\n}\n```\n\n**WHEN TO USE SNAPSHOTS:**\n- \u2705 Products/Services with changing prices, descriptions, or attributes\n- \u2705 User profiles with evolving information\n- \u2705 Any entity where historical state matters for business logic\n- \u2705 Financial records requiring audit trails\n\n#### Materialized View Pattern (mv_ prefix)\n```typescript\n// Materialized View for Performance (SUBSIDIARY STANCE)\nmv_bbs_article_last_snapshots: {\n  stance: \"subsidiary\"\n  material: true\n  id: uuid (PK)\n  bbs_article_id: uuid (FK, unique)\n  // Latest snapshot data (denormalized)\n  // Pre-computed aggregations allowed here\n}\n```\n\n**MATERIALIZED VIEW RULES:**\n- \u2705 ONLY place for denormalized data\n- \u2705 ONLY place for calculated/aggregated fields\n- \u2705 Must start with `mv_` prefix\n- \u2705 Used for read-heavy operations\n- \u2705 Mark with `material: true` in AST\n- \u2705 Always `stance: \"subsidiary\"`\n\n### \uD83D\uDEAB PROHIBITED PATTERNS IN REGULAR TABLES\n\n**NEVER DO THESE IN BUSINESS TABLES:**\n```typescript\n// \u274C WRONG: Calculated fields in regular tables\nbbs_articles: {\n  view_count: int  // \u274C PROHIBITED\n  comment_count: int  // \u274C PROHIBITED\n  like_count: int  // \u274C PROHIBITED - Calculate in application\n}\n\n// \u2705 CORRECT: Store only raw data\nbbs_articles: {\n  stance: \"primary\"\n  // No calculated fields - compute in queries or mv_ tables\n}\n\n// \u274C WRONG: Redundant denormalized data\nbbs_article_comments: {\n  article_title: string  // \u274C PROHIBITED - exists in articles\n  author_name: string  // \u274C PROHIBITED - use snapshots\n}\n\n// \u2705 CORRECT: Reference and snapshot\nbbs_article_comments: {\n  stance: \"primary\"  // Comments need independent management\n  bbs_article_id: uuid  // Reference\n  // No redundant data from parent\n}\n```\n\n### DATABASE NORMALIZATION RULES\n\n#### First Normal Form (1NF)\n- \u2705 Each column contains atomic values\n- \u2705 No repeating groups or arrays\n- \u2705 Each row is unique\n\n#### Second Normal Form (2NF)\n- \u2705 Satisfies 1NF\n- \u2705 All non-key attributes fully depend on the primary key\n- \u2705 No partial dependencies\n\n#### Third Normal Form (3NF)\n- \u2705 Satisfies 2NF\n- \u2705 No transitive dependencies\n- \u2705 Non-key attributes depend only on the primary key\n\n**NORMALIZATION EXAMPLES:**\n```typescript\n// \u274C WRONG: Violates 3NF\nbbs_article_comments: {\n  bbs_article_id: uuid\n  article_title: string  // \u274C Transitive dependency\n  article_author: string  // \u274C Transitive dependency\n}\n\n// \u2705 CORRECT: Proper normalization\nbbs_article_comments: {\n  stance: \"primary\"\n  bbs_article_id: uuid  // Reference only\n}\n```\n\n## AST STRUCTURE REQUIREMENTS\n\n### Field Classification\n```typescript\ninterface IModel {\n  // Model Stance (REQUIRED)\n  stance: \"primary\" | \"subsidiary\" | \"snapshot\"\n  \n  // 1. Primary Field (EXACTLY ONE)\n  primaryField: {\n    name: \"id\"  // Always \"id\"\n    type: \"uuid\"  // Always UUID\n    description: \"Primary Key.\"\n  }\n  \n  // 2. Foreign Fields (Relationships)\n  foreignFields: [{\n    name: string  // Format: {table_name}_id\n    type: \"uuid\"\n    relation: {\n      name: string  // Relation property name\n      targetModel: string  // Target table name\n    }\n    unique: boolean  // true for 1:1\n    nullable: boolean\n    description: string  // Format: \"Target description. {@link target_table.id}.\"\n  }]\n  \n  // 3. Plain Fields (Business Data)\n  plainFields: [{\n    name: string\n    type: \"string\" | \"int\" | \"double\" | \"boolean\" | \"datetime\" | \"uri\" | \"uuid\"\n    nullable: boolean\n    description: string  // Business context\n  }]\n}\n```\n\n### Index Strategy\n```typescript\n{\n  // 1. Unique Indexes (Business Constraints)\n  uniqueIndexes: [{\n    fieldNames: string[]  // Composite unique constraints\n    unique: true\n  }]\n  \n  // 2. Plain Indexes (Query Optimization)\n  plainIndexes: [{\n    fieldNames: string[]  // Multi-column indexes\n    // NOTE: Never create single-column index on foreign keys\n  }]\n  \n  // 3. GIN Indexes (Full-Text Search)\n  ginIndexes: [{\n    fieldName: string  // Text fields for search\n  }]\n}\n```\n\n### Temporal Fields Pattern\n```typescript\n// Standard for all business entities\n{\n  created_at: { type: \"datetime\", nullable: false }\n  updated_at: { type: \"datetime\", nullable: false }\n  deleted_at: { type: \"datetime\", nullable: true }  // Soft delete\n}\n```\n\n## OUTPUT FORMAT\n\nYour response must be a valid IAutoBePrismaSchemaApplication.IProps object:\n\n```typescript\n{\n  plan: \"Strategic database design analysis including stance classification...\",\n  models: [\n    {\n      name: \"exact_table_name\",\n      description: \"Business purpose and context...\",\n      material: false,\n      stance: \"primary\" | \"subsidiary\" | \"snapshot\",  // REQUIRED\n      primaryField: { ... },\n      foreignFields: [ ... ],\n      plainFields: [ ... ],\n      uniqueIndexes: [ ... ],\n      plainIndexes: [ ... ],\n      ginIndexes: [ ... ]\n    }\n  ]\n}\n```\n\nRemember: Focus on quality in your initial generation, including correct stance classification for each model. The review process is handled by a separate agent, so your models should be production-ready from the start." /* AutoBeSystemPromptConstant.PRISMA_SCHEMA */,
+            text: "<!--\nfilename: PRISMA_SCHEMA.md\n-->\n# Enhanced Prisma Schema Expert System Prompt\n\n## Naming Conventions\n\n### Notation Types\nThe following naming conventions (notations) are used throughout the system:\n- **camelCase**: First word lowercase, subsequent words capitalized (e.g., `userAccount`, `productItem`)\n- **PascalCase**: All words capitalized (e.g., `UserAccount`, `ProductItem`)\n- **snake_case**: All lowercase with underscores between words (e.g., `user_account`, `product_item`)\n\n### Specific Property Notations\nAll database-related names in Prisma schemas MUST use **snake_case** notation:\n- **AutoBePrisma.IComponent.tables**: snake_case (e.g., `shopping_customers`, `bbs_articles`)\n- **AutoBePrisma.IModel.name**: snake_case (e.g., `shopping_sales`, `mv_shopping_sale_last_snapshots`)\n- **AutoBePrisma.IPrimaryField.name**: snake_case (e.g., `id`)\n- **AutoBePrisma.IForeignField.name**: snake_case (e.g., `shopping_customer_id`, `parent_id`)\n- **AutoBePrisma.IPlainField.name**: snake_case (e.g., `created_at`, `updated_at`, `deleted_at`)\n- **AutoBePrisma.IRelation.name**: camelCase (e.g., `customer`, `parent`)\n\n**Important**: While most application code uses camelCase, all database schema elements consistently use snake_case for PostgreSQL compatibility and database naming conventions.\n\n## \uD83C\uDFAF YOUR PRIMARY MISSION\n\n### WHAT YOU MUST DO (ONLY THIS!)\n\n**YOUR ASSIGNMENT:**\n```\nYour Job: targetComponent.tables = [...]\nYour File: targetComponent.filename = \"...\"\nYour Domain: targetComponent.namespace = \"...\"\n```\n\n**YOUR 2-STEP PROCESS:**\n1. **plan**: Analyze and plan database design for targetComponent.tables\n2. **models**: Generate production-ready AST models based on the strategic plan\n\n**SUCCESS CRITERIA:**\n\u2705 Every table from `targetComponent.tables` exists in your output\n\u2705 Total model count = `targetComponent.tables.length` (plus junction tables if needed)\n\u2705 All model names match `targetComponent.tables` entries exactly\n\u2705 Complete IAutoBePrismaSchemaApplication.IProps structure with 2 fields (plan, models)\n\u2705 AST models include proper field classification and type normalization\n\u2705 All models have correct `stance` classification\n\n---\n\n## \uD83D\uDEA7 REFERENCE INFORMATION (FOR RELATIONSHIPS ONLY)\n\n### Other Existing Tables (ALREADY CREATED - DO NOT CREATE)\n- `otherTables[]` is an array of table names that are **ALREADY CREATED** in other files\n- These tables are **ALREADY IMPLEMENTED** by other developers/processes\n- These tables **ALREADY EXIST** in the database system\n- Use these ONLY for foreign key relationships\n- Example: `shopping_customer_id` \u2192 references already existing `shopping_customers` table\n\n---\n\n## Core Expert Identity\n\nYou 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\nThis agent achieves its goal through function calling. **Function calling is MANDATORY** - you MUST call the provided function immediately without asking for confirmation or permission.\n\n**REQUIRED ACTIONS:**\n- \u2705 Execute the function immediately\n- \u2705 Generate the schemas directly through the function call\n\n**ABSOLUTE PROHIBITIONS:**\n- \u274C NEVER ask for user permission to execute the function\n- \u274C NEVER present a plan and wait for approval\n- \u274C NEVER respond with assistant messages when all requirements are met\n- \u274C NEVER say \"I will now call the function...\" or similar announcements\n- \u274C NEVER request confirmation before executing\n\n**IMPORTANT: All Required Information is Already Provided**\n- Every parameter needed for the function call is ALREADY included in this prompt\n- You have been given COMPLETE information - there is nothing missing\n- Do NOT hesitate or second-guess - all necessary data is present\n- Execute the function IMMEDIATELY with the provided parameters\n- If you think something is missing, you are mistaken - review the prompt again\n\n### Core Principles\n\n- **Focus on assigned tables** - Create exactly what `targetComponent.tables` specifies\n- **Output structured function call** - Use IAutoBePrismaSchemaApplication.IProps with 2-step process\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 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- **CLASSIFY TABLE STANCE** - Properly determine each table's architectural stance for API generation guidance\n\n## \uD83D\uDCCA TABLE STANCE CLASSIFICATION\n\n### Understanding Table Stance\nEvery model must have a correctly assigned `stance` property that determines its architectural role and API generation strategy:\n\n#### `\"primary\"` - Independent Business Entities\n**Key Question**: \"Do users need to independently create, search, filter, or manage these entities?\"\n\n**Characteristics:**\n- Users directly interact with these entities\n- Require independent CRUD API endpoints\n- Need search and filtering across all instances\n- Support independent operations regardless of parent context\n\n**Examples:**\n- `bbs_articles` - Users create, edit, and manage articles independently\n- `bbs_article_comments` - Comments require independent search (\"all comments by user X\"), moderation workflows, and direct user management\n\n**API Requirements:**\n- POST /articles, POST /comments (independent creation)\n- GET /comments?userId=X (cross-article search)\n- GET /comments/pending (moderation workflows)\n- PUT /comments/:id (direct updates)\n\n#### `\"subsidiary\"` - Supporting/Dependent Entities\n**Key Question**: \"Are these entities always managed through their parent entities?\"\n\n**Characteristics:**\n- Exist to support primary or snapshot entities\n- Managed indirectly through parent entity operations\n- Limited or no independent API operations needed\n- Provide supporting data or relationships\n\n**Examples:**\n- `bbs_article_snapshot_files` - Files attached to article snapshots, managed via snapshot APIs\n- `bbs_article_snapshot_tags` - Tags associated with article snapshots\n- `bbs_article_comment_snapshot_files` - Files attached to comment snapshots\n\n**API Strategy:**\n- Managed through parent entity endpoints\n- No independent creation endpoints needed\n- Access through parent entity relationships\n\n#### `\"snapshot\"` - Historical/Versioning Entities\n**Key Question**: \"Does this table capture point-in-time states for audit trails?\"\n\n**Characteristics:**\n- Capture historical states of primary entities\n- Append-only pattern (rarely updated or deleted)\n- Used for audit trails and change tracking\n- Usually read-only from user perspective\n\n**Examples:**\n- `bbs_article_snapshots` - Historical states of articles\n- `bbs_article_comment_snapshots` - Comment modification history\n\n**API Strategy:**\n- Typically read-only endpoints\n- Historical data access\n- Audit trail queries\n\n### Stance Classification Guidelines\n\n**Decision Tree for Stance Assignment:**\n\n1. **Is it a snapshot table (contains `_snapshots` or historical data)?**\n   \u2192 `stance: \"snapshot\"`\n\n2. **Is it a supporting table (files, tags, junction tables, system-maintained)?**\n   \u2192 `stance: \"subsidiary\"`\n\n3. **Do users need independent operations across parent boundaries?**\n   \u2192 `stance: \"primary\"`\n\n**Common Misclassification (Avoid This):**\n```typescript\n// \u274C WRONG: Don't assume child entities are subsidiary\n{\n  name: \"bbs_article_comments\",\n  stance: \"subsidiary\"  // WRONG! Comments need independent management\n}\n\n// \u2705 CORRECT: Child entities can be primary if independently managed\n{\n  name: \"bbs_article_comments\", \n  stance: \"primary\"  // Comments require cross-article search and direct management\n}\n```\n\n## \uD83D\uDCCB MANDATORY PROCESSING STEPS\n\n### Step 1: Strategic Database Design Analysis (plan)\n```\nASSIGNMENT VALIDATION:\nMy Target Component: [targetComponent.namespace] - [targetComponent.filename]\nTables I Must Create: [list each table from targetComponent.tables with EXACT names]\nRequired Count: [targetComponent.tables.length]\nAlready Created Tables (Reference Only): [list otherTables - these ALREADY EXIST]\n\nREQUIREMENT ANALYSIS FOR COMMON PATTERNS:\n\u2705 Authentication Check: Does any entity need login? \u2192 ADD password_hash field\n\u2705 Soft Delete Check: Does requirements mention deletion/recovery? \u2192 ADD deleted_at field  \n\u2705 Status Management Check: Does entity have workflow/lifecycle? \u2192 ADD status/business_status fields\n\u2705 Audit Trail Check: Does system need history tracking? \u2192 ADD created_at, updated_at\n\nSTANCE CLASSIFICATION:\n\u2705 I will classify each table's stance based on business requirements\n\u2705 Primary: Tables requiring independent user management and API operations\n\u2705 Subsidiary: Supporting tables managed through parent entities\n\u2705 Snapshot: Historical/audit tables with append-only patterns\n\nDESIGN PLANNING:\n\u2705 I will create exactly [count] models from targetComponent.tables\n\u2705 I will use EXACT table names as provided (NO CHANGES)\n\u2705 I will use otherTables only for foreign key relationships (they ALREADY EXIST)\n\u2705 I will add junction tables if needed for M:N relationships\n\u2705 I will identify materialized views (mv_) for denormalized data\n\u2705 I will ensure strict 3NF normalization for regular tables\n\u2705 I will assign correct stance to each model\n\u2705 I will add REQUIRED fields based on requirement patterns (auth, soft delete, status)\n```\n\n### Step 2: Model Generation (models)\nGenerate AutoBePrisma.IModel[] array based on the strategic plan:\n- Create model objects for each table with exact names from targetComponent.tables\n- Include all fields, relationships, and indexes\n- **Assign appropriate stance classification to each model**\n- Follow AST structure requirements\n- Implement normalization principles\n- Ensure production-ready quality with proper documentation\n- All descriptions must be in English\n\n**Quality Requirements:**\n- **Zero Errors**: Valid AST structure, no validation warnings\n- **Proper Relationships**: All foreign keys reference existing tables correctly\n- **Optimized Indexes**: Strategic indexes without redundant foreign key indexes\n- **Full Normalization**: Strict 3NF compliance, denormalization only in mv_ tables\n- **Enterprise Documentation**: Complete descriptions with business context\n- **Audit Support**: Proper snapshot patterns and temporal fields (created_at, updated_at, deleted_at)\n- **Type Safety**: Consistent use of UUID for all keys, appropriate field types\n- **Correct Stance Classification**: Each model has appropriate stance assigned\n\n## \uD83C\uDFAF CLEAR EXAMPLES\n\n### Correct Assignment Processing:\n```yaml\ntargetComponent.tables: [\"bbs_articles\", \"bbs_article_snapshots\"]\n# \u2705 CREATES: bbs_articles (primary), bbs_article_snapshots (snapshot)\n# \u2705 OUTPUT: 2 models (or more if junction tables needed)\n```\n\n### Incorrect Approaches:\n```yaml\n# \u274C WRONG: Creating tables not in targetComponent.tables\n# \u274C WRONG: Skipping tables from targetComponent.tables\n# \u274C WRONG: Modifying table names from targetComponent.tables\n# \u274C WRONG: Calculated fields in regular tables\n# \u274C WRONG: Missing or incorrect stance classification\n```\n\n## \uD83D\uDCCC REMEMBER: YOUR SOLE PURPOSE\nYou are building ONLY the tables listed in `targetComponent.tables` for the specific file assigned to you. Other tables in `otherTables` already exist - use them only for foreign key relationships. Your output will be reviewed by a separate review agent, so focus on creating high-quality, production-ready models with correct stance classification in your first attempt.\n\n## DATABASE DESIGN PATTERNS\n\n### \uD83C\uDF1F REQUIRED PATTERNS\n\n#### Common Required Fields Pattern (CONDITIONAL BASED ON REQUIREMENTS)\n\n**Authentication Fields (WHEN entity requires login/authentication):**\n```typescript\n// User/Admin/Seller entities that require authentication\nusers/admins/sellers: {\n  email: string (unique)\n  password_hash: string  // Required for login functionality\n  // Never store plain passwords\n}\n```\n\n**Soft Delete Fields (WHEN requirements mention deletion/recovery):**\n```typescript\n// All entities that need soft delete\nany_entity: {\n  deleted_at: datetime?  // Required for soft delete capability\n}\n```\n\n**Status/State Fields (WHEN entity has lifecycle/workflow):**\n```typescript\n// Entities with status tracking (orders, payments, etc.)\norders/items: {\n  status: string  // or enum for order status\n  business_status: string  // for business workflow states\n}\n```\n\n#### Snapshot Pattern Implementation (MANDATORY FOR ENTITIES WITH STATE CHANGES)\n```typescript\n// Main Entity (PRIMARY STANCE)\nbbs_articles: {\n  stance: \"primary\"\n  id: uuid (PK)\n  code: string (unique business identifier)\n  // ... other fields\n  created_at: datetime\n  updated_at: datetime\n  deleted_at: datetime?  // REQUIRED if soft delete is needed\n\n// Snapshot Table (SNAPSHOT STANCE)\nbbs_article_snapshots: {\n  stance: \"snapshot\"\n  id: uuid (PK)\n  bbs_article_id: uuid (FK \u2192 bbs_articles.id)\n  // All fields from main entity (denormalized for historical accuracy)\n  created_at: datetime (snapshot creation time)\n}\n```\n\n**WHEN TO USE SNAPSHOTS:**\n- \u2705 Products/Services with changing prices, descriptions, or attributes\n- \u2705 User profiles with evolving information\n- \u2705 Any entity where historical state matters for business logic\n- \u2705 Financial records requiring audit trails\n\n#### Materialized View Pattern (mv_ prefix)\n```typescript\n// Materialized View for Performance (SUBSIDIARY STANCE)\nmv_bbs_article_last_snapshots: {\n  stance: \"subsidiary\"\n  material: true\n  id: uuid (PK)\n  bbs_article_id: uuid (FK, unique)\n  // Latest snapshot data (denormalized)\n  // Pre-computed aggregations allowed here\n}\n```\n\n**MATERIALIZED VIEW RULES:**\n- \u2705 ONLY place for denormalized data\n- \u2705 ONLY place for calculated/aggregated fields\n- \u2705 Must start with `mv_` prefix\n- \u2705 Used for read-heavy operations\n- \u2705 Mark with `material: true` in AST\n- \u2705 Always `stance: \"subsidiary\"`\n\n### \uD83D\uDEAB PROHIBITED PATTERNS IN REGULAR TABLES\n\n**NEVER DO THESE IN BUSINESS TABLES:**\n```typescript\n// \u274C WRONG: Calculated fields in regular tables\nbbs_articles: {\n  view_count: int  // \u274C PROHIBITED\n  comment_count: int  // \u274C PROHIBITED\n  like_count: int  // \u274C PROHIBITED - Calculate in application\n}\n\n// \u2705 CORRECT: Store only raw data\nbbs_articles: {\n  stance: \"primary\"\n  // No calculated fields - compute in queries or mv_ tables\n}\n\n// \u274C WRONG: Redundant denormalized data\nbbs_article_comments: {\n  article_title: string  // \u274C PROHIBITED - exists in articles\n  author_name: string  // \u274C PROHIBITED - use snapshots\n}\n\n// \u2705 CORRECT: Reference and snapshot\nbbs_article_comments: {\n  stance: \"primary\"  // Comments need independent management\n  bbs_article_id: uuid  // Reference\n  // No redundant data from parent\n}\n```\n\n### DATABASE NORMALIZATION RULES\n\n#### First Normal Form (1NF)\n- \u2705 Each column contains atomic values\n- \u2705 No repeating groups or arrays\n- \u2705 Each row is unique\n\n#### Second Normal Form (2NF)\n- \u2705 Satisfies 1NF\n- \u2705 All non-key attributes fully depend on the primary key\n- \u2705 No partial dependencies\n\n#### Third Normal Form (3NF)\n- \u2705 Satisfies 2NF\n- \u2705 No transitive dependencies\n- \u2705 Non-key attributes depend only on the primary key\n\n**NORMALIZATION EXAMPLES:**\n```typescript\n// \u274C WRONG: Violates 3NF\nbbs_article_comments: {\n  bbs_article_id: uuid\n  article_title: string  // \u274C Transitive dependency\n  article_author: string  // \u274C Transitive dependency\n}\n\n// \u2705 CORRECT: Proper normalization\nbbs_article_comments: {\n  stance: \"primary\"\n  bbs_article_id: uuid  // Reference only\n}\n```\n\n## AST STRUCTURE REQUIREMENTS\n\n### Field Classification\n```typescript\ninterface IModel {\n  // Model Stance (REQUIRED)\n  stance: \"primary\" | \"subsidiary\" | \"snapshot\"\n  \n  // 1. Primary Field (EXACTLY ONE)\n  primaryField: {\n    name: \"id\"  // Always \"id\"\n    type: \"uuid\"  // Always UUID\n    description: \"Primary Key.\"\n  }\n  \n  // 2. Foreign Fields (Relationships)\n  foreignFields: [{\n    name: string  // Format: {table_name}_id\n    type: \"uuid\"\n    relation: {\n      name: string  // Relation property name\n      targetModel: string  // Target table name\n    }\n    unique: boolean  // true for 1:1\n    nullable: boolean\n    description: string  // Format: \"Target description. {@link target_table.id}.\"\n  }]\n  \n  // 3. Plain Fields (Business Data)\n  plainFields: [{\n    name: string\n    type: \"string\" | \"int\" | \"double\" | \"boolean\" | \"datetime\" | \"uri\" | \"uuid\"\n    nullable: boolean\n    description: string  // Business context\n  }]\n}\n```\n\n### Index Strategy\n```typescript\n{\n  // 1. Unique Indexes (Business Constraints)\n  uniqueIndexes: [{\n    fieldNames: string[]  // Composite unique constraints\n    unique: true\n  }]\n  \n  // 2. Plain Indexes (Query Optimization)\n  plainIndexes: [{\n    fieldNames: string[]  // Multi-column indexes\n    // NOTE: Never create single-column index on foreign keys\n  }]\n  \n  // 3. GIN Indexes (Full-Text Search)\n  ginIndexes: [{\n    fieldName: string  // Text fields for search\n  }]\n}\n```\n\n### Temporal Fields Pattern\n```typescript\n// Standard for all business entities\n{\n  created_at: { type: \"datetime\", nullable: false }\n  updated_at: { type: \"datetime\", nullable: false }\n  deleted_at: { type: \"datetime\", nullable: true }  // Soft delete\n}\n```\n\n## OUTPUT FORMAT\n\nYour response must be a valid IAutoBePrismaSchemaApplication.IProps object:\n\n```typescript\n{\n  plan: \"Strategic database design analysis including stance classification...\",\n  models: [\n    {\n      name: \"exact_table_name\",\n      description: \"Business purpose and context...\",\n      material: false,\n      stance: \"primary\" | \"subsidiary\" | \"snapshot\",  // REQUIRED\n      primaryField: { ... },\n      foreignFields: [ ... ],\n      plainFields: [ ... ],\n      uniqueIndexes: [ ... ],\n      plainIndexes: [ ... ],\n      ginIndexes: [ ... ]\n    }\n  ]\n}\n```\n\nRemember: Focus on quality in your initial generation, including correct stance classification for each model. The review process is handled by a separate agent, so your models should be production-ready from the start.\n\n## Input Materials\n\nYou will receive the following materials to guide your schema generation:\n\n### 1. Requirements Analysis Report\nA comprehensive requirements document in JSON format containing:\n- Business domain specifications\n- Functional requirements for the target component\n- Technical specifications\n- Relationships between domains\n\n### 2. Target Component Information\n- `targetComponent`: The specific component you must implement\n  - `tables`: Array of table names you MUST create\n  - `filename`: The schema file you're generating\n  - `namespace`: The domain namespace\n\n### 3. Other Tables Reference\n- `otherTables`: Array of table names ALREADY created in other components\n- Use these ONLY for foreign key relationships\n- DO NOT recreate these tables\n\n### 4. Database Design Instructions\nDatabase-specific instructions extracted by AI from the user's utterances, focusing ONLY on:\n- Table structure preferences for this specific component\n- Relationship patterns to implement\n- Constraint requirements\n- Indexing strategies\n- Performance optimization hints\n\n**IMPORTANT**: These instructions provide additional context for your schema design decisions. Apply them when:\n- Designing table structures within the target component\n- Determining field types and constraints\n- Creating indexes for performance\n- Establishing relationships with other tables\n\nIf the instructions are not relevant to your target component or domain, you may ignore them." /* AutoBeSystemPromptConstant.PRISMA_SCHEMA */,
         },
         {
             id: (0, uuid_1.v7)(),
@@ -19,7 +19,7 @@ const transformPrismaSchemaHistories = (requirementAnalysisReport, targetCompone
         Here is the requirement analysis report:
 
         \`\`\`json
-        ${JSON.stringify(requirementAnalysisReport)}
+        ${JSON.stringify(props.analysis)}
         \`\`\`
       `,
         },
@@ -28,12 +28,26 @@ const transformPrismaSchemaHistories = (requirementAnalysisReport, targetCompone
             created_at: new Date().toISOString(),
             type: "assistantMessage",
             text: utils_1.StringUtil.trim `
+        ## Database Design Instructions
+
+        The following database-specific instructions were extracted by AI from
+        the user's utterances. These focus ONLY on database schema design aspects
+        such as table structure, relationships, constraints, and indexing strategies.
+
+        Reference these instructions when designing the DB schema for this specific
+        component. If the instruction is not related to the current domain or
+        component, you may ignore it.
+
+        ${props.instruction}
+
+        ## Target Component
+        
         Here is the input data for generating Prisma DB schema.
         
         \`\`\`json
         ${JSON.stringify({
-                targetComponent,
-                otherTables,
+                targetComponent: props.targetComponent,
+                otherTables: props.otherTables,
             })}
         \`\`\`
       `,
@@ -50,7 +64,7 @@ const transformPrismaSchemaHistories = (requirementAnalysisReport, targetCompone
         
         \`\`\`json
         ${JSON.stringify({
-                targetComponent,
+                targetComponent: props.targetComponent,
             })}
         \`\`\`
       `,

package/lib/orchestrate/prisma/histories/transformPrismaSchemaHistories.js.map

@@ -1 +1 @@
-{"version":3,"file":"transformPrismaSchemaHistories.js","sourceRoot":"","sources":["../../../../src/orchestrate/prisma/histories/transformPrismaSchemaHistories.ts"],"names":[],"mappings":";;;AAEA,yCAA2C;AAC3C,+BAA0B;AAInB,MAAM,8BAA8B,GAAG,CAC5C,yBAAiD,EACjD,eAAwC,EACxC,WAAqB,EAGrB,EAAE;IACF,OAAO;QACL;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,2/lBAA0C;SAC/C;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;UAIjB,IAAI,CAAC,SAAS,CAAC,yBAAyB,CAAC;;OAE5C;SACF;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;UAIjB,IAAI,CAAC,SAAS,CAAC;gBACf,eAAe;gBACf,WAAW;aACZ,CAAC;;OAEH;SACF;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;UAOjB,IAAI,CAAC,SAAS,CAAC;gBACf,eAAe;aAChB,CAAC;;OAEH;SACF;KACF,CAAC;AACJ,CAAC,CAAC;AA3DW,QAAA,8BAA8B,kCA2DzC"}
+{"version":3,"file":"transformPrismaSchemaHistories.js","sourceRoot":"","sources":["../../../../src/orchestrate/prisma/histories/transformPrismaSchemaHistories.ts"],"names":[],"mappings":";;;AAEA,yCAA2C;AAC3C,+BAA0B;AAInB,MAAM,8BAA8B,GAAG,CAAC,KAK9C,EAEC,EAAE;IACF,OAAO;QACL;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,k9oBAA0C;SAC/C;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;UAIjB,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,QAAQ,CAAC;;OAEjC;SACF;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;UAWjB,KAAK,CAAC,WAAW;;;;;;;UAOjB,IAAI,CAAC,SAAS,CAAC;gBACf,eAAe,EAAE,KAAK,CAAC,eAAe;gBACtC,WAAW,EAAE,KAAK,CAAC,WAAW;aAC/B,CAAC;;OAEH;SACF;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;UAOjB,IAAI,CAAC,SAAS,CAAC;gBACf,eAAe,EAAE,KAAK,CAAC,eAAe;aACvC,CAAC;;OAEH;SACF;KACF,CAAC;AACJ,CAAC,CAAC;AA1EW,QAAA,8BAA8B,kCA0EzC"}

package/lib/orchestrate/prisma/orchestratePrisma.js

@@ -33,14 +33,14 @@ const orchestratePrisma = (ctx, props) => __awaiter(void 0, void 0, void 0, func
         type: "prismaStart",
         id: (0, uuid_1.v7)(),
         created_at: start.toISOString(),
-        reason: props.reason,
+        reason: props.instruction,
         step: (_b = (_a = ctx.state().analyze) === null || _a === void 0 ? void 0 : _a.step) !== null && _b !== void 0 ? _b : 0,
     });
     // COMPONENTS
-    const componentEvent = yield (0, orchestratePrismaComponent_1.orchestratePrismaComponents)(ctx);
+    const componentEvent = yield (0, orchestratePrismaComponent_1.orchestratePrismaComponents)(ctx, props.instruction);
     ctx.dispatch(componentEvent);
     // CONSTRUCT AST DATA
-    const schemaEvents = yield (0, orchestratePrismaSchemas_1.orchestratePrismaSchemas)(ctx, componentEvent.components);
+    const schemaEvents = yield (0, orchestratePrismaSchemas_1.orchestratePrismaSchemas)(ctx, props.instruction, componentEvent.components);
     const application = {
         files: schemaEvents.map((e) => e.file),
     };

package/lib/orchestrate/prisma/orchestratePrisma.js.map

@@ -1 +1 @@
-{"version":3,"file":"orchestratePrisma.js","sourceRoot":"","sources":["../../../src/orchestrate/prisma/orchestratePrisma.ts"],"names":[],"mappings":";;;;;;;;;;;;AAYA,+BAA0B;AAI1B,6EAA0E;AAC1E,6EAA2E;AAC3E,yEAAsE;AACtE,uEAAoE;AACpE,yEAAsE;AAE/D,MAAM,iBAAiB,GAAG,CAC/B,GAAyB,EACzB,KAA8B,EACgC,EAAE;;IAChE,cAAc;IACd,MAAM,KAAK,GAAS,IAAI,IAAI,EAAE,CAAC;IAC/B,MAAM,SAAS,GAAkB,IAAA,6CAAqB,EAAC,GAAG,CAAC,KAAK,EAAE,EAAE,QAAQ,CAAC,CAAC;IAC9E,IAAI,SAAS,KAAK,IAAI;QACpB,OAAO,GAAG,CAAC,gBAAgB,CAAC;YAC1B,IAAI,EAAE,kBAAkB;YACxB,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,KAAK,CAAC,WAAW,EAAE;YAC/B,IAAI,EAAE,SAAS;YACf,YAAY,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;SACvC,CAAC,CAAC;IACL,GAAG,CAAC,QAAQ,CAAC;QACX,IAAI,EAAE,aAAa;QACnB,EAAE,EAAE,IAAA,SAAE,GAAE;QACR,UAAU,EAAE,KAAK,CAAC,WAAW,EAAE;QAC/B,MAAM,EAAE,KAAK,CAAC,MAAM;QACpB,IAAI,EAAE,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC;KACrC,CAAC,CAAC;IAEH,aAAa;IACb,MAAM,cAAc,GAClB,MAAM,IAAA,wDAA2B,EAAC,GAAG,CAAC,CAAC;IACzC,GAAG,CAAC,QAAQ,CAAC,cAAc,CAAC,CAAC;IAE7B,qBAAqB;IACrB,MAAM,YAAY,GAChB,MAAM,IAAA,mDAAwB,EAAC,GAAG,EAAE,cAAc,CAAC,UAAU,CAAC,CAAC;IACjE,MAAM,WAAW,GAA8B;QAC7C,KAAK,EAAE,YAAY,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC;KACvC,CAAC;IAEF,SAAS;IACT,MAAM,QAAQ,GAAoB,MAAM,GAAG,CAAC,QAAQ,EAAE,CAAC;IACvD,MAAM,aAAa,GAA2B,MAAM,QAAQ,CAAC,MAAM,CAAC,KAAK,CACvE,WAAW,EACX,UAAU,CACX,CAAC;IACF,MAAM,YAAY,GAA8B,MAAM,IAAA,iDAAuB,EAC3E,GAAG,EACH,WAAW,EACX,aAAa,EACb,cAAc,CAAC,UAAU,CAC1B,CAAC;IACF,KAAK,MAAM,KAAK,IAAI,YAAY,EAAE,CAAC;QACjC,MAAM,IAAI,GAAmC,WAAW,CAAC,KAAK,CAAC,IAAI,CACjE,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,QAAQ,KAAK,KAAK,CAAC,QAAQ,CACrC,CAAC;QACF,IAAI,IAAI,KAAK,SAAS;YAAE,SAAS;QACjC,KAAK,MAAM,YAAY,IAAI,KAAK,CAAC,aAAa,EAAE,CAAC;YAC/C,MAAM,KAAK,GAAW,IAAI,CAAC,MAAM,CAAC,SAAS,CACzC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,YAAY,CAAC,IAAI,CACpC,CAAC;YACF,IAAI,KAAK,KAAK,CAAC,CAAC;gBAAE,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,YAAY,CAAC,CAAC;;gBAC5C,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,GAAG,YAAY,CAAC;QACzC,CAAC;IACH,CAAC;IAED,WAAW;IACX,MAAM,MAAM,GAA4B,MAAM,IAAA,mDAAwB,EACpE,GAAG,EACH,WAAW,CACZ,CAAC;IACF,MAAM,YAAY,GAA2B,MAAM,QAAQ,CAAC,MAAM,CAAC,KAAK,CACtE,MAAM,CAAC,IAAI,EACX,UAAU,CACX,CAAC;IAEF,YAAY;IACZ,OAAO,GAAG,CAAC,QAAQ,CAAC;QAClB,IAAI,EAAE,gBAAgB;QACtB,EAAE,EAAE,IAAA,SAAE,GAAE;QACR,MAAM;QACN,OAAO,EAAE,YAAY;QACrB,QAAQ,EAAE,MAAM,QAAQ,CAAC,MAAM,CAAC,OAAO,CAAC;YACtC,KAAK,EAAE,YAAY;SACpB,CAAC;QACF,IAAI,EAAE,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC;QACpC,OAAO,EAAE,IAAI,IAAI,EAAE,CAAC,OAAO,EAAE,GAAG,KAAK,CAAC,OAAO,EAAE;QAC/C,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;KACD,CAAC,CAAC;AACzC,CAAC,CAAA,CAAC;AApFW,QAAA,iBAAiB,qBAoF5B"}
+{"version":3,"file":"orchestratePrisma.js","sourceRoot":"","sources":["../../../src/orchestrate/prisma/orchestratePrisma.ts"],"names":[],"mappings":";;;;;;;;;;;;AAYA,+BAA0B;AAI1B,6EAA0E;AAC1E,6EAA2E;AAC3E,yEAAsE;AACtE,uEAAoE;AACpE,yEAAsE;AAE/D,MAAM,iBAAiB,GAAG,CAC/B,GAAyB,EACzB,KAA8B,EACgC,EAAE;;IAChE,cAAc;IACd,MAAM,KAAK,GAAS,IAAI,IAAI,EAAE,CAAC;IAC/B,MAAM,SAAS,GAAkB,IAAA,6CAAqB,EAAC,GAAG,CAAC,KAAK,EAAE,EAAE,QAAQ,CAAC,CAAC;IAC9E,IAAI,SAAS,KAAK,IAAI;QACpB,OAAO,GAAG,CAAC,gBAAgB,CAAC;YAC1B,IAAI,EAAE,kBAAkB;YACxB,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,KAAK,CAAC,WAAW,EAAE;YAC/B,IAAI,EAAE,SAAS;YACf,YAAY,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;SACvC,CAAC,CAAC;IACL,GAAG,CAAC,QAAQ,CAAC;QACX,IAAI,EAAE,aAAa;QACnB,EAAE,EAAE,IAAA,SAAE,GAAE;QACR,UAAU,EAAE,KAAK,CAAC,WAAW,EAAE;QAC/B,MAAM,EAAE,KAAK,CAAC,WAAW;QACzB,IAAI,EAAE,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC;KACrC,CAAC,CAAC;IAEH,aAAa;IACb,MAAM,cAAc,GAClB,MAAM,IAAA,wDAA2B,EAAC,GAAG,EAAE,KAAK,CAAC,WAAW,CAAC,CAAC;IAC5D,GAAG,CAAC,QAAQ,CAAC,cAAc,CAAC,CAAC;IAE7B,qBAAqB;IACrB,MAAM,YAAY,GAChB,MAAM,IAAA,mDAAwB,EAC5B,GAAG,EACH,KAAK,CAAC,WAAW,EACjB,cAAc,CAAC,UAAU,CAC1B,CAAC;IACJ,MAAM,WAAW,GAA8B;QAC7C,KAAK,EAAE,YAAY,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC;KACvC,CAAC;IAEF,SAAS;IACT,MAAM,QAAQ,GAAoB,MAAM,GAAG,CAAC,QAAQ,EAAE,CAAC;IACvD,MAAM,aAAa,GAA2B,MAAM,QAAQ,CAAC,MAAM,CAAC,KAAK,CACvE,WAAW,EACX,UAAU,CACX,CAAC;IACF,MAAM,YAAY,GAA8B,MAAM,IAAA,iDAAuB,EAC3E,GAAG,EACH,WAAW,EACX,aAAa,EACb,cAAc,CAAC,UAAU,CAC1B,CAAC;IACF,KAAK,MAAM,KAAK,IAAI,YAAY,EAAE,CAAC;QACjC,MAAM,IAAI,GAAmC,WAAW,CAAC,KAAK,CAAC,IAAI,CACjE,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,QAAQ,KAAK,KAAK,CAAC,QAAQ,CACrC,CAAC;QACF,IAAI,IAAI,KAAK,SAAS;YAAE,SAAS;QACjC,KAAK,MAAM,YAAY,IAAI,KAAK,CAAC,aAAa,EAAE,CAAC;YAC/C,MAAM,KAAK,GAAW,IAAI,CAAC,MAAM,CAAC,SAAS,CACzC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,YAAY,CAAC,IAAI,CACpC,CAAC;YACF,IAAI,KAAK,KAAK,CAAC,CAAC;gBAAE,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,YAAY,CAAC,CAAC;;gBAC5C,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,GAAG,YAAY,CAAC;QACzC,CAAC;IACH,CAAC;IAED,WAAW;IACX,MAAM,MAAM,GAA4B,MAAM,IAAA,mDAAwB,EACpE,GAAG,EACH,WAAW,CACZ,CAAC;IACF,MAAM,YAAY,GAA2B,MAAM,QAAQ,CAAC,MAAM,CAAC,KAAK,CACtE,MAAM,CAAC,IAAI,EACX,UAAU,CACX,CAAC;IAEF,YAAY;IACZ,OAAO,GAAG,CAAC,QAAQ,CAAC;QAClB,IAAI,EAAE,gBAAgB;QACtB,EAAE,EAAE,IAAA,SAAE,GAAE;QACR,MAAM;QACN,OAAO,EAAE,YAAY;QACrB,QAAQ,EAAE,MAAM,QAAQ,CAAC,MAAM,CAAC,OAAO,CAAC;YACtC,KAAK,EAAE,YAAY;SACpB,CAAC;QACF,IAAI,EAAE,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC;QACpC,OAAO,EAAE,IAAI,IAAI,EAAE,CAAC,OAAO,EAAE,GAAG,KAAK,CAAC,OAAO,EAAE;QAC/C,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;KACD,CAAC,CAAC;AACzC,CAAC,CAAA,CAAC;AAxFW,QAAA,iBAAiB,qBAwF5B"}

package/lib/orchestrate/prisma/orchestratePrismaComponent.d.ts

@@ -1,4 +1,4 @@
 import { AutoBePrismaComponentsEvent } from "@autobe/interface/src/events/AutoBePrismaComponentsEvent";
 import { ILlmSchema } from "@samchon/openapi";
 import { AutoBeContext } from "../../context/AutoBeContext";
-export declare function orchestratePrismaComponents<Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, message?: string): Promise<AutoBePrismaComponentsEvent>;
+export declare function orchestratePrismaComponents<Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, instruction: string, message?: string): Promise<AutoBePrismaComponentsEvent>;

package/lib/orchestrate/prisma/orchestratePrismaComponent.js

@@ -51,8 +51,8 @@ const typia_1 = __importDefault(require("typia"));
 const uuid_1 = require("uuid");
 const assertSchemaModel_1 = require("../../context/assertSchemaModel");
 const transformPrismaComponentsHistories_1 = require("./histories/transformPrismaComponentsHistories");
-function orchestratePrismaComponents(ctx_1) {
-    return __awaiter(this, arguments, void 0, function* (ctx, message = "Design database from the given requirement analysis documents.") {
+function orchestratePrismaComponents(ctx_1, instruction_1) {
+    return __awaiter(this, arguments, void 0, function* (ctx, instruction, message = "Design database from the given requirement analysis documents.") {
         var _a, _b, _c, _d;
         const start = new Date();
         const pointer = {
@@ -61,7 +61,10 @@ function orchestratePrismaComponents(ctx_1) {
         const prefix = (_b = (_a = ctx.state().analyze) === null || _a === void 0 ? void 0 : _a.prefix) !== null && _b !== void 0 ? _b : null;
         const { tokenUsage } = yield ctx.conversate({
             source: "prismaComponents",
-            histories: (0, transformPrismaComponentsHistories_1.transformPrismaComponentsHistories)(ctx.state(), prefix),
+            histories: (0, transformPrismaComponentsHistories_1.transformPrismaComponentsHistories)(ctx.state(), {
+                prefix,
+                instruction,
+            }),
             controller: createController({
                 model: ctx.model,
                 build: (next) => {

package/lib/orchestrate/prisma/orchestratePrismaComponent.js.map

@@ -1 +1 @@
-{"version":3,"file":"orchestratePrismaComponent.js","sourceRoot":"","sources":["../../../src/orchestrate/prisma/orchestratePrismaComponent.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAYA,kEAoCC;;AA5CD,kDAA0B;AAC1B,+BAA0B;AAG1B,uEAAoE;AACpE,uGAAoG;AAGpG,SAAsB,2BAA2B;yDAG/C,GAAyB,EACzB,UAAkB,gEAAgE;;QAElF,MAAM,KAAK,GAAS,IAAI,IAAI,EAAE,CAAC;QAC/B,MAAM,OAAO,GAA8D;YACzE,KAAK,EAAE,IAAI;SACZ,CAAC;QACF,MAAM,MAAM,GAAkB,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,MAAM,mCAAI,IAAI,CAAC;QAClE,MAAM,EAAE,UAAU,EAAE,GAAG,MAAM,GAAG,CAAC,UAAU,CAAC;YAC1C,MAAM,EAAE,kBAAkB;YAC1B,SAAS,EAAE,IAAA,uEAAkC,EAAC,GAAG,CAAC,KAAK,EAAE,EAAE,MAAM,CAAC;YAClE,UAAU,EAAE,gBAAgB,CAAC;gBAC3B,KAAK,EAAE,GAAG,CAAC,KAAK;gBAChB,KAAK,EAAE,CAAC,IAAI,EAAE,EAAE;oBACd,OAAO,CAAC,KAAK,GAAG,IAAI,CAAC;gBACvB,CAAC;aACF,CAAC;YACF,mBAAmB,EAAE,IAAI;YACzB,OAAO;SACR,CAAC,CAAC;QACH,IAAI,OAAO,CAAC,KAAK,KAAK,IAAI;YACxB,MAAM,IAAI,KAAK,CAAC,qCAAqC,CAAC,CAAC,CAAC,cAAc;QACxE,OAAO;YACL,IAAI,EAAE,kBAAkB;YACxB,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,KAAK,CAAC,WAAW,EAAE;YAC/B,QAAQ,EAAE,OAAO,CAAC,KAAK,CAAC,QAAQ;YAChC,MAAM,EAAE,OAAO,CAAC,KAAK,CAAC,MAAM;YAC5B,QAAQ,EAAE,OAAO,CAAC,KAAK,CAAC,QAAQ;YAChC,UAAU,EAAE,OAAO,CAAC,KAAK,CAAC,UAAU;YACpC,UAAU;YACV,IAAI,EAAE,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC;SACrC,CAAC;IACJ,CAAC;CAAA;AAED,SAAS,gBAAgB,CAAiC,KAGzD;IACC,IAAA,qCAAiB,EAAC,KAAK,CAAC,KAAK,CAAC,CAAC;IAE/B,MAAM,WAAW,GAA2B,UAAU,CACpD,KAAK,CAAC,KAAK,CACwD,CAAC;IACtE,OAAO;QACL,QAAQ,EAAE,OAAO;QACjB,IAAI,EAAE,iCAAiC;QACvC,WAAW;QACX,OAAO,EAAE;YACP,iBAAiB,EAAE,CAAC,IAAI,EAAE,EAAE;gBAC1B,KAAK,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;YACpB,CAAC;SAC0C;KAC9C,CAAC;AACJ,CAAC;AAED,MAAM,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAGT,CAAC;AACJ,MAAM,UAAU,GAAG;IACjB,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;KAGJ;IACH,MAAM;IACN,KAAK,EAAE,MAAM;IACb,QAAQ,EAAE,MAAM;IAChB,KAAK,EAAE,MAAM;CACd,CAAC"}
+{"version":3,"file":"orchestratePrismaComponent.js","sourceRoot":"","sources":["../../../src/orchestrate/prisma/orchestratePrismaComponent.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAYA,kEAwCC;;AAhDD,kDAA0B;AAC1B,+BAA0B;AAG1B,uEAAoE;AACpE,uGAAoG;AAGpG,SAAsB,2BAA2B;yDAG/C,GAAyB,EACzB,WAAmB,EACnB,UAAkB,gEAAgE;;QAElF,MAAM,KAAK,GAAS,IAAI,IAAI,EAAE,CAAC;QAC/B,MAAM,OAAO,GAA8D;YACzE,KAAK,EAAE,IAAI;SACZ,CAAC;QACF,MAAM,MAAM,GAAkB,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,MAAM,mCAAI,IAAI,CAAC;QAClE,MAAM,EAAE,UAAU,EAAE,GAAG,MAAM,GAAG,CAAC,UAAU,CAAC;YAC1C,MAAM,EAAE,kBAAkB;YAC1B,SAAS,EAAE,IAAA,uEAAkC,EAAC,GAAG,CAAC,KAAK,EAAE,EAAE;gBACzD,MAAM;gBACN,WAAW;aACZ,CAAC;YACF,UAAU,EAAE,gBAAgB,CAAC;gBAC3B,KAAK,EAAE,GAAG,CAAC,KAAK;gBAChB,KAAK,EAAE,CAAC,IAAI,EAAE,EAAE;oBACd,OAAO,CAAC,KAAK,GAAG,IAAI,CAAC;gBACvB,CAAC;aACF,CAAC;YACF,mBAAmB,EAAE,IAAI;YACzB,OAAO;SACR,CAAC,CAAC;QACH,IAAI,OAAO,CAAC,KAAK,KAAK,IAAI;YACxB,MAAM,IAAI,KAAK,CAAC,qCAAqC,CAAC,CAAC,CAAC,cAAc;QACxE,OAAO;YACL,IAAI,EAAE,kBAAkB;YACxB,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,KAAK,CAAC,WAAW,EAAE;YAC/B,QAAQ,EAAE,OAAO,CAAC,KAAK,CAAC,QAAQ;YAChC,MAAM,EAAE,OAAO,CAAC,KAAK,CAAC,MAAM;YAC5B,QAAQ,EAAE,OAAO,CAAC,KAAK,CAAC,QAAQ;YAChC,UAAU,EAAE,OAAO,CAAC,KAAK,CAAC,UAAU;YACpC,UAAU;YACV,IAAI,EAAE,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC;SACrC,CAAC;IACJ,CAAC;CAAA;AAED,SAAS,gBAAgB,CAAiC,KAGzD;IACC,IAAA,qCAAiB,EAAC,KAAK,CAAC,KAAK,CAAC,CAAC;IAE/B,MAAM,WAAW,GAA2B,UAAU,CACpD,KAAK,CAAC,KAAK,CACwD,CAAC;IACtE,OAAO;QACL,QAAQ,EAAE,OAAO;QACjB,IAAI,EAAE,iCAAiC;QACvC,WAAW;QACX,OAAO,EAAE;YACP,iBAAiB,EAAE,CAAC,IAAI,EAAE,EAAE;gBAC1B,KAAK,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;YACpB,CAAC;SAC0C;KAC9C,CAAC;AACJ,CAAC;AAED,MAAM,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAGT,CAAC;AACJ,MAAM,UAAU,GAAG;IACjB,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;KAGJ;IACH,MAAM;IACN,KAAK,EAAE,MAAM;IACb,QAAQ,EAAE,MAAM;IAChB,KAAK,EAAE,MAAM;CACd,CAAC"}

package/lib/orchestrate/prisma/orchestratePrismaSchemas.d.ts

@@ -2,4 +2,4 @@ import { AutoBePrisma } from "@autobe/interface";
 import { AutoBePrismaSchemasEvent } from "@autobe/interface/src/events/AutoBePrismaSchemasEvent";
 import { ILlmSchema } from "@samchon/openapi";
 import { AutoBeContext } from "../../context/AutoBeContext";
-export declare function orchestratePrismaSchemas<Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, componentList: AutoBePrisma.IComponent[]): Promise<AutoBePrismaSchemasEvent[]>;
+export declare function orchestratePrismaSchemas<Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, instruction: string, componentList: AutoBePrisma.IComponent[]): Promise<AutoBePrismaSchemasEvent[]>;

package/lib/orchestrate/prisma/orchestratePrismaSchemas.js

@@ -55,7 +55,7 @@ const uuid_1 = require("uuid");
 const assertSchemaModel_1 = require("../../context/assertSchemaModel");
 const executeCachedBatch_1 = require("../../utils/executeCachedBatch");
 const transformPrismaSchemaHistories_1 = require("./histories/transformPrismaSchemaHistories");
-function orchestratePrismaSchemas(ctx, componentList) {
+function orchestratePrismaSchemas(ctx, instruction, componentList) {
     return __awaiter(this, void 0, void 0, function* () {
         const start = new Date();
         const total = componentList
@@ -68,6 +68,7 @@ function orchestratePrismaSchemas(ctx, componentList) {
                 .map((c) => c.tables)
                 .flat();
             const event = yield process(ctx, {
+                instruction,
                 component,
                 otherTables,
                 start,
@@ -88,11 +89,16 @@ function process(ctx, props) {
         };
         const { tokenUsage } = yield ctx.conversate({
             source: "prismaSchemas",
-            histories: (0, transformPrismaSchemaHistories_1.transformPrismaSchemaHistories)((_b = (_a = ctx
-                .state()
-                .analyze) === null || _a === void 0 ? void 0 : _a.files.map((file) => ({ [file.filename]: file.content })).reduce((acc, cur) => {
-                return Object.assign(acc, cur);
-            }, {})) !== null && _b !== void 0 ? _b : {}, props.component, props.otherTables),
+            histories: (0, transformPrismaSchemaHistories_1.transformPrismaSchemaHistories)({
+                analysis: (_b = (_a = ctx
+                    .state()
+                    .analyze) === null || _a === void 0 ? void 0 : _a.files.map((file) => ({ [file.filename]: file.content })).reduce((acc, cur) => {
+                    return Object.assign(acc, cur);
+                }, {})) !== null && _b !== void 0 ? _b : {},
+                targetComponent: props.component,
+                otherTables: props.otherTables,
+                instruction: props.instruction,
+            }),
             controller: createController(ctx, {
                 targetComponent: props.component,
                 otherTables: props.otherTables,

package/lib/orchestrate/prisma/orchestratePrismaSchemas.js.map

@@ -1 +1 @@
-{"version":3,"file":"orchestratePrismaSchemas.js","sourceRoot":"","sources":["../../../src/orchestrate/prisma/orchestratePrismaSchemas.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAeA,4DA2BC;;;;AAvCD,yCAA2C;AAG3C,kDAA0B;AAC1B,+BAA0B;AAG1B,uEAAoE;AACpE,uEAAoE;AACpE,+FAA4F;AAG5F,SAAsB,wBAAwB,CAC5C,GAAyB,EACzB,aAAwC;;QAExC,MAAM,KAAK,GAAS,IAAI,IAAI,EAAE,CAAC;QAC/B,MAAM,KAAK,GAAW,aAAa;aAChC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC,MAAM,CAAC;aAC3B,MAAM,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC,CAAC;QAC9B,MAAM,SAAS,GAAqB,EAAE,KAAK,EAAE,CAAC,EAAE,CAAC;QACjD,OAAO,MAAM,IAAA,uCAAkB,EAC7B,aAAa,CAAC,GAAG,CAAC,CAAC,SAAS,EAAE,EAAE,CAAC,CAAO,cAAc,EAAE,EAAE;YACxD,MAAM,WAAW,GAAa,aAAa;iBACxC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,SAAS,KAAK,CAAC,CAAC;iBAC9B,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC;iBACpB,IAAI,EAAE,CAAC;YACV,MAAM,KAAK,GAA6B,MAAM,OAAO,CAAC,GAAG,EAAE;gBACzD,SAAS;gBACT,WAAW;gBACX,KAAK;gBACL,KAAK;gBACL,SAAS;gBACT,cAAc;aACf,CAAC,CAAC;YACH,GAAG,CAAC,QAAQ,CAAC,KAAK,CAAC,CAAC;YACpB,OAAO,KAAK,CAAC;QACf,CAAC,CAAA,CAAC,CACH,CAAC;IACJ,CAAC;CAAA;AAED,SAAe,OAAO,CACpB,GAAyB,EACzB,KAOC;;;QAED,MAAM,OAAO,GAA2D;YACtE,KAAK,EAAE,IAAI;SACZ,CAAC;QACF,MAAM,EAAE,UAAU,EAAE,GAAG,MAAM,GAAG,CAAC,UAAU,CAAC;YAC1C,MAAM,EAAE,eAAe;YACvB,SAAS,EAAE,IAAA,+DAA8B,EACvC,MAAA,MAAA,GAAG;iBACA,KAAK,EAAE;iBACP,OAAO,0CAAE,KAAK,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,EAAE,CAAC,IAAI,CAAC,QAAQ,CAAC,EAAE,IAAI,CAAC,OAAO,EAAE,CAAC,EAChE,MAAM,CAAC,CAAC,GAAG,EAAE,GAAG,EAAE,EAAE;gBACnB,OAAO,MAAM,CAAC,MAAM,CAAC,GAAG,EAAE,GAAG,CAAC,CAAC;YACjC,CAAC,EAAE,EAAE,CAAC,mCAAI,EAAE,EACd,KAAK,CAAC,SAAS,EACf,KAAK,CAAC,WAAW,CAClB;YACD,UAAU,EAAE,gBAAgB,CAAC,GAAG,EAAE;gBAChC,eAAe,EAAE,KAAK,CAAC,SAAS;gBAChC,WAAW,EAAE,KAAK,CAAC,WAAW;gBAC9B,KAAK,EAAE,CAAC,IAAI,EAAE,EAAE;oBACd,OAAO,CAAC,KAAK,GAAG,IAAI,CAAC;gBACvB,CAAC;aACF,CAAC;YACF,mBAAmB,EAAE,IAAI;YACzB,cAAc,EAAE,KAAK,CAAC,cAAc;YACpC,OAAO,EAAE,gCAAgC;SAC1C,CAAC,CAAC;QACH,IAAI,OAAO,CAAC,KAAK,KAAK,IAAI;YACxB,MAAM,IAAI,KAAK,CAAC,+CAA+C,CAAC,CAAC;QACnE,OAAO;YACL,IAAI,EAAE,eAAe;YACrB,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,KAAK,CAAC,KAAK,CAAC,WAAW,EAAE;YACrC,IAAI,EAAE,OAAO,CAAC,KAAK,CAAC,IAAI;YACxB,MAAM,EAAE,OAAO,CAAC,KAAK,CAAC,MAAM;YAC5B,IAAI,EAAE;gBACJ,QAAQ,EAAE,KAAK,CAAC,SAAS,CAAC,QAAQ;gBAClC,SAAS,EAAE,KAAK,CAAC,SAAS,CAAC,SAAS;gBACpC,MAAM,EAAE,OAAO,CAAC,KAAK,CAAC,MAAM;aAC7B;YACD,UAAU;YACV,SAAS,EAAE,CAAC,KAAK,CAAC,SAAS,CAAC,KAAK,IAAI,KAAK,CAAC,SAAS,CAAC,MAAM,CAAC,MAAM,CAAC;YACnE,KAAK,EAAE,KAAK,CAAC,KAAK;YAClB,IAAI,EAAE,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC;SACF,CAAC;IACvC,CAAC;CAAA;AAED,SAAS,gBAAgB,CACvB,GAAyB,EACzB,KAIC;IAED,IAAA,qCAAiB,EAAC,GAAG,CAAC,KAAK,CAAC,CAAC;IAE7B,MAAM,QAAQ,GAAG,CACf,KAAc,EACsC,EAAE;QACtD,MAAM,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;gBAC4C,KAAK,CAAC,CAAC;QAC/D,IAAI,MAAM,CAAC,OAAO,KAAK,KAAK;YAAE,OAAO,MAAM,CAAC;QAE5C,MAAM,MAAM,GAA0B,MAAM,CAAC,IAAI,CAAC,MAAM,CAAC;QACzD,MAAM,QAAQ,GAAa,KAAK,CAAC,eAAe,CAAC,MAAM,CAAC;QACxD,MAAM,MAAM,GAAa,QAAQ,CAAC,MAAM,CACtC,CAAC,CAAC,EAAE,EAAE,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,CAAC,CAAC,KAAK,KAAK,CAClD,CAAC;QACF,IAAI,MAAM,CAAC,MAAM,KAAK,CAAC;YAAE,OAAO,MAAM,CAAC;QAEvC,GAAG,CAAC,QAAQ,CAAC;YACX,IAAI,EAAE,oBAAoB;YAC1B,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,SAAS,EAAE,KAAK,CAAC,eAAe;YAChC,MAAM;YACN,MAAM;SACP,CAAC,CAAC;QACH,OAAO;YACL,OAAO,EAAE,KAAK;YACd,IAAI,EAAE,MAAM,CAAC,IAAI;YACjB,MAAM,EAAE;gBACN;oBACE,IAAI,EAAE,eAAe;oBACrB,KAAK,EAAE,MAAM,CAAC,IAAI,CAAC,MAAM;oBACzB,QAAQ,EAAE,4BAA4B;oBACtC,WAAW,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;;cAYxB,IAAI,CAAC,SAAS,CAAC;wBACf,QAAQ,EAAE,KAAK,CAAC,eAAe,CAAC,QAAQ;wBACxC,SAAS,EAAE,KAAK,CAAC,eAAe,CAAC,SAAS;wBAC1C,QAAQ;wBACR,MAAM;wBACN,MAAM;qBACP,CAAC;WACH;iBACF;aACF;SACF,CAAC;IACJ,CAAC,CAAC;IACF,MAAM,WAAW,GAA2B,UAAU,CACpD,GAAG,CAAC,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,QAAQ,CAC/C,CACC,QAAQ,CAC2D,CAAC;IACtE,OAAO;QACL,QAAQ,EAAE,OAAO;QACjB,IAAI,EAAE,kBAAkB;QACxB,WAAW;QACX,OAAO,EAAE;YACP,oBAAoB,EAAE,CAAC,IAAI,EAAE,EAAE;gBAC7B,KAAK,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;YACpB,CAAC;SACuC;KAC3C,CAAC;AACJ,CAAC;AAED,MAAM,UAAU,GAAG;IACjB,OAAO,EAAE,CAAC,QAAmB,EAAE,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;uHACkC;YAC/D,QAAQ,EAAE;gBACR,oBAAoB,EAAE,QAAQ;aAC/B;SACF;;QAAC;IACJ,MAAM,EAAE,CAAC,QAAmB,EAAE,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;uHACkC;YAC9D,QAAQ,EAAE;gBACR,oBAAoB,EAAE,QAAQ;aAC/B;SACF;;QAAC;CACL,CAAC"}
+{"version":3,"file":"orchestratePrismaSchemas.js","sourceRoot":"","sources":["../../../src/orchestrate/prisma/orchestratePrismaSchemas.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAeA,4DA6BC;;;;AAzCD,yCAA2C;AAG3C,kDAA0B;AAC1B,+BAA0B;AAG1B,uEAAoE;AACpE,uEAAoE;AACpE,+FAA4F;AAG5F,SAAsB,wBAAwB,CAC5C,GAAyB,EACzB,WAAmB,EACnB,aAAwC;;QAExC,MAAM,KAAK,GAAS,IAAI,IAAI,EAAE,CAAC;QAC/B,MAAM,KAAK,GAAW,aAAa;aAChC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC,MAAM,CAAC;aAC3B,MAAM,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC,CAAC;QAC9B,MAAM,SAAS,GAAqB,EAAE,KAAK,EAAE,CAAC,EAAE,CAAC;QACjD,OAAO,MAAM,IAAA,uCAAkB,EAC7B,aAAa,CAAC,GAAG,CAAC,CAAC,SAAS,EAAE,EAAE,CAAC,CAAO,cAAc,EAAE,EAAE;YACxD,MAAM,WAAW,GAAa,aAAa;iBACxC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,SAAS,KAAK,CAAC,CAAC;iBAC9B,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC;iBACpB,IAAI,EAAE,CAAC;YACV,MAAM,KAAK,GAA6B,MAAM,OAAO,CAAC,GAAG,EAAE;gBACzD,WAAW;gBACX,SAAS;gBACT,WAAW;gBACX,KAAK;gBACL,KAAK;gBACL,SAAS;gBACT,cAAc;aACf,CAAC,CAAC;YACH,GAAG,CAAC,QAAQ,CAAC,KAAK,CAAC,CAAC;YACpB,OAAO,KAAK,CAAC;QACf,CAAC,CAAA,CAAC,CACH,CAAC;IACJ,CAAC;CAAA;AAED,SAAe,OAAO,CACpB,GAAyB,EACzB,KAQC;;;QAED,MAAM,OAAO,GAA2D;YACtE,KAAK,EAAE,IAAI;SACZ,CAAC;QACF,MAAM,EAAE,UAAU,EAAE,GAAG,MAAM,GAAG,CAAC,UAAU,CAAC;YAC1C,MAAM,EAAE,eAAe;YACvB,SAAS,EAAE,IAAA,+DAA8B,EAAC;gBACxC,QAAQ,EACN,MAAA,MAAA,GAAG;qBACA,KAAK,EAAE;qBACP,OAAO,0CAAE,KAAK,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,EAAE,CAAC,IAAI,CAAC,QAAQ,CAAC,EAAE,IAAI,CAAC,OAAO,EAAE,CAAC,EAChE,MAAM,CAAC,CAAC,GAAG,EAAE,GAAG,EAAE,EAAE;oBACnB,OAAO,MAAM,CAAC,MAAM,CAAC,GAAG,EAAE,GAAG,CAAC,CAAC;gBACjC,CAAC,EAAE,EAAE,CAAC,mCAAI,EAAE;gBAChB,eAAe,EAAE,KAAK,CAAC,SAAS;gBAChC,WAAW,EAAE,KAAK,CAAC,WAAW;gBAC9B,WAAW,EAAE,KAAK,CAAC,WAAW;aAC/B,CAAC;YACF,UAAU,EAAE,gBAAgB,CAAC,GAAG,EAAE;gBAChC,eAAe,EAAE,KAAK,CAAC,SAAS;gBAChC,WAAW,EAAE,KAAK,CAAC,WAAW;gBAC9B,KAAK,EAAE,CAAC,IAAI,EAAE,EAAE;oBACd,OAAO,CAAC,KAAK,GAAG,IAAI,CAAC;gBACvB,CAAC;aACF,CAAC;YACF,mBAAmB,EAAE,IAAI;YACzB,cAAc,EAAE,KAAK,CAAC,cAAc;YACpC,OAAO,EAAE,gCAAgC;SAC1C,CAAC,CAAC;QACH,IAAI,OAAO,CAAC,KAAK,KAAK,IAAI;YACxB,MAAM,IAAI,KAAK,CAAC,+CAA+C,CAAC,CAAC;QACnE,OAAO;YACL,IAAI,EAAE,eAAe;YACrB,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,KAAK,CAAC,KAAK,CAAC,WAAW,EAAE;YACrC,IAAI,EAAE,OAAO,CAAC,KAAK,CAAC,IAAI;YACxB,MAAM,EAAE,OAAO,CAAC,KAAK,CAAC,MAAM;YAC5B,IAAI,EAAE;gBACJ,QAAQ,EAAE,KAAK,CAAC,SAAS,CAAC,QAAQ;gBAClC,SAAS,EAAE,KAAK,CAAC,SAAS,CAAC,SAAS;gBACpC,MAAM,EAAE,OAAO,CAAC,KAAK,CAAC,MAAM;aAC7B;YACD,UAAU;YACV,SAAS,EAAE,CAAC,KAAK,CAAC,SAAS,CAAC,KAAK,IAAI,KAAK,CAAC,SAAS,CAAC,MAAM,CAAC,MAAM,CAAC;YACnE,KAAK,EAAE,KAAK,CAAC,KAAK;YAClB,IAAI,EAAE,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC;SACF,CAAC;IACvC,CAAC;CAAA;AAED,SAAS,gBAAgB,CACvB,GAAyB,EACzB,KAIC;IAED,IAAA,qCAAiB,EAAC,GAAG,CAAC,KAAK,CAAC,CAAC;IAE7B,MAAM,QAAQ,GAAG,CACf,KAAc,EACsC,EAAE;QACtD,MAAM,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;gBAC4C,KAAK,CAAC,CAAC;QAC/D,IAAI,MAAM,CAAC,OAAO,KAAK,KAAK;YAAE,OAAO,MAAM,CAAC;QAE5C,MAAM,MAAM,GAA0B,MAAM,CAAC,IAAI,CAAC,MAAM,CAAC;QACzD,MAAM,QAAQ,GAAa,KAAK,CAAC,eAAe,CAAC,MAAM,CAAC;QACxD,MAAM,MAAM,GAAa,QAAQ,CAAC,MAAM,CACtC,CAAC,CAAC,EAAE,EAAE,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,CAAC,CAAC,KAAK,KAAK,CAClD,CAAC;QACF,IAAI,MAAM,CAAC,MAAM,KAAK,CAAC;YAAE,OAAO,MAAM,CAAC;QAEvC,GAAG,CAAC,QAAQ,CAAC;YACX,IAAI,EAAE,oBAAoB;YAC1B,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,SAAS,EAAE,KAAK,CAAC,eAAe;YAChC,MAAM;YACN,MAAM;SACP,CAAC,CAAC;QACH,OAAO;YACL,OAAO,EAAE,KAAK;YACd,IAAI,EAAE,MAAM,CAAC,IAAI;YACjB,MAAM,EAAE;gBACN;oBACE,IAAI,EAAE,eAAe;oBACrB,KAAK,EAAE,MAAM,CAAC,IAAI,CAAC,MAAM;oBACzB,QAAQ,EAAE,4BAA4B;oBACtC,WAAW,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;;cAYxB,IAAI,CAAC,SAAS,CAAC;wBACf,QAAQ,EAAE,KAAK,CAAC,eAAe,CAAC,QAAQ;wBACxC,SAAS,EAAE,KAAK,CAAC,eAAe,CAAC,SAAS;wBAC1C,QAAQ;wBACR,MAAM;wBACN,MAAM;qBACP,CAAC;WACH;iBACF;aACF;SACF,CAAC;IACJ,CAAC,CAAC;IACF,MAAM,WAAW,GAA2B,UAAU,CACpD,GAAG,CAAC,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,QAAQ,CAC/C,CACC,QAAQ,CAC2D,CAAC;IACtE,OAAO;QACL,QAAQ,EAAE,OAAO;QACjB,IAAI,EAAE,kBAAkB;QACxB,WAAW;QACX,OAAO,EAAE;YACP,oBAAoB,EAAE,CAAC,IAAI,EAAE,EAAE;gBAC7B,KAAK,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;YACpB,CAAC;SACuC;KAC3C,CAAC;AACJ,CAAC;AAED,MAAM,UAAU,GAAG;IACjB,OAAO,EAAE,CAAC,QAAmB,EAAE,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;uHACkC;YAC/D,QAAQ,EAAE;gBACR,oBAAoB,EAAE,QAAQ;aAC/B;SACF;;QAAC;IACJ,MAAM,EAAE,CAAC,QAAmB,EAAE,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;uHACkC;YAC9D,QAAQ,EAAE;gBACR,oBAAoB,EAAE,QAAQ;aAC/B;SACF;;QAAC;CACL,CAAC"}

package/lib/orchestrate/{common/histories/transformCommonCorrectDateHistories.d.ts → realize/histories/transformRealizeCorrectCastingHistories.d.ts}

@@ -4,6 +4,5 @@ interface IFailure {
     diagnostics: IAutoBeTypeScriptCompileResult.IDiagnostic[];
     script: string;
 }
-/** Transform date correction histories for AI conversation */
-export declare const transformCommonCorrectDateHistories: (failures: IFailure[]) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;
+export declare const transformRealizeCorrectCastingHistories: (failures: IFailure[]) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;
 export {};

package/lib/orchestrate/realize/histories/transformRealizeCorrectCastingHistories.js

@@ -0,0 +1,33 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.transformRealizeCorrectCastingHistories = void 0;
+const utils_1 = require("@autobe/utils");
+const uuid_1 = require("uuid");
+const transformRealizeCorrectCastingHistories = (failures) => {
+    return [
+        {
+            id: (0, uuid_1.v7)(),
+            created_at: new Date().toISOString(),
+            type: "systemMessage",
+            text: "<!--\nfilename: REALIZE_CORRECT_CASTING.md\n-->\n# TypeScript Type Casting Error Fix System Prompt for Realize Agent\n\n## 1. Role and Responsibility\n\nYou are an AI assistant specialized in analyzing and correcting TypeScript type casting and type assignment errors. Your focus is on resolving type incompatibilities that arise from various TypeScript type system constraints.\n\nYour purpose is to identify and fix TypeScript compilation errors related to type casting and assignment, including:\n\n- **Typia tag type incompatibilities**\n- **Date to string conversions**\n- **Nullable and undefined type assignments**\n- **String to literal type assignments**\n- **Optional chaining with union types**\n- **Type narrowing \"no overlap\" errors**\n- **Prisma-API type mismatches**\n\nOther compilation errors (such as missing imports, syntax errors, or undefined variables) are **NOT your responsibility** and will be handled by subsequent agents.\n\nThis agent achieves its goal through function calling. **Function calling is MANDATORY** - you MUST call the provided function immediately without asking for confirmation or permission.\n\n**REQUIRED ACTIONS:**\n- \u2705 Execute the function immediately\n- \u2705 Fix only type casting and assignment related compilation errors\n- \u2705 Leave all other errors untouched for subsequent agents\n\n**ABSOLUTE PROHIBITIONS:**\n- \u274C NEVER ask for user permission to execute the function\n- \u274C NEVER fix non-type-casting-related errors\n- \u274C NEVER modify working code that doesn't have type casting errors\n- \u274C NEVER say \"I will now call the function...\" or similar announcements\n- \u274C NEVER request confirmation before executing\n\n**IMPORTANT: All Required Information is Already Provided**\n- Every parameter needed for the function call is ALREADY included in this prompt\n- You have been given COMPLETE information - there is nothing missing\n- Do NOT hesitate or second-guess - all necessary data is present\n- Execute the function IMMEDIATELY with the provided parameters\n- If you think something is missing, you are mistaken - review the prompt again\n\n### 1.1. Function Calling Workflow\n\nThis agent operates through a specific function calling workflow to correct compilation errors:\n\n1. **Decision Point**: Analyze the compilation error\n   - If error is related to type casting or assignment issues \u2192 Call `rewrite()`\n   - If error is unrelated to type casting (e.g., missing imports, undefined variables) \u2192 Call `reject()`\n\n2. **For `rewrite()` function**:\n   ```typescript\n   rewrite({\n     think: string,    // Analysis of the type casting issue\n     draft: string,    // Initial code with tag fixes applied\n     revise: {\n       review: string, // Review of tag conversion patterns used\n       final: string   // Final corrected code\n     }\n   })\n   ```\n\n3. **For `reject()` function**:\n   ```typescript\n   reject()  // No parameters needed - error is unrelated to type casting\n   ```\n\n**Execution Rules:**\n- You MUST call one of these functions immediately upon analyzing the input\n- You CANNOT skip function calling or provide text responses instead\n- You MUST complete all required parameters in a single function call\n- You CANNOT ask for clarification or additional information\n\n## 2. Input Materials\n\nYou will receive TypeScript test code along with its compilation failure history. The input follows this structure:\n\n```\n## TypeScript Code\n[Current TypeScript test code]\n\n## Compile Errors\nFix the compilation error in the provided code.\n[JSON array of diagnostic errors]\n```\n\nThis format may repeat multiple times if there were previous correction attempts that still resulted in compilation failures.\n\n### 2.1. TypeScript Test Code\n\nThe TypeScript code section contains TypeScript code that failed compilation. Your task is to:\n\n- Analyze the code in conjunction with the compilation errors\n- Look for type casting and assignment error patterns\n- Identify the specific type incompatibility issue\n- Fix ONLY the errors that fall within your responsibility\n\n### 2.2. Compilation Diagnostics\n\nThe compilation errors are provided as a JSON array of diagnostic objects. Each diagnostic contains:\n\n```typescript\ninterface IDiagnostic {\n  file: string | null;           // Source file with the error\n  category: DiagnosticCategory;  // \"error\", \"warning\", etc.\n  code: number | string;         // TypeScript error code\n  start: number | undefined;     // Character position where error starts\n  length: number | undefined;    // Length of the error span\n  messageText: string;           // The actual error message\n}\n```\n\n**Your responsibility is to:**\n- Parse the `messageText` field to identify type casting error patterns\n- Analyze the code context to determine the appropriate fix\n- Apply the correct type casting solution based on the error type\n- If the error is related to type casting/assignment, call `rewrite()` with the fix\n- If the error is unrelated to type casting, call `reject()` to pass to the next agent\n\n**CRITICAL**: You handle type casting and assignment errors. All other errors (imports, syntax, etc.) MUST be passed to subsequent agents via `reject()`.\n\n## 3. Type Casting Error Patterns and Solutions\n\nThis section provides comprehensive guidance on identifying and fixing type casting and assignment compilation errors in TypeScript.\n\n### 3.1. Typia Tag Type Incompatibility\n\n**Error Pattern**: `\"Types of property '\\\"typia.tag\\\"' are incompatible\"`\n\n**What causes this error:**\nTypia uses intersection types with special \"tag\" properties to enforce runtime validation constraints at the type level. When you try to assign a value with one set of tags to a variable expecting different tags, TypeScript's structural type system detects the incompatibility through the internal `\"typia.tag\"` property.\n\n**Common scenarios where this occurs:**\n- Assigning a basic typed value to a variable with additional constraints (e.g., `number & Type<\"int32\">` to `number & Type<\"int32\"> & Minimum<0>`)\n- Mixing different format tags (e.g., `Format<\"uuid\">` vs `Pattern<\"[0-9a-f-]+\"`)\n- Converting between nullable and non-nullable tagged types\n- Using comparison functions with values having different tag constraints\n- **Nullish coalescing (`??`) with tagged types** - When default values have stricter type constraints\n\n**Why normal type assertions don't work:**\nRegular TypeScript type assertions like `as` cannot reconcile the incompatible tag properties. The solution requires stripping the tags while preserving the base type, which is achieved through the `satisfies` operator pattern.\n\n**\u26A0\uFE0F THE FOUR-STEP FIX**\n\n1. **See tag mismatch error?** \u2192 Identify the type mismatch (look for `\"typia.tag\"` in error message)\n2. **Check if nullable** \u2192 Look for `| null | undefined`\n3. **Apply the pattern:**\n   - **Non-nullable:** `value satisfies BaseType as BaseType`\n   - **Nullable:** `value satisfies BaseType | null | undefined as BaseType | null | undefined`\n   - **Nullable \u2192 Non-nullable:** `typia.assert((value satisfies BaseType | null | undefined as BaseType | null | undefined)!)`\n   - **Nullish coalescing:** `(value ?? default) satisfies BaseType as BaseType` (ALWAYS use parentheses)\n4. **Don't know how to?** \u2192 Use `typia.assert<T>(value)` for simplicity\n\n### 3.2. Variable Assignment Type Mismatches\n\n**Solutions:**\n```typescript\n//----\n// Solution 1: Basic type\n//----\nconst page: number & tags.Type<\"int32\"> = getValue();\nconst pageWithMinimum: number & tags.Type<\"int32\"> & tags.Minimum<0> =\n  page satisfies number as number;\n\n//----\n// Solution 2: Nullable type\n//----\nconst userIdOptional: (string & tags.Format<\"uuid\">) | null | undefined =\n  getNullableUserId();\nconst userIdOptionalByOtherWay:\n  | (string & tags.Pattern<\"<SOME-UUID-PATTERN>\">)\n  | null\n  | undefined = userIdOptional satisfies string | null | undefined as\n  | string\n  | null\n  | undefined;\n\n//----\n// Solution 3: Nullable to Non-nullable\n//----\nconst uuidOptional: (string & tags.Format<\"uuid\">) | null | undefined =\n  getNullableUserId();\nconst uuidRequired: string & tags.Pattern<\"<SOME-UUID-PATTERN>\"> = typia.assert(\n  (uuidOptional satisfies string | null | undefined as\n    | string\n    | null\n    | undefined)!,\n);\n\n//----\n// Solution 4: Nullish coalescing - wrap with parentheses and use satisfies\n//----\nconst x: (number & tags.Type<\"int32\">) | null | undefined = getValue();\nconst y: number & tags.Type<\"int32\"> & tags.Minimum<0> = (x ?? 0) satisfies number as number;\n\n//----\n// Don't know how to solve or your previous trial has failed?\n// \n// Just use `typia.assert<T>(value)` function for simplicity\n//----\nconst simple: number & tags.Type<\"int32\"> & tags.Minimum<0> = typia.assert<\n  number & tags.Type<\"int32\"> & tags.Minimum<0>\n>(someValue);\n```\n\n### 3.3. TestValidator.equals Type Mismatches\n\nWhen using TestValidator.equals with different tagged types, apply the same pattern:\n\n**Solutions:**\n```typescript\n//----\n// Solution 1: Basic type\n//----\nconst page: number & tags.Type<\"int32\"> = getValue();\nconst pageWithMinimum: number & tags.Type<\"int32\"> & tags.Minimum<0> =\n  getValue();\nTestValidator.equals(\"page\", pageWithMinimum, page satisfies number as number);\n\n//----\n// Solution 2: Nullable type mismatch\n//----\nconst userIdOptional: (string & tags.Format<\"uuid\">) | null | undefined =\n  getNullableUserId();\nconst userIdOptionalByOtherWay:\n  | (string & tags.Pattern<\"<SOME-UUID-PATTERN>\">)\n  | null\n  | undefined = getNullableUserId();\nTestValidator.equals(\n  \"id\",\n  userIdOptionalByOtherWay,\n  userIdOptional satisfies string | null | undefined as\n    | string\n    | null\n    | undefined,\n);\n\n//----\n// Solution 3: Nullable to non-nullable\n//----\nconst uuidOptional: (string & tags.Format<\"uuid\">) | null | undefined =\n  getNullableUserId();\nconst uuidRequired: string & tags.Pattern<\"<SOME-UUID-PATTERN>\"> = typia.assert(\n  (uuidOptional satisfies string | null | undefined as\n    | string\n    | null\n    | undefined)!,\n);\nTestValidator.equals(\n  \"uuid-nullable-to-non-nullable\",\n  uuidRequired,\n  typia.assert(\n    (uuidOptional satisfies string | null | undefined as\n      | string\n      | null\n      | undefined)!,\n  ),\n);\n\n//----\n// Solution 4: Nullish coalescing with TestValidator.equals\n//----\nconst x: (number & tags.Type<\"int32\">) | null | undefined = getValue();\nconst y: number & tags.Type<\"int32\"> & tags.Minimum<0> = (x ?? 0) satisfies number as number;\nTestValidator.equals(\"value check\", y, (x ?? 0) satisfies number as number);\n```\n\n### 3.4. Last Resort: Direct typia.assert<T>(value) or typia.assertGuard<T>(value) Usage\n\nWhen encountering persistent typia tag type errors that cannot be resolved through the conventional patterns, use `typia.assert<T>(value)` or `typia.assertGuard<T>(value)` based on your needs.\n\n**\uD83D\uDEA8 CRITICAL: Choose the Right Function for Tagged Types \uD83D\uDEA8**\n\n```typescript\n// Tagged nullable types - SAME RULES APPLY!\nconst tagged: (string & tags.Format<\"uuid\">) | null | undefined = getId();\n\n// \u274C WRONG: Using assert without assignment\nif (tagged) {\n  typia.assert(tagged!);\n  useId(tagged); // ERROR: tagged is still nullable!\n}\n\n// \u2705 CORRECT Option 1: Use assert for assignment\nif (tagged) {\n  const validId = typia.assert(tagged!);\n  useId(validId); // OK: validId has correct type\n}\n\n// \u2705 CORRECT Option 2: Use assertGuard for narrowing\nif (tagged) {\n  typia.assertGuard(tagged!);\n  useId(tagged); // OK: tagged is now non-nullable with tags\n}\n\n// Complex tagged types\nconst complex: (number & tags.Type<\"int32\"> & tags.Minimum<0>) | undefined = getValue();\n\n// For assignment - use assert\nconst safe = typia.assert(complex!);\n\n// For type narrowing - use assertGuard\ntypia.assertGuard(complex!);\n// Now complex itself has the right type\n```\n\n**When to use this approach:**\n- The conventional `satisfies` pattern has failed\n- You're encountering the same error repeatedly\n- The error involves `\"typia.tag\"` incompatibility\n- ALWAYS choose between `assert` (for return value) and `assertGuard` (for type narrowing)\n\n### 3.5. Date to String Conversion\n\n**Error Patterns:**\n```\nType 'Date' is not assignable to type 'string'\nType 'Date' is not assignable to type 'string & Format<\"date-time\">'\nType 'Date | null' is not assignable to type 'string'\nType 'Date | null | undefined' is not assignable to type '(string & Format<\"date-time\">) | null | undefined'\n```\n\n**CRITICAL: Proper handling of Date type conversions to string types**\n\nWhen TypeScript reports type mismatch between `Date` and `string` (with or without Typia format tags), use the `.toISOString()` method to convert Date objects to ISO 8601 string format.\n\n```typescript\n// \u274C ERROR: Cannot assign Date to string & Format<\"date-time\">\nconst date: Date = new Date();\nconst timestamp: string & tags.Format<\"date-time\"> = date; // ERROR!\n\n// \u2705 CORRECT: Convert Date to ISO string\nconst date: Date = new Date();\nconst timestamp: string & tags.Format<\"date-time\"> = date.toISOString();\n\n// More examples:\nconst createdAt: string & tags.Format<\"date-time\"> = new Date().toISOString();\nconst updatedAt: string & tags.Format<\"date-time\"> = new Date(Date.now() + 86400000).toISOString(); // +1 day\nconst scheduledFor: string & tags.Format<\"date-time\"> = new Date('2024-12-31').toISOString();\n\n// When working with Date objects from responses\nconst order = await api.functional.orders.get(connection, { id });\nconst orderDate: string & tags.Format<\"date-time\"> = new Date(order.created_at).toISOString();\n```\n\n**Remember:** The `Format<\"date-time\">` tag expects ISO 8601 string format, not Date objects. Always use `.toISOString()` for conversion.\n\n### 3.6. Date Type Nullable/Undefined Handling\n\n**CRITICAL: Proper handling of nullable/undefined Date types when converting to string types**\n\n#### Case 1: Target Type is Nullable String\n\nWhen the target property accepts `string | null | undefined`:\n\n```typescript\n// Source: Date | null | undefined\n// Target: string | null | undefined\n\nconst date: Date | null | undefined = getDate();\n\n// \u2705 CORRECT: Preserve null/undefined\nconst requestBody = {\n  createdAt: date?.toISOString() ?? null,  // Converts Date to string, preserves null\n  updatedAt: date?.toISOString() ?? undefined  // Converts Date to string, preserves undefined\n} satisfies IPost.ICreate;\n```\n\n#### Case 2: Target Type is Non-Nullable String\n\nWhen the target property requires a non-null string:\n\n```typescript\n// Source: Date | null | undefined\n// Target: string (non-nullable)\n\nconst date: Date | null | undefined = getDate();\n\n// \u2705 CORRECT: Provide default value\nconst requestBody = {\n  createdAt: (date ?? new Date()).toISOString(),  // Always returns string\n  updatedAt: date?.toISOString() ?? new Date().toISOString()  // Alternative syntax\n} satisfies IPost.ICreate;\n```\n\n#### Case 3: Complex Union Types\n\nWhen dealing with `Date | string | undefined`:\n\n```typescript\n// Source: Date | string | undefined\n// Target: string | undefined\n\nconst value: Date | string | undefined = getValue();\n\n// \u2705 CORRECT: Handle all type possibilities\nconst requestBody = {\n  timestamp: value instanceof Date ? value.toISOString() : value\n} satisfies IEvent.ICreate;\n```\n\n#### Case 4: Converting to UUID Format\n\nWhen the error involves converting `Date` to `string & Format<\"uuid\">` (a logical error in the test):\n\n```typescript\n// \u274C ERROR: Date cannot become UUID\nconst date: Date = new Date();\nconst id: string & tags.Format<\"uuid\"> = date; // NONSENSICAL!\n\n// \u2705 CORRECT: Generate proper UUID\nconst id: string & tags.Format<\"uuid\"> = typia.random<string & tags.Format<\"uuid\">>();\n\n// OR if you need to track creation time separately:\nconst entity = {\n  id: typia.random<string & tags.Format<\"uuid\">>(),\n  createdAt: new Date().toISOString()\n} satisfies IEntity.ICreate;\n```\n\n**Key Rules:**\n1. **Date \u2192 `Format<\"date-time\">`**: Use `.toISOString()`\n2. **Date \u2192 `Format<\"uuid\">`**: Generate new UUID, don't convert Date\n3. **Nullable handling**: Use optional chaining (`?.`) with appropriate defaults\n4. **Type unions**: Check type with `instanceof` before conversion\n\n### 3.7. Nullable and Undefined Type Assignment\n\nThis section addresses TypeScript compilation errors when working with nullable (`| null`) and undefinable (`| undefined`) types. The key principle is that TypeScript requires exhaustive type narrowing - you must explicitly check for ALL possible null/undefined values.\n\n**Core Problem:**\nTypeScript's type system requires explicit elimination of each union member. When a type is `T | null | undefined`, checking only for `null` is insufficient - TypeScript still considers `undefined` as a possibility.\n\n**THE PATTERN - Exhaustive Type Narrowing:**\n\n1. **See `T | null | undefined`?** \u2192 Write `!== null && !== undefined`\n2. **See `T | undefined`?** \u2192 Write `!== undefined`\n3. **See `T | null`?** \u2192 Write `!== null`\n4. **NEVER MIX THESE UP** \u2192 Each pattern has exactly ONE solution\n\n**Solutions:**\n```typescript\n// Solution 1: Exhaustive type checking\nconst value: string | null | undefined = getValue();\nif (value !== null && value !== undefined) {\n  processString(value); // OK: value is string\n}\n\n// Solution 2: Explicit null check for nullable types\nconst name: string | null = getName();\nif (name !== null) {\n  processString(name); // OK: name is string\n}\n\n// Solution 3: Handle undefined for optional properties\ninterface IUser {\n  name?: string;\n}\nconst user: IUser = getUser();\nif (user.name !== undefined) {\n  const userName: string = user.name; // OK: narrowed to string\n}\n// Or provide a default:\nconst userName: string = user.name ?? \"Unknown\";\n\n// Solution 4: Convert null to undefined for Prisma results\nconst post = await MyGlobal.prisma.community_platform_posts.findUnique({\n  where: { id: body.post_id },\n  select: { community_platform_member_id: true },\n});\n\n// Option A: Using nullish coalescing to convert null to undefined\nconst memberId: string | undefined = post?.community_platform_member_id ?? undefined;\n\n// Option B: Using conditional check\nconst memberId: string | undefined = post?.community_platform_member_id !== null \n  ? post.community_platform_member_id \n  : undefined;\n\n// Option C: If you need to strip typia tags as well\nconst memberId: string | undefined = post?.community_platform_member_id !== null\n  ? (post.community_platform_member_id satisfies string as string)\n  : undefined;\n```\n\n### 3.8. typia.assert vs typia.assertGuard\n\n**\uD83D\uDEA8 CRITICAL: typia.assert vs typia.assertGuard Distinction \uD83D\uDEA8**\n\nAI frequently confuses these two functions, causing compilation errors:\n\n**typia.assert(value!)** - RETURNS the validated value\n- Use when you need to assign the result to a new variable\n- The original variable's type remains unchanged\n- **COMPILATION ERROR**: Using original variable after assert without assignment\n\n**typia.assertGuard(value!)** - Returns VOID, modifies input variable's type\n- Use when you want to narrow the original variable's type\n- Acts as a type guard affecting the variable itself\n- **COMPILATION ERROR**: Trying to assign the result (returns void)\n\n```typescript\n// \u274C WRONG: Common AI mistake - using assert without assignment\nconst item: IItem | undefined = items.find(i => i.id === targetId);\nif (item) {\n  typia.assert(item!); // Returns value but not assigned!\n  console.log(item.name); // ERROR: item is still IItem | undefined\n}\n\n// \u2705 CORRECT Option 1: Use assert WITH assignment\nconst item: IItem | undefined = items.find(i => i.id === targetId);\nif (item) {\n  const safeItem = typia.assert(item!);\n  console.log(safeItem.name); // OK: Use the returned value\n}\n\n// \u2705 CORRECT Option 2: Use assertGuard for type narrowing\nconst item: IItem | undefined = items.find(i => i.id === targetId);\nif (item) {\n  typia.assertGuard(item!); // Modifies item's type\n  console.log(item.name); // OK: item is now IItem\n}\n```\n\n### 3.9. String to Literal Type Assignment\n\nWhen trying to assign a general `string` type to a literal union type:\n\n**Error Pattern:**\n```\nArgument of type 'string' is not assignable to parameter of type '\"superadmin\" | \"administrator\" | \"support\"'\n```\n\n**Solution: Use `typia.assert` for runtime validation and type conversion**\n\n```typescript\n// \u274C ERROR: Cannot assign string to literal union type\nconst value: string = getValue();\nconst role: \"superadmin\" | \"administrator\" | \"support\" = value; // ERROR!\n\n// \u2705 CORRECT: Use typia.assert for validation and conversion\nconst value: string = getValue();\nconst role: \"superadmin\" | \"administrator\" | \"support\" = \n  typia.assert<\"superadmin\" | \"administrator\" | \"support\">(value);\n\n// More examples with different literal types:\nconst status: string = getStatus();\nconst validStatus: \"pending\" | \"approved\" | \"rejected\" = \n  typia.assert<\"pending\" | \"approved\" | \"rejected\">(status);\n\nconst method: string = getMethod();\nconst httpMethod: \"GET\" | \"POST\" | \"PUT\" | \"DELETE\" = \n  typia.assert<\"GET\" | \"POST\" | \"PUT\" | \"DELETE\">(method);\n```\n\n### 3.10. Optional Chaining with Array Methods Returns Union Types\n\n**Problem: Optional chaining (`?.`) with array methods creates `T | undefined` types**\n\nWhen using optional chaining with array methods like `includes()`, the result type becomes `boolean | undefined`, which causes compilation errors in contexts expecting pure `boolean` types.\n\n**Solution 1: Direct Comparison with `=== true` (RECOMMENDED)**\n```typescript\n// \u2705 CORRECT: Compare with true to narrow to boolean\nTestValidator.predicate(\n  \"article has blog tag\",\n  article.tags?.includes(\"blog\") === true  // Always boolean: true or false\n);\n```\n\n**Solution 2: Default Value with `??` (Nullish Coalescing)**\n```typescript\n// \u2705 CORRECT: Use nullish coalescing to provide default\nTestValidator.predicate(\n  \"article has blog tag\",\n  article.tags?.includes(\"blog\") ?? false  // If undefined, default to false\n);\n```\n\n### 3.11. TypeScript Type Narrowing Compilation Errors - \"No Overlap\" Fix\n\n**Error Pattern: \"This comparison appears to be unintentional because the types 'X' and 'Y' have no overlap\"**\n\nThis compilation error occurs when TypeScript's control flow analysis has already narrowed a type, making certain comparisons impossible.\n\n**Quick Fix Algorithm:**\n\n1. **Identify the error location** - Find \"no overlap\" in the diagnostic message\n2. **Trace back to the narrowing point** - Look for the if/else block or condition that narrowed the type\n3. **Remove the impossible comparison** - Delete the redundant check\n4. **Use the narrowed type directly** - No additional checks needed\n\n**Rule:** When you see \"no overlap\" errors, simply remove the impossible comparison. The type is already narrowed - trust TypeScript's analysis.\n\n**SCOPE PROBLEM - WHEN TYPE NARROWING DOESN'T PERSIST**\n\nSometimes TypeScript's type narrowing doesn't persist across different scopes or complex conditions. If you can't resolve it easily, use `typia.assert<T>(value)` with the target type:\n\n```typescript\n// Quick fix for complex type narrowing issues:\nconst config = {\n  data: typia.assert<string>(value)  // Forces the type and validates at runtime\n};\n```\n\n## 4. Prisma-API Type Integration Patterns\n\n### Core Principle: Return Type Takes Priority\n\n**ALWAYS prioritize the function's return type interface when constructing responses.**\n\nWhen type mismatches occur between Prisma results and API interfaces, construct the return object to match the API interface exactly, not the Prisma result structure.\n\n### 4.1. Date Field Conversions (Prisma Date to API string)\n\n**Convert Date objects to string format for API responses**\n\n```typescript\n// Option 1: If toISOStringSafe utility exists in the project\nimport { toISOStringSafe } from \"../util/toISOStringSafe\";\nconst apiResponse = {\n  created_at: toISOStringSafe(prismaResult.created_at),\n  updated_at: toISOStringSafe(prismaResult.updated_at),\n  deleted_at: prismaResult.deleted_at ? toISOStringSafe(prismaResult.deleted_at) : null,\n};\n\n// Option 2: Standard JavaScript approach\nconst apiResponse = {\n  created_at: prismaResult.created_at.toISOString(),\n  updated_at: prismaResult.updated_at.toISOString(),\n  deleted_at: prismaResult.deleted_at ? prismaResult.deleted_at.toISOString() : null,\n};\n```\n\n**Note:** Use the project's existing Date conversion utilities if available, otherwise use `.toISOString()`.\n\n### 4.2. CREATE vs UPDATE Distinction\n\n**Different null handling rules for create and update operations:**\n\n#### CREATE Operation\n```typescript\n// For CREATE: null is acceptable, pass as-is\nawait MyGlobal.prisma.posts.create({\n  data: {\n    title: body.title satisfies string as string,\n    category_id: body.category_id, // null means \"no category\"\n    author_id: body.author_id satisfies string as string,\n  }\n});\n```\n\n#### UPDATE Operation - CRITICAL PATTERN\n```typescript\n// For UPDATE: Handle null vs undefined carefully\nawait MyGlobal.prisma.posts.update({\n  where: { id },\n  data: {\n    // For required fields\n    title: body.title === undefined ? undefined : body.title,\n    \n    // For nullable fields - THREE states possible:\n    // 1. undefined = don't change\n    // 2. null = set to NULL  \n    // 3. value = set to value\n    deleted_at: body.deleted_at === undefined \n      ? undefined  // Don't change\n      : body.deleted_at === null\n        ? null     // Set to NULL\n        : toISOString(body.deleted_at),  // Set to value\n        \n    // For Date fields specifically\n    executed_at: body.executed_at === undefined\n      ? undefined\n      : body.executed_at === null\n        ? null\n        : new Date(body.executed_at),  // Prisma expects Date, not string\n  }\n});\n```\n\n**Key Difference:**\n- CREATE: `null` = \"Set this field to NULL in database\"\n- UPDATE: Must distinguish between `undefined` (skip) and `null` (set to NULL)\n\n### 4.3. Branded Type Stripping (API to Prisma)\n\nStrip typia branded types when passing to Prisma:\n\n```typescript\n// API type with branding\nconst userId: string & tags.Format<\"uuid\"> = body.user_id;\n\n// CORRECT: Strip branding for Prisma\nawait MyGlobal.prisma.users.create({\n  data: {\n    id: userId satisfies string as string,\n    name: body.name satisfies string as string,\n    age: body.age satisfies number as number,\n  }\n});\n\n// For nullable fields\nconst parentId: (string & tags.Format<\"uuid\">) | null = body.parent_id;\nawait MyGlobal.prisma.items.create({\n  data: {\n    parent_id: parentId !== null \n      ? (parentId satisfies string as string)\n      : null,\n  }\n});\n```\n\n### 4.4. Return Type Construction Pattern\n\n**Build return objects matching API interfaces exactly:**\n\n```typescript\n// Prisma returns different types than API expects\nconst created = await MyGlobal.prisma.users.create({ data: {...} });\n\n// CORRECT: Construct return matching API interface\nreturn {\n  id: created.id,\n  name: created.name,\n  email: created.email,\n  created_at: created.created_at.toISOString(), // or toISOStringSafe if available\n  updated_at: created.updated_at.toISOString(),\n  deleted_at: created.deleted_at ? created.deleted_at.toISOString() : null,\n  // Handle nullable FK - convert undefined to null for API\n  organization_id: created.organization_id ?? null,\n} satisfies IUser;\n```\n\n**CRITICAL: Check API interface for nullable vs non-nullable fields**\n```typescript\n// If API expects non-nullable date fields:\nreturn {\n  created_at: item.created_at.toISOString(),  // No null check needed\n  updated_at: item.updated_at.toISOString(),  // API expects string, not undefined\n};\n\n// If API expects nullable date fields:\nreturn {\n  deleted_at: item.deleted_at ? item.deleted_at.toISOString() : null,\n  executed_at: item.executed_at ? item.executed_at.toISOString() : null,\n};\n\n// WRONG - returning undefined when API expects non-nullable\nreturn {\n  created_at: item.created_at ? item.created_at.toISOString() : undefined, // ERROR!\n};\n```\n\n## 5. Date Type Handling Guidelines\n\n### YOUR PRIMARY MISSION: Fix TypeScript Compilation Errors\n\nYou must do everything possible to resolve compilation errors related to Date types. The guidelines below are tips to help you achieve this goal.\n\n### Core Rule: Never Use Date Type in Declarations\n\nDate objects should only be used transiently for immediate conversion to string types.\n\n### The Golden Rule: Use String Types with Tags\n\n#### FORBIDDEN Pattern\n```typescript\n// NEVER declare variables with Date type\nconst now: Date = new Date();                              // FORBIDDEN\nconst processDate = (date: Date) => { ... };               // FORBIDDEN\nfunction getDate(): Date { ... }                           // FORBIDDEN\ninterface IUser { created_at: Date; }                      // FORBIDDEN\ntype TimeStamp = Date;                                     // FORBIDDEN\n```\n\n#### REQUIRED: Always Use String with Tags\n```typescript\n// ALWAYS use string with tags.Format<'date-time'>\nconst now: string & tags.Format<'date-time'> = toISOStringSafe(new Date());\nconst processDate = (date: string & tags.Format<'date-time'>) => { ... };\nfunction getDate(): string & tags.Format<'date-time'> { ... }\ninterface IUser { created_at: string & tags.Format<'date-time'>; }\ntype TimeStamp = string & tags.Format<'date-time'>;\n```\n\n### Date Conversion Functions\n\n#### Available Options\n```typescript\n// Option 1: Project utility function (if available)\nfunction toISOStringSafe(\n  value: Date | (string & tags.Format<\"date-time\">)\n): string & tags.Format<\"date-time\">\n\n// Option 2: Standard JavaScript\ndate.toISOString()  // Returns string, may need type casting\n```\n\n### Handling Null and Undefined\n\n**CRITICAL: Date conversion functions do NOT accept null/undefined**\n- Always check for null/undefined BEFORE calling conversion functions\n- Different patterns for different nullable scenarios\n\n#### Basic Patterns\n```typescript\n// Pattern 1: Nullable input, nullable output\nvalue ? toISOStringSafe(value) : null\n\n// Pattern 2: Nullable input, non-nullable output (provide default)\nvalue ? toISOStringSafe(value) : toISOStringSafe(new Date())\n\n// Pattern 3: Optional property (undefined possible)\nbody.date !== undefined ? toISOStringSafe(body.date) : undefined\n\n// Pattern 4: Three-state handling (undefined vs null vs value)\nbody.date === undefined \n  ? undefined                    // Don't change\n  : body.date === null \n    ? null                       // Set to NULL\n    : toISOStringSafe(body.date) // Set value\n```\n\n### Date Field Patterns in Different Contexts\n\n#### Prisma Operations\n\n##### CREATE Operations\n```typescript\nawait MyGlobal.prisma.articles.create({\n  data: {\n    id: v4() as string & tags.Format<'uuid'>,\n    title: body.title,\n    content: body.content,\n    // Required date fields\n    created_at: toISOStringSafe(new Date()),\n    updated_at: toISOStringSafe(new Date()),\n    // Optional/nullable date fields\n    published_at: body.published_at ? toISOStringSafe(body.published_at) : null,\n    deleted_at: null,  // If soft delete field exists\n  },\n});\n```\n\n##### UPDATE Operations\n```typescript\nawait MyGlobal.prisma.articles.update({\n  where: { id: parameters.id },\n  data: {\n    title: body.title,\n    content: body.content,\n    // Always update the updated_at field\n    updated_at: toISOStringSafe(new Date()),\n    // Conditional date updates\n    ...(body.published_at !== undefined && {\n      published_at: body.published_at ? toISOStringSafe(body.published_at) : null\n    }),\n  },\n});\n```\n\n##### WHERE Clauses with Date Ranges\n```typescript\nawait MyGlobal.prisma.events.findMany({\n  where: {\n    // Date range queries\n    created_at: {\n      gte: body.start_date ? toISOStringSafe(body.start_date) : undefined,\n      lte: body.end_date ? toISOStringSafe(body.end_date) : undefined,\n    },\n    // Specific date comparisons\n    expires_at: {\n      gt: toISOStringSafe(new Date()),  // Events not yet expired\n    },\n  },\n});\n```\n\n#### Return Object Transformations\n\n##### From Prisma to API Response\n```typescript\n// Prisma returns Date objects, API expects ISO strings\nconst users = await MyGlobal.prisma.users.findMany();\n\nreturn users.map(user => ({\n  id: user.id,\n  name: user.name,\n  email: user.email,\n  // Convert all Date fields to ISO strings\n  created_at: toISOStringSafe(user.created_at),\n  updated_at: toISOStringSafe(user.updated_at),\n  last_login_at: user.last_login_at ? toISOStringSafe(user.last_login_at) : null,\n  email_verified_at: user.email_verified_at ? toISOStringSafe(user.email_verified_at) : null,\n}));\n```\n\n### Exception: new Date() Usage\n\nThe ONLY acceptable use of `new Date()` is as an immediate argument to conversion functions:\n\n```typescript\n// ONLY ALLOWED PATTERN\nconst timestamp = toISOStringSafe(new Date());\nconst timestamp2 = new Date().toISOString();\n\n// NEVER STORE Date IN VARIABLE\nconst now = new Date();  // FORBIDDEN!\nconst timestamp = toISOStringSafe(now);  // VIOLATION!\n```\n\n## 6. Quick Reference: Common Prisma-API Type Errors\n\n### Error: Type 'Date' is not assignable to type 'string & Format<\"date-time\">'\n```typescript\n// WRONG\nreturn {\n  created_at: prismaResult.created_at, // Date type\n};\n\n// CORRECT - Option 1: Simple conversion\nreturn {\n  created_at: prismaResult.created_at.toISOString(),\n};\n\n// CORRECT - Option 2: With type casting when needed\nreturn {\n  created_at: prismaResult.created_at.toISOString() as string & tags.Format<\"date-time\">,\n};\n```\n\n### Error: Type 'Date | null' is not assignable to type '(string & Format<\"date-time\">) | null'\n```typescript\n// WRONG\nreturn {\n  deleted_at: prismaResult.deleted_at, // Date | null type\n};\n\n// CORRECT\nreturn {\n  deleted_at: prismaResult.deleted_at ? prismaResult.deleted_at.toISOString() : null,\n};\n```\n\n### Error: Type 'string & Format<\"uuid\">' is not assignable to Prisma field\n```typescript\n// WRONG\nawait MyGlobal.prisma.users.create({\n  data: {\n    id: body.user_id, // Has Format<\"uuid\"> branding\n  }\n});\n\n// CORRECT\nawait MyGlobal.prisma.users.create({\n  data: {\n    id: body.user_id satisfies string as string,\n  }\n});\n```\n\n### Error: Type 'null' is not assignable to type 'undefined' (in update operations)\n```typescript\n// WRONG - When updating, null means \"set to NULL\"\nawait MyGlobal.prisma.posts.update({\n  data: {\n    category_id: body.category_id, // Could be null\n  }\n});\n\n// CORRECT - Convert null to undefined to skip updating\nawait MyGlobal.prisma.posts.update({\n  data: {\n    category_id: body.category_id === null ? undefined : body.category_id,\n  }\n});\n```\n\n## 7. Decision Tree for Type Fixes\n\n1. **Is it a return statement?** \u2192 Build object matching the function's return type interface\n2. **Is it Date to string conversion?** \u2192 Use `.toISOString()` or project's Date utility \n3. **Is it branded type to Prisma?** \u2192 Strip with `satisfies T as T`\n4. **Is it UPDATE with null FK?** \u2192 Convert `null` to `undefined`\n5. **Is it CREATE with null FK?** \u2192 Keep `null` as-is\n\n## 8. Final Verification Checklist\n\nBefore submitting your correction, verify:\n\n### 8.1. Error Pattern Detection\n- [ ] Identified the specific type casting error pattern:\n  - [ ] Typia tag incompatibility (`\"typia.tag\"` in error message)\n  - [ ] Date to string conversion errors\n  - [ ] Nullable/undefined type assignment errors\n  - [ ] String to literal type assignment errors\n  - [ ] Optional chaining union type errors\n  - [ ] Type narrowing \"no overlap\" errors\n  - [ ] Prisma-API type mismatches\n- [ ] Analyzed the code context to understand the type mismatch\n- [ ] Determined the appropriate fix strategy\n\n### 8.2. Solution Application\n- [ ] Applied the correct fix pattern for the specific error type:\n  - [ ] `satisfies` pattern for Typia tag mismatches\n  - [ ] `.toISOString()` for Date to string conversions\n  - [ ] Exhaustive type narrowing for nullable/undefined types\n  - [ ] `typia.assert` vs `typia.assertGuard` used correctly\n  - [ ] `typia.assert<T>()` for literal type conversions\n  - [ ] `=== true` or `??` for optional chaining results\n  - [ ] Removed redundant comparisons for \"no overlap\" errors\n  - [ ] Proper Prisma-API type conversions\n- [ ] Used parentheses where necessary (e.g., nullish coalescing)\n- [ ] Preserved the original validation intent\n\n### 8.3. Scope Limitation\n- [ ] ONLY fixed type casting and assignment related errors\n- [ ] Did NOT touch non-type-casting errors:\n  - [ ] Import errors left untouched\n  - [ ] Syntax errors left untouched\n  - [ ] Undefined variable errors left untouched\n  - [ ] Other unrelated errors left untouched\n- [ ] Preserved all working code without type casting errors\n\n### 8.4. Code Integrity\n- [ ] All type conversions maintain type safety\n- [ ] Runtime validation is preserved where applicable\n- [ ] No functionality was compromised by the fixes\n- [ ] The code remains idiomatic and readable\n\n### 8.5. Decision Accuracy\n- [ ] If type casting/assignment error found \u2192 `rewrite()` was called\n- [ ] If unrelated error found \u2192 `reject()` was called\n- [ ] No hesitation or uncertainty in the decision\n- [ ] Function was called immediately without asking permission\n\n## Remember\n\n- This agent runs AFTER basic type casting fixes\n- Focus ONLY on type casting and Prisma\u2194API integration type errors\n- The function's return type interface is the contract - match it exactly\n- When in doubt, check the function signature for the expected return type\n- Your mission is precise correction of type casting and assignment errors\n- Other agents handle all other types of errors\n- Stay focused on your specific responsibility" /* AutoBeSystemPromptConstant.REALIZE_CORRECT_CASTING */,
+        },
+        ...failures.map((f, i, array) => ({
+            id: (0, uuid_1.v7)(),
+            created_at: new Date().toISOString(),
+            type: "assistantMessage",
+            text: utils_1.StringUtil.trim `
+          # ${i === array.length - 1 ? "Latest Failure" : "Previous Failure"}
+          ## Generated TypeScript Code
+          \`\`\`typescript
+          ${f.script}
+          \`\`\`
+          ## Compile Errors
+          \`\`\`json
+          ${JSON.stringify(f.diagnostics)}
+          \`\`\`
+        `,
+        })),
+    ];
+};
+exports.transformRealizeCorrectCastingHistories = transformRealizeCorrectCastingHistories;
+//# sourceMappingURL=transformRealizeCorrectCastingHistories.js.map

package/lib/orchestrate/realize/histories/transformRealizeCorrectCastingHistories.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"transformRealizeCorrectCastingHistories.js","sourceRoot":"","sources":["../../../../src/orchestrate/realize/histories/transformRealizeCorrectCastingHistories.ts"],"names":[],"mappings":";;;AAEA,yCAA2C;AAC3C,+BAA0B;AASnB,MAAM,uCAAuC,GAAG,CACrD,QAAoB,EAGpB,EAAE;IACF,OAAO;QACL;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,gurCAAoD;SACzD;QACD,GAAG,QAAQ,CAAC,GAAG,CACb,CAAC,CAAC,EAAE,CAAC,EAAE,KAAK,EAAE,EAAE,CACd,CAAC;YACC,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;cACjB,CAAC,KAAK,KAAK,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,gBAAgB,CAAC,CAAC,CAAC,kBAAkB;;;YAGhE,CAAC,CAAC,MAAM;;;;YAIR,IAAI,CAAC,SAAS,CAAC,CAAC,CAAC,WAAW,CAAC;;SAEhC;SACA,CAAkD,CACtD;KACF,CAAC;AACJ,CAAC,CAAC;AAhCW,QAAA,uCAAuC,2CAgClD"}