@autobe/agent 0.30.4 → 0.30.5

package/lib/orchestrate/realize/orchestrateRealizeTransformerWrite.js

@@ -105,7 +105,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 transformer 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 transformer 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: [
@@ -123,7 +123,7 @@ function process(ctx, props) {
                                             complete: "#/components/schemas/IAutoBeRealizeTransformerWriteApplication.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 transformer implementation\n\nAll necessary DTO type information is obtained transitively from the DTO\ntype names provided in the plan (AutoBeRealizeTransformerPlan). 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: [
@@ -136,7 +136,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",
@@ -144,14 +144,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."
                         },
                         "IAutoBeRealizeTransformerWriteApplication.IComplete": {
                             type: "object",
@@ -162,29 +162,29 @@ function process(ctx, props) {
                                 },
                                 plan: {
                                     type: "string",
-                                    description: "Transformer 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 table for BOTH select() and\n   transform()\n4. Edge Cases and Special Handling - Type casts (Decimal, DateTime),\n   nullables\n\nThis forces you to READ the actual schema (not imagine it) and creates an\nexplicit specification for both select() and transform() functions."
+                                    description: "Transformer 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 table for BOTH select() and\n   transform()\n4. Edge Cases and Special Handling \u2014 type casts (Decimal, DateTime),\n   nullables\n\nThis forces you to READ the actual schema (not imagine it) and creates an\nexplicit specification for both select() and transform() functions."
                                 },
                                 selectMappings: {
                                     type: "array",
                                     items: {
                                         $ref: "#/components/schemas/AutoBeRealizeTransformerSelectMapping"
                                     },
-                                    description: "Database field-by-field selection mapping for the select() function.\n\nDocuments which database fields/relations must be selected from the\ndatabase to enable the transform() function. This ensures no required\ndata is missing from the query.\n\nMUST include EVERY database field needed by transform() - no exceptions.\nEach mapping specifies:\n\n- `member`: Exact database field/relation name (snake_case)\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`: Why this field is being selected (which DTO property needs it)\n\nThe `kind` property forces explicit classification of each member BEFORE\ndeciding what to select, preventing confusion between scalars and\nrelations, and ensuring correct select syntax.\n\nThe `nullable` property documents schema constraints that affect how\ntransform() will handle the data, enabling proper null handling in\ntransformations.\n\nMissing even a single required field will cause validation failure and\ntrigger regeneration.\n\nThis structured approach:\n\n- Prevents missing field selections through systematic coverage\n- Forces explicit decision-making for each database field (kind + nullable\n\n  - How)\n- Ensures select() and transform() are perfectly aligned\n- Documents what data to load from database\n- Prevents confusion between scalar fields and relations\n- Documents nullability constraints for transform() planning\n- Enables validation before code generation\n\n**Common selection patterns by kind**:\n\n- **Scalar fields (nullable: true/false)**: For direct mapping or type\n  conversion\n- **Computation sources (nullable: true/false)**: Fields needed for\n  computed DTO properties\n- **Aggregations (nullable: false)**: _count, _sum, _avg for DTO statistics\n- **BelongsTo relations (nullable: true/false)**: For nested object\n  transformers\n- **HasMany relations (nullable: null)**: For array transformers\n\nThe validator will cross-check this list against the database schema and\nDTO requirements to ensure complete coverage."
+                                    description: "Database field-by-field selection mapping for select().\n\nMUST include EVERY database field needed by transform() \u2014 no exceptions.\nEach mapping specifies:\n\n- `member`: Exact Prisma field/relation name (snake_case) \u2014 read from the\n  Relation Mapping Table and member list, NOT from DTO property names\n- `kind`: scalar, belongsTo, hasOne, or hasMany\n- `nullable`: true/false for scalar/belongsTo, null for hasMany/hasOne\n- `how`: Which DTO property needs it\n\nThe `kind` property forces explicit classification of each member BEFORE\ndeciding select syntax, preventing confusion between scalars and\nrelations.\n\nMissing even a single required field will cause validation failure."
                                 },
                                 transformMappings: {
                                     type: "array",
                                     items: {
                                         $ref: "#/components/schemas/AutoBeRealizeTransformerTransformMapping"
                                     },
-                                    description: "DTO property-by-property transformation mapping for the transform()\nfunction.\n\nDocuments how to transform database payload data into each DTO property.\nThis ensures complete DTO coverage and correct transformation logic.\n\nMUST include EVERY property from the DTO type definition - no exceptions.\nEach mapping specifies:\n\n- `property`: Exact DTO property name (camelCase)\n- `how`: How to obtain this property value from Prisma payload\n\nMissing even a single property will cause validation failure and trigger\nregeneration.\n\nThis structured approach:\n\n- Prevents property omissions through systematic coverage\n- Forces explicit decision-making for each property transformation\n- Documents transformation logic (direct mapping, type conversion,\n  computation, nested transformation)\n- Ensures select() and transform() are aligned\n- Enables validation before code generation\n\n**Common transformation patterns**:\n\n- **Direct mapping**: Simple field renaming (snake_case \u2192 camelCase)\n- **Type conversion**: Decimal \u2192 Number, DateTime \u2192 ISO string\n- **Nullable handling**: DateTime? \u2192 string | null\n- **Computed properties**: Calculate from multiple database fields\n- **Aggregation**: Use _count, _sum, _avg from database\n- **Nested objects**: Reuse neighbor transformers\n- **Arrays**: Map with ArrayUtil.asyncMap + neighbor transformer\n\nThe validator will cross-check this list against the actual DTO type\ndefinition and reject incomplete mappings."
+                                    description: "DTO property-by-property transformation mapping for transform().\n\nMUST include EVERY property from the DTO type definition \u2014 no exceptions.\nEach mapping specifies:\n\n- `property`: Exact DTO property name (camelCase)\n- `how`: How to obtain from Prisma payload\n\n**Common transformation patterns**:\n\n- Direct mapping: snake_case \u2192 camelCase\n- Type conversion: Decimal \u2192 Number, DateTime \u2192 ISO string\n- Nullable: DateTime? \u2192 string | null\n- Nested objects: Reuse neighbor transformers\n- Arrays: ArrayUtil.asyncMap + neighbor transformer\n\nMissing even a single property will cause validation failure."
                                 },
                                 draft: {
                                     type: "string",
-                                    description: "Initial transformer implementation draft.\n\nComplete implementation that strictly follows the plan's mapping table.\nEVERY field in the plan's Section 3 MUST appear in BOTH select() and\ntransform(). Implement:\n\n- Transform() first, select() second, Payload last (correct order)\n- All field mappings from plan with correct transformations\n- Neighbor transformer reuse (NEVER inline when transformer exists)\n- ALWAYS use `select`, NEVER use `include`"
+                                    description: "Complete implementation following plan's mapping table. EVERY field from\nplan Section 3 MUST appear in BOTH select() and transform(). Implement:\n\n- Transform() first, select() second, Payload last (correct order)\n- All field mappings from plan with correct transformations\n- Neighbor transformer reuse (NEVER inline when transformer exists)\n- ALWAYS use `select`, NEVER use `include`"
                                 },
                                 revise: {
                                     $ref: "#/components/schemas/IAutoBeRealizeTransformerWriteApplication.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: [
@@ -195,14 +195,14 @@ function process(ctx, props) {
                                 "draft",
                                 "revise"
                             ],
-                            description: "Request to generate transformer module implementation.\n\nExecutes three-phase generation to create complete transformer with:\n\n- `select()` function: Returns Prisma include/select specification\n- `transform()` function: Converts Prisma payload to DTO\n\nFollows plan \u2192 draft \u2192 revise pattern to ensure type safety and correct\nfield mappings.\n\nNote: The database schema name is provided as input from the planning\nphase, so it doesn't need to be returned in the response."
+                            description: "Generate transformer module (select + transform functions) via\nplan/draft/revise."
                         },
                         AutoBeRealizeTransformerSelectMapping: {
                             type: "object",
                             properties: {
                                 member: {
                                     type: "string",
-                                    description: "Exact Prisma field or relation name from the Prisma schema.\n\nMUST match the Prisma schema exactly (case-sensitive). Use snake_case as\nPrisma follows database conventions.\n\n**Field Types**:\n\n- **Scalar fields**: Database columns (id, email, created_at, unit_price,\n  etc.)\n- **BelongsTo relations**: Foreign key relations (customer, article,\n  category, etc.)\n- **HasMany relations**: One-to-many arrays (tags, comments, reviews, etc.)\n- **Aggregations**: Prisma computed fields (_count, _sum, _avg, etc.)\n\n**Examples**:\n\n```typescript\n// Scalar fields for direct mapping or conversion\n{ member: \"id\", kind: \"scalar\", nullable: false, how: \"For DTO.id\" }\n{ member: \"email\", kind: \"scalar\", nullable: false, how: \"For DTO.email\" }\n{ member: \"created_at\", kind: \"scalar\", nullable: false, how: \"For DTO.createdAt (needs .toISOString())\" }\n{ member: \"unit_price\", kind: \"scalar\", nullable: false, how: \"For DTO.price (Decimal \u2192 Number)\" }\n{ member: \"deleted_at\", kind: \"scalar\", nullable: true, how: \"For DTO.deletedAt (nullable DateTime)\" }\n\n// Scalar fields for computation\n{ member: \"quantity\", kind: \"scalar\", nullable: false, how: \"For DTO.totalPrice computation\" }\n{ member: \"expiry_date\", kind: \"scalar\", nullable: false, how: \"For DTO.isExpired computation\" }\n\n// Aggregations (special scalar type)\n{ member: \"_count\", kind: \"scalar\", nullable: false, how: \"For DTO.reviewCount\" }\n\n// BelongsTo relations (nested objects)\n{ member: \"customer\", kind: \"belongsTo\", nullable: false, how: \"For DTO.customer (nested transformer)\" }\n{ member: \"article\", kind: \"belongsTo\", nullable: false, how: \"For DTO.article (nested transformer)\" }\n{ member: \"parent\", kind: \"belongsTo\", nullable: true, how: \"For DTO.parent (optional nested)\" }\n\n// HasMany relations (arrays)\n{ member: \"tags\", kind: \"hasMany\", nullable: null, how: \"For DTO.tags (array transformer)\" }\n{ member: \"comments\", kind: \"hasMany\", nullable: null, how: \"For DTO.comments (array transformer)\" }\n```\n\nDO NOT use DTO property names here - this is about Prisma schema members,\nnot DTO properties."
+                                    description: "Exact Prisma field or relation name from the Prisma schema.\n\nMUST match the Prisma schema exactly (case-sensitive, snake_case).\n\n**Field Types**:\n\n- **Scalar fields**: Database columns (id, email, created_at, unit_price)\n- **BelongsTo relations**: FK relations (customer, article, category)\n- **HasMany relations**: 1:N arrays (tags, comments, reviews)\n- **Aggregations**: Prisma computed fields (_count, _sum, _avg)\n\n**Examples**:\n\n```typescript\n// Scalar fields\n{ member: \"id\", kind: \"scalar\", nullable: false, how: \"For DTO.id\" }\n{ member: \"created_at\", kind: \"scalar\", nullable: false, how: \"For DTO.createdAt (needs .toISOString())\" }\n{ member: \"unit_price\", kind: \"scalar\", nullable: false, how: \"For DTO.price (Decimal \u2192 Number)\" }\n{ member: \"deleted_at\", kind: \"scalar\", nullable: true, how: \"For DTO.deletedAt (nullable DateTime)\" }\n\n// BelongsTo relations \u2014 member is ALWAYS the Prisma relation name,\n// which may differ from the DTO property name\n{ member: \"customer\", kind: \"belongsTo\", nullable: false, how: \"For DTO.buyer (nested transformer)\" }\n{ member: \"user\", kind: \"belongsTo\", nullable: true, how: \"For DTO.voter (optional nested)\" }\n\n// HasMany relations\n{ member: \"tags\", kind: \"hasMany\", nullable: null, how: \"For DTO.tags (array transformer)\" }\n```\n\nDO NOT use DTO property names \u2014 this is about Prisma schema members. Read\nthe Relation Mapping Table and member list to find correct names."
                                 },
                                 kind: {
                                     oneOf: [
@@ -219,7 +219,7 @@ function process(ctx, props) {
                                             "const": "hasMany"
                                         }
                                     ],
-                                    description: "The kind of Prisma schema member being selected.\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\nwhat to select, preventing common mistakes in the select() function.\n\n**Possible values**:\n\n- `\"scalar\"`: Regular database column (id, email, created_at, unit_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 for select()**:\n\n- **Prevents confusion**: AI must consciously identify if \"customer\" is a\n  scalar or belongsTo relation\n- **Forces correct select syntax**: belongsTo/hasMany require nested select\n  objects, scalar requires `true`\n- **Enables Chain-of-Thought**: AI explicitly thinks about the kind before\n  deciding selection strategy\n- **Supports proper data loading**: Different kinds require different\n  selection approaches\n\n**Examples by kind**:\n\n```typescript\n// Scalar fields - simple selection\n{ member: \"id\", kind: \"scalar\", nullable: false, how: \"For DTO.id\" }\n{ member: \"email\", kind: \"scalar\", nullable: false, how: \"For DTO.email\" }\n{ member: \"created_at\", kind: \"scalar\", nullable: false, how: \"For DTO.createdAt\" }\n{ member: \"deleted_at\", kind: \"scalar\", nullable: true, how: \"For DTO.deletedAt\" }\n\n// BelongsTo relations - nested selection with transformer\n{ member: \"customer\", kind: \"belongsTo\", nullable: false, how: \"For DTO.customer (nested)\" }\n{ member: \"article\", kind: \"belongsTo\", nullable: false, how: \"For DTO.article (nested)\" }\n{ member: \"parent\", kind: \"belongsTo\", nullable: true, how: \"For DTO.parent (optional)\" }\n\n// HasMany relations - nested selection with array transformer\n{ member: \"tags\", kind: \"hasMany\", nullable: null, how: \"For DTO.tags (array)\" }\n{ member: \"comments\", kind: \"hasMany\", nullable: null, how: \"For DTO.comments (array)\" }\n```\n\nThe `kind` field works together with `nullable` and `how`: kind identifies\nWHAT it is, nullable identifies IF it's optional, how explains WHY we're\nselecting it."
+                                    description: "Kind of Prisma schema member.\n\n- `\"scalar\"`: Regular column \u2192 `{ field: true }`\n- `\"belongsTo\"`: FK relation \u2192 `{ relation: { select: ... } }`\n- `\"hasOne\"`: 1:1 relation \u2192 nested select\n- `\"hasMany\"`: 1:N relation \u2192 `{ relation: { select: ... } }`\n\nThe kind forces explicit classification of each member BEFORE deciding\nselect syntax, preventing confusion between scalars and relations."
                                 },
                                 nullable: {
                                     oneOf: [
@@ -230,11 +230,11 @@ function process(ctx, props) {
                                             type: "boolean"
                                         }
                                     ],
-                                    description: "Whether this Prisma member is nullable in the schema.\n\nThis property explicitly documents whether a field/relation can be null,\nforcing the AI to understand nullability constraints before deciding\nselection strategy. This affects how the transform() function will handle\nthe data.\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      - Will always have a value in the selected data\n      - Transform() can safely access without null checks\n      - Example: `created_at DateTime` \u2192 `nullable: false`\n  - `true`: Nullable column (e.g., `deleted_at DateTime?`)\n\n      - Might be null in the selected data\n      - Transform() must handle null case (e.g., `?? null`)\n      - Example: `deleted_at DateTime?` \u2192 `nullable: true`\n- **For belongsTo relations** (`kind: \"belongsTo\"`):\n\n  - `false`: Required foreign key (e.g., `customer_id String`)\n\n      - Relation will always exist in the selected data\n      - Transform() can safely use the nested transformer\n      - Example: `customer` relation \u2192 `nullable: false`\n  - `true`: Optional foreign key (e.g., `parent_id String?`)\n\n      - Relation might not exist in the selected data\n      - Transform() must handle null case\n      - Example: `parent` relation \u2192 `nullable: true`\n- **For hasMany/hasOne relations** (`kind: \"hasMany\"` or `kind: \"hasOne\"`):\n\n  - Always `null`: Nullability concept doesn't apply to these relations\n\n      - HasMany: Always returns array (empty or populated)\n      - HasOne: Handled differently in Prisma\n      - The `nullable` property has no semantic meaning\n\n**Why this matters for select()**:\n\n- **Informs transform() handling**: Knowing nullability helps plan correct\n  transformation\n- **Validates selection strategy**: Nullable fields need different handling\n  in transform()\n- **Supports Chain-of-Thought**: AI must think about nullability BEFORE\n  deciding selection\n- **Documents schema constraints**: Makes nullability explicit for validation\n\n**Examples**:\n\n```typescript\n// Non-nullable scalar (nullable: false)\n{ member: \"id\", kind: \"scalar\", nullable: false, how: \"For DTO.id\" }\n{ member: \"email\", kind: \"scalar\", nullable: false, how: \"For DTO.email\" }\n{ member: \"created_at\", kind: \"scalar\", nullable: false, how: \"For DTO.createdAt\" }\n\n// Nullable scalar (nullable: true)\n{ member: \"deleted_at\", kind: \"scalar\", nullable: true, how: \"For DTO.deletedAt (nullable)\" }\n{ member: \"description\", kind: \"scalar\", nullable: true, how: \"For DTO.description (optional)\" }\n\n// Required belongsTo (nullable: false)\n{ member: \"customer\", kind: \"belongsTo\", nullable: false, how: \"For DTO.customer (nested)\" }\n{ member: \"article\", kind: \"belongsTo\", nullable: false, how: \"For DTO.article (nested)\" }\n\n// Optional belongsTo (nullable: true)\n{ member: \"parent\", kind: \"belongsTo\", nullable: true, how: \"For DTO.parent (optional)\" }\n{ member: \"category\", kind: \"belongsTo\", nullable: true, how: \"For DTO.category (optional)\" }\n\n// HasMany relations (nullable: null - not applicable)\n{ member: \"comments\", kind: \"hasMany\", nullable: null, how: \"For DTO.comments (array)\" }\n{ member: \"tags\", kind: \"hasMany\", nullable: null, how: \"For DTO.tags (array)\" }\n```\n\nThe `nullable` property works with `kind` and `how`: kind identifies WHAT\nit is, nullable identifies IF it's optional, how explains WHY we're\nselecting it."
+                                    description: "Whether nullable in Prisma schema.\n\n- `false`: Always present \u2014 transform() can safely access\n- `true`: May be null \u2014 transform() must handle null case\n- `null`: Not applicable (hasMany/hasOne)"
                                 },
                                 how: {
                                     type: "string",
-                                    description: "Brief one-line explanation of why this Prisma field is being selected.\n\nKeep it concise and clear. Focus on which DTO property(ies) need this data.\n\n**For Write Phase** (planning field selection):\n\n- \"For DTO.id\"\n- \"For DTO.email\"\n- \"For DTO.createdAt (needs .toISOString())\"\n- \"For DTO.deletedAt (nullable DateTime)\"\n- \"For DTO.price (Decimal \u2192 Number conversion)\"\n- \"For DTO.totalPrice computation (with quantity)\"\n- \"For DTO.reviewCount aggregation\"\n- \"For DTO.isExpired computation\"\n- \"For DTO.customer (nested CustomerTransformer)\"\n- \"For DTO.tags (array TagTransformer)\"\n- \"For nested transformer's select() requirements\"\n\n**For Correct Phase** (documenting current state and fixes):\n\n- \"No change needed - correct\"\n- \"Already correct\"\n- \"Fix: Wrong field name 'user_email' \u2192 'email'\"\n- \"Fix: Missing field - add for DTO.totalPrice\"\n- \"Fix: Should use select, not include\"\n- \"Fix: Missing aggregation - add _count\"\n- \"Fix: Fabricated field - remove it\"\n- \"Fix: Selecting unused field - remove it\"\n\nEven if a selection is correct, you MUST include it in the mapping and\nexplain why. This ensures complete coverage and alignment with\ntransform().\n\nThis is NOT code - just a simple description of the selection purpose."
+                                    description: "Brief reason for selecting this field (NOT code).\n\nWrite phase: \"For DTO.id\", \"For DTO.createdAt (needs .toISOString())\", \"For\nDTO.customer (nested transformer)\".\n\nCorrect phase: \"No change needed\", \"Fix: Missing field \u2014 add for\nDTO.totalPrice\".\n\nEven if correct, you MUST include it in the mapping. This ensures complete\ncoverage and alignment with transform()."
                                 }
                             },
                             required: [
@@ -243,32 +243,32 @@ function process(ctx, props) {
                                 "nullable",
                                 "how"
                             ],
-                            description: "Single Prisma field selection mapping for the select() function.\n\nDocuments which Prisma fields/relations must be selected from the database to\nenable the transform() function to build the DTO. This structured approach\nensures no required data is missing from the query, preventing runtime\nerrors.\n\n**Purpose**:\n\n- Prevents missing field selections through systematic coverage verification\n- Forces explicit decision-making for each Prisma field selection\n- Ensures select() and transform() are perfectly aligned\n- Creates clear documentation of what data to load from database\n\n**Usage Contexts**:\n\n- **Write Phase**: Plan which Prisma fields to select for each DTO property\n- **Correct Phase**: Document current state and correction plan for each\n  selection\n\nThe validator cross-checks mappings against the Prisma schema and DTO\nrequirements to ensure nothing is overlooked, rejecting incomplete\nselections.\n\n**Critical Principle**:\n\nEvery DTO property in the transform() function requires corresponding Prisma\ndata. This mapping documents what must be selected to satisfy those\nrequirements. If transform() needs `prisma.created_at`, select() MUST include\n`created_at: true`."
+                            description: "Prisma field selection mapping for the select() function.\n\nDocuments which Prisma fields/relations must be selected to enable\ntransform() to build the DTO. EVERY required field must be listed \u2014 the\nvalidator rejects incomplete selections."
                         },
                         AutoBeRealizeTransformerTransformMapping: {
                             type: "object",
                             properties: {
                                 property: {
                                     type: "string",
-                                    description: "Exact DTO property name from the DTO type definition.\n\nMUST match the DTO interface exactly (case-sensitive). Examples:\n\n- Scalar properties: \"id\", \"email\", \"createdAt\"\n- Computed properties: \"totalPrice\", \"reviewCount\", \"isExpired\"\n- Nested objects: \"customer\", \"article\"\n- Arrays: \"tags\", \"comments\"\n\nUse camelCase as DTOs follow TypeScript conventions (unlike Prisma's\nsnake_case).\n\nInclude ALL properties from the DTO, even if they require complex\ntransformations or are computed from multiple Prisma fields.\n\n**Examples**:\n\n```typescript\n// Direct scalar mappings\n{ property: \"id\", how: \"From prisma.id\" }\n{ property: \"email\", how: \"From prisma.email\" }\n{ property: \"createdAt\", how: \"From prisma.created_at.toISOString()\" }\n\n// Type conversions\n{ property: \"price\", how: \"From prisma.unit_price (Decimal \u2192 Number)\" }\n{ property: \"deletedAt\", how: \"From prisma.deleted_at?.toISOString() ?? null\" }\n\n// Computed properties\n{ property: \"totalPrice\", how: \"Compute: prisma.unit_price * prisma.quantity\" }\n{ property: \"reviewCount\", how: \"From prisma._count.reviews\" }\n{ property: \"isExpired\", how: \"Compute: prisma.expiry_date < new Date()\" }\n\n// Nested transformations\n{ property: \"customer\", how: \"Transform with CustomerTransformer\" }\n{ property: \"tags\", how: \"Array map with TagTransformer\" }\n```"
+                                    description: "Exact DTO property name (case-sensitive, camelCase).\n\nInclude ALL properties: direct mappings, type conversions, computed values,\nand nested transformations.\n\n**Examples**:\n\n```typescript\n// Direct scalar mappings\n{ property: \"id\", how: \"From prisma.id\" }\n{ property: \"createdAt\", how: \"From prisma.created_at.toISOString()\" }\n\n// Type conversions\n{ property: \"price\", how: \"From prisma.unit_price (Decimal \u2192 Number)\" }\n{ property: \"deletedAt\", how: \"From prisma.deleted_at?.toISOString() ?? null\" }\n\n// Computed properties\n{ property: \"totalPrice\", how: \"Compute: prisma.unit_price * prisma.quantity\" }\n{ property: \"reviewCount\", how: \"From prisma._count.reviews\" }\n\n// Nested transformations (reuse neighbor transformers)\n{ property: \"customer\", how: \"Transform with CustomerTransformer\" }\n{ property: \"tags\", how: \"Array map with TagTransformer\" }\n```"
                                 },
                                 how: {
                                     type: "string",
-                                    description: "Brief one-line explanation of how to obtain this property's value from\nPrisma.\n\nKeep it concise and clear.\n\n**For Write Phase** (planning transformation strategy):\n\n- \"From prisma.email\"\n- \"From prisma.created_at.toISOString()\"\n- \"From prisma.unit_price (Decimal \u2192 Number)\"\n- \"From prisma.deleted_at?.toISOString() ?? null\"\n- \"Compute: prisma.unit_price * prisma.quantity\"\n- \"From prisma._count.reviews\"\n- \"Compute: prisma.expiry_date < new Date()\"\n- \"Transform with CustomerTransformer\"\n- \"Array map with TagTransformer\"\n- \"From prisma.customer.name (nested field)\"\n\n**For Correct Phase** (documenting current state and fixes):\n\n- \"No change needed - correct\"\n- \"Already correct\"\n- \"Fix: Wrong property name 'userEmail' \u2192 'email'\"\n- \"Fix: Missing property - add from prisma.total_price\"\n- \"Fix: Wrong transformation - should use .toISOString()\"\n- \"Fix: Should use TagTransformer instead of inline\"\n- \"Fix: Missing Decimal conversion\"\n- \"Fix: Fabricated property - remove it\"\n\nEven if a property is correct, you MUST include it in the mapping and\nexplain why. This ensures complete DTO coverage.\n\nThis is NOT code - just a simple description of the transformation\nstrategy."
+                                    description: "Brief strategy for obtaining this property's value (NOT code).\n\nWrite phase: \"From prisma.email\", \"From prisma.created_at.toISOString()\",\n\"From prisma.deleted_at?.toISOString() ?? null\", \"From prisma.unit_price\n(Decimal \u2192 Number)\", \"Transform with CustomerTransformer\", \"Array map with\nTagTransformer\", \"Compute: prisma.unit_price * prisma.quantity\".\n\nCorrect phase: \"No change needed\", \"Fix: Missing Decimal conversion\", \"Fix:\nShould use TagTransformer instead of inline\".\n\nEven if correct, you MUST include it. This ensures complete DTO coverage."
                                 }
                             },
                             required: [
                                 "property",
                                 "how"
                             ],
-                            description: "Single DTO property transformation mapping for the transform() function.\n\nDocuments how to transform Prisma payload data into each specific DTO\nproperty in the transform() function. This structured approach ensures\ncomplete DTO coverage by requiring explicit documentation for EVERY property\n\n- Including those requiring special transformations or computed from multiple\n  Prisma fields.\n\n**Purpose**:\n\n- Prevents property omissions through systematic coverage verification\n- Forces explicit decision-making for each DTO property transformation\n- Enables validation before code generation (Write) or correction (Correct)\n- Creates clear documentation of transformation logic\n\n**Usage Contexts**:\n\n- **Write Phase**: Plan how to transform each Prisma field \u2192 DTO property in\n  transform()\n- **Correct Phase**: Document current state and correction plan for each\n  property in transform()\n\nThe validator cross-checks mappings against the DTO type definition to ensure\nnothing is overlooked, rejecting incomplete mappings.\n\n**Critical Principle**:\n\nThis mapping is ONLY for the transform() function - it documents how to build\nthe DTO return object. The corresponding select() function requirements are\ndocumented separately in AutoBeRealizeTransformerSelectMapping."
+                            description: "DTO property transformation mapping for the transform() function.\n\nDocuments how to transform Prisma payload data into each DTO property. EVERY\nDTO property must be listed \u2014 the validator rejects incomplete mappings."
                         },
                         "IAutoBeRealizeTransformerWriteApplication.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 Section 3 in BOTH select() and\n   transform()\n3. System Rules - Mandatory neighbor reuse, function order, select (not\n   include)\n4. Type Safety - Type casts (Decimal\u2192Number, DateTime\u2192ISO), nullable\n   handling\n\nIdentify specific issues with line numbers and provide clear reasoning.\nThis catches hallucinated fields, missing transformations, and rule\nviolations."
+                                    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 in BOTH select() and\n   transform()\n3. System Rules \u2014 neighbor reuse, function order, select (not include)\n4. Type Safety \u2014 Decimal\u2192Number, DateTime\u2192ISO, nullable handling\n\nIdentify issues with line numbers. This catches hallucinated fields,\nmissing transformations, and rule violations."
                                 },
                                 final: {
                                     oneOf: [
@@ -279,7 +279,7 @@ function process(ctx, props) {
                                             type: "string"
                                         }
                                     ],
-                                    description: "Final transformer 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 transformer code with all review improvements applied, or null if\ndraft needs no changes."
                                 }
                             },
                             required: [
@@ -303,7 +303,7 @@ function process(ctx, props) {
                                 }
                             }
                         ],
