@autobe/agent 0.30.4 → 0.30.5

package/lib/orchestrate/realize/orchestrateRealizeTransformerCorrectOverall.js

@@ -97,7 +97,7 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                 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 (getDatabaseSchemas):\n\n- What critical information is missing that you don't already have?\n- Why do you need it specifically right now?\n- Be brief - state the gap, don't list everything you have.\n\nFor completion (complete):\n\n- What key assets did you acquire?\n- What did you accomplish?\n- Why is it sufficient to complete?\n- Summarize - don't enumerate every single item.\n\nThis reflection helps you avoid duplicate requests and premature\ncompletion."
+                                        description: "Think before you act.\n\nFor preliminary requests: what critical information is missing?\n\nFor completion: what did you acquire, what did you accomplish, why is it\nsufficient? Summarize \u2014 don't enumerate every single item."
                                     },
                                     request: {
                                         oneOf: [
@@ -115,7 +115,7 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                                 complete: "#/components/schemas/IAutoBeRealizeTransformerCorrectApplication.IComplete"
                                             }
                                         },
-                                        description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval\n(getDatabaseSchemas) or final error correction (complete). When\npreliminary returns empty array, that type is removed from the union,\nphysically preventing repeated calls."
+                                        description: "Action to perform. Exhausted preliminary types are removed from the\nunion, physically preventing repeated calls."
                                     }
                                 },
                                 required: [
@@ -128,7 +128,7 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                 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",
@@ -136,47 +136,47 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                             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."
                             },
                             "IAutoBeRealizeTransformerCorrectApplication.IComplete": {
                                 type: "object",
                                 properties: {
                                     type: {
                                         "const": "complete",
-                                        description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"complete\" indicates this is the final task\nexecution request."
+                                        description: "Type discriminator for completion request."
                                     },
                                     think: {
                                         type: "string",
-                                        description: "Systematic error analysis and correction strategy.\n\nMUST contain thorough analysis with these four mandatory sections:\n\n1. Error Inventory - Categorize ALL compilation errors by root cause type\n2. Root Cause Analysis - Identify WHY each error occurs (wrong field, wrong\n   transform, etc.)\n3. Schema Verification - Cross-check error-related fields against actual\n   database schema\n4. Correction Strategy - Specific fix for each error in BOTH select() and\n   transform()\n\nThis forces you to understand the REAL problem (not guess) and plan\nsurgical fixes that address root causes, not symptoms."
+                                        description: "Systematic error analysis. MUST contain four sections:\n\n1. Error Inventory \u2014 categorize ALL compilation errors by root cause\n2. Root Cause Analysis \u2014 identify WHY each error occurs (wrong field, wrong\n   transform, etc.)\n3. Schema Verification \u2014 cross-check error-related fields against actual\n   database schema\n4. Correction Strategy \u2014 specific fix for each error in BOTH select() and\n   transform()\n\nThis forces you to understand the REAL problem (not guess) and plan\nsurgical fixes that address root causes, not symptoms."
                                     },
                                     selectMappings: {
                                         type: "array",
                                         items: {
                                             $ref: "#/components/schemas/AutoBeRealizeTransformerSelectMapping"
                                         },
-                                        description: "Database field-by-field selection mapping verification for the select()\nfunction.\n\nReview which database fields/relations are being selected to identify\nmissing selections or incorrect field names that cause compilation\nerrors.\n\nFor each database field needed by transform(), document:\n\n- `member`: Exact database field/relation name (snake_case) - verify\n  against 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`: Current state + correction plan (\"No change needed\", \"Fix: wrong\n  field name\", etc.)\n\nThe `kind` property helps identify selection syntax errors (e.g., using\n`field: true` for a relation instead of nested select).\n\nThe `nullable` property helps catch nullability mismatch errors in\ntransform().\n\n**Common selection errors to identify**:\n\n- Wrong field name (typo or doesn't exist in schema)\n- Missing required field (transform() uses it but select() doesn't fetch\n  it)\n- Wrong selection syntax (true for relation, or nested select for scalar)\n- Selecting field that doesn't exist in database model\n- Missing aggregation (_count, _sum) when transform() needs it\n\nThis structured verification:\n\n- Catches missing field selections before runtime\n- Identifies field name typos by comparing with schema\n- Ensures select() provides all data transform() needs\n- Documents what corrections are needed for selection logic\n- Prevents \"field not found\" errors\n\nThe validator will cross-check this against the database schema to ensure\nall field names are valid and complete coverage.\n\n**Note**: If compilation succeeds, select() is typically correct. This\nmapping is mainly for cases where select() has errors (wrong field names,\nmissing selections)."
+                                        description: "Selection mapping verification for select(). For each database field\nneeded by transform(), document:\n\n- `member`: Exact Prisma field/relation name (snake_case) \u2014 verify against\n  the Relation Mapping Table and member list\n- `kind`: scalar, belongsTo, hasOne, or hasMany\n- `nullable`: true/false for scalar/belongsTo, null for hasMany/hasOne\n- `how`: Current state + correction plan (\"No change needed\", \"Fix: wrong\n  field name\", etc.)\n\n**Common selection errors to identify**:\n\n- Wrong field name (typo or doesn't exist in schema)\n- Missing required field (transform() uses it but select() doesn't)\n- Wrong syntax (true for relation, or nested select for scalar)\n\nMissing even a single required field will cause validation failure."
                                     },
                                     transformMappings: {
                                         type: "array",
                                         items: {
                                             $ref: "#/components/schemas/AutoBeRealizeTransformerTransformMapping"
                                         },
-                                        description: "DTO property-by-property mapping verification for the transform()\nfunction.\n\nReview EVERY property from the DTO type definition to ensure correct\ntransformation in the transform() function. This systematic approach\ncatches errors beyond what the compiler reports and prevents new issues.\n\nFor each DTO property in transform(), document:\n\n- `property`: Exact DTO property name (camelCase)\n- `how`: Current state + correction plan (\"No change needed\", \"Fix:\n  [problem] \u2192 [solution]\", etc.)\n\nEven properties without errors should be included with \"No change needed\"\nto ensure complete review. Missing even a single property could hide\nbugs.\n\nThis structured verification:\n\n- Catches silent errors compiler didn't report\n- Ensures no properties accidentally omitted in transform()\n- Documents transformation corrections explicitly\n- Verifies transform() logic correctness\n- Prevents regression in working transformations\n\n**Common correction scenarios in transform()**:\n\n- Missing type conversion (Decimal \u2192 Number, DateTime \u2192 ISO)\n- Wrong property name (DTO vs database mismatch)\n- Inline transformation when neighbor transformer exists\n- Missing computed property\n- Wrong nullable handling (DateTime? \u2192 string | null)\n- Fabricated property not in DTO\n- Missing property from DTO\n- Missing await for async transformers\n\nThe validator will cross-check this against the DTO type definition to\nensure nothing was overlooked.\n\n**Note**: This mapping is ONLY for the transform() function. The select()\nfunction is typically correct if compilation succeeds, as it's\nstructurally simpler."
+                                        description: "Transform mapping verification. MUST include EVERY DTO property.\n\n- `property`: Exact DTO property name (camelCase)\n- `how`: Current state + correction plan (\"No change needed\", \"Fix:\n  [problem] \u2192 [solution]\")\n\nEven correct properties must be included with \"No change needed\" to\nensure complete review.\n\nMissing even a single property will cause validation failure."
                                     },
                                     draft: {
                                         type: "string",
-                                        description: "Initial correction implementation.\n\nComplete corrected code that applies ALL fixes from the think phase\nstrategy. EVERY error in think Section 1 inventory MUST be addressed.\nImplement:\n\n- Field name corrections in select() (exact database field names)\n- Type casts in transform() (Decimal\u2192Number, DateTime\u2192ISO)\n- Neighbor transformer reuse (replace inline logic if transformer exists)\n- Function order fix (transform \u2192 select \u2192 Payload)\n\nApply fixes surgically - change ONLY what's broken, preserve working\nlogic."
+                                        description: "Complete corrected code. EVERY error from think Section 1 MUST be\naddressed. Implement:\n\n- Field name corrections in select() (exact database field names)\n- Type casts in transform() (Decimal\u2192Number, DateTime\u2192ISO)\n- Neighbor transformer reuse (replace inline logic if transformer exists)\n\nApply fixes surgically \u2014 change ONLY what's broken, preserve working\nlogic."
                                     },
                                     revise: {
                                         $ref: "#/components/schemas/IAutoBeRealizeTransformerCorrectApplication.IReviseProps",
-                                        description: "Revision and finalization phase.\n\nReviews the draft corrections and produces the final, error-free code\nthat maintains all business requirements."
+                                        description: "Reviews draft corrections and produces final error-free code."
                                     }
                                 },
                                 required: [
@@ -187,14 +187,14 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                     "draft",
                                     "revise"
                                 ],
-                                description: "Request to correct transformer implementation errors.\n\nExecutes three-phase error correction to resolve TypeScript compilation\nissues in transformer functions. Applies systematic fixes following think \u2192\ndraft \u2192 revise pattern to ensure error-free production code."
+                                description: "Correct transformer compilation errors via think/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: [
@@ -211,7 +211,7 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                                 "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: [
@@ -222,11 +222,11 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                                 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: [
@@ -235,32 +235,32 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                     "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."
                             },
                             "IAutoBeRealizeTransformerCorrectApplication.IReviseProps": {
                                 type: "object",
                                 properties: {
                                     review: {
                                         type: "string",
-                                        description: "Critical correction review and validation.\n\nMUST systematically verify using four checklists:\n\n1. Error Resolution - Confirm EVERY error from think Section 1 is fixed\n2. Root Cause Fix - Verify fixes address root causes (not workarounds/hacks)\n3. System Rules - Mandatory neighbor reuse, select (not include), proper\n   types\n4. No Regression - Confirm no NEW errors, Payload type matches select()\n\nIdentify any remaining issues with line numbers and root cause analysis.\nCatch Band-Aid fixes (any casts, type assertions) that hide real\nproblems."
+                                        description: "MUST systematically verify four checklists:\n\n1. Error Resolution \u2014 confirm EVERY error from think Section 1 is fixed\n2. Root Cause Fix \u2014 verify fixes address root causes (not workarounds/hacks)\n3. System Rules \u2014 neighbor reuse, select (not include), proper types\n4. No Regression \u2014 confirm no NEW errors, Payload type matches select()\n\nCatch Band-Aid fixes (any casts, type assertions) that hide real\nproblems."
                                     },
                                     final: {
                                         oneOf: [
@@ -271,7 +271,7 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                                 type: "string"
                                             }
                                         ],
-                                        description: "Final error-free transformer code with all corrections applied.\n\nApply ALL remaining fixes identified in the review to produce\ncompilation-ready code. If review found issues (workarounds, new errors),\nthis MUST contain proper fixes.\n\nReturn `null` ONLY if draft is already perfect and review found zero\nissues."
+                                        description: "Final error-free code with all corrections applied, or null if draft\nneeds no changes."
                                     }
                                 },
                                 required: [
@@ -295,7 +295,7 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                     }
                                 }
                             ],
