@autobe/agent 0.30.0-dev.20260315 → 0.30.1

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

@@ -1,117 +1,117 @@
-import { AutoBeDatabaseGroup } from "@autobe/interface";
-import { tags } from "typia";
-
-import { IAutoBePreliminaryGetAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetAnalysisSections";
-import { IAutoBePreliminaryGetPreviousAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetPreviousAnalysisSections";
-import { IAutoBePreliminaryGetPreviousDatabaseSchemas } from "../../common/structures/IAutoBePreliminaryGetPreviousDatabaseSchemas";
-
-export interface IAutoBeDatabaseGroupApplication {
-  /**
-   * Process database component group generation task or preliminary data
-   * requests.
-   *
-   * Generate logical groups for organizing database component extraction based
-   * on business domains. Processes group generation with incremental context
-   * loading to ensure comprehensive organization.
-   *
-   * @param props Request containing either preliminary data request or complete
-   *   task
-   */
-  process(props: IAutoBeDatabaseGroupApplication.IProps): void;
-}
-
-export namespace IAutoBeDatabaseGroupApplication {
-  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, getPreviousDatabaseSchemas):
-     *
-     * - 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 group 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 component groups.
-   *
-   * Executes group generation to organize database components based on business
-   * domains from requirements.
-   */
-  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 requirements structure and domain organization.
-     *
-     * Documents the agent's understanding of the business requirements:
-     *
-     * - What major business domains were identified from the requirements?
-     * - How are these domains related to each other?
-     * - What organizational patterns exist in the requirements?
-     * - What foundational vs domain-specific components are needed?
-     */
-    analysis: string;
-
-    /**
-     * Rationale for the component grouping decisions.
-     *
-     * Explains why the groups were organized this way:
-     *
-     * - Why was each component group created?
-     * - Why were certain domains combined or kept separate?
-     * - How does the grouping reflect the business domain structure?
-     * - What considerations drove the component ordering?
-     */
-    rationale: string;
-
-    /**
-     * Array of database component groups for organizing development.
-     *
-     * DO: Derive groups from business domains in requirements rather than
-     * arbitrary technical divisions. DO: Create foundational groups
-     * (Systematic, Actors) separately from domain-specific groups. DO: Organize
-     * groups around business workflows and entity relationships. DO: Provide
-     * complete coverage of all components without overlap.
-     */
-    groups: AutoBeDatabaseGroup[] & tags.MinItems<1>;
-  }
-}
+import { AutoBeDatabaseGroup } from "@autobe/interface";
+import { tags } from "typia";
+
+import { IAutoBePreliminaryGetAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetAnalysisSections";
+import { IAutoBePreliminaryGetPreviousAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetPreviousAnalysisSections";
+import { IAutoBePreliminaryGetPreviousDatabaseSchemas } from "../../common/structures/IAutoBePreliminaryGetPreviousDatabaseSchemas";
+
+export interface IAutoBeDatabaseGroupApplication {
+  /**
+   * Process database component group generation task or preliminary data
+   * requests.
+   *
+   * Generate logical groups for organizing database component extraction based
+   * on business domains. Processes group generation with incremental context
+   * loading to ensure comprehensive organization.
+   *
+   * @param props Request containing either preliminary data request or complete
+   *   task
+   */
+  process(props: IAutoBeDatabaseGroupApplication.IProps): void;
+}
+
+export namespace IAutoBeDatabaseGroupApplication {
+  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, getPreviousDatabaseSchemas):
+     *
+     * - 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 group 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 component groups.
+   *
+   * Executes group generation to organize database components based on business
+   * domains from requirements.
+   */
+  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 requirements structure and domain organization.
+     *
+     * Documents the agent's understanding of the business requirements:
+     *
+     * - What major business domains were identified from the requirements?
+     * - How are these domains related to each other?
+     * - What organizational patterns exist in the requirements?
+     * - What foundational vs domain-specific components are needed?
+     */
+    analysis: string;
+
+    /**
+     * Rationale for the component grouping decisions.
+     *
+     * Explains why the groups were organized this way:
+     *
+     * - Why was each component group created?
+     * - Why were certain domains combined or kept separate?
+     * - How does the grouping reflect the business domain structure?
+     * - What considerations drove the component ordering?
+     */
+    rationale: string;
+
+    /**
+     * Array of database component groups for organizing development.
+     *
+     * DO: Derive groups from business domains in requirements rather than
+     * arbitrary technical divisions. DO: Create foundational groups
+     * (Systematic, Actors) separately from domain-specific groups. DO: Organize
+     * groups around business workflows and entity relationships. DO: Provide
+     * complete coverage of all components without overlap.
+     */
+    groups: AutoBeDatabaseGroup[] & tags.MinItems<1>;
+  }
+}

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

