@autobe/agent 0.17.1 → 0.18.0

package/lib/orchestrate/realize/orchestrateRealizeCorrect.d.ts

@@ -0,0 +1,9 @@
+import { AutoBeRealizeAuthorization, AutoBeRealizeCorrectEvent, IAutoBeTypeScriptCompileResult } from "@autobe/interface";
+import { ILlmSchema } from "@samchon/openapi";
+import { AutoBeContext } from "../../context/AutoBeContext";
+import { IAutoBeRealizeScenarioApplication } from "./structures/IAutoBeRealizeScenarioApplication";
+export declare function orchestrateRealizeCorrect<Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, authorization: AutoBeRealizeAuthorization | null, scenario: IAutoBeRealizeScenarioApplication.IProps, code: string, diagnostic: IAutoBeTypeScriptCompileResult.IDiagnostic, progress: IProgress): Promise<AutoBeRealizeCorrectEvent>;
+export interface IProgress {
+    total: number;
+    completed: number;
+}

package/lib/orchestrate/realize/orchestrateRealizeScenario.d.ts

@@ -0,0 +1,91 @@
+import { AutoBeOpenApi, AutoBeRealizeAuthorization } from "@autobe/interface";
+import { ILlmSchema } from "@samchon/openapi";
+import { AutoBeContext } from "../../context/AutoBeContext";
+import { IAutoBeRealizeScenarioApplication } from "./structures/IAutoBeRealizeScenarioApplication";
+export interface IAutoBeRealizeScenario {
+    /**
+     * The name of the function to be generated.
+     *
+     * Derived from the Swagger path and method. The function name must be written
+     * in snake_case. It serves as the entry point in both code generation and
+     * test code.
+     *
+     * Once the function is generated, the function name and file name will be the
+     * same. The generated file will be located at
+     * `src/providers/${function_name}.ts`.
+     */
+    functionName: string;
+    /**
+     * Definition of path and query parameters extracted from the OpenAPI spec.
+     *
+     * Includes input values passed via URL path or query string. Used for type
+     * definitions, validation, and function signature construction.
+     */
+    parameters: AutoBeOpenApi.IParameter[];
+    /**
+     * Schema definition for the request body input.
+     *
+     * Extracted from the requestBody section of Swagger. Represents the input
+     * data passed in the body (e.g., JSON). Used for generating function
+     * arguments or DTOs.
+     */
+    inputSchema: AutoBeOpenApi.IRequestBody | null;
+    /**
+     * Schema definition for the response body.
+     *
+     * Extracted from the responses section of Swagger. Used to define the return
+     * type and expected output in test code.
+     */
+    outputSchema: AutoBeOpenApi.IResponseBody | null;
+    /**
+     * Natural language description of the function’s purpose.
+     *
+     * Extracted from the summary or description field of Swagger. Used for code
+     * documentation, test scenario generation, and conveying function intent.
+     */
+    description: string;
+    /**
+     * HTTP method information.
+     *
+     * Extracted from the Swagger operation method. Used to define the request
+     * type during code and test generation.
+     */
+    method: "get" | "post" | "put" | "delete" | "patch";
+    /**
+     * List of scenario descriptions for test code generation.
+     *
+     * Each scenario describes the expected behavior of the function under certain
+     * conditions. Used as a basis for TDD-style automated test generation.
+     */
+    testScenarios: string[];
+    /**
+     * Optional decorator event for customizing code generation behavior.
+     *
+     * Provides additional metadata or instructions that can modify how the
+     * function implementation is generated. Can include custom annotations,
+     * middleware configurations, or special handling directives that affect the
+     * final code output.
+     */
+    decoratorEvent?: AutoBeRealizeAuthorization;
+}
+/**
+ * Generates a planning result that defines what kind of function should be
+ * created, based solely on the provided Swagger (OpenAPI) operation — without
+ * using an LLM.
+ *
+ * This function analyzes the structure of the OpenAPI operation (such as the
+ * path, method, parameters, request/response schema, and descriptions) to
+ * determine the appropriate function name, input/output types, and purpose of
+ * the function.
+ *
+ * The result of this function (`RealizePlannerOutput`) will be passed to the
+ * next step in the AutoBE pipeline, which is responsible for generating the
+ * actual implementation code.
+ *
+ * @author Kakasoo
+ * @param ctx - AutoBE context including model and configuration
+ * @param operation - A single OpenAPI operation object to analyze and plan
+ * @returns A planning object containing all structural information needed to
+ *   generate the function
+ */
+export declare const orchestrateRealizeScenario: <Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, operation: AutoBeOpenApi.IOperation, authorization?: AutoBeRealizeAuthorization) => IAutoBeRealizeScenarioApplication.IProps;

