@autobe/agent 0.30.0-dev.20260315 → 0.30.1

package/src/orchestrate/prisma/histories/transformPrismaGroupHistory.ts

@@ -1,63 +1,63 @@
-import { StringUtil } from "@autobe/utils";
-import { v7 } from "uuid";
-
-import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
-import { AutoBeState } from "../../../context/AutoBeState";
-import { IAutoBeOrchestrateHistory } from "../../../structures/IAutoBeOrchestrateHistory";
-import { AutoBePreliminaryController } from "../../common/AutoBePreliminaryController";
-
-export const transformPrismaGroupHistory = (
-  state: AutoBeState,
-  props: {
-    instruction: string;
-    preliminary: AutoBePreliminaryController<
-      | "analysisSections"
-      | "previousAnalysisSections"
-      | "previousDatabaseSchemas"
-    >;
-  },
-): IAutoBeOrchestrateHistory => {
-  if (state.analyze === null)
-    // unreachable
-    throw new Error("Analyze state is not set.");
-  return {
-    histories: [
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "systemMessage",
-        text: AutoBeSystemPromptConstant.DATABASE_COMPONENT,
-      },
-      ...props.preliminary.getHistories(),
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "assistantMessage",
-        text: StringUtil.trim`
-          ## Database Design Instructions
-
-          The following database-specific instructions were extracted from
-          the user's requirements. These focus on database schema design aspects
-          such as component organization, domain grouping, and structural patterns.
-
-          Follow these instructions when organizing database component groups.
-          Carefully distinguish between:
-          - Suggestions or recommendations (consider these as guidance)
-          - Direct specifications or explicit commands (these must be followed exactly)
-
-          When instructions contain direct specifications or explicit design decisions,
-          follow them precisely even if you believe you have better alternatives.
-
-          ${props.instruction}
-        `,
-      },
-    ],
-    userMessage: StringUtil.trim`
-      ## Your Task: Organize Database Components into Logical Groups
-
-      Identify all business domains from the requirements and generate complete component groups covering them.
-
-      When ready, call \`process({ request: { type: "complete", ... } })\` with the group definitions.
-    `,
-  };
-};
+import { StringUtil } from "@autobe/utils";
+import { v7 } from "uuid";
+
+import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
+import { AutoBeState } from "../../../context/AutoBeState";
+import { IAutoBeOrchestrateHistory } from "../../../structures/IAutoBeOrchestrateHistory";
+import { AutoBePreliminaryController } from "../../common/AutoBePreliminaryController";
+
+export const transformPrismaGroupHistory = (
+  state: AutoBeState,
+  props: {
+    instruction: string;
+    preliminary: AutoBePreliminaryController<
+      | "analysisSections"
+      | "previousAnalysisSections"
+      | "previousDatabaseSchemas"
+    >;
+  },
+): IAutoBeOrchestrateHistory => {
+  if (state.analyze === null)
+    // unreachable
+    throw new Error("Analyze state is not set.");
+  return {
+    histories: [
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "systemMessage",
+        text: AutoBeSystemPromptConstant.DATABASE_COMPONENT,
+      },
+      ...props.preliminary.getHistories(),
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "assistantMessage",
+        text: StringUtil.trim`
+          ## Database Design Instructions
+
+          The following database-specific instructions were extracted from
+          the user's requirements. These focus on database schema design aspects
+          such as component organization, domain grouping, and structural patterns.
+
+          Follow these instructions when organizing database component groups.
+          Carefully distinguish between:
+          - Suggestions or recommendations (consider these as guidance)
+          - Direct specifications or explicit commands (these must be followed exactly)
+
+          When instructions contain direct specifications or explicit design decisions,
+          follow them precisely even if you believe you have better alternatives.
+
+          ${props.instruction}
+        `,
+      },
+    ],
+    userMessage: StringUtil.trim`
+      ## Your Task: Organize Database Components into Logical Groups
+
+      Identify all business domains from the requirements and generate complete component groups covering them.
+
+      When ready, call \`process({ request: { type: "complete", ... } })\` with the group definitions.
+    `,
+  };
+};

package/src/orchestrate/prisma/histories/transformPrismaGroupReviewHistory.ts

