@autobe/agent 0.8.0 → 0.9.1

package/lib/index.mjs

@@ -10,7 +10,7 @@ import "typia";
 
 import * as __typia_transform__accessExpressionAsString from "typia/lib/internal/_accessExpressionAsString.js";
 
-import { OpenApiTypeChecker, HttpMigration } from "@samchon/openapi";
+import { OpenApiTypeChecker } from "@samchon/openapi";
 
 import { OpenApiV3_1Emender } from "@samchon/openapi/lib/converters/OpenApiV3_1Emender";
 
@@ -140,7 +140,7 @@ class AutoBeAnalyzeAgent {
         const lastMessage = response[response.length - 1];
         if ("text" in lastMessage) {
             this.ctx.dispatch({
-                type: "analyzeWriteDocument",
+                type: "analyzeWrite",
                 files: this.fileMap,
                 created_at: (new Date).toISOString(),
                 step: this.ctx.state().analyze?.step ?? 0
@@ -2054,7 +2054,7 @@ async function orchestrateInterfaceComponents(ctx, operations, capacity = 12) {
         schemas: {}
     };
     for (const y of await Promise.all(matrix.map((async it => {
-        const row = await divideAndConquer$2(ctx, operations, it, 3, (count => {
+        const row = await divideAndConquer$1(ctx, operations, it, 3, (count => {
             progress += count;
         }));
         ctx.dispatch({
@@ -2073,7 +2073,7 @@ async function orchestrateInterfaceComponents(ctx, operations, capacity = 12) {
     return x;
 }
 
-async function divideAndConquer$2(ctx, operations, typeNames, retry, progress) {
+async function divideAndConquer$1(ctx, operations, typeNames, retry, progress) {
     const remained = new Set(typeNames);
     const components = {
         schemas: {}
@@ -2081,7 +2081,7 @@ async function divideAndConquer$2(ctx, operations, typeNames, retry, progress) {
     for (let i = 0; i < retry; ++i) {
         if (remained.size === 0) break;
         const before = remained.size;
-        const newbie = await process$5(ctx, operations, components, remained);
+        const newbie = await process$4(ctx, operations, components, remained);
         for (const key of Object.keys(newbie.schemas)) {
             components.schemas[key] = newbie.schemas[key];
             remained.delete(key);
@@ -2091,7 +2091,7 @@ async function divideAndConquer$2(ctx, operations, typeNames, retry, progress) {
     return components;
 }
 
-async function process$5(ctx, operations, oldbie, remained) {
+async function process$4(ctx, operations, oldbie, remained) {
     const pointer = {
         value: null
     };
@@ -2959,7 +2959,7 @@ async function orchestrateInterfaceOperations(ctx, endpoints, capacity = 12) {
     });
     let completed = 0;
     const operations = await Promise.all(matrix.map((async it => {
-        const row = await divideAndConquer$1(ctx, it, 3, (count => {
+        const row = await divideAndConquer(ctx, it, 3, (count => {
             completed += count;
         }));
         ctx.dispatch({
@@ -2975,13 +2975,13 @@ async function orchestrateInterfaceOperations(ctx, endpoints, capacity = 12) {
     return operations.flat();
 }
 
-async function divideAndConquer$1(ctx, endpoints, retry, progress) {
+async function divideAndConquer(ctx, endpoints, retry, progress) {
     const remained = new HashSet(endpoints, OpenApiEndpointComparator.hashCode, OpenApiEndpointComparator.equals);
     const operations = new HashMap(OpenApiEndpointComparator.hashCode, OpenApiEndpointComparator.equals);
     for (let i = 0; i < retry; ++i) {
         if (remained.empty() === true || operations.size() >= endpoints.length) break;
         const before = operations.size();
-        const newbie = await process$4(ctx, Array.from(remained));
+        const newbie = await process$3(ctx, Array.from(remained));
         for (const item of newbie) {
             operations.set(item, item);
             remained.erase(item);
@@ -2991,7 +2991,7 @@ async function divideAndConquer$1(ctx, endpoints, retry, progress) {
     return operations.toJSON().map((it => it.second));
 }
 
-async function process$4(ctx, endpoints) {
+async function process$3(ctx, endpoints) {
     const pointer = {
         value: null
     };
@@ -4854,7 +4854,7 @@ const orchestrateInterface = ctx => async props => {
         type: "interface",
         id: v4(),
         document,
-        files: await ctx.compiler.interface(document),
+        files: await ctx.compiler.interface.compile(document),
         reason: props.reason,
         step: ctx.state().analyze?.step ?? 0,
         created_at: start.toISOString(),
@@ -5368,7 +5368,7 @@ function orchestratePrismaCorrect(ctx, application, life = 4) {
 async function step$1(ctx, application, life) {
     const result = await ctx.compiler.prisma.validate(application);
     if (result.success) return result; else if (life <= 0) return result;
-    const schemas = await ctx.compiler.prisma.write(application);
+    const schemas = await ctx.compiler.prisma.write(application, "postgres");
     ctx.dispatch({
         type: "prismaValidate",
         result,
@@ -7084,7 +7084,7 @@ async function orchestratePrismaSchemas(ctx, components) {
     const total = components.reduce(((acc, c) => acc + c.tables.length), 0);
     let i = 0;
     return await Promise.all(components.map((async c => {
-        const result = await process$3(ctx, {
+        const result = await process$2(ctx, {
             filename: c.filename,
             tables: c.tables,
             entireTables
@@ -7102,7 +7102,7 @@ async function orchestratePrismaSchemas(ctx, components) {
     })));
 }
 
-async function process$3(ctx, component) {
+async function process$2(ctx, component) {
     const pointer = {
         value: null
     };
@@ -8886,7 +8886,7 @@ const orchestratePrisma = ctx => async props => {
     const result = await orchestratePrismaCorrect(ctx, {
         files: events.map((e => e.file))
     });
-    const schemas = await ctx.compiler.prisma.write(result.data);
+    const schemas = await ctx.compiler.prisma.write(result.data, "postgres");
     const history = {
         type: "prisma",
         id: v4(),
@@ -8914,47 +8914,146 @@ const orchestratePrisma = ctx => async props => {
     return history;
 };
 
-const transformTestCorrectHistories = (apiFiles, dtoFiles) => [ {
+async function randomBackoffRetry(fn, options = {}) {
+    const {maxRetries = 5, baseDelay = 4e3, maxDelay = 6e4, jitter = .8, handleError = isRetryError} = options;
+    let lastError;
+    for (let attempt = 0; attempt < maxRetries; attempt++) {
+        try {
+            return await fn();
+        } catch (err) {
+            lastError = err;
+            if (attempt === maxRetries - 1) throw err;
+            if (!handleError(err)) throw err;
+            const tempDelay = Math.min(baseDelay * 2 ** attempt, maxDelay);
+            const delay = tempDelay * (1 + Math.random() * jitter);
+            await new Promise((res => setTimeout(res, delay)));
+        }
+    }
+    throw lastError;
+}
+
+function isRetryError(error) {
+    if (error?.code === "insufficient_quota" || error?.error?.type === "insufficient_quota") {
+        return false;
+    }
+    if (typeof error?.status === "number" && error.status >= 500 || error?.error?.type === "server_error") {
+        return true;
+    }
+    if (error?.status === 429) {
+        return true;
+    }
+    const code = error?.code || error?.cause?.code;
+    if ([ "UND_ERR_SOCKET", "UND_ERR_CONNECT_TIMEOUT", "ETIMEDOUT", "ECONNRESET", "EPIPE" ].includes(code)) {
+        return true;
+    }
+    if (error?.message === "terminated" || error?.name === "AbortError") {
+        return true;
+    }
+    return false;
+}
+
+async function compileTestScenario(ctx, scenario) {
+    const document = filterDocument(scenario, ctx.state().interface.document);
+    const entries = Object.entries(await ctx.compiler.interface.compile(document));
+    const filter = prefix => Object.fromEntries(entries.filter((([key]) => key.startsWith(prefix))));
+    return {
+        sdk: filter("src/api/functional"),
+        dto: filter("src/api/structures"),
+        e2e: filter("test/features")
+    };
+}
+
+function filterDocument(scenario, document) {
+    const operations = document.operations.filter((op => scenario.endpoint.method === op.method && scenario.endpoint.path === op.path || scenario.dependencies.some((dp => dp.endpoint.method === op.method && dp.endpoint.path === op.path))));
+    const components = {
+        schemas: {}
+    };
+    const visit = typeName => {
+        OpenApiTypeChecker.visit({
+            components: document.components,
+            schema: {
+                $ref: `#/components/schemas/${typeName}`
+            },
+            closure: s => {
+                if (OpenApiTypeChecker.isReference(s)) {
+                    const key = s.$ref.split("/").pop();
+                    components.schemas[key] = document.components.schemas[key];
+                }
+            }
+        });
+    };
+    for (const op of operations) {
+        if (op.requestBody) visit(op.requestBody.typeName);
+        if (op.responseBody) visit(op.responseBody.typeName);
+    }
+    return {
+        operations,
+        components
+    };
+}
+
+function filterTestFileName(key) {
+    if (key.endsWith(".ts") === false) return false; else if (key.startsWith("src/") === true) return true;
+    return key.startsWith("test/") === true && key.startsWith("test/features/") === false && key.startsWith("test/benchmark/") === false;
+}
+
+const transformTestCorrectHistories = artifacts => [ {
     id: v4(),
     created_at: (new Date).toISOString(),
     type: "systemMessage",
-    text: '# Compiler Error Fix System Prompt\n\nYou are an expert TypeScript compiler error fixing agent specializing in resolving compilation errors in E2E test code that follows the `@nestia/e2e` testing framework conventions.\n\n## Your Role\n\n- Analyze the provided TypeScript code with compilation errors and generate the corrected version.  \n- Focus specifically on the error location, message, and problematic code segment.  \n- Maintain all existing functionality while resolving only the compilation issues.  \n- Follow the established code patterns and conventions from the original E2E test code.  \n- Use provided API Files and DTO Files to resolve module and type declaration issues.  \n- **CRITICAL**: Apply comprehensive fixes to prevent circular error loops by addressing all related import issues in a single pass.\n\n## Default Working Language: English\n\n- Use the language specified by user in messages as the working language when explicitly provided  \n- All thinking and responses must be in the working language  \n- All model/field names must be in English regardless of working language \n\n## Input Format\n\nYou will receive:  \n\n1. **Original Code**: TypeScript E2E test code with compilation errors  \n2. **Error Information**:  \n   - Exact character position of the error  \n   - Detailed error message from TypeScript compiler  \n   - The specific problematic code segment  \n3. **Instructions**: Specific guidance on what needs to be fixed  \n4. **API Files**: Reference files containing available API functions and their paths  \n5. **DTO Files**: Reference files containing available types and their import paths  \n\n## Code Fixing Guidelines\n\n### 1. Module Resolution Errors (CRITICAL PRIORITY)\n\n#### Universal Module Import Pattern Recognition and Fix:\n\n**ALWAYS scan the ENTIRE code for ALL import statements that match these patterns and fix them ALL at once:**\n\n```typescript\n// WRONG PATTERNS - Fix ALL of these in one pass:\nimport api from "@nestia/PROJECT-api";\nimport api from "@wrtnlabs/PROJECT-api"; \nimport api from "@anyorganization/PROJECT-api";\nimport { Type } from "@nestia/PROJECT-api/lib/structures/Type";\nimport { Type } from "@wrtnlabs/PROJECT-api/lib/structures/Type";\nimport { Type } from "@anyorganization/PROJECT-api/lib/structures/Type";\n\n// CORRECT PATTERN - Replace with:\nimport api from "@ORGANIZATION/PROJECT-api";\nimport { Type } from "@ORGANIZATION/PROJECT-api/lib/structures/Type";\n```\n\n#### Comprehensive Module Fix Strategy:\n\n1. **Pattern Detection**: Look for ANY import that contains:  \n   - `@[anything]/[project-name]-api` → Replace `@[anything]` with `@ORGANIZATION`  \n   - `@[project-name]-api` (missing org prefix) → Add `@ORGANIZATION/` prefix  \n\n2. **Common Error Patterns to Fix ALL AT ONCE**:  \n\n```typescript\n// Error Pattern 1: Wrong organization name\nCannot find module \'@wrtnlabs/template-api\'\nCannot find module \'@nestia/template-api\'\nCannot find module \'@anyorg/template-api\'\n// Fix: Replace with @ORGANIZATION/template-api\n\n// Error Pattern 2: Missing organization prefix  \nCannot find module \'@template-api\'\nCannot find module \'template-api\'\n// Fix: Add @ORGANIZATION/ prefix\n\n// Error Pattern 3: Structure imports with wrong org\nCannot find module \'@wrtnlabs/template-api/lib/structures/IType\'\nCannot find module \'@nestia/template-api/lib/structures/IType\'\n// Fix: Replace with @ORGANIZATION/template-api/lib/structures/IType\n```  \n\n3. **Comprehensive Import Scan and Fix**:  \n   - **BEFORE fixing the reported error**, scan ALL import statements in the code  \n   - Identify ALL imports that follow incorrect patterns  \n   - Fix ALL of them simultaneously to prevent error loops  \n   - Ensure consistent `@ORGANIZATION/PROJECT-api` pattern throughout  \n\n#### Module Resolution Fix Examples:\n\n```typescript\n// BEFORE (Multiple wrong patterns in same file):\nimport api from "@nestia/template-api";\nimport { IBbsArticle } from "@wrtnlabs/template-api/lib/structures/IBbsArticle";\nimport { IAttachmentFile } from "@template-api/lib/structures/IAttachmentFile";\n\n// AFTER (All fixed consistently):\nimport api from "@ORGANIZATION/template-api";\nimport { IBbsArticle } from "@ORGANIZATION/template-api/lib/structures/IBbsArticle";\nimport { IAttachmentFile } from "@ORGANIZATION/template-api/lib/structures/IAttachmentFile";\n```  \n\n### 2. Error Loop Prevention Strategy\n\n**CRITICAL**: To prevent 1 → 2 → 3 → 1 error loops:  \n\n1. **Holistic Code Analysis**: Before fixing the specific error, analyze ALL import statements in the entire code  \n2. **Batch Import Fixes**: Fix ALL import-related issues in a single pass, not just the reported error  \n3. **Pattern Consistency**: Ensure ALL imports follow the same `@ORGANIZATION/PROJECT-api` pattern  \n4. **Preemptive Fixes**: Look for and fix potential related errors that might surface after the current fix  \n\n**Implementation Approach**:  \n\n```typescript\n// Step 1: Scan entire code for ALL these patterns\nconst problemPatterns = [\n  /@[^/]+\\/[^-]+-api(?!\\/)/g,           // Wrong org prefix\n  /@[^-]+-api(?!\\/)/g,                  // Missing org prefix  \n  /from\\s+["\']@[^/]+\\/[^-]+-api/g,      // Wrong org in imports\n  /from\\s+["\']@[^-]+-api/g              // Missing org in imports\n];\n\n// Step 2: Replace ALL matches with @ORGANIZATION/PROJECT-api pattern\n// Step 3: Then fix the specific reported error\n```  \n\n### 3. API Function Usage Corrections\n\n- Ensure proper `import api from "@ORGANIZATION/PROJECT-api";` format (verify against API Files)  \n- Fix API function call patterns to follow:  \n\n  ```ts\n  api.functional.[...].methodName(...)\n  ```  \n\n- Correct connection parameter usage (avoid adding extra properties):  \n\n  ```ts\n  // Correct\n  await api.functional.bbs.articles.post(connection, { body: articleBody });\n  ```  \n\n- **Cross-reference API Files** to ensure function paths and method names are accurate  \n\n### 4. DTO Type Import Corrections\n\n- Fix import statements to use proper format based on **DTO Files**:  \n\n  ```ts\n  import { ITypeName } from "@ORGANIZATION/PROJECT-api/lib/structures/[...].ts";\n  ```  \n\n- Ensure `@ORGANIZATION` prefix is maintained in import paths  \n- **Verify type names and paths** against provided DTO Files  \n- Correct missing or incorrect type imports  \n- Fix type annotation errors  \n\n### 5. Test Function Structure Fixes\n\n- Ensure test functions follow the pattern:  \n\n  ```ts\n  export async function test_api_xxx(...): Promise<void> { ... }\n  ```  \n\n- Fix async/await usage errors  \n- Correct function parameter types (especially `connection: api.IConnection`)  \n\n### 6. Test Validator Usage Corrections\n\n- Fix `TestValidator` method calls:  \n\n  ```ts\n  TestValidator.equals("title", exceptionFunction)(expected)(actual);\n  TestValidator.predicate("title")(condition);\n  TestValidator.error("title")(task);\n  ```  \n\n- Correct currying function usage  \n- Fix assertion patterns  \n\n### 7. Typia Assert Corrections\n\n- Ensure proper `typia.assert<T>(value)` usage  \n- Fix generic type parameters  \n- Correct assertion patterns for response validation  \n\n### 8. Array Type Corrections\n\n```\nerror: Argument of type \'IBbsArticleComment[]\' is not assignable to parameter of type \'never[]\'.\n```  \n\n- To Resolve above Array parameter Error, If you declare empty array like `[]`, You must define the type of array together.  \n\nExample:  \n\n  ```typescript\n  TestValidator.equals("message")(\n      [] as IBbsArticleComment[],\n    )(data);\n  ```  \n\n### 9. Common TypeScript Error Fixes\n\n- **Import/Export errors**: Fix module resolution issues using API Files and DTO Files as reference  \n- **Type mismatches**: Align variable types with expected interfaces from DTO Files  \n- **Missing properties**: Add required properties to objects  \n- **Async/Promise errors**: Fix Promise handling and async function signatures  \n- **Generic type errors**: Correct generic type parameters  \n- **Null/undefined handling**: Add proper null checks or optional chaining  \n- **Interface compliance**: Ensure objects conform to their declared interfaces  \n\n## Error Resolution Strategy\n\n1. **Full Code Analysis**: FIRST perform comprehensive analysis of ENTIRE codebase for ALL potential TypeScript issues  \n2. **Error Chain Identification**: Identify cascading error patterns and relationships between different parts of code  \n3. **Holistic Fix Planning**: Plan fixes for ALL related errors that could cause loops, not just the reported error  \n4. **Reference File Consultation**:  \n   - For module errors: Consult API Files for correct import paths  \n   - For type errors: Consult DTO Files for correct type import paths  \n   - For function calls: Verify method signatures and parameters  \n5. **Batch Error Resolution**: Fix ALL identified issues simultaneously in logical groups:  \n   - All import/module issues together  \n   - All type declaration issues together  \n   - All function signature issues together  \n   - All usage/call site issues together  \n6. **Context Preservation**: Maintain the original test logic and flow  \n7. **Comprehensive Validation**: Ensure no new compilation errors or cascading issues are introduced  \n8. **Pattern Consistency**: Keep existing code style and conventions throughout all fixes  \n\n## Output Requirements\n\n- Return **only** the corrected TypeScript code  \n- Maintain all original functionality and test logic  \n- Preserve code formatting and style  \n- Ensure the fix addresses ALL related compilation errors (not just the reported one)  \n- **CRITICAL**: Fix ALL import pattern issues in a single pass to prevent error loops  \n- Do not add explanations, comments, or additional features  \n\n## Priority Error Handling\n\n1. **Comprehensive Analysis** (HIGHEST priority):  \n   - Scan ENTIRE codebase for ALL potential TypeScript compilation issues  \n   - Identify cascading error patterns and relationships  \n   - Map error chains that commonly cause loops (import → type → usage → validation)  \n\n2. **Batch Error Resolution** (CRITICAL):  \n   - Group related errors into logical fix batches:  \n     - **Module/Import Batch**: All import paths, module resolution, missing dependencies  \n     - **Type Batch**: All type declarations, interfaces, generic constraints  \n     - **Function Batch**: All function signatures, parameters, return types  \n     - **Usage Batch**: All variable assignments, method calls, property access  \n     - **Test Batch**: All TestValidator calls, assertion patterns, validation logic  \n   - Fix entire batches simultaneously to prevent cascading failures  \n\n3. **Specific Error Resolution**:  \n   - After comprehensive fixes, verify the originally reported error is resolved  \n   - Use DTO Files for type corrections and API Files for function signatures  \n   - Ensure consistency with established patterns  \n\n4. **General TypeScript Compilation**:  \n   - Apply standard TypeScript error resolution techniques  \n   - Maintain type safety throughout all fixes  \n\n## Error Loop Prevention Protocol\n\n**MANDATORY STEPS to prevent error loops:**  \n\n1. **Pre-Analysis**: Before fixing reported error, scan entire code for ALL import statements  \n2. **Pattern Matching**: Identify ALL imports matching problematic patterns:  \n   - `@[anything-except-ORGANIZATION]/[project]-api`  \n   - Missing `@ORGANIZATION/` prefix  \n   - Inconsistent organization naming  \n3. **Comprehensive Fix**: Replace ALL problematic imports with correct `@ORGANIZATION/PROJECT-api` pattern  \n4. **Validation**: Ensure ALL imports in the file follow consistent pattern  \n5. **Specific Fix**: Then address the specific reported compilation error  \n\n**Example of Comprehensive Fix Approach:**  \n\n```typescript\n// Input code with multiple potential issues:\nimport api from "@nestia/template-api";                    // Issue 1\nimport { IBbsArticle } from "@wrtnlabs/template-api/lib/structures/IBbsArticle";  // Issue 2  \nimport { IUser } from "@template-api/lib/structures/IUser";  // Issue 3\n\n// Output: ALL issues fixed simultaneously:\nimport api from "@ORGANIZATION/template-api";\nimport { IBbsArticle } from "@ORGANIZATION/template-api/lib/structures/IBbsArticle";\nimport { IUser } from "@ORGANIZATION/template-api/lib/structures/IUser";\n```'
+    text: '# Compiler Error Fix System Prompt\n\nYou are an expert TypeScript compiler error fixing agent specializing in resolving compilation errors in E2E test code that follows the `@nestia/e2e` testing framework conventions.\n\n## Your Role\n\n- Analyze the provided TypeScript code with compilation errors and generate the corrected version.  \n- Focus specifically on the error location, message, and problematic code segment.  \n- Maintain all existing functionality while resolving only the compilation issues.  \n- Follow the established code patterns and conventions from the original E2E test code.  \n- Use provided API Files and DTO Files to resolve module and type declaration issues.  \n- **CRITICAL**: Apply comprehensive fixes to prevent circular error loops by addressing all related import issues in a single pass.\n\n## Default Working Language: English\n\n- Use the language specified by user in messages as the working language when explicitly provided  \n- All thinking and responses must be in the working language  \n- All model/field names must be in English regardless of working language \n\n## Input Format\n\nYou will receive:  \n\n1. **Original Code**: TypeScript E2E test code with compilation errors  \n2. **Error Information**:  \n   - Exact character position of the error  \n   - Detailed error message from TypeScript compiler  \n   - The specific problematic code segment  \n3. **Instructions**: Specific guidance on what needs to be fixed  \n4. **API Files**: Reference files containing available API functions and their paths  \n5. **DTO Files**: Reference files containing available types and their import paths  \n\n## Code Fixing Guidelines\n\n### 1. Module Resolution Errors (CRITICAL PRIORITY)\n\n#### Universal Module Import Pattern Recognition and Fix:\n\n**ALWAYS scan the ENTIRE code for ALL import statements that match these patterns and fix them ALL at once:**\n\n```typescript\n// WRONG PATTERNS - Fix ALL of these in one pass:\nimport api from "@nestia/PROJECT-api";\nimport api from "@wrtnlabs/PROJECT-api"; \nimport api from "@anyorganization/PROJECT-api";\nimport { Type } from "@nestia/PROJECT-api/lib/structures/Type";\nimport { Type } from "@wrtnlabs/PROJECT-api/lib/structures/Type";\nimport { Type } from "@anyorganization/PROJECT-api/lib/structures/Type";\n\n// CORRECT PATTERN - Replace with:\nimport api from "@ORGANIZATION/PROJECT-api";\nimport { Type } from "@ORGANIZATION/PROJECT-api/lib/structures/Type";\n```\n\n#### Importing namespace rule\n\n```ts\n// ❌ Incorrect usage: importing inner types directly from a namespaced type\nimport {\n  IShoppingSaleInquiryComment,\n  IShoppingSaleInquiryComment_ICreate,\n  IShoppingSaleInquiryComment_IRequest,\n} from "@ORGANIZATION/PROJECT-api/lib/structures/IShoppingSaleInquiryComment";\n\n```\n\n```ts\n// ✅ Correct usage: import only the namespace and access inner types via dot notation\nimport {\n  IShoppingSaleInquiryComment,\n} from "@ORGANIZATION/PROJECT-api/lib/structures/IShoppingSaleInquiryComment";\n\ntype A = IShoppingSaleInquiryComment.ICreate // correct!\ntype B = IShoppingSaleInquiryComment.IRequest // correct!\n```\n\n- 💡 Rule: When working with types defined inside a namespace, import only the namespace and access inner types using dot notation (e.g., Namespace.InnerType).\nAvoid importing inner types directly, as it breaks encapsulation and may cause naming conflicts or improper typings.\n\n\n#### Comprehensive Module Fix Strategy:\n\n1. **Pattern Detection**: Look for ANY import that contains:  \n   - `@[anything]/[project-name]-api` → Replace `@[anything]` with `@ORGANIZATION`  \n   - `@[project-name]-api` (missing org prefix) → Add `@ORGANIZATION/` prefix  \n\n2. **Common Error Patterns to Fix ALL AT ONCE**:  \n\n```typescript\n// Error Pattern 1: Wrong organization name\nCannot find module \'@wrtnlabs/PROJECT-api\'\nCannot find module \'@nestia/PROJECT-api\'\nCannot find module \'@anyorg/PROJECT-api\'\n// Fix: Replace with @ORGANIZATION/PROJECT-api\n\n// Error Pattern 2: Missing organization prefix  \nCannot find module \'@PROJECT-api\'\nCannot find module \'PROJECT-api\'\n// Fix: Add @ORGANIZATION/ prefix\n\n// Error Pattern 3: Structure imports with wrong org\nCannot find module \'@wrtnlabs/PROJECT-api/lib/structures/IType\'\nCannot find module \'@nestia/PROJECT-api/lib/structures/IType\'\n// Fix: Replace with @ORGANIZATION/PROJECT-api/lib/structures/IType\n```  \n\n3. **Comprehensive Import Scan and Fix**:  \n   - **BEFORE fixing the reported error**, scan ALL import statements in the code  \n   - Identify ALL imports that follow incorrect patterns  \n   - Fix ALL of them simultaneously to prevent error loops  \n   - Ensure consistent `@ORGANIZATION/PROJECT-api` pattern throughout  \n\n#### Module Resolution Fix Examples:\n\n```typescript\n// BEFORE (Multiple wrong patterns in same file):\nimport api from "@nestia/PROJECT-api";\nimport { IBbsArticle } from "@wrtnlabs/PROJECT-api/lib/structures/IBbsArticle";\nimport { IAttachmentFile } from "@PROJECT-api/lib/structures/IAttachmentFile";\n\n// AFTER (All fixed consistently):\nimport api from "@ORGANIZATION/PROJECT-api";\nimport { IBbsArticle } from "@ORGANIZATION/PROJECT-api/lib/structures/IBbsArticle";\nimport { IAttachmentFile } from "@ORGANIZATION/PROJECT-api/lib/structures/IAttachmentFile";\n```  \n\n### 2. Error Loop Prevention Strategy\n\n**CRITICAL**: To prevent 1 → 2 → 3 → 1 error loops:  \n\n1. **Holistic Code Analysis**: Before fixing the specific error, analyze ALL import statements in the entire code  \n2. **Batch Import Fixes**: Fix ALL import-related issues in a single pass, not just the reported error  \n3. **Pattern Consistency**: Ensure ALL imports follow the same `@ORGANIZATION/PROJECT-api` pattern  \n4. **Preemptive Fixes**: Look for and fix potential related errors that might surface after the current fix  \n\n**Implementation Approach**:  \n\n```typescript\n// Step 1: Scan entire code for ALL these patterns\nconst problemPatterns = [\n  /@[^/]+\\/[^-]+-api(?!\\/)/g,           // Wrong org prefix\n  /@[^-]+-api(?!\\/)/g,                  // Missing org prefix  \n  /from\\s+["\']@[^/]+\\/[^-]+-api/g,      // Wrong org in imports\n  /from\\s+["\']@[^-]+-api/g              // Missing org in imports\n];\n\n// Step 2: Replace ALL matches with @ORGANIZATION/PROJECT-api pattern\n// Step 3: Then fix the specific reported error\n```  \n\n### 3. API Function Usage Corrections\n\n- Ensure proper `import api from "@ORGANIZATION/PROJECT-api";` format (verify against API Files)  \n- Fix API function call patterns to follow:  \n\n  ```ts\n  api.functional.[...].methodName(...)\n  ```  \n\n- Correct connection parameter usage (avoid adding extra properties):  \n\n  ```ts\n  // Correct\n  await api.functional.bbs.articles.post(connection, { body: articleBody });\n  ```  \n\n- **Cross-reference API Files** to ensure function paths and method names are accurate  \n\n### 4. DTO Type Import Corrections\n\n- Fix import statements to use proper format based on **DTO Files**:  \n\n  ```ts\n  import { ITypeName } from "@ORGANIZATION/PROJECT-api/lib/structures/[...].ts";\n  ```  \n\n- Ensure `@ORGANIZATION` prefix is maintained in import paths  \n- **Verify type names and paths** against provided DTO Files  \n- Correct missing or incorrect type imports  \n- Fix type annotation errors  \n\n### 5. Test Function Structure Fixes\n\n- Ensure test functions follow the pattern:  \n\n  ```ts\n  export async function test_api_xxx(...): Promise<void> { ... }\n  ```  \n\n- Fix async/await usage errors  \n- Correct function parameter types (especially `connection: api.IConnection`)  \n\n### 6. Test Validator Usage Corrections\n\n- Fix `TestValidator` method calls:  \n\n  ```ts\n  TestValidator.equals("title", exceptionFunction)(expected)(actual);\n  TestValidator.predicate("title")(condition);\n  TestValidator.error("title")(task);\n  ```  \n\n- Correct currying function usage  \n- Fix assertion patterns  \n\n### 7. Typia Assert Corrections\n\n- Ensure proper `typia.assert<T>(value)` usage  \n- Fix generic type parameters  \n- Correct assertion patterns for response validation  \n\n### 8. Array Type Corrections\n\n```\nerror: Argument of type \'IBbsArticleComment[]\' is not assignable to parameter of type \'never[]\'.\n```  \n\n- To Resolve above Array parameter Error, If you declare empty array like `[]`, You must define the type of array together.  \n\nExample:  \n\n  ```typescript\n  TestValidator.equals("message")(\n      [] as IBbsArticleComment[],\n    )(data);\n  ```  \n\n### 9. Common TypeScript Error Fixes\n\n- **Import/Export errors**: Fix module resolution issues using API Files and DTO Files as reference  \n- **Type mismatches**: Align variable types with expected interfaces from DTO Files  \n- **Missing properties**: Add required properties to objects  \n- **Async/Promise errors**: Fix Promise handling and async function signatures  \n- **Generic type errors**: Correct generic type parameters  \n- **Null/undefined handling**: Add proper null checks or optional chaining  \n- **Interface compliance**: Ensure objects conform to their declared interfaces  \n\n## Error Resolution Strategy\n\n1. **Full Code Analysis**: FIRST perform comprehensive analysis of ENTIRE codebase for ALL potential TypeScript issues  \n2. **Error Chain Identification**: Identify cascading error patterns and relationships between different parts of code  \n3. **Holistic Fix Planning**: Plan fixes for ALL related errors that could cause loops, not just the reported error  \n4. **Reference File Consultation**:  \n   - For module errors: Consult API Files for correct import paths  \n   - For type errors: Consult DTO Files for correct type import paths  \n   - For function calls: Verify method signatures and parameters  \n5. **Batch Error Resolution**: Fix ALL identified issues simultaneously in logical groups:  \n   - All import/module issues together  \n   - All type declaration issues together  \n   - All function signature issues together  \n   - All usage/call site issues together  \n6. **Context Preservation**: Maintain the original test logic and flow  \n7. **Comprehensive Validation**: Ensure no new compilation errors or cascading issues are introduced  \n8. **Pattern Consistency**: Keep existing code style and conventions throughout all fixes  \n\n## Output Requirements\n\n- Return **only** the corrected TypeScript code  \n- Maintain all original functionality and test logic  \n- Preserve code formatting and style  \n- Ensure the fix addresses ALL related compilation errors (not just the reported one)  \n- **CRITICAL**: Fix ALL import pattern issues in a single pass to prevent error loops  \n- Do not add explanations, comments, or additional features  \n\n## Priority Error Handling\n\n1. **Comprehensive Analysis** (HIGHEST priority):  \n   - Scan ENTIRE codebase for ALL potential TypeScript compilation issues  \n   - Identify cascading error patterns and relationships  \n   - Map error chains that commonly cause loops (import → type → usage → validation)  \n\n2. **Batch Error Resolution** (CRITICAL):  \n   - Group related errors into logical fix batches:  \n     - **Module/Import Batch**: All import paths, module resolution, missing dependencies  \n     - **Type Batch**: All type declarations, interfaces, generic constraints  \n     - **Function Batch**: All function signatures, parameters, return types  \n     - **Usage Batch**: All variable assignments, method calls, property access  \n     - **Test Batch**: All TestValidator calls, assertion patterns, validation logic  \n   - Fix entire batches simultaneously to prevent cascading failures  \n\n3. **Specific Error Resolution**:  \n   - After comprehensive fixes, verify the originally reported error is resolved  \n   - Use DTO Files for type corrections and API Files for function signatures  \n   - Ensure consistency with established patterns  \n\n4. **General TypeScript Compilation**:  \n   - Apply standard TypeScript error resolution techniques  \n   - Maintain type safety throughout all fixes  \n\n## Error Loop Prevention Protocol\n\n**MANDATORY STEPS to prevent error loops:**  \n\n1. **Pre-Analysis**: Before fixing reported error, scan entire code for ALL import statements  \n2. **Pattern Matching**: Identify ALL imports matching problematic patterns:  \n   - `@[anything-except-ORGANIZATION]/[project]-api`  \n   - Missing `@ORGANIZATION/` prefix  \n   - Inconsistent organization naming  \n3. **Comprehensive Fix**: Replace ALL problematic imports with correct `@ORGANIZATION/PROJECT-api` pattern  \n4. **Validation**: Ensure ALL imports in the file follow consistent pattern  \n5. **Specific Fix**: Then address the specific reported compilation error  \n\n**Example of Comprehensive Fix Approach:**  \n\n```typescript\n// Input code with multiple potential issues:\nimport api from "@nestia/PROJECT-api";                    // Issue 1\nimport { IBbsArticle } from "@wrtnlabs/PROJECT-api/lib/structures/IBbsArticle";  // Issue 2  \nimport { IUser } from "@PROJECT-api/lib/structures/IUser";  // Issue 3\n\n// Output: ALL issues fixed simultaneously:\nimport api from "@ORGANIZATION/PROJECT-api";\nimport { IBbsArticle } from "@ORGANIZATION/PROJECT-api/lib/structures/IBbsArticle";\nimport { IUser } from "@ORGANIZATION/PROJECT-api/lib/structures/IUser";\n```'
 }, {
     id: v4(),
     created_at: (new Date).toISOString(),
     type: "assistantMessage",
-    text: [ "You are the world's best TypeScript compiler error fixer.", "You will be given a **TypeScript code** with compilation errors, and your job is to fix the errors.", "", "## Rules", "- Follow the base E2E test style strictly. Never use other frameworks like Jest or Mocha.", "- Use `TestValidator.equals(...)` and `typia.assert(...)` to verify results.", "- Use `api.functional.XXX` for all API calls. These are defined in API Files.", "- Use helper functions like `generate_random_xxx(...)` **only if** they already exist in the base test imports.", "- Do not invent new helpers or use utilities that are not explicitly shown.", "- Keep all tests deterministic and reliable.", "", "## File References", "### API Files", "```typescript", JSON.stringify(apiFiles, null, 2), "```", "", "### DTO Files", "```typescript", JSON.stringify(dtoFiles, null, 2), "```", "", "Now Fix the E2E test function based on the given error information.", "Only output a single `async function` named `test_api_{...}`. No explanation, no commentary." ].join("\n")
+    text: [ "You are the world's best TypeScript compiler error fixer.", "You will be given a **TypeScript code** with compilation errors, and your job is to fix the errors.", "", "## Rules", "- Follow the base E2E test style strictly. Never use other frameworks like Jest or Mocha.", "- Use `TestValidator.equals(...)` and `typia.assert(...)` to verify results.", "- Use `api.functional.XXX` for all API calls. These are defined in API Files.", "- Use helper functions like `generate_random_xxx(...)` **only if** they already exist in the base test imports.", "- Do not invent new helpers or use utilities that are not explicitly shown.", "- Keep all tests deterministic and reliable.", "", "## File References", "### API Files", "```typescript", JSON.stringify(artifacts.sdk), "```", "", "### DTO Files", "```typescript", JSON.stringify(artifacts.dto), "```", "", "Now Fix the E2E test function based on the given error information.", "Only output a single `async function` named `test_api_{...}`. No explanation, no commentary." ].join("\n")
 } ];
 
-async function orchestrateTestCorrect(ctx, codes, life = 4) {
-    const testFiles = Object.fromEntries(codes.map((({filename, content}) => [ `test/features/api/${filename}`, content ])));
-    const retainedFiles = Object.fromEntries(Object.entries(ctx.state().interface?.files ?? {}).filter((([filename]) => !filename.startsWith("test/features/api"))));
+async function orchestrateTestCorrect(ctx, codes, scenarios, life = 4) {
+    const files = codes.map((({filename, content}, index) => {
+        const scenario = scenarios[index];
+        return {
+            location: filename,
+            content,
+            scenario
+        };
+    }));
+    const testFiles = Object.fromEntries(codes.map((c => [ c.filename, c.content ])));
+    const retainedFiles = Object.fromEntries(Object.entries(ctx.state().interface?.files ?? {}).filter((([key]) => filterTestFileName(key))));
+    const external = async location => {
+        const content = await ctx.compiler.typescript.getExternal(location);
+        if (content === undefined) throw new Error(`File not found: ${location}`);
+        return {
+            [location]: content
+        };
+    };
     const mergedFiles = {
         ...retainedFiles,
-        ...testFiles
+        ...testFiles,
+        ...await external("node_modules/@nestia/e2e/lib/TestValidator.d.ts"),
+        ...await external("node_modules/@nestia/fetcher/lib/IConnection.d.ts")
     };
-    const files = Object.fromEntries(Object.entries(mergedFiles).filter((([filename]) => filename.endsWith(".ts") && !filename.startsWith("test/benchmark/") || filename.endsWith(".json"))));
-    const response = await step(ctx, files, life);
+    const response = await step(ctx, mergedFiles, files, life);
     const event = {
         ...response,
         type: "testValidate",
-        files: {
-            ...mergedFiles,
-            ...response.files
-        }
+        files: [ ...Object.entries(mergedFiles).map((([filename, content]) => ({
+            location: filename,
+            content
+        }))), ...response.files ]
     };
     return event;
 }
 
-async function step(ctx, files, life) {
-    const result = await ctx.compiler.typescript({
-        files
+async function step(ctx, entireFiles, testFiles, life) {
+    const result = await ctx.compiler.typescript.compile({
+        files: entireFiles
     });
     if (result.type === "success") {
         return {
             type: "testValidate",
             created_at: (new Date).toISOString(),
-            files,
+            files: testFiles,
             result,
             step: ctx.state().interface?.step ?? 0
         };
@@ -8963,7 +9062,7 @@ async function step(ctx, files, life) {
         ctx.dispatch({
             type: "testValidate",
             created_at: (new Date).toISOString(),
-            files,
+            files: testFiles,
             result,
             step: ctx.state().interface?.step ?? 0
         });
@@ -8979,7 +9078,7 @@ async function step(ctx, files, life) {
         return {
             type: "testValidate",
             created_at: (new Date).toISOString(),
-            files,
+            files: testFiles,
             result: {
                 ...result,
                 type: "success"
@@ -8990,25 +9089,27 @@ async function step(ctx, files, life) {
     ctx.dispatch({
         type: "testValidate",
         created_at: (new Date).toISOString(),
-        files,
+        files: testFiles,
         result,
         step: ctx.state().interface?.step ?? 0
     });
     if (life <= 0) return {
         type: "testValidate",
         created_at: (new Date).toISOString(),
-        files,
+        files: testFiles,
         result,
         step: ctx.state().interface?.step ?? 0
     };
-    const validate = await Promise.all(Object.entries(diagnostics).map((async ([filename, d]) => {
-        const code = files[filename];
-        const response = await process$2(ctx, d, code);
+    const validatedFiles = await Promise.all(Object.entries(diagnostics).map((async ([filename, d]) => {
+        const file = testFiles.find((f => f.location === filename));
+        const code = file?.content;
+        const scenario = file?.scenario;
+        const response = await process$1(ctx, d, code, scenario);
         ctx.dispatch({
             type: "testCorrect",
             created_at: (new Date).toISOString(),
             files: {
-                ...files,
+                ...testFiles,
                 [filename]: response.content
             },
             result,
@@ -9017,25 +9118,23 @@ async function step(ctx, files, life) {
             think_again_with_compile_error: response.think_again_with_compile_error,
             step: ctx.state().interface?.step ?? 0
         });
-        return [ filename, response.content ];
+        return {
+            location: filename,
+            content: code,
+            scenario
+        };
     })));
-    const newFiles = {
-        ...files,
-        ...Object.fromEntries(validate)
-    };
-    return step(ctx, newFiles, life - 1);
+    return step(ctx, entireFiles, testFiles.map((f => {
+        const validated = validatedFiles.find((v => v.location === f.location));
+        return validated ? validated : f;
+    })), life - 1);
 }
 
-async function process$2(ctx, diagnostics, code) {
+async function process$1(ctx, diagnostics, code, scenario) {
     const pointer = {
         value: null
     };
-    const apiFiles = Object.entries(ctx.state().interface?.files ?? {}).filter((([filename]) => filename.startsWith("src/api/"))).reduce(((acc, [filename, content]) => Object.assign(acc, {
-        [filename]: content
-    })), {});
-    const dtoFiles = Object.entries(ctx.state().interface?.files ?? {}).filter((([filename]) => filename.startsWith("src/api/structures/"))).reduce(((acc, [filename, content]) => Object.assign(acc, {
-        [filename]: content
-    })), {});
+    const artifacts = await compileTestScenario(ctx, scenario);
     const agentica = new MicroAgentica({
         model: ctx.model,
         vendor: {
@@ -9044,19 +9143,25 @@ async function process$2(ctx, diagnostics, code) {
         config: {
             ...ctx.config ?? {}
         },
-        histories: transformTestCorrectHistories(apiFiles, dtoFiles),
+        histories: transformTestCorrectHistories(artifacts),
         controllers: [ createApplication$2({
             model: ctx.model,
             build: next => {
                 pointer.value = next;
             }
-        }) ]
+        }) ],
+        tokenUsage: ctx.usage()
     });
     enforceToolCall(agentica);
-    await agentica.conversate([ "Fix the compilation error in the provided code.", "", "## Original Code", "```typescript", code, "```", "", diagnostics.map((diagnostic => {
-        if (diagnostic.start === undefined || diagnostic.length === undefined) return "";
-        return [ "## Error Information", `- Position: Characters ${diagnostic.start} to ${diagnostic.start + diagnostic.length}`, `- Error Message: ${diagnostic.messageText}`, `- Problematic Code: \`${code.substring(diagnostic.start, diagnostic.start + diagnostic.length)}\``, "" ].join("\n");
-    })), "## Instructions", "1. Focus on the specific error location and message", "2. Provide the corrected TypeScript code", "3. Ensure the fix resolves the compilation error", "", "Return only the fixed code without explanations." ].join("\n"));
+    await randomBackoffRetry((async () => {
+        await agentica.conversate([ "Fix the compilation error in the provided code.", "", "## Original Code", "```typescript", code, "```", "", diagnostics.map((diagnostic => {
+            if (diagnostic.start === undefined || diagnostic.length === undefined) return "";
+            const checkDtoRegexp = `Cannot find module '@ORGANIZATION/template-api/lib/structures/IBbsArticleComment' or its corresponding type declarations.`;
+            const [group] = [ ...checkDtoRegexp.matchAll(/Cannot find module '(.*lib\/structures\/.*)'/g) ];
+            const [_, filename] = group ?? [];
+            return [ "## Error Information", `- Position: Characters ${diagnostic.start} to ${diagnostic.start + diagnostic.length}`, `- Error Message: ${diagnostic.messageText}`, `- Problematic Code: \`${code.substring(diagnostic.start, diagnostic.start + diagnostic.length)}\``, filename ? `The type files located under **/lib/structures are declared in '@ORGANIZATION/PROJECT-api/lib/structures'.\n` + `Note: '@ORGANIZATION/PROJECT-api' must be written exactly as is and should not be replaced.\n` : "" ].join("\n");
+        })), "## Instructions", "1. Focus on the specific error location and message", "2. Provide the corrected TypeScript code", "3. Ensure the fix resolves the compilation error", "", "Return only the fixed code without explanations." ].join("\n"));
+    }));
     if (pointer.value === null) throw new Error("Failed to modify test code.");
     return pointer.value;
 }
@@ -9349,129 +9454,191 @@ const collection$3 = {
     }
 };
 
-const transformTestProgressHistories = (apiFiles, dtoFiles) => [ {
-    id: v4(),
-    created_at: (new Date).toISOString(),
-    type: "systemMessage",
-    text: '# E2E Test Code Generator System Prompt\n\nYou are an expert E2E (End-to-End) test automation engineer specializing in generating test code directly from user scenarios using API functions and TypeScript DTO types.\n\n## Your Role\n\n- Analyze the given user scenario and generate complete E2E test code (max 300 lines).  \n- Use only the **provided API functions and DTO types** to implement realistic, maintainable, and deterministic test flows.  \n- Write tests in **TypeScript** using the `@nestia/e2e` testing style — do **not** use other test frameworks (e.g., Jest, Mocha).  \n- **Focus on simplicity and correctness** - avoid complex type manipulations and ensure all imports match the provided API structure.  \n- When generating E2E test code, you must perform extremely strict type checking.  \n\n## Default Working Language: English\n\n- Use the language specified by user in messages as the working language when explicitly provided  \n- All thinking and responses must be in the working language  \n- All model/field names must be in English regardless of working language  \n\n\n## Input Format\n\nYou will receive:\n\n1. **User Scenario**: A textual description of a business use-case or user flow  \n2. **Filename**: The desired filename for the test file  \n3. **API Files**: A collection of functions exposed by the system under test  \n4. **DTO Files**: TypeScript types used in request/response payloads of API functions  \n\n## Test Generation Guidelines\n\n### 1. API Function Usage\n\n- Must use `import api from "@ORGANIZATION/PROJECT-api";` to import api functions.  \n  - Never use other import statement like `import api from "@PROJECT/api"`  \n- **Only use API functions that are explicitly listed in the provided API Files** - do not assume functions exist.  \n- **Carefully match function names and paths** from the provided API structure.  \n- Connection parameter should be used as-is without modification:  \n\n  ```ts\n  // Correct Usage\n  await api.functional.bbs.articles.post(connection, { body: articleBody });\n\n  // Incorrect - Don\'t modify connection\n  const slowConnection = { ...connection, simulate: { delay: 4000 } };\n  ```  \n\n- API functions follow this pattern: `api.functional.[...].methodName(...)`  \n- For example, if file path is `src/api/functional/bbs/articles/comments/index.ts` and function is `postByArticleId`, use `api.functional.bbs.articles.comments.postByArticleId(...)`  \n\n### 2. DTO Type Usage\n\n- **Import DTO types exactly as provided** in the DTO Files section.  \n- Use the exact import path: `import { ITypeName } from "@ORGANIZATION/PROJECT-api/lib/structures/[exact-path]";`  \n- **Do not assume property names or structures** - only use properties that are explicitly defined in the provided DTO types.  \n- **Ensure all required properties are included** when creating request objects.  \n\nExample:  \n\n  ```ts\n  import { IBbsArticle } from "@ORGANIZATION/PROJECT-api/lib/structures/IBbsArticle";\n  ```  \n\n### 3. Type Safety and Error Prevention\n\n- **Always verify that functions and types exist** in the provided files before using them.  \n- **Use simple, direct type assertions** - avoid complex type manipulations.  \n- **Check for required vs optional properties** in DTO types before creating objects.  \n- **Use only documented API methods** - don\'t assume method existence.  \n\n### 4. Scenario Coverage\n\n- Fully implement the test scenario by chaining relevant API calls.  \n- If the scenario involves data creation, create prerequisite data using corresponding APIs.  \n- Include positive test cases (happy paths) and negative test cases when appropriate.  \n- **Keep test logic simple and straightforward** - avoid overly complex flows.  \n\n## Code Structure & Style\n\n### Test Function Structure\n\n```ts\nexport async function test_api_xxx(connection: api.IConnection): Promise<void> {\n  // Simple, clear test implementation\n}\n```\n\n### Validation Guidelines\n\n- Use `TestValidator` for validations as defined below  \n- Use `typia.assert` for type validations as defined below  \n- **Ensure proper function signatures** when using TestValidator methods  \n- **Verify all required properties** are included when creating test objects  \n\n### Test Validator Definition\n\n```ts\n/**\n * Test validator.\n *\n * `TestValidator` is a collection gathering E2E validation functions.\n *\n */\nexport declare namespace TestValidator {\n    /**\n     * Test whether condition is satisfied.\n     *\n     * @param title Title of error message when condition is not satisfied\n     * @return Currying function\n     */\n    const predicate: (title: string) => <T extends boolean | (() => boolean) | (() => Promise<boolean>)>(condition: T) => T extends () => Promise<boolean> ? Promise<void> : void;\n    /**\n     * Test whether two values are equal.\n     *\n     * If you want to validate `covers` relationship,\n     * call smaller first and then larger.\n     *\n     * Otherwise you wanna non equals validator, combine with {@link error}.\n     *\n     * @param title Title of error message when different\n     * @param exception Exception filter for ignoring some keys\n     * @returns Currying function\n     */\n    const equals: (title: string, exception?: (key: string) => boolean) => <T>(x: T) => (y: T) => void;\n    /**\n     * Test whether error occurs.\n     *\n     * If error occurs, nothing would be happened.\n     *\n     * However, no error exists, then exception would be thrown.\n     *\n     * @param title Title of exception because of no error exists\n     */\n    const error: (title: string) => <T>(task: () => T) => T extends Promise<any> ? Promise<void> : void;\n    const httpError: (title: string) => (...statuses: number[]) => <T>(task: () => T) => T extends Promise<any> ? Promise<void> : void;\n    function proceed(task: () => Promise<any>): Promise<Error | null>;\n    function proceed(task: () => any): Error | null;\n    /**\n     * Validate index API.\n     *\n     * Test whether two indexed values are equal.\n     *\n     * If two values are different, then exception would be thrown.\n     *\n     * @param title Title of error message when different\n     * @return Currying function\n     *\n     * @example https://github.com/samchon/nestia-template/blob/master/src/test/features/api/bbs/test_api_bbs_article_index_search.ts\n     */\n    const index: (title: string) => <Solution extends IEntity<any>>(expected: Solution[]) => <Summary extends IEntity<any>>(gotten: Summary[], trace?: boolean) => void;\n    /**\n     * Valiate search options.\n     *\n     * Test a pagination API supporting search options.\n     *\n     * @param title Title of error message when searching is invalid\n     * @returns Currying function\n     *\n     * @example https://github.com/samchon/nestia-template/blob/master/src/test/features/api/bbs/test_api_bbs_article_index_search.ts\n     */\n    const search: (title: string) => <Entity extends IEntity<any>, Request>(getter: (input: Request) => Promise<Entity[]>) => (total: Entity[], sampleCount?: number) => <Values extends any[]>(props: ISearchProps<Entity, Values, Request>) => Promise<void>;\n    interface ISearchProps<Entity extends IEntity<any>, Values extends any[], Request> {\n        fields: string[];\n        values(entity: Entity): Values;\n        filter(entity: Entity, values: Values): boolean;\n        request(values: Values): Request;\n    }\n    /**\n     * Validate sorting options.\n     *\n     * Test a pagination API supporting sorting options.\n     *\n     * You can validate detailed sorting options both ascending and descending orders\n     * with multiple fields. However, as it forms a complicate currying function,\n     * I recommend you to see below example code before using.\n     *\n     * @param title Title of error message when sorting is invalid\n     * @example https://github.com/samchon/nestia-template/blob/master/src/test/features/api/bbs/test_api_bbs_article_index_sort.ts\n     */\n    const sort: (title: string) => <T extends object, Fields extends string, Sortable extends Array<`-${Fields}` | `+${Fields}`> = Array<`-${Fields}` | `+${Fields}`>>(getter: (sortable: Sortable) => Promise<T[]>) => (...fields: Fields[]) => (comp: (x: T, y: T) => number, filter?: (elem: T) => boolean) => (direction: "+" | "-", trace?: boolean) => Promise<void>;\n    type Sortable<Literal extends string> = Array<`-${Literal}` | `+${Fields}`>;\n}\ninterface IEntity<Type extends string | number | bigint> {\n    id: Type;\n}\nexport {};\n```\n\n### Typia Assert Definition\n\n```ts\n/**\n * Asserts a value type.\n *\n * Asserts a parametric value type and throws a {@link TypeGuardError} with detailed\n * reason, if the parametric value is not following the type `T`. Otherwise, the\n * value is following the type `T`, just input parameter would be returned.\n *\n * If what you want is not asserting but just knowing whether the parametric value is\n * following the type `T` or not, you can choose the {@link is} function instead.\n * Otherwise you want to know all the errors, {@link validate} is the way to go.\n * Also, if you want to automatically cast the parametric value to the type `T`\n * when no problem (perform the assertion guard of type).\n *\n * On the other and, if you don\'t want to allow any superfluous property that is not\n * enrolled to the type `T`, you can use {@link assertEquals} function instead.\n *\n * @template T Type of the input value\n * @param input A value to be asserted\n * @param errorFactory Custom error factory. Default is `TypeGuardError`\n * @returns Parametric input value\n * @throws A {@link TypeGuardError} instance with detailed reason\n *\n */\nexport declare function assert<T>(input: T, errorFactory?: undefined | ((props: TypeGuardError.IProps) => Error)): T;\n/**\n * Asserts a value type.\n *\n * Asserts a parametric value type and throws a {@link TypeGuardError} with detailed\n * reason, if the parametric value is not following the type `T`. Otherwise, the\n * value is following the type `T`, just input parameter would be returned.\n *\n * If what you want is not asserting but just knowing whether the parametric value is\n * following the type `T` or not, you can choose the {@link is} function instead.\n * Otherwise, you want to know all the errors, {@link validate} is the way to go.\n *\n * On the other and, if you don\'t want to allow any superfluous property that is not\n * enrolled to the type `T`, you can use {@link assertEquals} function instead.\n *\n * @template T Type of the input value\n * @param input A value to be asserted\n * @param errorFactory Custom error factory. Default is `TypeGuardError`\n * @returns Parametric input value casted as `T`\n * @throws A {@link TypeGuardError} instance with detailed reason\n *\n */\nexport declare function assert<T>(input: unknown, errorFactory?: undefined | ((props: TypeGuardError.IProps) => Error)): T;\n/**\n * Assertion guard of a value type.\n *\n * Asserts a parametric value type and throws a {@link TypeGuardError} with detailed\n * reason, if the parametric value is not following the type `T`. Otherwise, the\n * value is following the type `T`, nothing would be returned, but the input value\n * would be automatically casted to the type `T`. This is the concept of\n * "Assertion Guard" of a value type.\n *\n * If what you want is not asserting but just knowing whether the parametric value is\n * following the type `T` or not, you can choose the {@link is} function instead.\n * Otherwise you want to know all the errors, {@link validate} is the way to go.\n * Also, if you want to returns the parametric value when no problem, you can use\n * {@link assert} function instead.\n *\n * On the other and, if you don\'t want to allow any superfluous property that is not\n * enrolled to the type `T`, you can use {@link assertGuardEquals} function instead.\n *\n * @template T Type of the input value\n * @param input A value to be asserted\n * @param errorFactory Custom error factory. Default is `TypeGuardError`\n * @throws A {@link TypeGuardError} instance with detailed reason\n *\n */\n```\n\n### Example Format:\n\n```ts\nimport { TestValidator } from "@nestia/e2e";\nimport api from "@ORGANIZATION/PROJECT-api";\nimport { IExampleDto } from "@ORGANIZATION/PROJECT-api/lib/structures/IExampleDto";\nimport typia from "typia";\n\nexport async function test_api_example_flow(connection: api.IConnection): Promise<void> {\n  const input: IExampleDto = { ... }; // construct valid input\n\n  const result = await api.functional.example.post(connection, input);\n\n  typia.assert(result); // ensure response matches expected type\n  TestValidator.equals("result", exceptFunction)(result.someField);\n}\n\n```  \n\n```ts\nexport async function test_api_hub_cart_commodity_at(\n  connection: api.IConnection,\n): Promise<void> {\n  await test_api_hub_admin_login(pool);\n  await test_api_hub_seller_join(pool);\n  await test_api_hub_customer_create(pool);\n\n  const sale: IHubSale = await generate_random_sale(pool, "approved");\n  const commodity: IHubCartCommodity = await generate_random_cart_commodity(\n    pool,\n    sale,\n  );\n\n  const read: IHubCartCommodity =\n    await HubApi.functional.hub.customers.carts.commodities.at(\n      pool.customer,\n      null,\n      commodity.id,\n    );\n  TestValidator.equals("at", exceptSaleKeys)(commodity)(read);\n}\n\nexport const exceptSaleKeys = (key: string): boolean =>\n  key === "aggregate" || key === "swagger" || key.endsWith("_at");\n\n```  \n\n### Import Guidelines\n\n- **Only import what you actually use**  \n- **Verify all imports exist** in the provided API and DTO files  \n- **Use exact import paths** as specified in the file structure  \n\n```ts\nimport { TestValidator } from "@nestia/e2e";\nimport api from "@ORGANIZATION/PROJECT-api";\nimport { ISimpleDto } from "@ORGANIZATION/PROJECT-api/lib/structures/ISimpleDto";\nimport typia from "typia";\n```  \n\n### Data Construction\n\n- **Create simple, valid test data** that matches the DTO structure exactly  \n- **Include all required properties** as defined in the DTO  \n- **Use literal values** rather than complex data generation  \n\n```ts\n// Simple, clear data construction\nconst articleInput: IBbsArticleInput = {\n  title: "Test Article",\n  body: "Test article content",\n  // Include all required properties from the DTO\n};\n```  \n\n## Error Prevention Rules\n\n### 1. Type Matching\n\n- Always ensure function parameters match the expected types from API definitions  \n- Verify that all required properties are included in request objects  \n- Don\'t use properties that aren\'t defined in the DTO types  \n\n### 2. Import Validation\n\n- Only import functions and types that exist in the provided files  \n- Use exact import paths without assumptions  \n- **Follow the exact TestValidator and typia.assert usage patterns** as defined in their type definitions  \n\n### 3. Simple Logic\n\n- Avoid complex type manipulations and filtering functions  \n- Use straightforward validation patterns  \n- Don\'t use TypeScript directives like `@ts-expect-error` or `@ts-ignore`  \n\n### 4. Null Safety\n\n- Check for null/undefined values before using them  \n- Use optional chaining when appropriate  \n- Handle potential null returns from API calls  \n\n```ts\n// Safe null handling\nif (result && result.data) {\n  typia.assert<IExpectedType>(result.data);\n}\n```  \n\n### 5. Type Safety\n\n- If you declare empty array like `[]`, You must define the type of array together.  \n\nExample:  \n\n  ```typescript\n  const emptyArray: IBbsArticle[] = [];\n\n  TestValidator.equals("message")(\n      [] as IBbsArticleComment[],\n    )(data);\n  ```\n\n\n## Output Format\n\nReturn the following:  \n\n1. **Filename**: Suggested filename for the test (from input)  \n2. **Full Test Code**: A TypeScript file (max 300 lines) containing the E2E test  \n3. **Test Explanation**: Brief paragraph explaining what the test does and how it maps to the scenario  \n4. **Execution Notes**: Any setup steps or dependencies required to run the test  \n\n## Best Practices\n\n- **Keep tests simple and readable** - prioritize clarity over cleverness  \n- **Use only provided API functions and DTO types** - no assumptions  \n- **Create minimal but meaningful tests** that cover the core scenario  \n- **Make tests deterministic** with predictable data and flows  \n- **Include clear comments** for complex business logic only  \n- **Follow naming conventions** (`test_api_[feature]_[action]`)  \n- **Validate inputs and outputs** with simple, direct assertions  \n\n## Error Handling\n\n- If the scenario lacks sufficient detail, ask for clarification   \n- If no matching API function is found for a step, mention it and suggest alternatives from the provided API list  \n- If a required DTO property is missing or unclear, request the complete DTO definition  \n- **Always verify that all used functions and types exist** in the provided files before generating code'
-}, {
-    id: v4(),
-    created_at: (new Date).toISOString(),
-    type: "assistantMessage",
-    text: [ "You are the world's best E2E test code generator.", "You will be given a **scenario**, and your job is to generate the corresponding **E2E test code** using only the provided API functions and DTOs.", "", "## Rules", "- Follow the base E2E test style strictly. Never use other frameworks like Jest or Mocha.", "- Use `TestValidator.equals(...)` and `typia.assert(...)` to verify results.", "- Use `HubApi.functional.XXX` for all API calls. These are defined in API Files.", "- Use helper functions like `generate_random_xxx(...)` **only if** they already exist in the base test imports.", "- Do not invent new helpers or use utilities that are not explicitly shown.", "- Keep all tests deterministic and reliable.", "", "## File References", "### API Files", "```typescript", JSON.stringify(apiFiles, null, 2), "```", "", "### DTO Files", "```typescript", JSON.stringify(dtoFiles, null, 2), "```", "", "Now generate the E2E test function based on the given scenario.", "Only output a single `async function` named `test_api_{...}`. No explanation, no commentary." ].join("\n")
-} ];
-
-async function orchestrateTestProgress(ctx, scenarios) {
-    const start = new Date;
-    let complete = 0;
-    const events = await Promise.all(scenarios.map((async scenario => {
-        const code = await process$1(ctx, scenario);
-        const event = {
-            type: "testProgress",
-            created_at: start.toISOString(),
-            filename: `${code.domain}/${scenario.functionName}.ts`,
-            content: code.content,
-            completed: ++complete,
-            total: scenarios.length,
-            step: ctx.state().interface?.step ?? 0
-        };
-        ctx.dispatch(event);
-        return event;
-    })));
-    return events;
+async function orchestrateTestScenario(ctx) {
+    const operations = ctx.state().interface?.document.operations ?? [];
+    if (operations.length === 0) {
+        throw new Error("Cannot write test scenarios because these are no operations.");
+    }
+    const exclude = [];
+    let include = Array.from(operations);
+    do {
+        const matrix = divideArray({
+            array: include,
+            capacity: 30
+        });
+        await Promise.all(matrix.map((async _include => {
+            exclude.push(...await execute(ctx, operations, _include, exclude.map((x => x.endpoint))));
+        })));
+        include = include.filter((op => {
+            if (exclude.some((pg => pg.endpoint.method === op.method && pg.endpoint.path === op.path))) {
+                return false;
+            }
+            return true;
+        }));
+    } while (include.length > 0);
+    return {
+        type: "testScenario",
+        step: ctx.state().analyze?.step ?? 0,
+        scenarios: exclude.flatMap((pg => pg.scenarios.map((plan => ({
+            endpoint: pg.endpoint,
+            draft: plan.draft,
+            functionName: plan.functionName,
+            dependencies: plan.dependsOn
+        }))))),
+        created_at: (new Date).toISOString()
+    };
 }
 
-async function process$1(ctx, scenario) {
+const execute = async (ctx, ops, include, exclude) => {
     const pointer = {
-        value: null
+        value: []
     };
-    const apiFiles = Object.entries(ctx.state().interface?.files ?? {}).filter((([filename]) => filename.startsWith("src/api/"))).reduce(((acc, [filename, content]) => Object.assign(acc, {
-        [filename]: content
-    })), {});
-    const dtoFiles = Object.entries(ctx.state().interface?.files ?? {}).filter((([filename]) => filename.startsWith("src/api/structures/"))).reduce(((acc, [filename, content]) => Object.assign(acc, {
-        [filename]: content
-    })), {});
     const agentica = new MicroAgentica({
         model: ctx.model,
         vendor: ctx.vendor,
         config: {
-            ...ctx.config ?? {}
+            ...ctx.config ?? {},
+            executor: {
+                describe: null
+            }
         },
-        histories: transformTestProgressHistories(apiFiles, dtoFiles),
+        tokenUsage: ctx.usage(),
+        histories: createHistoryProperties(ops, include, exclude),
         controllers: [ createApplication$1({
             model: ctx.model,
             build: next => {
-                pointer.value = next;
+                pointer.value ?? (pointer.value = []);
+                pointer.value.push(...next.scenarioGroups);
             }
         }) ]
     });
     enforceToolCall(agentica);
-    await agentica.conversate([ "Create test code for below scenario:", "", "```json", JSON.stringify(scenario, null, 2), "```" ].join("\n"));
-    if (pointer.value === null) throw new Error("Failed to create test code.");
+    await agentica.conversate(`create test scenarios.`);
+    if (pointer.value.length === 0) {
+        throw new Error("Failed to create test plans.");
+    }
     return pointer.value;
-}
+};
+
+const createHistoryProperties = (operations, include, exclude) => [ {
+    id: v4(),
+    created_at: (new Date).toISOString(),
+    type: "systemMessage",
+    text: 'You are the AutoAPI Test Scenario Generator.\n\nYour job is to analyze an array of API operation objects and generate realistic, structured test scenario drafts for each operation.\n\n---\n\n## Input Format\n\nYou will receive an array of `Operation` objects structured like this:\n\n```ts\n{\n  method: "post" | "get" | "put" | "patch" | "delete",\n  path: "/path/to/resource",\n  specification: string,     // API specification with business logic and constraints\n  description: string,       // Multi-paragraph description\n  summary: string,           // One-line summary\n  parameters: [...],         // List of path/query/body parameters\n  requestBody?: {\n    typeName: string,\n    description: string\n  },\n  responseBody: {\n    typeName: string,\n    description: string\n  }\n}\n```\n\n---\n\n## Output Format\n\nYour output must be an array of grouped test plans, using the following structure:\n\n```ts\n[\n  {\n    method: "post",\n    path: "/shopping/products",\n    plans: [\n      {\n        draft: "Test product creation by submitting two requests with the same product.pid. Confirm that the second request returns a uniqueness constraint error.",\n        dependsOn: [\n          {\n            method: "post",\n            path: "/shopping/categories",\n            purpose: "Create a category beforehand so the product can reference it."\n          },\n          {\n            method: "get",\n            path: "/users/me",\n            purpose: "Verify a valid user session and obtain user context for the test."\n          }\n        ]\n      },\n      {\n        draft: "Verify that missing required fields like \'name\' or \'price\' trigger appropriate validation errors.",\n        dependsOn: []\n      }\n    ]\n  },\n  {\n    method: "patch",\n    path: "/shopping/products/{productId}",\n    plans: [\n      {\n        draft: "Attempt to update a product with an invalid productId and expect a 404 error.",\n        dependsOn: []\n      }\n    ]\n  }\n]\n```\n\n- Each top-level object is a **plan group** for a single unique endpoint (`method + path`).\n- The `plans` array contains **one or more test drafts** for that endpoint.\n- Each `draft` may list its **prerequisite API calls** in the `dependsOn` array, which includes `method`, `path`, and a `purpose` for context.\n\n---\n\n### ✅ **Uniqueness Rule**\n\n> ⚠️ **Each `{method} + {path}` combination must appear only once** in the output array.\n> This means **you must not create multiple plan groups with the same HTTP method and path.**\n\n* Treat each `{method} + {path}` pair as a **unique test identifier**.\n* All test plans (`plans`) related to the same endpoint must be **grouped under a single PlanGroup object**.\n* Duplicating PlanGroups for the same endpoint will lead to invalid output.\n\n**✅ Good:**\n\n```ts\n[\n  {\n    method: "patch",\n    path: "/blog/posts/{postId}",\n    plans: [\n      { draft: "...", dependsOn: [...] },\n      { draft: "...", dependsOn: [...] }\n    ]\n  }\n]\n```\n\n**❌ Bad:**\n\n```ts\n[\n  {\n    method: "patch",\n    path: "/blog/posts/{postId}",\n    plans: [ ... ]\n  },\n  {\n    method: "patch",\n    path: "/blog/posts/{postId}", // Duplicate! Not allowed.\n    plans: [ ... ]\n  }\n]\n```\n\n---\n\n## Writing Guidelines\n\n1. **draft**:\n   - Write a clear and realistic test plan for the operation.\n   - Include both success and failure cases where applicable.\n   - Incorporate constraints mentioned in the API description such as uniqueness, foreign key requirements, or authentication.\n   - For complex operations, include multiple steps within the same `draft` string (e.g., create → verify → delete).\n\n2. **dependsOn**:\n   - List other API operations that must be invoked before this test can be executed.\n   - Each item must include `method`, `path`, and `purpose`.\n   - The `purpose` field should explain *why* the dependency is needed in the test setup.\n\n3. Treat each `{method} + {path}` combination as a unique test identifier.\n\n---\n\n## Purpose\n\nThese test scenario objects are designed to support QA engineers and backend developers in planning automated or manual tests. Each test draft reflects the core functionality and business rules of the API to ensure robust system behavior.'
+}, {
+    id: v4(),
+    created_at: (new Date).toISOString(),
+    type: "systemMessage",
+    text: [ "Below are the full operations. Please refer to this.", "Your role is to draft all test cases for each given Operation.", "It is also permissible to write multiple test codes on a single endpoint.", "However, rather than meaningless tests, business logic tests should be written and an E2E test situation should be assumed.", "", "```json", JSON.stringify(operations.map((el => ({
+        path: el.path,
+        method: el.method,
+        summary: el.summary
+    })))), "```" ].join("\n")
+}, {
+    id: v4(),
+    created_at: (new Date).toISOString(),
+    type: "systemMessage",
+    text: [ "# Included in Test Plan", include.map((el => `- ${el.method.toUpperCase()}: ${el.path}`)).join("\n"), "", "# Excluded from Test Plan", "These are the endpoints that have already been used in test codes generated as part of a plan group.", "These endpoints do not need to be tested again.", "However, it is allowed to reference or depend on these endpoints when writing test codes for other purposes.", exclude.map((el => `- ${el.method.toUpperCase()}: ${el.path}`)).join("\n") ].join("\n")
+} ];
 
 function createApplication$1(props) {
     assertSchemaModel(props.model);
     const application = collection$2[props.model];
-    return {
-        protocol: "class",
-        name: "Create Test Code",
-        application,
-        execute: {
-            createTestCode: next => {
-                props.build(next);
-            }
-        }
-    };
-}
-
-const claude$2 = {
-    model: "claude",
-    options: {
-        reference: true,
-        separate: null
-    },
-    functions: [ {
-        name: "createTestCode",
-        parameters: {
-            description: "Current Type: {@link ICreateTestCodeProps}",
-            type: "object",
-            properties: {
-                plan: {
-                    title: "Strategic approach for test implementation",
-                    description: "Strategic approach for test implementation.\n\nDefine the high-level strategy and logical flow for testing the given\nscenario. Focus on test methodology, data preparation, and assertion\nstrategy.\n\n### Critical Requirements\n\n- Must follow the Test Generation Guildelines.\n- Must Planning the test code Never occur the typescript compile error.\n\n### Planning Elements:\n\n#### Test Methodology\n\n- Identify test scenario type (CRUD operation, authentication flow,\n  validation test)\n- Define test data requirements and preparation strategy\n- Plan positive/negative test cases and edge cases\n- Design assertion logic and validation points\n\n#### Execution Strategy\n\n- Outline step-by-step test execution flow\n- Plan error handling and exception scenarios\n- Define cleanup and teardown procedures\n- Identify dependencies and prerequisites\n\n### Example Plan:\n\n    Test Strategy: Article Creation Validation\n    1. Prepare valid article data with required fields\n    2. Execute POST request to create article\n    3. Validate response structure and data integrity\n    4. Test error scenarios (missing fields, invalid data)\n    5. Verify database state changes\n    6. Reconsider the plan if it doesn't follow the Test Generation\n       Guildelines.",
-                    type: "string"
-                },
-                domain: {
-                    title: "Functional domain classification for test organization",
-                    description: 'Functional domain classification for test organization.\n\nDetermines file structure and test categorization based on API\nfunctionality. Used for organizing tests into logical groups and directory\nhierarchies.\n\n### Naming Rules:\n\n- Lowercase English words only\n- Singular nouns (e.g., "article", "user", "comment")\n- Kebab-case for compound words (e.g., "user-profile", "payment-method")\n- Match primary API resource being tested\n- Domain Name must be named only one word.\n\n### Domain Examples:\n\n- `article` → Article management operations\n- `comment` → Comment-related functionality\n- `auth` → Authentication and authorization\n- `user` → User management operations\n- `payment` → Payment processing\n- `notification` → Notification system',
-                    type: "string"
-                },
-                content: {
-                    title: "Complete TypeScript E2E test implementation",
-                    description: "Complete TypeScript E2E test implementation.\n\nGenerate fully functional, compilation-error-free test code following",
-                    type: "string"
-                }
-            },
-            required: [ "plan", "domain", "content" ],
-            additionalProperties: false,
-            $defs: {}
-        },
-        validate: (() => {
-            const _io0 = input => "string" === typeof input.plan && "string" === typeof input.domain && "string" === typeof input.content;
-            const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.plan || _report(_exceptionable, {
-                path: _path + ".plan",
+    application.functions[0].validate = next => {
+        const result = (() => {
+            const _io0 = input => Array.isArray(input.scenarioGroups) && input.scenarioGroups.every((elem => "object" === typeof elem && null !== elem && _io1(elem)));
+            const _io1 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && (Array.isArray(input.scenarios) && input.scenarios.every((elem => "object" === typeof elem && null !== elem && _io3(elem))));
+            const _io2 = input => "string" === typeof input.path && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method);
+            const _io3 = input => "string" === typeof input.draft && "string" === typeof input.functionName && (Array.isArray(input.dependsOn) && input.dependsOn.every((elem => "object" === typeof elem && null !== elem && _io4(elem))));
+            const _io4 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && "string" === typeof input.purpose;
+            const _vo0 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.scenarioGroups) || _report(_exceptionable, {
+                path: _path + ".scenarioGroups",
+                expected: "Array<IAutoBeTestScenarioApplication.IScenarioGroup>",
+                value: input.scenarioGroups
+            })) && input.scenarioGroups.map(((elem, _index4) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                path: _path + ".scenarioGroups[" + _index4 + "]",
+                expected: "IAutoBeTestScenarioApplication.IScenarioGroup",
+                value: elem
+            })) && _vo1(elem, _path + ".scenarioGroups[" + _index4 + "]", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".scenarioGroups[" + _index4 + "]",
+                expected: "IAutoBeTestScenarioApplication.IScenarioGroup",
+                value: elem
+            }))).every((flag => flag)) || _report(_exceptionable, {
+                path: _path + ".scenarioGroups",
+                expected: "Array<IAutoBeTestScenarioApplication.IScenarioGroup>",
+                value: input.scenarioGroups
+            }) ].every((flag => flag));
+            const _vo1 = (input, _path, _exceptionable = true) => [ ("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
+                path: _path + ".endpoint",
+                expected: "AutoBeOpenApi.IEndpoint",
+                value: input.endpoint
+            })) && _vo2(input.endpoint, _path + ".endpoint", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".endpoint",
+                expected: "AutoBeOpenApi.IEndpoint",
+                value: input.endpoint
+            }), (Array.isArray(input.scenarios) || _report(_exceptionable, {
+                path: _path + ".scenarios",
+                expected: "Array<IAutoBeTestScenarioApplication.IScenario>",
+                value: input.scenarios
+            })) && input.scenarios.map(((elem, _index5) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                path: _path + ".scenarios[" + _index5 + "]",
+                expected: "IAutoBeTestScenarioApplication.IScenario",
+                value: elem
+            })) && _vo3(elem, _path + ".scenarios[" + _index5 + "]", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".scenarios[" + _index5 + "]",
+                expected: "IAutoBeTestScenarioApplication.IScenario",
+                value: elem
+            }))).every((flag => flag)) || _report(_exceptionable, {
+                path: _path + ".scenarios",
+                expected: "Array<IAutoBeTestScenarioApplication.IScenario>",
+                value: input.scenarios
+            }) ].every((flag => flag));
+            const _vo2 = (input, _path, _exceptionable = true) => [ "string" === typeof input.path || _report(_exceptionable, {
+                path: _path + ".path",
                 expected: "string",
-                value: input.plan
-            }), "string" === typeof input.domain || _report(_exceptionable, {
-                path: _path + ".domain",
+                value: input.path
+            }), "get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method || _report(_exceptionable, {
+                path: _path + ".method",
+                expected: '("delete" | "get" | "patch" | "post" | "put")',
+                value: input.method
+            }) ].every((flag => flag));
+            const _vo3 = (input, _path, _exceptionable = true) => [ "string" === typeof input.draft || _report(_exceptionable, {
+                path: _path + ".draft",
                 expected: "string",
-                value: input.domain
-            }), "string" === typeof input.content || _report(_exceptionable, {
-                path: _path + ".content",
+                value: input.draft
+            }), "string" === typeof input.functionName || _report(_exceptionable, {
+                path: _path + ".functionName",
                 expected: "string",
-                value: input.content
+                value: input.functionName
+            }), (Array.isArray(input.dependsOn) || _report(_exceptionable, {
+                path: _path + ".dependsOn",
+                expected: "Array<IAutoBeTestScenarioApplication.IDependsOn>",
+                value: input.dependsOn
+            })) && input.dependsOn.map(((elem, _index6) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                path: _path + ".dependsOn[" + _index6 + "]",
+                expected: "IAutoBeTestScenarioApplication.IDependsOn",
+                value: elem
+            })) && _vo4(elem, _path + ".dependsOn[" + _index6 + "]", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".dependsOn[" + _index6 + "]",
+                expected: "IAutoBeTestScenarioApplication.IDependsOn",
+                value: elem
+            }))).every((flag => flag)) || _report(_exceptionable, {
+                path: _path + ".dependsOn",
+                expected: "Array<IAutoBeTestScenarioApplication.IDependsOn>",
+                value: input.dependsOn
+            }) ].every((flag => flag));
+            const _vo4 = (input, _path, _exceptionable = true) => [ ("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
+                path: _path + ".endpoint",
+                expected: "AutoBeOpenApi.IEndpoint",
+                value: input.endpoint
+            })) && _vo2(input.endpoint, _path + ".endpoint", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".endpoint",
+                expected: "AutoBeOpenApi.IEndpoint",
+                value: input.endpoint
+            }), "string" === typeof input.purpose || _report(_exceptionable, {
+                path: _path + ".purpose",
+                expected: "string",
+                value: input.purpose
             }) ].every((flag => flag));
             const __is = input => "object" === typeof input && null !== input && _io0(input);
             let errors;
@@ -9482,11 +9649,11 @@ const claude$2 = {
                     _report = __typia_transform__validateReport._validateReport(errors);
                     ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
                         path: _path + "",
-                        expected: "ICreateTestCodeProps",
+                        expected: "IAutoBeTestScenarioApplication.IProps",
                         value: input
                     })) && _vo0(input, _path + "", true) || _report(true, {
                         path: _path + "",
-                        expected: "ICreateTestCodeProps",
+                        expected: "IAutoBeTestScenarioApplication.IProps",
                         value: input
                     }))(input, "$input", true);
                     const success = 0 === errors.length;
@@ -9504,345 +9671,42 @@ const claude$2 = {
                     data: input
                 };
             };
-        })()
-    } ]
-};
-
-const collection$2 = {
-    chatgpt: {
-        model: "chatgpt",
-        options: {
-            reference: true,
-            strict: false,
-            separate: null
-        },
-        functions: [ {
-            name: "createTestCode",
-            parameters: {
-                description: "Current Type: {@link ICreateTestCodeProps}",
-                type: "object",
-                properties: {
-                    plan: {
-                        title: "Strategic approach for test implementation",
-                        description: "Strategic approach for test implementation.\n\nDefine the high-level strategy and logical flow for testing the given\nscenario. Focus on test methodology, data preparation, and assertion\nstrategy.\n\n### Critical Requirements\n\n- Must follow the Test Generation Guildelines.\n- Must Planning the test code Never occur the typescript compile error.\n\n### Planning Elements:\n\n#### Test Methodology\n\n- Identify test scenario type (CRUD operation, authentication flow,\n  validation test)\n- Define test data requirements and preparation strategy\n- Plan positive/negative test cases and edge cases\n- Design assertion logic and validation points\n\n#### Execution Strategy\n\n- Outline step-by-step test execution flow\n- Plan error handling and exception scenarios\n- Define cleanup and teardown procedures\n- Identify dependencies and prerequisites\n\n### Example Plan:\n\n    Test Strategy: Article Creation Validation\n    1. Prepare valid article data with required fields\n    2. Execute POST request to create article\n    3. Validate response structure and data integrity\n    4. Test error scenarios (missing fields, invalid data)\n    5. Verify database state changes\n    6. Reconsider the plan if it doesn't follow the Test Generation\n       Guildelines.",
-                        type: "string"
-                    },
-                    domain: {
-                        title: "Functional domain classification for test organization",
-                        description: 'Functional domain classification for test organization.\n\nDetermines file structure and test categorization based on API\nfunctionality. Used for organizing tests into logical groups and directory\nhierarchies.\n\n### Naming Rules:\n\n- Lowercase English words only\n- Singular nouns (e.g., "article", "user", "comment")\n- Kebab-case for compound words (e.g., "user-profile", "payment-method")\n- Match primary API resource being tested\n- Domain Name must be named only one word.\n\n### Domain Examples:\n\n- `article` → Article management operations\n- `comment` → Comment-related functionality\n- `auth` → Authentication and authorization\n- `user` → User management operations\n- `payment` → Payment processing\n- `notification` → Notification system',
-                        type: "string"
-                    },
-                    content: {
-                        title: "Complete TypeScript E2E test implementation",
-                        description: "Complete TypeScript E2E test implementation.\n\nGenerate fully functional, compilation-error-free test code following",
-                        type: "string"
+        })()(next);
+        if (result.success === false) return result;
+        const errors = [];
+        result.data.scenarioGroups.forEach(((pg, i, arr) => {
+            arr.forEach(((target, j) => {
+                if (i !== j && target.endpoint.method === pg.endpoint.method && target.endpoint.path === pg.endpoint.path) {
+                    if (!errors.some((el => el.path !== `planGroups[${j}].path` && el.value !== target.endpoint.path))) {
+                        errors.push({
+                            path: `planGroups[${j}].path`,
+                            expected: `planGroup's {method + path} cannot duplicated.`,
+                            value: target.endpoint.path
+                        });
                     }
-                },
-                required: [ "plan", "domain", "content" ],
-                additionalProperties: false,
-                $defs: {}
-            },
-            validate: (() => {
-                const _io0 = input => "string" === typeof input.plan && "string" === typeof input.domain && "string" === typeof input.content;
-                const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.plan || _report(_exceptionable, {
-                    path: _path + ".plan",
-                    expected: "string",
-                    value: input.plan
-                }), "string" === typeof input.domain || _report(_exceptionable, {
-                    path: _path + ".domain",
-                    expected: "string",
-                    value: input.domain
-                }), "string" === typeof input.content || _report(_exceptionable, {
-                    path: _path + ".content",
-                    expected: "string",
-                    value: input.content
-                }) ].every((flag => flag));
-                const __is = input => "object" === typeof input && null !== input && _io0(input);
-                let errors;
-                let _report;
-                return input => {
-                    if (false === __is(input)) {
-                        errors = [];
-                        _report = __typia_transform__validateReport._validateReport(errors);
-                        ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
-                            path: _path + "",
-                            expected: "ICreateTestCodeProps",
-                            value: input
-                        })) && _vo0(input, _path + "", true) || _report(true, {
-                            path: _path + "",
-                            expected: "ICreateTestCodeProps",
-                            value: input
-                        }))(input, "$input", true);
-                        const success = 0 === errors.length;
-                        return success ? {
-                            success,
-                            data: input
-                        } : {
-                            success,
-                            errors,
-                            data: input
-                        };
-                    }
-                    return {
-                        success: true,
-                        data: input
-                    };
-                };
-            })()
-        } ]
-    },
-    claude: claude$2,
-    llama: claude$2,
-    deepseek: claude$2,
-    3.1: claude$2,
-    "3.0": {
-        model: "3.0",
-        options: {
-            constraint: true,
-            recursive: 3,
-            separate: null
-        },
-        functions: [ {
-            name: "createTestCode",
-            parameters: {
-                type: "object",
-                properties: {
-                    plan: {
-                        type: "string",
-                        title: "Strategic approach for test implementation",
-                        description: "Strategic approach for test implementation.\n\nDefine the high-level strategy and logical flow for testing the given\nscenario. Focus on test methodology, data preparation, and assertion\nstrategy.\n\n### Critical Requirements\n\n- Must follow the Test Generation Guildelines.\n- Must Planning the test code Never occur the typescript compile error.\n\n### Planning Elements:\n\n#### Test Methodology\n\n- Identify test scenario type (CRUD operation, authentication flow,\n  validation test)\n- Define test data requirements and preparation strategy\n- Plan positive/negative test cases and edge cases\n- Design assertion logic and validation points\n\n#### Execution Strategy\n\n- Outline step-by-step test execution flow\n- Plan error handling and exception scenarios\n- Define cleanup and teardown procedures\n- Identify dependencies and prerequisites\n\n### Example Plan:\n\n    Test Strategy: Article Creation Validation\n    1. Prepare valid article data with required fields\n    2. Execute POST request to create article\n    3. Validate response structure and data integrity\n    4. Test error scenarios (missing fields, invalid data)\n    5. Verify database state changes\n    6. Reconsider the plan if it doesn't follow the Test Generation\n       Guildelines."
-                    },
-                    domain: {
-                        type: "string",
-                        title: "Functional domain classification for test organization",
-                        description: 'Functional domain classification for test organization.\n\nDetermines file structure and test categorization based on API\nfunctionality. Used for organizing tests into logical groups and directory\nhierarchies.\n\n### Naming Rules:\n\n- Lowercase English words only\n- Singular nouns (e.g., "article", "user", "comment")\n- Kebab-case for compound words (e.g., "user-profile", "payment-method")\n- Match primary API resource being tested\n- Domain Name must be named only one word.\n\n### Domain Examples:\n\n- `article` → Article management operations\n- `comment` → Comment-related functionality\n- `auth` → Authentication and authorization\n- `user` → User management operations\n- `payment` → Payment processing\n- `notification` → Notification system'
-                    },
-                    content: {
-                        type: "string",
-                        title: "Complete TypeScript E2E test implementation",
-                        description: "Complete TypeScript E2E test implementation.\n\nGenerate fully functional, compilation-error-free test code following"
+                    if (!errors.some((el => el.path !== `planGroups[${j}].method` && el.value !== target.endpoint.method))) {
+                        errors.push({
+                            path: `planGroups[${j}].method`,
+                            expected: `planGroup's {method + path} cannot duplicated.`,
+                            value: target.endpoint.method
+                        });
                     }
-                },
-                required: [ "plan", "domain", "content" ],
-                description: "Current Type: {@link ICreateTestCodeProps}",
-                additionalProperties: false
-            },
-            validate: (() => {
-                const _io0 = input => "string" === typeof input.plan && "string" === typeof input.domain && "string" === typeof input.content;
-                const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.plan || _report(_exceptionable, {
-                    path: _path + ".plan",
-                    expected: "string",
-                    value: input.plan
-                }), "string" === typeof input.domain || _report(_exceptionable, {
-                    path: _path + ".domain",
-                    expected: "string",
-                    value: input.domain
-                }), "string" === typeof input.content || _report(_exceptionable, {
-                    path: _path + ".content",
-                    expected: "string",
-                    value: input.content
-                }) ].every((flag => flag));
-                const __is = input => "object" === typeof input && null !== input && _io0(input);
-                let errors;
-                let _report;
-                return input => {
-                    if (false === __is(input)) {
-                        errors = [];
-                        _report = __typia_transform__validateReport._validateReport(errors);
-                        ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
-                            path: _path + "",
-                            expected: "ICreateTestCodeProps",
-                            value: input
-                        })) && _vo0(input, _path + "", true) || _report(true, {
-                            path: _path + "",
-                            expected: "ICreateTestCodeProps",
-                            value: input
-                        }))(input, "$input", true);
-                        const success = 0 === errors.length;
-                        return success ? {
-                            success,
-                            data: input
-                        } : {
-                            success,
-                            errors,
-                            data: input
-                        };
-                    }
-                    return {
-                        success: true,
-                        data: input
-                    };
-                };
-            })()
-        } ]
-    }
-};
-
-const transformTestScenarioHistories = (state, allEndpoints, files) => {
-    if (state.analyze === null) return [ {
-        id: v4(),
-        created_at: (new Date).toISOString(),
-        type: "systemMessage",
-        text: [ "Requirement analysis is not yet completed.", "Don't call the any tool function,", "but say to process the requirement analysis." ].join(" ")
-    } ]; else if (state.prisma === null) return [ {
-        id: v4(),
-        created_at: (new Date).toISOString(),
-        type: "systemMessage",
-        text: [ "Prisma DB schema generation is not yet completed.", "Don't call the any tool function,", "but say to process the Prisma DB schema generation." ].join(" ")
-    } ]; else if (state.analyze.step !== state.prisma.step) return [ {
-        id: v4(),
-        created_at: (new Date).toISOString(),
-        type: "systemMessage",
-        text: [ "Prisma DB schema generation has not been updated", "for the latest requirement analysis.", "Don't call the any tool function,", "but say to re-process the Prisma DB schema generation." ].join(" ")
-    } ]; else if (state.prisma.compiled.type !== "success") return [ {
-        id: v4(),
-        created_at: (new Date).toISOString(),
-        type: "systemMessage",
-        text: [ "Prisma DB schema generation has not been updated", "for the latest requirement analysis.", "Don't call the any tool function,", "but say to re-process the Prisma DB schema generation." ].join(" ")
-    } ]; else if (state.interface === null) return [ {
-        id: v4(),
-        created_at: (new Date).toISOString(),
-        type: "systemMessage",
-        text: [ "Interface generation is not yet completed.", "Don't call the any tool function,", "but say to process the interface generation." ].join(" ")
-    } ];
-    return [ {
-        id: v4(),
-        created_at: (new Date).toISOString(),
-        type: "systemMessage",
-        text: "# System Prompt: User Scenario Generator for API Endpoints\n\n## Role Definition\nYou are a world-class User Experience Analyst and Business Scenario Expert who specializes in analyzing API endpoints to generate comprehensive user scenarios from a pure user perspective. Your scenarios will be used as documentation and comments in test code to help developers understand the real-world user context behind each test.\n\n## Primary Objective\nGenerate all possible scenarios that real users might experience with a single given API endpoint, focusing exclusively on user intentions, motivations, and behaviors rather than technical testing perspectives.\n\n## Core Constraints\n\n### Single Endpoint Limitation\n- Each scenario must be completely achievable using ONLY the provided endpoint\n- Do NOT create scenarios that require multiple API calls or dependencies on other endpoints\n- Each user journey must be self-contained and complete within this single endpoint interaction\n\n### Practicality Constraint for Scenario Quantity\n\n- Do NOT generate an excessive number of test scenarios for trivial endpoints.\n- If the endpoint is a simple read-only operation that returns a static or predictable object (e.g. `{ cpu: number, system: number }`), limit scenarios to those that reflect meaningful variations in user context, not in raw input permutations.\n- Avoid producing multiple user error or edge case scenarios when they provide no additional business insight.\n- Prioritize business relevance over theoretical input diversity.\n- The goal is to maximize scenario value, not quantity.\n\n\n## Scenario Generation Principles\n\n### 1. Pure User-Centric Perspective\n- Focus entirely on what users want to achieve through the API\n- Consider real business contexts and user motivations\n- Emphasize user intent and expected value over technical implementation\n- Write as if documenting actual user stories for product requirements\n\n### 2. Comprehensive Single-Endpoint Coverage\nConsider all the following perspectives when generating scenarios for the single endpoint:\n\n#### A. Happy Path User Journeys\n- Most common and expected user behaviors\n- Standard workflows that lead to successful user outcomes\n- Primary business use cases users perform with this endpoint\n\n#### B. Alternative User Approaches\n- Valid but different ways users might achieve their goals\n- Scenarios using optional parameters or different input combinations\n- Less common but legitimate user behaviors within normal boundaries\n\n#### C. User Error Situations\n- Natural user mistakes with input data (incorrect formats, missing fields)\n- User attempts without proper authentication or authorization\n- User actions that violate business rules or constraints\n- User encounters with system limitations\n\n#### D. Boundary User Behaviors\n- User attempts with extreme values (minimum/maximum limits)\n- User submissions with empty, null, or unusual data\n- User inputs with special characters, long strings, or edge cases\n- User interactions testing system boundaries\n\n#### E. Contextual User Situations\n- User interactions when resources exist vs. don't exist\n- Different user roles attempting the same actions\n- Time-sensitive user scenarios (expired sessions, scheduled operations)\n- User attempts during various system states\n\n### 3. Scenario Writing Format for Test Documentation\nWrite each scenario using the following structure optimized for test code comments:\n\n```\n**Scenario**: [Clear, descriptive title from user perspective]\n\n**User Context**: [Who is the user and why are they performing this action]\n\n**User Goal**: [What the user wants to accomplish]\n\n**User Actions**: [Specific steps the user takes with this endpoint]\n\n**Expected Experience**: [What the user expects to happen and how they'll know it worked]\n\n**Business Value**: [Why this scenario matters to the business]\n\n**Input Test Files**: [The test file names required for combining this scenario. If you have multiple files, connect them with commas.]\n```\n\n## Scenario Generation Checklist for Single Endpoint\n\n### Data Input Perspective\n- [ ] User providing complete, valid data\n- [ ] User missing required fields (intentionally or accidentally)\n- [ ] User sending incorrectly formatted data\n- [ ] User using boundary values (maximum/minimum)\n- [ ] User including special characters or multilingual content\n\n### User Permission Perspective\n- [ ] Users with appropriate permissions\n- [ ] Users with insufficient permissions\n- [ ] Unauthenticated users attempting access\n- [ ] Users with expired authentication\n\n### Resource State Perspective\n- [ ] User interacting when target resource exists\n- [ ] User interacting when target resource doesn't exist\n- [ ] User interacting with resources in various states\n- [ ] User encountering resources modified by others\n\n### User Experience Perspective\n- [ ] Users with realistic data volumes\n- [ ] Users performing time-sensitive operations\n- [ ] Users with different technical skill levels\n- [ ] Users in different business contexts\n\n### Business Context Perspective\n- [ ] Users following standard business processes\n- [ ] Users encountering business rule violations\n- [ ] Users in exceptional business situations\n- [ ] Users with varying business needs\n\n## Output Requirements for Test Documentation\n\nEach scenario must provide sufficient detail for developers to understand:\n\n1. **User Story Context**: Clear understanding of who the user is and their motivation\n2. **Business Justification**: Why this scenario matters for the product\n3. **User Behavior Pattern**: How real users would naturally interact with the endpoint\n4. **Success Criteria**: How users measure successful completion of their goal\n5. **Function Name Guidance**: Clear enough description to derive meaningful test function names\n\n## Quality Standards for Test Code Comments\n\n- Write scenarios that help developers empathize with real users\n- Focus on business value and user outcomes, not technical mechanics\n- Provide enough context that a developer can understand the user's situation\n- Ensure scenarios reflect realistic business situations\n- Make each scenario distinct and valuable for understanding user needs\n- Use language that both technical and non-technical stakeholders can understand\n\n## Guidelines\n\n- Avoid mentioning test code, assertions, or technical implementation details\n- Write purely from the user's perspective using narrative language\n- Create realistic scenarios that reflect actual business situations\n- Ensure scenarios are comprehensive yet practical for a single endpoint\n- Focus on user value and business outcomes\n- Make scenarios detailed enough to understand full user context\n\n## Expected Input\nYou will receive a single API endpoint specification including:\n- HTTP method and endpoint path\n- Request/response schemas\n- Authentication requirements\n- Parameter definitions\n- Business context when available\n\n## Expected Output\nFor the given API endpoint, provide:\n- Categorized user scenarios covering all perspectives mentioned above\n- Each scenario following the specified format for test documentation\n- Scenarios that are complete and achievable with only the single provided endpoint\n- Clear mapping between user intentions and the specific API operation\n- Sufficient detail to understand both user context and business value\n\n## Working Language\n- Default working language: English\n- Use the language specified by user in messages as the working language when explicitly provided\n- All thinking and responses must be in the working language\n- Maintain consistent perspective and tone throughout all scenarios"
-    }, {
-        id: v4(),
-        created_at: (new Date).toISOString(),
-        type: "systemMessage",
-        text: [ "# Result of Analyze Agent", "- The following document contains the user requirements that were extracted through conversations with the user by the Analyze Agent.", "- The database schema was designed based on these requirements, so you may refer to this document when writing test code or reviewing the schema.", "", `## User Request`, "", `- ${state.analyze.reason}`, "", `## Requirement Analysis Report`, "", "```json", JSON.stringify(state.analyze.files), "```" ].join("\n")
-    }, {
-        id: v4(),
-        created_at: (new Date).toISOString(),
-        type: "systemMessage",
-        text: [ "# Result of Prisma Agent", "- Given the following database schema and entity-relationship diagram, write appropriate test code to validate the constraints and relationships defined in the schema. For example, if there is a unique column, include a test that ensures its uniqueness.", "- The test code should strictly adhere to the schema and relationships—no violations of constraints should occur.", "- Use the information from the schema and diagram to design meaningful and accurate test cases.", "", "## Prisma DB Schema", "```json", JSON.stringify(state.prisma.schemas), "```", "", "## Entity Relationship Diagrams", "```json", JSON.stringify(state.prisma.compiled.diagrams), "```" ].join("\n")
-    }, {
-        id: v4(),
-        created_at: (new Date).toISOString(),
-        type: "systemMessage",
-        text: [ "# Result of Interfaced Agent", "- OpenAPI document generation is ready.", "", "Call the provided tool function to generate the user scenarios", "referencing below OpenAPI document.", "", `## OpenAPI Document`, "```json", JSON.stringify(state.interface.document), "```" ].join("\n")
-    }, {
-        id: v4(),
-        created_at: (new Date).toISOString(),
-        type: "systemMessage",
-        text: "# System Prompt: User Scenario Generator for API Endpoints\n\n## Role Definition\nYou are a world-class User Experience Analyst and Business Scenario Expert who specializes in analyzing API endpoints to generate comprehensive user scenarios from a pure user perspective. Your scenarios will be used as documentation and comments in test code to help developers understand the real-world user context behind each test.\n\n## Primary Objective\nGenerate all possible scenarios that real users might experience with a single given API endpoint, focusing exclusively on user intentions, motivations, and behaviors rather than technical testing perspectives.\n\n## Core Constraints\n\n### Single Endpoint Limitation\n- Each scenario must be completely achievable using ONLY the provided endpoint\n- Do NOT create scenarios that require multiple API calls or dependencies on other endpoints\n- Each user journey must be self-contained and complete within this single endpoint interaction\n\n### Practicality Constraint for Scenario Quantity\n\n- Do NOT generate an excessive number of test scenarios for trivial endpoints.\n- If the endpoint is a simple read-only operation that returns a static or predictable object (e.g. `{ cpu: number, system: number }`), limit scenarios to those that reflect meaningful variations in user context, not in raw input permutations.\n- Avoid producing multiple user error or edge case scenarios when they provide no additional business insight.\n- Prioritize business relevance over theoretical input diversity.\n- The goal is to maximize scenario value, not quantity.\n\n\n## Scenario Generation Principles\n\n### 1. Pure User-Centric Perspective\n- Focus entirely on what users want to achieve through the API\n- Consider real business contexts and user motivations\n- Emphasize user intent and expected value over technical implementation\n- Write as if documenting actual user stories for product requirements\n\n### 2. Comprehensive Single-Endpoint Coverage\nConsider all the following perspectives when generating scenarios for the single endpoint:\n\n#### A. Happy Path User Journeys\n- Most common and expected user behaviors\n- Standard workflows that lead to successful user outcomes\n- Primary business use cases users perform with this endpoint\n\n#### B. Alternative User Approaches\n- Valid but different ways users might achieve their goals\n- Scenarios using optional parameters or different input combinations\n- Less common but legitimate user behaviors within normal boundaries\n\n#### C. User Error Situations\n- Natural user mistakes with input data (incorrect formats, missing fields)\n- User attempts without proper authentication or authorization\n- User actions that violate business rules or constraints\n- User encounters with system limitations\n\n#### D. Boundary User Behaviors\n- User attempts with extreme values (minimum/maximum limits)\n- User submissions with empty, null, or unusual data\n- User inputs with special characters, long strings, or edge cases\n- User interactions testing system boundaries\n\n#### E. Contextual User Situations\n- User interactions when resources exist vs. don't exist\n- Different user roles attempting the same actions\n- Time-sensitive user scenarios (expired sessions, scheduled operations)\n- User attempts during various system states\n\n### 3. Scenario Writing Format for Test Documentation\nWrite each scenario using the following structure optimized for test code comments:\n\n```\n**Scenario**: [Clear, descriptive title from user perspective]\n\n**User Context**: [Who is the user and why are they performing this action]\n\n**User Goal**: [What the user wants to accomplish]\n\n**User Actions**: [Specific steps the user takes with this endpoint]\n\n**Expected Experience**: [What the user expects to happen and how they'll know it worked]\n\n**Business Value**: [Why this scenario matters to the business]\n\n**Input Test Files**: [The test file names required for combining this scenario. If you have multiple files, connect them with commas.]\n```\n\n## Scenario Generation Checklist for Single Endpoint\n\n### Data Input Perspective\n- [ ] User providing complete, valid data\n- [ ] User missing required fields (intentionally or accidentally)\n- [ ] User sending incorrectly formatted data\n- [ ] User using boundary values (maximum/minimum)\n- [ ] User including special characters or multilingual content\n\n### User Permission Perspective\n- [ ] Users with appropriate permissions\n- [ ] Users with insufficient permissions\n- [ ] Unauthenticated users attempting access\n- [ ] Users with expired authentication\n\n### Resource State Perspective\n- [ ] User interacting when target resource exists\n- [ ] User interacting when target resource doesn't exist\n- [ ] User interacting with resources in various states\n- [ ] User encountering resources modified by others\n\n### User Experience Perspective\n- [ ] Users with realistic data volumes\n- [ ] Users performing time-sensitive operations\n- [ ] Users with different technical skill levels\n- [ ] Users in different business contexts\n\n### Business Context Perspective\n- [ ] Users following standard business processes\n- [ ] Users encountering business rule violations\n- [ ] Users in exceptional business situations\n- [ ] Users with varying business needs\n\n## Output Requirements for Test Documentation\n\nEach scenario must provide sufficient detail for developers to understand:\n\n1. **User Story Context**: Clear understanding of who the user is and their motivation\n2. **Business Justification**: Why this scenario matters for the product\n3. **User Behavior Pattern**: How real users would naturally interact with the endpoint\n4. **Success Criteria**: How users measure successful completion of their goal\n5. **Function Name Guidance**: Clear enough description to derive meaningful test function names\n\n## Quality Standards for Test Code Comments\n\n- Write scenarios that help developers empathize with real users\n- Focus on business value and user outcomes, not technical mechanics\n- Provide enough context that a developer can understand the user's situation\n- Ensure scenarios reflect realistic business situations\n- Make each scenario distinct and valuable for understanding user needs\n- Use language that both technical and non-technical stakeholders can understand\n\n## Guidelines\n\n- Avoid mentioning test code, assertions, or technical implementation details\n- Write purely from the user's perspective using narrative language\n- Create realistic scenarios that reflect actual business situations\n- Ensure scenarios are comprehensive yet practical for a single endpoint\n- Focus on user value and business outcomes\n- Make scenarios detailed enough to understand full user context\n\n## Expected Input\nYou will receive a single API endpoint specification including:\n- HTTP method and endpoint path\n- Request/response schemas\n- Authentication requirements\n- Parameter definitions\n- Business context when available\n\n## Expected Output\nFor the given API endpoint, provide:\n- Categorized user scenarios covering all perspectives mentioned above\n- Each scenario following the specified format for test documentation\n- Scenarios that are complete and achievable with only the single provided endpoint\n- Clear mapping between user intentions and the specific API operation\n- Sufficient detail to understand both user context and business value\n\n## Working Language\n- Default working language: English\n- Use the language specified by user in messages as the working language when explicitly provided\n- All thinking and responses must be in the working language\n- Maintain consistent perspective and tone throughout all scenarios"
-    }, {
-        id: v4(),
-        created_at: (new Date).toISOString(),
-        type: "systemMessage",
-        text: [ `This is a description of different APIs.`, `Different APIs may have to be called to create one.`, `Check which functions have been developed.`, "```json", JSON.stringify(allEndpoints, null, 2), "```" ].join("\n")
-    }, {
-        id: v4(),
-        created_at: (new Date).toISOString(),
-        type: "systemMessage",
-        text: [ "Below is basically the generated test code,", "which is a test to verify that the API is simply called and successful.", "Since there is already an automatically generated API,", "when a user requests to create a test scenario, two or more APIs must be combined,", "but a test in which the currently given endpoint is the main must be created.", '"Input Test Files" should be selected from the list of files here.', "```json", JSON.stringify(files, null, 2), "```" ].join("\n")
-    } ];
-};
-
-async function orchestrateTestScenario(ctx, capacity = 4) {
-    const files = Object.entries(ctx.state().interface?.files ?? {}).filter((([filename]) => filename.startsWith("test/features/api/"))).reduce(((acc, [filename, content]) => Object.assign(acc, {
-        [filename]: content
-    })), {});
-    const operations = ctx.state().interface?.document.operations ?? [];
-    const endpoints = operations.map((it => ({
-        method: it.method,
-        path: it.path,
-        summary: it.summary,
-        description: it.description,
-        parameters: it.parameters,
-        requestBody: it.requestBody,
-        responseBody: it.responseBody
-    })));
-    const matrix = divideArray({
-        array: endpoints,
-        capacity
-    });
-    const start = new Date;
-    let completed = 0;
-    const scenarios = await Promise.all(matrix.map((async e => {
-        const rows = await divideAndConquer(ctx, e, endpoints, files, 3, (count => {
-            completed += count;
+                }
+            }));
         }));
-        ctx.dispatch({
-            type: "testScenario",
-            scenarios: rows,
-            total: rows.flatMap((el => el.scenarios)).length,
-            step: ctx.state().test?.step ?? 0,
-            completed,
-            created_at: start.toISOString()
-        });
-        return rows;
-    })));
-    return {
-        type: "testScenario",
-        scenarios: scenarios.flat(),
-        total: scenarios.flat().flatMap((el => el.scenarios)).length,
-        step: ctx.state().test?.step ?? 0,
-        completed,
-        created_at: start.toISOString()
-    };
-}
-
-async function divideAndConquer(ctx, endpoints, allEndpoints, files, retry, progress) {
-    const remained = new HashSet(endpoints, OpenApiEndpointComparator.hashCode, OpenApiEndpointComparator.equals);
-    const scenarios = new HashMap(OpenApiEndpointComparator.hashCode, OpenApiEndpointComparator.equals);
-    for (let i = 0; i < retry; ++i) {
-        if (remained.empty() === true || scenarios.size() >= endpoints.length) break;
-        const before = scenarios.size();
-        const newbie = await process(ctx, Array.from(remained), allEndpoints, files);
-        for (const item of newbie) {
-            scenarios.set(item.endpoint, item.scenarios);
-            remained.erase(item.endpoint);
+        if (errors.length !== 0) {
+            console.log(JSON.stringify(errors, null, 2), "errors");
+            return {
+                success: false,
+                errors,
+                data: next
+            };
         }
-        if (scenarios.size() - before !== 0) progress(scenarios.size() - before);
-    }
-    return Array.from(scenarios.toJSON()).map((it => ({
-        endpoint: it.first,
-        scenarios: it.second
-    })));
-}
-
-async function process(ctx, endpoints, allEndpoints, files) {
-    const pointer = {
-        value: null
+        return result;
     };
-    const agentica = new MicroAgentica({
-        model: ctx.model,
-        vendor: ctx.vendor,
-        config: {
-            ...ctx.config ?? {
-                locale: "en-US"
-            },
-            systemPrompt: {
-                describe: () => "Answer only 'completion' or 'failure'."
-            }
-        },
-        tokenUsage: ctx.usage(),
-        histories: [ ...transformTestScenarioHistories(ctx.state(), allEndpoints, files) ],
-        controllers: [ createApplication({
-            model: ctx.model,
-            build: next => {
-                pointer.value ?? (pointer.value = []);
-                pointer.value.push(...next.scenarios);
-            }
-        }) ]
-    });
-    enforceToolCall(agentica);
-    await agentica.conversate([ "Make User Scenarios for below endpoints:", "", "```json", JSON.stringify(endpoints, null, 2), "```" ].join("\n"));
-    if (pointer.value === null) throw new Error("Failed to make scenarios.");
-    return pointer.value;
-}
-
-function createApplication(props) {
-    assertSchemaModel(props.model);
-    const application = collection$1[props.model];
     return {
         protocol: "class",
-        name: "Make User Scenarios",
+        name: "Make test plans",
         application,
         execute: {
             makeScenario: next => {
@@ -9852,7 +9716,7 @@ function createApplication(props) {
     };
 }
 
-const claude$1 = {
+const claude$2 = {
     model: "claude",
     options: {
         reference: true,
@@ -9861,19 +9725,19 @@ const claude$1 = {
     functions: [ {
         name: "makeScenario",
         parameters: {
-            description: " Properties containing the endpoints and user scenarios.\n\n------------------------------\n\nCurrent Type: {@link IMakeScenarioProps}",
+            description: " Properties containing the endpoints and test scenarios.\n\n------------------------------\n\nCurrent Type: {@link IAutoBeTestScenarioApplication.IProps}",
             type: "object",
             properties: {
-                scenarios: {
-                    title: "Array of user scenarios",
-                    description: "Array of user scenarios.",
+                scenarioGroups: {
+                    title: "Array of test scenario groups",
+                    description: "Array of test scenario groups.",
                     type: "array",
                     items: {
-                        description: "Current Type: {@link AutoBeTest.IScenario}",
+                        description: "Current Type: {@link IAutoBeTestScenarioApplication.IScenarioGroup}",
                         type: "object",
                         properties: {
                             endpoint: {
-                                description: "Target API endpoint for user scenario generation.\n\nThis represents the single API endpoint that will be analyzed to generate\ncomprehensive user scenarios. The endpoint contains all technical\nspecifications needed to understand user interactions, including HTTP\nmethods, paths, parameters, request/response schemas, and authentication\nrequirements.\n\n## Core Purpose\n\n- Serves as the foundation for user-centric scenario generation\n- Contains complete API specification for understanding user capabilities\n- Provides schema constraints for realistic user data generation\n- Defines authentication and permission requirements for user context\n\n## User Scenario Context\n\nThis endpoint information enables generation of scenarios that consider:\n\n- What users can realistically accomplish with this endpoint\n- How users would naturally interact with the API functionality\n- What business value users seek from this endpoint\n- What constraints and limitations users will encounter\n- How authentication affects user access patterns\n- What data formats users need to provide or expect to receive\n\n## Single Endpoint Constraint\n\nEach scenario generated must interact with ONLY this endpoint. Scenarios\nshould not assume or require calls to other endpoints, ensuring each user\njourney is complete and testable in isolation.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
+                                description: "Target API endpoint to test.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
                                 type: "object",
                                 properties: {
                                     path: {
@@ -9900,24 +9764,66 @@ const claude$1 = {
                                 required: [ "path", "method" ]
                             },
                             scenarios: {
-                                title: "Comprehensive collection of user-centric scenarios for the endpoint",
-                                description: "Comprehensive collection of user-centric scenarios for the endpoint.\n\nEach scenario represents a realistic user journey, intention, or\nsituation when interacting with this specific API endpoint. All scenarios\nare written from the user's perspective, focusing on what they want to\nachieve and how they naturally interact with the API functionality.\n\n## Scenario Coverage Framework\n\nThe scenarios must comprehensively cover all user interaction patterns:\n\n### 1. Happy Path User Journeys\n\n- Primary business use cases that users commonly perform\n- Standard workflows leading to successful user outcomes\n- Typical user behaviors with valid inputs and proper permissions\n- Most frequent user intentions and expected interactions\n\n### 2. Alternative User Approaches\n\n- Valid alternative ways users might achieve their goals\n- User scenarios utilizing optional parameters or different input patterns\n- Less common but legitimate user behaviors within normal boundaries\n- User experimentation with available API features\n\n### 3. User Error Situations\n\n- Natural user mistakes with input data (incorrect formats, missing fields)\n- User attempts without proper authentication or authorization\n- User actions that violate business rules or constraints\n- User encounters with system limitations (rate limits, quotas)\n\n### 4. Boundary User Behaviors\n\n- User attempts with extreme values (minimum/maximum limits)\n- User submissions with empty, null, or unusual data\n- User inputs with special characters, long strings, or edge cases\n- User interactions testing system boundaries\n\n### 5. Contextual User Situations\n\n- User interactions when resources exist vs. don't exist\n- Different user roles attempting the same actions\n- Time-sensitive user scenarios (expired sessions, scheduled operations)\n- User attempts during various system states\n\n## User-Centric Quality Standards\n\nEach scenario must:\n\n- Focus entirely on user motivation, context, and expected outcomes\n- Describe realistic business situations users actually encounter\n- Include clear user intent and the value they seek\n- Specify user-provided data and user-expected results\n- Be complete within the single endpoint constraint\n- Provide sufficient context for understanding user behavior patterns\n- Avoid technical implementation details or testing terminology\n\n## Single Endpoint Constraint Application\n\nEvery scenario must:\n\n- Complete the entire user journey using only this one endpoint\n- Not depend on or reference other API endpoints\n- Include all necessary context within the scenario itself\n- Represent a complete, self-contained user interaction\n\n## Business Value Focus\n\nThese user scenarios ensure:\n\n- Understanding of real user needs and behaviors\n- Comprehensive coverage of user interaction patterns\n- Proper handling of user errors and edge cases\n- Appropriate user feedback and experience design\n- Business rule validation from user perspective\n- Security and permission handling for different user contexts",
+                                title: "Array of test scenarios",
+                                description: "Array of test scenarios.",
                                 type: "array",
                                 items: {
-                                    description: "Current Type: {@link AutoBeTest.Scenario}",
+                                    description: "Description of the current {@link IAutoBeTestScenarioApplication.IScenario} type:\n\n> Represents a test scenario for a single API operation.\n> \n> This interface extends `AutoBeOpenApi.IEndpoint`, inheriting its HTTP\n> method and path information, and adds two key properties:\n> \n> - `draft`: A free-form, human-readable test scenario description for the API\n>   endpoint.\n> - `dependsOn`: A list of other API endpoints that must be invoked beforehand\n>   in order to prepare the context for this test. Each dependency includes\n>   the purpose of the dependency.\n> \n> This structure is intended to help organize test specifications for complex\n> workflows and ensure that all prerequisites are explicitly declared.",
                                     type: "object",
                                     properties: {
+                                        draft: {
+                                            description: "A detailed natural language description of how this API endpoint should\nbe tested. This should include both successful and failure scenarios,\nbusiness rule validations, edge cases, and any sequence of steps\nnecessary to perform the test. A subsequent agent will use this draft to\ngenerate multiple test scenarios.",
+                                            type: "string"
+                                        },
                                         functionName: {
                                             title: "Descriptive function name derived from the user scenario",
                                             description: "Descriptive function name derived from the user scenario.\n\nThe function name serves as a concise, technical identifier that clearly\nrepresents the specific user scenario being described. It should be\nimmediately understandable and directly correspond to the user situation\nwithout requiring additional context.\n\n## Naming Convention\n\n- Must start with `test_` prefix (mandatory requirement)\n- Use snake_case formatting throughout\n- Include the primary user action (create, get, update, delete, list, etc.)\n- Specify the target resource (user, product, order, profile, etc.)\n- Add scenario-specific context (valid_data, invalid_email, not_found,\n  etc.)\n\n## Content Structure\n\nFunction names should follow this pattern:\n`test_[user_action]_[resource]_[scenario_context]`\n\nWhere:\n\n- `user_action`: What the user is trying to do\n- `resource`: What the user is interacting with\n- `scenario_context`: The specific situation or condition\n\n## User-Focused Examples\n\n- `test_create_user_profile_with_complete_information` - User providing all\n  available profile data\n- `test_retrieve_user_profile_when_profile_exists` - User accessing their\n  existing profile\n- `test_update_user_email_with_valid_new_address` - User changing their\n  email to a valid new one\n- `test_delete_user_account_when_user_lacks_permission` - User attempting\n  account deletion without authorization\n- `test_search_user_profiles_with_pagination_preferences` - User browsing\n  profiles with specific pagination\n\n## Clarity Guidelines\n\n- Prioritize clarity over brevity\n- Avoid technical jargon or implementation terms\n- Use terminology that reflects user perspective\n- Ensure the name alone conveys the user's intent\n- Make it understandable to non-technical stakeholders\n- Keep consistent with user scenario description\n\n## Single Endpoint Alignment\n\nFunction names must reflect scenarios that:\n\n- Accomplish user goals through this single endpoint only\n- Don't imply dependency on other API operations\n- Represent complete user interactions",
                                             type: "string"
                                         },
-                                        scenario: {
-                                            description: "Comprehensive user scenario description written from pure user\nperspective.\n\nThis describes a complete user journey, motivation, and expected outcome\nwhen interacting with the API endpoint. The description focuses entirely\non user intent, context, and natural behavior patterns rather than\ntechnical testing considerations.\n\n## User-Centric Writing Approach\n\n- Write as if describing a real person's experience and motivation\n- Focus on business context and user goals, not system functionality\n- Use natural language that business stakeholders would understand\n- Emphasize user value and expected benefits\n- Avoid technical terminology or implementation details\n\n## Required Content Elements\n\nEach scenario description must include:\n\n### 1. User Context and Motivation\n\n- Who is the user (role, background, current situation)\n- Why they need to perform this action (business motivation)\n- What problem they're trying to solve or goal they want to achieve\n- Any relevant background circumstances or constraints\n\n### 2. User Actions and Behavior\n\n- Specific steps the user takes to accomplish their goal\n- What information or data the user provides\n- How the user naturally approaches the interaction\n- Any decision-making process the user goes through\n\n### 3. User Expectations and Desired Outcomes\n\n- What the user expects to happen as a result\n- How the user will know if they were successful\n- What value or benefit the user expects to receive\n- How this fits into their broader workflow or objectives\n\n### 4. Business Impact and Value\n\n- How this scenario relates to business objectives\n- What business processes or workflows this supports\n- Why this user behavior matters to the organization\n- What risks or opportunities this scenario represents\n\n## Single Endpoint Constraint Integration\n\nEach scenario must:\n\n- Represent a complete user journey achievable through this single endpoint\n- Include all necessary context without referencing other API operations\n- Describe user expectations based solely on this endpoint's capabilities\n- Avoid scenarios that would logically require multiple API calls\n\n## Quality and Realism Standards\n\n- Base scenarios on realistic business situations\n- Include specific, concrete details rather than generic descriptions\n- Ensure scenarios reflect actual user behaviors and motivations\n- Make each scenario distinct and valuable for understanding user needs\n- Provide enough detail to understand full context without being verbose\n\n## User-Focused Example Scenarios\n\n- \"A busy project manager needs to quickly create a new team member's user\n  account during an onboarding meeting. They have all the necessary\n  information readily available and expect the account to be immediately\n  active so the new employee can start working right away.\"\n- \"A customer support representative is helping a customer who forgot their\n  login credentials. The customer provides their email address, and the\n  representative expects to quickly retrieve the associated account\n  information to assist with password recovery.\"\n- \"A system administrator discovers that a former employee's account is\n  still active after their departure. They need to immediately deactivate\n  this account for security purposes and expect confirmation that the\n  account can no longer be used to access company resources.\"\n\n## Language and Tone\n\n- Use active voice and present tense when describing user actions\n- Write in a narrative style that tells the user's story\n- Balance professional tone with human context\n- Ensure accessibility for both technical and non-technical readers\n- Maintain consistency in perspective throughout the description",
-                                            type: "string"
+                                        dependsOn: {
+                                            description: "A list of other API endpoints that must be executed before this test\nscenario. This helps express dependencies such as data creation or\nauthentication steps required to reach the intended test state.",
+                                            type: "array",
+                                            items: {
+                                                description: "Current Type: {@link IAutoBeTestScenarioApplication.IDependsOn}",
+                                                type: "object",
+                                                properties: {
+                                                    endpoint: {
+                                                        description: "Target API endpoint that must be executed before the main operation.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
+                                                        type: "object",
+                                                        properties: {
+                                                            path: {
+                                                                title: "HTTP path of the API operation",
+                                                                description: "HTTP path of the API operation.\n\nThe URL path for accessing this API operation, using path parameters\nenclosed in curly braces (e.g., `/shoppings/customers/sales/{saleId}`).\n\nIt must be corresponded to the {@link parameters path parameters}.\n\nThe path structure should clearly indicate which database entity this\noperation is manipulating, helping to ensure all entities have\nappropriate API coverage.",
+                                                                type: "string"
+                                                            },
+                                                            method: {
+                                                                title: "HTTP method of the API operation",
+                                                                description: "HTTP method of the API operation.\n\nNote that, if the API operation has {@link requestBody}, method must not\nbe `get`.\n\nAlso, even though the API operation has been designed to only get\ninformation, but it needs complicated request information, it must be\ndefined as `patch` method with {@link requestBody} data specification.\n\n- `get`: get information\n- `patch`: get information with complicated request data\n  ({@link requestBody})\n- `post`: create new record\n- `put`: update existing record\n- `delete`: remove record",
+                                                                oneOf: [ {
+                                                                    const: "get"
+                                                                }, {
+                                                                    const: "post"
+                                                                }, {
+                                                                    const: "put"
+                                                                }, {
+                                                                    const: "delete"
+                                                                }, {
+                                                                    const: "patch"
+                                                                } ]
+                                                            }
+                                                        },
+                                                        required: [ "path", "method" ]
+                                                    },
+                                                    purpose: {
+                                                        description: 'A concise exscenarioation of why this API call is required before\nexecuting the test for the main operation.\n\nExample: "Creates a category so that a product can be linked to it during\ncreation."',
+                                                        type: "string"
+                                                    }
+                                                },
+                                                required: [ "endpoint", "purpose" ]
+                                            }
                                         }
                                     },
-                                    required: [ "functionName", "scenario" ]
+                                    required: [ "draft", "functionName", "dependsOn" ]
                                 }
                             }
                         },
@@ -9925,32 +9831,33 @@ const claude$1 = {
                     }
                 }
             },
-            required: [ "scenarios" ],
+            required: [ "scenarioGroups" ],
             additionalProperties: false,
             $defs: {}
         },
-        description: "Make user scenarios for the given endpoints.",
+        description: "Make test scenarios for the given endpoints.",
         validate: (() => {
-            const _io0 = input => Array.isArray(input.scenarios) && input.scenarios.every((elem => "object" === typeof elem && null !== elem && _io1(elem)));
+            const _io0 = input => Array.isArray(input.scenarioGroups) && input.scenarioGroups.every((elem => "object" === typeof elem && null !== elem && _io1(elem)));
             const _io1 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && (Array.isArray(input.scenarios) && input.scenarios.every((elem => "object" === typeof elem && null !== elem && _io3(elem))));
             const _io2 = input => "string" === typeof input.path && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method);
-            const _io3 = input => "string" === typeof input.functionName && "string" === typeof input.scenario;
-            const _vo0 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.scenarios) || _report(_exceptionable, {
-                path: _path + ".scenarios",
-                expected: "Array<AutoBeTest.IScenario>",
-                value: input.scenarios
-            })) && input.scenarios.map(((elem, _index3) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                path: _path + ".scenarios[" + _index3 + "]",
-                expected: "AutoBeTest.IScenario",
+            const _io3 = input => "string" === typeof input.draft && "string" === typeof input.functionName && (Array.isArray(input.dependsOn) && input.dependsOn.every((elem => "object" === typeof elem && null !== elem && _io4(elem))));
+            const _io4 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && "string" === typeof input.purpose;
+            const _vo0 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.scenarioGroups) || _report(_exceptionable, {
+                path: _path + ".scenarioGroups",
+                expected: "Array<IAutoBeTestScenarioApplication.IScenarioGroup>",
+                value: input.scenarioGroups
+            })) && input.scenarioGroups.map(((elem, _index4) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                path: _path + ".scenarioGroups[" + _index4 + "]",
+                expected: "IAutoBeTestScenarioApplication.IScenarioGroup",
                 value: elem
-            })) && _vo1(elem, _path + ".scenarios[" + _index3 + "]", _exceptionable) || _report(_exceptionable, {
-                path: _path + ".scenarios[" + _index3 + "]",
-                expected: "AutoBeTest.IScenario",
+            })) && _vo1(elem, _path + ".scenarioGroups[" + _index4 + "]", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".scenarioGroups[" + _index4 + "]",
+                expected: "IAutoBeTestScenarioApplication.IScenarioGroup",
                 value: elem
             }))).every((flag => flag)) || _report(_exceptionable, {
-                path: _path + ".scenarios",
-                expected: "Array<AutoBeTest.IScenario>",
-                value: input.scenarios
+                path: _path + ".scenarioGroups",
+                expected: "Array<IAutoBeTestScenarioApplication.IScenarioGroup>",
+                value: input.scenarioGroups
             }) ].every((flag => flag));
             const _vo1 = (input, _path, _exceptionable = true) => [ ("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
                 path: _path + ".endpoint",
@@ -9962,19 +9869,19 @@ const claude$1 = {
                 value: input.endpoint
             }), (Array.isArray(input.scenarios) || _report(_exceptionable, {
                 path: _path + ".scenarios",
-                expected: "Array<AutoBeTest.Scenario>",
+                expected: "Array<IAutoBeTestScenarioApplication.IScenario>",
                 value: input.scenarios
-            })) && input.scenarios.map(((elem, _index4) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                path: _path + ".scenarios[" + _index4 + "]",
-                expected: "AutoBeTest.Scenario",
+            })) && input.scenarios.map(((elem, _index5) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                path: _path + ".scenarios[" + _index5 + "]",
+                expected: "IAutoBeTestScenarioApplication.IScenario",
                 value: elem
-            })) && _vo3(elem, _path + ".scenarios[" + _index4 + "]", _exceptionable) || _report(_exceptionable, {
-                path: _path + ".scenarios[" + _index4 + "]",
-                expected: "AutoBeTest.Scenario",
+            })) && _vo3(elem, _path + ".scenarios[" + _index5 + "]", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".scenarios[" + _index5 + "]",
+                expected: "IAutoBeTestScenarioApplication.IScenario",
                 value: elem
             }))).every((flag => flag)) || _report(_exceptionable, {
                 path: _path + ".scenarios",
-                expected: "Array<AutoBeTest.Scenario>",
+                expected: "Array<IAutoBeTestScenarioApplication.IScenario>",
                 value: input.scenarios
             }) ].every((flag => flag));
             const _vo2 = (input, _path, _exceptionable = true) => [ "string" === typeof input.path || _report(_exceptionable, {
@@ -9986,14 +9893,676 @@ const claude$1 = {
                 expected: '("delete" | "get" | "patch" | "post" | "put")',
                 value: input.method
             }) ].every((flag => flag));
-            const _vo3 = (input, _path, _exceptionable = true) => [ "string" === typeof input.functionName || _report(_exceptionable, {
+            const _vo3 = (input, _path, _exceptionable = true) => [ "string" === typeof input.draft || _report(_exceptionable, {
+                path: _path + ".draft",
+                expected: "string",
+                value: input.draft
+            }), "string" === typeof input.functionName || _report(_exceptionable, {
                 path: _path + ".functionName",
                 expected: "string",
                 value: input.functionName
-            }), "string" === typeof input.scenario || _report(_exceptionable, {
+            }), (Array.isArray(input.dependsOn) || _report(_exceptionable, {
+                path: _path + ".dependsOn",
+                expected: "Array<IAutoBeTestScenarioApplication.IDependsOn>",
+                value: input.dependsOn
+            })) && input.dependsOn.map(((elem, _index6) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                path: _path + ".dependsOn[" + _index6 + "]",
+                expected: "IAutoBeTestScenarioApplication.IDependsOn",
+                value: elem
+            })) && _vo4(elem, _path + ".dependsOn[" + _index6 + "]", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".dependsOn[" + _index6 + "]",
+                expected: "IAutoBeTestScenarioApplication.IDependsOn",
+                value: elem
+            }))).every((flag => flag)) || _report(_exceptionable, {
+                path: _path + ".dependsOn",
+                expected: "Array<IAutoBeTestScenarioApplication.IDependsOn>",
+                value: input.dependsOn
+            }) ].every((flag => flag));
+            const _vo4 = (input, _path, _exceptionable = true) => [ ("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
+                path: _path + ".endpoint",
+                expected: "AutoBeOpenApi.IEndpoint",
+                value: input.endpoint
+            })) && _vo2(input.endpoint, _path + ".endpoint", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".endpoint",
+                expected: "AutoBeOpenApi.IEndpoint",
+                value: input.endpoint
+            }), "string" === typeof input.purpose || _report(_exceptionable, {
+                path: _path + ".purpose",
+                expected: "string",
+                value: input.purpose
+            }) ].every((flag => flag));
+            const __is = input => "object" === typeof input && null !== input && _io0(input);
+            let errors;
+            let _report;
+            return input => {
+                if (false === __is(input)) {
+                    errors = [];
+                    _report = __typia_transform__validateReport._validateReport(errors);
+                    ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
+                        path: _path + "",
+                        expected: "IAutoBeTestScenarioApplication.IProps",
+                        value: input
+                    })) && _vo0(input, _path + "", true) || _report(true, {
+                        path: _path + "",
+                        expected: "IAutoBeTestScenarioApplication.IProps",
+                        value: input
+                    }))(input, "$input", true);
+                    const success = 0 === errors.length;
+                    return success ? {
+                        success,
+                        data: input
+                    } : {
+                        success,
+                        errors,
+                        data: input
+                    };
+                }
+                return {
+                    success: true,
+                    data: input
+                };
+            };
+        })()
+    } ]
+};
+
+const collection$2 = {
+    chatgpt: {
+        model: "chatgpt",
+        options: {
+            reference: true,
+            strict: false,
+            separate: null
+        },
+        functions: [ {
+            name: "makeScenario",
+            parameters: {
+                description: " Properties containing the endpoints and test scenarios.\n\n------------------------------\n\nCurrent Type: {@link IAutoBeTestScenarioApplication.IProps}",
+                type: "object",
+                properties: {
+                    scenarioGroups: {
+                        title: "Array of test scenario groups",
+                        description: "Array of test scenario groups.",
+                        type: "array",
+                        items: {
+                            description: "Current Type: {@link IAutoBeTestScenarioApplication.IScenarioGroup}",
+                            type: "object",
+                            properties: {
+                                endpoint: {
+                                    description: "Target API endpoint to test.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
+                                    type: "object",
+                                    properties: {
+                                        path: {
+                                            title: "HTTP path of the API operation",
+                                            description: "HTTP path of the API operation.\n\nThe URL path for accessing this API operation, using path parameters\nenclosed in curly braces (e.g., `/shoppings/customers/sales/{saleId}`).\n\nIt must be corresponded to the {@link parameters path parameters}.\n\nThe path structure should clearly indicate which database entity this\noperation is manipulating, helping to ensure all entities have\nappropriate API coverage.",
+                                            type: "string"
+                                        },
+                                        method: {
+                                            title: "HTTP method of the API operation",
+                                            description: "HTTP method of the API operation.\n\nNote that, if the API operation has {@link requestBody}, method must not\nbe `get`.\n\nAlso, even though the API operation has been designed to only get\ninformation, but it needs complicated request information, it must be\ndefined as `patch` method with {@link requestBody} data specification.\n\n- `get`: get information\n- `patch`: get information with complicated request data\n  ({@link requestBody})\n- `post`: create new record\n- `put`: update existing record\n- `delete`: remove record",
+                                            type: "string",
+                                            enum: [ "get", "post", "put", "delete", "patch" ]
+                                        }
+                                    },
+                                    required: [ "path", "method" ]
+                                },
+                                scenarios: {
+                                    title: "Array of test scenarios",
+                                    description: "Array of test scenarios.",
+                                    type: "array",
+                                    items: {
+                                        description: "Description of the current {@link IAutoBeTestScenarioApplication.IScenario} type:\n\n> Represents a test scenario for a single API operation.\n> \n> This interface extends `AutoBeOpenApi.IEndpoint`, inheriting its HTTP\n> method and path information, and adds two key properties:\n> \n> - `draft`: A free-form, human-readable test scenario description for the API\n>   endpoint.\n> - `dependsOn`: A list of other API endpoints that must be invoked beforehand\n>   in order to prepare the context for this test. Each dependency includes\n>   the purpose of the dependency.\n> \n> This structure is intended to help organize test specifications for complex\n> workflows and ensure that all prerequisites are explicitly declared.",
+                                        type: "object",
+                                        properties: {
+                                            draft: {
+                                                description: "A detailed natural language description of how this API endpoint should\nbe tested. This should include both successful and failure scenarios,\nbusiness rule validations, edge cases, and any sequence of steps\nnecessary to perform the test. A subsequent agent will use this draft to\ngenerate multiple test scenarios.",
+                                                type: "string"
+                                            },
+                                            functionName: {
+                                                title: "Descriptive function name derived from the user scenario",
+                                                description: "Descriptive function name derived from the user scenario.\n\nThe function name serves as a concise, technical identifier that clearly\nrepresents the specific user scenario being described. It should be\nimmediately understandable and directly correspond to the user situation\nwithout requiring additional context.\n\n## Naming Convention\n\n- Must start with `test_` prefix (mandatory requirement)\n- Use snake_case formatting throughout\n- Include the primary user action (create, get, update, delete, list, etc.)\n- Specify the target resource (user, product, order, profile, etc.)\n- Add scenario-specific context (valid_data, invalid_email, not_found,\n  etc.)\n\n## Content Structure\n\nFunction names should follow this pattern:\n`test_[user_action]_[resource]_[scenario_context]`\n\nWhere:\n\n- `user_action`: What the user is trying to do\n- `resource`: What the user is interacting with\n- `scenario_context`: The specific situation or condition\n\n## User-Focused Examples\n\n- `test_create_user_profile_with_complete_information` - User providing all\n  available profile data\n- `test_retrieve_user_profile_when_profile_exists` - User accessing their\n  existing profile\n- `test_update_user_email_with_valid_new_address` - User changing their\n  email to a valid new one\n- `test_delete_user_account_when_user_lacks_permission` - User attempting\n  account deletion without authorization\n- `test_search_user_profiles_with_pagination_preferences` - User browsing\n  profiles with specific pagination\n\n## Clarity Guidelines\n\n- Prioritize clarity over brevity\n- Avoid technical jargon or implementation terms\n- Use terminology that reflects user perspective\n- Ensure the name alone conveys the user's intent\n- Make it understandable to non-technical stakeholders\n- Keep consistent with user scenario description\n\n## Single Endpoint Alignment\n\nFunction names must reflect scenarios that:\n\n- Accomplish user goals through this single endpoint only\n- Don't imply dependency on other API operations\n- Represent complete user interactions",
+                                                type: "string"
+                                            },
+                                            dependsOn: {
+                                                description: "A list of other API endpoints that must be executed before this test\nscenario. This helps express dependencies such as data creation or\nauthentication steps required to reach the intended test state.",
+                                                type: "array",
+                                                items: {
+                                                    description: "Current Type: {@link IAutoBeTestScenarioApplication.IDependsOn}",
+                                                    type: "object",
+                                                    properties: {
+                                                        endpoint: {
+                                                            description: "Target API endpoint that must be executed before the main operation.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
+                                                            type: "object",
+                                                            properties: {
+                                                                path: {
+                                                                    title: "HTTP path of the API operation",
+                                                                    description: "HTTP path of the API operation.\n\nThe URL path for accessing this API operation, using path parameters\nenclosed in curly braces (e.g., `/shoppings/customers/sales/{saleId}`).\n\nIt must be corresponded to the {@link parameters path parameters}.\n\nThe path structure should clearly indicate which database entity this\noperation is manipulating, helping to ensure all entities have\nappropriate API coverage.",
+                                                                    type: "string"
+                                                                },
+                                                                method: {
+                                                                    title: "HTTP method of the API operation",
+                                                                    description: "HTTP method of the API operation.\n\nNote that, if the API operation has {@link requestBody}, method must not\nbe `get`.\n\nAlso, even though the API operation has been designed to only get\ninformation, but it needs complicated request information, it must be\ndefined as `patch` method with {@link requestBody} data specification.\n\n- `get`: get information\n- `patch`: get information with complicated request data\n  ({@link requestBody})\n- `post`: create new record\n- `put`: update existing record\n- `delete`: remove record",
+                                                                    type: "string",
+                                                                    enum: [ "get", "post", "put", "delete", "patch" ]
+                                                                }
+                                                            },
+                                                            required: [ "path", "method" ]
+                                                        },
+                                                        purpose: {
+                                                            description: 'A concise exscenarioation of why this API call is required before\nexecuting the test for the main operation.\n\nExample: "Creates a category so that a product can be linked to it during\ncreation."',
+                                                            type: "string"
+                                                        }
+                                                    },
+                                                    required: [ "endpoint", "purpose" ]
+                                                }
+                                            }
+                                        },
+                                        required: [ "draft", "functionName", "dependsOn" ]
+                                    }
+                                }
+                            },
+                            required: [ "endpoint", "scenarios" ]
+                        }
+                    }
+                },
+                required: [ "scenarioGroups" ],
+                additionalProperties: false,
+                $defs: {}
+            },
+            description: "Make test scenarios for the given endpoints.",
+            validate: (() => {
+                const _io0 = input => Array.isArray(input.scenarioGroups) && input.scenarioGroups.every((elem => "object" === typeof elem && null !== elem && _io1(elem)));
+                const _io1 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && (Array.isArray(input.scenarios) && input.scenarios.every((elem => "object" === typeof elem && null !== elem && _io3(elem))));
+                const _io2 = input => "string" === typeof input.path && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method);
+                const _io3 = input => "string" === typeof input.draft && "string" === typeof input.functionName && (Array.isArray(input.dependsOn) && input.dependsOn.every((elem => "object" === typeof elem && null !== elem && _io4(elem))));
+                const _io4 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && "string" === typeof input.purpose;
+                const _vo0 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.scenarioGroups) || _report(_exceptionable, {
+                    path: _path + ".scenarioGroups",
+                    expected: "Array<IAutoBeTestScenarioApplication.IScenarioGroup>",
+                    value: input.scenarioGroups
+                })) && input.scenarioGroups.map(((elem, _index4) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".scenarioGroups[" + _index4 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IScenarioGroup",
+                    value: elem
+                })) && _vo1(elem, _path + ".scenarioGroups[" + _index4 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".scenarioGroups[" + _index4 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IScenarioGroup",
+                    value: elem
+                }))).every((flag => flag)) || _report(_exceptionable, {
+                    path: _path + ".scenarioGroups",
+                    expected: "Array<IAutoBeTestScenarioApplication.IScenarioGroup>",
+                    value: input.scenarioGroups
+                }) ].every((flag => flag));
+                const _vo1 = (input, _path, _exceptionable = true) => [ ("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
+                    path: _path + ".endpoint",
+                    expected: "AutoBeOpenApi.IEndpoint",
+                    value: input.endpoint
+                })) && _vo2(input.endpoint, _path + ".endpoint", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".endpoint",
+                    expected: "AutoBeOpenApi.IEndpoint",
+                    value: input.endpoint
+                }), (Array.isArray(input.scenarios) || _report(_exceptionable, {
+                    path: _path + ".scenarios",
+                    expected: "Array<IAutoBeTestScenarioApplication.IScenario>",
+                    value: input.scenarios
+                })) && input.scenarios.map(((elem, _index5) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".scenarios[" + _index5 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IScenario",
+                    value: elem
+                })) && _vo3(elem, _path + ".scenarios[" + _index5 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".scenarios[" + _index5 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IScenario",
+                    value: elem
+                }))).every((flag => flag)) || _report(_exceptionable, {
+                    path: _path + ".scenarios",
+                    expected: "Array<IAutoBeTestScenarioApplication.IScenario>",
+                    value: input.scenarios
+                }) ].every((flag => flag));
+                const _vo2 = (input, _path, _exceptionable = true) => [ "string" === typeof input.path || _report(_exceptionable, {
+                    path: _path + ".path",
+                    expected: "string",
+                    value: input.path
+                }), "get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method || _report(_exceptionable, {
+                    path: _path + ".method",
+                    expected: '("delete" | "get" | "patch" | "post" | "put")',
+                    value: input.method
+                }) ].every((flag => flag));
+                const _vo3 = (input, _path, _exceptionable = true) => [ "string" === typeof input.draft || _report(_exceptionable, {
+                    path: _path + ".draft",
+                    expected: "string",
+                    value: input.draft
+                }), "string" === typeof input.functionName || _report(_exceptionable, {
+                    path: _path + ".functionName",
+                    expected: "string",
+                    value: input.functionName
+                }), (Array.isArray(input.dependsOn) || _report(_exceptionable, {
+                    path: _path + ".dependsOn",
+                    expected: "Array<IAutoBeTestScenarioApplication.IDependsOn>",
+                    value: input.dependsOn
+                })) && input.dependsOn.map(((elem, _index6) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".dependsOn[" + _index6 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IDependsOn",
+                    value: elem
+                })) && _vo4(elem, _path + ".dependsOn[" + _index6 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".dependsOn[" + _index6 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IDependsOn",
+                    value: elem
+                }))).every((flag => flag)) || _report(_exceptionable, {
+                    path: _path + ".dependsOn",
+                    expected: "Array<IAutoBeTestScenarioApplication.IDependsOn>",
+                    value: input.dependsOn
+                }) ].every((flag => flag));
+                const _vo4 = (input, _path, _exceptionable = true) => [ ("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
+                    path: _path + ".endpoint",
+                    expected: "AutoBeOpenApi.IEndpoint",
+                    value: input.endpoint
+                })) && _vo2(input.endpoint, _path + ".endpoint", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".endpoint",
+                    expected: "AutoBeOpenApi.IEndpoint",
+                    value: input.endpoint
+                }), "string" === typeof input.purpose || _report(_exceptionable, {
+                    path: _path + ".purpose",
+                    expected: "string",
+                    value: input.purpose
+                }) ].every((flag => flag));
+                const __is = input => "object" === typeof input && null !== input && _io0(input);
+                let errors;
+                let _report;
+                return input => {
+                    if (false === __is(input)) {
+                        errors = [];
+                        _report = __typia_transform__validateReport._validateReport(errors);
+                        ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
+                            path: _path + "",
+                            expected: "IAutoBeTestScenarioApplication.IProps",
+                            value: input
+                        })) && _vo0(input, _path + "", true) || _report(true, {
+                            path: _path + "",
+                            expected: "IAutoBeTestScenarioApplication.IProps",
+                            value: input
+                        }))(input, "$input", true);
+                        const success = 0 === errors.length;
+                        return success ? {
+                            success,
+                            data: input
+                        } : {
+                            success,
+                            errors,
+                            data: input
+                        };
+                    }
+                    return {
+                        success: true,
+                        data: input
+                    };
+                };
+            })()
+        } ]
+    },
+    claude: claude$2,
+    llama: claude$2,
+    deepseek: claude$2,
+    3.1: claude$2,
+    "3.0": {
+        model: "3.0",
+        options: {
+            constraint: true,
+            recursive: 3,
+            separate: null
+        },
+        functions: [ {
+            name: "makeScenario",
+            parameters: {
+                type: "object",
+                properties: {
+                    scenarioGroups: {
+                        type: "array",
+                        items: {
+                            type: "object",
+                            properties: {
+                                endpoint: {
+                                    type: "object",
+                                    properties: {
+                                        path: {
+                                            type: "string",
+                                            title: "HTTP path of the API operation",
+                                            description: "HTTP path of the API operation.\n\nThe URL path for accessing this API operation, using path parameters\nenclosed in curly braces (e.g., `/shoppings/customers/sales/{saleId}`).\n\nIt must be corresponded to the {@link parameters path parameters}.\n\nThe path structure should clearly indicate which database entity this\noperation is manipulating, helping to ensure all entities have\nappropriate API coverage."
+                                        },
+                                        method: {
+                                            type: "string",
+                                            enum: [ "get", "post", "put", "delete", "patch" ],
+                                            title: "HTTP method of the API operation",
+                                            description: "HTTP method of the API operation.\n\nNote that, if the API operation has {@link requestBody}, method must not\nbe `get`.\n\nAlso, even though the API operation has been designed to only get\ninformation, but it needs complicated request information, it must be\ndefined as `patch` method with {@link requestBody} data specification.\n\n- `get`: get information\n- `patch`: get information with complicated request data\n  ({@link requestBody})\n- `post`: create new record\n- `put`: update existing record\n- `delete`: remove record"
+                                        }
+                                    },
+                                    required: [ "path", "method" ],
+                                    description: "Target API endpoint to test.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
+                                    additionalProperties: false
+                                },
+                                scenarios: {
+                                    type: "array",
+                                    items: {
+                                        type: "object",
+                                        properties: {
+                                            draft: {
+                                                type: "string",
+                                                description: "A detailed natural language description of how this API endpoint should\nbe tested. This should include both successful and failure scenarios,\nbusiness rule validations, edge cases, and any sequence of steps\nnecessary to perform the test. A subsequent agent will use this draft to\ngenerate multiple test scenarios."
+                                            },
+                                            functionName: {
+                                                type: "string",
+                                                title: "Descriptive function name derived from the user scenario",
+                                                description: "Descriptive function name derived from the user scenario.\n\nThe function name serves as a concise, technical identifier that clearly\nrepresents the specific user scenario being described. It should be\nimmediately understandable and directly correspond to the user situation\nwithout requiring additional context.\n\n## Naming Convention\n\n- Must start with `test_` prefix (mandatory requirement)\n- Use snake_case formatting throughout\n- Include the primary user action (create, get, update, delete, list, etc.)\n- Specify the target resource (user, product, order, profile, etc.)\n- Add scenario-specific context (valid_data, invalid_email, not_found,\n  etc.)\n\n## Content Structure\n\nFunction names should follow this pattern:\n`test_[user_action]_[resource]_[scenario_context]`\n\nWhere:\n\n- `user_action`: What the user is trying to do\n- `resource`: What the user is interacting with\n- `scenario_context`: The specific situation or condition\n\n## User-Focused Examples\n\n- `test_create_user_profile_with_complete_information` - User providing all\n  available profile data\n- `test_retrieve_user_profile_when_profile_exists` - User accessing their\n  existing profile\n- `test_update_user_email_with_valid_new_address` - User changing their\n  email to a valid new one\n- `test_delete_user_account_when_user_lacks_permission` - User attempting\n  account deletion without authorization\n- `test_search_user_profiles_with_pagination_preferences` - User browsing\n  profiles with specific pagination\n\n## Clarity Guidelines\n\n- Prioritize clarity over brevity\n- Avoid technical jargon or implementation terms\n- Use terminology that reflects user perspective\n- Ensure the name alone conveys the user's intent\n- Make it understandable to non-technical stakeholders\n- Keep consistent with user scenario description\n\n## Single Endpoint Alignment\n\nFunction names must reflect scenarios that:\n\n- Accomplish user goals through this single endpoint only\n- Don't imply dependency on other API operations\n- Represent complete user interactions"
+                                            },
+                                            dependsOn: {
+                                                type: "array",
+                                                items: {
+                                                    type: "object",
+                                                    properties: {
+                                                        endpoint: {
+                                                            type: "object",
+                                                            properties: {
+                                                                path: {
+                                                                    type: "string",
+                                                                    title: "HTTP path of the API operation",
+                                                                    description: "HTTP path of the API operation.\n\nThe URL path for accessing this API operation, using path parameters\nenclosed in curly braces (e.g., `/shoppings/customers/sales/{saleId}`).\n\nIt must be corresponded to the {@link parameters path parameters}.\n\nThe path structure should clearly indicate which database entity this\noperation is manipulating, helping to ensure all entities have\nappropriate API coverage."
+                                                                },
+                                                                method: {
+                                                                    type: "string",
+                                                                    enum: [ "get", "post", "put", "delete", "patch" ],
+                                                                    title: "HTTP method of the API operation",
+                                                                    description: "HTTP method of the API operation.\n\nNote that, if the API operation has {@link requestBody}, method must not\nbe `get`.\n\nAlso, even though the API operation has been designed to only get\ninformation, but it needs complicated request information, it must be\ndefined as `patch` method with {@link requestBody} data specification.\n\n- `get`: get information\n- `patch`: get information with complicated request data\n  ({@link requestBody})\n- `post`: create new record\n- `put`: update existing record\n- `delete`: remove record"
+                                                                }
+                                                            },
+                                                            required: [ "path", "method" ],
+                                                            description: "Target API endpoint that must be executed before the main operation.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
+                                                            additionalProperties: false
+                                                        },
+                                                        purpose: {
+                                                            type: "string",
+                                                            description: 'A concise exscenarioation of why this API call is required before\nexecuting the test for the main operation.\n\nExample: "Creates a category so that a product can be linked to it during\ncreation."'
+                                                        }
+                                                    },
+                                                    required: [ "endpoint", "purpose" ],
+                                                    description: "Current Type: {@link IAutoBeTestScenarioApplication.IDependsOn}",
+                                                    additionalProperties: false
+                                                },
+                                                description: "A list of other API endpoints that must be executed before this test\nscenario. This helps express dependencies such as data creation or\nauthentication steps required to reach the intended test state."
+                                            }
+                                        },
+                                        required: [ "draft", "functionName", "dependsOn" ],
+                                        description: "Description of the current {@link IAutoBeTestScenarioApplication.IScenario} type:\n\n> Represents a test scenario for a single API operation.\n> \n> This interface extends `AutoBeOpenApi.IEndpoint`, inheriting its HTTP\n> method and path information, and adds two key properties:\n> \n> - `draft`: A free-form, human-readable test scenario description for the API\n>   endpoint.\n> - `dependsOn`: A list of other API endpoints that must be invoked beforehand\n>   in order to prepare the context for this test. Each dependency includes\n>   the purpose of the dependency.\n> \n> This structure is intended to help organize test specifications for complex\n> workflows and ensure that all prerequisites are explicitly declared.",
+                                        additionalProperties: false
+                                    },
+                                    title: "Array of test scenarios",
+                                    description: "Array of test scenarios."
+                                }
+                            },
+                            required: [ "endpoint", "scenarios" ],
+                            description: "Current Type: {@link IAutoBeTestScenarioApplication.IScenarioGroup}",
+                            additionalProperties: false
+                        },
+                        title: "Array of test scenario groups",
+                        description: "Array of test scenario groups."
+                    }
+                },
+                required: [ "scenarioGroups" ],
+                description: " Properties containing the endpoints and test scenarios.\n\n------------------------------\n\nCurrent Type: {@link IAutoBeTestScenarioApplication.IProps}",
+                additionalProperties: false
+            },
+            description: "Make test scenarios for the given endpoints.",
+            validate: (() => {
+                const _io0 = input => Array.isArray(input.scenarioGroups) && input.scenarioGroups.every((elem => "object" === typeof elem && null !== elem && _io1(elem)));
+                const _io1 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && (Array.isArray(input.scenarios) && input.scenarios.every((elem => "object" === typeof elem && null !== elem && _io3(elem))));
+                const _io2 = input => "string" === typeof input.path && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method);
+                const _io3 = input => "string" === typeof input.draft && "string" === typeof input.functionName && (Array.isArray(input.dependsOn) && input.dependsOn.every((elem => "object" === typeof elem && null !== elem && _io4(elem))));
+                const _io4 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && "string" === typeof input.purpose;
+                const _vo0 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.scenarioGroups) || _report(_exceptionable, {
+                    path: _path + ".scenarioGroups",
+                    expected: "Array<IAutoBeTestScenarioApplication.IScenarioGroup>",
+                    value: input.scenarioGroups
+                })) && input.scenarioGroups.map(((elem, _index4) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".scenarioGroups[" + _index4 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IScenarioGroup",
+                    value: elem
+                })) && _vo1(elem, _path + ".scenarioGroups[" + _index4 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".scenarioGroups[" + _index4 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IScenarioGroup",
+                    value: elem
+                }))).every((flag => flag)) || _report(_exceptionable, {
+                    path: _path + ".scenarioGroups",
+                    expected: "Array<IAutoBeTestScenarioApplication.IScenarioGroup>",
+                    value: input.scenarioGroups
+                }) ].every((flag => flag));
+                const _vo1 = (input, _path, _exceptionable = true) => [ ("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
+                    path: _path + ".endpoint",
+                    expected: "AutoBeOpenApi.IEndpoint",
+                    value: input.endpoint
+                })) && _vo2(input.endpoint, _path + ".endpoint", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".endpoint",
+                    expected: "AutoBeOpenApi.IEndpoint",
+                    value: input.endpoint
+                }), (Array.isArray(input.scenarios) || _report(_exceptionable, {
+                    path: _path + ".scenarios",
+                    expected: "Array<IAutoBeTestScenarioApplication.IScenario>",
+                    value: input.scenarios
+                })) && input.scenarios.map(((elem, _index5) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".scenarios[" + _index5 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IScenario",
+                    value: elem
+                })) && _vo3(elem, _path + ".scenarios[" + _index5 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".scenarios[" + _index5 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IScenario",
+                    value: elem
+                }))).every((flag => flag)) || _report(_exceptionable, {
+                    path: _path + ".scenarios",
+                    expected: "Array<IAutoBeTestScenarioApplication.IScenario>",
+                    value: input.scenarios
+                }) ].every((flag => flag));
+                const _vo2 = (input, _path, _exceptionable = true) => [ "string" === typeof input.path || _report(_exceptionable, {
+                    path: _path + ".path",
+                    expected: "string",
+                    value: input.path
+                }), "get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method || _report(_exceptionable, {
+                    path: _path + ".method",
+                    expected: '("delete" | "get" | "patch" | "post" | "put")',
+                    value: input.method
+                }) ].every((flag => flag));
+                const _vo3 = (input, _path, _exceptionable = true) => [ "string" === typeof input.draft || _report(_exceptionable, {
+                    path: _path + ".draft",
+                    expected: "string",
+                    value: input.draft
+                }), "string" === typeof input.functionName || _report(_exceptionable, {
+                    path: _path + ".functionName",
+                    expected: "string",
+                    value: input.functionName
+                }), (Array.isArray(input.dependsOn) || _report(_exceptionable, {
+                    path: _path + ".dependsOn",
+                    expected: "Array<IAutoBeTestScenarioApplication.IDependsOn>",
+                    value: input.dependsOn
+                })) && input.dependsOn.map(((elem, _index6) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".dependsOn[" + _index6 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IDependsOn",
+                    value: elem
+                })) && _vo4(elem, _path + ".dependsOn[" + _index6 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".dependsOn[" + _index6 + "]",
+                    expected: "IAutoBeTestScenarioApplication.IDependsOn",
+                    value: elem
+                }))).every((flag => flag)) || _report(_exceptionable, {
+                    path: _path + ".dependsOn",
+                    expected: "Array<IAutoBeTestScenarioApplication.IDependsOn>",
+                    value: input.dependsOn
+                }) ].every((flag => flag));
+                const _vo4 = (input, _path, _exceptionable = true) => [ ("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
+                    path: _path + ".endpoint",
+                    expected: "AutoBeOpenApi.IEndpoint",
+                    value: input.endpoint
+                })) && _vo2(input.endpoint, _path + ".endpoint", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".endpoint",
+                    expected: "AutoBeOpenApi.IEndpoint",
+                    value: input.endpoint
+                }), "string" === typeof input.purpose || _report(_exceptionable, {
+                    path: _path + ".purpose",
+                    expected: "string",
+                    value: input.purpose
+                }) ].every((flag => flag));
+                const __is = input => "object" === typeof input && null !== input && _io0(input);
+                let errors;
+                let _report;
+                return input => {
+                    if (false === __is(input)) {
+                        errors = [];
+                        _report = __typia_transform__validateReport._validateReport(errors);
+                        ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
+                            path: _path + "",
+                            expected: "IAutoBeTestScenarioApplication.IProps",
+                            value: input
+                        })) && _vo0(input, _path + "", true) || _report(true, {
+                            path: _path + "",
+                            expected: "IAutoBeTestScenarioApplication.IProps",
+                            value: input
+                        }))(input, "$input", true);
+                        const success = 0 === errors.length;
+                        return success ? {
+                            success,
+                            data: input
+                        } : {
+                            success,
+                            errors,
+                            data: input
+                        };
+                    }
+                    return {
+                        success: true,
+                        data: input
+                    };
+                };
+            })()
+        } ]
+    }
+};
+
+const transformTestWriteHistories = props => [ {
+    id: v4(),
+    created_at: (new Date).toISOString(),
+    type: "systemMessage",
+    text: '# E2E Test Function Writing AI Agent System Prompt\n\n## 1. Overview\n\nYou are a specialized AI Agent for writing E2E test functions targeting backend server APIs. Your core mission is to generate complete and accurate E2E test code based on provided test scenarios, DTO definitions, SDK libraries, and mock functions.\n\nYou will receive 4 types of input materials: (1) Test scenarios to be executed (2) TypeScript DTO definition files (3) Type-safe SDK library (4) Mock functions filled with random data. Based on these materials, you must write E2E tests that completely reproduce actual business flows. In particular, you must precisely analyze API functions and DTO types to discover and implement essential steps not explicitly mentioned in scenarios.\n\nDuring the writing process, you must adhere to 5 core principles: implement all scenario steps in order without omission, write complete JSDoc-style comments, follow consistent function naming conventions, use only the provided SDK for API calls, and perform type validation on all responses.\n\nThe final deliverable must be a complete E2E test function ready for use in production environments, satisfying code completeness, readability, and maintainability. You must prioritize completeness over efficiency, implementing all steps specified in scenarios without omission, even for complex and lengthy processes.\n\n## 2. Input Material Composition\n\nThe Agent will receive the following 4 core input materials and must perform deep analysis and understanding beyond superficial reading. Rather than simply following given scenarios, you must identify the interrelationships among all input materials and discover potential requirements.\n\n### 2.1. Test Scenarios\n- Test scenarios written in narrative form by AI after analyzing API functions and their definitions\n- Include prerequisite principles and execution order that test functions **must** follow\n- Specify complex business flows step by step, with each step being **non-omittable**\n\n**Deep Analysis Requirements:**\n- **Business Context Understanding**: Grasp why each step is necessary and what meaning it has in actual user scenarios\n- **Implicit Prerequisite Discovery**: Identify intermediate steps that are not explicitly mentioned in scenarios but are naturally necessary (e.g., login session maintenance, data state transitions)\n- **Dependency Relationship Mapping**: Track how data generated in each step is used in subsequent steps\n- **Exception Consideration**: Anticipate errors or exceptional cases that may occur in each step\n- **Business Rule Inference**: Understand domain-specific business rules and constraints hidden in scenario backgrounds\n\n**Scenario Example:**\n```\nValidate the modification of review posts.\n\nHowever, the fact that customers can write review posts in a shopping mall means that the customer has already joined the shopping mall, completed product purchase and payment, and the seller has completed delivery.\n\nTherefore, in this test function, all of these must be carried out, so before writing a review post, all of the following preliminary tasks must be performed. It will be quite a long process.\n\n1. Seller signs up\n2. Seller registers a product\n3. Customer signs up\n4. Customer views the product in detail\n5. Customer adds the product to shopping cart\n6. Customer places a purchase order\n7. Customer confirms purchase and makes payment\n8. Seller confirms order and processes delivery\n9. Customer writes a review post\n10. Customer modifies the review post\n11. Re-view the review post to confirm modifications.\n```\n\n### 2.2. DTO (Data Transfer Object) Definition Files\n- Data transfer objects composed of TypeScript type definitions\n- Include all type information used in API requests/responses\n- Support nested namespace and interface structures, utilizing `typia` tags\n\n**Deep Analysis Requirements:**\n- **Type Constraint Analysis**: Complete understanding of validation rules like `tags.Format<"uuid">`, `tags.MinItems<1>`, `tags.Minimum<0>`\n- **Interface Inheritance Relationship Analysis**: Analyze relationships between types through `extends`, `Partial<>`, `Omit<>`\n- **Namespace Structure Exploration**: Understand the purpose and usage timing of nested types like `ICreate`, `IUpdate`, `ISnapshot`\n- **Required/Optional Field Distinction**: Understand which fields are required and optional, and their respective business meanings\n- **Data Transformation Pattern Identification**: Track data lifecycle like Create → Entity → Update → Snapshot\n- **Type Safety Requirements**: Understand exact type matching and validation logic required by each API\n\n**DTO Example:**\n```typescript\nimport { tags } from "typia";\n\nimport { IAttachmentFile } from "../../../common/IAttachmentFile";\nimport { IShoppingCustomer } from "../../actors/IShoppingCustomer";\nimport { IShoppingSaleInquiry } from "./IShoppingSaleInquiry";\nimport { IShoppingSaleInquiryAnswer } from "./IShoppingSaleInquiryAnswer";\n\n/**\n * Reviews for sale snapshots.\n *\n * `IShoppingSaleReview` is a subtype entity of {@link IShoppingSaleInquiry},\n * and is used when a {@link IShoppingCustomer customer} purchases a\n * {@link IShoppingSale sale} ({@link IShoppingSaleSnapshot snapshot} at the time)\n * registered by the {@link IShoppingSeller seller} as a product and leaves a\n * review and rating for it.\n *\n * For reference, `IShoppingSaleReview` and\n * {@link IShoppingOrderGod shopping_order_goods} have a logarithmic relationship\n * of N: 1, but this does not mean that customers can continue to write reviews\n * for the same product indefinitely. Wouldn\'t there be restrictions, such as\n * if you write a review once, you can write an additional review a month later?\n *\n * @author Samchon\n */\nexport interface IShoppingSaleReview {\n  /**\n   * Primary Key.\n   */\n  id: string & tags.Format<"uuid">;\n\n  /**\n   * Discriminator type.\n   */\n  type: "review";\n\n  /**\n   * Customer who wrote the inquiry.\n   */\n  customer: IShoppingCustomer;\n\n  /**\n   * Formal answer for the inquiry by the seller.\n   */\n  answer: null | IShoppingSaleInquiryAnswer;\n\n  /**\n   * Whether the seller has viewed the inquiry or not.\n   */\n  read_by_seller: boolean;\n\n  /**\n   * List of snapshot contents.\n   *\n   * It is created for the first time when an article is created, and is\n   * accumulated every time the article is modified.\n   */\n  snapshots: IShoppingSaleReview.ISnapshot[] & tags.MinItems<1>;\n\n  /**\n   * Creation time of article.\n   */\n  created_at: string & tags.Format<"date-time">;\n}\nexport namespace IShoppingSaleReview {\n  /**\n   * Snapshot content of the review article.\n   */\n  export interface ISnapshot extends ICreate {\n    /**\n     * Primary Key.\n     */\n    id: string;\n\n    /**\n     * Creation time of snapshot record.\n     *\n     * In other words, creation time or update time or article.\n     */\n    created_at: string & tags.Format<"date-time">;\n  }\n\n  /**\n   * Creation information of the review.\n   */\n  export interface ICreate {\n    /**\n     * Format of body.\n     *\n     * Same meaning with extension like `html`, `md`, `txt`.\n     */\n    format: "html" | "md" | "txt";\n\n    /**\n     * Title of article.\n     */\n    title: string;\n\n    /**\n     * Content body of article.\n     */\n    body: string;\n\n    /**\n     * List of attachment files.\n     */\n    files: IAttachmentFile.ICreate[];\n\n    /**\n     * Target good\'s {@link IShoppingOrderGood.id}.\n     */\n    good_id: string & tags.Format<"uuid">;\n\n    /**\n     * Score of the review.\n     */\n    score: number & tags.Minimum<0> & tags.Maximum<100>;\n  }\n\n  /**\n   * Updating information of the review.\n   */\n  export interface IUpdate extends Partial<Omit<ICreate, "good_id">> {}\n}\n```\n\n### 2.3. SDK (Software Development Kit) Library\n- TypeScript functions corresponding to each API endpoint\n- Ensures type-safe API calls and is automatically generated by Nestia\n- Includes complete function signatures, metadata, and path information\n\n**Deep Analysis Requirements:**\n- **API Endpoint Classification**: Understand functional and role-based API grouping through namespace structure\n- **Parameter Structure Analysis**: Distinguish roles of path parameters, query parameters, and body in Props type\n- **HTTP Method Meaning Understanding**: Understand the meaning of each method (POST, GET, PUT, DELETE) in respective business logic\n- **Response Type Mapping**: Understand relationships between Output types and actual business objects\n- **Permission System Analysis**: Understand access permission structure through namespaces like `sellers`, `customers`\n- **API Call Order**: Understand dependency relationships of other APIs that must precede specific API calls\n- **Error Handling Methods**: Predict possible HTTP status codes and error conditions for each API\n\n**SDK Function Example:**\n```typescript\n/**\n * Update a review.\n *\n * Update a {@link IShoppingSaleReview review}\'s content and score.\n *\n * By the way, as is the general policy of this shopping mall regarding\n * articles, modifying a question articles does not actually change the\n * existing content. Modified content is accumulated and recorded in the\n * existing article record as a new\n * {@link IShoppingSaleReview.ISnapshot snapshot}. And this is made public\n * to everyone, including the {@link IShoppingCustomer customer} and the\n * {@link IShoppingSeller seller}, and anyone who can view the article can\n * also view the entire editing histories.\n *\n * This is to prevent customers or sellers from modifying their articles and\n * manipulating the circumstances due to the nature of e-commerce, where\n * disputes easily arise. That is, to preserve evidence.\n *\n * @param props.saleId Belonged sale\'s {@link IShoppingSale.id }\n * @param props.id Target review\'s {@link IShoppingSaleReview.id }\n * @param props.body Update info of the review\n * @returns Newly created snapshot record of the review\n * @tag Sale\n * @author Samchon\n *\n * @controller ShoppingCustomerSaleReviewController.update\n * @path POST /shoppings/customers/sales/:saleId/reviews/:id\n * @nestia Generated by Nestia - https://github.com/samchon/nestia\n */\nexport async function update(\n  connection: IConnection,\n  props: update.Props,\n): Promise<update.Output> {\n  return PlainFetcher.fetch(\n    {\n      ...connection,\n      headers: {\n        ...connection.headers,\n        "Content-Type": "application/json",\n      },\n    },\n    {\n      ...update.METADATA,\n      template: update.METADATA.path,\n      path: update.path(props),\n    },\n    props.body,\n  );\n}\nexport namespace update {\n  export type Props = {\n    /**\n     * Belonged sale\'s\n     */\n    saleId: string & Format<"uuid">;\n\n    /**\n     * Target review\'s\n     */\n    id: string & Format<"uuid">;\n\n    /**\n     * Update info of the review\n     */\n    body: Body;\n  };\n  export type Body = IShoppingSaleReview.IUpdate;\n  export type Output = IShoppingSaleReview.ISnapshot;\n\n  export const METADATA = {\n    method: "POST",\n    path: "/shoppings/customers/sales/:saleId/reviews/:id",\n    request: {\n      type: "application/json",\n      encrypted: false,\n    },\n    response: {\n      type: "application/json",\n      encrypted: false,\n    },\n    status: 201,\n  } as const;\n\n  export const path = (props: Omit<Props, "body">) =>\n    `/shoppings/customers/sales/${encodeURIComponent(props.saleId?.toString() ?? "null")}/reviews/${encodeURIComponent(props.id?.toString() ?? "null")}`;\n}\n```\n\n### 2.4. Random-based Mock E2E Functions\n- Basic templates filled with `typia.random<T>()` for parameters without actual business logic\n- **Guide Role**: Show function call methods, type usage, and import patterns\n- When implementing, refer to this template structure but completely replace the content\n\n**Deep Analysis Requirements:**\n- **Import Pattern Learning**: Understand which paths to import necessary types from and what naming conventions to use\n- **Function Signature Understanding**: Understand the meaning of `connection: api.IConnection` parameter and `Promise<void>` return type\n- **SDK Call Method**: Understand parameter structuring methods when calling API functions and `satisfies` keyword usage patterns\n- **Type Validation Pattern**: Understand `typia.assert()` usage and application timing\n- **Actual Data Requirements**: Understand how to compose actual business-meaningful data to replace `typia.random<T>()`\n- **Code Style Consistency**: Maintain consistency with existing codebase including indentation, variable naming, comment style\n- **Test Function Naming**: Understand existing naming conventions and apply them consistently to new test function names\n\n**Random-based Mock E2E Test Function Example:**\n```typescript\nimport typia from "typia";\nimport type { Format } from "typia/lib/tags/Format";\n\nimport api from "../../../../../src/api";\nimport type { IShoppingSaleReview } from "../../../../../src/api/structures/shoppings/sales/inquiries/IShoppingSaleReview";\n\nexport const test_api_shoppings_customers_sales_reviews_update = async (\n  connection: api.IConnection,\n) => {\n  const output: IShoppingSaleReview.ISnapshot =\n    await api.functional.shoppings.customers.sales.reviews.update(connection, {\n      saleId: typia.random<string & Format<"uuid">>(),\n      id: typia.random<string & Format<"uuid">>(),\n      body: typia.random<IShoppingSaleReview.IUpdate>(),\n    });\n  typia.assert(output);\n};\n```\n\n**Comprehensive Analysis Approach:**\nThe Agent must understand the **interrelationships** among these 4 input materials beyond analyzing them individually. You must comprehensively understand how business flows required by scenarios can be implemented with DTOs and SDK, and how mock function structures map to actual requirements. Additionally, you must infer **unspecified parts** from given materials and proactively discover **additional elements needed** for complete E2E testing.\n\n## 3. Core Writing Principles\n\n### 3.1. Scenario Adherence Principles\n- **Absolute Principle**: Complete implementation of all steps specified in test scenarios in order\n  - If "11 steps" are specified in a scenario, all 11 steps must be implemented\n  - Changing step order or skipping steps is **absolutely prohibited**\n  - **Prioritize completeness over efficiency**\n- No step in scenarios can be omitted or changed\n  - "Seller signs up" → Must call seller signup API\n  - "Customer views the product in detail" → Must call product view API\n  - More specific step descriptions require more accurate implementation\n- Strictly adhere to logical order and dependencies of business flows\n  - Example: Product registration → Signup → Shopping cart → Order → Payment → Delivery → Review creation → Review modification\n  - Each step depends on results (IDs, objects, etc.) from previous steps, so order cannot be changed\n  - Data dependencies: `sale.id`, `order.id`, `review.id` etc. must be used in subsequent steps\n- **Proactive Scenario Analysis**: Discover and implement essential steps not explicitly mentioned\n  - Precisely analyze provided API functions and DTO types\n  - Identify intermediate steps needed for business logic completion\n  - Add validation steps necessary for data integrity even if not in scenarios\n\n### 3.2. Comment Writing Principles\n- **Required**: Write complete scenarios in JSDoc format at the top of test functions\n- Include scenario background explanation and overall process\n- Clearly document step-by-step numbers and descriptions\n- Explain business context of why such complex processes are necessary\n- **Format**: Use `/** ... */` block comments\n\n### 3.3. Function Naming Conventions\n- **Basic Format**: `test_api_{domain}_{action}_{specific_scenario}`\n- **prefix**: Must start with `test_api_`\n- **domain**: Reflect API endpoint domain and action (e.g., `shopping`, `customer`, `seller`)\n- **scenario**: Express representative name or characteristics of scenario (e.g., `review_update`, `login_failure`)\n- **Examples**: `test_api_shopping_sale_review_update`, `test_api_customer_authenticate_login_failure`\n\n### 3.4. SDK Usage Principles\n- **Required**: All API calls must use provided SDK functions\n- Direct HTTP calls or other methods are **absolutely prohibited**\n- Adhere to exact parameter structure and types of SDK functions\n- Call functions following exact namespace paths (`api.functional.shoppings.sellers...`)\n- **Important**: Use `satisfies` keyword in request body to enhance type safety\n  - Example: `body: { ... } satisfies IShoppingSeller.IJoin`\n  - Prevent compile-time type errors and support IDE auto-completion\n\n### 3.5. Type Validation Principles\n- **Basic Principle**: Perform `typia.assert(value)` when API response is not `void`\n- Ensure runtime type safety for all important objects and responses\n- Configure tests to terminate immediately upon type validation failure for clear error cause identification\n\n### 3.6. Import Statement Guidelines\nAll E2E test functions must follow these standardized import patterns for consistency and maintainability:\n\n- **typia Library**: \n  ```typescript\n  import typia from "typia";\n  ```\n\n- **API SDK Functions**: \n  ```typescript\n  import api from "@ORGANIZATION/PROJECT-api";\n  ```\n\n- **DTO Types**: \n  ```typescript\n  import { DtoName } from "@ORGANIZATION/PROJECT-api/lib/structures/DtoName";\n  ```\n  - Example: `import { IShoppingSeller } from "@ORGANIZATION/PROJECT-api/lib/structures/IShoppingSeller";`\n  - Import each DTO type individually with explicit naming\n  - Follow the exact path structure: `@ORGANIZATION/PROJECT-api/lib/structures/`\n\n- **Test Validation Utilities**: \n  ```typescript\n  import { TestValidator } from "@nestia/e2e";\n  ```\n\n**Import Organization Requirements:**\n- Group imports in the following order: typia, API SDK, DTO types, TestValidator\n- Maintain alphabetical ordering within each group\n- Use explicit imports rather than wildcard imports for better type safety\n- Ensure all necessary types are imported before function implementation\n- Verify import paths match exactly with the project structure\n\n**Import Example:**\n```typescript\nimport { TestValidator } from "@nestia/e2e";\nimport typia from "typia";\n\nimport api from "@ORGANIZATION/PROJECT-api";\nimport { IShoppingCustomer } from "@ORGANIZATION/PROJECT-api/lib/structures/IShoppingCustomer";\nimport { IShoppingSale } from "@ORGANIZATION/PROJECT-api/lib/structures/IShoppingSale";\nimport { IShoppingSeller } from "@ORGANIZATION/PROJECT-api/lib/structures/IShoppingSeller";\n```\n\n## 4. Detailed Implementation Guidelines\n\n### 4.1. API and DTO Analysis Methodology\n- **Priority Analysis**: Systematically analyze all provided API functions and DTO types before implementation\n- **Dependency Understanding**: Understand call order and data dependency relationships between APIs\n- **Type Structure Understanding**: Understand nested structures, required/optional fields, and constraints of DTOs\n- **Business Logic Inference**: Infer actual business flows from API specifications and type definitions\n- **Missing Step Discovery**: Identify steps needed for complete testing but not specified in scenarios\n\n### 4.2. Function Structure\n```typescript\nimport { TestValidator } from "@nestia/e2e";\nimport typia from "typia";\n\nimport api from "@ORGANIZATION/PROJECT-api";\nimport { IShoppingCartCommodity } from "@ORGANIZATION/PROJECT-api/lib/structures/IShoppingCartCommodity";\n// ... import all necessary types\n\n/**\n * [Clearly explain test purpose]\n * \n * [Explain business context and necessity]\n * \n * [Step-by-step process]\n * 1. First step\n * 2. Second step\n * ...\n */\nexport async function test_api_{naming_convention}(\n  connection: api.IConnection,\n): Promise<void> {\n  // Implementation for each step\n}\n```\n\n### 4.3. Variable Declaration and Type Specification\n- Declare each API call result with clear types (`const seller: IShoppingSeller = ...`)\n- Write variable names meaningfully reflecting business domain\n- Use consistent naming convention (camelCase)\n- Prefer explicit type declaration over type inference\n\n### 4.4. API Call Patterns\n- Use exact namespace paths of SDK functions\n- Strictly adhere to parameter object structure\n- Use `satisfies` keyword in request body to enhance type safety\n\n### 4.5. Authentication and Session Management\n- Handle appropriate login/logout when multiple user roles are needed in test scenarios\n- Adhere to API call order appropriate for each role\'s permissions\n- **Important**: Clearly mark account switching points with comments\n- Example: Seller → Customer → Seller account switching\n- Accurately distinguish APIs accessible only after login in respective sessions\n\n### 4.6. Data Consistency Validation\n- Use `TestValidator.equals()` function to validate data consistency\n- Appropriately validate ID matching, state changes, data integrity\n- Confirm accurate structure matching when comparing arrays or objects\n- **Format**: `TestValidator.equals("description")(expected)(actual)`\n- Add descriptions for clear error messages when validation fails\n- **Error Situation Validation**: Use `TestValidator.error()` or `TestValidator.httpError()` for expected errors\n\n## 5. Complete Implementation Example\n\nThe following is a complete example of E2E test function that should actually be written:\n\n```typescript\nimport { TestValidator } from "@nestia/e2e";\nimport typia from "typia";\n\nimport api from "@ORGANIZATION/PROJECT-api";\nimport { IShoppingCartCommodity } from "@ORGANIZATION/PROJECT-api/lib/structures/IShoppingCartCommodity";\nimport { IShoppingCustomer } from "@ORGANIZATION/PROJECT-api/lib/structures/IShoppingCustomer";\nimport { IShoppingDelivery } from "@ORGANIZATION/PROJECT-api/lib/structures/IShoppingDelivery";\nimport { IShoppingOrder }   from "@ORGANIZATION/PROJECT-api/lib/structures/IShoppingOrder";\nimport { IShoppingOrderPublish } from "@ORGANIZATION/PROJECT-api/lib/structures/IShoppingOrderPublish";\nimport { IShoppingSale }    from "@ORGANIZATION/PROJECT-api/lib/structures/IShoppingSale";\nimport { IShoppingSaleReview } from "@ORGANIZATION/PROJECT-api/lib/structures/IShoppingSaleReview";\nimport { IShoppingSeller }  from "@ORGANIZATION/PROJECT-api/lib/structures/IShoppingSeller";\n\n/**\n * Validate the modification of review posts.\n *\n * However, the fact that customers can write review posts in a shopping mall means \n * that the customer has already joined the shopping mall, completed product purchase \n * and payment, and the seller has completed delivery.\n *\n * Therefore, in this test function, all of these must be carried out, so before \n * writing a review post, all of the following preliminary tasks must be performed. \n * It will be quite a long process.\n *\n * 1. Seller signs up\n * 2. Seller registers a product\n * 3. Customer signs up\n * 4. Customer views the product in detail\n * 5. Customer adds the product to shopping cart\n * 6. Customer places a purchase order\n * 7. Customer confirms purchase and makes payment\n * 8. Seller confirms order and processes delivery\n * 9. Customer writes a review post\n * 10. Customer modifies the review post\n * 11. Re-view the review post to confirm modifications.\n */\nexport async function test_api_shopping_sale_review_update(\n  connection: api.IConnection,\n): Promise<void> {\n  // 1. Seller signs up\n  const seller: IShoppingSeller = \n    await api.functional.shoppings.sellers.authenticate.join(\n      connection,\n      {\n        body: {\n          email: "john@wrtn.io",\n          name: "John Doe",\n          nickname: "john-doe",\n          mobile: "821011112222",\n          password: "1234",\n        } satisfies IShoppingSeller.IJoin,\n      },\n    );\n  typia.assert(seller);\n\n  // 2. Seller registers a product\n  const sale: IShoppingSale = \n    await api.functional.shoppings.sellers.sales.create(\n      connection,\n      {\n        body: {\n          ...\n        } satisfies IShoppingSale.ICreate,\n      },\n    );\n  typia.assert(sale);\n\n  // 3. Customer signs up\n  const customer: IShoppingCustomer = \n    await api.functional.shoppings.customers.authenticate.join(\n      connection,\n      {\n        body: {\n          email: "anonymous@wrtn.io",\n          name: "Jaxtyn",\n          nickname: "anonymous",\n          mobile: "821033334444",\n          password: "1234",\n        } satisfies IShoppingCustomer.IJoin,\n      },\n    );\n  typia.assert(customer);\n  \n  // 4. Customer views the product in detail\n  const saleReloaded: IShoppingSale = \n    await api.functional.shoppings.customers.sales.at(\n      connection,\n      {\n        id: sale.id,\n      },\n    );\n  typia.assert(saleReloaded);\n  TestValidator.equals("sale")(sale.id)(saleReloaded.id);\n\n  // 5. Customer adds the product to shopping cart\n  const commodity: IShoppingCartCommodity = \n    await api.functional.shoppings.customers.carts.commodities.create(\n      connection,\n      {\n        body: {\n          sale_id: sale.id,\n          stocks: sale.units.map((u) => ({\n            unit_id: u.id,\n            stock_id: u.stocks[0].id,\n            quantity: 1,\n          })),\n          volume: 1,\n        } satisfies IShoppingCartCommodity.ICreate,\n      },\n    );\n  typia.assert(commodity);\n\n  // 6. Customer places a purchase order\n  const order: IShoppingOrder = \n    await api.functional.shoppings.customers.orders.create(\n      connection,\n      {\n        body: {\n          goods: [\n            {\n              commodity_id: commodity.id,\n              volume: 1,\n            },\n          ],\n        } satisfies IShoppingOrder.ICreate,\n      }\n    );\n  typia.assert(order);\n\n  // 7. Customer confirms purchase and makes payment\n  const publish: IShoppingOrderPublish = \n    await api.functional.shoppings.customers.orders.publish.create(\n      connection,\n      {\n        orderId: order.id,\n        body: {\n          address: {\n            mobile: "821033334444",\n            name: "Jaxtyn",\n            country: "South Korea",\n            province: "Seoul",\n            city: "Seoul Seocho-gu",\n            department: "Wrtn Apartment",\n            possession: "140-1415",\n            zip_code: "08273",\n          },\n          vendor: {\n            code: "@payment-vendor-code",\n            uid: "@payment-transaction-uid",\n          },\n        } satisfies IShoppingOrderPublish.ICreate,\n      },\n    );\n  typia.assert(publish);\n\n  // Switch to seller account\n  await api.functional.shoppings.sellers.authenticate.login(\n    connection,\n    {\n      body: {\n        email: "john@wrtn.io",\n        password: "1234",\n      } satisfies IShoppingSeller.ILogin,\n    },\n  );\n\n  // 8. Seller confirms order and processes delivery\n  const orderReloaded: IShoppingOrder = \n    await api.functional.shoppings.sellers.orders.at(\n      connection,\n      {\n        id: order.id,\n      }\n    );\n  typia.assert(orderReloaded);\n  TestValidator.equals("order")(order.id)(orderReloaded.id);\n\n  const delivery: IShoppingDelivery = \n    await api.functional.shoppings.sellers.deliveries.create(\n      connection,\n      {\n        body: {\n          pieces: order.goods.map((g) => \n            g.commodity.stocks.map((s) => ({\n              publish_id: publish.id,\n              good_id: g.id,\n              stock_id: s.id,\n              quantity: 1,\n            }))).flat(),\n          journeys: [\n            {\n              type: "delivering",\n              title: "Delivering",\n              description: null,\n              started_at: new Date().toISOString(),\n              completed_at: new Date().toISOString(),\n            },\n          ],\n          shippers: [\n            {\n              company: "Lozen",\n              name: "QuickMan",\n              mobile: "01055559999",\n            }\n          ],\n        } satisfies IShoppingDelivery.ICreate\n      }\n    )\n  typia.assert(delivery);\n\n  // Switch back to customer account\n  await api.functional.shoppings.customers.authenticate.login(\n    connection,\n    {\n      body: {\n        email: "anonymous@wrtn.io",\n        password: "1234",\n      } satisfies IShoppingCustomer.ILogin,\n    },\n  );\n\n  // 9. Customer writes a review post\n  const review: IShoppingSaleReview = \n    await api.functional.shoppings.customers.sales.reviews.create(\n      connection,\n      {\n        saleId: sale.id,\n        body: {\n          good_id: order.goods[0].id,\n          title: "Some title",\n          body: "Some content body",\n          format: "md",\n          files: [],\n          score: 100,\n        } satisfies IShoppingSaleReview.ICreate,\n      },\n    );\n  typia.assert(review);\n\n  // 10. Customer modifies the review post\n  const snapshot: IShoppingSaleReview.ISnapshot = \n    await api.functional.shoppings.customers.sales.reviews.update(\n      connection,\n      {\n        saleId: sale.id,\n        id: review.id,\n        body: {\n          title: "Some new title",\n          body: "Some new content body",\n        } satisfies IShoppingSaleReview.IUpdate,\n      },\n    );\n  typia.assert(snapshot);\n\n  // 11. Re-view the review post to confirm modifications\n  const read: IShoppingSaleReview = \n    await api.functional.shoppings.customers.sales.reviews.at(\n      connection,\n      {\n        saleId: sale.id,\n        id: review.id,\n      },\n    );\n  typia.assert(read);\n  TestValidator.equals("snapshots")(read.snapshots)([\n    ...review.snapshots,\n    snapshot,\n  ]);\n}\n```\n\n### 5.1. Implementation Example Commentary\n\n**1. Import Statements**: Explicitly import all necessary types and utilities, accurately referencing package paths in `@ORGANIZATION/PROJECT-api` format and type definitions under `lib/structures/`. Follow the standardized import guidelines with proper grouping and alphabetical ordering.\n\n**2. Comment Structure**: JSDoc comments at the top of functions explain the background and necessity of entire scenarios, specifying detailed 11-step processes with numbers.\n\n**3. Function Name**: `test_api_shopping_sale_review_update` follows naming conventions expressing domain (shopping), entity (sale), function (review), and action (update) in order.\n\n**4. Variable Type Declaration**: Declare each API call result with clear types (`IShoppingSeller`, `IShoppingSale`, etc.) to ensure type safety.\n\n**5. SDK Function Calls**: Use exact namespace paths like `api.functional.shoppings.sellers.authenticate.join` and structure parameters according to SDK definitions.\n\n**6. satisfies Usage**: Use `satisfies` keyword in request body to enhance type safety (`satisfies IShoppingSeller.IJoin`, etc.).\n\n**7. Type Validation**: Apply `typia.assert()` to all API responses to ensure runtime type safety.\n\n**8. Account Switching**: Call login functions at appropriate times for role switching between sellers and customers.\n\n**9. Data Validation**: Use `TestValidator.equals()` to validate ID matching, array state changes, etc.\n\n**10. Complex Data Structures**: Appropriately structure complex nested objects like delivery information and shopping cart products to reflect actual business logic.\n\n## 6. Error Prevention Guidelines\n\n### 6.1. Common Mistake Prevention\n- **Typo Prevention**: Verify accuracy of SDK function paths, type names, property names\n- **Type Consistency**: Ensure consistency between variable type declarations and actual usage\n- **Missing Required Validation**: Verify application of `typia.assert()`\n- **Missing Imports**: Verify import of all necessary types and utilities\n- **Code Style**: Maintain consistent indentation, naming conventions, comment style\n\n### 6.2. Business Logic Validation\n- Adhere to logical order of scenarios\n- Verify fulfillment of essential prerequisites\n- Consider data dependency relationships\n- **State Transition**: Verify proper data state changes in each step\n- **Permission Check**: Verify only appropriate APIs are called for each user role\n\n### 6.3. Type Safety Assurance\n- Perform appropriate type validation on all API responses\n- Use `satisfies` keyword in request body\n- Verify consistency between DTO interfaces and actual data structures\n- **Compile Time**: Utilize TypeScript compiler\'s type checking\n- **Runtime**: Actual data validation through `typia.assert`\n\n## 7. Quality Standards\n\n### 7.1. Completeness\n- All scenario steps implemented without omission\n- Appropriate validation performed for each step\n- Consideration of exceptional situations included\n- **Test Coverage**: Include all major API endpoints\n- **Edge Cases**: Handle possible error situations\n\n### 7.2. Readability\n- Use clear and meaningful variable names\n- Include appropriate comments and explanations\n- Maintain logical code structure and consistent indentation\n- **Step-by-step Comments**: Clearly separate each business step\n- **Code Formatting**: Maintain consistent style and readability\n\n### 7.3. Maintainability\n- Utilize reusable patterns\n- Minimize hardcoded values\n- Design with extensible structure\n- **Modularization**: Implement repetitive logic with clear patterns\n- **Extensibility**: Structure that allows easy addition of new test cases\n\n## 8. Error Scenario Testing (Appendix)\n\n### 8.1. Purpose and Importance of Error Testing\nE2E testing must verify that systems operate correctly not only in normal business flows but also in expected error situations. It\'s important to confirm that appropriate HTTP status codes and error messages are returned in situations like incorrect input, unauthorized access, requests for non-existent resources.\n\n### 8.2. Error Validation Function Usage\n- **TestValidator.error()**: For general error situations where HTTP status code cannot be determined with certainty\n- **TestValidator.httpError()**: When specific HTTP status code can be determined with confidence\n- **Format**: `TestValidator.httpError("description")(statusCode)(() => APICall)`\n\n### 8.3. Error Test Writing Principles\n- **Clear Failure Conditions**: Clearly set conditions that should intentionally fail\n- **Appropriate Test Data**: Simulate realistic error situations like non-existent emails, incorrect passwords\n- **Concise Structure**: Unlike normal flows, compose error tests with minimal steps\n- **Function Naming Convention**: `test_api_{domain}_{action}_failure` or `test_api_{domain}_{action}_{specific_error}`\n- **CRITICAL**: Never use `// @ts-expect-error` comments when testing error cases. These functions test **runtime errors**, not compilation errors. The TypeScript code should compile successfully while the API calls are expected to fail at runtime.\n\n### 8.4. Error Test Example\n\n```typescript\nimport { TestValidator } from "@nestia/e2e";\n\nimport api from "@ORGANIZATION/PROJECT-api";\nimport { IShoppingCustomer } from "@ORGANIZATION/PROJECT-api/lib/structures/IShoppingCustomer";\n\n/**\n * Validate customer login failure.\n * \n * Verify that appropriate error response is returned when attempting \n * to login with a non-existent email address.\n */\nexport async function test_api_customer_authenticate_login_failure(\n  connection: api.IConnection,\n): Promise<void> {\n  await TestValidator.httpError("login failure")(403)(() =>\n    api.functional.shoppings.customers.authenticate.login(\n      connection,\n      {\n        body: {\n          email: "never-existing-email@sadfasdfasdf.com",\n          password: "1234",\n        } satisfies IShoppingCustomer.ILogin,\n      },\n    ),\n  );\n}\n```\n\n### 8.5. Common Error Test Scenarios\n- **Authentication Failure**: Incorrect login information, expired tokens\n- **Permission Error**: Requests for resources without access rights\n- **Resource Not Found**: Attempts to query with non-existent IDs\n- **Validation Failure**: Input of incorrectly formatted data\n- **Duplicate Data**: Signup attempts with already existing emails\n\n### 8.6. Precautions When Writing Error Tests\n- Write error tests as separate independent functions\n- Do not mix with normal flow tests\n- Accurately specify expected HTTP status codes\n- Focus on status codes rather than error message content\n- **IMPORTANT**: Never add `// @ts-expect-error` comments - error validation functions handle runtime errors while maintaining TypeScript type safety\n\n## 9. Final Checklist\n\nE2E test function writing completion requires verification of the following items:\n\n### 9.1. Essential Element Verification\n- [ ] Are all scenario steps implemented in order?\n- [ ] Are complete JSDoc-style comments written?\n- [ ] Does the function name follow naming conventions (`test_api_{domain}_{action}_{scenario}`)?\n- [ ] Are SDK used for all API calls?\n- [ ] Is the `satisfies` keyword used in request body?\n- [ ] Is `typia.assert` applied where necessary?\n- [ ] Are all necessary types imported with correct paths?\n- [ ] Do import statements follow the standardized guidelines (typia, API SDK, DTO types, TestValidator)?\n- [ ] Are error test cases written without `// @ts-expect-error` comments?\n\n### 9.2. Quality Element Verification\n- [ ] Are variable names meaningful and consistent?\n- [ ] Are account switches performed at appropriate times?\n- [ ] Is data validation performed correctly?\n- [ ] Is code structure logical with good readability?\n- [ ] Are error scenarios handled appropriately when needed without TypeScript error suppression comments?\n- [ ] Is business logic completeness guaranteed?\n- [ ] Are imports organized properly with alphabetical ordering within groups?\n\nPlease adhere to all these principles and guidelines to write complete and accurate E2E test functions. Your mission is not simply to write code, but to build a robust test system that perfectly reproduces and validates actual business scenarios.'
+}, {
+    id: v4(),
+    created_at: (new Date).toISOString(),
+    type: "assistantMessage",
+    text: [ "Here is the list of input material composition.", "", "Make e2e test functions based on the following information.", "", "## Secnario Plan", "```json", JSON.stringify(props.scenario), "```", "", "## DTO Definitions", "```json", JSON.stringify(props.artifacts.dto), "```", "", "## API (SDK) Functions", "```json", JSON.stringify(props.artifacts.sdk), "```", "", "## E2E Mockup Functions", "```json", JSON.stringify(props.artifacts.e2e), "```", "" ].join("\n")
+} ];
+
+async function orchestrateTestWrite(ctx, scenarios) {
+    const start = new Date;
+    let complete = 0;
+    const events = await Promise.all(scenarios.map((async scenario => {
+        const code = await process(ctx, scenario);
+        const event = {
+            type: "testWrite",
+            created_at: start.toISOString(),
+            filename: `test/features/api/${code.domain}/${scenario.functionName}.ts`,
+            content: code.content,
+            completed: ++complete,
+            total: scenarios.length,
+            step: ctx.state().interface?.step ?? 0
+        };
+        ctx.dispatch(event);
+        return event;
+    })));
+    return events;
+}
+
+async function process(ctx, scenario) {
+    const pointer = {
+        value: null
+    };
+    const artifacts = await compileTestScenario(ctx, scenario);
+    const agentica = new MicroAgentica({
+        model: ctx.model,
+        vendor: ctx.vendor,
+        config: {
+            ...ctx.config ?? {}
+        },
+        histories: transformTestWriteHistories({
+            scenario,
+            artifacts
+        }),
+        controllers: [ createApplication({
+            model: ctx.model,
+            build: next => {
+                pointer.value = next;
+            }
+        }) ],
+        tokenUsage: ctx.usage()
+    });
+    enforceToolCall(agentica);
+    await agentica.conversate("Create e2e test functions.");
+    if (pointer.value === null) throw new Error("Failed to create test code.");
+    return pointer.value;
+}
+
+function createApplication(props) {
+    assertSchemaModel(props.model);
+    const application = collection$1[props.model];
+    return {
+        protocol: "class",
+        name: "Create Test Code",
+        application,
+        execute: {
+            createTestCode: next => {
+                props.build(next);
+            }
+        }
+    };
+}
+
+const claude$1 = {
+    model: "claude",
+    options: {
+        reference: true,
+        separate: null
+    },
+    functions: [ {
+        name: "createTestCode",
+        parameters: {
+            description: "Current Type: {@link ICreateTestCodeProps}",
+            type: "object",
+            properties: {
+                scenario: {
+                    title: "Strategic approach for test implementation",
+                    description: "Strategic approach for test implementation.\n\nDefine the high-level strategy and logical flow for testing the given\nscenario. Focus on test methodology, data preparation, and assertion\nstrategy.\n\n### Critical Requirements\n\n- Must follow the Test Generation Guildelines.\n- Must Planning the test code Never occur the typescript compile error.\n\n### Planning Elements:\n\n#### Test Methodology\n\n- Identify test scenario type (CRUD operation, authentication flow,\n  validation test)\n- Define test data requirements and preparation strategy\n- Plan positive/negative test cases and edge cases\n- Design assertion logic and validation points\n\n#### Execution Strategy\n\n- Outline step-by-step test execution flow\n- Plan error handling and exception plans\n- Define cleanup and teardown procedures\n- Identify dependencies and prerequisites\n\n### Example Plan:\n\n    Test Strategy: Article Creation Validation\n    1. Prepare valid article data with required fields\n    2. Execute POST request to create article\n    3. Validate response structure and data integrity\n    4. Test error plans (missing fields, invalid data)\n    5. Verify database state changes\n    6. Reconsider the scenario if it doesn't follow the Test Generation\n       Guildelines.",
+                    type: "string"
+                },
+                domain: {
+                    title: "Functional domain classification for test organization",
+                    description: 'Functional domain classification for test organization.\n\nDetermines file structure and test categorization based on API\nfunctionality. Used for organizing tests into logical groups and directory\nhierarchies.\n\n### Naming Rules:\n\n- Lowercase English words only\n- Singular nouns (e.g., "article", "user", "comment")\n- Kebab-case for compound words (e.g., "user-profile", "payment-method")\n- Match primary API resource being tested\n- Domain Name must be named only one word.\n\n### Domain Examples:\n\n- `article` → Article management operations\n- `comment` → Comment-related functionality\n- `auth` → Authentication and authorization\n- `user` → User management operations\n- `payment` → Payment processing\n- `notification` → Notification system',
+                    type: "string"
+                },
+                content: {
+                    title: "Complete TypeScript E2E test implementation",
+                    description: "Complete TypeScript E2E test implementation.\n\nGenerate fully functional, compilation-error-free test code following",
+                    type: "string"
+                }
+            },
+            required: [ "scenario", "domain", "content" ],
+            additionalProperties: false,
+            $defs: {}
+        },
+        validate: (() => {
+            const _io0 = input => "string" === typeof input.scenario && "string" === typeof input.domain && "string" === typeof input.content;
+            const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.scenario || _report(_exceptionable, {
                 path: _path + ".scenario",
                 expected: "string",
                 value: input.scenario
+            }), "string" === typeof input.domain || _report(_exceptionable, {
+                path: _path + ".domain",
+                expected: "string",
+                value: input.domain
+            }), "string" === typeof input.content || _report(_exceptionable, {
+                path: _path + ".content",
+                expected: "string",
+                value: input.content
             }) ].every((flag => flag));
             const __is = input => "object" === typeof input && null !== input && _io0(input);
             let errors;
@@ -10004,11 +10573,11 @@ const claude$1 = {
                     _report = __typia_transform__validateReport._validateReport(errors);
                     ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
                         path: _path + "",
-                        expected: "IMakeScenarioProps",
+                        expected: "ICreateTestCodeProps",
                         value: input
                     })) && _vo0(input, _path + "", true) || _report(true, {
                         path: _path + "",
-                        expected: "IMakeScenarioProps",
+                        expected: "ICreateTestCodeProps",
                         value: input
                     }))(input, "$input", true);
                     const success = 0 === errors.length;
@@ -10039,132 +10608,45 @@ const collection$1 = {
             separate: null
         },
         functions: [ {
-            name: "makeScenario",
+            name: "createTestCode",
             parameters: {
-                description: " Properties containing the endpoints and user scenarios.\n\n------------------------------\n\nCurrent Type: {@link IMakeScenarioProps}",
+                description: "Current Type: {@link ICreateTestCodeProps}",
                 type: "object",
                 properties: {
-                    scenarios: {
-                        title: "Array of user scenarios",
-                        description: "Array of user scenarios.",
-                        type: "array",
-                        items: {
-                            description: "Current Type: {@link AutoBeTest.IScenario}",
-                            type: "object",
-                            properties: {
-                                endpoint: {
-                                    description: "Target API endpoint for user scenario generation.\n\nThis represents the single API endpoint that will be analyzed to generate\ncomprehensive user scenarios. The endpoint contains all technical\nspecifications needed to understand user interactions, including HTTP\nmethods, paths, parameters, request/response schemas, and authentication\nrequirements.\n\n## Core Purpose\n\n- Serves as the foundation for user-centric scenario generation\n- Contains complete API specification for understanding user capabilities\n- Provides schema constraints for realistic user data generation\n- Defines authentication and permission requirements for user context\n\n## User Scenario Context\n\nThis endpoint information enables generation of scenarios that consider:\n\n- What users can realistically accomplish with this endpoint\n- How users would naturally interact with the API functionality\n- What business value users seek from this endpoint\n- What constraints and limitations users will encounter\n- How authentication affects user access patterns\n- What data formats users need to provide or expect to receive\n\n## Single Endpoint Constraint\n\nEach scenario generated must interact with ONLY this endpoint. Scenarios\nshould not assume or require calls to other endpoints, ensuring each user\njourney is complete and testable in isolation.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
-                                    type: "object",
-                                    properties: {
-                                        path: {
-                                            title: "HTTP path of the API operation",
-                                            description: "HTTP path of the API operation.\n\nThe URL path for accessing this API operation, using path parameters\nenclosed in curly braces (e.g., `/shoppings/customers/sales/{saleId}`).\n\nIt must be corresponded to the {@link parameters path parameters}.\n\nThe path structure should clearly indicate which database entity this\noperation is manipulating, helping to ensure all entities have\nappropriate API coverage.",
-                                            type: "string"
-                                        },
-                                        method: {
-                                            title: "HTTP method of the API operation",
-                                            description: "HTTP method of the API operation.\n\nNote that, if the API operation has {@link requestBody}, method must not\nbe `get`.\n\nAlso, even though the API operation has been designed to only get\ninformation, but it needs complicated request information, it must be\ndefined as `patch` method with {@link requestBody} data specification.\n\n- `get`: get information\n- `patch`: get information with complicated request data\n  ({@link requestBody})\n- `post`: create new record\n- `put`: update existing record\n- `delete`: remove record",
-                                            type: "string",
-                                            enum: [ "get", "post", "put", "delete", "patch" ]
-                                        }
-                                    },
-                                    required: [ "path", "method" ]
-                                },
-                                scenarios: {
-                                    title: "Comprehensive collection of user-centric scenarios for the endpoint",
-                                    description: "Comprehensive collection of user-centric scenarios for the endpoint.\n\nEach scenario represents a realistic user journey, intention, or\nsituation when interacting with this specific API endpoint. All scenarios\nare written from the user's perspective, focusing on what they want to\nachieve and how they naturally interact with the API functionality.\n\n## Scenario Coverage Framework\n\nThe scenarios must comprehensively cover all user interaction patterns:\n\n### 1. Happy Path User Journeys\n\n- Primary business use cases that users commonly perform\n- Standard workflows leading to successful user outcomes\n- Typical user behaviors with valid inputs and proper permissions\n- Most frequent user intentions and expected interactions\n\n### 2. Alternative User Approaches\n\n- Valid alternative ways users might achieve their goals\n- User scenarios utilizing optional parameters or different input patterns\n- Less common but legitimate user behaviors within normal boundaries\n- User experimentation with available API features\n\n### 3. User Error Situations\n\n- Natural user mistakes with input data (incorrect formats, missing fields)\n- User attempts without proper authentication or authorization\n- User actions that violate business rules or constraints\n- User encounters with system limitations (rate limits, quotas)\n\n### 4. Boundary User Behaviors\n\n- User attempts with extreme values (minimum/maximum limits)\n- User submissions with empty, null, or unusual data\n- User inputs with special characters, long strings, or edge cases\n- User interactions testing system boundaries\n\n### 5. Contextual User Situations\n\n- User interactions when resources exist vs. don't exist\n- Different user roles attempting the same actions\n- Time-sensitive user scenarios (expired sessions, scheduled operations)\n- User attempts during various system states\n\n## User-Centric Quality Standards\n\nEach scenario must:\n\n- Focus entirely on user motivation, context, and expected outcomes\n- Describe realistic business situations users actually encounter\n- Include clear user intent and the value they seek\n- Specify user-provided data and user-expected results\n- Be complete within the single endpoint constraint\n- Provide sufficient context for understanding user behavior patterns\n- Avoid technical implementation details or testing terminology\n\n## Single Endpoint Constraint Application\n\nEvery scenario must:\n\n- Complete the entire user journey using only this one endpoint\n- Not depend on or reference other API endpoints\n- Include all necessary context within the scenario itself\n- Represent a complete, self-contained user interaction\n\n## Business Value Focus\n\nThese user scenarios ensure:\n\n- Understanding of real user needs and behaviors\n- Comprehensive coverage of user interaction patterns\n- Proper handling of user errors and edge cases\n- Appropriate user feedback and experience design\n- Business rule validation from user perspective\n- Security and permission handling for different user contexts",
-                                    type: "array",
-                                    items: {
-                                        description: "Current Type: {@link AutoBeTest.Scenario}",
-                                        type: "object",
-                                        properties: {
-                                            functionName: {
-                                                title: "Descriptive function name derived from the user scenario",
-                                                description: "Descriptive function name derived from the user scenario.\n\nThe function name serves as a concise, technical identifier that clearly\nrepresents the specific user scenario being described. It should be\nimmediately understandable and directly correspond to the user situation\nwithout requiring additional context.\n\n## Naming Convention\n\n- Must start with `test_` prefix (mandatory requirement)\n- Use snake_case formatting throughout\n- Include the primary user action (create, get, update, delete, list, etc.)\n- Specify the target resource (user, product, order, profile, etc.)\n- Add scenario-specific context (valid_data, invalid_email, not_found,\n  etc.)\n\n## Content Structure\n\nFunction names should follow this pattern:\n`test_[user_action]_[resource]_[scenario_context]`\n\nWhere:\n\n- `user_action`: What the user is trying to do\n- `resource`: What the user is interacting with\n- `scenario_context`: The specific situation or condition\n\n## User-Focused Examples\n\n- `test_create_user_profile_with_complete_information` - User providing all\n  available profile data\n- `test_retrieve_user_profile_when_profile_exists` - User accessing their\n  existing profile\n- `test_update_user_email_with_valid_new_address` - User changing their\n  email to a valid new one\n- `test_delete_user_account_when_user_lacks_permission` - User attempting\n  account deletion without authorization\n- `test_search_user_profiles_with_pagination_preferences` - User browsing\n  profiles with specific pagination\n\n## Clarity Guidelines\n\n- Prioritize clarity over brevity\n- Avoid technical jargon or implementation terms\n- Use terminology that reflects user perspective\n- Ensure the name alone conveys the user's intent\n- Make it understandable to non-technical stakeholders\n- Keep consistent with user scenario description\n\n## Single Endpoint Alignment\n\nFunction names must reflect scenarios that:\n\n- Accomplish user goals through this single endpoint only\n- Don't imply dependency on other API operations\n- Represent complete user interactions",
-                                                type: "string"
-                                            },
-                                            scenario: {
-                                                description: "Comprehensive user scenario description written from pure user\nperspective.\n\nThis describes a complete user journey, motivation, and expected outcome\nwhen interacting with the API endpoint. The description focuses entirely\non user intent, context, and natural behavior patterns rather than\ntechnical testing considerations.\n\n## User-Centric Writing Approach\n\n- Write as if describing a real person's experience and motivation\n- Focus on business context and user goals, not system functionality\n- Use natural language that business stakeholders would understand\n- Emphasize user value and expected benefits\n- Avoid technical terminology or implementation details\n\n## Required Content Elements\n\nEach scenario description must include:\n\n### 1. User Context and Motivation\n\n- Who is the user (role, background, current situation)\n- Why they need to perform this action (business motivation)\n- What problem they're trying to solve or goal they want to achieve\n- Any relevant background circumstances or constraints\n\n### 2. User Actions and Behavior\n\n- Specific steps the user takes to accomplish their goal\n- What information or data the user provides\n- How the user naturally approaches the interaction\n- Any decision-making process the user goes through\n\n### 3. User Expectations and Desired Outcomes\n\n- What the user expects to happen as a result\n- How the user will know if they were successful\n- What value or benefit the user expects to receive\n- How this fits into their broader workflow or objectives\n\n### 4. Business Impact and Value\n\n- How this scenario relates to business objectives\n- What business processes or workflows this supports\n- Why this user behavior matters to the organization\n- What risks or opportunities this scenario represents\n\n## Single Endpoint Constraint Integration\n\nEach scenario must:\n\n- Represent a complete user journey achievable through this single endpoint\n- Include all necessary context without referencing other API operations\n- Describe user expectations based solely on this endpoint's capabilities\n- Avoid scenarios that would logically require multiple API calls\n\n## Quality and Realism Standards\n\n- Base scenarios on realistic business situations\n- Include specific, concrete details rather than generic descriptions\n- Ensure scenarios reflect actual user behaviors and motivations\n- Make each scenario distinct and valuable for understanding user needs\n- Provide enough detail to understand full context without being verbose\n\n## User-Focused Example Scenarios\n\n- \"A busy project manager needs to quickly create a new team member's user\n  account during an onboarding meeting. They have all the necessary\n  information readily available and expect the account to be immediately\n  active so the new employee can start working right away.\"\n- \"A customer support representative is helping a customer who forgot their\n  login credentials. The customer provides their email address, and the\n  representative expects to quickly retrieve the associated account\n  information to assist with password recovery.\"\n- \"A system administrator discovers that a former employee's account is\n  still active after their departure. They need to immediately deactivate\n  this account for security purposes and expect confirmation that the\n  account can no longer be used to access company resources.\"\n\n## Language and Tone\n\n- Use active voice and present tense when describing user actions\n- Write in a narrative style that tells the user's story\n- Balance professional tone with human context\n- Ensure accessibility for both technical and non-technical readers\n- Maintain consistency in perspective throughout the description",
-                                                type: "string"
-                                            }
-                                        },
-                                        required: [ "functionName", "scenario" ]
-                                    }
-                                }
-                            },
-                            required: [ "endpoint", "scenarios" ]
-                        }
+                    scenario: {
+                        title: "Strategic approach for test implementation",
+                        description: "Strategic approach for test implementation.\n\nDefine the high-level strategy and logical flow for testing the given\nscenario. Focus on test methodology, data preparation, and assertion\nstrategy.\n\n### Critical Requirements\n\n- Must follow the Test Generation Guildelines.\n- Must Planning the test code Never occur the typescript compile error.\n\n### Planning Elements:\n\n#### Test Methodology\n\n- Identify test scenario type (CRUD operation, authentication flow,\n  validation test)\n- Define test data requirements and preparation strategy\n- Plan positive/negative test cases and edge cases\n- Design assertion logic and validation points\n\n#### Execution Strategy\n\n- Outline step-by-step test execution flow\n- Plan error handling and exception plans\n- Define cleanup and teardown procedures\n- Identify dependencies and prerequisites\n\n### Example Plan:\n\n    Test Strategy: Article Creation Validation\n    1. Prepare valid article data with required fields\n    2. Execute POST request to create article\n    3. Validate response structure and data integrity\n    4. Test error plans (missing fields, invalid data)\n    5. Verify database state changes\n    6. Reconsider the scenario if it doesn't follow the Test Generation\n       Guildelines.",
+                        type: "string"
+                    },
+                    domain: {
+                        title: "Functional domain classification for test organization",
+                        description: 'Functional domain classification for test organization.\n\nDetermines file structure and test categorization based on API\nfunctionality. Used for organizing tests into logical groups and directory\nhierarchies.\n\n### Naming Rules:\n\n- Lowercase English words only\n- Singular nouns (e.g., "article", "user", "comment")\n- Kebab-case for compound words (e.g., "user-profile", "payment-method")\n- Match primary API resource being tested\n- Domain Name must be named only one word.\n\n### Domain Examples:\n\n- `article` → Article management operations\n- `comment` → Comment-related functionality\n- `auth` → Authentication and authorization\n- `user` → User management operations\n- `payment` → Payment processing\n- `notification` → Notification system',
+                        type: "string"
+                    },
+                    content: {
+                        title: "Complete TypeScript E2E test implementation",
+                        description: "Complete TypeScript E2E test implementation.\n\nGenerate fully functional, compilation-error-free test code following",
+                        type: "string"
                     }
                 },
-                required: [ "scenarios" ],
+                required: [ "scenario", "domain", "content" ],
                 additionalProperties: false,
                 $defs: {}
             },
-            description: "Make user scenarios for the given endpoints.",
             validate: (() => {
-                const _io0 = input => Array.isArray(input.scenarios) && input.scenarios.every((elem => "object" === typeof elem && null !== elem && _io1(elem)));
-                const _io1 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && (Array.isArray(input.scenarios) && input.scenarios.every((elem => "object" === typeof elem && null !== elem && _io3(elem))));
-                const _io2 = input => "string" === typeof input.path && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method);
-                const _io3 = input => "string" === typeof input.functionName && "string" === typeof input.scenario;
-                const _vo0 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.scenarios) || _report(_exceptionable, {
-                    path: _path + ".scenarios",
-                    expected: "Array<AutoBeTest.IScenario>",
-                    value: input.scenarios
-                })) && input.scenarios.map(((elem, _index3) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".scenarios[" + _index3 + "]",
-                    expected: "AutoBeTest.IScenario",
-                    value: elem
-                })) && _vo1(elem, _path + ".scenarios[" + _index3 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".scenarios[" + _index3 + "]",
-                    expected: "AutoBeTest.IScenario",
-                    value: elem
-                }))).every((flag => flag)) || _report(_exceptionable, {
-                    path: _path + ".scenarios",
-                    expected: "Array<AutoBeTest.IScenario>",
-                    value: input.scenarios
-                }) ].every((flag => flag));
-                const _vo1 = (input, _path, _exceptionable = true) => [ ("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
-                    path: _path + ".endpoint",
-                    expected: "AutoBeOpenApi.IEndpoint",
-                    value: input.endpoint
-                })) && _vo2(input.endpoint, _path + ".endpoint", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".endpoint",
-                    expected: "AutoBeOpenApi.IEndpoint",
-                    value: input.endpoint
-                }), (Array.isArray(input.scenarios) || _report(_exceptionable, {
-                    path: _path + ".scenarios",
-                    expected: "Array<AutoBeTest.Scenario>",
-                    value: input.scenarios
-                })) && input.scenarios.map(((elem, _index4) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".scenarios[" + _index4 + "]",
-                    expected: "AutoBeTest.Scenario",
-                    value: elem
-                })) && _vo3(elem, _path + ".scenarios[" + _index4 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".scenarios[" + _index4 + "]",
-                    expected: "AutoBeTest.Scenario",
-                    value: elem
-                }))).every((flag => flag)) || _report(_exceptionable, {
-                    path: _path + ".scenarios",
-                    expected: "Array<AutoBeTest.Scenario>",
-                    value: input.scenarios
-                }) ].every((flag => flag));
-                const _vo2 = (input, _path, _exceptionable = true) => [ "string" === typeof input.path || _report(_exceptionable, {
-                    path: _path + ".path",
-                    expected: "string",
-                    value: input.path
-                }), "get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method || _report(_exceptionable, {
-                    path: _path + ".method",
-                    expected: '("delete" | "get" | "patch" | "post" | "put")',
-                    value: input.method
-                }) ].every((flag => flag));
-                const _vo3 = (input, _path, _exceptionable = true) => [ "string" === typeof input.functionName || _report(_exceptionable, {
-                    path: _path + ".functionName",
-                    expected: "string",
-                    value: input.functionName
-                }), "string" === typeof input.scenario || _report(_exceptionable, {
+                const _io0 = input => "string" === typeof input.scenario && "string" === typeof input.domain && "string" === typeof input.content;
+                const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.scenario || _report(_exceptionable, {
                     path: _path + ".scenario",
                     expected: "string",
                     value: input.scenario
+                }), "string" === typeof input.domain || _report(_exceptionable, {
+                    path: _path + ".domain",
+                    expected: "string",
+                    value: input.domain
+                }), "string" === typeof input.content || _report(_exceptionable, {
+                    path: _path + ".content",
+                    expected: "string",
+                    value: input.content
                 }) ].every((flag => flag));
                 const __is = input => "object" === typeof input && null !== input && _io0(input);
                 let errors;
@@ -10175,11 +10657,11 @@ const collection$1 = {
                         _report = __typia_transform__validateReport._validateReport(errors);
                         ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
                             path: _path + "",
-                            expected: "IMakeScenarioProps",
+                            expected: "ICreateTestCodeProps",
                             value: input
                         })) && _vo0(input, _path + "", true) || _report(true, {
                             path: _path + "",
-                            expected: "IMakeScenarioProps",
+                            expected: "ICreateTestCodeProps",
                             value: input
                         }))(input, "$input", true);
                         const success = 0 === errors.length;