package/lib/orchestrate/realize/orchestrateRealizeWrite.d.ts

@@ -0,0 +1,9 @@
+import { AutoBeRealizeAuthorization, AutoBeRealizeWriteEvent } from "@autobe/interface";
+import { ILlmSchema } from "@samchon/openapi";
+import { AutoBeContext } from "../../context/AutoBeContext";
+import { IAutoBeRealizeScenarioApplication } from "./structures/IAutoBeRealizeScenarioApplication";
+export declare function orchestrateRealizeWrite<Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, authorization: AutoBeRealizeAuthorization | null, scenario: IAutoBeRealizeScenarioApplication.IProps, progress: IProgress): Promise<AutoBeRealizeWriteEvent>;
+export interface IProgress {
+    total: number;
+    completed: number;
+}

package/lib/orchestrate/realize/structures/IAutoBeRealizeAuthorizationApplication.d.ts

@@ -1,3 +1,4 @@
+import { CamelPattern, PascalPattern } from "@autobe/interface";
 export interface IAutoBeRealizeAuthorizationApplication {
     createDecorator: (next: IAutoBeRealizeAuthorizationApplication.IProps) => void;
 }
@@ -32,8 +33,10 @@ export declare namespace IAutoBeRealizeAuthorizationApplication {
          * format (e.g., adminAuthorize, userAuthorize). This function will be
          * called by the decorator to verify JWT tokens and return authenticated
          * user information for the specified role.
+         *
+         * MUST use camelCase naming convention.
          */
-        name: string;
+        name: string & CamelPattern;
         /**
          * Complete TypeScript code for the authentication Provider function. Must
          * include: JWT token verification using jwtAuthorize function, role type
@@ -51,8 +54,10 @@ export declare namespace IAutoBeRealizeAuthorizationApplication {
          * decorator in Controller methods to automatically authenticate and
          * authorize users for the specific role, injecting the authenticated user
          * payload as a method parameter.
+         *
+         * MUST use PascalCase naming convention.
          */
-        name: string;
+        name: string & PascalPattern;
         /**
          * Complete TypeScript code for the authentication Decorator implementation.
          * Must include: SwaggerCustomizer integration to add bearer token security
@@ -69,8 +74,10 @@ export declare namespace IAutoBeRealizeAuthorizationApplication {
          * (e.g., AdminPayload, UserPayload). This type defines the structure of the
          * authenticated user data that will be injected into Controller methods
          * when using the decorator.
+         *
+         * MUST use PascalCase naming convention.
          */
-        name: string;
+        name: string & PascalPattern;
         /**
          * Complete TypeScript code for the Payload type interface in {Role}Payload
          * format (e.g., AdminPayload, UserPayload). Must include: id field with

package/lib/orchestrate/realize/structures/IAutoBeRealizeReviewApplication.d.ts

@@ -0,0 +1,79 @@
+import { IAutoBeRealizeWriteApplication } from "./IAutoBeRealizeWriteApplication";
+export interface IAutoBeRealizeCorrectApplication {
+    review: (props: IAutoBeRealizeCorrectApplication.IProps) => void;
+}
+export declare namespace IAutoBeRealizeCorrectApplication {
+    interface IProps extends IAutoBeRealizeWriteApplication.IProps {
+        /**
+         * Compilation Error Analysis and Resolution Strategy
+         *
+         * This field contains a detailed analysis of TypeScript compilation errors
+         * that occurred during the previous compilation attempt, along with
+         * specific strategies to resolve each error.
+         *
+         * The analysis MUST include:
+         *
+         * 📊 ERROR BREAKDOWN:
+         *
+         * - List of all TypeScript error codes encountered (e.g., TS2339, TS2345)
+         * - Exact error messages and the lines/files where they occurred
+         * - Categorization of errors by type (type mismatch, missing property, etc.)
+         *
+         * 🔍 ROOT CAUSE ANALYSIS:
+         *
+         * - Why each error occurred (e.g., incorrect type assumptions, missing
+         *   fields)
+         * - Relationship between errors (e.g., cascading errors from a single issue)
+         * - Common patterns identified across multiple errors
+         *
+         * 🛠 RESOLUTION STRATEGY:
+         *
+         * - Specific fixes for each error type
+         * - Priority order for addressing errors (fix critical errors first)
+         * - Alternative approaches if the direct fix is not possible
+         *
+         * 📝 SCHEMA VERIFICATION:
+         *
+         * - Re-verification of Prisma schema fields actually available
+         * - Identification of assumed fields that don't exist
+         * - Correct field types and relationships
+         *
+         * ⚠️ COMMON ERROR PATTERNS TO CHECK:
+         *
+         * - Using non-existent fields (e.g., deleted_at, created_by)
+         * - Type mismatches in Prisma operations
+         * - Incorrect date handling (using Date instead of string)
+         * - Missing required fields in create/update operations
+         * - Incorrect relation handling in nested operations
+         *
+         * 🎯 CORRECTION APPROACH:
+         *
+         * - Remove references to non-existent fields
+         * - Fix type conversions (especially dates with toISOStringSafe())
+         * - Simplify complex nested operations into separate queries
+         * - Add missing required fields
+         * - Use correct Prisma input types
+         *
+         * Example structure:
+         *
+         *     Errors Found:
+         *     1. TS2339: Property 'deleted_at' does not exist on type 'User'
+         *        - Cause: Field assumed but not in schema
+         *        - Fix: Remove all deleted_at references
+         *
+         *     2. TS2345: Type 'Date' is not assignable to type 'string'
+         *        - Cause: Direct Date assignment without conversion
+         *        - Fix: Use toISOStringSafe() for all date values
+         *
+         *     Resolution Plan:
+         *     1. First, remove all non-existent field references
+         *     2. Then, fix all date type conversions
+         *     3. Finally, adjust Prisma query structures
+         *
+         * This analysis ensures the review process addresses all compilation errors
+         * systematically and produces error-free code in the corrected
+         * implementation.
+         */
+        errorAnalysis: string;
+    }
+}