@@ -1,79 +1,79 @@
-import { AutoBeDatabaseGroup } from "@autobe/interface";
-import { StringUtil } from "@autobe/utils";
-import { v7 } from "uuid";
-
-import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
-import { IAutoBeOrchestrateHistory } from "../../../structures/IAutoBeOrchestrateHistory";
-import { AutoBePreliminaryController } from "../../common/AutoBePreliminaryController";
-
-export const transformPrismaGroupReviewHistory = (props: {
-  preliminary: AutoBePreliminaryController<
-    "analysisSections" | "previousAnalysisSections" | "previousDatabaseSchemas"
-  >;
-  groups: AutoBeDatabaseGroup[];
-  instruction: string;
-}): IAutoBeOrchestrateHistory => ({
-  histories: [
-    {
-      id: v7(),
-      created_at: new Date().toISOString(),
-      type: "systemMessage",
-      text: AutoBeSystemPromptConstant.DATABASE_GROUP,
-    },
-    {
-      id: v7(),
-      created_at: new Date().toISOString(),
-      type: "systemMessage",
-      text: AutoBeSystemPromptConstant.DATABASE_GROUP_REVIEW,
-    },
-    ...props.preliminary.getHistories(),
-    {
-      id: v7(),
-      created_at: new Date().toISOString(),
-      type: "assistantMessage",
-      text: StringUtil.trim`
-        ## Component Groups to Review
-
-        The following component group skeletons were generated by the Database Group Agent.
-        Review them against the business requirements and apply necessary revisions.
-
-        ### Current Groups
-
-        \`\`\`json
-        ${JSON.stringify(props.groups)}
-        \`\`\`
-
-        ### User Instructions
-
-        ${props.instruction}
-      `,
-    },
-  ],
-  userMessage: StringUtil.trim`
-    Review the component group structure and apply necessary revisions.
-
-    **🚨 CRITICAL: Authorization Group is PROTECTED**
-    - The authorization group (\`kind: "authorization"\`) is **IMMUTABLE**
-    - You can ONLY review and revise **domain groups** (\`kind: "domain"\`)
-    - ❌ Cannot create/update/erase authorization groups
-
-    **Group Structure Rules:**
-    - Exactly 1 group with \`kind: "authorization"\` - DO NOT MODIFY
-    - At least 1 group with \`kind: "domain"\` (for business domain tables)
-    - Each domain group should cover a focused business domain (3-15 estimated tables)
-    - Namespace must be PascalCase, filename must follow \`schema-{number}-{domain}.prisma\` format
-
-    **Steps:**
-    1. Understand business requirements and identify all business domains
-    2. Verify every business domain has a corresponding domain group
-    3. Check domain group boundaries and naming conventions (skip authorization group)
-    4. Call \`process({ request: { type: "complete", review: "...", revises: [...] } })\`
-
-    **Revisions (domain groups only):**
-    - **Create**: Add domain groups for missing business domains (\`kind: "domain"\` only)
-    - **Update**: Fix domain groups with naming or scope issues
-    - **Erase**: Remove redundant domain groups
-
-    If no changes are needed, return an empty revises array.
-  `,
-});
+import { AutoBeDatabaseGroup } from "@autobe/interface";
+import { StringUtil } from "@autobe/utils";
+import { v7 } from "uuid";
+
+import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
+import { IAutoBeOrchestrateHistory } from "../../../structures/IAutoBeOrchestrateHistory";
+import { AutoBePreliminaryController } from "../../common/AutoBePreliminaryController";
+
+export const transformPrismaGroupReviewHistory = (props: {
+  preliminary: AutoBePreliminaryController<
+    "analysisSections" | "previousAnalysisSections" | "previousDatabaseSchemas"
+  >;
+  groups: AutoBeDatabaseGroup[];
+  instruction: string;
+}): IAutoBeOrchestrateHistory => ({
+  histories: [
+    {
+      id: v7(),
+      created_at: new Date().toISOString(),
+      type: "systemMessage",
+      text: AutoBeSystemPromptConstant.DATABASE_GROUP,
+    },
+    {
+      id: v7(),
+      created_at: new Date().toISOString(),
+      type: "systemMessage",
+      text: AutoBeSystemPromptConstant.DATABASE_GROUP_REVIEW,
+    },
+    ...props.preliminary.getHistories(),
+    {
+      id: v7(),
+      created_at: new Date().toISOString(),
+      type: "assistantMessage",
+      text: StringUtil.trim`
+        ## Component Groups to Review
+
+        The following component group skeletons were generated by the Database Group Agent.
+        Review them against the business requirements and apply necessary revisions.
+
+        ### Current Groups
+
+        \`\`\`json
+        ${JSON.stringify(props.groups)}
+        \`\`\`
+
+        ### User Instructions
+
+        ${props.instruction}
+      `,
+    },
+  ],
+  userMessage: StringUtil.trim`
+    Review the component group structure and apply necessary revisions.
+
+    **🚨 CRITICAL: Authorization Group is PROTECTED**
+    - The authorization group (\`kind: "authorization"\`) is **IMMUTABLE**
+    - You can ONLY review and revise **domain groups** (\`kind: "domain"\`)
+    - ❌ Cannot create/update/erase authorization groups
+
+    **Group Structure Rules:**
+    - Exactly 1 group with \`kind: "authorization"\` - DO NOT MODIFY
+    - At least 1 group with \`kind: "domain"\` (for business domain tables)
+    - Each domain group should cover a focused business domain (3-15 estimated tables)
+    - Namespace must be PascalCase, filename must follow \`schema-{number}-{domain}.prisma\` format
+
+    **Steps:**
+    1. Understand business requirements and identify all business domains
+    2. Verify every business domain has a corresponding domain group
+    3. Check domain group boundaries and naming conventions (skip authorization group)
+    4. Call \`process({ request: { type: "complete", review: "...", revises: [...] } })\`
+
+    **Revisions (domain groups only):**
+    - **Create**: Add domain groups for missing business domains (\`kind: "domain"\` only)
+    - **Update**: Fix domain groups with naming or scope issues
+    - **Erase**: Remove redundant domain groups
+
+    If no changes are needed, return an empty revises array.
+  `,
+});

