@autobe/agent 0.30.0-dev.20260315 → 0.30.1

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

@@ -1,153 +1,153 @@
-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 IAutoBeDatabaseAuthorizationReviewApplication {
-  /**
-   * Analyze requirements and review the single authorization component
-   * containing tables for ALL actors.
-   *
-   * Your PRIMARY task is to deeply analyze authentication requirements and
-   * ensure complete table coverage for EVERY actor type in the authorization
-   * component. The component contains tables for all actors
-   * (guest/member/admin), and you must verify that each actor has its required
-   * tables.
-   *
-   * ALWAYS fetch analysis sections first using `getAnalysisSections` to
-   * understand what authentication features are required, then systematically
-   * verify that EVERY actor has main actor table + session table, and apply
-   * corrections.
-   *
-   * @param props Request containing either preliminary data request or complete
-   *   task with table revisions for all actors
-   */
-  process(props: IAutoBeDatabaseAuthorizationReviewApplication.IProps): void;
-}
-
-export namespace IAutoBeDatabaseAuthorizationReviewApplication {
-  export interface IProps {
-    /**
-     * Reflect on requirements analysis before acting.
-     *
-     * For preliminary requests (getAnalysisSections,
-     * getPreviousAnalysisSections, getPreviousDatabaseSchemas):
-     *
-     * - What authentication requirements do you need to analyze?
-     * - Which actor types need to be verified?
-     *
-     * For completion (complete):
-     *
-     * - What authentication 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 authentication requirements analysis.
-     */
-    request:
-      | IComplete
-      | IAutoBePreliminaryGetAnalysisSections
-      | IAutoBePreliminaryGetPreviousAnalysisSections
-      | IAutoBePreliminaryGetPreviousDatabaseSchemas;
-  }
-
-  /**
-   * Submit table revisions after authentication requirements analysis.
-   *
-   * The authorization component contains tables for ALL actors, so ensure no
-   * actor is missing its required tables.
-   */
-  export interface IComplete {
-    /** Type discriminator. Value "complete" indicates final submission. */
-    type: "complete";
-
-    /**
-     * Authentication requirements coverage analysis.
-     *
-     * Document how you analyzed authentication requirements and mapped them to
-     * table modifications:
-     *
-     * - What actor types are defined?
-     * - Does each actor have a main table and session table?
-     * - What authentication support tables are needed?
-     * - 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 authentication requirements but
-     * doesn't exist.
-     *
-     * ```typescript
-     * {
-     *   "type": "create",
-     *   "reason": "Actor 'customer' requires password reset token storage",
-     *   "table": "shopping_customer_password_resets",
-     *   "description": "Stores password reset tokens with expiration for customers"
-     * }
-     * ```
-     *
-     * ### Update - Rename tables
-     *
-     * Use when a table has naming convention issues.
-     *
-     * ```typescript
-     * {
-     *   "type": "update",
-     *   "reason": "Table name violates actor naming convention",
-     *   "original": "customerSessions",
-     *   "updated": "shopping_customer_sessions",
-     *   "description": "Authentication sessions for shopping customers"
-     * }
-     * ```
-     *
-     * ### Erase - Remove tables
-     *
-     * Use when a table doesn't belong to authorization.
-     *
-     * ```typescript
-     * {
-     *   "type": "erase",
-     *   "reason": "Table is a business domain entity, not authentication",
-     *   "table": "shopping_orders"
-     * }
-     * ```
-     *
-     * ## Constraints:
-     *
-     * - Only CREATE tables related to authentication and authorization
-     * - Each actor MUST have a main actor table and session table
-     * - Each operation must have a clear, requirement-based reason
-     * - Empty array is valid if no modifications are needed
-     *
-     * ## Naming Conventions:
-     *
-     * - Snake case: `user_sessions` not `userSessions`
-     * - Plural form: `users` not `user`
-     * - Domain prefix: `shopping_customer_sessions`
-     * - Actor name in table: all tables must contain the actor name
-     */
-    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 IAutoBeDatabaseAuthorizationReviewApplication {
+  /**
+   * Analyze requirements and review the single authorization component
+   * containing tables for ALL actors.
+   *
+   * Your PRIMARY task is to deeply analyze authentication requirements and
+   * ensure complete table coverage for EVERY actor type in the authorization
+   * component. The component contains tables for all actors
+   * (guest/member/admin), and you must verify that each actor has its required
+   * tables.
+   *
+   * ALWAYS fetch analysis sections first using `getAnalysisSections` to
+   * understand what authentication features are required, then systematically
+   * verify that EVERY actor has main actor table + session table, and apply
+   * corrections.
+   *
+   * @param props Request containing either preliminary data request or complete
+   *   task with table revisions for all actors
+   */
+  process(props: IAutoBeDatabaseAuthorizationReviewApplication.IProps): void;
+}
+
+export namespace IAutoBeDatabaseAuthorizationReviewApplication {
+  export interface IProps {
+    /**
+     * Reflect on requirements analysis before acting.
+     *
+     * For preliminary requests (getAnalysisSections,
+     * getPreviousAnalysisSections, getPreviousDatabaseSchemas):
+     *
+     * - What authentication requirements do you need to analyze?
+     * - Which actor types need to be verified?
+     *
+     * For completion (complete):
+     *
+     * - What authentication 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 authentication requirements analysis.
+     */
+    request:
+      | IComplete
+      | IAutoBePreliminaryGetAnalysisSections
+      | IAutoBePreliminaryGetPreviousAnalysisSections
+      | IAutoBePreliminaryGetPreviousDatabaseSchemas;
+  }
+
+  /**
+   * Submit table revisions after authentication requirements analysis.
+   *
+   * The authorization component contains tables for ALL actors, so ensure no
+   * actor is missing its required tables.
+   */
+  export interface IComplete {
+    /** Type discriminator. Value "complete" indicates final submission. */
+    type: "complete";
+
+    /**
+     * Authentication requirements coverage analysis.
+     *
+     * Document how you analyzed authentication requirements and mapped them to
+     * table modifications:
+     *
+     * - What actor types are defined?
+     * - Does each actor have a main table and session table?
+     * - What authentication support tables are needed?
+     * - 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 authentication requirements but
+     * doesn't exist.
+     *
+     * ```typescript
+     * {
+     *   "type": "create",
+     *   "reason": "Actor 'customer' requires password reset token storage",
+     *   "table": "shopping_customer_password_resets",
+     *   "description": "Stores password reset tokens with expiration for customers"
+     * }
+     * ```
+     *
+     * ### Update - Rename tables
+     *
+     * Use when a table has naming convention issues.
+     *
+     * ```typescript
+     * {
+     *   "type": "update",
+     *   "reason": "Table name violates actor naming convention",
+     *   "original": "customerSessions",
+     *   "updated": "shopping_customer_sessions",
+     *   "description": "Authentication sessions for shopping customers"
+     * }
+     * ```
+     *
+     * ### Erase - Remove tables
+     *
+     * Use when a table doesn't belong to authorization.
+     *
+     * ```typescript
+     * {
+     *   "type": "erase",
+     *   "reason": "Table is a business domain entity, not authentication",
+     *   "table": "shopping_orders"
+     * }
+     * ```
+     *
+     * ## Constraints:
+     *
+     * - Only CREATE tables related to authentication and authorization
+     * - Each actor MUST have a main actor table and session table
+     * - Each operation must have a clear, requirement-based reason
+     * - Empty array is valid if no modifications are needed
+     *
+     * ## Naming Conventions:
+     *
+     * - Snake case: `user_sessions` not `userSessions`
+     * - Plural form: `users` not `user`
+     * - Domain prefix: `shopping_customer_sessions`
+     * - Actor name in table: all tables must contain the actor name
+     */
+    revises: AutoBeDatabaseComponentTableRevise[];
+  }
+}

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

@@ -1,142 +1,142 @@
-import { AutoBeDatabaseComponentTableDesign } from "@autobe/interface";
-
-import { IAutoBePreliminaryGetAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetAnalysisSections";
-import { IAutoBePreliminaryGetPreviousAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetPreviousAnalysisSections";
-import { IAutoBePreliminaryGetPreviousDatabaseSchemas } from "../../common/structures/IAutoBePreliminaryGetPreviousDatabaseSchemas";
-
-export interface IAutoBeDatabaseComponentApplication {
-  /**
-   * Process table design task for a single component skeleton or preliminary
-   * data requests.
-   *
-   * Receives a component skeleton (namespace, filename, thinking, review,
-   * rationale already determined by DATABASE_GROUP phase) and fills in the
-   * tables field with complete table designs for that single component.
-   *
-   * This is NOT about creating or organizing multiple components. The component
-   * identity is fixed. This agent ONLY designs the tables that belong to the
-   * provided component skeleton.
-   *
-   * @param props Request containing either preliminary data request or complete
-   *   table design
-   */
-  process(props: IAutoBeDatabaseComponentApplication.IProps): void;
-}
-
-export namespace IAutoBeDatabaseComponentApplication {
-  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,
-     * getPreviousAnalysisSections):
-     *
-     * - 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 table design (complete). When
-     * preliminary returns empty array, that type is removed from the union,
-     * physically preventing repeated calls.
-     */
-    request:
-      | IComplete
-      | IAutoBePreliminaryGetAnalysisSections
-      | IAutoBePreliminaryGetPreviousAnalysisSections
-      | IAutoBePreliminaryGetPreviousDatabaseSchemas;
-  }
-
-  /**
-   * Request to complete the database component by filling in table designs.
-   *
-   * Takes a component skeleton (namespace, filename already determined by
-   * DATABASE_GROUP phase) and fills in the tables field by designing all
-   * necessary database tables for this single component.
-   *
-   * This is NOT about creating multiple components - the component identity is
-   * already fixed. This is ONLY about designing the tables that belong to this
-   * single component.
-   */
-  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";
-
-    /**
-     * Analysis of the component's scope and table requirements.
-     *
-     * Documents the agent's understanding of this component's domain:
-     *
-     * - What is the component's business purpose (from the skeleton)?
-     * - What entities from the requirements belong to this component?
-     * - What relationships exist between these entities?
-     * - What normalization patterns were identified?
-     */
-    analysis: string;
-
-    /**
-     * Rationale for the table design decisions.
-     *
-     * Explains why tables were designed this way:
-     *
-     * - Why was each table created?
-     * - Why were certain entities kept separate vs combined?
-     * - What normalization principles were applied?
-     * - How do the tables fulfill the component's rationale?
-     */
-    rationale: string;
-
-    /**
-     * Array of table designs for THIS SINGLE component.
-     *
-     * Contains all database tables that belong to the component skeleton
-     * received as input. Each table design includes table name (snake_case,
-     * plural) and description explaining the table's purpose and contents.
-     *
-     * The AI agent must design tables based on:
-     *
-     * - The component's namespace and intended domain (from skeleton)
-     * - Business requirements from analysis sections
-     * - Previous database schemas for consistency
-     * - Normalization principles (3NF)
-     * - Relationship integrity
-     *
-     * CRITICAL CONSTRAINTS:
-     *
-     * - The namespace and filename are ALREADY DETERMINED by the component
-     *   skeleton
-     * - Do NOT create multiple components or reorganize component boundaries
-     * - Do NOT include thinking, review, decision, or rationale - those are
-     *   already in the skeleton
-     * - ALL tables generated here belong to THE SINGLE component skeleton
-     *   provided
-     * - ONLY provide the tables array - nothing else
-     */
-    tables: AutoBeDatabaseComponentTableDesign[];
-  }
-}
+import { AutoBeDatabaseComponentTableDesign } from "@autobe/interface";
+
+import { IAutoBePreliminaryGetAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetAnalysisSections";
+import { IAutoBePreliminaryGetPreviousAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetPreviousAnalysisSections";
+import { IAutoBePreliminaryGetPreviousDatabaseSchemas } from "../../common/structures/IAutoBePreliminaryGetPreviousDatabaseSchemas";
+
+export interface IAutoBeDatabaseComponentApplication {
+  /**
+   * Process table design task for a single component skeleton or preliminary
+   * data requests.
+   *
+   * Receives a component skeleton (namespace, filename, thinking, review,
+   * rationale already determined by DATABASE_GROUP phase) and fills in the
+   * tables field with complete table designs for that single component.
+   *
+   * This is NOT about creating or organizing multiple components. The component
+   * identity is fixed. This agent ONLY designs the tables that belong to the
+   * provided component skeleton.
+   *
+   * @param props Request containing either preliminary data request or complete
+   *   table design
+   */
+  process(props: IAutoBeDatabaseComponentApplication.IProps): void;
+}
+
+export namespace IAutoBeDatabaseComponentApplication {
+  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,
+     * getPreviousAnalysisSections):
+     *
+     * - 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 table design (complete). When
+     * preliminary returns empty array, that type is removed from the union,
+     * physically preventing repeated calls.
+     */
+    request:
+      | IComplete
+      | IAutoBePreliminaryGetAnalysisSections
+      | IAutoBePreliminaryGetPreviousAnalysisSections
+      | IAutoBePreliminaryGetPreviousDatabaseSchemas;
+  }
+
+  /**
+   * Request to complete the database component by filling in table designs.
+   *
+   * Takes a component skeleton (namespace, filename already determined by
+   * DATABASE_GROUP phase) and fills in the tables field by designing all
+   * necessary database tables for this single component.
+   *
+   * This is NOT about creating multiple components - the component identity is
+   * already fixed. This is ONLY about designing the tables that belong to this
+   * single component.
+   */
+  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";
+
+    /**
+     * Analysis of the component's scope and table requirements.
+     *
+     * Documents the agent's understanding of this component's domain:
+     *
+     * - What is the component's business purpose (from the skeleton)?
+     * - What entities from the requirements belong to this component?
+     * - What relationships exist between these entities?
+     * - What normalization patterns were identified?
+     */
+    analysis: string;
+
+    /**
+     * Rationale for the table design decisions.
+     *
+     * Explains why tables were designed this way:
+     *
+     * - Why was each table created?
+     * - Why were certain entities kept separate vs combined?
+     * - What normalization principles were applied?
+     * - How do the tables fulfill the component's rationale?
+     */
+    rationale: string;
+
+    /**
+     * Array of table designs for THIS SINGLE component.
+     *
+     * Contains all database tables that belong to the component skeleton
+     * received as input. Each table design includes table name (snake_case,
+     * plural) and description explaining the table's purpose and contents.
+     *
+     * The AI agent must design tables based on:
+     *
+     * - The component's namespace and intended domain (from skeleton)
+     * - Business requirements from analysis sections
+     * - Previous database schemas for consistency
+     * - Normalization principles (3NF)
+     * - Relationship integrity
+     *
+     * CRITICAL CONSTRAINTS:
+     *
+     * - The namespace and filename are ALREADY DETERMINED by the component
+     *   skeleton
+     * - Do NOT create multiple components or reorganize component boundaries
+     * - Do NOT include thinking, review, decision, or rationale - those are
+     *   already in the skeleton
+     * - ALL tables generated here belong to THE SINGLE component skeleton
+     *   provided
+     * - ONLY provide the tables array - nothing else
+     */
+    tables: AutoBeDatabaseComponentTableDesign[];
+  }
+}