package/lib/orchestrate/realize/structures/IAutoBeRealizeScenarioApplication.d.ts

@@ -0,0 +1,38 @@
+import { AutoBeOpenApi, AutoBeRealizeAuthorization } from "@autobe/interface";
+export declare namespace IAutoBeRealizeScenarioApplication {
+    interface IProps {
+        /** The OpenAPI operation to be realized. */
+        operation: AutoBeOpenApi.IOperation;
+        /**
+         * The name of the function to be generated.
+         *
+         * Derived from the Swagger path and method. The function name must be
+         * written in snake_case. It serves as the entry point in both code
+         * generation and test code.
+         *
+         * Once the function is generated, the function name and file name will be
+         * the same. The generated file will be located at
+         * `src/providers/${function_name}.ts`.
+         */
+        functionName: string;
+        /** For example, `src/providers/${function_name}.ts`. */
+        location: string;
+        /**
+         * List of scenario descriptions for test code generation.
+         *
+         * Each scenario describes the expected behavior of the function under
+         * certain conditions. Used as a basis for TDD-style automated test
+         * generation.
+         */
+        testScenarios: string[];
+        /**
+         * Optional decorator event for customizing code generation behavior.
+         *
+         * Provides additional metadata or instructions that can modify how the
+         * function implementation is generated. Can include custom annotations,
+         * middleware configurations, or special handling directives that affect the
+         * final code output.
+         */
+        decoratorEvent?: AutoBeRealizeAuthorization;
+    }
+}

package/lib/orchestrate/realize/structures/IAutoBeRealizeWriteApplication.d.ts