package/src/orchestrate/prisma/histories/transformPrismaSchemaHistory.ts

@@ -1,97 +1,97 @@
-import { IMicroAgenticaHistoryJson } from "@agentica/core";
-import {
-  AutoBeDatabaseComponent,
-  AutoBeDatabaseComponentTableDesign,
-} from "@autobe/interface";
-import { StringUtil } from "@autobe/utils";
-import { singular } from "pluralize";
-import { v7 } from "uuid";
-
-import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
-import { IAutoBeOrchestrateHistory } from "../../../structures/IAutoBeOrchestrateHistory";
-import { AutoBePreliminaryController } from "../../common/AutoBePreliminaryController";
-
-export const transformPrismaSchemaHistory = (props: {
-  otherComponents: AutoBeDatabaseComponent[];
-  component: AutoBeDatabaseComponent;
-  design: AutoBeDatabaseComponentTableDesign;
-  instruction: string;
-  preliminary: AutoBePreliminaryController<
-    "analysisSections" | "previousAnalysisSections" | "previousDatabaseSchemas"
-  >;
-}): IAutoBeOrchestrateHistory => {
-  const children: string[] = [props.component, ...props.otherComponents]
-    .flatMap((c) => c.tables.map((t) => t.name))
-    .filter((s) => s !== props.design.name)
-    .filter((s) => s.startsWith(singular(props.design.name) + "_"));
-  return {
-    histories: [
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "systemMessage",
-        text: AutoBeSystemPromptConstant.DATABASE_SCHEMA,
-      },
-      ...props.preliminary.getHistories(),
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "assistantMessage",
-        text: StringUtil.trim`
-          ## Database Design Instructions
-
-          The following database-specific instructions were extracted from
-          the user's requirements. These focus on database schema design aspects
-          such as table structure, relationships, constraints, and indexing strategies.
-
-          Follow these instructions when designing the DB schema. Carefully distinguish between:
-          - Suggestions or recommendations (consider these as guidance)
-          - Direct specifications or explicit commands (these must be followed exactly)
-
-          When instructions contain direct specifications or explicit design decisions,
-          follow them precisely even if you believe you have better alternatives.
-
-          ${props.instruction}
-
-          ## Component Context
-
-          Here is the component context for generating DB schema.
-
-          \`\`\`json
-          ${JSON.stringify({
-            targetComponent: props.component,
-            otherComponents: props.otherComponents,
-          })}
-          \`\`\`
-
-          ## Table Context
-
-          You are generating the database schema for the target table:
-
-          - Component Namespace: ${props.component.namespace}
-          - Target Table Name: ${props.design.name}
-          - Target Table Summary: ${props.design.description}
-        `,
-      },
-      ...(children.length !== 0
-        ? [
-            {
-              id: v7(),
-              created_at: new Date().toISOString(),
-              type: "assistantMessage",
-              text: StringUtil.trim`
-                ## Child Table Collision Warning
-
-                The following child tables are already assigned to other
-                agents, so do NOT recreate them and your child table names
-                must NOT collide with any of them:
-
-                ${children.map((t) => `- ${t}`).join("\n")}
-              `,
-            } satisfies IMicroAgenticaHistoryJson,
-          ]
-        : []),
-    ],
-    userMessage: "Make database schema please",
-  };
-};
+import { IMicroAgenticaHistoryJson } from "@agentica/core";
+import {
+  AutoBeDatabaseComponent,
+  AutoBeDatabaseComponentTableDesign,
+} from "@autobe/interface";
+import { StringUtil } from "@autobe/utils";
+import { singular } from "pluralize";
+import { v7 } from "uuid";
+
+import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
+import { IAutoBeOrchestrateHistory } from "../../../structures/IAutoBeOrchestrateHistory";
+import { AutoBePreliminaryController } from "../../common/AutoBePreliminaryController";
+
+export const transformPrismaSchemaHistory = (props: {
+  otherComponents: AutoBeDatabaseComponent[];
+  component: AutoBeDatabaseComponent;
+  design: AutoBeDatabaseComponentTableDesign;
+  instruction: string;
+  preliminary: AutoBePreliminaryController<
+    "analysisSections" | "previousAnalysisSections" | "previousDatabaseSchemas"
+  >;
+}): IAutoBeOrchestrateHistory => {
+  const children: string[] = [props.component, ...props.otherComponents]
+    .flatMap((c) => c.tables.map((t) => t.name))
+    .filter((s) => s !== props.design.name)
+    .filter((s) => s.startsWith(singular(props.design.name) + "_"));
+  return {
+    histories: [
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "systemMessage",
+        text: AutoBeSystemPromptConstant.DATABASE_SCHEMA,
+      },
+      ...props.preliminary.getHistories(),
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "assistantMessage",
+        text: StringUtil.trim`
+          ## Database Design Instructions
+
+          The following database-specific instructions were extracted from
+          the user's requirements. These focus on database schema design aspects
+          such as table structure, relationships, constraints, and indexing strategies.
+
+          Follow these instructions when designing the DB schema. Carefully distinguish between:
+          - Suggestions or recommendations (consider these as guidance)
+          - Direct specifications or explicit commands (these must be followed exactly)
+
+          When instructions contain direct specifications or explicit design decisions,
+          follow them precisely even if you believe you have better alternatives.
+
+          ${props.instruction}
+
+          ## Component Context
+
+          Here is the component context for generating DB schema.
+
+          \`\`\`json
+          ${JSON.stringify({
+            targetComponent: props.component,
+            otherComponents: props.otherComponents,
+          })}
+          \`\`\`
+
+          ## Table Context
+
+          You are generating the database schema for the target table:
+
+          - Component Namespace: ${props.component.namespace}
+          - Target Table Name: ${props.design.name}
+          - Target Table Summary: ${props.design.description}
+        `,
+      },
+      ...(children.length !== 0
+        ? [
+            {
+              id: v7(),
+              created_at: new Date().toISOString(),
+              type: "assistantMessage",
+              text: StringUtil.trim`
+                ## Child Table Collision Warning
+
+                The following child tables are already assigned to other
+                agents, so do NOT recreate them and your child table names
+                must NOT collide with any of them:
+
+                ${children.map((t) => `- ${t}`).join("\n")}
+              `,
+            } satisfies IMicroAgenticaHistoryJson,
+          ]
+        : []),
+    ],
+    userMessage: "Make database schema please",
+  };
+};