@autobe/agent 0.30.0-dev.20260315 → 0.30.1

package/src/orchestrate/common/structures/IAutoBePreliminaryGetInterfaceSchemas.ts

@@ -1,31 +1,31 @@
-import { tags } from "typia";
-
-/**
- * Request to retrieve OpenAPI schema type definitions for context.
- *
- * This type is used in the preliminary phase to request specific schema
- * definitions from components.schemas for review or complementary generation.
- *
- * @author Samchon
- */
-export interface IAutoBePreliminaryGetInterfaceSchemas {
-  /**
-   * Type discriminator for the request.
-   *
-   * Determines which action to perform: preliminary data retrieval or actual
-   * task execution. Value "getInterfaceSchemas" indicates this is a preliminary
-   * data request for interface schemas.
-   */
-  type: "getInterfaceSchemas";
-
-  /**
-   * List of schema type names to retrieve.
-   *
-   * Schema names from the OpenAPI components.schemas section (e.g., "IUser",
-   * "IUser.ICreate", "IPost.IUpdate").
-   *
-   * CRITICAL: DO NOT request the same type names that you have already
-   * requested in previous calls.
-   */
-  typeNames: string[] & tags.MinItems<1>;
-}
+import { tags } from "typia";
+
+/**
+ * Request to retrieve OpenAPI schema type definitions for context.
+ *
+ * This type is used in the preliminary phase to request specific schema
+ * definitions from components.schemas for review or complementary generation.
+ *
+ * @author Samchon
+ */
+export interface IAutoBePreliminaryGetInterfaceSchemas {
+  /**
+   * Type discriminator for the request.
+   *
+   * Determines which action to perform: preliminary data retrieval or actual
+   * task execution. Value "getInterfaceSchemas" indicates this is a preliminary
+   * data request for interface schemas.
+   */
+  type: "getInterfaceSchemas";
+
+  /**
+   * List of schema type names to retrieve.
+   *
+   * Schema names from the OpenAPI components.schemas section (e.g., "IUser",
+   * "IUser.ICreate", "IPost.IUpdate").
+   *
+   * CRITICAL: DO NOT request the same type names that you have already
+   * requested in previous calls.
+   */
+  typeNames: string[] & tags.MinItems<1>;
+}

package/src/orchestrate/common/structures/IAutoBePreliminaryGetPreviousAnalysisSections.ts

@@ -1,28 +1,28 @@
-import { tags } from "typia";
-
-/**
- * Request to retrieve individual analysis sections from previous iteration by
- * numeric ID.
- *
- * Same as {@link IAutoBePreliminaryGetAnalysisSections} but for sections from
- * the previous generation cycle, enabling comparison and consistency checks.
- *
- * @author Juntak
- */
-export interface IAutoBePreliminaryGetPreviousAnalysisSections {
-  /**
-   * Type discriminator for the request.
-   *
-   * Value "getPreviousAnalysisSections" indicates this is a preliminary data
-   * request for analysis sections from the previous iteration.
-   */
-  type: "getPreviousAnalysisSections";
-
-  /**
-   * List of section IDs to retrieve from the previous iteration.
-   *
-   * CRITICAL: DO NOT request the same section IDs that you have already
-   * requested in previous calls.
-   */
-  sectionIds: (number & tags.Type<"uint32">)[] & tags.MinItems<1>;
-}
+import { tags } from "typia";
+
+/**
+ * Request to retrieve individual analysis sections from previous iteration by
+ * numeric ID.
+ *
+ * Same as {@link IAutoBePreliminaryGetAnalysisSections} but for sections from
+ * the previous generation cycle, enabling comparison and consistency checks.
+ *
+ * @author Juntak
+ */
+export interface IAutoBePreliminaryGetPreviousAnalysisSections {
+  /**
+   * Type discriminator for the request.
+   *
+   * Value "getPreviousAnalysisSections" indicates this is a preliminary data
+   * request for analysis sections from the previous iteration.
+   */
+  type: "getPreviousAnalysisSections";
+
+  /**
+   * List of section IDs to retrieve from the previous iteration.
+   *
+   * CRITICAL: DO NOT request the same section IDs that you have already
+   * requested in previous calls.
+   */
+  sectionIds: (number & tags.Type<"uint32">)[] & tags.MinItems<1>;
+}

package/src/orchestrate/common/structures/IAutoBePreliminaryGetPreviousDatabaseSchemas.ts