@@ -0,0 +1,276 @@
+export interface IAutoBeRealizeWriteApplication {
+    coding: (next: IAutoBeRealizeWriteApplication.IProps) => void;
+}
+export declare namespace IAutoBeRealizeWriteApplication {
+    interface IProps {
+        /**
+         * Step 1.
+         *
+         * 🧠 Provider Function Implementation Plan
+         *
+         * This field outlines the strategic plan for implementing the provider
+         * function according to the Realize Coder Agent specification. Before
+         * writing the actual code, think through the logic and structure.
+         *
+         * The plan MUST follow MANDATORY SCHEMA-FIRST APPROACH:
+         *
+         * 📋 STEP 1 - PRISMA SCHEMA VERIFICATION (MOST CRITICAL):
+         *
+         * - EXAMINE the actual Prisma schema model definition
+         * - LIST EVERY field that exists in the model with exact types
+         * - EXPLICITLY NOTE fields that DO NOT exist (e.g., "Note: deleted_at field
+         *   DOES NOT EXIST")
+         * - Common assumption errors to avoid: `deleted_at`, `created_by`,
+         *   `updated_by`, `is_deleted`, `is_active`
+         *
+         * 📋 STEP 2 - FIELD INVENTORY:
+         *
+         * - List ONLY fields confirmed to exist in schema
+         * - Example: "Verified fields in user model: id (String), email (String),
+         *   created_at (DateTime), updated_at (DateTime)"
+         * - Example: "Fields that DO NOT exist: deleted_at, is_active, created_by"
+         *
+         * 📋 STEP 3 - FIELD ACCESS STRATEGY:
+         *
+         * - Plan which verified fields will be used in select, update, create
+         *   operations
+         * - For complex operations with type errors, plan to use separate queries
+         *   instead of nested operations
+         *
+         * 📋 STEP 4 - TYPE COMPATIBILITY:
+         *
+         * - Plan DateTime to ISO string conversions using toISOStringSafe()
+         * - Plan handling of nullable vs required fields
+         *
+         * 📋 STEP 5 - IMPLEMENTATION APPROACH:
+         *
+         * - 🧩 Required business entities (e.g., users, posts, logs) and their
+         *   relationships
+         * - 🛠 Operations needed to fulfill the business scenario (e.g., fetch,
+         *   create, update) using ONLY verified fields
+         * - 🔄 Data dependencies between steps (e.g., use userId to fetch related
+         *   data)
+         * - ✅ Validation points (based on business rules, not field presence)
+         * - 🚧 Error and edge cases that must be handled explicitly (e.g., missing
+         *   records)
+         * - 🏗 Structure: always a single `async function`, using only `parameters`
+         *   and `body`
+         *
+         * ⚠️ Important Constraints:
+         *
+         * - Do NOT perform input validation — assume `parameters` and `body` are
+         *   already valid
+         * - Use `typia.random<T>()` with an explanatory comment if logic can't be
+         *   implemented
+         * - Never use `any` or make assumptions without sufficient context
+         * - Use only allowed imports — DTOs and Prisma types
+         * - Use `MyGlobal.prisma` for DB access and respect Prisma typing rules
+         *
+         * ⚠️ TypeScript-specific considerations:
+         *
+         * - Do **not** use native `Date` objects directly; always convert all dates
+         *   using `toISOStringSafe()` and brand as `string &
+         *   tags.Format<'date-time'>`. This rule applies throughout all phases.
+         * - Prefer `satisfies` for DTO conformance instead of unsafe `as` casts
+         * - Avoid weak typing such as `any`, `as any`, or `satisfies any`
+         * - Use branded types (e.g., `tags.Format<'uuid'>`) and literal unions where
+         *   applicable
+         *
+         * ✅ Example Structure:
+         *
+         * ```ts
+         * export async function doSomething(
+         *   user: { id: string & tags.Format<"uuid">; type: string },
+         *   parameters: IParams,
+         *   body: IBody
+         * ): Promise<IReturn> {
+         *   const { id } = parameters;
+         *   const { name } = body;
+         *   const user = await MyGlobal.prisma.users.findFirst({ where: { id } });
+         *   if (!user) throw new Error("User not found");
+         *   ...
+         *   return result;
+         * }
+         * ```
+         *
+         * 🔍 Feasibility Analysis Requirement:
+         *
+         * - Before generating any code, the agent **must analyze** whether the
+         *   requested implementation is **feasible based on the given Prisma schema
+         *   and DTO types**.
+         * - If required fields or relationships are **missing or incompatible**, the
+         *   plan should explicitly state that the implementation is **not
+         *   possible** with the current schema/DTO, and no code should be generated
+         *   in later stages.
+         * - In such cases, only a detailed **comment in the `implementationCode`**
+         *   should be returned explaining why the logic cannot be implemented.
+         *
+         * 🔥 Error Handling Plan:
+         *
+         * If an error is expected or encountered during implementation:
+         *
+         * - Clearly document the error message(s) and TypeScript error codes.
+         * - Analyze the root cause (e.g., type mismatch, missing field, nullability
+         *   issue).
+         * - Define concrete steps to resolve the issue, such as:
+         *
+         *   - Adjusting type declarations or using Prisma-generated input types.
+         *   - Using `?? undefined` to normalize nullable fields.
+         *   - Applying correct relation handling (e.g., `connect` instead of direct
+         *       foreign key assignment).
+         *   - Ensuring all date fields use `.toISOString()` and proper branding.
+         * - Include fallback or workaround plans if a direct fix is complex.
+         * - If no error is present, simply omit this section.
+         *
+         * This plan ensures the function will:
+         *
+         * - Respect the global architecture and coding conventions
+         * - Be safe, predictable, and aligned with upstream logic
+         */
+        plan: string;
+        /**
+         * Step 2.
+         *
+         * The Prisma schema string that will be used to validate the implementation
+         * logic in this file.
+         *
+         * You must **explicitly specify only the relevant models and fields** from
+         * your full schema that are used in this implementation. This ensures that
+         * your logic is aligned with the expected database structure without
+         * accidentally introducing unrelated fields or models.
+         *
+         * ⚠️ Important: The value of this field must be a valid Prisma schema
+         * string containing only the models used in this code — not the entire
+         * schema.
+         *
+         * This acts as a safeguard against:
+         *
+         * - Forgetting required fields used in this implementation
+         * - Including fields or models that are not actually used
+         */
+        prisma_schemas: string;
+        /**
+         * Step 3.
+         *
+         * Draft WITHOUT using native Date type.
+         *
+         * This is the initial drafting phase where you outline the basic skeleton
+         * of the function. CRITICAL: This draft must NEVER use the native Date
+         * type.
+         *
+         * - The function signature must correctly include `user`, `parameters`, and
+         *   `body` arguments.
+         * - Design the main flow of business logic, such as DB fetches and early
+         *   returns based on conditions.
+         * - Mark any incomplete or missing parts clearly with placeholders (e.g.,
+         *   comments or temporary values).
+         *
+         * ⚠️ Import rules:
+         *
+         * - Do NOT add any new import statements manually.
+         * - All necessary imports are provided globally or by the system
+         *   automatically.
+         * - Writing import statements directly is prohibited and may cause compile
+         *   errors. If import errors occur, check your environment configuration.
+         *
+         * ✅ Requirements:
+         *
+         * - Avoid using the `any` type at all costs to ensure type safety.
+         * - NEVER declare variables with `: Date` type
+         * - ALWAYS use `string & tags.Format<'date-time'>` for date values
+         * - Use `toISOStringSafe(new Date())` for current timestamps
+         * - Maintain a single-function structure; avoid using classes.
+         */
+        draft_without_date_type: string;
+        /**
+         * Step 4.
+         *
+         * A refined version of the draft with improved completeness.
+         *
+         * - Replace placeholder logic with real DTO-conformant operations.
+         * - Add error handling (`throw new Error(...)`) where necessary.
+         * - Begin resolving structural or type mismatches.
+         *
+         * ✅ Requirements:
+         *
+         * - Use `satisfies` to ensure DTO conformity.
+         * - Avoid unsafe `as` casts unless only for branding or literal narrowing.
+         * - Use `toISOStringSafe()` for all date conversions (NOT `.toISOString()`).
+         * - Ensure all object keys strictly conform to the expected type definitions.
+         */
+        review: string;
+        /**
+         * 🛠 Phase 4-2: With compiler feedback (optional)
+         *
+         * A correction pass that applies fixes for compile-time errors that arose
+         * during the review stage (if any).
+         *
+         * ✅ Must:
+         *
+         * - Only include this field if TypeScript errors are detected in the Review
+         *   phase.
+         * - Resolve all TypeScript errors without using `as any`.
+         * - Provide safe brand casting only if required (e.g., `as string &
+         *   tags.Format<'uuid'>`).
+         * - If no TypeScript errors exist, this field MUST contain the text: "No
+         *   TypeScript errors detected - skipping this phase"
+         */
+        withCompilerFeedback: string;
+        /**
+         * Step 5.
+         *
+         * The complete and fully correct TypeScript function implementation.
+         *
+         * - Passes strict type checking without errors.
+         * - Uses only safe branding or literal type assertions.
+         * - Converts all date values properly using `toISOStringSafe()`.
+         * - Follows DTO structures using `satisfies`.
+         * - Avoids any weak typing such as `any`, `as any`, or `satisfies any`.
+         * - Uses only allowed imports (e.g., from `../api/structures` and
+         *   `MyGlobal.prisma`).
+         * - NEVER creates intermediate variables for Prisma operations.
+         *
+         * ⚠️ Fallback Behavior:
+         *
+         * - If the `plan` phase explicitly determines that the requested logic is
+         *   **not feasible** due to mismatches or limitations in the provided
+         *   Prisma schema and DTO types:
+         *
+         *   - The implementation must still return a syntactically valid function.
+         *   - In such cases, return mock data using `typia.random<T>()` wrapped in the
+         *       correct structure, along with a comment explaining the limitation.
+         *
+         *   Example fallback:
+         *
+         * ```ts
+         *   // ⚠️ Cannot implement logic due to missing relation between A and B
+         *   export async function someFunction(...) {
+         *     return typia.random<IReturn>(); // mocked output
+         *   }
+         * ```
+         *
+         * ⚠️ Prohibited Practices:
+         *
+         * - Do NOT add or modify import statements manually. Imports are handled
+         *   automatically by the system.
+         * - Do NOT use `any`, `as any`, or `satisfies any` to bypass type checking.
+         * - Do NOT assign native `Date` objects directly; always convert them using
+         *   `toISOStringSafe()`.
+         * - Do NOT use unsafe type assertions except for safe branding or literal
+         *   narrowing.
+         * - Do NOT write code outside the single async function structure (e.g., no
+         *   classes or multiple functions).
+         * - Do NOT perform any input validation — assume all inputs are already
+         *   validated.
+         * - Do NOT use dynamic import expressions (`import()`); all imports must be
+         *   static.
+         * - Do NOT use Prisma-generated input types; always use types from
+         *   `../api/structures`.
+         * - Do NOT use `Object.prototype.hasOwnProperty.call()` for field checks.
+         * - Do NOT escape newlines or quotes in the implementation string (e.g., no
+         *   `\\n` or `\"`); use a properly formatted template literal with actual
+         *   line breaks instead.
+         */
+        implementationCode: string;
+    }
+}