-                        description: "Process transformer generation task or preliminary data requests.\n\nGenerates complete transformer module through three-phase workflow (plan \u2192\ndraft \u2192 revise). Ensures type safety, proper Prisma payload types, and\ncorrect DTO mapping."
+                        description: "Process transformer generation task or preliminary data requests."
                     }
                 ]
             },
@@ -559,11 +559,11 @@ function createController(props) {
                     type: "object",
                     properties: {
                         thinking: {
-                            description: "Think before you act.\n\nBefore requesting preliminary data or completing your task, reflect on\nyour current state and explain your reasoning:\n\nFor preliminary requests:\n\n- What database schemas are missing that you need?\n- Why do you need them for transformer 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 transformer 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 transformer implementation\n\nAll necessary DTO type information is obtained transitively from the DTO\ntype names provided in the plan (AutoBeRealizeTransformerPlan). 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"
@@ -588,18 +588,18 @@ function createController(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"
@@ -613,7 +613,7 @@ function createController(props) {
                             ]
                         },
                         "IAutoBeRealizeTransformerWriteApplication.IComplete": {
-                            description: "Request to generate transformer module implementation.\n\nExecutes three-phase generation to create complete transformer with:\n\n- `select()` function: Returns Prisma include/select specification\n- `transform()` function: Converts Prisma payload to DTO\n\nFollows plan \u2192 draft \u2192 revise pattern to ensure type safety and correct\nfield mappings.\n\nNote: The database schema name is provided as input from the planning\nphase, so it doesn't need to be returned in the response.",
+                            description: "Generate transformer module (select + transform functions) via\nplan/draft/revise.",
                             type: "object",
                             properties: {
                                 type: {
@@ -624,29 +624,29 @@ function createController(props) {
                                     ]
                                 },
                                 plan: {
-                                    description: "Transformer 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 table for BOTH select() and\n   transform()\n4. Edge Cases and Special Handling - Type casts (Decimal, DateTime),\n   nullables\n\nThis forces you to READ the actual schema (not imagine it) and creates an\nexplicit specification for both select() and transform() functions.",
+                                    description: "Transformer 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 table for BOTH select() and\n   transform()\n4. Edge Cases and Special Handling \u2014 type casts (Decimal, DateTime),\n   nullables\n\nThis forces you to READ the actual schema (not imagine it) and creates an\nexplicit specification for both select() and transform() functions.",
                                     type: "string"
                                 },
                                 selectMappings: {
-                                    description: "Database field-by-field selection mapping for the select() function.\n\nDocuments which database fields/relations must be selected from the\ndatabase to enable the transform() function. This ensures no required\ndata is missing from the query.\n\nMUST include EVERY database field needed by transform() - no exceptions.\nEach mapping specifies:\n\n- `member`: Exact database field/relation name (snake_case)\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`: Why this field is being selected (which DTO property needs it)\n\nThe `kind` property forces explicit classification of each member BEFORE\ndeciding what to select, preventing confusion between scalars and\nrelations, and ensuring correct select syntax.\n\nThe `nullable` property documents schema constraints that affect how\ntransform() will handle the data, enabling proper null handling in\ntransformations.\n\nMissing even a single required field will cause validation failure and\ntrigger regeneration.\n\nThis structured approach:\n\n- Prevents missing field selections through systematic coverage\n- Forces explicit decision-making for each database field (kind + nullable\n\n  - How)\n- Ensures select() and transform() are perfectly aligned\n- Documents what data to load from database\n- Prevents confusion between scalar fields and relations\n- Documents nullability constraints for transform() planning\n- Enables validation before code generation\n\n**Common selection patterns by kind**:\n\n- **Scalar fields (nullable: true/false)**: For direct mapping or type\n  conversion\n- **Computation sources (nullable: true/false)**: Fields needed for\n  computed DTO properties\n- **Aggregations (nullable: false)**: _count, _sum, _avg for DTO statistics\n- **BelongsTo relations (nullable: true/false)**: For nested object\n  transformers\n- **HasMany relations (nullable: null)**: For array transformers\n\nThe validator will cross-check this list against the database schema and\nDTO requirements to ensure complete coverage.",
+                                    description: "Database field-by-field selection mapping for select().\n\nMUST include EVERY database field needed by transform() \u2014 no exceptions.\nEach mapping specifies:\n\n- `member`: Exact Prisma field/relation name (snake_case) \u2014 read from the\n  Relation Mapping Table and member list, NOT from DTO property names\n- `kind`: scalar, belongsTo, hasOne, or hasMany\n- `nullable`: true/false for scalar/belongsTo, null for hasMany/hasOne\n- `how`: Which DTO property needs it\n\nThe `kind` property forces explicit classification of each member BEFORE\ndeciding select syntax, preventing confusion between scalars and\nrelations.\n\nMissing even a single required field will cause validation failure.",
                                     type: "array",
                                     items: {
                                         $ref: "#/$defs/AutoBeRealizeTransformerSelectMapping"
                                     }
                                 },
                                 transformMappings: {
-                                    description: "DTO property-by-property transformation mapping for the transform()\nfunction.\n\nDocuments how to transform database payload data into each DTO property.\nThis ensures complete DTO coverage and correct transformation logic.\n\nMUST include EVERY property from the DTO type definition - no exceptions.\nEach mapping specifies:\n\n- `property`: Exact DTO property name (camelCase)\n- `how`: How to obtain this property value from Prisma payload\n\nMissing even a single property will cause validation failure and trigger\nregeneration.\n\nThis structured approach:\n\n- Prevents property omissions through systematic coverage\n- Forces explicit decision-making for each property transformation\n- Documents transformation logic (direct mapping, type conversion,\n  computation, nested transformation)\n- Ensures select() and transform() are aligned\n- Enables validation before code generation\n\n**Common transformation patterns**:\n\n- **Direct mapping**: Simple field renaming (snake_case \u2192 camelCase)\n- **Type conversion**: Decimal \u2192 Number, DateTime \u2192 ISO string\n- **Nullable handling**: DateTime? \u2192 string | null\n- **Computed properties**: Calculate from multiple database fields\n- **Aggregation**: Use _count, _sum, _avg from database\n- **Nested objects**: Reuse neighbor transformers\n- **Arrays**: Map with ArrayUtil.asyncMap + neighbor transformer\n\nThe validator will cross-check this list against the actual DTO type\ndefinition and reject incomplete mappings.",
+                                    description: "DTO property-by-property transformation mapping for transform().\n\nMUST include EVERY property from the DTO type definition \u2014 no exceptions.\nEach mapping specifies:\n\n- `property`: Exact DTO property name (camelCase)\n- `how`: How to obtain from Prisma payload\n\n**Common transformation patterns**:\n\n- Direct mapping: snake_case \u2192 camelCase\n- Type conversion: Decimal \u2192 Number, DateTime \u2192 ISO string\n- Nullable: DateTime? \u2192 string | null\n- Nested objects: Reuse neighbor transformers\n- Arrays: ArrayUtil.asyncMap + neighbor transformer\n\nMissing even a single property will cause validation failure.",
                                     type: "array",
                                     items: {
                                         $ref: "#/$defs/AutoBeRealizeTransformerTransformMapping"
                                     }
                                 },
                                 draft: {
-                                    description: "Initial transformer implementation draft.\n\nComplete implementation that strictly follows the plan's mapping table.\nEVERY field in the plan's Section 3 MUST appear in BOTH select() and\ntransform(). Implement:\n\n- Transform() first, select() second, Payload last (correct order)\n- All field mappings from plan with correct transformations\n- Neighbor transformer reuse (NEVER inline when transformer exists)\n- ALWAYS use `select`, NEVER use `include`",
+                                    description: "Complete implementation following plan's mapping table. EVERY field from\nplan Section 3 MUST appear in BOTH select() and transform(). Implement:\n\n- Transform() first, select() second, Payload last (correct order)\n- All field mappings from plan with correct transformations\n- Neighbor transformer reuse (NEVER inline when transformer exists)\n- ALWAYS use `select`, NEVER use `include`",
                                     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/IAutoBeRealizeTransformerWriteApplication.IReviseProps"
                                 }
                             },
@@ -660,15 +660,15 @@ function createController(props) {
                             ]
                         },
                         AutoBeRealizeTransformerSelectMapping: {
-                            description: "Single Prisma field selection mapping for the select() function.\n\nDocuments which Prisma fields/relations must be selected from the database to\nenable the transform() function to build the DTO. This structured approach\nensures no required data is missing from the query, preventing runtime\nerrors.\n\n**Purpose**:\n\n- Prevents missing field selections through systematic coverage verification\n- Forces explicit decision-making for each Prisma field selection\n- Ensures select() and transform() are perfectly aligned\n- Creates clear documentation of what data to load from database\n\n**Usage Contexts**:\n\n- **Write Phase**: Plan which Prisma fields to select for each DTO property\n- **Correct Phase**: Document current state and correction plan for each\n  selection\n\nThe validator cross-checks mappings against the Prisma schema and DTO\nrequirements to ensure nothing is overlooked, rejecting incomplete\nselections.\n\n**Critical Principle**:\n\nEvery DTO property in the transform() function requires corresponding Prisma\ndata. This mapping documents what must be selected to satisfy those\nrequirements. If transform() needs `prisma.created_at`, select() MUST include\n`created_at: true`.",
+                            description: "Prisma field selection mapping for the select() function.\n\nDocuments which Prisma fields/relations must be selected to enable\ntransform() to build the DTO. EVERY required field must be listed \u2014 the\nvalidator rejects incomplete selections.",
                             type: "object",
                             properties: {
                                 member: {
-                                    description: "Exact Prisma field or relation name from the Prisma schema.\n\nMUST match the Prisma schema exactly (case-sensitive). Use snake_case as\nPrisma follows database conventions.\n\n**Field Types**:\n\n- **Scalar fields**: Database columns (id, email, created_at, unit_price,\n  etc.)\n- **BelongsTo relations**: Foreign key relations (customer, article,\n  category, etc.)\n- **HasMany relations**: One-to-many arrays (tags, comments, reviews, etc.)\n- **Aggregations**: Prisma computed fields (_count, _sum, _avg, etc.)\n\n**Examples**:\n\n```typescript\n// Scalar fields for direct mapping or conversion\n{ member: \"id\", kind: \"scalar\", nullable: false, how: \"For DTO.id\" }\n{ member: \"email\", kind: \"scalar\", nullable: false, how: \"For DTO.email\" }\n{ member: \"created_at\", kind: \"scalar\", nullable: false, how: \"For DTO.createdAt (needs .toISOString())\" }\n{ member: \"unit_price\", kind: \"scalar\", nullable: false, how: \"For DTO.price (Decimal \u2192 Number)\" }\n{ member: \"deleted_at\", kind: \"scalar\", nullable: true, how: \"For DTO.deletedAt (nullable DateTime)\" }\n\n// Scalar fields for computation\n{ member: \"quantity\", kind: \"scalar\", nullable: false, how: \"For DTO.totalPrice computation\" }\n{ member: \"expiry_date\", kind: \"scalar\", nullable: false, how: \"For DTO.isExpired computation\" }\n\n// Aggregations (special scalar type)\n{ member: \"_count\", kind: \"scalar\", nullable: false, how: \"For DTO.reviewCount\" }\n\n// BelongsTo relations (nested objects)\n{ member: \"customer\", kind: \"belongsTo\", nullable: false, how: \"For DTO.customer (nested transformer)\" }\n{ member: \"article\", kind: \"belongsTo\", nullable: false, how: \"For DTO.article (nested transformer)\" }\n{ member: \"parent\", kind: \"belongsTo\", nullable: true, how: \"For DTO.parent (optional nested)\" }\n\n// HasMany relations (arrays)\n{ member: \"tags\", kind: \"hasMany\", nullable: null, how: \"For DTO.tags (array transformer)\" }\n{ member: \"comments\", kind: \"hasMany\", nullable: null, how: \"For DTO.comments (array transformer)\" }\n```\n\nDO NOT use DTO property names here - this is about Prisma schema members,\nnot DTO properties.",
+                                    description: "Exact Prisma field or relation name from the Prisma schema.\n\nMUST match the Prisma schema exactly (case-sensitive, snake_case).\n\n**Field Types**:\n\n- **Scalar fields**: Database columns (id, email, created_at, unit_price)\n- **BelongsTo relations**: FK relations (customer, article, category)\n- **HasMany relations**: 1:N arrays (tags, comments, reviews)\n- **Aggregations**: Prisma computed fields (_count, _sum, _avg)\n\n**Examples**:\n\n```typescript\n// Scalar fields\n{ member: \"id\", kind: \"scalar\", nullable: false, how: \"For DTO.id\" }\n{ member: \"created_at\", kind: \"scalar\", nullable: false, how: \"For DTO.createdAt (needs .toISOString())\" }\n{ member: \"unit_price\", kind: \"scalar\", nullable: false, how: \"For DTO.price (Decimal \u2192 Number)\" }\n{ member: \"deleted_at\", kind: \"scalar\", nullable: true, how: \"For DTO.deletedAt (nullable DateTime)\" }\n\n// BelongsTo relations \u2014 member is ALWAYS the Prisma relation name,\n// which may differ from the DTO property name\n{ member: \"customer\", kind: \"belongsTo\", nullable: false, how: \"For DTO.buyer (nested transformer)\" }\n{ member: \"user\", kind: \"belongsTo\", nullable: true, how: \"For DTO.voter (optional nested)\" }\n\n// HasMany relations\n{ member: \"tags\", kind: \"hasMany\", nullable: null, how: \"For DTO.tags (array transformer)\" }\n```\n\nDO NOT use DTO property names \u2014 this is about Prisma schema members. Read\nthe Relation Mapping Table and member list to find correct names.",
                                     type: "string"
                                 },
                                 kind: {
-                                    description: "The kind of Prisma schema member being selected.\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\nwhat to select, preventing common mistakes in the select() function.\n\n**Possible values**:\n\n- `\"scalar\"`: Regular database column (id, email, created_at, unit_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 for select()**:\n\n- **Prevents confusion**: AI must consciously identify if \"customer\" is a\n  scalar or belongsTo relation\n- **Forces correct select syntax**: belongsTo/hasMany require nested select\n  objects, scalar requires `true`\n- **Enables Chain-of-Thought**: AI explicitly thinks about the kind before\n  deciding selection strategy\n- **Supports proper data loading**: Different kinds require different\n  selection approaches\n\n**Examples by kind**:\n\n```typescript\n// Scalar fields - simple selection\n{ member: \"id\", kind: \"scalar\", nullable: false, how: \"For DTO.id\" }\n{ member: \"email\", kind: \"scalar\", nullable: false, how: \"For DTO.email\" }\n{ member: \"created_at\", kind: \"scalar\", nullable: false, how: \"For DTO.createdAt\" }\n{ member: \"deleted_at\", kind: \"scalar\", nullable: true, how: \"For DTO.deletedAt\" }\n\n// BelongsTo relations - nested selection with transformer\n{ member: \"customer\", kind: \"belongsTo\", nullable: false, how: \"For DTO.customer (nested)\" }\n{ member: \"article\", kind: \"belongsTo\", nullable: false, how: \"For DTO.article (nested)\" }\n{ member: \"parent\", kind: \"belongsTo\", nullable: true, how: \"For DTO.parent (optional)\" }\n\n// HasMany relations - nested selection with array transformer\n{ member: \"tags\", kind: \"hasMany\", nullable: null, how: \"For DTO.tags (array)\" }\n{ member: \"comments\", kind: \"hasMany\", nullable: null, how: \"For DTO.comments (array)\" }\n```\n\nThe `kind` field works together with `nullable` and `how`: kind identifies\nWHAT it is, nullable identifies IF it's optional, how explains WHY we're\nselecting it.",
+                                    description: "Kind of Prisma schema member.\n\n- `\"scalar\"`: Regular column \u2192 `{ field: true }`\n- `\"belongsTo\"`: FK relation \u2192 `{ relation: { select: ... } }`\n- `\"hasOne\"`: 1:1 relation \u2192 nested select\n- `\"hasMany\"`: 1:N relation \u2192 `{ relation: { select: ... } }`\n\nThe kind forces explicit classification of each member BEFORE deciding\nselect syntax, preventing confusion between scalars and relations.",
                                     type: "string",
                                     "enum": [
                                         "scalar",
@@ -678,7 +678,7 @@ function createController(props) {
                                     ]
                                 },
                                 nullable: {
-                                    description: "Whether this Prisma member is nullable in the schema.\n\nThis property explicitly documents whether a field/relation can be null,\nforcing the AI to understand nullability constraints before deciding\nselection strategy. This affects how the transform() function will handle\nthe data.\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      - Will always have a value in the selected data\n      - Transform() can safely access without null checks\n      - Example: `created_at DateTime` \u2192 `nullable: false`\n  - `true`: Nullable column (e.g., `deleted_at DateTime?`)\n\n      - Might be null in the selected data\n      - Transform() must handle null case (e.g., `?? null`)\n      - Example: `deleted_at DateTime?` \u2192 `nullable: true`\n- **For belongsTo relations** (`kind: \"belongsTo\"`):\n\n  - `false`: Required foreign key (e.g., `customer_id String`)\n\n      - Relation will always exist in the selected data\n      - Transform() can safely use the nested transformer\n      - Example: `customer` relation \u2192 `nullable: false`\n  - `true`: Optional foreign key (e.g., `parent_id String?`)\n\n      - Relation might not exist in the selected data\n      - Transform() must handle null case\n      - Example: `parent` relation \u2192 `nullable: true`\n- **For hasMany/hasOne relations** (`kind: \"hasMany\"` or `kind: \"hasOne\"`):\n\n  - Always `null`: Nullability concept doesn't apply to these relations\n\n      - HasMany: Always returns array (empty or populated)\n      - HasOne: Handled differently in Prisma\n      - The `nullable` property has no semantic meaning\n\n**Why this matters for select()**:\n\n- **Informs transform() handling**: Knowing nullability helps plan correct\n  transformation\n- **Validates selection strategy**: Nullable fields need different handling\n  in transform()\n- **Supports Chain-of-Thought**: AI must think about nullability BEFORE\n  deciding selection\n- **Documents schema constraints**: Makes nullability explicit for validation\n\n**Examples**:\n\n```typescript\n// Non-nullable scalar (nullable: false)\n{ member: \"id\", kind: \"scalar\", nullable: false, how: \"For DTO.id\" }\n{ member: \"email\", kind: \"scalar\", nullable: false, how: \"For DTO.email\" }\n{ member: \"created_at\", kind: \"scalar\", nullable: false, how: \"For DTO.createdAt\" }\n\n// Nullable scalar (nullable: true)\n{ member: \"deleted_at\", kind: \"scalar\", nullable: true, how: \"For DTO.deletedAt (nullable)\" }\n{ member: \"description\", kind: \"scalar\", nullable: true, how: \"For DTO.description (optional)\" }\n\n// Required belongsTo (nullable: false)\n{ member: \"customer\", kind: \"belongsTo\", nullable: false, how: \"For DTO.customer (nested)\" }\n{ member: \"article\", kind: \"belongsTo\", nullable: false, how: \"For DTO.article (nested)\" }\n\n// Optional belongsTo (nullable: true)\n{ member: \"parent\", kind: \"belongsTo\", nullable: true, how: \"For DTO.parent (optional)\" }\n{ member: \"category\", kind: \"belongsTo\", nullable: true, how: \"For DTO.category (optional)\" }\n\n// HasMany relations (nullable: null - not applicable)\n{ member: \"comments\", kind: \"hasMany\", nullable: null, how: \"For DTO.comments (array)\" }\n{ member: \"tags\", kind: \"hasMany\", nullable: null, how: \"For DTO.tags (array)\" }\n```\n\nThe `nullable` property works with `kind` and `how`: kind identifies WHAT\nit is, nullable identifies IF it's optional, how explains WHY we're\nselecting it.",
+                                    description: "Whether nullable in Prisma schema.\n\n- `false`: Always present \u2014 transform() can safely access\n- `true`: May be null \u2014 transform() must handle null case\n- `null`: Not applicable (hasMany/hasOne)",
                                     anyOf: [
                                         {
                                             type: "null"
@@ -689,7 +689,7 @@ function createController(props) {
                                     ]
                                 },
                                 how: {
-                                    description: "Brief one-line explanation of why this Prisma field is being selected.\n\nKeep it concise and clear. Focus on which DTO property(ies) need this data.\n\n**For Write Phase** (planning field selection):\n\n- \"For DTO.id\"\n- \"For DTO.email\"\n- \"For DTO.createdAt (needs .toISOString())\"\n- \"For DTO.deletedAt (nullable DateTime)\"\n- \"For DTO.price (Decimal \u2192 Number conversion)\"\n- \"For DTO.totalPrice computation (with quantity)\"\n- \"For DTO.reviewCount aggregation\"\n- \"For DTO.isExpired computation\"\n- \"For DTO.customer (nested CustomerTransformer)\"\n- \"For DTO.tags (array TagTransformer)\"\n- \"For nested transformer's select() requirements\"\n\n**For Correct Phase** (documenting current state and fixes):\n\n- \"No change needed - correct\"\n- \"Already correct\"\n- \"Fix: Wrong field name 'user_email' \u2192 'email'\"\n- \"Fix: Missing field - add for DTO.totalPrice\"\n- \"Fix: Should use select, not include\"\n- \"Fix: Missing aggregation - add _count\"\n- \"Fix: Fabricated field - remove it\"\n- \"Fix: Selecting unused field - remove it\"\n\nEven if a selection is correct, you MUST include it in the mapping and\nexplain why. This ensures complete coverage and alignment with\ntransform().\n\nThis is NOT code - just a simple description of the selection purpose.",
+                                    description: "Brief reason for selecting this field (NOT code).\n\nWrite phase: \"For DTO.id\", \"For DTO.createdAt (needs .toISOString())\", \"For\nDTO.customer (nested transformer)\".\n\nCorrect phase: \"No change needed\", \"Fix: Missing field \u2014 add for\nDTO.totalPrice\".\n\nEven if correct, you MUST include it in the mapping. This ensures complete\ncoverage and alignment with transform().",
                                     type: "string"
                                 }
                             },
@@ -701,15 +701,15 @@ function createController(props) {
                             ]
                         },
                         AutoBeRealizeTransformerTransformMapping: {
-                            description: "Single DTO property transformation mapping for the transform() function.\n\nDocuments how to transform Prisma payload data into each specific DTO\nproperty in the transform() function. This structured approach ensures\ncomplete DTO coverage by requiring explicit documentation for EVERY property\n\n- Including those requiring special transformations or computed from multiple\n  Prisma fields.\n\n**Purpose**:\n\n- Prevents property omissions through systematic coverage verification\n- Forces explicit decision-making for each DTO property transformation\n- Enables validation before code generation (Write) or correction (Correct)\n- Creates clear documentation of transformation logic\n\n**Usage Contexts**:\n\n- **Write Phase**: Plan how to transform each Prisma field \u2192 DTO property in\n  transform()\n- **Correct Phase**: Document current state and correction plan for each\n  property in transform()\n\nThe validator cross-checks mappings against the DTO type definition to ensure\nnothing is overlooked, rejecting incomplete mappings.\n\n**Critical Principle**:\n\nThis mapping is ONLY for the transform() function - it documents how to build\nthe DTO return object. The corresponding select() function requirements are\ndocumented separately in AutoBeRealizeTransformerSelectMapping.",
+                            description: "DTO property transformation mapping for the transform() function.\n\nDocuments how to transform Prisma payload data into each DTO property. EVERY\nDTO property must be listed \u2014 the validator rejects incomplete mappings.",
                             type: "object",
                             properties: {
                                 property: {
-                                    description: "Exact DTO property name from the DTO type definition.\n\nMUST match the DTO interface exactly (case-sensitive). Examples:\n\n- Scalar properties: \"id\", \"email\", \"createdAt\"\n- Computed properties: \"totalPrice\", \"reviewCount\", \"isExpired\"\n- Nested objects: \"customer\", \"article\"\n- Arrays: \"tags\", \"comments\"\n\nUse camelCase as DTOs follow TypeScript conventions (unlike Prisma's\nsnake_case).\n\nInclude ALL properties from the DTO, even if they require complex\ntransformations or are computed from multiple Prisma fields.\n\n**Examples**:\n\n```typescript\n// Direct scalar mappings\n{ property: \"id\", how: \"From prisma.id\" }\n{ property: \"email\", how: \"From prisma.email\" }\n{ property: \"createdAt\", how: \"From prisma.created_at.toISOString()\" }\n\n// Type conversions\n{ property: \"price\", how: \"From prisma.unit_price (Decimal \u2192 Number)\" }\n{ property: \"deletedAt\", how: \"From prisma.deleted_at?.toISOString() ?? null\" }\n\n// Computed properties\n{ property: \"totalPrice\", how: \"Compute: prisma.unit_price * prisma.quantity\" }\n{ property: \"reviewCount\", how: \"From prisma._count.reviews\" }\n{ property: \"isExpired\", how: \"Compute: prisma.expiry_date < new Date()\" }\n\n// Nested transformations\n{ property: \"customer\", how: \"Transform with CustomerTransformer\" }\n{ property: \"tags\", how: \"Array map with TagTransformer\" }\n```",
+                                    description: "Exact DTO property name (case-sensitive, camelCase).\n\nInclude ALL properties: direct mappings, type conversions, computed values,\nand nested transformations.\n\n**Examples**:\n\n```typescript\n// Direct scalar mappings\n{ property: \"id\", how: \"From prisma.id\" }\n{ property: \"createdAt\", how: \"From prisma.created_at.toISOString()\" }\n\n// Type conversions\n{ property: \"price\", how: \"From prisma.unit_price (Decimal \u2192 Number)\" }\n{ property: \"deletedAt\", how: \"From prisma.deleted_at?.toISOString() ?? null\" }\n\n// Computed properties\n{ property: \"totalPrice\", how: \"Compute: prisma.unit_price * prisma.quantity\" }\n{ property: \"reviewCount\", how: \"From prisma._count.reviews\" }\n\n// Nested transformations (reuse neighbor transformers)\n{ property: \"customer\", how: \"Transform with CustomerTransformer\" }\n{ property: \"tags\", how: \"Array map with TagTransformer\" }\n```",
                                     type: "string"
                                 },
                                 how: {
-                                    description: "Brief one-line explanation of how to obtain this property's value from\nPrisma.\n\nKeep it concise and clear.\n\n**For Write Phase** (planning transformation strategy):\n\n- \"From prisma.email\"\n- \"From prisma.created_at.toISOString()\"\n- \"From prisma.unit_price (Decimal \u2192 Number)\"\n- \"From prisma.deleted_at?.toISOString() ?? null\"\n- \"Compute: prisma.unit_price * prisma.quantity\"\n- \"From prisma._count.reviews\"\n- \"Compute: prisma.expiry_date < new Date()\"\n- \"Transform with CustomerTransformer\"\n- \"Array map with TagTransformer\"\n- \"From prisma.customer.name (nested field)\"\n\n**For Correct Phase** (documenting current state and fixes):\n\n- \"No change needed - correct\"\n- \"Already correct\"\n- \"Fix: Wrong property name 'userEmail' \u2192 'email'\"\n- \"Fix: Missing property - add from prisma.total_price\"\n- \"Fix: Wrong transformation - should use .toISOString()\"\n- \"Fix: Should use TagTransformer instead of inline\"\n- \"Fix: Missing Decimal conversion\"\n- \"Fix: Fabricated property - remove it\"\n\nEven if a property is correct, you MUST include it in the mapping and\nexplain why. This ensures complete DTO coverage.\n\nThis is NOT code - just a simple description of the transformation\nstrategy.",
+                                    description: "Brief strategy for obtaining this property's value (NOT code).\n\nWrite phase: \"From prisma.email\", \"From prisma.created_at.toISOString()\",\n\"From prisma.deleted_at?.toISOString() ?? null\", \"From prisma.unit_price\n(Decimal \u2192 Number)\", \"Transform with CustomerTransformer\", \"Array map with\nTagTransformer\", \"Compute: prisma.unit_price * prisma.quantity\".\n\nCorrect phase: \"No change needed\", \"Fix: Missing Decimal conversion\", \"Fix:\nShould use TagTransformer instead of inline\".\n\nEven if correct, you MUST include it. This ensures complete DTO coverage.",
                                     type: "string"
                                 }
                             },
@@ -722,11 +722,11 @@ function createController(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 Section 3 in BOTH select() and\n   transform()\n3. System Rules - Mandatory neighbor reuse, function order, select (not\n   include)\n4. Type Safety - Type casts (Decimal\u2192Number, DateTime\u2192ISO), nullable\n   handling\n\nIdentify specific issues with line numbers and provide clear reasoning.\nThis catches hallucinated fields, missing transformations, and rule\nviolations.",
+                                    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 in BOTH select() and\n   transform()\n3. System Rules \u2014 neighbor reuse, function order, select (not include)\n4. Type Safety \u2014 Decimal\u2192Number, DateTime\u2192ISO, nullable handling\n\nIdentify issues with line numbers. This catches hallucinated fields,\nmissing transformations, and rule violations.",
                                     type: "string"
                                 },
                                 final: {
-                                    description: "Final transformer 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 transformer code with all review improvements applied, or null if\ndraft needs no changes.",
                                     anyOf: [
                                         {
                                             type: "null"
@@ -744,7 +744,7 @@ function createController(props) {
                         }
                     }
                 },
-                description: "Process transformer generation task or preliminary data requests.\n\nGenerates complete transformer module through three-phase workflow (plan \u2192\ndraft \u2192 revise). Ensures type safety, proper Prisma payload types, and\ncorrect DTO mapping.",
+                description: "Process transformer 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.selectMappings) && input.selectMappings.every(elem => "object" === typeof elem && null !== elem && _io3(elem))) && (Array.isArray(input.transformMappings) && input.transformMappings.every(elem => "object" === typeof elem && null !== elem && _io4(elem))) && "string" === typeof input.draft && ("object" === typeof input.revise && null !== input.revise && _io5(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.property && "string" === typeof input.how; const _io5 = input => "string" === typeof input.review && (null === input.final || "string" === typeof input.final); const _iu0 = input => (() => {
                     if ("getDatabaseSchemas" === input.type)
                         return _io1(input);

package/lib/orchestrate/realize/programmers/AutoBeRealizeTransformerProgrammer.d.ts

@@ -8,6 +8,19 @@ export declare namespace AutoBeRealizeTransformerProgrammer {
     }): boolean;
     function getName(dtoTypeName: string): string;
     function getNeighbors(code: string): string[];
+    function getRelationMappingTable(props: {
+        application: AutoBeDatabase.IApplication;
+        model: AutoBeDatabase.IModel;
+    }): Array<{
+        propertyKey: string;
+        targetModel: string;
+        relationType: string;
+        fkColumns: string;
+    }>;
+    function formatRelationMappingTable(props: {
+        application: AutoBeDatabase.IApplication;
+        model: AutoBeDatabase.IModel;
+    }): string;
     function getSelectMappingMetadata(props: {
         application: AutoBeDatabase.IApplication;
         model: AutoBeDatabase.IModel;
@@ -19,6 +32,7 @@ export declare namespace AutoBeRealizeTransformerProgrammer {
     function writeTemplate(props: {
         plan: AutoBeRealizeTransformerPlan;
         schema: AutoBeOpenApi.IJsonSchemaDescriptive.IObject;
+        schemas: Record<string, AutoBeOpenApi.IJsonSchema>;
     }): string;
     function writeStructures(ctx: AutoBeContext, dtoTypeName: string): Promise<Record<string, string>>;
     function replaceImportStatements(ctx: AutoBeContext, props: {
@@ -39,6 +53,10 @@ export declare namespace AutoBeRealizeTransformerProgrammer {
             final: string | null;
         };
     }): IValidation.IError[];
+    function getRecursiveProperty(props: {
+        schemas: Record<string, AutoBeOpenApi.IJsonSchema>;
+        typeName: string;
+    }): string | null;
     const fixApplication: (props: {
         definition: ILlmApplication;
         application: AutoBeDatabase.IApplication;