@@ -1,154 +1,154 @@
-import { AutoBeDatabaseGroupRevise } from "@autobe/interface";
-
-import { IAutoBePreliminaryGetAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetAnalysisSections";
-import { IAutoBePreliminaryGetPreviousAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetPreviousAnalysisSections";
-import { IAutoBePreliminaryGetPreviousDatabaseSchemas } from "../../common/structures/IAutoBePreliminaryGetPreviousDatabaseSchemas";
-
-export interface IAutoBeDatabaseGroupReviewApplication {
-  /**
-   * Analyze requirements and review the component group skeletons.
-   *
-   * Your PRIMARY task is to verify that the group structure provides complete,
-   * well-organized coverage of all business domains described in the
-   * requirements. Review existing groups and identify necessary modifications
-   * using create, update, or erase operations.
-   *
-   * ALWAYS fetch analysis sections first using `getAnalysisSections` to
-   * understand what business domains exist, then systematically verify group
-   * coverage and apply corrections.
-   *
-   * @param props Request containing either preliminary data request or complete
-   *   task with group revisions
-   */
-  process(props: IAutoBeDatabaseGroupReviewApplication.IProps): void;
-}
-
-export namespace IAutoBeDatabaseGroupReviewApplication {
-  export interface IProps {
-    /**
-     * Reflect on requirements analysis before acting.
-     *
-     * For preliminary requests (getAnalysisSections,
-     * getPreviousAnalysisSections, getPreviousDatabaseSchemas):
-     *
-     * - What business domains do you need to analyze?
-     * - What requirements will help verify group coverage?
-     *
-     * For completion (complete):
-     *
-     * - What domains did you analyze?
-     * - How many revisions are you making and why?
-     * - Summarize the domain-to-group mapping.
-     */
-    thinking: string;
-
-    /**
-     * Request type discriminator.
-     *
-     * Use preliminary requests (getAnalysisSections, etc.) to fetch
-     * requirements documents. Use complete to submit group revisions after
-     * thorough domain coverage analysis.
-     */
-    request:
-      | IComplete
-      | IAutoBePreliminaryGetAnalysisSections
-      | IAutoBePreliminaryGetPreviousAnalysisSections
-      | IAutoBePreliminaryGetPreviousDatabaseSchemas;
-  }
-
-  /** Submit group revisions after domain coverage analysis. */
-  export interface IComplete {
-    /** Type discriminator. Value "complete" indicates final submission. */
-    type: "complete";
-
-    /**
-     * Domain coverage analysis.
-     *
-     * Document how you analyzed business requirements and mapped them to group
-     * modifications:
-     *
-     * - What business domains are defined in requirements?
-     * - Does each domain have a corresponding group?
-     * - Are group boundaries appropriate?
-     * - Are kind assignments correct?
-     *
-     * Be specific - reference actual requirements and explain the
-     * domain-to-revisions mapping.
-     */
-    review: string;
-
-    /**
-     * Array of group 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 groups
-     *
-     * Use when a business domain has no corresponding group.
-     *
-     * ```typescript
-     * {
-     *   "type": "create",
-     *   "reason": "Notification functionality exists in requirements but has no group",
-     *   "group": {
-     *     "thinking": "...",
-     *     "review": "...",
-     *     "rationale": "...",
-     *     "namespace": "Notifications",
-     *     "filename": "schema-10-notifications.prisma",
-     *     "kind": "domain"
-     *   }
-     * }
-     * ```
-     *
-     * ### Update - Modify existing groups
-     *
-     * Use when a group has property issues.
-     *
-     * ```typescript
-     * {
-     *   "type": "update",
-     *   "reason": "Namespace uses incorrect casing",
-     *   "originalNamespace": "products_catalog",
-     *   "group": {
-     *     "thinking": "...",
-     *     "review": "...",
-     *     "rationale": "...",
-     *     "namespace": "Products",
-     *     "filename": "schema-03-products.prisma",
-     *     "kind": "domain"
-     *   }
-     * }
-     * ```
-     *
-     * ### Erase - Remove groups
-     *
-     * Use when a group is unnecessary.
-     *
-     * ```typescript
-     * {
-     *   "type": "erase",
-     *   "reason": "Group is redundant with existing Products group",
-     *   "namespace": "Catalog"
-     * }
-     * ```
-     *
-     * ## Constraints:
-     *
-     * - After revisions: exactly 1 authorization group, ≥1 domain groups
-     * - Each operation must have a clear, requirement-based reason
-     * - Empty array is valid if no modifications are needed
-     *
-     * ## Naming Conventions:
-     *
-     * - Namespace: PascalCase (e.g., "Products", "Orders")
-     * - Filename: `schema-{number}-{domain}.prisma` format
-     * - Kind: "authorization" or "domain"
-     */
-    revises: AutoBeDatabaseGroupRevise[];
-  }
-}
+import { AutoBeDatabaseGroupRevise } from "@autobe/interface";
+
+import { IAutoBePreliminaryGetAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetAnalysisSections";
+import { IAutoBePreliminaryGetPreviousAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetPreviousAnalysisSections";
+import { IAutoBePreliminaryGetPreviousDatabaseSchemas } from "../../common/structures/IAutoBePreliminaryGetPreviousDatabaseSchemas";
+
+export interface IAutoBeDatabaseGroupReviewApplication {
+  /**
+   * Analyze requirements and review the component group skeletons.
+   *
+   * Your PRIMARY task is to verify that the group structure provides complete,
+   * well-organized coverage of all business domains described in the
+   * requirements. Review existing groups and identify necessary modifications
+   * using create, update, or erase operations.
+   *
+   * ALWAYS fetch analysis sections first using `getAnalysisSections` to
+   * understand what business domains exist, then systematically verify group
+   * coverage and apply corrections.
+   *
+   * @param props Request containing either preliminary data request or complete
+   *   task with group revisions
+   */
+  process(props: IAutoBeDatabaseGroupReviewApplication.IProps): void;
+}
+
+export namespace IAutoBeDatabaseGroupReviewApplication {
+  export interface IProps {
+    /**
+     * Reflect on requirements analysis before acting.
+     *
+     * For preliminary requests (getAnalysisSections,
+     * getPreviousAnalysisSections, getPreviousDatabaseSchemas):
+     *
+     * - What business domains do you need to analyze?
+     * - What requirements will help verify group coverage?
+     *
+     * For completion (complete):
+     *
+     * - What domains did you analyze?
+     * - How many revisions are you making and why?
+     * - Summarize the domain-to-group mapping.
+     */
+    thinking: string;
+
+    /**
+     * Request type discriminator.
+     *
+     * Use preliminary requests (getAnalysisSections, etc.) to fetch
+     * requirements documents. Use complete to submit group revisions after
+     * thorough domain coverage analysis.
+     */
+    request:
+      | IComplete
+      | IAutoBePreliminaryGetAnalysisSections
+      | IAutoBePreliminaryGetPreviousAnalysisSections
+      | IAutoBePreliminaryGetPreviousDatabaseSchemas;
+  }
+
+  /** Submit group revisions after domain coverage analysis. */
+  export interface IComplete {
+    /** Type discriminator. Value "complete" indicates final submission. */
+    type: "complete";
+
+    /**
+     * Domain coverage analysis.
+     *
+     * Document how you analyzed business requirements and mapped them to group
+     * modifications:
+     *
+     * - What business domains are defined in requirements?
+     * - Does each domain have a corresponding group?
+     * - Are group boundaries appropriate?
+     * - Are kind assignments correct?
+     *
+     * Be specific - reference actual requirements and explain the
+     * domain-to-revisions mapping.
+     */
+    review: string;
+
+    /**
+     * Array of group 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 groups
+     *
+     * Use when a business domain has no corresponding group.
+     *
+     * ```typescript
+     * {
+     *   "type": "create",
+     *   "reason": "Notification functionality exists in requirements but has no group",
+     *   "group": {
+     *     "thinking": "...",
+     *     "review": "...",
+     *     "rationale": "...",
+     *     "namespace": "Notifications",
+     *     "filename": "schema-10-notifications.prisma",
+     *     "kind": "domain"
+     *   }
+     * }
+     * ```
+     *
+     * ### Update - Modify existing groups
+     *
+     * Use when a group has property issues.
+     *
+     * ```typescript
+     * {
+     *   "type": "update",
+     *   "reason": "Namespace uses incorrect casing",
+     *   "originalNamespace": "products_catalog",
+     *   "group": {
+     *     "thinking": "...",
+     *     "review": "...",
+     *     "rationale": "...",
+     *     "namespace": "Products",
+     *     "filename": "schema-03-products.prisma",
+     *     "kind": "domain"
+     *   }
+     * }
+     * ```
+     *
+     * ### Erase - Remove groups
+     *
+     * Use when a group is unnecessary.
+     *
+     * ```typescript
+     * {
+     *   "type": "erase",
+     *   "reason": "Group is redundant with existing Products group",
+     *   "namespace": "Catalog"
+     * }
+     * ```
+     *
+     * ## Constraints:
+     *
+     * - After revisions: exactly 1 authorization group, ≥1 domain groups
+     * - Each operation must have a clear, requirement-based reason
+     * - Empty array is valid if no modifications are needed
+     *
+     * ## Naming Conventions:
+     *
+     * - Namespace: PascalCase (e.g., "Products", "Orders")
+     * - Filename: `schema-{number}-{domain}.prisma` format
+     * - Kind: "authorization" or "domain"
+     */
+    revises: AutoBeDatabaseGroupRevise[];
+  }
+}