@autobe/agent 0.30.4 → 0.30.5

package/lib/orchestrate/realize/orchestrateRealizeCollectorWrite.js

@@ -107,7 +107,7 @@ function process(ctx, props) {
                             properties: {
                                 thinking: {
                                     type: "string",
-                                    description: "Think before you act.\n\nBefore requesting preliminary data or completing your task, reflect on\nyour current state and explain your reasoning:\n\nFor preliminary requests:\n\n- What database schemas are missing that you need?\n- Why do you need them for collector generation?\n- Be brief - state the gap, don't list everything you have.\n\nFor completion:\n\n- What schemas did you acquire?\n- What collector patterns did you implement?\n- Why is it sufficient to complete?\n- Summarize - don't enumerate every field mapping.\n\nNote: All necessary DTO type information is available transitively from\nthe DTO type names in the plan. You only need to request database\nschemas.\n\nThis reflection helps you avoid duplicate requests and premature\ncompletion."
+                                    description: "Think before you act.\n\nFor preliminary requests: what database schemas are missing and why?\n\nFor completion: what schemas did you acquire, what patterns did you\nimplement, and why is it sufficient? Summarize \u2014 don't enumerate every\nfield.\n\nNote: All DTO type information is available transitively from the plan's\nDTO type names. You only need to request database schemas."
                                 },
                                 request: {
                                     oneOf: [
@@ -125,7 +125,7 @@ function process(ctx, props) {
                                             complete: "#/components/schemas/IAutoBeRealizeCollectorWriteApplication.IComplete"
                                         }
                                     },
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform:\n\n- \"getDatabaseSchemas\": Retrieve database table schemas for DB structure\n- \"complete\": Generate final collector implementation\n\nAll necessary DTO type information is obtained transitively from the DTO\ntype names provided in the plan (AutoBeRealizeCollectorPlan). Each DTO\ntype name allows the system to recursively fetch all referenced types,\nproviding complete type information without requiring explicit schema\nrequests.\n\nThe preliminary types are removed from the union after their respective\ndata has been provided, physically preventing repeated calls."
+                                    description: "Action to perform. Exhausted preliminary types are removed from the\nunion, physically preventing repeated calls."
                                 }
                             },
                             required: [
@@ -138,7 +138,7 @@ function process(ctx, props) {
                             properties: {
                                 type: {
                                     "const": "getDatabaseSchemas",
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getDatabaseSchemas\" indicates this is a preliminary\ndata request for database schemas."
+                                    description: "Type discriminator."
                                 },
                                 schemaNames: {
                                     type: "array",
@@ -146,14 +146,14 @@ function process(ctx, props) {
                                         type: "string"
                                     },
                                     minItems: 1,
-                                    description: "List of database table names to retrieve.\n\nTable names from the database schema representing database entities (e.g.,\n\"user\", \"post\", \"comment\").\n\nCRITICAL: DO NOT request the same schema names that you have already\nrequested in previous calls."
+                                    description: "Database table names to retrieve. DO NOT request same names already\nrequested in previous calls."
                                 }
                             },
                             required: [
                                 "type",
                                 "schemaNames"
                             ],
-                            description: "Request to retrieve database schema definitions for context.\n\nThis type is used in the preliminary phase to request specific database table\nschemas needed for generating type-safe API operations."
+                            description: "Request to retrieve database schema definitions for context."
                         },
                         "IAutoBeRealizeCollectorWriteApplication.IComplete": {
                             type: "object",
@@ -164,22 +164,22 @@ function process(ctx, props) {
                                 },
                                 plan: {
                                     type: "string",
-                                    description: "Collector implementation plan and strategy.\n\nMUST contain thorough analysis with these four mandatory sections:\n\n1. Database Schema Field Inventory - List ALL fields with exact names from\n   schema\n2. DTO Property Inventory - List ALL properties with types\n3. Field-by-Field Mapping Strategy - Explicit mapping table for every field\n4. Edge Cases and Special Handling - Nullable, arrays, conditionals\n\nThis forces you to READ the actual schema (not imagine it) and creates an\nexplicit specification that the draft must implement."
+                                    description: "Collector implementation plan. MUST contain four sections:\n\n1. Database Schema Field Inventory \u2014 ALL fields with exact names from schema\n2. DTO Property Inventory \u2014 ALL properties with types\n3. Field-by-Field Mapping Strategy \u2014 explicit mapping for every field\n4. Edge Cases and Special Handling \u2014 nullable, arrays, conditionals\n\nThis forces you to READ the actual schema (not imagine it) and creates an\nexplicit specification that the draft must implement."
                                 },
                                 mappings: {
                                     type: "array",
                                     items: {
                                         $ref: "#/components/schemas/AutoBeRealizeCollectorMapping"
                                     },
-                                    description: "Field-by-field mapping table for complete database coverage.\n\nMUST include EVERY field and relation from the database schema - no\nexceptions. Each mapping specifies:\n\n- `member`: Exact field/relation name from database schema\n- `kind`: Whether it's a scalar field, belongsTo, hasOne, or hasMany\n  relation\n- `nullable`: Whether the field/relation is nullable (true/false for\n  scalar/belongsTo, null for hasMany/hasOne)\n- `how`: How to obtain/generate the value for that field\n\nThe `kind` property forces explicit classification of each member BEFORE\ndeciding how to handle it, preventing common errors like treating\nbelongsTo relations as scalar fields.\n\nThe `nullable` property forces explicit identification of nullability\nconstraints BEFORE deciding handling strategy, preventing errors like\nassigning null to non-nullable fields or using null instead of undefined\nfor optional relations.\n\nMissing even a single field will cause validation failure and trigger\nregeneration.\n\nThis structured approach:\n\n- Prevents field omissions through systematic coverage\n- Forces explicit decision-making for each field (kind + nullable + how)\n- Prevents confusion between scalar fields and relations\n- Prevents null assignment errors through explicit nullability tracking\n- Enables validation before code generation\n- Creates clear documentation of field handling strategy\n\nThe validator will cross-check this list against the actual database\nschema and reject incomplete mappings."
+                                    description: "Field-by-field mapping for complete database coverage.\n\nMUST include EVERY field and relation from the database schema \u2014 no\nexceptions. Each mapping specifies:\n\n- `member`: Exact Prisma field/relation name \u2014 read from schema, NOT from\n  DTO property names or FK column names\n- `kind`: scalar, belongsTo, hasOne, or hasMany\n- `nullable`: true/false for scalar/belongsTo, null for hasMany/hasOne\n- `how`: How to obtain/generate the value for that field\n\nThe `kind` property forces explicit classification BEFORE deciding how to\nhandle it, preventing errors like treating belongsTo as scalar.\n\nMissing even a single field will cause validation failure."
                                 },
                                 draft: {
                                     type: "string",
-                                    description: "Initial collector implementation draft.\n\nComplete implementation that strictly follows the plan's mapping table.\nEVERY field in the plan's Section 3 mapping strategy MUST appear in this\ndraft. Implement:\n\n- Namespace with collect() function\n- All field mappings from plan (direct, connect, nested create)\n- Neighbor collector reuse (NEVER inline when collector exists)\n- UUID generation with v4(), proper Prisma CreateInput types"
+                                    description: "Complete implementation following plan's mapping table. EVERY field from\nplan Section 3 MUST appear. Implement:\n\n- Namespace with collect() function\n- All field mappings (direct, connect, nested create)\n- Neighbor collector reuse (NEVER inline when collector exists)\n- UUID generation with v4(), proper Prisma CreateInput types"
                                 },
                                 revise: {
                                     $ref: "#/components/schemas/IAutoBeRealizeCollectorWriteApplication.IReviseProps",
-                                    description: "Revision and finalization phase.\n\nReviews the draft implementation and produces the final code with all\nimprovements and corrections applied."
+                                    description: "Reviews draft and produces final code."
                                 }
                             },
                             required: [
@@ -189,14 +189,14 @@ function process(ctx, props) {
                                 "draft",
                                 "revise"
                             ],
-                            description: "Request to generate collector module implementation.\n\nExecutes three-phase generation to create complete collector with:\n\n- Collect() function: Converts DTO to database input\n- Proper handling of nested relationships\n- UUID generation for new records\n- Type-safe Prisma create/connect syntax\n\nFollows plan \u2192 draft \u2192 revise pattern to ensure type safety and correct\nrelationship handling."
+                            description: "Generate collector module via plan/draft/revise."
                         },
                         AutoBeRealizeCollectorMapping: {
                             type: "object",
                             properties: {
                                 member: {
                                     type: "string",
-                                    description: "Exact field or relation name from Prisma schema.\n\nMUST match the schema exactly (case-sensitive). Examples:\n\n- Scalar fields: \"id\", \"email\", \"created_at\"\n- BelongsTo relations: \"customer\", \"article\"\n- HasMany relations: \"comments\", \"shopping_sale_tags\"\n\nDO NOT use database column names (e.g., \"customer_id\" is WRONG - use\n\"customer\").\n\nInclude ALL fields from the schema, even if they are optional or not used\nin this particular collector."
+                                    description: "Exact field or relation name from Prisma schema (case-sensitive).\n\n**Examples**:\n\n```typescript\n// Scalar fields\n{ member: \"id\", kind: \"scalar\", nullable: false, how: \"Generate with v4()\" }\n{ member: \"email\", kind: \"scalar\", nullable: false, how: \"From props.body.email\" }\n{ member: \"created_at\", kind: \"scalar\", nullable: false, how: \"Default to new Date()\" }\n{ member: \"description\", kind: \"scalar\", nullable: true, how: \"From props.body.description ?? null\" }\n\n// BelongsTo relations \u2014 use Prisma RELATION name, NOT FK column name\n{ member: \"customer\", kind: \"belongsTo\", nullable: false, how: \"Connect using props.customer.id\" }\n{ member: \"parent\", kind: \"belongsTo\", nullable: true, how: \"Undefined (nullable FK)\" }\n\n// HasMany relations\n{ member: \"tags\", kind: \"hasMany\", nullable: null, how: \"Nested create with TagCollector\" }\n{ member: \"comments\", kind: \"hasMany\", nullable: null, how: \"Not needed (optional has-many)\" }\n```\n\nDO NOT use FK column names (e.g., \"customer_id\" is WRONG \u2014 use \"customer\").\nInclude ALL members even if unused in this collector."
                                 },
                                 kind: {
                                     oneOf: [
@@ -213,7 +213,7 @@ function process(ctx, props) {
                                             "const": "hasMany"
                                         }
                                     ],
-                                    description: "The kind of Prisma schema member.\n\nExplicitly identifies whether this member is a scalar field or a relation,\nand if it's a relation, what type of relation it is. This classification\nforces the AI to think through the nature of each member before planning\nhow to handle it, preventing common mistakes like treating belongsTo\nrelations as scalar fields.\n\n**Possible values**:\n\n- `\"scalar\"`: Regular database column (id, email, created_at, total_price,\n  etc.)\n- `\"belongsTo\"`: Foreign key relation pointing to parent entity (customer,\n  article, category, etc.)\n- `\"hasOne\"`: One-to-one relation where this side owns the relationship\n- `\"hasMany\"`: One-to-many or many-to-many relation (comments, tags, reviews,\n  etc.)\n\n**Why this matters**:\n\n- **Prevents confusion**: AI must consciously identify if \"customer\" is a\n  relation (needs `{ connect: { id: ... } }`) or a scalar field\n- **Forces correct syntax**: belongsTo requires `connect`, hasMany requires\n  `create`, scalar requires direct value assignment\n- **Enables Chain-of-Thought**: AI explicitly thinks about the kind before\n  deciding the handling strategy in the `how` field\n- **Catches common errors**: Prevents treating FK relations as scalar IDs\n\n**Examples by kind**:\n\n```typescript\n// Scalar fields\n{ member: \"id\", kind: \"scalar\", nullable: false, how: \"Generate with v4()\" }\n{ member: \"email\", kind: \"scalar\", nullable: false, how: \"From props.body.email\" }\n{ member: \"created_at\", kind: \"scalar\", nullable: false, how: \"Default to new Date()\" }\n{ member: \"description\", kind: \"scalar\", nullable: true, how: \"From props.body.description ?? null\" }\n\n// BelongsTo relations (FK pointing to parent)\n{ member: \"customer\", kind: \"belongsTo\", nullable: false, how: \"Connect using props.customer.id\" }\n{ member: \"article\", kind: \"belongsTo\", nullable: false, how: \"Connect using props.article.id\" }\n{ member: \"parent\", kind: \"belongsTo\", nullable: true, how: \"Undefined (nullable FK)\" }\n\n// HasMany relations (reverse side of FK)\n{ member: \"comments\", kind: \"hasMany\", nullable: null, how: \"Not needed (optional has-many)\" }\n{ member: \"tags\", kind: \"hasMany\", nullable: null, how: \"Nested create with TagCollector\" }\n{ member: \"reviews\", kind: \"hasMany\", nullable: null, how: \"Not applicable for this collector\" }\n```\n\nThe `kind` field works together with `nullable` and `how`: kind identifies\nWHAT it is, nullable identifies IF it's optional, how explains HOW to\nhandle it."
+                                    description: "Kind of Prisma schema member.\n\n- `\"scalar\"`: Regular column \u2192 direct value assignment\n- `\"belongsTo\"`: FK relation \u2192 `{ connect: { id } }`\n- `\"hasOne\"`: 1:1 relation this side owns\n- `\"hasMany\"`: 1:N or M:N \u2192 `{ create: [...] }` or omit\n\nThe kind forces explicit classification BEFORE deciding how to handle it,\npreventing confusion like treating belongsTo relations as scalar fields."
                                 },
                                 nullable: {
                                     oneOf: [
@@ -224,11 +224,11 @@ function process(ctx, props) {
                                             type: "boolean"
                                         }
                                     ],
-                                    description: "Whether this member is nullable in the Prisma schema.\n\nThis property explicitly documents whether a field/relation can be null,\nforcing the AI to understand nullability constraints before deciding how to\nhandle the member. This prevents errors like assigning null to non-nullable\nfields or forgetting to handle optional relations properly.\n\n**Value semantics by kind**:\n\n- **For scalar fields** (`kind: \"scalar\"`):\n\n  - `false`: Non-nullable column (e.g., `email String`, `id String`)\n\n      - Must always have a value\n      - Cannot use `null` or `undefined`\n      - Example: `email: props.body.email` (required)\n  - `true`: Nullable column (e.g., `description String?`, `deleted_at\n      DateTime?`)\n\n      - Can be null\n      - Use `?? null` pattern for optional DTO values\n      - Example: `description: props.body.description ?? null`\n- **For belongsTo relations** (`kind: \"belongsTo\"`):\n\n  - `false`: Required foreign key (e.g., `customer_id String`)\n\n      - Must always connect to parent entity\n      - Cannot use `undefined`\n      - Example: `customer: { connect: { id: props.customer.id } }`\n  - `true`: Optional foreign key (e.g., `parent_id String?`, `category_id\n      String?`)\n\n      - Can be omitted\n      - Use `undefined` (NOT `null`) when not provided\n      - Example: `parent: props.body.parentId ? { connect: { id:\n              props.body.parentId } } : undefined`\n- **For hasMany/hasOne relations** (`kind: \"hasMany\"` or `kind: \"hasOne\"`):\n\n  - Always `null`: Nullability concept doesn't apply to relation arrays/objects\n\n      - HasMany: Always optional (empty array or nested creates)\n      - HasOne: Handled differently (create or omit)\n      - The `nullable` property has no semantic meaning for these kinds\n\n**Why this matters**:\n\n- **Prevents null assignment errors**: Can't assign null to non-nullable\n  fields\n- **Forces correct optional handling**: nullable: true \u2192 use `?? null` or\n  `undefined`\n- **Catches required field omissions**: nullable: false \u2192 must provide value\n- **Enables proper FK handling**: nullable belongsTo \u2192 use `undefined` not\n  `null`\n- **Supports Chain-of-Thought**: AI must think about nullability BEFORE\n  deciding handling strategy\n\n**Examples**:\n\n```typescript\n// Non-nullable scalar (nullable: false)\n{ member: \"id\", kind: \"scalar\", nullable: false, how: \"Generate with v4()\" }\n{ member: \"email\", kind: \"scalar\", nullable: false, how: \"From props.body.email\" }\n{ member: \"created_at\", kind: \"scalar\", nullable: false, how: \"Default to new Date()\" }\n\n// Nullable scalar (nullable: true)\n{ member: \"description\", kind: \"scalar\", nullable: true, how: \"From props.body.description ?? null\" }\n{ member: \"deleted_at\", kind: \"scalar\", nullable: true, how: \"Default to null\" }\n{ member: \"completed_at\", kind: \"scalar\", nullable: true, how: \"From props.body.completedAt ?? null\" }\n\n// Required belongsTo (nullable: false)\n{ member: \"customer\", kind: \"belongsTo\", nullable: false, how: \"Connect using props.customer.id\" }\n{ member: \"article\", kind: \"belongsTo\", nullable: false, how: \"Connect using props.article.id\" }\n\n// Optional belongsTo (nullable: true)\n{ member: \"parent\", kind: \"belongsTo\", nullable: true, how: \"Undefined (nullable FK)\" }\n{ member: \"category\", kind: \"belongsTo\", nullable: true, how: \"Connect using props.body.categoryId or undefined\" }\n\n// HasMany relations (nullable: null - not applicable)\n{ member: \"comments\", kind: \"hasMany\", nullable: null, how: \"Not needed (optional has-many)\" }\n{ member: \"tags\", kind: \"hasMany\", nullable: null, how: \"Nested create with TagCollector\" }\n{ member: \"reviews\", kind: \"hasMany\", nullable: null, how: \"Not applicable for this collector\" }\n```\n\nThe `nullable` property works with `kind` to determine the correct Prisma\nsyntax: kind identifies WHAT it is, nullable identifies IF it's optional,\nhow explains HOW to handle it."
+                                    description: "Whether nullable in Prisma schema.\n\n- `false`: Non-nullable \u2014 must provide value\n- `true`: Nullable \u2014 use `?? null` for scalar, `undefined` for belongsTo\n- `null`: Not applicable (hasMany/hasOne)"
                                 },
                                 how: {
                                     type: "string",
-                                    description: "Brief one-line explanation of how to obtain this field's value.\n\nKeep it concise and clear.\n\n**For Write Phase** (planning field generation):\n\n- \"Generate with v4()\"\n- \"From props.body.email\"\n- \"Connect using props.references.customer_id\"\n- \"Nested create with ShoppingSaleTagCollector\"\n- \"Query comment to get article_id\"\n- \"Default to new Date()\"\n- \"Undefined (nullable FK)\"\n- \"Not applicable for this collector\"\n- \"Not needed (optional has-many)\"\n\n**For Correct Phase** (documenting current state and fixes):\n\n- \"No change needed - correct\"\n- \"Already correct\"\n- \"Fix: Wrong name 'user_email' \u2192 'email'\"\n- \"Fix: Missing field - add with props.body.email\"\n- \"Fix: Wrong type - change to connect syntax\"\n- \"Fix: Should use CustomerCollector instead of inline\"\n- \"Fix: Using null instead of undefined\"\n- \"Fix: Fabricated field - remove it\"\n\nEven if a field is correct or not used, you MUST include it in the mapping\nand explain why. This ensures complete schema coverage.\n\nThis is NOT code - just a simple description of the strategy."
+                                    description: "Brief strategy for obtaining this field's value (NOT code).\n\nWrite phase: \"Generate with v4()\", \"From props.body.email\", \"Connect using\nprops.customer.id\", \"Nested create with TagCollector\".\n\nCorrect phase: \"No change needed\", \"Fix: Wrong name 'x' \u2192 'y'\".\n\nEven if correct or unused, you MUST include it. This ensures complete\nschema coverage."
                                 }
                             },
                             required: [
@@ -237,14 +237,14 @@ function process(ctx, props) {
                                 "nullable",
                                 "how"
                             ],
-                            description: "Single field/relation mapping strategy for Prisma CreateInput generation.\n\nDocuments the handling strategy for one specific field or relation in the\nPrisma CreateInput. This structured approach ensures complete schema coverage\nby requiring explicit documentation for EVERY field - including those not\nused or not applicable.\n\n**Purpose**:\n\n- Prevents field omissions through systematic coverage verification\n- Forces explicit decision-making for each Prisma schema member\n- Enables validation before code generation (Write) or correction (Correct)\n- Creates clear documentation of field handling strategy\n\n**Usage Contexts**:\n\n- **Write Phase**: Plan how to generate each field from DTO \u2192 Prisma\n- **Correct Phase**: Document current state and correction plan for each field\n\nThe validator cross-checks mappings against the Prisma schema to ensure\nnothing is overlooked, rejecting incomplete mappings."
+                            description: "Field/relation mapping for Prisma CreateInput generation.\n\nDocuments handling strategy for ONE Prisma schema member. EVERY field and\nrelation must be listed \u2014 the validator rejects incomplete mappings."
                         },
                         "IAutoBeRealizeCollectorWriteApplication.IReviseProps": {
                             type: "object",
                             properties: {
                                 review: {
                                     type: "string",
-                                    description: "Critical review and improvement analysis.\n\nMUST systematically verify using four checklists:\n\n1. Schema Fidelity - Cross-check EVERY field name against plan Section 1\n   inventory\n2. Plan Adherence - Verify EVERY mapping from plan Section 3 is implemented\n3. System Rules - Mandatory neighbor reuse, props structure, satisfies type\n4. Type Safety - Compilation check, nullable handling, async/await\n\nIdentify specific issues with line numbers and provide clear reasoning.\nThis catches hallucinated fields, missing mappings, and rule violations."
+                                    description: "MUST systematically verify four checklists:\n\n1. Schema Fidelity \u2014 cross-check EVERY field name against plan Section 1\n2. Plan Adherence \u2014 verify EVERY mapping from Section 3 is implemented\n3. System Rules \u2014 neighbor reuse, props structure, satisfies type\n4. Type Safety \u2014 compilation check, nullable handling, async/await\n\nIdentify issues with line numbers. This catches hallucinated fields,\nmissing mappings, and rule violations."
                                 },
                                 final: {
                                     oneOf: [
@@ -255,7 +255,7 @@ function process(ctx, props) {
                                             type: "string"
                                         }
                                     ],
-                                    description: "Final collector code with all review improvements applied.\n\nApply ALL fixes identified in the review to produce production-ready\ncode. If review found issues, this MUST contain the corrected\nimplementation.\n\nReturn `null` ONLY if the draft is already perfect and review found zero\nissues."
+                                    description: "Final collector code with all review improvements applied, or null if\ndraft needs no changes."
                                 }
                             },
                             required: [
@@ -279,7 +279,7 @@ function process(ctx, props) {
                                 }
                             }
                         ],
-                        description: "Process collector generation task or preliminary data requests.\n\nGenerates complete collector module through three-phase workflow (plan \u2192\ndraft \u2192 revise). Ensures type safety, proper database input types, and\ncorrect relationship handling."
+                        description: "Process collector generation task or preliminary data requests."
                     }
                 ]
             },