package/lib/orchestrate/test/histories/transformTestCorrectHistories.d.ts

@@ -0,0 +1,4 @@
+import { IAgenticaHistoryJson } from "@agentica/core";
+import { IAutoBeTypeScriptCompileResult } from "@autobe/interface";
+import { IAutoBeTestFunction } from "../structures/IAutoBeTestFunction";
+export declare const transformTestCorrectHistories: (func: IAutoBeTestFunction, failure: IAutoBeTypeScriptCompileResult.IFailure) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;

package/lib/orchestrate/test/histories/transformTestHistories.d.ts

@@ -0,0 +1,3 @@
+import { IAgenticaHistoryJson } from "@agentica/core";
+import { AutoBeState } from "../../../context/AutoBeState";
+export declare const transformTestHistories: (state: AutoBeState) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;

package/lib/orchestrate/test/histories/transformTestScenarioHistories.d.ts

@@ -0,0 +1,3 @@
+import { IAgenticaHistoryJson } from "@agentica/core";
+import { AutoBeOpenApi } from "@autobe/interface";
+export declare const transformTestScenarioHistories: (entire: AutoBeOpenApi.IOperation[], include: AutoBeOpenApi.IOperation[], exclude: Pick<AutoBeOpenApi.IOperation, "method" | "path">[]) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;