@@ -10212,134 +10694,44 @@ const collection$1 = {
             separate: null
         },
         functions: [ {
-            name: "makeScenario",
+            name: "createTestCode",
             parameters: {
                 type: "object",
                 properties: {
-                    scenarios: {
-                        type: "array",
-                        items: {
-                            type: "object",
-                            properties: {
-                                endpoint: {
-                                    type: "object",
-                                    properties: {
-                                        path: {
-                                            type: "string",
-                                            title: "HTTP path of the API operation",
-                                            description: "HTTP path of the API operation.\n\nThe URL path for accessing this API operation, using path parameters\nenclosed in curly braces (e.g., `/shoppings/customers/sales/{saleId}`).\n\nIt must be corresponded to the {@link parameters path parameters}.\n\nThe path structure should clearly indicate which database entity this\noperation is manipulating, helping to ensure all entities have\nappropriate API coverage."
-                                        },
-                                        method: {
-                                            type: "string",
-                                            enum: [ "get", "post", "put", "delete", "patch" ],
-                                            title: "HTTP method of the API operation",
-                                            description: "HTTP method of the API operation.\n\nNote that, if the API operation has {@link requestBody}, method must not\nbe `get`.\n\nAlso, even though the API operation has been designed to only get\ninformation, but it needs complicated request information, it must be\ndefined as `patch` method with {@link requestBody} data specification.\n\n- `get`: get information\n- `patch`: get information with complicated request data\n  ({@link requestBody})\n- `post`: create new record\n- `put`: update existing record\n- `delete`: remove record"
-                                        }
-                                    },
-                                    required: [ "path", "method" ],
-                                    description: "Target API endpoint for user scenario generation.\n\nThis represents the single API endpoint that will be analyzed to generate\ncomprehensive user scenarios. The endpoint contains all technical\nspecifications needed to understand user interactions, including HTTP\nmethods, paths, parameters, request/response schemas, and authentication\nrequirements.\n\n## Core Purpose\n\n- Serves as the foundation for user-centric scenario generation\n- Contains complete API specification for understanding user capabilities\n- Provides schema constraints for realistic user data generation\n- Defines authentication and permission requirements for user context\n\n## User Scenario Context\n\nThis endpoint information enables generation of scenarios that consider:\n\n- What users can realistically accomplish with this endpoint\n- How users would naturally interact with the API functionality\n- What business value users seek from this endpoint\n- What constraints and limitations users will encounter\n- How authentication affects user access patterns\n- What data formats users need to provide or expect to receive\n\n## Single Endpoint Constraint\n\nEach scenario generated must interact with ONLY this endpoint. Scenarios\nshould not assume or require calls to other endpoints, ensuring each user\njourney is complete and testable in isolation.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
-                                    additionalProperties: false
-                                },
-                                scenarios: {
-                                    type: "array",
-                                    items: {
-                                        type: "object",
-                                        properties: {
-                                            functionName: {
-                                                type: "string",
-                                                title: "Descriptive function name derived from the user scenario",
-                                                description: "Descriptive function name derived from the user scenario.\n\nThe function name serves as a concise, technical identifier that clearly\nrepresents the specific user scenario being described. It should be\nimmediately understandable and directly correspond to the user situation\nwithout requiring additional context.\n\n## Naming Convention\n\n- Must start with `test_` prefix (mandatory requirement)\n- Use snake_case formatting throughout\n- Include the primary user action (create, get, update, delete, list, etc.)\n- Specify the target resource (user, product, order, profile, etc.)\n- Add scenario-specific context (valid_data, invalid_email, not_found,\n  etc.)\n\n## Content Structure\n\nFunction names should follow this pattern:\n`test_[user_action]_[resource]_[scenario_context]`\n\nWhere:\n\n- `user_action`: What the user is trying to do\n- `resource`: What the user is interacting with\n- `scenario_context`: The specific situation or condition\n\n## User-Focused Examples\n\n- `test_create_user_profile_with_complete_information` - User providing all\n  available profile data\n- `test_retrieve_user_profile_when_profile_exists` - User accessing their\n  existing profile\n- `test_update_user_email_with_valid_new_address` - User changing their\n  email to a valid new one\n- `test_delete_user_account_when_user_lacks_permission` - User attempting\n  account deletion without authorization\n- `test_search_user_profiles_with_pagination_preferences` - User browsing\n  profiles with specific pagination\n\n## Clarity Guidelines\n\n- Prioritize clarity over brevity\n- Avoid technical jargon or implementation terms\n- Use terminology that reflects user perspective\n- Ensure the name alone conveys the user's intent\n- Make it understandable to non-technical stakeholders\n- Keep consistent with user scenario description\n\n## Single Endpoint Alignment\n\nFunction names must reflect scenarios that:\n\n- Accomplish user goals through this single endpoint only\n- Don't imply dependency on other API operations\n- Represent complete user interactions"
-                                            },
-                                            scenario: {
-                                                type: "string",
-                                                description: "Comprehensive user scenario description written from pure user\nperspective.\n\nThis describes a complete user journey, motivation, and expected outcome\nwhen interacting with the API endpoint. The description focuses entirely\non user intent, context, and natural behavior patterns rather than\ntechnical testing considerations.\n\n## User-Centric Writing Approach\n\n- Write as if describing a real person's experience and motivation\n- Focus on business context and user goals, not system functionality\n- Use natural language that business stakeholders would understand\n- Emphasize user value and expected benefits\n- Avoid technical terminology or implementation details\n\n## Required Content Elements\n\nEach scenario description must include:\n\n### 1. User Context and Motivation\n\n- Who is the user (role, background, current situation)\n- Why they need to perform this action (business motivation)\n- What problem they're trying to solve or goal they want to achieve\n- Any relevant background circumstances or constraints\n\n### 2. User Actions and Behavior\n\n- Specific steps the user takes to accomplish their goal\n- What information or data the user provides\n- How the user naturally approaches the interaction\n- Any decision-making process the user goes through\n\n### 3. User Expectations and Desired Outcomes\n\n- What the user expects to happen as a result\n- How the user will know if they were successful\n- What value or benefit the user expects to receive\n- How this fits into their broader workflow or objectives\n\n### 4. Business Impact and Value\n\n- How this scenario relates to business objectives\n- What business processes or workflows this supports\n- Why this user behavior matters to the organization\n- What risks or opportunities this scenario represents\n\n## Single Endpoint Constraint Integration\n\nEach scenario must:\n\n- Represent a complete user journey achievable through this single endpoint\n- Include all necessary context without referencing other API operations\n- Describe user expectations based solely on this endpoint's capabilities\n- Avoid scenarios that would logically require multiple API calls\n\n## Quality and Realism Standards\n\n- Base scenarios on realistic business situations\n- Include specific, concrete details rather than generic descriptions\n- Ensure scenarios reflect actual user behaviors and motivations\n- Make each scenario distinct and valuable for understanding user needs\n- Provide enough detail to understand full context without being verbose\n\n## User-Focused Example Scenarios\n\n- \"A busy project manager needs to quickly create a new team member's user\n  account during an onboarding meeting. They have all the necessary\n  information readily available and expect the account to be immediately\n  active so the new employee can start working right away.\"\n- \"A customer support representative is helping a customer who forgot their\n  login credentials. The customer provides their email address, and the\n  representative expects to quickly retrieve the associated account\n  information to assist with password recovery.\"\n- \"A system administrator discovers that a former employee's account is\n  still active after their departure. They need to immediately deactivate\n  this account for security purposes and expect confirmation that the\n  account can no longer be used to access company resources.\"\n\n## Language and Tone\n\n- Use active voice and present tense when describing user actions\n- Write in a narrative style that tells the user's story\n- Balance professional tone with human context\n- Ensure accessibility for both technical and non-technical readers\n- Maintain consistency in perspective throughout the description"
-                                            }
-                                        },
-                                        required: [ "functionName", "scenario" ],
-                                        description: "Current Type: {@link AutoBeTest.Scenario}",
-                                        additionalProperties: false
-                                    },
-                                    title: "Comprehensive collection of user-centric scenarios for the endpoint",
-                                    description: "Comprehensive collection of user-centric scenarios for the endpoint.\n\nEach scenario represents a realistic user journey, intention, or\nsituation when interacting with this specific API endpoint. All scenarios\nare written from the user's perspective, focusing on what they want to\nachieve and how they naturally interact with the API functionality.\n\n## Scenario Coverage Framework\n\nThe scenarios must comprehensively cover all user interaction patterns:\n\n### 1. Happy Path User Journeys\n\n- Primary business use cases that users commonly perform\n- Standard workflows leading to successful user outcomes\n- Typical user behaviors with valid inputs and proper permissions\n- Most frequent user intentions and expected interactions\n\n### 2. Alternative User Approaches\n\n- Valid alternative ways users might achieve their goals\n- User scenarios utilizing optional parameters or different input patterns\n- Less common but legitimate user behaviors within normal boundaries\n- User experimentation with available API features\n\n### 3. User Error Situations\n\n- Natural user mistakes with input data (incorrect formats, missing fields)\n- User attempts without proper authentication or authorization\n- User actions that violate business rules or constraints\n- User encounters with system limitations (rate limits, quotas)\n\n### 4. Boundary User Behaviors\n\n- User attempts with extreme values (minimum/maximum limits)\n- User submissions with empty, null, or unusual data\n- User inputs with special characters, long strings, or edge cases\n- User interactions testing system boundaries\n\n### 5. Contextual User Situations\n\n- User interactions when resources exist vs. don't exist\n- Different user roles attempting the same actions\n- Time-sensitive user scenarios (expired sessions, scheduled operations)\n- User attempts during various system states\n\n## User-Centric Quality Standards\n\nEach scenario must:\n\n- Focus entirely on user motivation, context, and expected outcomes\n- Describe realistic business situations users actually encounter\n- Include clear user intent and the value they seek\n- Specify user-provided data and user-expected results\n- Be complete within the single endpoint constraint\n- Provide sufficient context for understanding user behavior patterns\n- Avoid technical implementation details or testing terminology\n\n## Single Endpoint Constraint Application\n\nEvery scenario must:\n\n- Complete the entire user journey using only this one endpoint\n- Not depend on or reference other API endpoints\n- Include all necessary context within the scenario itself\n- Represent a complete, self-contained user interaction\n\n## Business Value Focus\n\nThese user scenarios ensure:\n\n- Understanding of real user needs and behaviors\n- Comprehensive coverage of user interaction patterns\n- Proper handling of user errors and edge cases\n- Appropriate user feedback and experience design\n- Business rule validation from user perspective\n- Security and permission handling for different user contexts"
-                                }
-                            },
-                            required: [ "endpoint", "scenarios" ],
-                            description: "Current Type: {@link AutoBeTest.IScenario}",
-                            additionalProperties: false
-                        },
-                        title: "Array of user scenarios",
-                        description: "Array of user scenarios."
+                    scenario: {
+                        type: "string",
+                        title: "Strategic approach for test implementation",
+                        description: "Strategic approach for test implementation.\n\nDefine the high-level strategy and logical flow for testing the given\nscenario. Focus on test methodology, data preparation, and assertion\nstrategy.\n\n### Critical Requirements\n\n- Must follow the Test Generation Guildelines.\n- Must Planning the test code Never occur the typescript compile error.\n\n### Planning Elements:\n\n#### Test Methodology\n\n- Identify test scenario type (CRUD operation, authentication flow,\n  validation test)\n- Define test data requirements and preparation strategy\n- Plan positive/negative test cases and edge cases\n- Design assertion logic and validation points\n\n#### Execution Strategy\n\n- Outline step-by-step test execution flow\n- Plan error handling and exception plans\n- Define cleanup and teardown procedures\n- Identify dependencies and prerequisites\n\n### Example Plan:\n\n    Test Strategy: Article Creation Validation\n    1. Prepare valid article data with required fields\n    2. Execute POST request to create article\n    3. Validate response structure and data integrity\n    4. Test error plans (missing fields, invalid data)\n    5. Verify database state changes\n    6. Reconsider the scenario if it doesn't follow the Test Generation\n       Guildelines."
+                    },
+                    domain: {
+                        type: "string",
+                        title: "Functional domain classification for test organization",
+                        description: 'Functional domain classification for test organization.\n\nDetermines file structure and test categorization based on API\nfunctionality. Used for organizing tests into logical groups and directory\nhierarchies.\n\n### Naming Rules:\n\n- Lowercase English words only\n- Singular nouns (e.g., "article", "user", "comment")\n- Kebab-case for compound words (e.g., "user-profile", "payment-method")\n- Match primary API resource being tested\n- Domain Name must be named only one word.\n\n### Domain Examples:\n\n- `article` → Article management operations\n- `comment` → Comment-related functionality\n- `auth` → Authentication and authorization\n- `user` → User management operations\n- `payment` → Payment processing\n- `notification` → Notification system'
+                    },
+                    content: {
+                        type: "string",
+                        title: "Complete TypeScript E2E test implementation",
+                        description: "Complete TypeScript E2E test implementation.\n\nGenerate fully functional, compilation-error-free test code following"
                     }
                 },
-                required: [ "scenarios" ],
-                description: " Properties containing the endpoints and user scenarios.\n\n------------------------------\n\nCurrent Type: {@link IMakeScenarioProps}",
+                required: [ "scenario", "domain", "content" ],
+                description: "Current Type: {@link ICreateTestCodeProps}",
                 additionalProperties: false
             },
-            description: "Make user scenarios for the given endpoints.",
             validate: (() => {
-                const _io0 = input => Array.isArray(input.scenarios) && input.scenarios.every((elem => "object" === typeof elem && null !== elem && _io1(elem)));
-                const _io1 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && (Array.isArray(input.scenarios) && input.scenarios.every((elem => "object" === typeof elem && null !== elem && _io3(elem))));
-                const _io2 = input => "string" === typeof input.path && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method);
-                const _io3 = input => "string" === typeof input.functionName && "string" === typeof input.scenario;
-                const _vo0 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.scenarios) || _report(_exceptionable, {
-                    path: _path + ".scenarios",
-                    expected: "Array<AutoBeTest.IScenario>",
-                    value: input.scenarios
-                })) && input.scenarios.map(((elem, _index3) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".scenarios[" + _index3 + "]",
-                    expected: "AutoBeTest.IScenario",
-                    value: elem
-                })) && _vo1(elem, _path + ".scenarios[" + _index3 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".scenarios[" + _index3 + "]",
-                    expected: "AutoBeTest.IScenario",
-                    value: elem
-                }))).every((flag => flag)) || _report(_exceptionable, {
-                    path: _path + ".scenarios",
-                    expected: "Array<AutoBeTest.IScenario>",
-                    value: input.scenarios
-                }) ].every((flag => flag));
-                const _vo1 = (input, _path, _exceptionable = true) => [ ("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
-                    path: _path + ".endpoint",
-                    expected: "AutoBeOpenApi.IEndpoint",
-                    value: input.endpoint
-                })) && _vo2(input.endpoint, _path + ".endpoint", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".endpoint",
-                    expected: "AutoBeOpenApi.IEndpoint",
-                    value: input.endpoint
-                }), (Array.isArray(input.scenarios) || _report(_exceptionable, {
-                    path: _path + ".scenarios",
-                    expected: "Array<AutoBeTest.Scenario>",
-                    value: input.scenarios
-                })) && input.scenarios.map(((elem, _index4) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
-                    path: _path + ".scenarios[" + _index4 + "]",
-                    expected: "AutoBeTest.Scenario",
-                    value: elem
-                })) && _vo3(elem, _path + ".scenarios[" + _index4 + "]", _exceptionable) || _report(_exceptionable, {
-                    path: _path + ".scenarios[" + _index4 + "]",
-                    expected: "AutoBeTest.Scenario",
-                    value: elem
-                }))).every((flag => flag)) || _report(_exceptionable, {
-                    path: _path + ".scenarios",
-                    expected: "Array<AutoBeTest.Scenario>",
-                    value: input.scenarios
-                }) ].every((flag => flag));
-                const _vo2 = (input, _path, _exceptionable = true) => [ "string" === typeof input.path || _report(_exceptionable, {
-                    path: _path + ".path",
-                    expected: "string",
-                    value: input.path
-                }), "get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method || _report(_exceptionable, {
-                    path: _path + ".method",
-                    expected: '("delete" | "get" | "patch" | "post" | "put")',
-                    value: input.method
-                }) ].every((flag => flag));
-                const _vo3 = (input, _path, _exceptionable = true) => [ "string" === typeof input.functionName || _report(_exceptionable, {
-                    path: _path + ".functionName",
-                    expected: "string",
-                    value: input.functionName
-                }), "string" === typeof input.scenario || _report(_exceptionable, {
+                const _io0 = input => "string" === typeof input.scenario && "string" === typeof input.domain && "string" === typeof input.content;
+                const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.scenario || _report(_exceptionable, {
                     path: _path + ".scenario",
                     expected: "string",
                     value: input.scenario
+                }), "string" === typeof input.domain || _report(_exceptionable, {
+                    path: _path + ".domain",
+                    expected: "string",
+                    value: input.domain
+                }), "string" === typeof input.content || _report(_exceptionable, {
+                    path: _path + ".content",
+                    expected: "string",
+                    value: input.content
                 }) ].every((flag => flag));
                 const __is = input => "object" === typeof input && null !== input && _io0(input);
                 let errors;
@@ -10350,11 +10742,11 @@ const collection$1 = {
                         _report = __typia_transform__validateReport._validateReport(errors);
                         ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
                             path: _path + "",
-                            expected: "IMakeScenarioProps",
+                            expected: "ICreateTestCodeProps",
                             value: input
                         })) && _vo0(input, _path + "", true) || _report(true, {
                             path: _path + "",
-                            expected: "IMakeScenarioProps",
+                            expected: "ICreateTestCodeProps",
                             value: input
                         }))(input, "$input", true);
                         const success = 0 === errors.length;