@@ -507,11 +507,11 @@ function createController(ctx, props) {
                     type: "object",
                     properties: {
                         thinking: {
-                            description: "Think before you act.\n\nBefore requesting preliminary data or completing your task, reflect on\nyour current state and explain your reasoning:\n\nFor preliminary requests:\n\n- What database schemas are missing that you need?\n- Why do you need them for collector generation?\n- Be brief - state the gap, don't list everything you have.\n\nFor completion:\n\n- What schemas did you acquire?\n- What collector patterns did you implement?\n- Why is it sufficient to complete?\n- Summarize - don't enumerate every field mapping.\n\nNote: All necessary DTO type information is available transitively from\nthe DTO type names in the plan. You only need to request database\nschemas.\n\nThis reflection helps you avoid duplicate requests and premature\ncompletion.",
+                            description: "Think before you act.\n\nFor preliminary requests: what database schemas are missing and why?\n\nFor completion: what schemas did you acquire, what patterns did you\nimplement, and why is it sufficient? Summarize \u2014 don't enumerate every\nfield.\n\nNote: All DTO type information is available transitively from the plan's\nDTO type names. You only need to request database schemas.",
                             type: "string"
                         },
                         request: {
-                            description: "Type discriminator for the request.\n\nDetermines which action to perform:\n\n- \"getDatabaseSchemas\": Retrieve database table schemas for DB structure\n- \"complete\": Generate final collector implementation\n\nAll necessary DTO type information is obtained transitively from the DTO\ntype names provided in the plan (AutoBeRealizeCollectorPlan). Each DTO\ntype name allows the system to recursively fetch all referenced types,\nproviding complete type information without requiring explicit schema\nrequests.\n\nThe preliminary types are removed from the union after their respective\ndata has been provided, physically preventing repeated calls.",
+                            description: "Action to perform. Exhausted preliminary types are removed from the\nunion, physically preventing repeated calls.",
                             anyOf: [
                                 {
                                     $ref: "#/$defs/IAutoBePreliminaryGetDatabaseSchemas"
@@ -536,18 +536,18 @@ function createController(ctx, props) {
                     additionalProperties: false,
                     $defs: {
                         IAutoBePreliminaryGetDatabaseSchemas: {
-                            description: "Request to retrieve database schema definitions for context.\n\nThis type is used in the preliminary phase to request specific database table\nschemas needed for generating type-safe API operations.",
+                            description: "Request to retrieve database schema definitions for context.",
                             type: "object",
                             properties: {
                                 type: {
-                                    description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"getDatabaseSchemas\" indicates this is a preliminary\ndata request for database schemas.",
+                                    description: "Type discriminator.",
                                     type: "string",
                                     "enum": [
                                         "getDatabaseSchemas"
                                     ]
                                 },
                                 schemaNames: {
-                                    description: "List of database table names to retrieve.\n\nTable names from the database schema representing database entities (e.g.,\n\"user\", \"post\", \"comment\").\n\nCRITICAL: DO NOT request the same schema names that you have already\nrequested in previous calls.",
+                                    description: "Database table names to retrieve. DO NOT request same names already\nrequested in previous calls.",
                                     type: "array",
                                     items: {
                                         type: "string"
@@ -561,7 +561,7 @@ function createController(ctx, props) {
                             ]
                         },
                         "IAutoBeRealizeCollectorWriteApplication.IComplete": {
-                            description: "Request to generate collector module implementation.\n\nExecutes three-phase generation to create complete collector with:\n\n- Collect() function: Converts DTO to database input\n- Proper handling of nested relationships\n- UUID generation for new records\n- Type-safe Prisma create/connect syntax\n\nFollows plan \u2192 draft \u2192 revise pattern to ensure type safety and correct\nrelationship handling.",
+                            description: "Generate collector module via plan/draft/revise.",
                             type: "object",
                             properties: {
                                 type: {
@@ -572,22 +572,22 @@ function createController(ctx, props) {
                                     ]
                                 },
                                 plan: {
-                                    description: "Collector implementation plan and strategy.\n\nMUST contain thorough analysis with these four mandatory sections:\n\n1. Database Schema Field Inventory - List ALL fields with exact names from\n   schema\n2. DTO Property Inventory - List ALL properties with types\n3. Field-by-Field Mapping Strategy - Explicit mapping table for every field\n4. Edge Cases and Special Handling - Nullable, arrays, conditionals\n\nThis forces you to READ the actual schema (not imagine it) and creates an\nexplicit specification that the draft must implement.",
+                                    description: "Collector implementation plan. MUST contain four sections:\n\n1. Database Schema Field Inventory \u2014 ALL fields with exact names from schema\n2. DTO Property Inventory \u2014 ALL properties with types\n3. Field-by-Field Mapping Strategy \u2014 explicit mapping for every field\n4. Edge Cases and Special Handling \u2014 nullable, arrays, conditionals\n\nThis forces you to READ the actual schema (not imagine it) and creates an\nexplicit specification that the draft must implement.",
                                     type: "string"
                                 },
                                 mappings: {
-                                    description: "Field-by-field mapping table for complete database coverage.\n\nMUST include EVERY field and relation from the database schema - no\nexceptions. Each mapping specifies:\n\n- `member`: Exact field/relation name from database schema\n- `kind`: Whether it's a scalar field, belongsTo, hasOne, or hasMany\n  relation\n- `nullable`: Whether the field/relation is nullable (true/false for\n  scalar/belongsTo, null for hasMany/hasOne)\n- `how`: How to obtain/generate the value for that field\n\nThe `kind` property forces explicit classification of each member BEFORE\ndeciding how to handle it, preventing common errors like treating\nbelongsTo relations as scalar fields.\n\nThe `nullable` property forces explicit identification of nullability\nconstraints BEFORE deciding handling strategy, preventing errors like\nassigning null to non-nullable fields or using null instead of undefined\nfor optional relations.\n\nMissing even a single field will cause validation failure and trigger\nregeneration.\n\nThis structured approach:\n\n- Prevents field omissions through systematic coverage\n- Forces explicit decision-making for each field (kind + nullable + how)\n- Prevents confusion between scalar fields and relations\n- Prevents null assignment errors through explicit nullability tracking\n- Enables validation before code generation\n- Creates clear documentation of field handling strategy\n\nThe validator will cross-check this list against the actual database\nschema and reject incomplete mappings.",
+                                    description: "Field-by-field mapping for complete database coverage.\n\nMUST include EVERY field and relation from the database schema \u2014 no\nexceptions. Each mapping specifies:\n\n- `member`: Exact Prisma field/relation name \u2014 read from schema, NOT from\n  DTO property names or FK column names\n- `kind`: scalar, belongsTo, hasOne, or hasMany\n- `nullable`: true/false for scalar/belongsTo, null for hasMany/hasOne\n- `how`: How to obtain/generate the value for that field\n\nThe `kind` property forces explicit classification BEFORE deciding how to\nhandle it, preventing errors like treating belongsTo as scalar.\n\nMissing even a single field will cause validation failure.",
                                     type: "array",
                                     items: {
                                         $ref: "#/$defs/AutoBeRealizeCollectorMapping"
                                     }
                                 },
                                 draft: {
-                                    description: "Initial collector implementation draft.\n\nComplete implementation that strictly follows the plan's mapping table.\nEVERY field in the plan's Section 3 mapping strategy MUST appear in this\ndraft. Implement:\n\n- Namespace with collect() function\n- All field mappings from plan (direct, connect, nested create)\n- Neighbor collector reuse (NEVER inline when collector exists)\n- UUID generation with v4(), proper Prisma CreateInput types",
+                                    description: "Complete implementation following plan's mapping table. EVERY field from\nplan Section 3 MUST appear. Implement:\n\n- Namespace with collect() function\n- All field mappings (direct, connect, nested create)\n- Neighbor collector reuse (NEVER inline when collector exists)\n- UUID generation with v4(), proper Prisma CreateInput types",
                                     type: "string"
                                 },
                                 revise: {
-                                    description: "Revision and finalization phase.\n\nReviews the draft implementation and produces the final code with all\nimprovements and corrections applied.",
+                                    description: "Reviews draft and produces final code.",
                                     $ref: "#/$defs/IAutoBeRealizeCollectorWriteApplication.IReviseProps"
                                 }
                             },
@@ -600,15 +600,15 @@ function createController(ctx, props) {
                             ]
                         },
                         AutoBeRealizeCollectorMapping: {
-                            description: "Single field/relation mapping strategy for Prisma CreateInput generation.\n\nDocuments the handling strategy for one specific field or relation in the\nPrisma CreateInput. This structured approach ensures complete schema coverage\nby requiring explicit documentation for EVERY field - including those not\nused or not applicable.\n\n**Purpose**:\n\n- Prevents field omissions through systematic coverage verification\n- Forces explicit decision-making for each Prisma schema member\n- Enables validation before code generation (Write) or correction (Correct)\n- Creates clear documentation of field handling strategy\n\n**Usage Contexts**:\n\n- **Write Phase**: Plan how to generate each field from DTO \u2192 Prisma\n- **Correct Phase**: Document current state and correction plan for each field\n\nThe validator cross-checks mappings against the Prisma schema to ensure\nnothing is overlooked, rejecting incomplete mappings.",
+                            description: "Field/relation mapping for Prisma CreateInput generation.\n\nDocuments handling strategy for ONE Prisma schema member. EVERY field and\nrelation must be listed \u2014 the validator rejects incomplete mappings.",
                             type: "object",
                             properties: {
                                 member: {
-                                    description: "Exact field or relation name from Prisma schema.\n\nMUST match the schema exactly (case-sensitive). Examples:\n\n- Scalar fields: \"id\", \"email\", \"created_at\"\n- BelongsTo relations: \"customer\", \"article\"\n- HasMany relations: \"comments\", \"shopping_sale_tags\"\n\nDO NOT use database column names (e.g., \"customer_id\" is WRONG - use\n\"customer\").\n\nInclude ALL fields from the schema, even if they are optional or not used\nin this particular collector.",
+                                    description: "Exact field or relation name from Prisma schema (case-sensitive).\n\n**Examples**:\n\n```typescript\n// Scalar fields\n{ member: \"id\", kind: \"scalar\", nullable: false, how: \"Generate with v4()\" }\n{ member: \"email\", kind: \"scalar\", nullable: false, how: \"From props.body.email\" }\n{ member: \"created_at\", kind: \"scalar\", nullable: false, how: \"Default to new Date()\" }\n{ member: \"description\", kind: \"scalar\", nullable: true, how: \"From props.body.description ?? null\" }\n\n// BelongsTo relations \u2014 use Prisma RELATION name, NOT FK column name\n{ member: \"customer\", kind: \"belongsTo\", nullable: false, how: \"Connect using props.customer.id\" }\n{ member: \"parent\", kind: \"belongsTo\", nullable: true, how: \"Undefined (nullable FK)\" }\n\n// HasMany relations\n{ member: \"tags\", kind: \"hasMany\", nullable: null, how: \"Nested create with TagCollector\" }\n{ member: \"comments\", kind: \"hasMany\", nullable: null, how: \"Not needed (optional has-many)\" }\n```\n\nDO NOT use FK column names (e.g., \"customer_id\" is WRONG \u2014 use \"customer\").\nInclude ALL members even if unused in this collector.",
                                     type: "string"
                                 },
                                 kind: {
-                                    description: "The kind of Prisma schema member.\n\nExplicitly identifies whether this member is a scalar field or a relation,\nand if it's a relation, what type of relation it is. This classification\nforces the AI to think through the nature of each member before planning\nhow to handle it, preventing common mistakes like treating belongsTo\nrelations as scalar fields.\n\n**Possible values**:\n\n- `\"scalar\"`: Regular database column (id, email, created_at, total_price,\n  etc.)\n- `\"belongsTo\"`: Foreign key relation pointing to parent entity (customer,\n  article, category, etc.)\n- `\"hasOne\"`: One-to-one relation where this side owns the relationship\n- `\"hasMany\"`: One-to-many or many-to-many relation (comments, tags, reviews,\n  etc.)\n\n**Why this matters**:\n\n- **Prevents confusion**: AI must consciously identify if \"customer\" is a\n  relation (needs `{ connect: { id: ... } }`) or a scalar field\n- **Forces correct syntax**: belongsTo requires `connect`, hasMany requires\n  `create`, scalar requires direct value assignment\n- **Enables Chain-of-Thought**: AI explicitly thinks about the kind before\n  deciding the handling strategy in the `how` field\n- **Catches common errors**: Prevents treating FK relations as scalar IDs\n\n**Examples by kind**:\n\n```typescript\n// Scalar fields\n{ member: \"id\", kind: \"scalar\", nullable: false, how: \"Generate with v4()\" }\n{ member: \"email\", kind: \"scalar\", nullable: false, how: \"From props.body.email\" }\n{ member: \"created_at\", kind: \"scalar\", nullable: false, how: \"Default to new Date()\" }\n{ member: \"description\", kind: \"scalar\", nullable: true, how: \"From props.body.description ?? null\" }\n\n// BelongsTo relations (FK pointing to parent)\n{ member: \"customer\", kind: \"belongsTo\", nullable: false, how: \"Connect using props.customer.id\" }\n{ member: \"article\", kind: \"belongsTo\", nullable: false, how: \"Connect using props.article.id\" }\n{ member: \"parent\", kind: \"belongsTo\", nullable: true, how: \"Undefined (nullable FK)\" }\n\n// HasMany relations (reverse side of FK)\n{ member: \"comments\", kind: \"hasMany\", nullable: null, how: \"Not needed (optional has-many)\" }\n{ member: \"tags\", kind: \"hasMany\", nullable: null, how: \"Nested create with TagCollector\" }\n{ member: \"reviews\", kind: \"hasMany\", nullable: null, how: \"Not applicable for this collector\" }\n```\n\nThe `kind` field works together with `nullable` and `how`: kind identifies\nWHAT it is, nullable identifies IF it's optional, how explains HOW to\nhandle it.",
+                                    description: "Kind of Prisma schema member.\n\n- `\"scalar\"`: Regular column \u2192 direct value assignment\n- `\"belongsTo\"`: FK relation \u2192 `{ connect: { id } }`\n- `\"hasOne\"`: 1:1 relation this side owns\n- `\"hasMany\"`: 1:N or M:N \u2192 `{ create: [...] }` or omit\n\nThe kind forces explicit classification BEFORE deciding how to handle it,\npreventing confusion like treating belongsTo relations as scalar fields.",
                                     type: "string",
                                     "enum": [
                                         "scalar",
@@ -618,7 +618,7 @@ function createController(ctx, props) {
                                     ]
                                 },
                                 nullable: {
-                                    description: "Whether this member is nullable in the Prisma schema.\n\nThis property explicitly documents whether a field/relation can be null,\nforcing the AI to understand nullability constraints before deciding how to\nhandle the member. This prevents errors like assigning null to non-nullable\nfields or forgetting to handle optional relations properly.\n\n**Value semantics by kind**:\n\n- **For scalar fields** (`kind: \"scalar\"`):\n\n  - `false`: Non-nullable column (e.g., `email String`, `id String`)\n\n      - Must always have a value\n      - Cannot use `null` or `undefined`\n      - Example: `email: props.body.email` (required)\n  - `true`: Nullable column (e.g., `description String?`, `deleted_at\n      DateTime?`)\n\n      - Can be null\n      - Use `?? null` pattern for optional DTO values\n      - Example: `description: props.body.description ?? null`\n- **For belongsTo relations** (`kind: \"belongsTo\"`):\n\n  - `false`: Required foreign key (e.g., `customer_id String`)\n\n      - Must always connect to parent entity\n      - Cannot use `undefined`\n      - Example: `customer: { connect: { id: props.customer.id } }`\n  - `true`: Optional foreign key (e.g., `parent_id String?`, `category_id\n      String?`)\n\n      - Can be omitted\n      - Use `undefined` (NOT `null`) when not provided\n      - Example: `parent: props.body.parentId ? { connect: { id:\n              props.body.parentId } } : undefined`\n- **For hasMany/hasOne relations** (`kind: \"hasMany\"` or `kind: \"hasOne\"`):\n\n  - Always `null`: Nullability concept doesn't apply to relation arrays/objects\n\n      - HasMany: Always optional (empty array or nested creates)\n      - HasOne: Handled differently (create or omit)\n      - The `nullable` property has no semantic meaning for these kinds\n\n**Why this matters**:\n\n- **Prevents null assignment errors**: Can't assign null to non-nullable\n  fields\n- **Forces correct optional handling**: nullable: true \u2192 use `?? null` or\n  `undefined`\n- **Catches required field omissions**: nullable: false \u2192 must provide value\n- **Enables proper FK handling**: nullable belongsTo \u2192 use `undefined` not\n  `null`\n- **Supports Chain-of-Thought**: AI must think about nullability BEFORE\n  deciding handling strategy\n\n**Examples**:\n\n```typescript\n// Non-nullable scalar (nullable: false)\n{ member: \"id\", kind: \"scalar\", nullable: false, how: \"Generate with v4()\" }\n{ member: \"email\", kind: \"scalar\", nullable: false, how: \"From props.body.email\" }\n{ member: \"created_at\", kind: \"scalar\", nullable: false, how: \"Default to new Date()\" }\n\n// Nullable scalar (nullable: true)\n{ member: \"description\", kind: \"scalar\", nullable: true, how: \"From props.body.description ?? null\" }\n{ member: \"deleted_at\", kind: \"scalar\", nullable: true, how: \"Default to null\" }\n{ member: \"completed_at\", kind: \"scalar\", nullable: true, how: \"From props.body.completedAt ?? null\" }\n\n// Required belongsTo (nullable: false)\n{ member: \"customer\", kind: \"belongsTo\", nullable: false, how: \"Connect using props.customer.id\" }\n{ member: \"article\", kind: \"belongsTo\", nullable: false, how: \"Connect using props.article.id\" }\n\n// Optional belongsTo (nullable: true)\n{ member: \"parent\", kind: \"belongsTo\", nullable: true, how: \"Undefined (nullable FK)\" }\n{ member: \"category\", kind: \"belongsTo\", nullable: true, how: \"Connect using props.body.categoryId or undefined\" }\n\n// HasMany relations (nullable: null - not applicable)\n{ member: \"comments\", kind: \"hasMany\", nullable: null, how: \"Not needed (optional has-many)\" }\n{ member: \"tags\", kind: \"hasMany\", nullable: null, how: \"Nested create with TagCollector\" }\n{ member: \"reviews\", kind: \"hasMany\", nullable: null, how: \"Not applicable for this collector\" }\n```\n\nThe `nullable` property works with `kind` to determine the correct Prisma\nsyntax: kind identifies WHAT it is, nullable identifies IF it's optional,\nhow explains HOW to handle it.",
+                                    description: "Whether nullable in Prisma schema.\n\n- `false`: Non-nullable \u2014 must provide value\n- `true`: Nullable \u2014 use `?? null` for scalar, `undefined` for belongsTo\n- `null`: Not applicable (hasMany/hasOne)",
                                     anyOf: [
                                         {
                                             type: "null"
@@ -629,7 +629,7 @@ function createController(ctx, props) {
                                     ]
                                 },
                                 how: {
-                                    description: "Brief one-line explanation of how to obtain this field's value.\n\nKeep it concise and clear.\n\n**For Write Phase** (planning field generation):\n\n- \"Generate with v4()\"\n- \"From props.body.email\"\n- \"Connect using props.references.customer_id\"\n- \"Nested create with ShoppingSaleTagCollector\"\n- \"Query comment to get article_id\"\n- \"Default to new Date()\"\n- \"Undefined (nullable FK)\"\n- \"Not applicable for this collector\"\n- \"Not needed (optional has-many)\"\n\n**For Correct Phase** (documenting current state and fixes):\n\n- \"No change needed - correct\"\n- \"Already correct\"\n- \"Fix: Wrong name 'user_email' \u2192 'email'\"\n- \"Fix: Missing field - add with props.body.email\"\n- \"Fix: Wrong type - change to connect syntax\"\n- \"Fix: Should use CustomerCollector instead of inline\"\n- \"Fix: Using null instead of undefined\"\n- \"Fix: Fabricated field - remove it\"\n\nEven if a field is correct or not used, you MUST include it in the mapping\nand explain why. This ensures complete schema coverage.\n\nThis is NOT code - just a simple description of the strategy.",
+                                    description: "Brief strategy for obtaining this field's value (NOT code).\n\nWrite phase: \"Generate with v4()\", \"From props.body.email\", \"Connect using\nprops.customer.id\", \"Nested create with TagCollector\".\n\nCorrect phase: \"No change needed\", \"Fix: Wrong name 'x' \u2192 'y'\".\n\nEven if correct or unused, you MUST include it. This ensures complete\nschema coverage.",
                                     type: "string"
                                 }
                             },
@@ -644,11 +644,11 @@ function createController(ctx, props) {
                             type: "object",
                             properties: {
                                 review: {
-                                    description: "Critical review and improvement analysis.\n\nMUST systematically verify using four checklists:\n\n1. Schema Fidelity - Cross-check EVERY field name against plan Section 1\n   inventory\n2. Plan Adherence - Verify EVERY mapping from plan Section 3 is implemented\n3. System Rules - Mandatory neighbor reuse, props structure, satisfies type\n4. Type Safety - Compilation check, nullable handling, async/await\n\nIdentify specific issues with line numbers and provide clear reasoning.\nThis catches hallucinated fields, missing mappings, and rule violations.",
+                                    description: "MUST systematically verify four checklists:\n\n1. Schema Fidelity \u2014 cross-check EVERY field name against plan Section 1\n2. Plan Adherence \u2014 verify EVERY mapping from Section 3 is implemented\n3. System Rules \u2014 neighbor reuse, props structure, satisfies type\n4. Type Safety \u2014 compilation check, nullable handling, async/await\n\nIdentify issues with line numbers. This catches hallucinated fields,\nmissing mappings, and rule violations.",
                                     type: "string"
                                 },
                                 final: {
-                                    description: "Final collector code with all review improvements applied.\n\nApply ALL fixes identified in the review to produce production-ready\ncode. If review found issues, this MUST contain the corrected\nimplementation.\n\nReturn `null` ONLY if the draft is already perfect and review found zero\nissues.",
+                                    description: "Final collector code with all review improvements applied, or null if\ndraft needs no changes.",
                                     anyOf: [
                                         {
                                             type: "null"
@@ -666,7 +666,7 @@ function createController(ctx, props) {
                         }
                     }
                 },
-                description: "Process collector generation task or preliminary data requests.\n\nGenerates complete collector module through three-phase workflow (plan \u2192\ndraft \u2192 revise). Ensures type safety, proper database input types, and\ncorrect relationship handling.",
+                description: "Process collector generation task or preliminary data requests.",
                 validate: (() => { const _io0 = input => "string" === typeof input.thinking && ("object" === typeof input.request && null !== input.request && _iu0(input.request)); const _io1 = input => "getDatabaseSchemas" === input.type && (Array.isArray(input.schemaNames) && (1 <= input.schemaNames.length && input.schemaNames.every(elem => "string" === typeof elem))); const _io2 = input => "complete" === input.type && "string" === typeof input.plan && (Array.isArray(input.mappings) && input.mappings.every(elem => "object" === typeof elem && null !== elem && _io3(elem))) && "string" === typeof input.draft && ("object" === typeof input.revise && null !== input.revise && _io4(input.revise)); const _io3 = input => "string" === typeof input.member && ("scalar" === input.kind || "belongsTo" === input.kind || "hasOne" === input.kind || "hasMany" === input.kind) && (null === input.nullable || "boolean" === typeof input.nullable) && "string" === typeof input.how; const _io4 = input => "string" === typeof input.review && (null === input.final || "string" === typeof input.final); const _iu0 = input => (() => {
                     if ("getDatabaseSchemas" === input.type)
                         return _io1(input);