@autobe/agent 0.24.2 → 0.25.1

package/src/orchestrate/test/orchestrateTestWrite.ts

@@ -22,10 +22,13 @@ import { IAutoBeTestWriteResult } from "./structures/IAutoBeTestWriteResult";
 
 export async function orchestrateTestWrite<Model extends ILlmSchema.Model>(
   ctx: AutoBeContext<Model>,
-  scenarios: AutoBeTestScenario[],
+  props: {
+    instruction: string;
+    scenarios: AutoBeTestScenario[];
+  },
 ): Promise<IAutoBeTestWriteResult[]> {
   const progress: AutoBeProgressEventBase = {
-    total: scenarios.length,
+    total: props.scenarios.length,
     completed: 0,
   };
   const result: Array<IAutoBeTestWriteResult | null> = await executeCachedBatch(
@@ -34,7 +37,7 @@ export async function orchestrateTestWrite<Model extends ILlmSchema.Model>(
      * individual test code implementations. Each scenario is processed to
      * generate corresponding test code and progress events.
      */
-    scenarios.map((scenario) => async (promptCacheKey) => {
+    props.scenarios.map((scenario) => async (promptCacheKey) => {
       try {
         const artifacts: IAutoBeTestScenarioArtifacts =
           await getTestScenarioArtifacts(ctx, scenario);
@@ -43,6 +46,7 @@ export async function orchestrateTestWrite<Model extends ILlmSchema.Model>(
           artifacts,
           progress,
           promptCacheKey,
+          instruction: props.instruction,
         });
         ctx.dispatch(event);
         return {
@@ -65,6 +69,7 @@ async function process<Model extends ILlmSchema.Model>(
     artifacts: IAutoBeTestScenarioArtifacts;
     progress: AutoBeProgressEventBase;
     promptCacheKey: string;
+    instruction: string;
   },
 ): Promise<AutoBeTestWriteEvent> {
   const { scenario, artifacts, progress, promptCacheKey } = props;
@@ -73,7 +78,11 @@ async function process<Model extends ILlmSchema.Model>(
   };
   const { tokenUsage } = await ctx.conversate({
     source: "testWrite",
-    histories: await transformTestWriteHistories(ctx, scenario, artifacts),
+    histories: await transformTestWriteHistories(ctx, {
+      scenario,
+      artifacts,
+      instruction: props.instruction,
+    }),
     controller: createController({
       model: ctx.model,
       build: (next) => {
@@ -90,11 +99,12 @@ async function process<Model extends ILlmSchema.Model>(
     throw new Error("Failed to create test code.");
   }
 
-  pointer.value.revise.final = await completeTestCode(
-    ctx,
-    artifacts,
-    pointer.value.revise.final,
-  );
+  if (pointer.value.revise.final)
+    pointer.value.revise.final = await completeTestCode(
+      ctx,
+      artifacts,
+      pointer.value.revise.final,
+    );
   pointer.value.draft = await completeTestCode(
     ctx,
     artifacts,
@@ -109,7 +119,7 @@ async function process<Model extends ILlmSchema.Model>(
     domain: pointer.value.domain,
     draft: pointer.value.draft,
     review: pointer.value.revise?.review,
-    final: pointer.value.revise?.final,
+    final: pointer.value.revise?.final ?? undefined,
     tokenUsage,
     completed: ++progress.completed,
     total: progress.total,

package/src/orchestrate/test/structures/IAutoBeTestCorrectApplication.ts

@@ -91,161 +91,6 @@ export namespace IAutoBeTestCorrectApplication {
     revise: IReviseProps;
   }
 
-  // /**
-  //  * Comprehensive compilation error analysis and correction planning
-  //  * properties.
-  //  *
-  //  * This interface structures the AI's deep thinking process during error
-  //  * correction, requiring individual analysis of each compilation error along
-  //  * with an overall strategy assessment. The AI must meticulously examine every
-  //  * error message, understand its root cause, and propose targeted solutions
-  //  * while maintaining a holistic view of the correction process.
-  //  *
-  //  * The structure enforces granular error analysis while ensuring the AI
-  //  * maintains awareness of overarching patterns and systemic issues that may
-  //  * require broader strategic changes like scenario rewrites or architectural
-  //  * adjustments.
-  //  */
-  // export interface IThinkProps {
-  //   /**
-  //    * Individual analyses for each compilation diagnostic.
-  //    *
-  //    * Contains detailed examination of every compilation error encountered,
-  //    * with specific analysis and targeted solutions. Each entry represents a
-  //    * single compilation diagnostic that must be resolved. The AI must read the
-  //    * IAutoBeTypeScriptCompileResult.IDiagnostic objects, interpret their
-  //    * content, and provide human-readable summaries along with precise fixes.
-  //    *
-  //    * This granular approach ensures no error is overlooked and each issue
-  //    * receives appropriate attention and resolution strategy.
-  //    */
-  //   analyses: IDiagnosticAnalysis[] & tags.MinItems<1>;
-
-  //   /**
-  //    * Overall assessment of compilation issues and correction strategies.
-  //    *
-  //    * Synthesizes patterns across all individual errors to identify systemic
-  //    * issues and overarching correction strategies. This includes verification
-  //    * of TEST_WRITE.md and TEST_CORRECT.md compliance, assessment of whether
-  //    * scenario rewrites are needed, identification of common error patterns,
-  //    * and documentation of broad strategic decisions.
-  //    *
-  //    * Must address: type safety compliance, async/await patterns, scenario
-  //    * adaptation requirements, and overall code quality considerations that
-  //    * span multiple errors.
-  //    */
-  //   overall: string;
-  // }
-
-  // /**
-  //  * Detailed analysis structure for individual compilation diagnostics.
-  //  *
-  //  * Represents the AI's systematic approach to understanding and resolving each
-  //  * compilation diagnostic. Each diagnostic must be thoroughly analyzed to
-  //  * understand its root cause, with a specific solution that addresses the
-  //  * exact issue while maintaining type safety and code quality.
-  //  */
-  // export interface IDiagnosticAnalysis {
-  //   /**
-  //    * AI-generated summary of the compilation diagnostic.
-  //    *
-  //    * The AI must analyze the `IAutoBeTypeScriptCompileResult.IDiagnostic`
-  //    * object and provide a clear, concise summary of the error. This should
-  //    * include the error message, file location, line/column position, and error
-  //    * code in a human-readable format. The AI interprets and restructures the
-  //    * raw diagnostic data to present it in a more understandable way.
-  //    *
-  //    * **IMPORTANT**: The AI should not copy the raw diagnostic object. Instead,
-  //    * it must read and understand the diagnostic details, then compose a clear
-  //    * string description that captures all essential information about the
-  //    * error.
-  //    */
-  //   diagnostic: string;
-
-  //   /**
-  //    * Root cause analysis of why this compilation error occurred.
-  //    *
-  //    * **🚨 CRITICAL FIRST CHECK: Is this caused by INTENTIONAL TYPE ERROR TESTING? 🚨**
-  //    * - Look for `as any` usage in the error location
-  //    * - Check if code is intentionally sending wrong types to test type validation
-  //    * - Check if code is testing missing required fields
-  //    * - **IF YES → Root cause: "Prohibited type error testing code that must be DELETED"**
-  //    *
-  //    * **⚠️ THINK BEYOND THE DIAGNOSTIC LINE - EXPAND YOUR INVESTIGATION ⚠️**
-  //    * - Do NOT focus only on the error line - it might be just a symptom
-  //    * - The real cause might be ABOVE the error location in earlier code
-  //    * - The test scenario itself might be fundamentally flawed or impossible
-  //    * - Consider if the scenario is requesting non-existent APIs or prohibited actions
-  //    * - Example: Error on line 50 might be caused by wrong type assignment on line 20
-  //    * - Example: API call fails because the scenario describes unimplemented functionality
-  //    *
-  //    * AI must examine the error message carefully and identify the specific
-  //    * reason for failure. This includes understanding whether it's a missing
-  //    * property, type mismatch, nullable/undefined issue, incorrect API usage,
-  //    * intentional type error testing, flawed scenario, or other TypeScript
-  //    * violations. The analysis should be precise and fact-based, but also
-  //    * consider the broader context and causal relationships.
-  //    *
-  //    * **MANDATORY**: The AI must thoroughly review ALL sections of
-  //    * TEST_CORRECT.md and apply relevant error patterns and analysis guidelines
-  //    * from sections 4.1-4.16 to ensure accurate diagnosis.
-  //    *
-  //    * Example: "Property 'code' is missing because the object literal lacks
-  //    * this required field from ICommunityPlatformCommunity.ICreate interface"
-  //    *
-  //    * Example: "Type error caused by intentional wrong type test using 'as any'
-  //    * - prohibited pattern that must be deleted"
-  //    *
-  //    * Example: "API endpoint doesn't exist - scenario requests unimplemented
-  //    * functionality that cannot be tested"
-  //    */
-  //   analysis: string;
-
-  //   /**
-  //    * Specific solution to resolve this compilation error.
-  //    *
-  //    * **🚨 IF ROOT CAUSE IS TYPE ERROR TESTING → Solution: "DELETE entire test block" 🚨**
-  //    * **🚨 IF PROBLEM IS UNRECOVERABLE → Solution: "DELETE the problematic section" 🚨**
-  //    * - NEVER try to "fix" intentional type error tests - DELETE them
-  //    * - NEVER violate type safety to force a fix - DELETE instead
-  //    * - Tests using `as any` to send wrong types must be DELETED
-  //    * - Tests checking type validation must be DELETED
-  //    * - Unrecoverable compilation errors should result in DELETION
-  //    *
-  //    * **THREE SOLUTION TYPES:**
-  //    * 1. **FIX**: Correct the error while maintaining functionality
-  //    * 2. **DELETE**: Remove prohibited or unrecoverable code entirely
-  //    * 3. **REWRITE**: Restructure if the scenario itself is fundamentally flawed
-  //    *
-  //    * Detailed correction strategy that addresses the exact issue identified in
-  //    * the analysis. Solutions must be actionable, type-safe, and compliant with
-  //    * all project guidelines. For nullable/undefined errors with typia tags,
-  //    * immediately apply typia.assert(value!) pattern. For missing properties,
-  //    * specify what will be added and how.
-  //    *
-  //    * **CRITICAL**: The AI must thoroughly review BOTH TEST_WRITE.md and
-  //    * TEST_CORRECT.md before proposing solutions. All prohibitions from
-  //    * TEST_WRITE.md must be strictly respected (no type bypasses, proper
-  //    * async/await usage, etc.), and correction patterns from TEST_CORRECT.md
-  //    * sections 4.1-4.16 must be properly applied.
-  //    *
-  //    * **DELETION IS A VALID SOLUTION** when:
-  //    * - Code violates absolute prohibitions
-  //    * - Fixing would require type safety violations
-  //    * - The scenario describes impossible functionality
-  //    * - Multiple fix attempts have failed
-  //    *
-  //    * Example: "Add missing 'code' property using typia.random<string>() to
-  //    * generate a valid string value that satisfies the interface requirement"
-  //    *
-  //    * Example: "DELETE this entire test - it's testing type errors with 'as any'"
-  //    *
-  //    * Example: "DELETE this section - API endpoint doesn't exist and cannot be
-  //    * tested without violating type safety"
-  //    */
-  //   solution: string;
-  // }
-
   /**
    * Revision properties for the final review and implementation phases.
    *
@@ -253,74 +98,6 @@ export namespace IAutoBeTestCorrectApplication {
    * workflow, ensuring systematic review and production-ready code delivery.
    */
   export interface IReviseProps {
-    // /**
-    //  * Dual-document compliance validation for TEST_WRITE.md and
-    //  * TEST_CORRECT.md.
-    //  *
-    //  * This property tracks whether each section from BOTH TEST_WRITE.md and
-    //  * TEST_CORRECT.md guidelines has been properly followed. Since the correct
-    //  * agent must ensure compliance with both documents, keys should include
-    //  * sections from both prompt files.
-    //  *
-    //  * Each ICheck item should have:
-    //  *
-    //  * - Title: Prefixed with source document for clarity ("TEST_WRITE: " or
-    //  *   "TEST_CORRECT: ")
-    //  * - State: Compliance status (true if followed, false if violated)
-    //  *
-    //  * Note: Section identifiers may evolve as documentation updates, so
-    //  * implementations should be flexible in handling different key formats.
-    //  *
-    //  * Example:
-    //  *
-    //  * ```typescript
-    //  * rules: [
-    //  *   { title: "TEST_WRITE: 1. Role and Responsibility", state: true },
-    //  *   { title: "TEST_WRITE: 3.1. Import Management", state: true },
-    //  *   {
-    //  *     title: "TEST_CORRECT: 4.1. Missing Properties Pattern",
-    //  *     state: true,
-    //  *   },
-    //  *   {
-    //  *     title: "TEST_CORRECT: 4.2. Type Mismatch Pattern",
-    //  *     state: false,
-    //  *   },
-    //  *   // ... other sections from both documents
-    //  * ];
-    //  * ```
-    //  */
-    // rules: ICheck[] & tags.MinItems<1>;
-
-    // /**
-    //  * Combined quality checklist validation from both prompt documents.
-    //  *
-    //  * This property captures the compliance status for checklist items from
-    //  * BOTH TEST_WRITE.md (Section 5: Final Checklist) and TEST_CORRECT.md
-    //  * (Section 5: Final Review Checklist). The correct agent must validate
-    //  * against both checklists to ensure comprehensive quality control.
-    //  *
-    //  * Each ICheck item should have:
-    //  *
-    //  * - Title: Checklist item as described in the documents
-    //  * - State: Whether the criterion has been satisfied
-    //  *
-    //  * Note: Checklist items may be updated over time, so implementations should
-    //  * adapt to documentation changes while maintaining the validation purpose.
-    //  *
-    //  * Example:
-    //  *
-    //  * ```typescript
-    //  * checkList: [
-    //  *   { title: "No compilation errors", state: true },
-    //  *   { title: "Proper async/await usage", state: true },
-    //  *   { title: "All typia tags preserved", state: true },
-    //  *   { title: "No type bypasses or workarounds", state: false },
-    //  *   // ... other checklist items from both documents
-    //  * ];
-    //  * ```
-    //  */
-    // checkList: ICheck[] & tags.MinItems<1>;
-
     /**
      * Step 3: Code review and correction validation.
      *
@@ -347,17 +124,21 @@ export namespace IAutoBeTestCorrectApplication {
      * incorporating all review feedback and validation results. This code
      * represents the completed error correction, guaranteed to compile
      * successfully while preserving all original test functionality and
-     * business logic.
+     * business logic. When the draft correction already perfectly resolves all
+     * issues with no problems found during review, this value can be null,
+     * indicating no further refinement was necessary.
      *
      * The final implementation resolves all compilation issues, maintains
      * strict type safety, follows all established conventions, and delivers a
      * production-ready test that accurately validates the intended API
-     * behaviors and user workflows.
+     * behaviors and user workflows. A null value signifies the draft correction
+     * was already optimal and requires no modifications.
      *
      * Workflow: Review integration → Final refinement → Production-ready
-     * implementation. This is the ultimate deliverable that will replace the
-     * compilation-failed code.
+     * implementation (or null if draft needs no changes). This is the ultimate
+     * deliverable that will replace the compilation-failed code when provided,
+     * otherwise the draft correction is used as-is.
      */
-    final: string;
+    final: string | null;
   }
 }

package/src/orchestrate/test/structures/IAutoBeTestCorrectInvalidRequestApplication.ts

@@ -131,7 +131,10 @@ export namespace IAutoBeTestCorrectInvalidRequestApplication {
      * Final corrected code.
      *
      * The complete, cleaned test code with all invalid API request sections
-     * removed, ready for compilation.
+     * removed, ready for compilation. When the draft already successfully
+     * removes all problematic code with no additional issues found during
+     * review, this value can be null, indicating the draft deletion was
+     * sufficient and requires no further changes.
      *
      * This code must:
      *
@@ -140,7 +143,10 @@ export namespace IAutoBeTestCorrectInvalidRequestApplication {
      * - Have no `as any` or similar type violations
      * - Maintain the original file structure
      * - Be production-ready E2E test code
+     *
+     * A null value indicates the draft successfully removed all invalid code
+     * and needs no additional modifications.
      */
-    final: string;
+    final: string | null;
   }
 }

package/src/orchestrate/test/structures/IAutoBeTestWriteApplication.ts

@@ -65,8 +65,8 @@ export namespace IAutoBeTestWriteApplication {
      *
      * Contains the iterative improvement workflow that transforms the initial
      * draft into production-ready test code. The review phase identifies issues
-     * to fix or code to delete, followed by the final phase that produces
-     * the polished, production-ready test implementation.
+     * to fix or code to delete, followed by the final phase that produces the
+     * polished, production-ready test implementation.
      *
      * Workflow: Draft → Review analysis → Final implementation
      */
@@ -74,52 +74,6 @@ export namespace IAutoBeTestWriteApplication {
   }
 
   export interface IReviseProps {
-    // /**
-    //  * Test implementation rules compliance validation.
-    //  *
-    //  * This property tracks whether each section of the TEST_WRITE.md guidelines
-    //  * has been properly followed. Each array element represents a section from
-    //  * the documentation with its title and compliance status.
-    //  *
-    //  * Note: The specific section titles may evolve as documentation updates, so
-    //  * implementations should be flexible in handling different titles.
-    //  *
-    //  * Example:
-    //  *
-    //  * ```typescript
-    //  * rules: [
-    //  *   { title: "1. Role and Responsibility", state: true },
-    //  *   { title: "2. Input Materials Provided", state: true },
-    //  *   { title: "3. Code Generation Requirements", state: false },
-    //  *   // ... other sections
-    //  * ];
-    //  * ```
-    //  */
-    // rules: ICheck[] & tags.MinItems<1>;
-
-    // /**
-    //  * Final quality checklist validation results.
-    //  *
-    //  * This property captures the compliance status for each item in the Final
-    //  * Checklist (Section 5) from TEST_WRITE.md. Each array element represents a
-    //  * checklist item with its description and validation result.
-    //  *
-    //  * Note: Checklist items may be updated over time, so implementations should
-    //  * adapt to documentation changes while maintaining the validation purpose.
-    //  *
-    //  * Example:
-    //  *
-    //  * ```typescript
-    //  * checkList: [
-    //  *   { title: "NO additional import statements", state: true },
-    //  *   { title: "NO wrong type data in requests", state: true },
-    //  *   { title: "EVERY api.functional.* call has await", state: false },
-    //  *   // ... other checklist items
-    //  * ];
-    //  * ```
-    //  */
-    // checkList: ICheck[] & tags.MinItems<1>;
-
     /**
      * Step 4: Code review and quality assessment.
      *
@@ -180,7 +134,9 @@ export namespace IAutoBeTestWriteApplication {
      *
      * AI produces the final, polished version of the test code incorporating
      * all review feedback. This code represents the completed test
-     * implementation, ready for production deployment.
+     * implementation, ready for production deployment. When the draft code is
+     * already perfect with no issues found during review, this value can be
+     * null, indicating no revisions were necessary.
      *
      * **🚨 CRITICAL: APPLY ALL FIXES AND DELETIONS FROM REVIEW 🚨**
      *
@@ -188,41 +144,18 @@ export namespace IAutoBeTestWriteApplication {
      * - DELETE all prohibited code identified in review
      * - If review found type error tests, they MUST be deleted in final
      * - If review found code to DELETE, final MUST be different from draft
+     * - If review finds NO issues requiring changes, set to null
      *
      * All identified issues must be resolved, and the code must meet the
-     * highest quality standards.
+     * highest quality standards. A null value indicates the draft code already
+     * meets all requirements without modification.
      *
      * Workflow: Review feedback → Apply FIXES → Apply DELETIONS →
-     * Production-ready implementation
+     * Production-ready implementation (or null if no changes needed)
      *
      * This is the ultimate deliverable that will be used in the actual test
-     * suite.
+     * suite when provided, otherwise the draft is used as-is.
      */
-    final: string;
+    final: string | null;
   }
-
-  // /**
-  //  * Check validation item structure.
-  //  *
-  //  * Represents a validation check with its title and compliance state. Used for
-  //  * both rules validation and final checklist validation.
-  //  */
-  // export interface ICheck {
-  //   /**
-  //    * The title or description of the check.
-  //    *
-  //    * For rules: Section identifiers from TEST_WRITE.md (e.g., "1. Role and
-  //    * Responsibility") For checklist: Checklist item descriptions (e.g., "No
-  //    * compilation errors")
-  //    */
-  //   title: string;
-
-  //   /**
-  //    * The validation state of this check.
-  //    *
-  //    * - True: The requirement has been satisfied
-  //    * - False: The requirement has been violated or not met
-  //    */
-  //   state: boolean;
-  // }
 }

package/src/orchestrate/test/utils/getPrerequisites.ts

@@ -0,0 +1,51 @@
+import { AutoBeOpenApi } from "@autobe/interface";
+import { AutoBeOpenApiEndpointComparator } from "@autobe/utils";
+import { HashMap } from "tstl";
+
+export const getPrerequisites = (props: {
+  document: AutoBeOpenApi.IDocument;
+  endpoint: AutoBeOpenApi.IEndpoint;
+}): AutoBeOpenApi.IPrerequisite[] => {
+  const visited: Set<string> = new Set<string>();
+  const result: HashMap<
+    AutoBeOpenApi.IEndpoint,
+    AutoBeOpenApi.IPrerequisite[]
+  > = new HashMap<AutoBeOpenApi.IEndpoint, AutoBeOpenApi.IPrerequisite[]>(
+    AutoBeOpenApiEndpointComparator.hashCode,
+    AutoBeOpenApiEndpointComparator.equals,
+  );
+
+  const traverse = (endpoint: AutoBeOpenApi.IEndpoint): void => {
+    const key = `${endpoint.method}:${endpoint.path}`;
+
+    // prevent circular structure: skip visited endpoint
+    if (visited.has(key)) return;
+    visited.add(key);
+
+    const operation: AutoBeOpenApi.IOperation | undefined =
+      props.document.operations.find(
+        (op) => op.method === endpoint.method && op.path === endpoint.path,
+      );
+
+    if (operation === undefined) return;
+
+    // add current operation's prerequisites
+    for (const prerequisite of operation.prerequisites) {
+      // check if already in result to avoid duplicates
+      const exists: boolean = result.has(prerequisite.endpoint);
+
+      if (!exists) {
+        result.set(prerequisite.endpoint, [prerequisite]);
+      }
+
+      // recursively traverse prerequisite's prerequisites
+      traverse(prerequisite.endpoint);
+    }
+  };
+
+  traverse(props.endpoint);
+  return result
+    .toJSON()
+    .map((it) => it.second)
+    .flat();
+};

package/src/orchestrate/test/utils/getReferenceIds.ts

@@ -7,7 +7,8 @@ export const getReferenceIds = (props: {
 }): string[] => {
   const result: Set<string> = new Set();
   const emplace = (key: string) => {
-    if (key.endsWith("_id") || key.endsWith("Id")) result.add(key);
+    if (key.endsWith("_id") || key.endsWith("Id") || key === "id")
+      result.add(key);
   };
 
   props.operation.parameters.forEach((p) => emplace(p.name));

package/lib/orchestrate/common/histories/transformCommonCorrectDateHistories.js

@@ -1,48 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.transformCommonCorrectDateHistories = void 0;
-const utils_1 = require("@autobe/utils");
-const uuid_1 = require("uuid");
-/** Transform date correction histories for AI conversation */
-const transformCommonCorrectDateHistories = (failures) => [
-    {
-        id: (0, uuid_1.v7)(),
-        created_at: new Date().toISOString(),
-        type: "systemMessage",
-        text: "<!--\nfilename: REALIZE_DATE.md\n-->\n# \uD83D\uDCC5 Date Type Handling Guide for Realize Agent\n\n## \uD83D\uDEA8 CRITICAL: Date Type is ABSOLUTELY FORBIDDEN in TypeScript Declarations\n\nThis document provides comprehensive guidelines for handling date-related types in the Realize Agent system. Violations of these rules will cause compilation failures.\n\n## \uD83D\uDD34 The Golden Rule: NEVER Use Native Date Type\n\n### \u274C ABSOLUTELY FORBIDDEN\n```typescript\n// NEVER declare variables with Date type\nconst now: Date = new Date();                              // \u274C FORBIDDEN\nconst processDate = (date: Date) => { ... };               // \u274C FORBIDDEN\nfunction getDate(): Date { ... }                           // \u274C FORBIDDEN\ninterface IUser { created_at: Date; }                      // \u274C FORBIDDEN\ntype TimeStamp = Date;                                     // \u274C FORBIDDEN\n```\n\n### \u2705 REQUIRED: Always Use String with Tags\n```typescript\n// ALWAYS use string with tags.Format<'date-time'>\nconst now: string & tags.Format<'date-time'> = toISOStringSafe(new Date());\nconst processDate = (date: string & tags.Format<'date-time'>) => { ... };\nfunction getDate(): string & tags.Format<'date-time'> { ... }\ninterface IUser { created_at: string & tags.Format<'date-time'>; }\ntype TimeStamp = string & tags.Format<'date-time'>;\n```\n\n## \uD83D\uDEE0\uFE0F The toISOStringSafe() Function\n\n### Function Signature\n```typescript\nfunction toISOStringSafe(\n  value: Date | (string & tags.Format<\"date-time\">)\n): string & tags.Format<\"date-time\">\n```\n\n### Purpose\n`toISOStringSafe()` is the ONLY approved method for converting Date objects or date strings to ISO strings with proper type branding.\n\n### \u26A0\uFE0F CRITICAL: Parameter Requirements\n\n**toISOStringSafe REQUIRES a non-null parameter!**\n- The function accepts `Date` or ISO string format\n- It does NOT accept `null` or `undefined`\n- Always check for null/undefined BEFORE calling\n\n```typescript\n// \u274C WRONG: Function doesn't accept null\ntoISOStringSafe(nullableValue)                             // Type error if nullable!\n\n// \u2705 CORRECT: Check null first, then call\nvalue ? toISOStringSafe(value) : null                      // Safe null handling\n```\n\n### Common Usage Patterns\n\n#### 1. Creating New Timestamps\n```typescript\n// \u2705 For new timestamps\nconst created_at = toISOStringSafe(new Date());\nconst updated_at = toISOStringSafe(new Date());\n\n// \u2705 Converting existing date strings\nconst formatted_date = toISOStringSafe(dateString);\n```\n\n#### 2. Converting Prisma DateTime Fields\n```typescript\n// \u2705 Converting from Prisma (which returns Date objects)\nreturn {\n  created_at: toISOStringSafe(created.created_at),\n  updated_at: toISOStringSafe(created.updated_at),\n  expires_at: created.expires_at ? toISOStringSafe(created.expires_at) : null,\n};\n```\n\n#### 3. Processing API Input Dates\n```typescript\n// \u2705 Converting date strings from API input\nawait MyGlobal.prisma.posts.create({\n  data: {\n    title: body.title,\n    content: body.content,\n    published_at: body.published_at ? toISOStringSafe(body.published_at) : null,\n    scheduled_at: body.scheduled_at ? toISOStringSafe(body.scheduled_at) : null,\n  },\n});\n```\n\n## \uD83D\uDCCA Date Field Patterns in Different Contexts\n\n### 1. Prisma Operations\n\n#### CREATE Operations\n```typescript\nawait MyGlobal.prisma.articles.create({\n  data: {\n    id: v4() as string & tags.Format<'uuid'>,\n    title: body.title,\n    content: body.content,\n    // Required date fields\n    created_at: toISOStringSafe(new Date()),\n    updated_at: toISOStringSafe(new Date()),\n    // Optional/nullable date fields\n    published_at: body.published_at ? toISOStringSafe(body.published_at) : null,\n    deleted_at: null,  // If soft delete field exists\n  },\n});\n```\n\n#### UPDATE Operations\n```typescript\nawait MyGlobal.prisma.articles.update({\n  where: { id: parameters.id },\n  data: {\n    title: body.title,\n    content: body.content,\n    // Always update the updated_at field\n    updated_at: toISOStringSafe(new Date()),\n    // Conditional date updates\n    ...(body.published_at !== undefined && {\n      published_at: body.published_at ? toISOStringSafe(body.published_at) : null\n    }),\n  },\n});\n```\n\n#### WHERE Clauses with Date Ranges\n```typescript\nawait MyGlobal.prisma.events.findMany({\n  where: {\n    // Date range queries\n    created_at: {\n      gte: body.start_date ? toISOStringSafe(body.start_date) : undefined,\n      lte: body.end_date ? toISOStringSafe(body.end_date) : undefined,\n    },\n    // Specific date comparisons\n    expires_at: {\n      gt: toISOStringSafe(new Date()),  // Events not yet expired\n    },\n  },\n});\n```\n\n### 2. Return Object Transformations\n\n#### From Prisma to API Response\n```typescript\n// Prisma returns Date objects, API expects ISO strings\nconst users = await MyGlobal.prisma.users.findMany();\n\nreturn users.map(user => ({\n  id: user.id,\n  name: user.name,\n  email: user.email,\n  // Convert all Date fields to ISO strings\n  created_at: toISOStringSafe(user.created_at),\n  updated_at: toISOStringSafe(user.updated_at),\n  last_login_at: user.last_login_at ? toISOStringSafe(user.last_login_at) : null,\n  email_verified_at: user.email_verified_at ? toISOStringSafe(user.email_verified_at) : null,\n}));\n```\n\n### 3. Complex Date Operations\n\n#### Soft Delete Implementation\n```typescript\n// If schema has deleted_at field (always check first!)\nawait MyGlobal.prisma.posts.update({\n  where: { id: parameters.id },\n  data: {\n    deleted_at: toISOStringSafe(new Date()),  // Mark as deleted\n    updated_at: toISOStringSafe(new Date()),\n  },\n});\n\n// Querying non-deleted items\nawait MyGlobal.prisma.posts.findMany({\n  where: {\n    deleted_at: null,  // Only get non-deleted posts\n  },\n});\n```\n\n#### Date Calculations\n```typescript\n// Calculate expiry date (30 days from now)\nconst now = new Date();\nconst expiryDate = new Date(now.getTime() + 30 * 24 * 60 * 60 * 1000);\n\nawait MyGlobal.prisma.subscriptions.create({\n  data: {\n    user_id: user.id,\n    started_at: toISOStringSafe(now),\n    expires_at: toISOStringSafe(expiryDate),\n  },\n});\n```\n\n## \uD83D\uDEAB Common Date Type Errors and Solutions\n\n### Error: \"Type 'Date' is not assignable to type 'string & tags.Format<'date-time'>'\"\n\n**Cause**: Trying to assign a Date object directly without conversion\n\n```typescript\n// \u274C WRONG\nreturn {\n  created_at: new Date(),  // ERROR!\n};\n\n// \u2705 CORRECT\nreturn {\n  created_at: toISOStringSafe(new Date()),\n};\n```\n\n### Error: \"Argument of type 'null' is not assignable to parameter\"\n\n**Cause**: Trying to pass null or undefined to toISOStringSafe\n\n```typescript\n// \u274C WRONG\nconst date = toISOStringSafe(nullableDate);  // Type error if nullable!\n\n// \u2705 CORRECT\nconst date = nullableDate ? toISOStringSafe(nullableDate) : null;\n```\n\n### Error: \"Type 'string | null' is not assignable to type 'string & tags.Format<'date-time'>'\"\n\n**Cause**: Nullable date field being assigned to required date field\n\n```typescript\n// \u274C WRONG (if API expects non-nullable)\nreturn {\n  created_at: user.created_at ? toISOStringSafe(user.created_at) : null,  // ERROR!\n};\n\n// \u2705 CORRECT (provide default for required fields)\nreturn {\n  created_at: user.created_at \n    ? toISOStringSafe(user.created_at) \n    : toISOStringSafe(new Date()),  // Default to current time\n};\n```\n\n## \uD83D\uDCCB Date Type Checklist\n\nBefore implementing any date-related functionality, verify:\n\n1. \u2705 **NO Date type declarations** - Search for `: Date` in your code\n2. \u2705 **All Date objects wrapped in toISOStringSafe()** - Never use .toISOString() directly\n3. \u2705 **Null checks before toISOStringSafe()** - Function cannot handle null\n4. \u2705 **Proper type annotations** - Use `string & tags.Format<'date-time'>`\n5. \u2705 **Schema verification** - Check if date fields actually exist in Prisma schema\n6. \u2705 **API contract alignment** - Verify if fields are nullable or required in DTOs\n\n## \uD83C\uDFAF Quick Reference\n\n### DO \u2705\n- `toISOStringSafe(new Date())`\n- `toISOStringSafe(dateString)` for existing strings\n- `value ? toISOStringSafe(value) : null` for nullable values\n- `string & tags.Format<'date-time'>` for type declarations\n- Check null/undefined BEFORE calling toISOStringSafe\n- Check Prisma schema for date field existence\n\n### DON'T \u274C\n- `const date: Date = new Date()` - storing Date in variables\n- `new Date().toISOString()` - use toISOStringSafe instead\n- `toISOStringSafe(nullableValue)` - function doesn't accept null\n- `toISOStringSafe()` - function requires a parameter\n- Assume date fields exist (like deleted_at)\n- Use Date type in function signatures\n\n## \uD83D\uDD0D Exception: new Date() Usage\n\nThe ONLY acceptable use of `new Date()` is as an immediate argument to `toISOStringSafe()`:\n\n```typescript\n// \u2705 ONLY ALLOWED PATTERN\nconst timestamp = toISOStringSafe(new Date());\n\n// \u274C NEVER STORE Date IN VARIABLE\nconst now = new Date();  // FORBIDDEN!\nconst timestamp = toISOStringSafe(now);  // VIOLATION!\n```\n\n## \uD83D\uDCDD Summary\n\nThe Date type handling in Realize Agent follows a strict pattern:\n1. **Never** declare Date types in TypeScript\n2. **Always** use `string & tags.Format<'date-time'>` for type declarations\n3. **Always** use `toISOStringSafe()` for Date/string to ISO conversions\n4. **Always** check null/undefined before calling `toISOStringSafe()` - it doesn't accept null\n5. **Always** pass a parameter to `toISOStringSafe()` - it's not optional\n6. **Always** verify schema before using date fields\n\nFollowing these rules ensures type safety, prevents runtime errors, and maintains consistency across the entire codebase." /* AutoBeSystemPromptConstant.REALIZE_DATE */,
-    },
-    ...failures.map((f, i, array) => ({
-        id: (0, uuid_1.v7)(),
-        created_at: new Date().toISOString(),
-        type: "assistantMessage",
-        text: utils_1.StringUtil.trim `
-          # ${i === array.length - 1 ? "Latest Date Type Failure" : "Previous Date Type Failure"}
-          
-          ## Generated TypeScript Code
-          \`\`\`typescript
-          ${f.script}
-          \`\`\`
-          
-          ## Date-Related Compile Errors
-          ${f.diagnostics
-            .map((d) => {
-            const location = d.file
-                ? `[${d.file}${d.start ? `:${d.start}` : ""}]`
-                : "[Unknown location]";
-            const code = d.code ? `TS${d.code}` : "";
-            const messageText = d.messageText || "Date type error";
-            return `- ${location} ${code}: ${messageText}`;
-        })
-            .join("\n")}
-          
-          ## Required Fixes:
-          - Replace all Date type declarations with string & tags.Format<"date-time">
-          - Wrap Date objects with toISOStringSafe(value)
-          - Check null/undefined BEFORE calling toISOStringSafe (it doesn't accept null)
-          - Remove Date variable declarations (const now = new Date() is forbidden)
-          - toISOStringSafe requires a parameter - it's not optional
-        `,
-    })),
-];
-exports.transformCommonCorrectDateHistories = transformCommonCorrectDateHistories;
-//# sourceMappingURL=transformCommonCorrectDateHistories.js.map

package/lib/orchestrate/common/histories/transformCommonCorrectDateHistories.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"transformCommonCorrectDateHistories.js","sourceRoot":"","sources":["../../../../src/orchestrate/common/histories/transformCommonCorrectDateHistories.ts"],"names":[],"mappings":";;;AAEA,yCAA2C;AAC3C,+BAA0B;AAS1B,8DAA8D;AACvD,MAAM,mCAAmC,GAAG,CACjD,QAAoB,EAGpB,EAAE,CAAC;IACH;QACE,EAAE,EAAE,IAAA,SAAE,GAAE;QACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;QACpC,IAAI,EAAE,eAAe;QACrB,IAAI,+wTAAyC;KAC9C;IACD,GAAG,QAAQ,CAAC,GAAG,CACb,CAAC,CAAC,EAAE,CAAC,EAAE,KAAK,EAAE,EAAE,CACd,CAAC;QACC,EAAE,EAAE,IAAA,SAAE,GAAE;QACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;QACpC,IAAI,EAAE,kBAAkB;QACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;cACf,CAAC,KAAK,KAAK,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,0BAA0B,CAAC,CAAC,CAAC,4BAA4B;;;;YAIpF,CAAC,CAAC,MAAM;;;;YAIR,CAAC,CAAC,WAAW;aACZ,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE;YACT,MAAM,QAAQ,GAAG,CAAC,CAAC,IAAI;gBACrB,CAAC,CAAC,IAAI,CAAC,CAAC,IAAI,GAAG,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,KAAK,EAAE,CAAC,CAAC,CAAC,EAAE,GAAG;gBAC9C,CAAC,CAAC,oBAAoB,CAAC;YACzB,MAAM,IAAI,GAAG,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;YACzC,MAAM,WAAW,GAAG,CAAC,CAAC,WAAW,IAAI,iBAAiB,CAAC;YACvD,OAAO,KAAK,QAAQ,IAAI,IAAI,KAAK,WAAW,EAAE,CAAC;QACjD,CAAC,CAAC;aACD,IAAI,CAAC,IAAI,CAAC;;;;;;;;SAQd;KACF,CAAkD,CACtD;CACF,CAAC;AA9CW,QAAA,mCAAmC,uCA8C9C"}

package/lib/orchestrate/common/structures/IAutoBeCommonCorrectDateApplication.d.ts

@@ -1,35 +0,0 @@
-import typia from "typia";
-/** Application interface for Date type correction in generated code */
-export interface IAutoBeCommonCorrectDateApplication {
-    /**
-     * Rewrite the function to fix Date type issues
-     *
-     * @param props - Correction properties
-     */
-    rewrite(props: IAutoBeCommonCorrectDateApplication.IProps): void;
-    /** Reject the correction task if Date issues cannot be fixed */
-    reject(): void;
-}
-export declare namespace IAutoBeCommonCorrectDateApplication {
-    /** Properties for Date type correction */
-    interface IProps {
-        /** The correction revision containing the fixed code */
-        revise: {
-            /** Optional: Analysis of Date type errors found */
-            analysis?: string & typia.tags.MaxLength<4000>;
-            /** Optional: Strategy for fixing Date issues */
-            strategy?: string & typia.tags.MaxLength<2000>;
-            /**
-             * Final corrected code with all Date type issues resolved
-             *
-             * Must follow these rules:
-             *
-             * - No ': Date' type declarations
-             * - All dates use 'string & tags.Format<"date-time">'
-             * - All Date objects wrapped with toISOStringSafe()
-             * - Null checks before toISOStringSafe()
-             */
-            final: string;
-        };
-    }
-}