-                            description: "Process transformer correction task or preliminary data requests.\n\nSystematically analyzes and corrects TypeScript compilation errors in\ntransformer functions through three-phase workflow (think \u2192 draft \u2192\nrevise). Maintains business logic integrity while resolving all compilation\nissues."
+                            description: "Process transformer correction task or preliminary data requests."
                         }
                     ]
                 },
@@ -516,11 +516,11 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                 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 (getDatabaseSchemas):\n\n- What critical information is missing that you don't already have?\n- Why do you need it specifically right now?\n- Be brief - state the gap, don't list everything you have.\n\nFor completion (complete):\n\n- What key assets did you acquire?\n- What did you accomplish?\n- Why is it sufficient to complete?\n- Summarize - don't enumerate every single item.\n\nThis reflection helps you avoid duplicate requests and premature\ncompletion.",
+                                        description: "Think before you act.\n\nFor preliminary requests: what critical information is missing?\n\nFor completion: what did you acquire, what did you accomplish, why is it\nsufficient? Summarize \u2014 don't enumerate every single item.",
                                         type: "string"
                                     },
                                     request: {
-                                        description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval\n(getDatabaseSchemas) or final error correction (complete). When\npreliminary returns empty array, that type is removed from the union,\nphysically preventing repeated calls.",
+                                        description: "Action to perform. Exhausted preliminary types are removed from the\nunion, physically preventing repeated calls.",
                                         anyOf: [
                                             {
                                                 $ref: "#/$defs/IAutoBePreliminaryGetDatabaseSchemas"
@@ -545,18 +545,18 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                 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"
@@ -570,40 +570,40 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                         ]
                                     },
                                     "IAutoBeRealizeTransformerCorrectApplication.IComplete": {
-                                        description: "Request to correct transformer implementation errors.\n\nExecutes three-phase error correction to resolve TypeScript compilation\nissues in transformer functions. Applies systematic fixes following think \u2192\ndraft \u2192 revise pattern to ensure error-free production code.",
+                                        description: "Correct transformer compilation errors via think/draft/revise.",
                                         type: "object",
                                         properties: {
                                             type: {
-                                                description: "Type discriminator for the request.\n\nDetermines which action to perform: preliminary data retrieval or actual\ntask execution. Value \"complete\" indicates this is the final task\nexecution request.",
+                                                description: "Type discriminator for completion request.",
                                                 type: "string",
                                                 "enum": [
                                                     "complete"
                                                 ]
                                             },
                                             think: {
-                                                description: "Systematic error analysis and correction strategy.\n\nMUST contain thorough analysis with these four mandatory sections:\n\n1. Error Inventory - Categorize ALL compilation errors by root cause type\n2. Root Cause Analysis - Identify WHY each error occurs (wrong field, wrong\n   transform, etc.)\n3. Schema Verification - Cross-check error-related fields against actual\n   database schema\n4. Correction Strategy - Specific fix for each error in BOTH select() and\n   transform()\n\nThis forces you to understand the REAL problem (not guess) and plan\nsurgical fixes that address root causes, not symptoms.",
+                                                description: "Systematic error analysis. MUST contain four sections:\n\n1. Error Inventory \u2014 categorize ALL compilation errors by root cause\n2. Root Cause Analysis \u2014 identify WHY each error occurs (wrong field, wrong\n   transform, etc.)\n3. Schema Verification \u2014 cross-check error-related fields against actual\n   database schema\n4. Correction Strategy \u2014 specific fix for each error in BOTH select() and\n   transform()\n\nThis forces you to understand the REAL problem (not guess) and plan\nsurgical fixes that address root causes, not symptoms.",
                                                 type: "string"
                                             },
                                             selectMappings: {
-                                                description: "Database field-by-field selection mapping verification for the select()\nfunction.\n\nReview which database fields/relations are being selected to identify\nmissing selections or incorrect field names that cause compilation\nerrors.\n\nFor each database field needed by transform(), document:\n\n- `member`: Exact database field/relation name (snake_case) - verify\n  against 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`: Current state + correction plan (\"No change needed\", \"Fix: wrong\n  field name\", etc.)\n\nThe `kind` property helps identify selection syntax errors (e.g., using\n`field: true` for a relation instead of nested select).\n\nThe `nullable` property helps catch nullability mismatch errors in\ntransform().\n\n**Common selection errors to identify**:\n\n- Wrong field name (typo or doesn't exist in schema)\n- Missing required field (transform() uses it but select() doesn't fetch\n  it)\n- Wrong selection syntax (true for relation, or nested select for scalar)\n- Selecting field that doesn't exist in database model\n- Missing aggregation (_count, _sum) when transform() needs it\n\nThis structured verification:\n\n- Catches missing field selections before runtime\n- Identifies field name typos by comparing with schema\n- Ensures select() provides all data transform() needs\n- Documents what corrections are needed for selection logic\n- Prevents \"field not found\" errors\n\nThe validator will cross-check this against the database schema to ensure\nall field names are valid and complete coverage.\n\n**Note**: If compilation succeeds, select() is typically correct. This\nmapping is mainly for cases where select() has errors (wrong field names,\nmissing selections).",
+                                                description: "Selection mapping verification for select(). For each database field\nneeded by transform(), document:\n\n- `member`: Exact Prisma field/relation name (snake_case) \u2014 verify against\n  the Relation Mapping Table and member list\n- `kind`: scalar, belongsTo, hasOne, or hasMany\n- `nullable`: true/false for scalar/belongsTo, null for hasMany/hasOne\n- `how`: Current state + correction plan (\"No change needed\", \"Fix: wrong\n  field name\", etc.)\n\n**Common selection errors to identify**:\n\n- Wrong field name (typo or doesn't exist in schema)\n- Missing required field (transform() uses it but select() doesn't)\n- Wrong syntax (true for relation, or nested select for scalar)\n\nMissing even a single required field will cause validation failure.",
                                                 type: "array",
                                                 items: {
                                                     $ref: "#/$defs/AutoBeRealizeTransformerSelectMapping"
                                                 }
                                             },
                                             transformMappings: {
-                                                description: "DTO property-by-property mapping verification for the transform()\nfunction.\n\nReview EVERY property from the DTO type definition to ensure correct\ntransformation in the transform() function. This systematic approach\ncatches errors beyond what the compiler reports and prevents new issues.\n\nFor each DTO property in transform(), document:\n\n- `property`: Exact DTO property name (camelCase)\n- `how`: Current state + correction plan (\"No change needed\", \"Fix:\n  [problem] \u2192 [solution]\", etc.)\n\nEven properties without errors should be included with \"No change needed\"\nto ensure complete review. Missing even a single property could hide\nbugs.\n\nThis structured verification:\n\n- Catches silent errors compiler didn't report\n- Ensures no properties accidentally omitted in transform()\n- Documents transformation corrections explicitly\n- Verifies transform() logic correctness\n- Prevents regression in working transformations\n\n**Common correction scenarios in transform()**:\n\n- Missing type conversion (Decimal \u2192 Number, DateTime \u2192 ISO)\n- Wrong property name (DTO vs database mismatch)\n- Inline transformation when neighbor transformer exists\n- Missing computed property\n- Wrong nullable handling (DateTime? \u2192 string | null)\n- Fabricated property not in DTO\n- Missing property from DTO\n- Missing await for async transformers\n\nThe validator will cross-check this against the DTO type definition to\nensure nothing was overlooked.\n\n**Note**: This mapping is ONLY for the transform() function. The select()\nfunction is typically correct if compilation succeeds, as it's\nstructurally simpler.",
+                                                description: "Transform mapping verification. MUST include EVERY DTO property.\n\n- `property`: Exact DTO property name (camelCase)\n- `how`: Current state + correction plan (\"No change needed\", \"Fix:\n  [problem] \u2192 [solution]\")\n\nEven correct properties must be included with \"No change needed\" to\nensure complete review.\n\nMissing even a single property will cause validation failure.",
                                                 type: "array",
                                                 items: {
                                                     $ref: "#/$defs/AutoBeRealizeTransformerTransformMapping"
                                                 }
                                             },
                                             draft: {
-                                                description: "Initial correction implementation.\n\nComplete corrected code that applies ALL fixes from the think phase\nstrategy. EVERY error in think Section 1 inventory MUST be addressed.\nImplement:\n\n- Field name corrections in select() (exact database field names)\n- Type casts in transform() (Decimal\u2192Number, DateTime\u2192ISO)\n- Neighbor transformer reuse (replace inline logic if transformer exists)\n- Function order fix (transform \u2192 select \u2192 Payload)\n\nApply fixes surgically - change ONLY what's broken, preserve working\nlogic.",
+                                                description: "Complete corrected code. EVERY error from think Section 1 MUST be\naddressed. Implement:\n\n- Field name corrections in select() (exact database field names)\n- Type casts in transform() (Decimal\u2192Number, DateTime\u2192ISO)\n- Neighbor transformer reuse (replace inline logic if transformer exists)\n\nApply fixes surgically \u2014 change ONLY what's broken, preserve working\nlogic.",
                                                 type: "string"
                                             },
                                             revise: {
-                                                description: "Revision and finalization phase.\n\nReviews the draft corrections and produces the final, error-free code\nthat maintains all business requirements.",
+                                                description: "Reviews draft corrections and produces final error-free code.",
                                                 $ref: "#/$defs/IAutoBeRealizeTransformerCorrectApplication.IReviseProps"
                                             }
                                         },
@@ -617,15 +617,15 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                         ]
                                     },
                                     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",