package/lib/orchestrate/test/histories/transformTestWriteHistories.d.ts

@@ -0,0 +1,8 @@
+import { IAgenticaHistoryJson } from "@agentica/core";
+import { AutoBeTestScenario } from "@autobe/interface";
+import { IAutoBeTestScenarioArtifacts } from "../structures/IAutoBeTestScenarioArtifacts";
+export declare function transformTestWriteHistories(scenario: AutoBeTestScenario, artifacts: IAutoBeTestScenarioArtifacts): Array<IAgenticaHistoryJson.ISystemMessage>;
+export declare namespace transformTestWriteHistories {
+    function structures(artifacts: IAutoBeTestScenarioArtifacts): string;
+    function functional(artifacts: IAutoBeTestScenarioArtifacts): string;
+}

package/lib/orchestrate/test/orchestrateTestScenario.d.ts

@@ -1,4 +1,4 @@
-import { AutoBeTestScenarioEvent } from "@autobe/interface";
+import { AutoBeTestScenario } from "@autobe/interface";
 import { ILlmSchema } from "@samchon/openapi";
 import { AutoBeContext } from "../../context/AutoBeContext";
-export declare function orchestrateTestScenario<Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>): Promise<AutoBeTestScenarioEvent>;
+export declare function orchestrateTestScenario<Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>): Promise<AutoBeTestScenario[]>;