@@ -1,88 +1,88 @@
-import { tags } from "typia";
-
-/**
- * Request to retrieve database schemas from a previous version.
- *
- * This type is used to load database schema definitions that were generated in
- * a **previous version** of the AutoBE generation pipeline. This is NOT about
- * re-requesting schemas within the same execution, but rather accessing
- * artifacts from an earlier version.
- *
- * **Use Case:** When regenerating or modifying the database schema based on
- * user change requests, agents need to reference the previously generated
- * database schemas to understand the existing database structure and what needs
- * to be modified.
- *
- * **Key Difference from `getDatabaseSchemas`:**
- *
- * - `getDatabaseSchemas`: Fetches schemas from the **current version** (the
- *   version being generated right now)
- * - `getPreviousDatabaseSchemas`: Fetches schemas from the **previous version**
- *   (the last successfully generated version)
- *
- * **Example Scenario:**
- *
- *     Initial generation:
- *     - DATABASE phase creates: users, posts, comments tables
- *     - Generation completes successfully
- *
- *     User: "Add email verification status to users"
- *
- *     Regeneration:
- *     - DATABASE phase starts regeneration
- *     - Calls getPreviousDatabaseSchemas(["users"])
- *       → Loads the previous version of users table schema
- *     - Creates new version with emailVerified field added
- *
- * **Waterfall + Spiral Pattern:**
- *
- * This aligns with AutoBE's regeneration cycles where:
- *
- * - Compilation failures trigger regeneration with corrections
- * - User modifications trigger new versions
- * - Previous schemas serve as reference for incremental changes
- *
- * @author Samchon
- */
-export interface IAutoBePreliminaryGetPreviousDatabaseSchemas {
-  /**
-   * Type discriminator for the request.
-   *
-   * Determines which action to perform: preliminary data retrieval or actual
-   * task execution. Value "getPreviousDatabaseSchemas" indicates this is a
-   * preliminary data request for database schemas from a previous version.
-   */
-  type: "getPreviousDatabaseSchemas";
-
-  /**
-   * List of database table names to retrieve from the previous version.
-   *
-   * These are table schema names that were generated in a previous version and
-   * are needed as reference context for the current regeneration.
-   *
-   * **Important Notes:**
-   *
-   * - These schemas MUST exist in the previous version
-   * - This function is only available when a previous version exists
-   * - Used for reference/comparison, not for re-requesting within same execution
-   * - Table names are in snake_case (e.g., "shopping_sale", "bbs_article")
-   *
-   * **When This Function is Available:**
-   *
-   * - When a previous version exists
-   * - When user requests modifications to existing database schema
-   * - During correction/regeneration cycles that need previous schema context
-   *
-   * **When This Function is NOT Available:**
-   *
-   * - During initial generation (no previous version exists)
-   * - No previous database schemas available for this orchestration task
-   *
-   * **Example Table Names:**
-   *
-   * - "users", "posts", "comments"
-   * - "shopping_sales", "shopping_orders", "shopping_products"
-   * - "bbs_articles", "bbs_article_files"
-   */
-  schemaNames: string[] & tags.MinItems<1>;
-}
+import { tags } from "typia";
+
+/**
+ * Request to retrieve database schemas from a previous version.
+ *
+ * This type is used to load database schema definitions that were generated in
+ * a **previous version** of the AutoBE generation pipeline. This is NOT about
+ * re-requesting schemas within the same execution, but rather accessing
+ * artifacts from an earlier version.
+ *
+ * **Use Case:** When regenerating or modifying the database schema based on
+ * user change requests, agents need to reference the previously generated
+ * database schemas to understand the existing database structure and what needs
+ * to be modified.
+ *
+ * **Key Difference from `getDatabaseSchemas`:**
+ *
+ * - `getDatabaseSchemas`: Fetches schemas from the **current version** (the
+ *   version being generated right now)
+ * - `getPreviousDatabaseSchemas`: Fetches schemas from the **previous version**
+ *   (the last successfully generated version)
+ *
+ * **Example Scenario:**
+ *
+ *     Initial generation:
+ *     - DATABASE phase creates: users, posts, comments tables
+ *     - Generation completes successfully
+ *
+ *     User: "Add email verification status to users"
+ *
+ *     Regeneration:
+ *     - DATABASE phase starts regeneration
+ *     - Calls getPreviousDatabaseSchemas(["users"])
+ *       → Loads the previous version of users table schema
+ *     - Creates new version with emailVerified field added
+ *
+ * **Waterfall + Spiral Pattern:**
+ *
+ * This aligns with AutoBE's regeneration cycles where:
+ *
+ * - Compilation failures trigger regeneration with corrections
+ * - User modifications trigger new versions
+ * - Previous schemas serve as reference for incremental changes
+ *
+ * @author Samchon
+ */
+export interface IAutoBePreliminaryGetPreviousDatabaseSchemas {
+  /**
+   * Type discriminator for the request.
+   *
+   * Determines which action to perform: preliminary data retrieval or actual
+   * task execution. Value "getPreviousDatabaseSchemas" indicates this is a
+   * preliminary data request for database schemas from a previous version.
+   */
+  type: "getPreviousDatabaseSchemas";
+
+  /**
+   * List of database table names to retrieve from the previous version.
+   *
+   * These are table schema names that were generated in a previous version and
+   * are needed as reference context for the current regeneration.
+   *
+   * **Important Notes:**
+   *
+   * - These schemas MUST exist in the previous version
+   * - This function is only available when a previous version exists
+   * - Used for reference/comparison, not for re-requesting within same execution
+   * - Table names are in snake_case (e.g., "shopping_sale", "bbs_article")
+   *
+   * **When This Function is Available:**
+   *
+   * - When a previous version exists
+   * - When user requests modifications to existing database schema
+   * - During correction/regeneration cycles that need previous schema context
+   *
+   * **When This Function is NOT Available:**
+   *
+   * - During initial generation (no previous version exists)
+   * - No previous database schemas available for this orchestration task
+   *
+   * **Example Table Names:**
+   *
+   * - "users", "posts", "comments"
+   * - "shopping_sales", "shopping_orders", "shopping_products"
+   * - "bbs_articles", "bbs_article_files"
+   */
+  schemaNames: string[] & tags.MinItems<1>;
+}