@@ -635,7 +635,7 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                                 ]
                                             },
                                             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"
@@ -646,7 +646,7 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                                 ]
                                             },
                                             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"
                                             }
                                         },
@@ -658,15 +658,15 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                         ]
                                     },
                                     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"
                                             }
                                         },
@@ -679,11 +679,11 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                         type: "object",
                                         properties: {
                                             review: {
-                                                description: "Critical correction review and validation.\n\nMUST systematically verify using four checklists:\n\n1. Error Resolution - Confirm EVERY error from think Section 1 is fixed\n2. Root Cause Fix - Verify fixes address root causes (not workarounds/hacks)\n3. System Rules - Mandatory neighbor reuse, select (not include), proper\n   types\n4. No Regression - Confirm no NEW errors, Payload type matches select()\n\nIdentify any remaining issues with line numbers and root cause analysis.\nCatch Band-Aid fixes (any casts, type assertions) that hide real\nproblems.",
+                                                description: "MUST systematically verify four checklists:\n\n1. Error Resolution \u2014 confirm EVERY error from think Section 1 is fixed\n2. Root Cause Fix \u2014 verify fixes address root causes (not workarounds/hacks)\n3. System Rules \u2014 neighbor reuse, select (not include), proper types\n4. No Regression \u2014 confirm no NEW errors, Payload type matches select()\n\nCatch Band-Aid fixes (any casts, type assertions) that hide real\nproblems.",
                                                 type: "string"
                                             },
                                             final: {
-                                                description: "Final error-free transformer code with all corrections applied.\n\nApply ALL remaining fixes identified in the review to produce\ncompilation-ready code. If review found issues (workarounds, new errors),\nthis MUST contain proper fixes.\n\nReturn `null` ONLY if draft is already perfect and review found zero\nissues.",
+                                                description: "Final error-free code with all corrections applied, or null if draft\nneeds no changes.",
                                                 anyOf: [
                                                     {
                                                         type: "null"
@@ -701,7 +701,7 @@ const orchestrateRealizeTransformerCorrectOverall = (ctx, props) => __awaiter(vo
                                     }
                                 }
                             },
-                            description: "Process transformer correction task or preliminary data requests.\n\nSystematically analyzes and corrects TypeScript compilation errors in\ntransformer functions through three-phase workflow (think \u2192 draft \u2192\nrevise). Maintains business logic integrity while resolving all compilation\nissues.",
+                            description: "Process transformer correction task or preliminary data requests.",
                             validate: (() => { const _io0 = input => "string" === typeof input.thinking && ("object" === typeof input.request && null !== input.request && _iu0(input.request)); const _io1 = input => "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.think && (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);