@@ -10398,10 +10790,9 @@ const orchestrateTest = ctx => async props => {
         ctx.dispatch(history);
         return history;
     }
-    const scenarioEvent = await orchestrateTestScenario(ctx);
-    const scenarios = scenarioEvent.scenarios.map((scenario => scenario.scenarios)).flat();
-    const codes = await orchestrateTestProgress(ctx, scenarios);
-    const correct = await orchestrateTestCorrect(ctx, codes);
+    const {scenarios} = await orchestrateTestScenario(ctx);
+    const codes = await orchestrateTestWrite(ctx, scenarios);
+    const correct = await orchestrateTestCorrect(ctx, codes, scenarios);
     const history = {
         type: "test",
         id: v4(),
@@ -10415,7 +10806,10 @@ const orchestrateTest = ctx => async props => {
     ctx.dispatch({
         type: "testComplete",
         created_at: start.toISOString(),
-        files: correct.files,
+        files: correct.files.map((f => ({
+            [f.location]: f.content
+        }))).reduce(((acc, cur) => Object.assign(acc, cur)), {}),
+        compiled: correct.result,
         step: ctx.state().interface?.step ?? 0
     });
     ctx.state().test = history;
@@ -11835,29 +12229,30 @@ function emplaceMap(dict, key, generator) {
 
 class AutoBeAgent {
     constructor(props) {
-        this.props = props;
+        this.props_ = props;
         this.histories_ = props.histories?.slice() ?? [];
         this.state_ = createAutoBeState(this.histories_);
+        this.listeners_ = new Map;
+        const vendor = {
+            ...props.vendor,
+            semaphore: new Semaphore(props.vendor.semaphore ?? 16)
+        };
         this.context_ = {
+            vendor,
             model: props.model,
-            vendor: props.vendor,
             config: props.config,
             compiler: props.compiler,
             histories: () => this.histories_,
             state: () => this.state_,
             usage: () => this.agentica_.getTokenUsage(),
-            files: () => this.getFiles(),
+            files: options => this.getFiles(options),
             dispatch: event => {
                 this.dispatch(event).catch((() => {}));
             }
         };
-        this.listeners_ = new Map;
         this.agentica_ = new MicroAgentica({
+            vendor,
             model: props.model,
-            vendor: {
-                ...props.vendor,
-                semaphore: new Semaphore(props.vendor.semaphore ?? 16)
-            },
             config: {
                 ...props.config ?? {},
                 executor: {
@@ -11898,21 +12293,10 @@ class AutoBeAgent {
     }
     clone() {
         return new AutoBeAgent({
-            ...this.props,
+            ...this.props_,
             histories: this.histories_.slice()
         });
     }
-    on(type, listener) {
-        emplaceMap(this.listeners_, type, (() => new Set)).add(listener);
-        return this;
-    }
-    off(type, listener) {
-        const set = this.listeners_.get(type);
-        if (set === undefined) return this;
-        set.delete(listener);
-        if (set.size === 0) this.listeners_.delete(type);
-        return this;
-    }
     async conversate(content) {
         const index = this.histories_.length;
         const userMessageHistory = {
@@ -11929,13 +12313,13 @@ class AutoBeAgent {
         await this.agentica_.conversate(content);
         return this.histories_.slice(index);
     }
-    getFiles() {
+    async getFiles(options) {
         const files = {
             ...Object.fromEntries(this.state_.analyze ? Object.entries(this.state_.analyze.files).map((([key, value]) => [ `docs/analysis/${key.split("/").at(-1)}`, value ])) : []),
-            ...Object.fromEntries(this.state_.prisma?.result.success === true ? [ ...Object.entries(this.state_.prisma.schemas).map((([key, value]) => [ `prisma/schema/${key.split("/").at(-1)}`, value ])), ...this.state_.prisma.compiled.type === "success" ? [ [ "docs/ERD.md", this.state_.prisma.compiled.document ] ] : [], ...this.state_.prisma.compiled.type === "failure" ? [ [ "prisma/compile-error-reason.log", this.state_.prisma.compiled.reason ] ] : [], [ "autobe/prisma.json", JSON.stringify(this.state_.prisma.result.data, null, 2) ] ] : []),
+            ...Object.fromEntries(!!this.state_.prisma?.result ? [ ...Object.entries((options?.dbms ?? "postgres") === "postgres" ? this.state_.prisma.schemas : await this.context_.compiler.prisma.write(this.state_.prisma.result.data, options.dbms)).map((([key, value]) => [ `prisma/schema/${key.split("/").at(-1)}`, value ])), ...this.state_.prisma.compiled.type === "success" ? [ [ "docs/ERD.md", this.state_.prisma.compiled.document ] ] : [], ...this.state_.prisma.compiled.type === "failure" ? [ [ "prisma/compile-error-reason.log", this.state_.prisma.compiled.reason ] ] : [], [ "autobe/prisma.json", JSON.stringify(this.state_.prisma.result.data, null, 2) ] ] : []),
             ...this.state_.interface ? this.state_.interface.files : {},
-            ...this.state_.test?.compiled.type === "success" ? this.state_.test.files : {},
-            ...this.state_.realize?.compiled.type === "success" ? this.state_.realize.files : {},
+            ...this.state_.test ? Object.fromEntries(this.state_.test.files.map((f => [ f.location, f.content ]))) : {},
+            ...this.state_.realize ? this.state_.realize.files : {},
             "autobe/histories.json": JSON.stringify(this.histories_, null, 2),
             "autobe/tokenUsage.json": JSON.stringify(this.getTokenUsage(), null, 2),
             ...this.state_.interface ? {
@@ -11953,6 +12337,17 @@ class AutoBeAgent {
     getContext() {
         return this.context_;
     }
+    on(type, listener) {
+        emplaceMap(this.listeners_, type, (() => new Set)).add(listener);
+        return this;
+    }
+    off(type, listener) {
+        const set = this.listeners_.get(type);
+        if (set === undefined) return this;
+        set.delete(listener);
+        if (set.size === 0) this.listeners_.delete(type);
+        return this;
+    }
     async dispatch(event) {
         const set = this.listeners_.get(event.type);
         if (set === undefined) return;
@@ -11966,43 +12361,9 @@ class AutoBeAgent {
 
 var AutoBeTokenUsage = AgenticaTokenUsage;
 
-function invertOpenApiDocument(document) {
-    const app = HttpMigration.application(document);
-    return {
-        operations: app.routes.filter((r => r.query === null)).map((r => ({
-            specification: empty("specification"),
-            method: r.method,
-            path: r.path,
-            summary: r.operation().summary ?? empty("summary"),
-            description: r.operation().description ?? empty("description"),
-            parameters: r.parameters.map((p => ({
-                name: p.name,
-                description: p.parameter().description ?? empty("description"),
-                schema: p.schema
-            }))),
-            requestBody: r.body?.type === "application/json" && OpenApiTypeChecker.isReference(r.body.schema) ? {
-                description: r.body.description() ?? empty("description"),
-                typeName: r.body.schema.$ref.split("/").pop()
-            } : null,
-            responseBody: r.success?.type === "application/json" && OpenApiTypeChecker.isReference(r.success.schema) ? {
-                description: r.success.description() ?? empty("description"),
-                typeName: r.success.schema.$ref.split("/").pop()
-            } : null
-        }))),
-        components: {
-            schemas: document.components?.schemas ?? {}
-        }
-    };
-}
-
-function empty(key) {
-    return `Describe ${key} as much as possible with clear and concise words.`;
-}
-
 var index$1 = Object.freeze({
     __proto__: null,
-    createAgenticaHistory,
-    invertOpenApiDocument
+    createAgenticaHistory
 });
 
 var index = Object.freeze({