@autobe/agent 0.30.0-dev.20260315 → 0.30.0

package/src/orchestrate/prisma/structures/IAutoBeDatabaseComponentReviewApplication.ts

@@ -1,151 +1,151 @@
-import { AutoBeDatabaseComponentTableRevise } from "@autobe/interface";
-
-import { IAutoBePreliminaryGetAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetAnalysisSections";
-import { IAutoBePreliminaryGetPreviousAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetPreviousAnalysisSections";
-import { IAutoBePreliminaryGetPreviousDatabaseSchemas } from "../../common/structures/IAutoBePreliminaryGetPreviousDatabaseSchemas";
-
-export interface IAutoBeDatabaseComponentReviewApplication {
-  /**
-   * Analyze requirements and review the component's table list.
-   *
-   * Your PRIMARY task is to deeply analyze user requirements and ensure
-   * complete table coverage for all features in this component's domain. Review
-   * existing tables and identify necessary modifications using create, update,
-   * or erase operations.
-   *
-   * ALWAYS fetch analysis sections first using `getAnalysisSections` to
-   * understand what features this component's domain needs to support, then
-   * systematically verify table coverage and apply corrections.
-   *
-   * @param props Request containing either preliminary data request or complete
-   *   task with table revisions
-   */
-  process(props: IAutoBeDatabaseComponentReviewApplication.IProps): void;
-}
-
-export namespace IAutoBeDatabaseComponentReviewApplication {
-  export interface IProps {
-    /**
-     * Reflect on requirements analysis before acting.
-     *
-     * For preliminary requests (getAnalysisSections,
-     * getPreviousAnalysisSections, getPreviousDatabaseSchemas):
-     *
-     * - What requirements documents do you need to analyze this component?
-     * - Which features in this domain need to be understood?
-     *
-     * For completion (complete):
-     *
-     * - What requirements did you analyze?
-     * - How many revisions are you making and why?
-     * - Summarize the requirements-to-revisions mapping.
-     */
-    thinking: string;
-
-    /**
-     * Request type discriminator.
-     *
-     * Use preliminary requests (getAnalysisSections, etc.) to fetch
-     * requirements documents. Use complete to submit table revisions after
-     * thorough requirements analysis.
-     */
-    request:
-      | IComplete
-      | IAutoBePreliminaryGetAnalysisSections
-      | IAutoBePreliminaryGetPreviousAnalysisSections
-      | IAutoBePreliminaryGetPreviousDatabaseSchemas;
-  }
-
-  /** Submit table revisions after requirements analysis. */
-  export interface IComplete {
-    /** Type discriminator. Value "complete" indicates final submission. */
-    type: "complete";
-
-    /**
-     * Requirements coverage analysis.
-     *
-     * Document how you analyzed requirements and mapped them to table
-     * modifications:
-     *
-     * - What features does this domain support?
-     * - What data storage needs does each feature have?
-     * - What tables are missing to fulfill these requirements?
-     * - What existing tables need renaming or removal?
-     *
-     * Be specific - reference actual requirements and explain the
-     * requirements-to-revisions mapping.
-     */
-    review: string;
-
-    /**
-     * Array of table revision operations.
-     *
-     * Include all create, update, and erase operations identified during
-     * review. Each operation must include a reason explaining why the change is
-     * necessary.
-     *
-     * ## Operation Types:
-     *
-     * ### Create - Add missing tables
-     *
-     * Use when a table is needed to fulfill requirements but doesn't exist.
-     *
-     * ```typescript
-     * {
-     *   "type": "create",
-     *   "reason": "Requirement 3.2 specifies order cancellation tracking",
-     *   "table": "order_cancellations",
-     *   "description": "Stores cancellation records with reasons and timestamps"
-     * }
-     * ```
-     *
-     * ### Update - Rename tables
-     *
-     * Use when a table has naming convention issues.
-     *
-     * ```typescript
-     * {
-     *   "type": "update",
-     *   "reason": "Table name violates snake_case convention",
-     *   "original": "orderCancel",
-     *   "updated": "order_cancellations",
-     *   "description": "Stores cancellation records with reasons and timestamps"
-     * }
-     * ```
-     *
-     * ### Erase - Remove tables
-     *
-     * Use when a table belongs to another domain or is unnecessary.
-     *
-     * ```typescript
-     * {
-     *   "type": "erase",
-     *   "reason": "Table belongs to Actors component, not Orders",
-     *   "table": "shopping_customers"
-     * }
-     * ```
-     *
-     * ## Constraints:
-     *
-     * - Only CREATE tables that CLEARLY belong to THIS component's domain
-     * - If uncertain about domain ownership → DO NOT CREATE
-     * - Each operation must have a clear, requirement-based reason
-     * - Empty array is valid if no modifications are needed
-     *
-     * ## Validation Rules:
-     *
-     * - CREATE/UPDATE table names are checked against "Tables in Other
-     *   Components"
-     * - If the table name already exists in another component → validation FAILS
-     * - Always check "Tables in Other Components" before CREATE/UPDATE operations
-     * - Your revises only affect Target Component, never other components' tables
-     *
-     * ## Naming Conventions:
-     *
-     * - Snake case: `user_profiles` not `userProfiles`
-     * - Plural form: `users` not `user`
-     * - Domain prefix: `shopping_customers`
-     */
-    revises: AutoBeDatabaseComponentTableRevise[];
-  }
-}
+import { AutoBeDatabaseComponentTableRevise } from "@autobe/interface";
+
+import { IAutoBePreliminaryGetAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetAnalysisSections";
+import { IAutoBePreliminaryGetPreviousAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetPreviousAnalysisSections";
+import { IAutoBePreliminaryGetPreviousDatabaseSchemas } from "../../common/structures/IAutoBePreliminaryGetPreviousDatabaseSchemas";
+
+export interface IAutoBeDatabaseComponentReviewApplication {
+  /**
+   * Analyze requirements and review the component's table list.
+   *
+   * Your PRIMARY task is to deeply analyze user requirements and ensure
+   * complete table coverage for all features in this component's domain. Review
+   * existing tables and identify necessary modifications using create, update,
+   * or erase operations.
+   *
+   * ALWAYS fetch analysis sections first using `getAnalysisSections` to
+   * understand what features this component's domain needs to support, then
+   * systematically verify table coverage and apply corrections.
+   *
+   * @param props Request containing either preliminary data request or complete
+   *   task with table revisions
+   */
+  process(props: IAutoBeDatabaseComponentReviewApplication.IProps): void;
+}
+
+export namespace IAutoBeDatabaseComponentReviewApplication {
+  export interface IProps {
+    /**
+     * Reflect on requirements analysis before acting.
+     *
+     * For preliminary requests (getAnalysisSections,
+     * getPreviousAnalysisSections, getPreviousDatabaseSchemas):
+     *
+     * - What requirements documents do you need to analyze this component?
+     * - Which features in this domain need to be understood?
+     *
+     * For completion (complete):
+     *
+     * - What requirements did you analyze?
+     * - How many revisions are you making and why?
+     * - Summarize the requirements-to-revisions mapping.
+     */
+    thinking: string;
+
+    /**
+     * Request type discriminator.
+     *
+     * Use preliminary requests (getAnalysisSections, etc.) to fetch
+     * requirements documents. Use complete to submit table revisions after
+     * thorough requirements analysis.
+     */
+    request:
+      | IComplete
+      | IAutoBePreliminaryGetAnalysisSections
+      | IAutoBePreliminaryGetPreviousAnalysisSections
+      | IAutoBePreliminaryGetPreviousDatabaseSchemas;
+  }
+
+  /** Submit table revisions after requirements analysis. */
+  export interface IComplete {
+    /** Type discriminator. Value "complete" indicates final submission. */
+    type: "complete";
+
+    /**
+     * Requirements coverage analysis.
+     *
+     * Document how you analyzed requirements and mapped them to table
+     * modifications:
+     *
+     * - What features does this domain support?
+     * - What data storage needs does each feature have?
+     * - What tables are missing to fulfill these requirements?
+     * - What existing tables need renaming or removal?
+     *
+     * Be specific - reference actual requirements and explain the
+     * requirements-to-revisions mapping.
+     */
+    review: string;
+
+    /**
+     * Array of table revision operations.
+     *
+     * Include all create, update, and erase operations identified during
+     * review. Each operation must include a reason explaining why the change is
+     * necessary.
+     *
+     * ## Operation Types:
+     *
+     * ### Create - Add missing tables
+     *
+     * Use when a table is needed to fulfill requirements but doesn't exist.
+     *
+     * ```typescript
+     * {
+     *   "type": "create",
+     *   "reason": "Requirement 3.2 specifies order cancellation tracking",
+     *   "table": "order_cancellations",
+     *   "description": "Stores cancellation records with reasons and timestamps"
+     * }
+     * ```
+     *
+     * ### Update - Rename tables
+     *
+     * Use when a table has naming convention issues.
+     *
+     * ```typescript
+     * {
+     *   "type": "update",
+     *   "reason": "Table name violates snake_case convention",
+     *   "original": "orderCancel",
+     *   "updated": "order_cancellations",
+     *   "description": "Stores cancellation records with reasons and timestamps"
+     * }
+     * ```
+     *
+     * ### Erase - Remove tables
+     *
+     * Use when a table belongs to another domain or is unnecessary.
+     *
+     * ```typescript
+     * {
+     *   "type": "erase",
+     *   "reason": "Table belongs to Actors component, not Orders",
+     *   "table": "shopping_customers"
+     * }
+     * ```
+     *
+     * ## Constraints:
+     *
+     * - Only CREATE tables that CLEARLY belong to THIS component's domain
+     * - If uncertain about domain ownership → DO NOT CREATE
+     * - Each operation must have a clear, requirement-based reason
+     * - Empty array is valid if no modifications are needed
+     *
+     * ## Validation Rules:
+     *
+     * - CREATE/UPDATE table names are checked against "Tables in Other
+     *   Components"
+     * - If the table name already exists in another component → validation FAILS
+     * - Always check "Tables in Other Components" before CREATE/UPDATE operations
+     * - Your revises only affect Target Component, never other components' tables
+     *
+     * ## Naming Conventions:
+     *
+     * - Snake case: `user_profiles` not `userProfiles`
+     * - Plural form: `users` not `user`
+     * - Domain prefix: `shopping_customers`
+     */
+    revises: AutoBeDatabaseComponentTableRevise[];
+  }
+}

package/src/orchestrate/prisma/structures/IAutoBeDatabaseCorrectApplication.ts

@@ -1,157 +1,157 @@
-import { AutoBeDatabase } from "@autobe/interface";
-
-import { IAutoBePreliminaryGetAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetAnalysisSections";
-import { IAutoBePreliminaryGetDatabaseSchemas } from "../../common/structures/IAutoBePreliminaryGetDatabaseSchemas";
-import { IAutoBePreliminaryGetPreviousAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetPreviousAnalysisSections";
-import { IAutoBePreliminaryGetPreviousDatabaseSchemas } from "../../common/structures/IAutoBePreliminaryGetPreviousDatabaseSchemas";
-
-export interface IAutoBeDatabaseCorrectApplication {
-  /**
-   * Process schema correction task or preliminary data requests.
-   *
-   * Fixes validation errors in specific database models while preserving all
-   * business logic and model descriptions. Returns ONLY corrected models.
-   *
-   * @param props Request containing either preliminary data request or complete
-   *   task
-   */
-  process(props: IAutoBeDatabaseCorrectApplication.IProps): void;
-}
-export namespace IAutoBeDatabaseCorrectApplication {
-  export interface IProps {
-    /**
-     * Think before you act.
-     *
-     * Before requesting preliminary data or completing your task, reflect on
-     * your current state and explain your reasoning:
-     *
-     * For preliminary requests (getAnalysisSections, getDatabaseSchemas, etc.):
-     *
-     * - What critical information is missing that you don't already have?
-     * - Why do you need it specifically right now?
-     * - Be brief - state the gap, don't list everything you have.
-     *
-     * For completion (complete):
-     *
-     * - What key assets did you acquire?
-     * - What did you accomplish?
-     * - Why is it sufficient to complete?
-     * - Summarize - don't enumerate every single item.
-     *
-     * This reflection helps you avoid duplicate requests and premature
-     * completion.
-     */
-    thinking: string;
-
-    /**
-     * Type discriminator for the request.
-     *
-     * Determines which action to perform: preliminary data retrieval
-     * (getAnalysisSections, getPreviousAnalysisSections, getDatabaseSchemas,
-     * getPreviousDatabaseSchemas) or final schema correction (complete). When
-     * preliminary returns empty array, that type is removed from the union,
-     * physically preventing repeated calls.
-     */
-    request:
-      | IComplete
-      | IAutoBePreliminaryGetAnalysisSections
-      | IAutoBePreliminaryGetDatabaseSchemas
-      | IAutoBePreliminaryGetPreviousAnalysisSections
-      | IAutoBePreliminaryGetPreviousDatabaseSchemas;
-  }
-
-  /**
-   * Request to fix validation errors in database models.
-   *
-   * Executes targeted error correction to resolve specific validation issues in
-   * affected models only. Applies minimal changes while preserving original
-   * design intent and business logic.
-   */
-  export interface IComplete {
-    /**
-     * Type discriminator for the request.
-     *
-     * Determines which action to perform: preliminary data retrieval or actual
-     * task execution. Value "complete" indicates this is the final task
-     * execution request.
-     */
-    type: "complete";
-
-    /**
-     * Detailed execution plan for fixing validation errors.
-     *
-     * Contains systematic reasoning and step-by-step error resolution approach
-     * for targeted model validation issues.
-     *
-     * Required planning content:
-     *
-     * 1. Error scope analysis:
-     *
-     *    - List all validation errors from IAutoBeDatabaseValidation.IError[]
-     *    - Extract unique table names to identify affected models
-     *    - Categorize errors by type (field duplications, references, types,
-     *         indexes)
-     *    - Identify which models need correction vs. remain unchanged
-     * 2. Targeted fix strategy:
-     *
-     *    - Focus ONLY on models mentioned in validation errors
-     *    - Outline minimal changes needed for each affected model
-     *    - Plan cross-model reference updates without modifying non-error models
-     *    - Ensure unchanged models maintain valid references to corrected models
-     * 3. Model-specific fix plan:
-     *
-     *    - Model-by-model modification plan for ONLY affected models
-     *    - Exact field additions, renames, or type corrections required
-     *    - Reference updates within corrected models only
-     *    - Index corrections limited to affected models
-     * 4. Minimal scope validation:
-     *
-     *    - Confirm which models will be included in output (error models only)
-     *    - List models that will remain unchanged in original schema
-     *    - Identify cross-model dependencies without including unchanged models
-     *    - Preserve all business logic within corrected models
-     * 5. Targeted impact assessment:
-     *
-     *    - Potential effects of fixes on unchanged models (reference validation)
-     *    - Verification points for corrected models only
-     *    - Ensure no new validation errors in targeted models
-     *    - Confirm minimal output scope compliance
-     */
-    planning: string;
-
-    /**
-     * Models with validation errors that need correction.
-     *
-     * Contains ONLY models mentioned in IAutoBeDatabaseValidation.IError[]
-     * array. Each model has specific validation errors requiring targeted
-     * correction. Models not mentioned in errors are excluded from this input.
-     *
-     * Expected validation issues:
-     *
-     * - Duplicate field/relation names within these specific models
-     * - Invalid foreign key references from these models to other models
-     * - Single foreign key fields in index arrays within these models
-     * - Invalid naming conventions within these specific models
-     * - Type validation errors in fields of these models
-     *
-     * Model content analysis:
-     *
-     * - Complete field definitions for each error model only
-     * - Relationships from these models (may reference unchanged models)
-     * - Indexes within these models that need correction
-     * - Business descriptions specific to these models
-     * - Cross-model references that need validation (read-only for targets)
-     *
-     * Processing notes:
-     *
-     * - Input contains ONLY models with validation errors
-     * - May reference other models not included in this input
-     * - Cross-model references must be validated but target models won't be
-     *   modified
-     * - Output should return corrected versions of ONLY these input models
-     * - All business logic and descriptions within these models must be preserved
-     * - Corrections must not break references from unchanged models
-     */
-    models: AutoBeDatabase.IModel[];
-  }
-}
+import { AutoBeDatabase } from "@autobe/interface";
+
+import { IAutoBePreliminaryGetAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetAnalysisSections";
+import { IAutoBePreliminaryGetDatabaseSchemas } from "../../common/structures/IAutoBePreliminaryGetDatabaseSchemas";
+import { IAutoBePreliminaryGetPreviousAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetPreviousAnalysisSections";
+import { IAutoBePreliminaryGetPreviousDatabaseSchemas } from "../../common/structures/IAutoBePreliminaryGetPreviousDatabaseSchemas";
+
+export interface IAutoBeDatabaseCorrectApplication {
+  /**
+   * Process schema correction task or preliminary data requests.
+   *
+   * Fixes validation errors in specific database models while preserving all
+   * business logic and model descriptions. Returns ONLY corrected models.
+   *
+   * @param props Request containing either preliminary data request or complete
+   *   task
+   */
+  process(props: IAutoBeDatabaseCorrectApplication.IProps): void;
+}
+export namespace IAutoBeDatabaseCorrectApplication {
+  export interface IProps {
+    /**
+     * Think before you act.
+     *
+     * Before requesting preliminary data or completing your task, reflect on
+     * your current state and explain your reasoning:
+     *
+     * For preliminary requests (getAnalysisSections, getDatabaseSchemas, etc.):
+     *
+     * - What critical information is missing that you don't already have?
+     * - Why do you need it specifically right now?
+     * - Be brief - state the gap, don't list everything you have.
+     *
+     * For completion (complete):
+     *
+     * - What key assets did you acquire?
+     * - What did you accomplish?
+     * - Why is it sufficient to complete?
+     * - Summarize - don't enumerate every single item.
+     *
+     * This reflection helps you avoid duplicate requests and premature
+     * completion.
+     */
+    thinking: string;
+
+    /**
+     * Type discriminator for the request.
+     *
+     * Determines which action to perform: preliminary data retrieval
+     * (getAnalysisSections, getPreviousAnalysisSections, getDatabaseSchemas,
+     * getPreviousDatabaseSchemas) or final schema correction (complete). When
+     * preliminary returns empty array, that type is removed from the union,
+     * physically preventing repeated calls.
+     */
+    request:
+      | IComplete
+      | IAutoBePreliminaryGetAnalysisSections
+      | IAutoBePreliminaryGetDatabaseSchemas
+      | IAutoBePreliminaryGetPreviousAnalysisSections
+      | IAutoBePreliminaryGetPreviousDatabaseSchemas;
+  }
+
+  /**
+   * Request to fix validation errors in database models.
+   *
+   * Executes targeted error correction to resolve specific validation issues in
+   * affected models only. Applies minimal changes while preserving original
+   * design intent and business logic.
+   */
+  export interface IComplete {
+    /**
+     * Type discriminator for the request.
+     *
+     * Determines which action to perform: preliminary data retrieval or actual
+     * task execution. Value "complete" indicates this is the final task
+     * execution request.
+     */
+    type: "complete";
+
+    /**
+     * Detailed execution plan for fixing validation errors.
+     *
+     * Contains systematic reasoning and step-by-step error resolution approach
+     * for targeted model validation issues.
+     *
+     * Required planning content:
+     *
+     * 1. Error scope analysis:
+     *
+     *    - List all validation errors from IAutoBeDatabaseValidation.IError[]
+     *    - Extract unique table names to identify affected models
+     *    - Categorize errors by type (field duplications, references, types,
+     *         indexes)
+     *    - Identify which models need correction vs. remain unchanged
+     * 2. Targeted fix strategy:
+     *
+     *    - Focus ONLY on models mentioned in validation errors
+     *    - Outline minimal changes needed for each affected model
+     *    - Plan cross-model reference updates without modifying non-error models
+     *    - Ensure unchanged models maintain valid references to corrected models
+     * 3. Model-specific fix plan:
+     *
+     *    - Model-by-model modification plan for ONLY affected models
+     *    - Exact field additions, renames, or type corrections required
+     *    - Reference updates within corrected models only
+     *    - Index corrections limited to affected models
+     * 4. Minimal scope validation:
+     *
+     *    - Confirm which models will be included in output (error models only)
+     *    - List models that will remain unchanged in original schema
+     *    - Identify cross-model dependencies without including unchanged models
+     *    - Preserve all business logic within corrected models
+     * 5. Targeted impact assessment:
+     *
+     *    - Potential effects of fixes on unchanged models (reference validation)
+     *    - Verification points for corrected models only
+     *    - Ensure no new validation errors in targeted models
+     *    - Confirm minimal output scope compliance
+     */
+    planning: string;
+
+    /**
+     * Models with validation errors that need correction.
+     *
+     * Contains ONLY models mentioned in IAutoBeDatabaseValidation.IError[]
+     * array. Each model has specific validation errors requiring targeted
+     * correction. Models not mentioned in errors are excluded from this input.
+     *
+     * Expected validation issues:
+     *
+     * - Duplicate field/relation names within these specific models
+     * - Invalid foreign key references from these models to other models
+     * - Single foreign key fields in index arrays within these models
+     * - Invalid naming conventions within these specific models
+     * - Type validation errors in fields of these models
+     *
+     * Model content analysis:
+     *
+     * - Complete field definitions for each error model only
+     * - Relationships from these models (may reference unchanged models)
+     * - Indexes within these models that need correction
+     * - Business descriptions specific to these models
+     * - Cross-model references that need validation (read-only for targets)
+     *
+     * Processing notes:
+     *
+     * - Input contains ONLY models with validation errors
+     * - May reference other models not included in this input
+     * - Cross-model references must be validated but target models won't be
+     *   modified
+     * - Output should return corrected versions of ONLY these input models
+     * - All business logic and descriptions within these models must be preserved
+     * - Corrections must not break references from unchanged models
+     */
+    models: AutoBeDatabase.IModel[];
+  }
+}