@autobe/agent 0.30.4 → 0.30.5

package/lib/orchestrate/prisma/structures/IAutoBeDatabaseSchemaReviewApplication.d.ts

@@ -4,122 +4,45 @@ import { IAutoBePreliminaryGetDatabaseSchemas } from "../../common/structures/IA
 import { IAutoBePreliminaryGetPreviousAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetPreviousAnalysisSections";
 import { IAutoBePreliminaryGetPreviousDatabaseSchemas } from "../../common/structures/IAutoBePreliminaryGetPreviousDatabaseSchemas";
 export interface IAutoBeDatabaseSchemaReviewApplication {
-    /**
-     * Process schema review task or preliminary data requests.
-     *
-     * Reviews generated database models to validate normalization, relationships,
-     * indexes, and business alignment, producing necessary modifications.
-     *
-     * @param props Request containing either preliminary data request or complete
-     *   task
-     */
+    /** Process schema review task or retrieve preliminary data. */
     process(props: IAutoBeDatabaseSchemaReviewApplication.IProps): void;
 }
 export declare namespace IAutoBeDatabaseSchemaReviewApplication {
     interface IProps {
         /**
-         * Think before you act.
-         *
-         * Before requesting preliminary data or completing your task, reflect on
-         * your current state and explain your reasoning:
-         *
-         * For preliminary requests (getAnalysisSections, getDatabaseSchemas, etc.):
-         *
-         * - What critical information is missing that you don't already have?
-         * - Why do you need it specifically right now?
-         * - Be brief - state the gap, don't list everything you have.
-         *
-         * For completion (complete):
-         *
-         * - What key assets did you acquire?
-         * - What did you accomplish?
-         * - Why is it sufficient to complete?
-         * - Summarize - don't enumerate every single item.
-         *
-         * This reflection helps you avoid duplicate requests and premature
-         * completion.
+         * Reasoning about your current state: what's missing (preliminary) or what
+         * you accomplished (completion).
          */
         thinking: string;
         /**
-         * Type discriminator for the request.
-         *
-         * Determines which action to perform: preliminary data retrieval
-         * (getAnalysisSections, getPreviousAnalysisSections, getDatabaseSchemas,
-         * getPreviousDatabaseSchemas) or final schema review (complete). When
-         * preliminary returns empty array, that type is removed from the union,
-         * physically preventing repeated calls.
+         * Action to perform. Exhausted preliminary types are removed from the
+         * union.
          */
         request: IComplete | IAutoBePreliminaryGetAnalysisSections | IAutoBePreliminaryGetDatabaseSchemas | IAutoBePreliminaryGetPreviousAnalysisSections | IAutoBePreliminaryGetPreviousDatabaseSchemas;
     }
     /**
-     * Request to review and refine database schema models.
-     *
-     * Executes comprehensive schema review to validate design quality and
-     * identify necessary improvements for normalization, relationships, and
-     * performance optimization.
+     * Review and refine database schema models for normalization, relationships,
+     * and performance.
      */
     interface IComplete {
-        /**
-         * Type discriminator for the request.
-         *
-         * Determines which action to perform: preliminary data retrieval or actual
-         * task execution. Value "complete" indicates this is the final task
-         * execution request.
-         */
+        /** Type discriminator for completion request. */
         type: "complete";
         /**
-         * Comprehensive review analysis of the schema.
-         *
-         * Contains detailed evaluation of the schema design including:
-         *
-         * - Normalization validation: Confirms 3NF compliance and proper data
-         *   structure
-         * - Relationship integrity: Validates foreign key references and cardinality
-         * - Performance optimization: Reviews indexing strategy and query patterns
-         * - Business logic alignment: Ensures schema supports all use cases
-         * - Naming conventions: Verifies consistent naming patterns
-         * - Data type consistency: Confirms appropriate field types
-         * - Temporal field handling: Validates audit trail implementation
-         *
-         * The review identifies potential issues and confirms adherence to best
-         * practices before final implementation.
+         * Review analysis covering normalization, relationships, indexes, naming,
+         * and business alignment.
          */
         review: string;
         /**
-         * Strategic database design plan.
-         *
-         * Contains the original planning document outlining the database
-         * architecture strategy including table structures, relationships,
-         * normalization approach, and business requirement mapping. This plan
-         * serves as the blueprint for validating the implemented schema.
-         *
-         * Planning components:
-         *
-         * - Business requirements: Mapping of business needs to database structures
-         * - Table design: Entity definitions and attribute specifications
-         * - Relationship strategy: Cardinality and referential integrity planning
-         * - Normalization approach: Application of 1NF, 2NF, 3NF principles
-         * - Performance considerations: Index strategy and query optimization
-         * - Snapshot architecture: Temporal data handling and audit requirements
-         * - Materialized views: Denormalization strategy for performance
+         * Database design plan serving as the blueprint for validating the
+         * implemented schema.
          */
         plan: string;
         /**
-         * Corrected schema definition based on review feedback, or null if no
-         * changes are needed.
-         *
-         * When not null, the definition carries exactly one corrected
-         * {@link AutoBeDatabaseSchemaDefinition.model} for the reviewed target table
-         * so that the output stays within the LLM's maximum output token limit. If
-         * the review determines that additional child tables are required (e.g. 1NF
-         * decomposition), they are declared in
-         * {@link AutoBeDatabaseSchemaDefinition.newDesigns} as lightweight name +
-         * description pairs and will be generated by their own dedicated pipeline
-         * calls.
+         * Corrected schema definition, or null if no changes are needed.
          *
-         * If null, the original model remains unchanged from the original schema.
-         * If not null, the modification must resolve issues identified in the
-         * review.
+         * When not null, carries exactly one corrected
+         * {@link AutoBeDatabaseSchemaDefinition.model}. Additional child tables go
+         * in {@link AutoBeDatabaseSchemaDefinition.newDesigns}.
          */
         content: AutoBeDatabaseSchemaDefinition | null;
     }

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

@@ -35,7 +35,7 @@ function transformRealizeOperationCorrectHistory(props) {
             {
                 id: (0, uuid_1.v7)(),
                 type: "systemMessage",
-                text: "<!--\nfilename: REALIZE_OPERATION_CORRECT.md\n-->\n# Realize Correction Agent\n\nYou fix **TypeScript compilation errors** in provider functions. Refer to the Realize Coder Agent prompt for all coding rules and patterns \u2014 this prompt covers only the correction workflow.\n\n**Function calling is MANDATORY** - call the provided function immediately when ready.\n\n## 1. Execution Strategy\n\n1. **Analyze**: Review TypeScript diagnostics and identify error patterns\n2. **Request Context** (if needed): Use `getDatabaseSchemas`, `getRealizeCollectors`, `getRealizeTransformers`\n3. **Execute**: Call `process({ request: { type: \"complete\", think, draft, revise } })` after analysis\n\n**PROHIBITIONS**:\n- \u274C NEVER call complete in parallel with preliminary requests\n- \u274C NEVER ask for user permission or present a plan\n- \u274C NEVER respond with text when all requirements are met\n\n## 2. Chain of Thought: `thinking` Field\n\n```typescript\n// Preliminary - state what's missing\nthinking: \"Need schema fields to fix type errors. Don't have them.\"\n\n// Completion - summarize accomplishment\nthinking: \"Fixed all 12 TypeScript errors, code compiles successfully.\"\n```\n\n## 3. Output Format\n\n```typescript\nexport namespace IAutoBeRealizeOperationCorrectApplication {\n  export interface IComplete {\n    type: \"complete\";\n    think: string;   // Error analysis and strategy\n    draft: string;   // Initial correction attempt\n    revise: {\n      review: string;        // Validation analysis\n      final: string | null;  // Final code (null if draft is sufficient)\n    };\n  }\n}\n```\n\n**CRITICAL**: No import statements - start directly with `export async function...`\n\n**CRITICAL**: The function name, parameter types, and return type are given by the system \u2014 preserve them exactly. Fix errors in the **implementation body**, not by altering the signature (e.g., adding `| null` to the return type).\n\n## 4. Common Error Patterns\n\n### 4.1. Error 2353: \"Field does not exist in type\"\n\n```typescript\n// ERROR: 'username' does not exist\nwhere: { username: { contains: term } }\n\n// FIX: Remove or rename to actual field\nwhere: { name: { contains: term } }  // Use correct field from schema\n```\n\n### 4.2. Error 2322: Type Assignment Errors\n\n| Pattern | Fix |\n|---------|-----|\n| `string \\| null` \u2192 `string` | `value ?? \"\"` |\n| `Date` \u2192 `string` | `value.toISOString()` |\n| `Date` \u2192 `string & Format<\"date-time\">` | `value.toISOString()` \u2014 this is the most common TS2322; Prisma returns `Date`, DTO expects `string` |\n| `Decimal` \u2192 `number` | `Number(value)` |\n| `string \\| null` \u2192 `string & Format<\"date-time\">` | `(date ?? contextualDefault).toISOString()` \u2014 analyze field semantics (e.g., `expired_at` null = unlimited \u2192 far-future, NOT `new Date()`) |\n| `number & Type<\"int32\">` \u2192 `Minimum<0>` | `value satisfies number as number` |\n\n**Most frequent TS2322**: `Type 'Date' is not assignable to type 'string & Format<\"date-time\">'`. Every Prisma `DateTime` field returns a `Date` object. When building a DTO return object, ALWAYS call `.toISOString()`:\n\n```typescript\n// \u274C WRONG \u2014 causes TS2322\ncreated_at: record.created_at,              // Date from Prisma\nupdated_at: new Date(),                     // Date object\n\n// \u2705 FIX\ncreated_at: record.created_at.toISOString(),\nupdated_at: new Date().toISOString(),\ndeleted_at: record.deleted_at?.toISOString() ?? null,  // nullable\n```\n\n### 4.3. Error 2339: Property Not in Select\n\n`Property 'X' does not exist on type` \u2014 if the object comes from a Prisma query with `select`, check whether `X` is included in the select clause. Also check for typos or table-name/property-name confusion (see 4.5).\n\n**Diagnosis**: Find the query producing the object, then add the missing property:\n\n| What's missing | Add to select |\n|----------------|---------------|\n| Scalar field | `fieldName: true` |\n| Relation | `relation: { select: { ... } }` or `relation: Transformer.select()` |\n| Aggregate count | `_count: { select: { relation: true } }` |\n\n```typescript\n// \u274C ERROR: Property 'author' does not exist on type '{ id: string; title: string; }'\nconst article = await MyGlobal.prisma.bbs_articles.findUniqueOrThrow({\n  where: { id },\n  select: { id: true, title: true }  // 'author' not selected\n});\nreturn { author: article.author };  // \u274C\n\n// \u2705 FIX: Add the relation to select\nconst article = await MyGlobal.prisma.bbs_articles.findUniqueOrThrow({\n  where: { id },\n  select: {\n    id: true,\n    title: true,\n    author: { select: { id: true, name: true } },  // \u2705 Added\n  }\n});\n```\n\n### 4.4. Null vs Undefined Conversion\n\n```typescript\n// Check the ACTUAL interface definition\ninterface IExample {\n  fieldA?: string;           // Optional \u2192 use undefined\n  fieldB: string | null;     // Nullable \u2192 use null\n}\n\n// Apply correct pattern\nreturn {\n  fieldA: dbValue === null ? undefined : dbValue,  // Optional field\n  fieldB: dbValue ?? null,                          // Nullable field\n};\n```\n\n### 4.5. Table Name Instead of Relation Property Name\n\nGiven this Prisma schema:\n\n```prisma\nmodel bbs_article_comments {\n  //----\n  // COLUMNS\n  //----\n  id              String    @id @db.Uuid\n  bbs_article_id  String    @db.Uuid\n  bbs_user_id     String    @db.Uuid\n  body            String\n  created_at      DateTime  @db.Timestamptz\n\n  //----\n  // BELONGED RELATIONS\n  //   - format: (propertyKey targetModel constraint)\n  //----\n  article         bbs_articles              @relation(fields: [bbs_article_id], references: [id], onDelete: Cascade)\n  user            bbs_users                 @relation(fields: [bbs_user_id], references: [id], onDelete: Cascade)\n\n  //----\n  // HAS RELATIONS\n  //   - format: (propertyKey targetModel)\n  //----\n  files           bbs_article_comment_files[]\n  hits            bbs_article_comment_hits[]\n}\n```\n\n```typescript\n// \u274C ERROR: 'bbs_article_comment_files' does not exist on type CreateInput\nbbs_article_comment_files: {\n  create: await ArrayUtil.asyncMap(...)\n},\n\n// \u2705 FIX: Use the relation property name (left side of the definition)\n// Given: files  bbs_article_comment_files[]\nfiles: {\n  create: await ArrayUtil.asyncMap(...)\n},\n```\n\n### 4.6. Unwrapping Transformer.select() with `.select`\n\n```typescript\n// \u274C ERROR: Type mismatch \u2014 .select strips the wrapper\nselect: {\n  user: BbsUserAtSummaryTransformer.select().select,\n  files: BbsArticleCommentFileTransformer.select().select,\n}\n\n// \u2705 FIX: Assign select() directly \u2014 it already returns { select: {...} }\nselect: {\n  user: BbsUserAtSummaryTransformer.select(),\n  files: BbsArticleCommentFileTransformer.select(),\n}\n```\n\n### 4.7. M:N Join Table \u2014 Table Name + `.select` Unwrap Compound Error\n\n```typescript\n// \u274C ERROR: Table name + .select unwrap\nbbs_article_tags: {\n  select: { tag: BbsTagAtSummaryTransformer.select().select },\n},\n\n// \u2705 FIX: Relation property name + direct select() + satisfies\narticleTags: {\n  select: { tag: BbsTagAtSummaryTransformer.select() },\n} satisfies Prisma.bbs_article_tagsFindManyArgs,\n```\n\n### 4.8. Optional Nullable Field Narrowing\n\nDTO fields typed `field?: T | null | undefined` carry three states (common in Update DTOs, but not exclusive). Checking only `!== undefined` leaves `null` in the type:\n\n```typescript\n// \u274C ERROR: narrowed to T | null, not T\nif (props.body.start_date !== undefined) {\n  Date.parse(props.body.start_date); // TS2345: '... | null' not assignable to 'string'\n}\n\n// \u2705 FIX: check both\nif (props.body.start_date !== undefined && props.body.start_date !== null) {\n  Date.parse(props.body.start_date); // OK\n}\n```\n\n### 4.9. Error 2339: Hallucinated DTO Property\n\n`Property 'X' does not exist on type 'ICreate'` (or `IUpdate`, `IRequest`) \u2014 the code accesses a property on `props.body` that was never declared in the DTO interface. **This is NOT a select issue** \u2014 the property simply doesn't exist in the type definition.\n\n**Diagnosis**: The original code invented a property that \"makes sense\" but isn't part of the API contract. The fix is to **remove the access** and derive the value from other sources.\n\n```typescript\n// \u274C ERROR: Property 'orderItemId' does not exist on type 'IShoppingSaleReview.ICreate'\nconst item = await MyGlobal.prisma.shopping_order_items.findUniqueOrThrow({\n  where: { id: props.body.orderItemId },  // Not in ICreate\n});\n\n// \u2705 FIX: Use path parameter instead\nconst sale = await MyGlobal.prisma.shopping_sales.findUniqueOrThrow({\n  where: { id: props.saleId },  // Path parameter from function signature\n  select: { id: true },\n});\n```\n\n| Where the value actually lives | Example |\n|-------------------------------|---------|\n| Path parameter | `props.saleId`, `props.articleId` |\n| Auth context | `props.customer.id`, `props.seller.id` |\n| Database lookup | Query by a known ID from params |\n| Computed from existing fields | Derive from other `props.body.*` properties |\n\n**Key distinction from 4.3**: Section 4.3 fixes TS2339 on Prisma query results (add to `select`). This section fixes TS2339 on `props.body` / `props.customer` (remove the access, use another source).\n\n## 5. Unrecoverable Errors\n\nWhen schema-API mismatch is fundamental:\n\n```typescript\n/**\n * [Original Description]\n *\n * Cannot implement: Schema missing [field_name] required by API.\n */\nexport async function method__path(props: {...}): Promise<IResponse> {\n  return typia.random<IResponse>();\n}\n```\n\n## 6. Quick Reference\n\n| Error | First Try | Alternative |\n|-------|-----------|-------------|\n| 2353 (field doesn't exist) | DELETE the field | Use correct field name |\n| 2322 (null \u2192 string) | Add `?? \"\"` | Check if optional |\n| 2322 (Date \u2192 string) | `.toISOString()` | - |\n| 2322 (string \\| null \u2192 string) | `(date ?? contextualDefault).toISOString()` | Analyze field semantics for default |\n| Tag type mismatch | `value satisfies number as number` | - |\n| 2339 (on query result) | Add to select | Scalar: `true`, Relation: `{ select: {...} }` |\n| 2339 (on `props.body.X`) | Remove access, use path params/auth context | NOT a select issue \u2014 property doesn't exist in DTO |\n| 2345 (`T \\| null` \u2192 `T`) | Check `!== undefined && !== null` | Optional nullable field |\n| 2345 (string \u2192 literal) | `as \"literal\"` | - |\n| Table name in query | Use relation property name | Check Prisma schema |\n| `.select().select` | Remove trailing `.select` | - |\n| Type validation code | **DELETE IT** | No alternative |\n\n## 7. Final Checklist\n\n### Compiler Authority\n- [ ] NO compiler errors remain\n- [ ] Compiler's judgment is FINAL\n\n### Runtime Validation (MUST DELETE)\n- [ ] Deleted ALL `typeof` checks\n- [ ] Deleted ALL `String.trim()` validation\n- [ ] Deleted ALL length checks on parameters\n- [ ] NO type checking logic remains\n\n### Prisma Operations\n- [ ] Used relation property names (NOT table names or FK columns)\n- [ ] `satisfies Prisma.{table}FindManyArgs` on inline nested selects\n- [ ] Transformer.select() assigned directly (NOT `.select().select`)\n- [ ] Select includes all accessed fields (relations, scalars, FK columns)\n\n### Parameter Types\n- [ ] No hallucinated `props.body.*` properties \u2014 only declared DTO fields\n- [ ] Missing values sourced from path params / auth context / DB queries\n\n### Code Quality\n- [ ] No import statements\n- [ ] Business logic preserved\n- [ ] Function signature preserved (no return type changes)" /* AutoBeSystemPromptConstant.REALIZE_OPERATION_CORRECT */,
+                text: "<!--\nfilename: REALIZE_OPERATION_CORRECT.md\n-->\n# Realize Correction Agent\n\nYou fix **TypeScript compilation errors** in provider functions. Refer to the Realize Coder Agent prompt for all coding rules and patterns \u2014 this prompt covers only the correction workflow.\n\n**Function calling is MANDATORY** - call the provided function immediately when ready.\n\n## 1. Execution Strategy\n\n1. **Analyze**: Review TypeScript diagnostics and identify error patterns\n2. **Request Context** (if needed): Use `getDatabaseSchemas`, `getRealizeCollectors`, `getRealizeTransformers`\n3. **Execute**: Call `process({ request: { type: \"complete\", think, draft, revise } })` after analysis\n\n**PROHIBITIONS**:\n- \u274C NEVER call complete in parallel with preliminary requests\n- \u274C NEVER ask for user permission or present a plan\n- \u274C NEVER respond with text when all requirements are met\n\n## 2. Chain of Thought: `thinking` Field\n\n```typescript\n// Preliminary - state what's missing\nthinking: \"Need schema fields to fix type errors. Don't have them.\"\n\n// Completion - summarize accomplishment\nthinking: \"Fixed all 12 TypeScript errors, code compiles successfully.\"\n```\n\n## 3. Output Format\n\n```typescript\nexport namespace IAutoBeRealizeOperationCorrectApplication {\n  export interface IComplete {\n    type: \"complete\";\n    think: string;   // Error analysis and strategy\n    draft: string;   // Initial correction attempt\n    revise: {\n      review: string;        // Validation analysis\n      final: string | null;  // Final code (null if draft is sufficient)\n    };\n  }\n}\n```\n\n**CRITICAL**: No import statements - start directly with `export async function...`\n\n**CRITICAL**: The function name, parameter types, and return type are given by the system \u2014 preserve them exactly. Fix errors in the **implementation body**, not by altering the signature (e.g., adding `| null` to the return type).\n\n## 4. Common Error Patterns\n\n### 4.1. Error 2353: \"Field does not exist in type\"\n\n```typescript\n// ERROR: 'username' does not exist\nwhere: { username: { contains: term } }\n\n// FIX: Remove or rename to actual field\nwhere: { name: { contains: term } }  // Use correct field from schema\n```\n\n### 4.2. Error 2322: Type Assignment Errors\n\n| Pattern | Fix |\n|---------|-----|\n| `string \\| null` \u2192 `string` | `value ?? \"\"` |\n| `Date` \u2192 `string` | `value.toISOString()` |\n| `Date` \u2192 `string & Format<\"date-time\">` | `value.toISOString()` \u2014 this is the most common TS2322; Prisma returns `Date`, DTO expects `string` |\n| `Decimal` \u2192 `number` | `Number(value)` |\n| `string \\| null` \u2192 `string & Format<\"date-time\">` | `(date ?? contextualDefault).toISOString()` \u2014 analyze field semantics (e.g., `expired_at` null = unlimited \u2192 far-future, NOT `new Date()`) |\n| `number & Type<\"int32\">` \u2192 `Minimum<0>` | `value satisfies number as number` |\n\n**Most frequent TS2322**: `Type 'Date' is not assignable to type 'string & Format<\"date-time\">'`. Every Prisma `DateTime` field returns a `Date` object. When building a DTO return object, ALWAYS call `.toISOString()`:\n\n```typescript\n// \u274C WRONG \u2014 causes TS2322\ncreated_at: record.created_at,              // Date from Prisma\nupdated_at: new Date(),                     // Date object\n\n// \u2705 FIX\ncreated_at: record.created_at.toISOString(),\nupdated_at: new Date().toISOString(),\ndeleted_at: record.deleted_at?.toISOString() ?? null,  // nullable\n```\n\n### 4.3. Error 2339: Property Not in Select\n\n`Property 'X' does not exist on type` \u2014 if the object comes from a Prisma query with `select`, check whether `X` is included in the select clause. Also check for typos or table-name/property-name confusion (see 4.5).\n\n**Diagnosis**: Find the query producing the object, then add the missing property:\n\n| What's missing | Add to select |\n|----------------|---------------|\n| Scalar field | `fieldName: true` |\n| Relation | `relation: { select: { ... } }` or `relation: Transformer.select()` |\n| Aggregate count | `_count: { select: { relation: true } }` |\n\n```typescript\n// \u274C ERROR: Property 'author' does not exist on type '{ id: string; title: string; }'\nconst article = await MyGlobal.prisma.bbs_articles.findUniqueOrThrow({\n  where: { id },\n  select: { id: true, title: true }  // 'author' not selected\n});\nreturn { author: article.author };  // \u274C\n\n// \u2705 FIX: Add the relation to select\nconst article = await MyGlobal.prisma.bbs_articles.findUniqueOrThrow({\n  where: { id },\n  select: {\n    id: true,\n    title: true,\n    author: { select: { id: true, name: true } },  // \u2705 Added\n  }\n});\n```\n\n### 4.4. Null vs Undefined Conversion\n\n```typescript\n// Check the ACTUAL interface definition\ninterface IExample {\n  fieldA?: string;           // Optional \u2192 use undefined\n  fieldB: string | null;     // Nullable \u2192 use null\n}\n\n// Apply correct pattern\nreturn {\n  fieldA: dbValue === null ? undefined : dbValue,  // Optional field\n  fieldB: dbValue ?? null,                          // Nullable field\n};\n```\n\n### 4.5. Table Name Instead of Relation Property Name\n\nGiven this Prisma schema:\n\n```prisma\nmodel bbs_article_comments {\n  //----\n  // COLUMNS\n  //----\n  id              String    @id @db.Uuid\n  bbs_article_id  String    @db.Uuid\n  bbs_user_id     String    @db.Uuid\n  body            String\n  created_at      DateTime  @db.Timestamptz\n\n  //----\n  // BELONGED RELATIONS\n  //   - format: (propertyKey targetModel constraint)\n  //----\n  article         bbs_articles              @relation(fields: [bbs_article_id], references: [id], onDelete: Cascade)\n  user            bbs_users                 @relation(fields: [bbs_user_id], references: [id], onDelete: Cascade)\n\n  //----\n  // HAS RELATIONS\n  //   - format: (propertyKey targetModel)\n  //----\n  files           bbs_article_comment_files[]\n  hits            bbs_article_comment_hits[]\n}\n```\n\n```typescript\n// \u274C ERROR: 'bbs_article_comment_files' does not exist on type CreateInput\nbbs_article_comment_files: {\n  create: await ArrayUtil.asyncMap(...)\n},\n\n// \u2705 FIX: Use the relation property name (left side of the definition)\n// Given: files  bbs_article_comment_files[]\nfiles: {\n  create: await ArrayUtil.asyncMap(...)\n},\n```\n\n### 4.5.1. Verifying Relation Names Against Schema\n\nWhen TS2353 says `'X' does not exist in type 'YSelect'`:\n\n1. **X is NOT a valid relation name** for table Y\n2. Check the Relation Mapping Table in your context for the correct propertyKey\n3. Common confusions:\n   - Table name `shopping_categories` vs property name `category`\n   - FK column `shopping_seller_id` vs relation `seller`\n   - DTO name `orderItems` vs property name `items`\n4. After finding the correct name, update BOTH the `select` clause AND any `transform`/return code that references the relation\n\n### 4.6. Unwrapping Transformer.select() with `.select`\n\n```typescript\n// \u274C ERROR: Type mismatch \u2014 .select strips the wrapper\nselect: {\n  user: BbsUserAtSummaryTransformer.select().select,\n  files: BbsArticleCommentFileTransformer.select().select,\n}\n\n// \u2705 FIX: Assign select() directly \u2014 it already returns { select: {...} }\nselect: {\n  user: BbsUserAtSummaryTransformer.select(),\n  files: BbsArticleCommentFileTransformer.select(),\n}\n```\n\n### 4.7. M:N Join Table \u2014 Table Name + `.select` Unwrap Compound Error\n\n```typescript\n// \u274C ERROR: Table name + .select unwrap\nbbs_article_tags: {\n  select: { tag: BbsTagAtSummaryTransformer.select().select },\n},\n\n// \u2705 FIX: Relation property name + direct select() + satisfies\narticleTags: {\n  select: { tag: BbsTagAtSummaryTransformer.select() },\n} satisfies Prisma.bbs_article_tagsFindManyArgs,\n```\n\n### 4.8. Optional Nullable Field Narrowing\n\nDTO fields typed `field?: T | null | undefined` carry three states (common in Update DTOs, but not exclusive). Checking only `!== undefined` leaves `null` in the type:\n\n```typescript\n// \u274C ERROR: narrowed to T | null, not T\nif (props.body.start_date !== undefined) {\n  Date.parse(props.body.start_date); // TS2345: '... | null' not assignable to 'string'\n}\n\n// \u2705 FIX: check both\nif (props.body.start_date !== undefined && props.body.start_date !== null) {\n  Date.parse(props.body.start_date); // OK\n}\n```\n\n### 4.9. Error 2339: Hallucinated DTO Property\n\n`Property 'X' does not exist on type 'ICreate'` (or `IUpdate`, `IRequest`) \u2014 the code accesses a property on `props.body` that was never declared in the DTO interface. **This is NOT a select issue** \u2014 the property simply doesn't exist in the type definition.\n\n**Diagnosis**: The original code invented a property that \"makes sense\" but isn't part of the API contract. The fix is to **remove the access** and derive the value from other sources.\n\n```typescript\n// \u274C ERROR: Property 'orderItemId' does not exist on type 'IShoppingSaleReview.ICreate'\nconst item = await MyGlobal.prisma.shopping_order_items.findUniqueOrThrow({\n  where: { id: props.body.orderItemId },  // Not in ICreate\n});\n\n// \u2705 FIX: Use path parameter instead\nconst sale = await MyGlobal.prisma.shopping_sales.findUniqueOrThrow({\n  where: { id: props.saleId },  // Path parameter from function signature\n  select: { id: true },\n});\n```\n\n| Where the value actually lives | Example |\n|-------------------------------|---------|\n| Path parameter | `props.saleId`, `props.articleId` |\n| Auth context | `props.customer.id`, `props.seller.id` |\n| Database lookup | Query by a known ID from params |\n| Computed from existing fields | Derive from other `props.body.*` properties |\n\n**Key distinction from 4.3**: Section 4.3 fixes TS2339 on Prisma query results (add to `select`). This section fixes TS2339 on `props.body` / `props.customer` (remove the access, use another source).\n\n## 5. Unrecoverable Errors\n\nWhen schema-API mismatch is fundamental:\n\n```typescript\n/**\n * [Original Description]\n *\n * Cannot implement: Schema missing [field_name] required by API.\n */\nexport async function method__path(props: {...}): Promise<IResponse> {\n  return typia.random<IResponse>();\n}\n```\n\n## 6. Quick Reference\n\n| Error | First Try | Alternative |\n|-------|-----------|-------------|\n| 2353 (field doesn't exist) | DELETE the field | Use correct field name |\n| 2322 (null \u2192 string) | Add `?? \"\"` | Check if optional |\n| 2322 (Date \u2192 string) | `.toISOString()` | - |\n| 2322 (string \\| null \u2192 string) | `(date ?? contextualDefault).toISOString()` | Analyze field semantics for default |\n| Tag type mismatch | `value satisfies number as number` | - |\n| 2339 (on query result) | Add to select | Scalar: `true`, Relation: `{ select: {...} }` |\n| 2339 (on `props.body.X`) | Remove access, use path params/auth context | NOT a select issue \u2014 property doesn't exist in DTO |\n| 2345 (`T \\| null` \u2192 `T`) | Check `!== undefined && !== null` | Optional nullable field |\n| 2345 (string \u2192 literal) | `as \"literal\"` | - |\n| Table name in query | Use relation property name | Check Prisma schema |\n| `.select().select` | Remove trailing `.select` | - |\n| Type validation code | **DELETE IT** | No alternative |\n\n## 7. Final Checklist\n\n### Compiler Authority\n- [ ] NO compiler errors remain\n- [ ] Compiler's judgment is FINAL\n\n### Runtime Validation (MUST DELETE)\n- [ ] Deleted ALL `typeof` checks\n- [ ] Deleted ALL `String.trim()` validation\n- [ ] Deleted ALL length checks on parameters\n- [ ] NO type checking logic remains\n\n### Prisma Operations\n- [ ] Used relation property names (NOT table names or FK columns)\n- [ ] `satisfies Prisma.{table}FindManyArgs` on inline nested selects\n- [ ] Transformer.select() assigned directly (NOT `.select().select`)\n- [ ] Select includes all accessed fields (relations, scalars, FK columns)\n\n### Parameter Types\n- [ ] No hallucinated `props.body.*` properties \u2014 only declared DTO fields\n- [ ] Missing values sourced from path params / auth context / DB queries\n\n### Code Quality\n- [ ] No import statements\n- [ ] Business logic preserved\n- [ ] Function signature preserved (no return type changes)" /* AutoBeSystemPromptConstant.REALIZE_OPERATION_CORRECT */,
                 created_at: new Date().toISOString(),
             },
             ...(0, transformPreviousAndLatestCorrectHistory_1.transformPreviousAndLatestCorrectHistory)(props.failures.map((f) => ({

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

@@ -1 +1 @@
-{"version":3,"file":"transformRealizeOperationCorrectHistory.js","sourceRoot":"","sources":["../../../../src/orchestrate/realize/histories/transformRealizeOperationCorrectHistory.ts"],"names":[],"mappings":";;AAkBA,0FA2EC;AAxFD,yCAA2C;AAC3C,+BAA0B;AAM1B,8HAA2H;AAC3H,sGAAmG;AAGnG,mGAAgG;AAEhG,SAAgB,uCAAuC,CAAC,KAYvD;;IACC,MAAM,QAAQ,GAA4B,KAAK,CAAC,KAAK,CAAC,SAAU,CAAC,QAAQ,CAAC;IAC1E,MAAM,SAAS,GAA6B,QAAQ,CAAC,UAAU,CAAC,IAAI,CAClE,CAAC,CAAC,EAAE,EAAE,CACJ,CAAC,CAAC,MAAM,KAAK,KAAK,CAAC,QAAQ,CAAC,QAAQ,CAAC,MAAM;QAC3C,CAAC,CAAC,IAAI,KAAK,KAAK,CAAC,QAAQ,CAAC,QAAQ,CAAC,IAAI,CACzC,CAAC;IACH,MAAM,QAAQ,GACZ,mEAAgC,CAAC,WAAW,CAAC;QAC3C,cAAc,EAAE,KAAK,CAAC,cAAc;QACpC,SAAS;KACV,CAAC,CAAC;IACL,MAAM,cAAc,GAClB,IAAA,6EAAqC,EAAC;QACpC,KAAK,EAAE,KAAK,CAAC,KAAK;QAClB,QAAQ;QACR,aAAa,EAAE,MAAA,QAAQ,CAAC,cAAc,mCAAI,IAAI;QAC9C,mBAAmB,EAAE,KAAK,CAAC,cAAc;QACzC,GAAG,EAAE,KAAK,CAAC,GAAG;QACd,WAAW,EAAE,KAAK,CAAC,WAAW;KAC/B,CAAC,CAAC;IACL,OAAO;QACL,SAAS,EAAE;YACT,GAAG,cAAc,CAAC,SAAS;YAC3B;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,eAAe;gBACrB,IAAI,omUAAmD;aACxD;YACD;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,IAAI,EAAE,eAAe;gBACrB,IAAI,siXAAsD;gBAC1D,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;aACrC;YACD,GAAG,IAAA,mFAAwC,EACzC,KAAK,CAAC,QAAQ,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC;gBACzB,MAAM,EAAE,CAAC,CAAC,QAAQ,CAAC,OAAO;gBAC1B,WAAW,EAAE,CAAC,CAAC,WAAW;aAC3B,CAAC,CAAC,CACJ;SACF;QACD,WAAW,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;QAQxB,mEAAgC,CAAC,aAAa,CAAC;YAC/C,cAAc,EAAE,KAAK,CAAC,cAAc;YACpC,SAAS;YACT,OAAO,EAAE,KAAK,CAAC,KAAK,CAAC,SAAU,CAAC,QAAQ,CAAC,UAAU,CAAC,OAAO;SAC5D,CAAC;;;;QAIA,KAAK,CAAC,QAAQ,CAAC,OAAO;;KAEzB;KACF,CAAC;AACJ,CAAC"}
+{"version":3,"file":"transformRealizeOperationCorrectHistory.js","sourceRoot":"","sources":["../../../../src/orchestrate/realize/histories/transformRealizeOperationCorrectHistory.ts"],"names":[],"mappings":";;AAkBA,0FA2EC;AAxFD,yCAA2C;AAC3C,+BAA0B;AAM1B,8HAA2H;AAC3H,sGAAmG;AAGnG,mGAAgG;AAEhG,SAAgB,uCAAuC,CAAC,KAYvD;;IACC,MAAM,QAAQ,GAA4B,KAAK,CAAC,KAAK,CAAC,SAAU,CAAC,QAAQ,CAAC;IAC1E,MAAM,SAAS,GAA6B,QAAQ,CAAC,UAAU,CAAC,IAAI,CAClE,CAAC,CAAC,EAAE,EAAE,CACJ,CAAC,CAAC,MAAM,KAAK,KAAK,CAAC,QAAQ,CAAC,QAAQ,CAAC,MAAM;QAC3C,CAAC,CAAC,IAAI,KAAK,KAAK,CAAC,QAAQ,CAAC,QAAQ,CAAC,IAAI,CACzC,CAAC;IACH,MAAM,QAAQ,GACZ,mEAAgC,CAAC,WAAW,CAAC;QAC3C,cAAc,EAAE,KAAK,CAAC,cAAc;QACpC,SAAS;KACV,CAAC,CAAC;IACL,MAAM,cAAc,GAClB,IAAA,6EAAqC,EAAC;QACpC,KAAK,EAAE,KAAK,CAAC,KAAK;QAClB,QAAQ;QACR,aAAa,EAAE,MAAA,QAAQ,CAAC,cAAc,mCAAI,IAAI;QAC9C,mBAAmB,EAAE,KAAK,CAAC,cAAc;QACzC,GAAG,EAAE,KAAK,CAAC,GAAG;QACd,WAAW,EAAE,KAAK,CAAC,WAAW;KAC/B,CAAC,CAAC;IACL,OAAO;QACL,SAAS,EAAE;YACT,GAAG,cAAc,CAAC,SAAS;YAC3B;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,eAAe;gBACrB,IAAI,omUAAmD;aACxD;YACD;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,IAAI,EAAE,eAAe;gBACrB,IAAI,wmYAAsD;gBAC1D,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;aACrC;YACD,GAAG,IAAA,mFAAwC,EACzC,KAAK,CAAC,QAAQ,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC;gBACzB,MAAM,EAAE,CAAC,CAAC,QAAQ,CAAC,OAAO;gBAC1B,WAAW,EAAE,CAAC,CAAC,WAAW;aAC3B,CAAC,CAAC,CACJ;SACF;QACD,WAAW,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;QAQxB,mEAAgC,CAAC,aAAa,CAAC;YAC/C,cAAc,EAAE,KAAK,CAAC,cAAc;YACpC,SAAS;YACT,OAAO,EAAE,KAAK,CAAC,KAAK,CAAC,SAAU,CAAC,QAAQ,CAAC,UAAU,CAAC,OAAO;SAC5D,CAAC;;;;QAIA,KAAK,CAAC,QAAQ,CAAC,OAAO;;KAEzB;KACF,CAAC;AACJ,CAAC"}

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

@@ -22,7 +22,7 @@ const transformRealizeOperationWriteHistory = (props) => {
                 id: (0, uuid_1.v7)(),
                 created_at: new Date().toISOString(),
                 type: "systemMessage",
-                text: "<!--\nfilename: REALIZE_OPERATION_WRITE.md\n-->\n# Realize Coder Agent\n\nYou generate **production-grade TypeScript provider functions** for NestJS API operations.\n\n**Function calling is MANDATORY** - call the provided function immediately when ready.\n\n## 1. Execution Strategy\n\n1. **Analyze**: Review operation specification and DTO types\n2. **Request Context** (if needed): Use `getDatabaseSchemas`, `getRealizeCollectors`, `getRealizeTransformers`\n3. **Execute**: Call `process({ request: { type: \"complete\", plan, draft, revise } })` after gathering context\n\n**PROHIBITIONS**:\n- \u274C NEVER call complete in parallel with preliminary requests\n- \u274C NEVER ask for user permission or present a plan\n- \u274C NEVER respond with text when all requirements are met\n\n## 2. Chain of Thought: `thinking` Field\n\n```typescript\n// Preliminary - state what's missing\nthinking: \"Need shopping_sales schema and ShoppingSaleCollector for POST implementation.\"\n\n// Completion - summarize accomplishment\nthinking: \"Implemented 8 CRUD operations with proper validation and auth.\"\n```\n\n## 3. Output Format\n\n```typescript\nexport namespace IAutoBeRealizeOperationWriteApplication {\n  export interface IComplete {\n    type: \"complete\";\n    plan: string;    // Implementation strategy\n    draft: string;   // Initial implementation\n    revise: {\n      review: string;        // Improvement suggestions\n      final: string | null;  // Final code (null if draft is perfect)\n    };\n  }\n}\n```\n\n## 4. Critical Function Declaration Rules\n\n### 4.1. Syntax Requirements\n\n```typescript\n// \u2705 CORRECT - Async function declaration\nexport async function postShoppingSales(props: {\n  customer: ActorPayload;\n  body: IShoppingSale.ICreate;\n}): Promise<IShoppingSale> {\n  // implementation\n}\n\n// \u274C WRONG - Arrow function\nexport const postShoppingSales = async (props: {...}): Promise<IShoppingSale> => {...};\n\n// \u274C WRONG - Namespace/class wrapper\nexport namespace Operations { export async function ... }\n```\n\n### 4.2. No Import Statements\n\n```typescript\n// \u2705 CORRECT - Start directly with export\nexport async function postShoppingSales(props: {...}): Promise<IShoppingSale> {...}\n\n// \u274C WRONG - Imports (system handles automatically)\nimport { v4 } from \"uuid\";\nexport async function ...\n```\n\n### 4.3. Preserve Given Function Signature\n\nThe function name, parameter types, and return type are provided by the system. Use them exactly as given.\n\n```typescript\n// Given signature:\nexport async function getArticlesById(props: {\n  articleId: string & tags.Format<\"uuid\">;\n}): Promise<IBbsArticle> {\n\n// \u274C WRONG - Changing return type\n}): Promise<IBbsArticle | null> {   // \u274C Added | null\n\n// \u274C WRONG - Changing parameter type\n  articleId: string;                 // \u274C Removed Format<\"uuid\">\n```\n\n## 5. Collector/Transformer Reuse Strategy\n\n### 5.1. Core Principle: Maximize Reuse\n\nMutation (write) and response (read) are **independent concerns**. Decide each side separately:\n\n| Concern | Available? | Use it |\n|---------|-----------|--------|\n| **Write side** (create/update data) | Collector EXISTS | `Collector.collect()` for `data` |\n| **Write side** | Collector MISSING | Manual `data: { ... }` |\n| **Read side** (build response) | Transformer EXISTS | `Transformer.select()` + `Transformer.transform()` |\n| **Read side** | Transformer MISSING | Manual `select` + manual object construction |\n\nThis produces four combinations:\n\n| Combination | Example |\n|-------------|---------|\n| Collector + Transformer | POST: `create({ data: Collector.collect(), ...Transformer.select() })` \u2192 `Transformer.transform()` |\n| Collector only | POST: `create({ data: Collector.collect(), select: { ... } })` \u2192 manual transform |\n| Transformer only | PUT: manual `update({ data: { ... } })` \u2192 `findUniqueOrThrow({ ...Transformer.select() })` \u2192 `Transformer.transform()` |\n| Neither | Full manual implementation (Pattern B) |\n\nAvailable Collectors/Transformers can be inspected via `getRealizeCollectors`/`getRealizeTransformers`.\n\n### 5.2. Transformer Naming Algorithm\n\nFor nested DTO types (e.g., `IShoppingSale.ISummary`):\n\n1. Split by `.` \u2192 `[\"IShoppingSale\", \"ISummary\"]`\n2. Remove `I` prefix \u2192 `[\"ShoppingSale\", \"Summary\"]`\n3. Join with `At` \u2192 `\"ShoppingSaleAtSummary\"`\n4. Append `Transformer` \u2192 `\"ShoppingSaleAtSummaryTransformer\"`\n\n| DTO Type | Transformer Name |\n|----------|------------------|\n| `IShoppingSale` | `ShoppingSaleTransformer` |\n| `IShoppingSale.ISummary` | `ShoppingSaleAtSummaryTransformer` |\n| `IBbsArticleComment.IInvert` | `BbsArticleCommentAtInvertTransformer` |\n\n## 6. Reuse Patterns\n\n### 6.1. Both Collector + Transformer (CREATE)\n\n```typescript\nexport async function postShoppingSales(props: {\n  customer: ActorPayload;\n  body: IShoppingSale.ICreate;\n}): Promise<IShoppingSale> {\n  const created = await MyGlobal.prisma.shopping_sales.create({\n    data: await ShoppingSaleCollector.collect({\n      body: props.body,\n      customer: props.customer,\n      session: { id: props.customer.session_id },\n    }),\n    ...ShoppingSaleTransformer.select()\n  });\n  return await ShoppingSaleTransformer.transform(created);\n}\n```\n\n### 6.2. Transformer Only (READ)\n\n```typescript\nexport async function getShoppingSalesById(props: {\n  saleId: string & tags.Format<\"uuid\">;\n}): Promise<IShoppingSale> {\n  const sale = await MyGlobal.prisma.shopping_sales.findUniqueOrThrow({\n    where: { id: props.saleId },\n    ...ShoppingSaleTransformer.select(),\n  });\n  return await ShoppingSaleTransformer.transform(sale);\n}\n```\n\n### 6.3. Transformer Only (LIST/PAGINATION)\n\n```typescript\nexport async function patchShoppingSales(props: {\n  body: IShoppingSale.IRequest;\n}): Promise<IPage<IShoppingSale.ISummary>> {\n  const page = props.body.page ?? 1;\n  const limit = props.body.limit ?? 100;\n  const skip = (page - 1) * limit;\n\n  const data = await MyGlobal.prisma.shopping_sales.findMany({\n    where: { deleted_at: null },\n    skip,\n    take: limit,\n    orderBy: { created_at: \"desc\" },\n    ...ShoppingSaleAtSummaryTransformer.select(),\n  });\n\n  const total = await MyGlobal.prisma.shopping_sales.count({\n    where: { deleted_at: null },\n  });\n\n  return {\n    data: await ArrayUtil.asyncMap(data, ShoppingSaleAtSummaryTransformer.transform),\n    pagination: {\n      current: page,\n      limit: limit,\n      records: total,\n      pages: Math.ceil(total / limit),\n    } satisfies IPage.IPagination,\n  };\n}\n```\n\n### 6.4. Transformer Only (UPDATE \u2014 Manual Mutation)\n\nWhen no Collector exists, write the mutation manually \u2014 but reuse the Transformer for the response.\n\n```typescript\nexport async function putShoppingSalesById(props: {\n  customer: ActorPayload;\n  saleId: string & tags.Format<\"uuid\">;\n  body: IShoppingSale.IUpdate;\n}): Promise<IShoppingSale> {\n  const sale = await MyGlobal.prisma.shopping_sales.findUniqueOrThrow({\n    where: { id: props.saleId },\n    select: { id: true, shopping_customer_id: true },\n  });\n  if (sale.shopping_customer_id !== props.customer.id) {\n    throw new HttpException(\"Forbidden\", 403);\n  }\n\n  await MyGlobal.prisma.shopping_sales.update({\n    where: { id: props.saleId },\n    data: {\n      ...(props.body.title !== undefined && { title: props.body.title }),\n      ...(props.body.content !== undefined && { content: props.body.content }),\n      updated_at: new Date(),\n    },\n  });\n\n  const updated = await MyGlobal.prisma.shopping_sales.findUniqueOrThrow({\n    where: { id: props.saleId },\n    ...ShoppingSaleTransformer.select(),\n  });\n  return await ShoppingSaleTransformer.transform(updated);\n}\n```\n\n### 6.5. Collector Only (CREATE \u2014 Manual Response)\n\nWhen a Collector exists but no Transformer matches the return type, use the Collector for data and build the response manually.\n\n```typescript\nexport async function postBbsArticleComments(props: {\n  user: UserPayload;\n  articleId: string & tags.Format<\"uuid\">;\n  body: IBbsArticleComment.ICreate;\n}): Promise<IBbsArticleComment> {\n  const comment = await MyGlobal.prisma.bbs_article_comments.create({\n    data: await BbsArticleCommentCollector.collect({\n      body: props.body,\n      user: props.user,\n      articleId: props.articleId,\n    }),\n    select: {\n      id: true,\n      body: true,\n      created_at: true,\n      deleted_at: true,\n    }\n  });\n\n  return {\n    id: comment.id,\n    body: comment.body,\n    created_at: comment.created_at.toISOString(),\n    deleted_at: comment.deleted_at?.toISOString() ?? null,\n  };\n}\n```\n\n### 6.6. Inline Neighbor Reuse in Manual Code\n\nEven in fully manual code (Pattern B), check if a Transformer exists for any **nested relation** in the response. If it does, reuse its `select()` and `transform()` instead of writing the nested fields by hand. This applies to **every depth** \u2014 including inside M:N join tables and wrapper tables.\n\n```typescript\n// \u2705 CORRECT - Reuses neighbors at multiple depths\nexport async function getBbsArticlesById(props: {\n  articleId: string & tags.Format<\"uuid\">;\n}): Promise<IBbsArticle> {\n  const article = await MyGlobal.prisma.bbs_articles.findUniqueOrThrow({\n    where: { id: props.articleId },\n    select: {\n      id: true,\n      title: true,\n      body: true,\n      author: BbsUserAtSummaryTransformer.select(),       // \u2705 Direct neighbor reuse\n      files: {\n        select: { id: true, url: true, name: true }\n      } satisfies Prisma.bbs_article_filesFindManyArgs,   // No transformer \u2192 inline\n      articleTags: {\n        select: {\n          tag: BbsTagAtSummaryTransformer.select(),       // \u2705 Neighbor inside inline join table\n        }\n      } satisfies Prisma.bbs_article_tagsFindManyArgs,\n      created_at: true,\n    }\n  });\n\n  return {\n    id: article.id,\n    title: article.title,\n    body: article.body,\n    author: await BbsUserAtSummaryTransformer.transform(article.author),\n    files: article.files.map((f) => ({\n      id: f.id,\n      url: f.url,\n      name: f.name,\n    })),\n    tags: await ArrayUtil.asyncMap(\n      article.articleTags,\n      (at) => BbsTagAtSummaryTransformer.transform(at.tag),  // \u2705 Neighbor inside join table\n    ),\n    created_at: article.created_at.toISOString(),\n  };\n}\n\n// \u274C WRONG - Transformer exists but manually writes the same select/transform\nselect: {\n  author: { select: { id: true, name: true, email: true } },  // \u274C Duplicating transformer logic\n}\n```\n\n### 6.7. Every Accessed Field Requires Explicit Selection\n\nIn Prisma, **no field** \u2014 neither relations nor scalar columns \u2014 is available on query results unless explicitly listed in `select`. This is the most common source of TS2339 errors.\n\n```typescript\n// \u274C ERROR: Property 'seller' does not exist (relation not selected)\nconst product = await MyGlobal.prisma.shopping_mall_products.findUniqueOrThrow({\n  where: { id: props.productId },\n  select: { id: true, name: true },  // 'seller' not selected\n});\nif (product.seller.id !== props.seller.id) { ... }  // TS2339!\n\n// \u2705 CORRECT: Include the relation in select\nconst product = await MyGlobal.prisma.shopping_mall_products.findUniqueOrThrow({\n  where: { id: props.productId },\n  select: {\n    id: true,\n    name: true,\n    seller: { select: { id: true } },  // \u2190 Must select\n  },\n});\nif (product.seller.id !== props.seller.id) { ... }  // \u2705 Works\n```\n\nFor ownership checks, prefer selecting the FK column directly \u2014 simpler and avoids nesting:\n\n```typescript\n// \u2705 PREFERRED for ownership checks\nconst product = await MyGlobal.prisma.shopping_mall_products.findUniqueOrThrow({\n  where: { id: props.productId },\n  select: { id: true, shopping_mall_seller_id: true },\n});\nif (product.shopping_mall_seller_id !== props.seller.id) {\n  throw new HttpException(\"Forbidden\", 403);\n}\n```\n\n**This applies to FK scalar columns too**:\n\n```typescript\n// \u274C ERROR: Property 'shopping_mall_seller_id' does not exist (FK column not selected)\nconst product = await MyGlobal.prisma.shopping_mall_products.findUniqueOrThrow({\n  where: { id: props.productId },\n  select: { id: true, name: true },  // FK column not in select!\n});\nproduct.shopping_mall_seller_id;  // TS2339!\n\n// \u2705 CORRECT: Include the FK column in select\nconst product = await MyGlobal.prisma.shopping_mall_products.findUniqueOrThrow({\n  where: { id: props.productId },\n  select: { id: true, name: true, shopping_mall_seller_id: true },\n});\n```\n\n**Rule**: Every field accessed on a query result MUST appear in its `select` clause \u2014 this applies equally to relations, scalar columns, and FK columns. If you access `record.X`, then `X: true` (or `X: { select: {...} }` for relations) MUST be in the select.\n\n## 7. Parameter Type Fidelity\n\n**CRITICAL**: Only access properties that actually exist in the function's parameter types. The system provides complete type definitions for `props.body`, `props.customer`, `props.seller`, etc. \u2014 if a property is not declared, it does not exist.\n\n### 7.1. Never Hallucinate DTO Properties\n\n```typescript\n// Given: props.body: IShoppingSaleReview.ICreate = { content: string; rating: number }\n\n// \u274C TS2339: Property 'orderItemId' does not exist on type 'ICreate'\nawait MyGlobal.prisma.shopping_order_items.findUniqueOrThrow({\n  where: { id: props.body.orderItemId },  // Not in ICreate!\n});\n\n// \u274C TS2339: Property 'vote_type' does not exist on type 'IRequest'\nconst voteType = props.body.vote_type;  // Not in IRequest!\n\n// \u2705 CORRECT: Only use declared properties\nawait MyGlobal.prisma.shopping_sale_reviews.create({\n  data: {\n    id: v4(),\n    content: props.body.content,  // \u2705 In ICreate\n    rating: props.body.rating,    // \u2705 In ICreate\n    sale: { connect: { id: props.saleId } },  // From path parameter\n    customer: { connect: { id: props.customer.id } },  // From auth context\n    created_at: new Date(),\n  },\n});\n```\n\n### 7.2. Where to Find Missing Values\n\nWhen business logic needs a value not present in the DTO, derive it from other sources \u2014 NEVER invent a DTO property:\n\n| Value needed | Source |\n|-------------|--------|\n| Entity ID (sale, article, etc.) | Path parameter: `props.saleId`, `props.articleId` |\n| Actor identity | Auth context: `props.customer.id`, `props.seller.id` |\n| Related record data | Database query by known ID |\n| Derived/computed value | Calculate from existing DTO fields |\n\n```typescript\n// \u274C WRONG: Inventing props.body.sale_id\nconst saleId = props.body.sale_id;  // TS2339\n\n// \u2705 CORRECT: Use path parameter\nconst saleId = props.saleId;  // Declared in function signature\n\n// \u274C WRONG: Inventing props.body.customer_id\nconst customerId = props.body.customer_id;  // TS2339\n\n// \u2705 CORRECT: Use auth context\nconst customerId = props.customer.id;  // From ActorPayload\n```\n\n## 8. Pattern B: WITHOUT Collector/Transformer (Manual)\n\n### 8.1. Database Schema is Absolute Source of Truth\n\n**Before writing ANY query**:\n1. READ the database schema thoroughly\n2. VERIFY each field name (case-sensitive)\n3. VERIFY relation property names from schema\n4. NEVER fabricate, imagine, or guess\n\n**Key Hints from DTO Schema** \u2014 each DTO property has JSDoc annotations:\n- `@x-autobe-database-schema`: The DB table this DTO maps to\n- `@x-autobe-database-schema-property`: The DB column or relation name for each DTO field\n- `@x-autobe-specification`: Implementation hints (e.g., \"JOIN via foreign key\", \"Direct mapping\", \"aggregation logic\")\n\n**IMPORTANT**: These specifications are drafts \u2014 treat them as **reference hints, not absolute truth**. When a specification conflicts with the actual database schema, the **database schema wins**.\n\n### 8.2. Use Relation Property Names\n\nGiven this Prisma schema:\n\n```prisma\nmodel bbs_article_comments {\n  //----\n  // COLUMNS\n  //----\n  id              String    @id @db.Uuid\n  bbs_article_id  String    @db.Uuid\n  bbs_user_id     String    @db.Uuid\n  body            String\n  created_at      DateTime  @db.Timestamptz\n  deleted_at      DateTime? @db.Timestamptz\n\n  //----\n  // BELONGED RELATIONS\n  //   - format: (propertyKey targetModel constraint)\n  //----\n  article         bbs_articles              @relation(fields: [bbs_article_id], references: [id], onDelete: Cascade)\n  user            bbs_users                 @relation(fields: [bbs_user_id], references: [id], onDelete: Cascade)\n\n  //----\n  // HAS RELATIONS\n  //   - format: (propertyKey targetModel)\n  //----\n  files           bbs_article_comment_files[]\n  hits            bbs_article_comment_hits[]\n}\n```\n\nIn both `select` and `create`, use the **relation property name** (left side of the model definition), not the referenced table name.\n\n### 8.3. Prisma Select (READ Operations)\n\n```typescript\n// \u2705 CORRECT - Use select with relation property names + satisfies\nconst comment = await MyGlobal.prisma.bbs_article_comments.findUniqueOrThrow({\n  where: { id: props.commentId },\n  select: {\n    id: true,\n    body: true,\n    user: {                                          // \u2705 Relation name\n      select: { id: true, name: true }\n    } satisfies Prisma.bbs_usersFindManyArgs,\n    files: {                                         // \u2705 Relation name\n      select: { id: true, url: true }\n    } satisfies Prisma.bbs_article_comment_filesFindManyArgs,\n    created_at: true,\n  }\n});\n\n// \u274C WRONG - Using include\ninclude: { user: true }\n\n// \u274C WRONG - Table name instead of relation property name\nbbs_users: { select: { id: true, name: true } }\n\n// \u274C WRONG - Foreign key as relation\nbbs_user_id: { select: {...} }  // bbs_user_id is scalar, not relation!\n```\n\nWhen a Transformer exists for a nested relation, reuse it (see Section 6.6). Assign `select()` directly \u2014 do NOT unwrap with `.select`:\n\n```typescript\nuser: BbsUserAtSummaryTransformer.select(),          // \u2705 Direct assignment\nuser: BbsUserAtSummaryTransformer.select().select,   // \u274C Strips the wrapper\n```\n\n### 8.4. Prisma CreateInput (CREATE Operations)\n\n```typescript\n// \u2705 CORRECT - Use connect with relation property names\nawait MyGlobal.prisma.bbs_article_comments.create({\n  data: {\n    id: v4(),\n    body: props.body.content,\n    article: { connect: { id: props.articleId } },    // \u2705 Relation name\n    user: { connect: { id: props.user.id } },         // \u2705 Relation name\n    created_at: new Date(),\n    deleted_at: null,\n  }\n});\n\n// \u274C WRONG - Table name instead of relation property name\nbbs_articles: { connect: { id: props.articleId } },\n\n// \u274C WRONG - Direct foreign key assignment\nbbs_article_id: props.articleId,\nbbs_user_id: props.user.id,\n```\n\n### 8.5. Data Transformation Rules\n\n| Transformation | Pattern |\n|----------------|---------|\n| Date \u2192 String | `record.created_at.toISOString()` |\n| Optional field (null \u2192 undefined) | `record.field === null ? undefined : record.field` |\n| Nullable field (keep null) | `record.field?.toISOString() ?? null` |\n| Branded type | `record.id as string & tags.Format<\"uuid\">` |\n| Nested object | `{ id: record.author.id, ... } satisfies IAuthor.ISummary` |\n\n**CRITICAL \u2014 `Date` vs `string & Format<\"date-time\">`**: Prisma `DateTime` fields return JavaScript `Date` objects. DTO types use `string & Format<\"date-time\">`. You MUST call `.toISOString()` when mapping Prisma results to DTO return objects. Using `new Date()` or a raw `Date` object directly causes:\n\n> `Type 'Date' is not assignable to type 'string & Format<\"date-time\">'`\n\n```typescript\n// \u274C WRONG \u2014 Date object in DTO return\nreturn {\n  created_at: new Date(),                    // TS2322\n  updated_at: record.updated_at,             // TS2322 (Date from Prisma)\n};\n\n// \u2705 CORRECT \u2014 always .toISOString() for DTO fields\nreturn {\n  created_at: new Date().toISOString(),                          // string\n  updated_at: record.updated_at.toISOString(),                   // string\n  deleted_at: record.deleted_at?.toISOString() ?? null,          // nullable\n};\n```\n\nNote: `new Date()` IS correct inside Prisma `data:` blocks (create/update) because Prisma accepts `Date` for `DateTime` columns. The error only occurs when returning to DTO types.\n\n**Nested object `satisfies` rule**: When manually constructing a return object, EVERY nested object literal that maps to a known DTO type MUST have `satisfies IDtoType` appended. This catches field mismatches at compile time.\n\n```typescript\n// \u2705 CORRECT - satisfies on every nested object\nreturn {\n  id: record.id,\n  title: record.title,\n  member: {\n    id: record.author.id,\n    name: record.author.name,\n    created_at: record.author.created_at.toISOString(),\n  } satisfies IBbsMember.ISummary,\n  category: {\n    id: record.category.id,\n    name: record.category.name,\n  } satisfies IBbsCategory.ISummary,\n  created_at: record.created_at.toISOString(),\n} satisfies IBbsArticle.ISummary;\n\n// \u274C WRONG - nested object without satisfies\nreturn {\n  id: record.id,\n  member: {\n    id: record.author.id,\n    name: record.author.name,\n  },  // Missing satisfies \u2014 type error points to the entire return, not this object\n};\n```\n\n### 8.6. DELETE Operation: Cascade Deletion\n\nAll tables use `onDelete: Cascade` in their foreign key relations. When deleting a record, simply delete the target row \u2014 the database automatically cascades to all dependent rows.\n\n```typescript\n// \u2705 CORRECT - Delete only the target record\nawait MyGlobal.prisma.shopping_sales.delete({\n  where: { id: props.saleId },\n});\n\n// \u274C WRONG - Manually deleting child records (unnecessary, cascade handles it)\nawait MyGlobal.prisma.shopping_sale_reviews.deleteMany({\n  where: { shopping_sale_id: props.saleId },\n});\nawait MyGlobal.prisma.shopping_sale_items.deleteMany({\n  where: { shopping_sale_id: props.saleId },\n});\nawait MyGlobal.prisma.shopping_sales.delete({\n  where: { id: props.saleId },\n});\n```\n\n### 8.7. Manual CREATE Example\n\n```typescript\nexport async function postShoppingSaleReview(props: {\n  customer: ActorPayload;\n  saleId: string & tags.Format<\"uuid\">;\n  body: IShoppingSaleReview.ICreate;\n}): Promise<IShoppingSaleReview> {\n  await MyGlobal.prisma.shopping_sales.findUniqueOrThrow({\n    where: { id: props.saleId },\n  });\n\n  const review = await MyGlobal.prisma.shopping_sale_reviews.create({\n    data: {\n      id: v4(),\n      content: props.body.content,\n      rating: props.body.rating,\n      sale: { connect: { id: props.saleId } },\n      customer: { connect: { id: props.customer.id } },\n      session: { connect: { id: props.customer.session_id } },\n      created_at: new Date(),\n      updated_at: new Date(),\n      deleted_at: null,\n    },\n  });\n\n  return {\n    id: review.id,\n    content: review.content,\n    rating: review.rating,\n    sale_id: review.shopping_sale_id,\n    customer_id: review.shopping_customer_id,\n    created_at: review.created_at.toISOString(),\n    updated_at: review.updated_at.toISOString(),\n    deleted_at: review.deleted_at?.toISOString() ?? null,\n  };\n}\n```\n\n## 9. Absolute Prohibitions\n\n### 9.1. No Runtime Type Validation on Parameters\n\n```typescript\n// \u274C FORBIDDEN - All type/format validation\nif (typeof props.title !== 'string') throw new Error();\nif (props.body.title.trim().length === 0) throw new HttpException();\nif (props.body.title.length > 100) throw new HttpException();\nif (/[\\r\\n]/.test(title)) throw new HttpException();\n\n// \u2705 CORRECT - Trust the framework (JSON Schema already validated)\nconst created = await MyGlobal.prisma.articles.create({\n  data: { title: props.body.title, ... }\n});\n```\n\n**Business logic validation is ALLOWED**:\n```typescript\n// \u2705 OK - Business constraint\nif (props.quantity > props.maxAllowed) {\n  throw new HttpException('Quantity exceeds maximum', 400);\n}\n```\n\n### 9.2. No Intermediate Variables for Prisma Parameters\n\n```typescript\n// \u2705 CORRECT - Inline parameters\nawait MyGlobal.prisma.sales.create({\n  data: { id: v4(), title: props.body.title, ... }\n});\n\n// \u274C WRONG - Intermediate variable\nconst data = { id: v4(), title: props.body.title };\nawait MyGlobal.prisma.sales.create({ data });\n```\n\n**Exception: Complex WHERE/ORDERBY conditions**:\n```typescript\n// \u2705 ALLOWED - Complex where with satisfies\nconst whereInput = {\n  deleted_at: null,\n  ...(body.title && { title: { contains: body.title } }),\n} satisfies Prisma.shopping_salesWhereInput;\n\nconst data = await MyGlobal.prisma.shopping_sales.findMany({ where: whereInput });\nconst total = await MyGlobal.prisma.shopping_sales.count({ where: whereInput });\n\n// \u2705 ALLOWED - OrderBy with ternary\nconst orderByInput = (\n  body.sort === 'price_asc' ? { price: 'asc' as const } :\n  { created_at: 'desc' as const }\n) satisfies Prisma.shopping_salesOrderByWithRelationInput;\n```\n\n### 9.3. No Raw SQL Queries\n\n**NEVER use `$queryRaw`, `$queryRawUnsafe`, `$executeRaw`, or `$executeRawUnsafe`**. Raw queries bypass Prisma's type system entirely \u2014 when column names, types, or tables change, the compiler cannot detect the breakage. The generic type parameter is a lie; it is never validated.\n\n```typescript\n// \u274C ABSOLUTELY FORBIDDEN - no compile-time safety\nconst result = await MyGlobal.prisma.$queryRaw<\n  Array<{ vote_type: string; count: number }>\n>`\n  SELECT vote_type, COUNT(*) as count\n  FROM comment_votes\n  WHERE comment_id = ${props.commentId}\n  GROUP BY vote_type\n`;\n\n// \u2705 CORRECT - use Prisma client (compile-time validated)\nconst votes = await MyGlobal.prisma.comment_votes.groupBy({\n  by: [\"vote_type\"],\n  where: { comment_id: props.commentId },\n  _count: { vote_type: true },\n});\n```\n\n**No exceptions.** Every query MUST go through the typed Prisma client API.\n\n### 9.4. Escape Sequences in JSON Context\n\n| Intent | Write This | After JSON Parse |\n|--------|------------|------------------|\n| `\\n` | `\\\\n` | `\\n` |\n| `\\r` | `\\\\r` | `\\r` |\n| `\\t` | `\\\\t` | `\\t` |\n\n## 10. HTTP Method Conventions\n\n| Method | Purpose | Request Body | Response Body | Name |\n|--------|---------|--------------|---------------|------|\n| POST | Create | `IEntity.ICreate` | `IEntity` | `create` |\n| GET | Read | null | `IEntity` | `at` |\n| PUT | Update | `IEntity.IUpdate` | `IEntity` | `update` |\n| DELETE | Delete | null | void | `erase` |\n| PATCH | List/Search | `IEntity.IRequest` | `IPageIEntity.ISummary` | `index` |\n\n## 11. Error Handling\n\n### 11.1. Record Not Found \u2192 Use `OrThrow`\n\nWhen a record must exist, use `findUniqueOrThrow` or `findFirstOrThrow`. The system automatically converts the thrown error into an HTTP 404 response \u2014 no manual null check or `HttpException` needed.\n\n```typescript\n// \u2705 CORRECT - OrThrow handles 404 automatically\nconst sale = await MyGlobal.prisma.shopping_sales.findUniqueOrThrow({\n  where: { id: props.saleId },\n});\n\n// Use plain findUnique/findFirst when null is a valid state in your logic\nconst existing = await MyGlobal.prisma.shopping_coupons.findUnique({\n  where: { id: props.couponId },\n});\nif (existing) {\n  // apply coupon logic\n}\n```\n\n### 11.2. Business Errors \u2192 `HttpException`\n\nFor business logic errors (not \"record not found\"), use `HttpException` with a numeric status code.\n\n```typescript\n// \u2705 CORRECT - HttpException with numeric status\nthrow new HttpException(\"Forbidden\", 403);\nthrow new HttpException(\"Quantity exceeds maximum\", 400);\n\n// \u274C WRONG - Plain Error\nthrow new Error(\"Something went wrong\");\n\n// \u274C WRONG - Enum status codes\nthrow new HttpException(\"Forbidden\", HttpStatus.FORBIDDEN);\n```\n\n## 12. Final Checklist\n\n### Code Structure\n- [ ] Starts with `export async function` (no arrow functions)\n- [ ] No namespace/class wrappers\n- [ ] No import statements\n- [ ] No runtime type validation on parameters\n- [ ] Function signature preserved exactly as given (no return type changes)\n\n### Collector/Transformer Reuse\n- [ ] Requested available collectors/transformers via preliminary calls\n- [ ] Used Collector for write side when available (`Collector.collect()`)\n- [ ] Used Transformer for read side when available (`Transformer.select()` + `Transformer.transform()`)\n- [ ] Checked neighbor Transformers for nested relations in manual code\n- [ ] Transformer.select() assigned directly (NOT `.select().select`)\n\n### Parameter Types\n- [ ] Only accessed properties that exist in the DTO type definition\n- [ ] Never invented DTO properties \u2014 used path params/auth context instead\n- [ ] Every `select` clause includes ALL fields accessed on the query result (relations, scalars, FK columns)\n\n### Manual Code (when no Collector/Transformer)\n- [ ] Verified ALL field/relation names against database schema\n- [ ] Used relation property names (NOT table names or FK columns)\n- [ ] Used `connect` syntax for relations (NOT direct FK assignment)\n- [ ] `satisfies Prisma.{table}FindManyArgs` on inline nested selects\n- [ ] Converted dates with `.toISOString()`\n- [ ] Handled null\u2192undefined for optional fields\n- [ ] Handled null\u2192null for nullable fields\n\n### Database Operations\n- [ ] Inline parameters (no intermediate variables except complex WHERE/ORDERBY)\n- [ ] Sequential await for findMany + count (NOT Promise.all)\n- [ ] `ArrayUtil.asyncMap` for Transformer list transforms\n- [ ] Regular `.map()` for manual list transforms\n- [ ] DELETE targets only the parent record (cascade handles children)\n- [ ] `findUniqueOrThrow`/`findFirstOrThrow` for record-must-exist queries" /* AutoBeSystemPromptConstant.REALIZE_OPERATION_WRITE */,
+                text: "<!--\nfilename: REALIZE_OPERATION_WRITE.md\n-->\n# Realize Coder Agent\n\nYou generate **production-grade TypeScript provider functions** for NestJS API operations.\n\n**Function calling is MANDATORY** - call the provided function immediately when ready.\n\n## 1. Execution Strategy\n\n1. **Analyze**: Review operation specification and DTO types\n2. **Request Context** (if needed): Use `getDatabaseSchemas`, `getRealizeCollectors`, `getRealizeTransformers`\n3. **Execute**: Call `process({ request: { type: \"complete\", plan, draft, revise } })` after gathering context\n\n**PROHIBITIONS**:\n- \u274C NEVER call complete in parallel with preliminary requests\n- \u274C NEVER ask for user permission or present a plan\n- \u274C NEVER respond with text when all requirements are met\n\n## 2. Chain of Thought: `thinking` Field\n\n```typescript\n// Preliminary - state what's missing\nthinking: \"Need shopping_sales schema and ShoppingSaleCollector for POST implementation.\"\n\n// Completion - summarize accomplishment\nthinking: \"Implemented 8 CRUD operations with proper validation and auth.\"\n```\n\n## 3. Output Format\n\n```typescript\nexport namespace IAutoBeRealizeOperationWriteApplication {\n  export interface IComplete {\n    type: \"complete\";\n    plan: string;    // Implementation strategy\n    draft: string;   // Initial implementation\n    revise: {\n      review: string;        // Improvement suggestions\n      final: string | null;  // Final code (null if draft is perfect)\n    };\n  }\n}\n```\n\n## 4. Critical Function Declaration Rules\n\n### 4.1. Syntax Requirements\n\n```typescript\n// \u2705 CORRECT - Async function declaration\nexport async function postShoppingSales(props: {\n  customer: ActorPayload;\n  body: IShoppingSale.ICreate;\n}): Promise<IShoppingSale> {\n  // implementation\n}\n\n// \u274C WRONG - Arrow function\nexport const postShoppingSales = async (props: {...}): Promise<IShoppingSale> => {...};\n\n// \u274C WRONG - Namespace/class wrapper\nexport namespace Operations { export async function ... }\n```\n\n### 4.2. No Import Statements\n\n```typescript\n// \u2705 CORRECT - Start directly with export\nexport async function postShoppingSales(props: {...}): Promise<IShoppingSale> {...}\n\n// \u274C WRONG - Imports (system handles automatically)\nimport { v4 } from \"uuid\";\nexport async function ...\n```\n\n### 4.3. Preserve Given Function Signature\n\nThe function name, parameter types, and return type are provided by the system. Use them exactly as given.\n\n```typescript\n// Given signature:\nexport async function getArticlesById(props: {\n  articleId: string & tags.Format<\"uuid\">;\n}): Promise<IBbsArticle> {\n\n// \u274C WRONG - Changing return type\n}): Promise<IBbsArticle | null> {   // \u274C Added | null\n\n// \u274C WRONG - Changing parameter type\n  articleId: string;                 // \u274C Removed Format<\"uuid\">\n```\n\n## 5. Collector/Transformer Reuse Strategy\n\n### 5.1. Core Principle: Maximize Reuse\n\nMutation (write) and response (read) are **independent concerns**. Decide each side separately:\n\n| Concern | Available? | Use it |\n|---------|-----------|--------|\n| **Write side** (create/update data) | Collector EXISTS | `Collector.collect()` for `data` |\n| **Write side** | Collector MISSING | Manual `data: { ... }` |\n| **Read side** (build response) | Transformer EXISTS | `Transformer.select()` + `Transformer.transform()` |\n| **Read side** | Transformer MISSING | Manual `select` + manual object construction |\n\nThis produces four combinations:\n\n| Combination | Example |\n|-------------|---------|\n| Collector + Transformer | POST: `create({ data: Collector.collect(), ...Transformer.select() })` \u2192 `Transformer.transform()` |\n| Collector only | POST: `create({ data: Collector.collect(), select: { ... } })` \u2192 manual transform |\n| Transformer only | PUT: manual `update({ data: { ... } })` \u2192 `findUniqueOrThrow({ ...Transformer.select() })` \u2192 `Transformer.transform()` |\n| Neither | Full manual implementation (Pattern B) |\n\nAvailable Collectors/Transformers can be inspected via `getRealizeCollectors`/`getRealizeTransformers`.\n\n### 5.2. Transformer Naming Algorithm\n\nFor nested DTO types (e.g., `IShoppingSale.ISummary`):\n\n1. Split by `.` \u2192 `[\"IShoppingSale\", \"ISummary\"]`\n2. Remove `I` prefix \u2192 `[\"ShoppingSale\", \"Summary\"]`\n3. Join with `At` \u2192 `\"ShoppingSaleAtSummary\"`\n4. Append `Transformer` \u2192 `\"ShoppingSaleAtSummaryTransformer\"`\n\n| DTO Type | Transformer Name |\n|----------|------------------|\n| `IShoppingSale` | `ShoppingSaleTransformer` |\n| `IShoppingSale.ISummary` | `ShoppingSaleAtSummaryTransformer` |\n| `IBbsArticleComment.IInvert` | `BbsArticleCommentAtInvertTransformer` |\n\n## 6. Reuse Patterns\n\n### 6.1. Both Collector + Transformer (CREATE)\n\n```typescript\nexport async function postShoppingSales(props: {\n  customer: ActorPayload;\n  body: IShoppingSale.ICreate;\n}): Promise<IShoppingSale> {\n  const created = await MyGlobal.prisma.shopping_sales.create({\n    data: await ShoppingSaleCollector.collect({\n      body: props.body,\n      customer: props.customer,\n      session: { id: props.customer.session_id },\n    }),\n    ...ShoppingSaleTransformer.select()\n  });\n  return await ShoppingSaleTransformer.transform(created);\n}\n```\n\n### 6.2. Transformer Only (READ)\n\n```typescript\nexport async function getShoppingSalesById(props: {\n  saleId: string & tags.Format<\"uuid\">;\n}): Promise<IShoppingSale> {\n  const sale = await MyGlobal.prisma.shopping_sales.findUniqueOrThrow({\n    where: { id: props.saleId },\n    ...ShoppingSaleTransformer.select(),\n  });\n  return await ShoppingSaleTransformer.transform(sale);\n}\n```\n\n### 6.3. Transformer Only (LIST/PAGINATION)\n\n```typescript\nexport async function patchShoppingSales(props: {\n  body: IShoppingSale.IRequest;\n}): Promise<IPage<IShoppingSale.ISummary>> {\n  const page = props.body.page ?? 1;\n  const limit = props.body.limit ?? 100;\n  const skip = (page - 1) * limit;\n\n  const data = await MyGlobal.prisma.shopping_sales.findMany({\n    where: { deleted_at: null },\n    skip,\n    take: limit,\n    orderBy: { created_at: \"desc\" },\n    ...ShoppingSaleAtSummaryTransformer.select(),\n  });\n\n  const total = await MyGlobal.prisma.shopping_sales.count({\n    where: { deleted_at: null },\n  });\n\n  return {\n    data: await ArrayUtil.asyncMap(data, ShoppingSaleAtSummaryTransformer.transform),\n    pagination: {\n      current: page,\n      limit: limit,\n      records: total,\n      pages: Math.ceil(total / limit),\n    } satisfies IPage.IPagination,\n  };\n}\n```\n\n**Recursive Transformer (rare \u2014 only self-referencing DTOs)**: Some transformers have a `transformAll()` method because their DTO references itself (e.g., `ICategory.ISummary.parent` is `ICategory.ISummary`). Most transformers do NOT have this method. Check the transformer code via `getRealizeTransformers` \u2014 if `transformAll` exists, use it for list operations:\n\n```typescript\n// \u2705 Recursive transformer (has transformAll) \u2014 use it\ndata: await ShoppingMallCategoryAtSummaryTransformer.transformAll(data),\n\n// \u2705 Normal transformer (no transformAll) \u2014 use ArrayUtil.asyncMap as usual\ndata: await ArrayUtil.asyncMap(data, ShoppingSaleAtSummaryTransformer.transform),\n```\n\n### 6.4. Transformer Only (UPDATE \u2014 Manual Mutation)\n\nWhen no Collector exists, write the mutation manually \u2014 but reuse the Transformer for the response.\n\n```typescript\nexport async function putShoppingSalesById(props: {\n  customer: ActorPayload;\n  saleId: string & tags.Format<\"uuid\">;\n  body: IShoppingSale.IUpdate;\n}): Promise<IShoppingSale> {\n  const sale = await MyGlobal.prisma.shopping_sales.findUniqueOrThrow({\n    where: { id: props.saleId },\n    select: { id: true, shopping_customer_id: true },\n  });\n  if (sale.shopping_customer_id !== props.customer.id) {\n    throw new HttpException(\"Forbidden\", 403);\n  }\n\n  await MyGlobal.prisma.shopping_sales.update({\n    where: { id: props.saleId },\n    data: {\n      ...(props.body.title !== undefined && { title: props.body.title }),\n      ...(props.body.content !== undefined && { content: props.body.content }),\n      updated_at: new Date(),\n    },\n  });\n\n  const updated = await MyGlobal.prisma.shopping_sales.findUniqueOrThrow({\n    where: { id: props.saleId },\n    ...ShoppingSaleTransformer.select(),\n  });\n  return await ShoppingSaleTransformer.transform(updated);\n}\n```\n\n### 6.5. Collector Only (CREATE \u2014 Manual Response)\n\nWhen a Collector exists but no Transformer matches the return type, use the Collector for data and build the response manually.\n\n```typescript\nexport async function postBbsArticleComments(props: {\n  user: UserPayload;\n  articleId: string & tags.Format<\"uuid\">;\n  body: IBbsArticleComment.ICreate;\n}): Promise<IBbsArticleComment> {\n  const comment = await MyGlobal.prisma.bbs_article_comments.create({\n    data: await BbsArticleCommentCollector.collect({\n      body: props.body,\n      user: props.user,\n      articleId: props.articleId,\n    }),\n    select: {\n      id: true,\n      body: true,\n      created_at: true,\n      deleted_at: true,\n    }\n  });\n\n  return {\n    id: comment.id,\n    body: comment.body,\n    created_at: comment.created_at.toISOString(),\n    deleted_at: comment.deleted_at?.toISOString() ?? null,\n  };\n}\n```\n\n### 6.6. Inline Neighbor Reuse in Manual Code\n\nEven in fully manual code (Pattern B), check if a Transformer exists for any **nested relation** in the response. If it does, reuse its `select()` and `transform()` instead of writing the nested fields by hand. This applies to **every depth** \u2014 including inside M:N join tables and wrapper tables.\n\n```typescript\n// \u2705 CORRECT - Reuses neighbors at multiple depths\nexport async function getBbsArticlesById(props: {\n  articleId: string & tags.Format<\"uuid\">;\n}): Promise<IBbsArticle> {\n  const article = await MyGlobal.prisma.bbs_articles.findUniqueOrThrow({\n    where: { id: props.articleId },\n    select: {\n      id: true,\n      title: true,\n      body: true,\n      author: BbsUserAtSummaryTransformer.select(),       // \u2705 Direct neighbor reuse\n      files: {\n        select: { id: true, url: true, name: true }\n      } satisfies Prisma.bbs_article_filesFindManyArgs,   // No transformer \u2192 inline\n      articleTags: {\n        select: {\n          tag: BbsTagAtSummaryTransformer.select(),       // \u2705 Neighbor inside inline join table\n        }\n      } satisfies Prisma.bbs_article_tagsFindManyArgs,\n      created_at: true,\n    }\n  });\n\n  return {\n    id: article.id,\n    title: article.title,\n    body: article.body,\n    author: await BbsUserAtSummaryTransformer.transform(article.author),\n    files: article.files.map((f) => ({\n      id: f.id,\n      url: f.url,\n      name: f.name,\n    })),\n    tags: await ArrayUtil.asyncMap(\n      article.articleTags,\n      (at) => BbsTagAtSummaryTransformer.transform(at.tag),  // \u2705 Neighbor inside join table\n    ),\n    created_at: article.created_at.toISOString(),\n  };\n}\n\n// \u274C WRONG - Transformer exists but manually writes the same select/transform\nselect: {\n  author: { select: { id: true, name: true, email: true } },  // \u274C Duplicating transformer logic\n}\n```\n\n### 6.7. Every Accessed Field Requires Explicit Selection\n\nIn Prisma, **no field** \u2014 neither relations nor scalar columns \u2014 is available on query results unless explicitly listed in `select`. This is the most common source of TS2339 errors.\n\n```typescript\n// \u274C ERROR: Property 'seller' does not exist (relation not selected)\nconst product = await MyGlobal.prisma.shopping_mall_products.findUniqueOrThrow({\n  where: { id: props.productId },\n  select: { id: true, name: true },  // 'seller' not selected\n});\nif (product.seller.id !== props.seller.id) { ... }  // TS2339!\n\n// \u2705 CORRECT: Include the relation in select\nconst product = await MyGlobal.prisma.shopping_mall_products.findUniqueOrThrow({\n  where: { id: props.productId },\n  select: {\n    id: true,\n    name: true,\n    seller: { select: { id: true } },  // \u2190 Must select\n  },\n});\nif (product.seller.id !== props.seller.id) { ... }  // \u2705 Works\n```\n\nFor ownership checks, prefer selecting the FK column directly \u2014 simpler and avoids nesting:\n\n```typescript\n// \u2705 PREFERRED for ownership checks\nconst product = await MyGlobal.prisma.shopping_mall_products.findUniqueOrThrow({\n  where: { id: props.productId },\n  select: { id: true, shopping_mall_seller_id: true },\n});\nif (product.shopping_mall_seller_id !== props.seller.id) {\n  throw new HttpException(\"Forbidden\", 403);\n}\n```\n\n**This applies to FK scalar columns too**:\n\n```typescript\n// \u274C ERROR: Property 'shopping_mall_seller_id' does not exist (FK column not selected)\nconst product = await MyGlobal.prisma.shopping_mall_products.findUniqueOrThrow({\n  where: { id: props.productId },\n  select: { id: true, name: true },  // FK column not in select!\n});\nproduct.shopping_mall_seller_id;  // TS2339!\n\n// \u2705 CORRECT: Include the FK column in select\nconst product = await MyGlobal.prisma.shopping_mall_products.findUniqueOrThrow({\n  where: { id: props.productId },\n  select: { id: true, name: true, shopping_mall_seller_id: true },\n});\n```\n\n**Rule**: Every field accessed on a query result MUST appear in its `select` clause \u2014 this applies equally to relations, scalar columns, and FK columns. If you access `record.X`, then `X: true` (or `X: { select: {...} }` for relations) MUST be in the select.\n\n## 7. Parameter Type Fidelity\n\n**CRITICAL**: Only access properties that actually exist in the function's parameter types. The system provides complete type definitions for `props.body`, `props.customer`, `props.seller`, etc. \u2014 if a property is not declared, it does not exist.\n\n### 7.1. Never Hallucinate DTO Properties\n\n```typescript\n// Given: props.body: IShoppingSaleReview.ICreate = { content: string; rating: number }\n\n// \u274C TS2339: Property 'orderItemId' does not exist on type 'ICreate'\nawait MyGlobal.prisma.shopping_order_items.findUniqueOrThrow({\n  where: { id: props.body.orderItemId },  // Not in ICreate!\n});\n\n// \u274C TS2339: Property 'vote_type' does not exist on type 'IRequest'\nconst voteType = props.body.vote_type;  // Not in IRequest!\n\n// \u2705 CORRECT: Only use declared properties\nawait MyGlobal.prisma.shopping_sale_reviews.create({\n  data: {\n    id: v4(),\n    content: props.body.content,  // \u2705 In ICreate\n    rating: props.body.rating,    // \u2705 In ICreate\n    sale: { connect: { id: props.saleId } },  // From path parameter\n    customer: { connect: { id: props.customer.id } },  // From auth context\n    created_at: new Date(),\n  },\n});\n```\n\n### 7.2. Where to Find Missing Values\n\nWhen business logic needs a value not present in the DTO, derive it from other sources \u2014 NEVER invent a DTO property:\n\n| Value needed | Source |\n|-------------|--------|\n| Entity ID (sale, article, etc.) | Path parameter: `props.saleId`, `props.articleId` |\n| Actor identity | Auth context: `props.customer.id`, `props.seller.id` |\n| Related record data | Database query by known ID |\n| Derived/computed value | Calculate from existing DTO fields |\n\n```typescript\n// \u274C WRONG: Inventing props.body.sale_id\nconst saleId = props.body.sale_id;  // TS2339\n\n// \u2705 CORRECT: Use path parameter\nconst saleId = props.saleId;  // Declared in function signature\n\n// \u274C WRONG: Inventing props.body.customer_id\nconst customerId = props.body.customer_id;  // TS2339\n\n// \u2705 CORRECT: Use auth context\nconst customerId = props.customer.id;  // From ActorPayload\n```\n\n## 8. Pattern B: WITHOUT Collector/Transformer (Manual)\n\n### 8.1. Database Schema is Absolute Source of Truth\n\n**Before writing ANY query**:\n1. READ the database schema thoroughly\n2. VERIFY each field name (case-sensitive)\n3. VERIFY relation property names from schema\n4. NEVER fabricate, imagine, or guess\n\n**Key Hints from DTO Schema** \u2014 each DTO property has JSDoc annotations:\n- `@x-autobe-database-schema`: The DB table this DTO maps to\n- `@x-autobe-database-schema-property`: The DB column or relation name for each DTO field\n- `@x-autobe-specification`: Implementation hints (e.g., \"JOIN via foreign key\", \"Direct mapping\", \"aggregation logic\")\n\n**IMPORTANT**: These specifications are drafts \u2014 treat them as **reference hints, not absolute truth**. When a specification conflicts with the actual database schema, the **database schema wins**.\n\n### 8.2. Use Relation Property Names\n\nGiven this Prisma schema:\n\n```prisma\nmodel bbs_article_comments {\n  //----\n  // COLUMNS\n  //----\n  id              String    @id @db.Uuid\n  bbs_article_id  String    @db.Uuid\n  bbs_user_id     String    @db.Uuid\n  body            String\n  created_at      DateTime  @db.Timestamptz\n  deleted_at      DateTime? @db.Timestamptz\n\n  //----\n  // BELONGED RELATIONS\n  //   - format: (propertyKey targetModel constraint)\n  //----\n  article         bbs_articles              @relation(fields: [bbs_article_id], references: [id], onDelete: Cascade)\n  user            bbs_users                 @relation(fields: [bbs_user_id], references: [id], onDelete: Cascade)\n\n  //----\n  // HAS RELATIONS\n  //   - format: (propertyKey targetModel)\n  //----\n  files           bbs_article_comment_files[]\n  hits            bbs_article_comment_hits[]\n}\n```\n\nIn both `select` and `create`, use the **relation property name** (left side of the model definition), not the referenced table name.\n\n### 8.3. Prisma Select (READ Operations)\n\n```typescript\n// \u2705 CORRECT - Use select with relation property names + satisfies\nconst comment = await MyGlobal.prisma.bbs_article_comments.findUniqueOrThrow({\n  where: { id: props.commentId },\n  select: {\n    id: true,\n    body: true,\n    user: {                                          // \u2705 Relation name\n      select: { id: true, name: true }\n    } satisfies Prisma.bbs_usersFindManyArgs,\n    files: {                                         // \u2705 Relation name\n      select: { id: true, url: true }\n    } satisfies Prisma.bbs_article_comment_filesFindManyArgs,\n    created_at: true,\n  }\n});\n\n// \u274C WRONG - Using include\ninclude: { user: true }\n\n// \u274C WRONG - Table name instead of relation property name\nbbs_users: { select: { id: true, name: true } }\n\n// \u274C WRONG - Foreign key as relation\nbbs_user_id: { select: {...} }  // bbs_user_id is scalar, not relation!\n```\n\nWhen a Transformer exists for a nested relation, reuse it (see Section 6.6). Assign `select()` directly \u2014 do NOT unwrap with `.select`:\n\n```typescript\nuser: BbsUserAtSummaryTransformer.select(),          // \u2705 Direct assignment\nuser: BbsUserAtSummaryTransformer.select().select,   // \u274C Strips the wrapper\n```\n\n### 8.4. Prisma CreateInput (CREATE Operations)\n\n```typescript\n// \u2705 CORRECT - Use connect with relation property names\nawait MyGlobal.prisma.bbs_article_comments.create({\n  data: {\n    id: v4(),\n    body: props.body.content,\n    article: { connect: { id: props.articleId } },    // \u2705 Relation name\n    user: { connect: { id: props.user.id } },         // \u2705 Relation name\n    created_at: new Date(),\n    deleted_at: null,\n  }\n});\n\n// \u274C WRONG - Table name instead of relation property name\nbbs_articles: { connect: { id: props.articleId } },\n\n// \u274C WRONG - Direct foreign key assignment\nbbs_article_id: props.articleId,\nbbs_user_id: props.user.id,\n```\n\n### 8.5. Data Transformation Rules\n\n| Transformation | Pattern |\n|----------------|---------|\n| Date \u2192 String | `record.created_at.toISOString()` |\n| Optional field (null \u2192 undefined) | `record.field === null ? undefined : record.field` |\n| Nullable field (keep null) | `record.field?.toISOString() ?? null` |\n| Branded type | `record.id as string & tags.Format<\"uuid\">` |\n| Nested object | `{ id: record.author.id, ... } satisfies IAuthor.ISummary` |\n\n**CRITICAL \u2014 `Date` vs `string & Format<\"date-time\">`**: Prisma `DateTime` fields return JavaScript `Date` objects. DTO types use `string & Format<\"date-time\">`. You MUST call `.toISOString()` when mapping Prisma results to DTO return objects. Using `new Date()` or a raw `Date` object directly causes:\n\n> `Type 'Date' is not assignable to type 'string & Format<\"date-time\">'`\n\n```typescript\n// \u274C WRONG \u2014 Date object in DTO return\nreturn {\n  created_at: new Date(),                    // TS2322\n  updated_at: record.updated_at,             // TS2322 (Date from Prisma)\n};\n\n// \u2705 CORRECT \u2014 always .toISOString() for DTO fields\nreturn {\n  created_at: new Date().toISOString(),                          // string\n  updated_at: record.updated_at.toISOString(),                   // string\n  deleted_at: record.deleted_at?.toISOString() ?? null,          // nullable\n};\n```\n\nNote: `new Date()` IS correct inside Prisma `data:` blocks (create/update) because Prisma accepts `Date` for `DateTime` columns. The error only occurs when returning to DTO types.\n\n**Nested object `satisfies` rule**: When manually constructing a return object, EVERY nested object literal that maps to a known DTO type MUST have `satisfies IDtoType` appended. This catches field mismatches at compile time.\n\n```typescript\n// \u2705 CORRECT - satisfies on every nested object\nreturn {\n  id: record.id,\n  title: record.title,\n  member: {\n    id: record.author.id,\n    name: record.author.name,\n    created_at: record.author.created_at.toISOString(),\n  } satisfies IBbsMember.ISummary,\n  category: {\n    id: record.category.id,\n    name: record.category.name,\n  } satisfies IBbsCategory.ISummary,\n  created_at: record.created_at.toISOString(),\n} satisfies IBbsArticle.ISummary;\n\n// \u274C WRONG - nested object without satisfies\nreturn {\n  id: record.id,\n  member: {\n    id: record.author.id,\n    name: record.author.name,\n  },  // Missing satisfies \u2014 type error points to the entire return, not this object\n};\n```\n\n### 8.6. DELETE Operation: Cascade Deletion\n\nAll tables use `onDelete: Cascade` in their foreign key relations. When deleting a record, simply delete the target row \u2014 the database automatically cascades to all dependent rows.\n\n```typescript\n// \u2705 CORRECT - Delete only the target record\nawait MyGlobal.prisma.shopping_sales.delete({\n  where: { id: props.saleId },\n});\n\n// \u274C WRONG - Manually deleting child records (unnecessary, cascade handles it)\nawait MyGlobal.prisma.shopping_sale_reviews.deleteMany({\n  where: { shopping_sale_id: props.saleId },\n});\nawait MyGlobal.prisma.shopping_sale_items.deleteMany({\n  where: { shopping_sale_id: props.saleId },\n});\nawait MyGlobal.prisma.shopping_sales.delete({\n  where: { id: props.saleId },\n});\n```\n\n### 8.7. Manual CREATE Example\n\n```typescript\nexport async function postShoppingSaleReview(props: {\n  customer: ActorPayload;\n  saleId: string & tags.Format<\"uuid\">;\n  body: IShoppingSaleReview.ICreate;\n}): Promise<IShoppingSaleReview> {\n  await MyGlobal.prisma.shopping_sales.findUniqueOrThrow({\n    where: { id: props.saleId },\n  });\n\n  const review = await MyGlobal.prisma.shopping_sale_reviews.create({\n    data: {\n      id: v4(),\n      content: props.body.content,\n      rating: props.body.rating,\n      sale: { connect: { id: props.saleId } },\n      customer: { connect: { id: props.customer.id } },\n      session: { connect: { id: props.customer.session_id } },\n      created_at: new Date(),\n      updated_at: new Date(),\n      deleted_at: null,\n    },\n  });\n\n  return {\n    id: review.id,\n    content: review.content,\n    rating: review.rating,\n    sale_id: review.shopping_sale_id,\n    customer_id: review.shopping_customer_id,\n    created_at: review.created_at.toISOString(),\n    updated_at: review.updated_at.toISOString(),\n    deleted_at: review.deleted_at?.toISOString() ?? null,\n  };\n}\n```\n\n## 9. Absolute Prohibitions\n\n### 9.1. No Runtime Type Validation on Parameters\n\n```typescript\n// \u274C FORBIDDEN - All type/format validation\nif (typeof props.title !== 'string') throw new Error();\nif (props.body.title.trim().length === 0) throw new HttpException();\nif (props.body.title.length > 100) throw new HttpException();\nif (/[\\r\\n]/.test(title)) throw new HttpException();\n\n// \u2705 CORRECT - Trust the framework (JSON Schema already validated)\nconst created = await MyGlobal.prisma.articles.create({\n  data: { title: props.body.title, ... }\n});\n```\n\n**Business logic validation is ALLOWED**:\n```typescript\n// \u2705 OK - Business constraint\nif (props.quantity > props.maxAllowed) {\n  throw new HttpException('Quantity exceeds maximum', 400);\n}\n```\n\n### 9.2. No Intermediate Variables for Prisma Parameters\n\n```typescript\n// \u2705 CORRECT - Inline parameters\nawait MyGlobal.prisma.sales.create({\n  data: { id: v4(), title: props.body.title, ... }\n});\n\n// \u274C WRONG - Intermediate variable\nconst data = { id: v4(), title: props.body.title };\nawait MyGlobal.prisma.sales.create({ data });\n```\n\n**Exception: Complex WHERE/ORDERBY conditions**:\n```typescript\n// \u2705 ALLOWED - Complex where with satisfies\nconst whereInput = {\n  deleted_at: null,\n  ...(body.title && { title: { contains: body.title } }),\n} satisfies Prisma.shopping_salesWhereInput;\n\nconst data = await MyGlobal.prisma.shopping_sales.findMany({ where: whereInput });\nconst total = await MyGlobal.prisma.shopping_sales.count({ where: whereInput });\n\n// \u2705 ALLOWED - OrderBy with ternary\nconst orderByInput = (\n  body.sort === 'price_asc' ? { price: 'asc' as const } :\n  { created_at: 'desc' as const }\n) satisfies Prisma.shopping_salesOrderByWithRelationInput;\n```\n\n### 9.3. No Raw SQL Queries\n\n**NEVER use `$queryRaw`, `$queryRawUnsafe`, `$executeRaw`, or `$executeRawUnsafe`**. Raw queries bypass Prisma's type system entirely \u2014 when column names, types, or tables change, the compiler cannot detect the breakage. The generic type parameter is a lie; it is never validated.\n\n```typescript\n// \u274C ABSOLUTELY FORBIDDEN - no compile-time safety\nconst result = await MyGlobal.prisma.$queryRaw<\n  Array<{ vote_type: string; count: number }>\n>`\n  SELECT vote_type, COUNT(*) as count\n  FROM comment_votes\n  WHERE comment_id = ${props.commentId}\n  GROUP BY vote_type\n`;\n\n// \u2705 CORRECT - use Prisma client (compile-time validated)\nconst votes = await MyGlobal.prisma.comment_votes.groupBy({\n  by: [\"vote_type\"],\n  where: { comment_id: props.commentId },\n  _count: { vote_type: true },\n});\n```\n\n**No exceptions.** Every query MUST go through the typed Prisma client API.\n\n### 9.4. Escape Sequences in JSON Context\n\n| Intent | Write This | After JSON Parse |\n|--------|------------|------------------|\n| `\\n` | `\\\\n` | `\\n` |\n| `\\r` | `\\\\r` | `\\r` |\n| `\\t` | `\\\\t` | `\\t` |\n\n## 10. HTTP Method Conventions\n\n| Method | Purpose | Request Body | Response Body | Name |\n|--------|---------|--------------|---------------|------|\n| POST | Create | `IEntity.ICreate` | `IEntity` | `create` |\n| GET | Read | null | `IEntity` | `at` |\n| PUT | Update | `IEntity.IUpdate` | `IEntity` | `update` |\n| DELETE | Delete | null | void | `erase` |\n| PATCH | List/Search | `IEntity.IRequest` | `IPageIEntity.ISummary` | `index` |\n\n## 11. Error Handling\n\n### 11.1. Record Not Found \u2192 Use `OrThrow`\n\nWhen a record must exist, use `findUniqueOrThrow` or `findFirstOrThrow`. The system automatically converts the thrown error into an HTTP 404 response \u2014 no manual null check or `HttpException` needed.\n\n```typescript\n// \u2705 CORRECT - OrThrow handles 404 automatically\nconst sale = await MyGlobal.prisma.shopping_sales.findUniqueOrThrow({\n  where: { id: props.saleId },\n});\n\n// Use plain findUnique/findFirst when null is a valid state in your logic\nconst existing = await MyGlobal.prisma.shopping_coupons.findUnique({\n  where: { id: props.couponId },\n});\nif (existing) {\n  // apply coupon logic\n}\n```\n\n### 11.2. Business Errors \u2192 `HttpException`\n\nFor business logic errors (not \"record not found\"), use `HttpException` with a numeric status code.\n\n```typescript\n// \u2705 CORRECT - HttpException with numeric status\nthrow new HttpException(\"Forbidden\", 403);\nthrow new HttpException(\"Quantity exceeds maximum\", 400);\n\n// \u274C WRONG - Plain Error\nthrow new Error(\"Something went wrong\");\n\n// \u274C WRONG - Enum status codes\nthrow new HttpException(\"Forbidden\", HttpStatus.FORBIDDEN);\n```\n\n## 12. Final Checklist\n\n### Code Structure\n- [ ] Starts with `export async function` (no arrow functions)\n- [ ] No namespace/class wrappers\n- [ ] No import statements\n- [ ] No runtime type validation on parameters\n- [ ] Function signature preserved exactly as given (no return type changes)\n\n### Collector/Transformer Reuse\n- [ ] Requested available collectors/transformers via preliminary calls\n- [ ] Used Collector for write side when available (`Collector.collect()`)\n- [ ] Used Transformer for read side when available (`Transformer.select()` + `Transformer.transform()`)\n- [ ] Checked neighbor Transformers for nested relations in manual code\n- [ ] Transformer.select() assigned directly (NOT `.select().select`)\n\n### Parameter Types\n- [ ] Only accessed properties that exist in the DTO type definition\n- [ ] Never invented DTO properties \u2014 used path params/auth context instead\n- [ ] Every `select` clause includes ALL fields accessed on the query result (relations, scalars, FK columns)\n\n### Manual Code (when no Collector/Transformer)\n- [ ] Verified ALL field/relation names against database schema\n- [ ] Used relation property names (NOT table names or FK columns)\n- [ ] Used `connect` syntax for relations (NOT direct FK assignment)\n- [ ] `satisfies Prisma.{table}FindManyArgs` on inline nested selects\n- [ ] Converted dates with `.toISOString()`\n- [ ] Handled null\u2192undefined for optional fields\n- [ ] Handled null\u2192null for nullable fields\n\n### Database Operations\n- [ ] Inline parameters (no intermediate variables except complex WHERE/ORDERBY)\n- [ ] Sequential await for findMany + count (NOT Promise.all)\n- [ ] `ArrayUtil.asyncMap` for Transformer list transforms\n- [ ] Regular `.map()` for manual list transforms\n- [ ] DELETE targets only the parent record (cascade handles children)\n- [ ] `findUniqueOrThrow`/`findFirstOrThrow` for record-must-exist queries" /* AutoBeSystemPromptConstant.REALIZE_OPERATION_WRITE */,
             },
             ...props.preliminary.getHistories(),
             ...authorizationHistories,

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

@@ -1 +1 @@
-{"version":3,"file":"transformRealizeOperationWriteHistory.js","sourceRoot":"","sources":["../../../../src/orchestrate/realize/histories/transformRealizeOperationWriteHistory.ts"],"names":[],"mappings":";;;AAEA,yCAA2C;AAC3C,+BAA0B;AAO1B,sGAAmG;AAEnG,gFAA6E;AAC7E,qGAAkG;AAE3F,MAAM,qCAAqC,GAAG,CAAC,KAYrD,EAA6B,EAAE;IAC9B,MAAM,QAAQ,GAA2B,MAAM,CAAC,WAAW,CACzD,KAAK,CAAC,mBAAmB,CAAC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC;QACpC,EAAE,CAAC,OAAO,CAAC,QAAQ;QACnB,EAAE,CAAC,OAAO,CAAC,OAAO;KACnB,CAAC,CACH,CAAC;IACF,MAAM,SAAS,GAA6B,KAAK,CAAC,QAAQ,CAAC,SAAS,CAAC;IACrE,MAAM,sBAAsB,GAC1B,SAAS,CAAC,iBAAiB;QACzB,CAAC,CAAC,IAAA,+EAAsC,EAAC,SAAS,EAAE,QAAQ,CAAC;QAC7D,CAAC,CAAC,EAAE,CAAC;IACT,MAAM,QAAQ,GAA4B,KAAK,CAAC,KAAK,CAAC,SAAU,CAAC,QAAQ,CAAC;IAE1E,OAAO;QACL,SAAS,EAAE;YACT;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,eAAe;gBACrB,IAAI,og7BAAoD;aACzD;YACD,GAAG,KAAK,CAAC,WAAW,CAAC,YAAY,EAAE;YACnC,GAAG,sBAAsB;YACzB;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,eAAe;gBACrB,IAAI,EAAE,yrEAA4D,UAAU,CAC1E,cAAc,EACd,IAAA,mDAAwB,EAAC,SAAS,EAAE,KAAK,CAAC,aAAa,CAAC,CACzD;qBACE,UAAU,CAAC,SAAS,EAAE,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC;qBAChD,UAAU,CACT,cAAc,2zCAEf;aACJ;YACD;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,IAAI,EAAE,eAAe;gBACrB,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,mEAAgC,CAAC,aAAa,CAAC;oBACnD,cAAc,EAAE,KAAK,CAAC,mBAAmB;oBACzC,OAAO,EAAE,QAAQ,CAAC,UAAU,CAAC,OAAO;oBACpC,SAAS;iBACV,CAAC;aACH;YACD;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,IAAI,EAAE,eAAe;gBACrB,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;YAIjB,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,QAAQ,CAAC;;SAEjC;aACF;YACD;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,kBAAkB;gBACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;;SAYpB;aACF;SACF;QACD,WAAW,EAAE,kBAAU,CAAC,IAAI,CAAA;iCACC,SAAS,CAAC,MAAM,CAAC,WAAW,EAAE,IAAI,SAAS,CAAC,IAAI;;;;;;;;;;;;;;;;;KAiB5E;KACF,CAAC;AACJ,CAAC,CAAC;AA/GW,QAAA,qCAAqC,yCA+GhD"}
+{"version":3,"file":"transformRealizeOperationWriteHistory.js","sourceRoot":"","sources":["../../../../src/orchestrate/realize/histories/transformRealizeOperationWriteHistory.ts"],"names":[],"mappings":";;;AAEA,yCAA2C;AAC3C,+BAA0B;AAO1B,sGAAmG;AAEnG,gFAA6E;AAC7E,qGAAkG;AAE3F,MAAM,qCAAqC,GAAG,CAAC,KAYrD,EAA6B,EAAE;IAC9B,MAAM,QAAQ,GAA2B,MAAM,CAAC,WAAW,CACzD,KAAK,CAAC,mBAAmB,CAAC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC;QACpC,EAAE,CAAC,OAAO,CAAC,QAAQ;QACnB,EAAE,CAAC,OAAO,CAAC,OAAO;KACnB,CAAC,CACH,CAAC;IACF,MAAM,SAAS,GAA6B,KAAK,CAAC,QAAQ,CAAC,SAAS,CAAC;IACrE,MAAM,sBAAsB,GAC1B,SAAS,CAAC,iBAAiB;QACzB,CAAC,CAAC,IAAA,+EAAsC,EAAC,SAAS,EAAE,QAAQ,CAAC;QAC7D,CAAC,CAAC,EAAE,CAAC;IACT,MAAM,QAAQ,GAA4B,KAAK,CAAC,KAAK,CAAC,SAAU,CAAC,QAAQ,CAAC;IAE1E,OAAO;QACL,SAAS,EAAE;YACT;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,eAAe;gBACrB,IAAI,2s8BAAoD;aACzD;YACD,GAAG,KAAK,CAAC,WAAW,CAAC,YAAY,EAAE;YACnC,GAAG,sBAAsB;YACzB;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,eAAe;gBACrB,IAAI,EAAE,yrEAA4D,UAAU,CAC1E,cAAc,EACd,IAAA,mDAAwB,EAAC,SAAS,EAAE,KAAK,CAAC,aAAa,CAAC,CACzD;qBACE,UAAU,CAAC,SAAS,EAAE,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC;qBAChD,UAAU,CACT,cAAc,2zCAEf;aACJ;YACD;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,IAAI,EAAE,eAAe;gBACrB,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,mEAAgC,CAAC,aAAa,CAAC;oBACnD,cAAc,EAAE,KAAK,CAAC,mBAAmB;oBACzC,OAAO,EAAE,QAAQ,CAAC,UAAU,CAAC,OAAO;oBACpC,SAAS;iBACV,CAAC;aACH;YACD;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,IAAI,EAAE,eAAe;gBACrB,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;YAIjB,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,QAAQ,CAAC;;SAEjC;aACF;YACD;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,kBAAkB;gBACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;;SAYpB;aACF;SACF;QACD,WAAW,EAAE,kBAAU,CAAC,IAAI,CAAA;iCACC,SAAS,CAAC,MAAM,CAAC,WAAW,EAAE,IAAI,SAAS,CAAC,IAAI;;;;;;;;;;;;;;;;;KAiB5E;KACF,CAAC;AACJ,CAAC,CAAC;AA/GW,QAAA,qCAAqC,yCA+GhD"}