@autobe/agent 0.30.0-dev.20260315 → 0.30.1

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

@@ -1,144 +1,144 @@
-import { AutoBeDatabaseSchemaDefinition } from "@autobe/interface";
-
-import { IAutoBePreliminaryGetAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetAnalysisSections";
-import { IAutoBePreliminaryGetPreviousAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetPreviousAnalysisSections";
-import { IAutoBePreliminaryGetPreviousDatabaseSchemas } from "../../common/structures/IAutoBePreliminaryGetPreviousDatabaseSchemas";
-
-export interface IAutoBeDatabaseSchemaApplication {
-  /**
-   * Process schema generation task or preliminary data requests.
-   *
-   * Generates database models for the target component following normalization
-   * principles and database design best practices.
-   *
-   * @param props Request containing either preliminary data request or complete
-   *   task
-   */
-  process(props: IAutoBeDatabaseSchemaApplication.IProps): void;
-}
-export namespace IAutoBeDatabaseSchemaApplication {
-  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,
-     * getPreviousDatabaseSchemas) or final schema generation (complete). When
-     * preliminary returns empty array, that type is removed from the union,
-     * physically preventing repeated calls.
-     */
-    request:
-      | IComplete
-      | IAutoBePreliminaryGetAnalysisSections
-      | IAutoBePreliminaryGetPreviousAnalysisSections
-      | IAutoBePreliminaryGetPreviousDatabaseSchemas;
-  }
-
-  /**
-   * Request to generate database schema models.
-   *
-   * Executes schema generation to create production-ready database models
-   * following normalization principles, relationship patterns, and indexing
-   * strategies.
-   */
-  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";
-
-    /**
-     * Strategic database design analysis and planning.
-     *
-     * Contains the database architecture strategy for the target table and any
-     * child tables needed for First Normal Form (1NF) compliance, including
-     * structure, relationships, normalization approach, indexing strategies,
-     * and business requirement mapping. This planning phase defines the
-     * blueprint for the model implementations.
-     *
-     * Key planning aspects:
-     *
-     * - Assignment validation: Extract targetTable as the assignment
-     * - Target table: The primary table matching targetTable is mandatory
-     * - Child tables: Additional tables to decompose repeating groups or
-     *   non-atomic values into separate normalized tables (1NF compliance)
-     * - Child table naming: Must use singular form of targetTable as prefix
-     *   (e.g., for "shopping_orders": "shopping_order_items")
-     * - Other tables: Identify existing tables from otherComponents for foreign
-     *   key relationships — never recreate them
-     * - Normalization: Strict adherence to 1NF, 2NF, 3NF principles
-     * - Snapshot architecture: Design for historical data preservation
-     * - Junction tables: Plan M:N relationships with proper naming
-     *   ({table1}_{table2})
-     * - Materialized views: Identify needs for mv_ prefixed denormalized tables
-     */
-    plan: string;
-
-    /**
-     * Schema definition containing the single target table model and any newly
-     * discovered table designs.
-     *
-     * The definition carries exactly one
-     * {@link AutoBeDatabaseSchemaDefinition.model} — the target table assigned
-     * to this call — so that the output stays within the LLM's maximum output
-     * token limit. If normalization (e.g. 1NF decomposition) requires
-     * additional child tables, declare them in
-     * {@link AutoBeDatabaseSchemaDefinition.newDesigns} as lightweight name +
-     * description pairs; they will be generated by their own dedicated pipeline
-     * calls.
-     *
-     * Model implementation requirements:
-     *
-     * - Primary keys: Always UUID type with field name "id"
-     * - Foreign keys: Proper IRelation configurations for all relationships
-     * - Business fields: Only raw data fields - no calculated or derived values
-     * - Data types: Limited to uuid, string, int, double, datetime, boolean, uri
-     * - Relationships: Correct patterns for 1:1, 1:N, and M:N
-     * - Indexes:
-     *
-     *   - UniqueIndexes: Business constraints and composite unique keys
-     *   - PlainIndexes: Multi-column query optimization (never single FK)
-     *   - GinIndexes: Full-text search on appropriate string fields
-     * - Materialized views: Tables prefixed with "mv_" have material flag set
-     * - Documentation: Comprehensive English descriptions with business context
-     *
-     * Quality standards:
-     *
-     * - Strict adherence to 3NF (Third Normal Form)
-     * - No denormalization except in materialized views (mv_ tables)
-     * - All foreign keys reference valid existing tables
-     * - Consistent created_at, updated_at, deleted_at patterns
-     * - Proper historical data preservation where needed
-     * - Optimized index strategy for expected query patterns
-     */
-    definition: AutoBeDatabaseSchemaDefinition;
-  }
-}
+import { AutoBeDatabaseSchemaDefinition } from "@autobe/interface";
+
+import { IAutoBePreliminaryGetAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetAnalysisSections";
+import { IAutoBePreliminaryGetPreviousAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetPreviousAnalysisSections";
+import { IAutoBePreliminaryGetPreviousDatabaseSchemas } from "../../common/structures/IAutoBePreliminaryGetPreviousDatabaseSchemas";
+
+export interface IAutoBeDatabaseSchemaApplication {
+  /**
+   * Process schema generation task or preliminary data requests.
+   *
+   * Generates database models for the target component following normalization
+   * principles and database design best practices.
+   *
+   * @param props Request containing either preliminary data request or complete
+   *   task
+   */
+  process(props: IAutoBeDatabaseSchemaApplication.IProps): void;
+}
+export namespace IAutoBeDatabaseSchemaApplication {
+  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,
+     * getPreviousDatabaseSchemas) or final schema generation (complete). When
+     * preliminary returns empty array, that type is removed from the union,
+     * physically preventing repeated calls.
+     */
+    request:
+      | IComplete
+      | IAutoBePreliminaryGetAnalysisSections
+      | IAutoBePreliminaryGetPreviousAnalysisSections
+      | IAutoBePreliminaryGetPreviousDatabaseSchemas;
+  }
+
+  /**
+   * Request to generate database schema models.
+   *
+   * Executes schema generation to create production-ready database models
+   * following normalization principles, relationship patterns, and indexing
+   * strategies.
+   */
+  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";
+
+    /**
+     * Strategic database design analysis and planning.
+     *
+     * Contains the database architecture strategy for the target table and any
+     * child tables needed for First Normal Form (1NF) compliance, including
+     * structure, relationships, normalization approach, indexing strategies,
+     * and business requirement mapping. This planning phase defines the
+     * blueprint for the model implementations.
+     *
+     * Key planning aspects:
+     *
+     * - Assignment validation: Extract targetTable as the assignment
+     * - Target table: The primary table matching targetTable is mandatory
+     * - Child tables: Additional tables to decompose repeating groups or
+     *   non-atomic values into separate normalized tables (1NF compliance)
+     * - Child table naming: Must use singular form of targetTable as prefix
+     *   (e.g., for "shopping_orders": "shopping_order_items")
+     * - Other tables: Identify existing tables from otherComponents for foreign
+     *   key relationships — never recreate them
+     * - Normalization: Strict adherence to 1NF, 2NF, 3NF principles
+     * - Snapshot architecture: Design for historical data preservation
+     * - Junction tables: Plan M:N relationships with proper naming
+     *   ({table1}_{table2})
+     * - Materialized views: Identify needs for mv_ prefixed denormalized tables
+     */
+    plan: string;
+
+    /**
+     * Schema definition containing the single target table model and any newly
+     * discovered table designs.
+     *
+     * The definition carries exactly one
+     * {@link AutoBeDatabaseSchemaDefinition.model} — the target table assigned
+     * to this call — so that the output stays within the LLM's maximum output
+     * token limit. If normalization (e.g. 1NF decomposition) requires
+     * additional child tables, declare them in
+     * {@link AutoBeDatabaseSchemaDefinition.newDesigns} as lightweight name +
+     * description pairs; they will be generated by their own dedicated pipeline
+     * calls.
+     *
+     * Model implementation requirements:
+     *
+     * - Primary keys: Always UUID type with field name "id"
+     * - Foreign keys: Proper IRelation configurations for all relationships
+     * - Business fields: Only raw data fields - no calculated or derived values
+     * - Data types: Limited to uuid, string, int, double, datetime, boolean, uri
+     * - Relationships: Correct patterns for 1:1, 1:N, and M:N
+     * - Indexes:
+     *
+     *   - UniqueIndexes: Business constraints and composite unique keys
+     *   - PlainIndexes: Multi-column query optimization (never single FK)
+     *   - GinIndexes: Full-text search on appropriate string fields
+     * - Materialized views: Tables prefixed with "mv_" have material flag set
+     * - Documentation: Comprehensive English descriptions with business context
+     *
+     * Quality standards:
+     *
+     * - Strict adherence to 3NF (Third Normal Form)
+     * - No denormalization except in materialized views (mv_ tables)
+     * - All foreign keys reference valid existing tables
+     * - Consistent created_at, updated_at, deleted_at patterns
+     * - Proper historical data preservation where needed
+     * - Optimized index strategy for expected query patterns
+     */
+    definition: AutoBeDatabaseSchemaDefinition;
+  }
+}

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