package/src/orchestrate/common/structures/IAutoBePreliminaryGetPreviousInterfaceOperations.ts

@@ -1,102 +1,102 @@
-import { AutoBeOpenApi } from "@autobe/interface";
-import { tags } from "typia";
-
-/**
- * Request to retrieve interface operations from a previous version.
- *
- * This type is used to load API operation definitions that were generated in a
- * **previous version** of the AutoBE generation pipeline. This is NOT about
- * re-requesting operations within the same execution, but rather accessing
- * artifacts from an earlier version.
- *
- * **Use Case:** When regenerating or modifying API operations based on user
- * change requests, agents need to reference the previously generated operations
- * to understand the existing API design and what needs to be modified.
- *
- * **Key Difference from `getInterfaceOperations`:**
- *
- * - `getInterfaceOperations`: Fetches operations from the **current version**
- *   (the version being generated right now)
- * - `getPreviousInterfaceOperations`: Fetches operations from the **previous
- *   version** (the last successfully generated version)
- *
- * **Example Scenario:**
- *
- *     Initial generation:
- *     - INTERFACE phase creates: GET /users, POST /users, GET /users/{id}
- *     - Generation completes successfully
- *
- *     User: "Change user creation to require email verification"
- *
- *     Regeneration:
- *     - INTERFACE phase starts regeneration
- *     - Calls getPreviousInterfaceOperations([{method: "POST", path: "/users"}])
- *       → Loads the previous version of POST /users operation
- *     - Creates new version with emailVerification requirement in request body
- *
- * **Automatic Schema Loading:**
- *
- * When operations are loaded from the previous version, their associated
- * request/response body schemas are also referenced, providing complete context
- * for understanding the operation's data structures.
- *
- * **Waterfall + Spiral Pattern:**
- *
- * This aligns with AutoBE's regeneration cycles where:
- *
- * - Compilation failures trigger regeneration with corrections
- * - User modifications trigger new versions
- * - Previous operations serve as reference for incremental API changes
- *
- * @author Samchon
- */
-export interface IAutoBePreliminaryGetPreviousInterfaceOperations {
-  /**
-   * Type discriminator for the request.
-   *
-   * Determines which action to perform: preliminary data retrieval or actual
-   * task execution. Value "getPreviousInterfaceOperations" indicates this is a
-   * preliminary data request for interface operations from a previous version.
-   */
-  type: "getPreviousInterfaceOperations";
-
-  /**
-   * List of API operation endpoints to retrieve from the previous version.
-   *
-   * These are endpoint identifiers (method + path) that were generated in a
-   * previous version and are needed as reference context for the current
-   * regeneration.
-   *
-   * **Important Notes:**
-   *
-   * - These endpoints MUST exist in the previous version
-   * - This function is only available when a previous version exists
-   * - Used for reference/comparison, not for re-requesting within same execution
-   * - Each endpoint is identified by: `{method: "GET|POST|PUT|DELETE|PATCH",
-   *   path: "/api/path"}`
-   *
-   * **When This Function is Available:**
-   *
-   * - When a previous version exists
-   * - When user requests modifications to existing API operations
-   * - During correction/regeneration cycles that need previous operation context
-   *
-   * **When This Function is NOT Available:**
-   *
-   * - During initial generation (no previous version exists)
-   * - No previous interface operations available for this orchestration task
-   *
-   * **Endpoint Format:**
-   *
-   * - Method: HTTP verb in uppercase (e.g., "GET", "POST", "PUT", "DELETE",
-   *   "PATCH")
-   * - Path: OpenAPI path with parameters (e.g., "/users/{id}", "/posts")
-   *
-   * **Example Endpoints:**
-   *
-   * - `{method: "GET", path: "/users/{id}"}`
-   * - `{method: "POST", path: "/shoppings/orders"}`
-   * - `{method: "PATCH", path: "/bbs/articles"}`
-   */
-  endpoints: AutoBeOpenApi.IEndpoint[] & tags.MinItems<1>;
-}
+import { AutoBeOpenApi } from "@autobe/interface";
+import { tags } from "typia";
+
+/**
+ * Request to retrieve interface operations from a previous version.
+ *
+ * This type is used to load API operation definitions that were generated in a
+ * **previous version** of the AutoBE generation pipeline. This is NOT about
+ * re-requesting operations within the same execution, but rather accessing
+ * artifacts from an earlier version.
+ *
+ * **Use Case:** When regenerating or modifying API operations based on user
+ * change requests, agents need to reference the previously generated operations
+ * to understand the existing API design and what needs to be modified.
+ *
+ * **Key Difference from `getInterfaceOperations`:**
+ *
+ * - `getInterfaceOperations`: Fetches operations from the **current version**
+ *   (the version being generated right now)
+ * - `getPreviousInterfaceOperations`: Fetches operations from the **previous
+ *   version** (the last successfully generated version)
+ *
+ * **Example Scenario:**
+ *
+ *     Initial generation:
+ *     - INTERFACE phase creates: GET /users, POST /users, GET /users/{id}
+ *     - Generation completes successfully
+ *
+ *     User: "Change user creation to require email verification"
+ *
+ *     Regeneration:
+ *     - INTERFACE phase starts regeneration
+ *     - Calls getPreviousInterfaceOperations([{method: "POST", path: "/users"}])
+ *       → Loads the previous version of POST /users operation
+ *     - Creates new version with emailVerification requirement in request body
+ *
+ * **Automatic Schema Loading:**
+ *
+ * When operations are loaded from the previous version, their associated
+ * request/response body schemas are also referenced, providing complete context
+ * for understanding the operation's data structures.
+ *
+ * **Waterfall + Spiral Pattern:**
+ *
+ * This aligns with AutoBE's regeneration cycles where:
+ *
+ * - Compilation failures trigger regeneration with corrections
+ * - User modifications trigger new versions
+ * - Previous operations serve as reference for incremental API changes
+ *
+ * @author Samchon
+ */
+export interface IAutoBePreliminaryGetPreviousInterfaceOperations {
+  /**
+   * Type discriminator for the request.
+   *
+   * Determines which action to perform: preliminary data retrieval or actual
+   * task execution. Value "getPreviousInterfaceOperations" indicates this is a
+   * preliminary data request for interface operations from a previous version.
+   */
+  type: "getPreviousInterfaceOperations";
+
+  /**
+   * List of API operation endpoints to retrieve from the previous version.
+   *
+   * These are endpoint identifiers (method + path) that were generated in a
+   * previous version and are needed as reference context for the current
+   * regeneration.
+   *
+   * **Important Notes:**
+   *
+   * - These endpoints MUST exist in the previous version
+   * - This function is only available when a previous version exists
+   * - Used for reference/comparison, not for re-requesting within same execution
+   * - Each endpoint is identified by: `{method: "GET|POST|PUT|DELETE|PATCH",
+   *   path: "/api/path"}`
+   *
+   * **When This Function is Available:**
+   *
+   * - When a previous version exists
+   * - When user requests modifications to existing API operations
+   * - During correction/regeneration cycles that need previous operation context
+   *
+   * **When This Function is NOT Available:**
+   *
+   * - During initial generation (no previous version exists)
+   * - No previous interface operations available for this orchestration task
+   *
+   * **Endpoint Format:**
+   *
+   * - Method: HTTP verb in uppercase (e.g., "GET", "POST", "PUT", "DELETE",
+   *   "PATCH")
+   * - Path: OpenAPI path with parameters (e.g., "/users/{id}", "/posts")
+   *
+   * **Example Endpoints:**
+   *
+   * - `{method: "GET", path: "/users/{id}"}`
+   * - `{method: "POST", path: "/shoppings/orders"}`
+   * - `{method: "PATCH", path: "/bbs/articles"}`
+   */
+  endpoints: AutoBeOpenApi.IEndpoint[] & tags.MinItems<1>;
+}