package/lib/orchestrate/test/structures/IAutoBeTestScenarioApplication.d.ts

@@ -1,4 +1,5 @@
-import { AutoBeOpenApi } from "@autobe/interface";
+import { AutoBeOpenApi, SnakePattern } from "@autobe/interface";
+import { tags } from "typia";
 export interface IAutoBeTestScenarioApplication {
     /**
      * Make test scenarios for the given endpoints.
@@ -28,7 +29,7 @@ export declare namespace IAutoBeTestScenarioApplication {
          * Each scenario represents a specific test case for the same `path` and
          * `method`.
          */
-        scenarios: IScenario[];
+        scenarios: IScenario[] & tags.MinItems<1>;
     }
     /**
      * Represents a test scenario for a single API operation.
@@ -56,36 +57,36 @@ export declare namespace IAutoBeTestScenarioApplication {
          *
          * ## Naming Convention
          *
-         * - Must start with `test_` prefix (mandatory requirement)
-         * - Use snake_case formatting throughout
-         * - Include the primary user action (create, get, update, delete, list, etc.)
-         * - Specify the target resource (user, product, order, profile, etc.)
-         * - Add scenario-specific context (valid_data, invalid_email, not_found,
-         *   etc.)
+         * MUST use snake_case naming convention.
+         *
+         * - Must start with `test_api_` prefix (mandatory requirement)
+         * - ALWAYS start with business feature, NOT action verbs
+         * - Business feature comes first, followed by scenario context
+         * - Embed action verbs within the scenario description, not at the beginning
          *
          * ## Content Structure
          *
          * Function names should follow this pattern:
-         * `test_[user_action]_[resource]_[scenario_context]`
+         * `test_api_[core_feature]_[specific_scenario]`
          *
          * Where:
          *
-         * - `user_action`: What the user is trying to do
-         * - `resource`: What the user is interacting with
-         * - `scenario_context`: The specific situation or condition
+         * - `core_feature`: The main business feature or entity being tested
+         *   (customer, seller, cart, push_message, etc.)
+         * - `specific_scenario`: The specific operation or scenario context
+         *   (join_verification_not_found, login_success,
+         *   moderator_assignment_update, discountable_ticket_duplicated,
+         *   csv_export, etc.)
          *
-         * ## User-Focused Examples
+         * ## Business Feature-Based Examples
          *
-         * - `test_create_user_profile_with_complete_information` - User providing all
-         *   available profile data
-         * - `test_retrieve_user_profile_when_profile_exists` - User accessing their
-         *   existing profile
-         * - `test_update_user_email_with_valid_new_address` - User changing their
-         *   email to a valid new one
-         * - `test_delete_user_account_when_user_lacks_permission` - User attempting
-         *   account deletion without authorization
-         * - `test_search_user_profiles_with_pagination_preferences` - User browsing
-         *   profiles with specific pagination
+         * - `test_api_customer_join_verification_not_found` - Customer join
+         *   verification when verification code not found
+         * - `test_api_seller_login` - Seller login operation
+         * - `test_api_cart_discountable_ticket_duplicated` - Cart discountable ticket
+         *   with duplication scenario
+         * - `test_api_push_message_csv` - Push message functionality with CSV format
+         * - `test_api_product_review_update` - Product review update operation
          *
          * ## Clarity Guidelines
          *
@@ -104,7 +105,7 @@ export declare namespace IAutoBeTestScenarioApplication {
          * - Don't imply dependency on other API operations
          * - Represent complete user interactions
          */
-        functionName: string;
+        functionName: string & SnakePattern;
         /**
          * A list of other API endpoints that this scenario logically depends on.
          *