@@ -1,138 +1,138 @@
-import { AutoBeDatabaseSchemaDefinition } 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 IAutoBeDatabaseSchemaReviewApplication {
-  /**
-   * Process schema review task or preliminary data requests.
-   *
-   * Reviews generated database models to validate normalization, relationships,
-   * indexes, and business alignment, producing necessary modifications.
-   *
-   * @param props Request containing either preliminary data request or complete
-   *   task
-   */
-  process(props: IAutoBeDatabaseSchemaReviewApplication.IProps): void;
-}
-export namespace IAutoBeDatabaseSchemaReviewApplication {
-  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 review (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 review and refine database schema models.
-   *
-   * Executes comprehensive schema review to validate design quality and
-   * identify necessary improvements for normalization, relationships, and
-   * performance optimization.
-   */
-  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";
-
-    /**
-     * Comprehensive review analysis of the schema.
-     *
-     * Contains detailed evaluation of the schema design including:
-     *
-     * - Normalization validation: Confirms 3NF compliance and proper data
-     *   structure
-     * - Relationship integrity: Validates foreign key references and cardinality
-     * - Performance optimization: Reviews indexing strategy and query patterns
-     * - Business logic alignment: Ensures schema supports all use cases
-     * - Naming conventions: Verifies consistent naming patterns
-     * - Data type consistency: Confirms appropriate field types
-     * - Temporal field handling: Validates audit trail implementation
-     *
-     * The review identifies potential issues and confirms adherence to best
-     * practices before final implementation.
-     */
-    review: string;
-
-    /**
-     * Strategic database design plan.
-     *
-     * Contains the original planning document outlining the database
-     * architecture strategy including table structures, relationships,
-     * normalization approach, and business requirement mapping. This plan
-     * serves as the blueprint for validating the implemented schema.
-     *
-     * Planning components:
-     *
-     * - Business requirements: Mapping of business needs to database structures
-     * - Table design: Entity definitions and attribute specifications
-     * - Relationship strategy: Cardinality and referential integrity planning
-     * - Normalization approach: Application of 1NF, 2NF, 3NF principles
-     * - Performance considerations: Index strategy and query optimization
-     * - Snapshot architecture: Temporal data handling and audit requirements
-     * - Materialized views: Denormalization strategy for performance
-     */
-    plan: string;
-
-    /**
-     * Corrected schema definition based on review feedback, or null if no
-     * changes are needed.
-     *
-     * When not null, the definition carries exactly one corrected
-     * {@link AutoBeDatabaseSchemaDefinition.model} for the reviewed target table
-     * so that the output stays within the LLM's maximum output token limit. If
-     * the review determines that additional child tables are required (e.g. 1NF
-     * decomposition), they are declared in
-     * {@link AutoBeDatabaseSchemaDefinition.newDesigns} as lightweight name +
-     * description pairs and will be generated by their own dedicated pipeline
-     * calls.
-     *
-     * If null, the original model remains unchanged from the original schema.
-     * If not null, the modification must resolve issues identified in the
-     * review.
-     */
-    content: AutoBeDatabaseSchemaDefinition | null;
-  }
-}
+import { AutoBeDatabaseSchemaDefinition } 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 IAutoBeDatabaseSchemaReviewApplication {
+  /**
+   * Process schema review task or preliminary data requests.
+   *
+   * Reviews generated database models to validate normalization, relationships,
+   * indexes, and business alignment, producing necessary modifications.
+   *
+   * @param props Request containing either preliminary data request or complete
+   *   task
+   */
+  process(props: IAutoBeDatabaseSchemaReviewApplication.IProps): void;
+}
+export namespace IAutoBeDatabaseSchemaReviewApplication {
+  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 review (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 review and refine database schema models.
+   *
+   * Executes comprehensive schema review to validate design quality and
+   * identify necessary improvements for normalization, relationships, and
+   * performance optimization.
+   */
+  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";
+
+    /**
+     * Comprehensive review analysis of the schema.
+     *
+     * Contains detailed evaluation of the schema design including:
+     *
+     * - Normalization validation: Confirms 3NF compliance and proper data
+     *   structure
+     * - Relationship integrity: Validates foreign key references and cardinality
+     * - Performance optimization: Reviews indexing strategy and query patterns
+     * - Business logic alignment: Ensures schema supports all use cases
+     * - Naming conventions: Verifies consistent naming patterns
+     * - Data type consistency: Confirms appropriate field types
+     * - Temporal field handling: Validates audit trail implementation
+     *
+     * The review identifies potential issues and confirms adherence to best
+     * practices before final implementation.
+     */
+    review: string;
+
+    /**
+     * Strategic database design plan.
+     *
+     * Contains the original planning document outlining the database
+     * architecture strategy including table structures, relationships,
+     * normalization approach, and business requirement mapping. This plan
+     * serves as the blueprint for validating the implemented schema.
+     *
+     * Planning components:
+     *
+     * - Business requirements: Mapping of business needs to database structures
+     * - Table design: Entity definitions and attribute specifications
+     * - Relationship strategy: Cardinality and referential integrity planning
+     * - Normalization approach: Application of 1NF, 2NF, 3NF principles
+     * - Performance considerations: Index strategy and query optimization
+     * - Snapshot architecture: Temporal data handling and audit requirements
+     * - Materialized views: Denormalization strategy for performance
+     */
+    plan: string;
+
+    /**
+     * Corrected schema definition based on review feedback, or null if no
+     * changes are needed.
+     *
+     * When not null, the definition carries exactly one corrected
+     * {@link AutoBeDatabaseSchemaDefinition.model} for the reviewed target table
+     * so that the output stays within the LLM's maximum output token limit. If
+     * the review determines that additional child tables are required (e.g. 1NF
+     * decomposition), they are declared in
+     * {@link AutoBeDatabaseSchemaDefinition.newDesigns} as lightweight name +
+     * description pairs and will be generated by their own dedicated pipeline
+     * calls.
+     *
+     * If null, the original model remains unchanged from the original schema.
+     * If not null, the modification must resolve issues identified in the
+     * review.
+     */
+    content: AutoBeDatabaseSchemaDefinition | null;
+  }
+}