@autobe/agent 0.30.0-dev.20260315 → 0.30.0

package/src/orchestrate/interface/histories/transformInterfaceBaseEndpointWriteHistory.ts

@@ -1,68 +1,68 @@
-import { AutoBeInterfaceGroup, AutoBeOpenApi } from "@autobe/interface";
-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";
-import { transformInterfaceEndpointAuthorizationSection } from "./transformInterfaceEndpointAuthorizationSection";
-
-export const transformInterfaceBaseEndpointWriteHistory = (props: {
-  state: AutoBeState;
-  group: AutoBeInterfaceGroup;
-  preliminary: AutoBePreliminaryController<
-    | "analysisSections"
-    | "databaseSchemas"
-    | "previousAnalysisSections"
-    | "previousDatabaseSchemas"
-    | "previousInterfaceOperations"
-  >;
-  authorizeOperations: AutoBeOpenApi.IOperation[];
-  instruction: string;
-}): IAutoBeOrchestrateHistory => ({
-  histories: [
-    {
-      type: "systemMessage",
-      id: v7(),
-      created_at: new Date().toISOString(),
-      text: AutoBeSystemPromptConstant.INTERFACE_BASE_ENDPOINT_WRITE,
-    },
-    ...props.preliminary.getHistories(),
-    {
-      type: "assistantMessage",
-      id: v7(),
-      created_at: new Date().toISOString(),
-      text: StringUtil.trim`
-        ## API Design Instructions (Reference)
-
-        The following API-specific instructions were extracted from
-        the user's requirements. These focus on API interface design aspects
-        such as endpoint patterns, request/response formats, DTO schemas,
-        and operation specifications.
-
-        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}
-
-        ${transformInterfaceEndpointAuthorizationSection(props.authorizeOperations)}
-        
-        ## Target Group for Design (YOUR TASK)
-
-        You are designing base CRUD endpoints for the **${props.group.name}** group.
-
-        \`\`\`json
-        ${JSON.stringify(props.group)}
-        \`\`\`
-
-        Design base CRUD endpoints that cover all entities in this group.
-        `,
-    },
-  ],
-  userMessage: `Design endpoints for the ${props.group.name} group please`,
-});
+import { AutoBeInterfaceGroup, AutoBeOpenApi } from "@autobe/interface";
+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";
+import { transformInterfaceEndpointAuthorizationSection } from "./transformInterfaceEndpointAuthorizationSection";
+
+export const transformInterfaceBaseEndpointWriteHistory = (props: {
+  state: AutoBeState;
+  group: AutoBeInterfaceGroup;
+  preliminary: AutoBePreliminaryController<
+    | "analysisSections"
+    | "databaseSchemas"
+    | "previousAnalysisSections"
+    | "previousDatabaseSchemas"
+    | "previousInterfaceOperations"
+  >;
+  authorizeOperations: AutoBeOpenApi.IOperation[];
+  instruction: string;
+}): IAutoBeOrchestrateHistory => ({
+  histories: [
+    {
+      type: "systemMessage",
+      id: v7(),
+      created_at: new Date().toISOString(),
+      text: AutoBeSystemPromptConstant.INTERFACE_BASE_ENDPOINT_WRITE,
+    },
+    ...props.preliminary.getHistories(),
+    {
+      type: "assistantMessage",
+      id: v7(),
+      created_at: new Date().toISOString(),
+      text: StringUtil.trim`
+        ## API Design Instructions (Reference)
+
+        The following API-specific instructions were extracted from
+        the user's requirements. These focus on API interface design aspects
+        such as endpoint patterns, request/response formats, DTO schemas,
+        and operation specifications.
+
+        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}
+
+        ${transformInterfaceEndpointAuthorizationSection(props.authorizeOperations)}
+        
+        ## Target Group for Design (YOUR TASK)
+
+        You are designing base CRUD endpoints for the **${props.group.name}** group.
+
+        \`\`\`json
+        ${JSON.stringify(props.group)}
+        \`\`\`
+
+        Design base CRUD endpoints that cover all entities in this group.
+        `,
+    },
+  ],
+  userMessage: `Design endpoints for the ${props.group.name} group please`,
+});

package/src/orchestrate/interface/histories/transformInterfaceCommonHistory.ts

@@ -1,64 +1,64 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { v7 } from "uuid";
-
-import { AutoBeState } from "../../../context/AutoBeState";
-
-export const transformInterfaceCommonHistory = (
-  state: AutoBeState,
-): Array<IAgenticaHistoryJson.ISystemMessage> | null => {
-  if (state.analyze === null)
-    return [
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "systemMessage",
-        text: [
-          "Requirement analysis is not yet completed.",
-          "Don't call the any tool function,",
-          "but say to process the requirement analysis.",
-        ].join(" "),
-      },
-    ];
-  else if (state.database === null)
-    return [
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "systemMessage",
-        text: [
-          "Database schema generation is not yet completed.",
-          "Don't call the any tool function,",
-          "but say to process the database schema generation.",
-        ].join(" "),
-      },
-    ];
-  else if (state.analyze.step !== state.database.step)
-    return [
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "systemMessage",
-        text: [
-          "Database schema generation has not been updated",
-          "for the latest requirement analysis.",
-          "Don't call the any tool function,",
-          "but say to re-process the database schema generation.",
-        ].join(" "),
-      },
-    ];
-  else if (state.database.compiled.type !== "success")
-    return [
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "systemMessage",
-        text: [
-          "Database schema generation has not been updated",
-          "for the latest requirement analysis.",
-          "Don't call the any tool function,",
-          "but say to re-process the database schema generation.",
-        ].join(" "),
-      },
-    ];
-  return null;
-};
+import { IAgenticaHistoryJson } from "@agentica/core";
+import { v7 } from "uuid";
+
+import { AutoBeState } from "../../../context/AutoBeState";
+
+export const transformInterfaceCommonHistory = (
+  state: AutoBeState,
+): Array<IAgenticaHistoryJson.ISystemMessage> | null => {
+  if (state.analyze === null)
+    return [
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "systemMessage",
+        text: [
+          "Requirement analysis is not yet completed.",
+          "Don't call the any tool function,",
+          "but say to process the requirement analysis.",
+        ].join(" "),
+      },
+    ];
+  else if (state.database === null)
+    return [
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "systemMessage",
+        text: [
+          "Database schema generation is not yet completed.",
+          "Don't call the any tool function,",
+          "but say to process the database schema generation.",
+        ].join(" "),
+      },
+    ];
+  else if (state.analyze.step !== state.database.step)
+    return [
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "systemMessage",
+        text: [
+          "Database schema generation has not been updated",
+          "for the latest requirement analysis.",
+          "Don't call the any tool function,",
+          "but say to re-process the database schema generation.",
+        ].join(" "),
+      },
+    ];
+  else if (state.database.compiled.type !== "success")
+    return [
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "systemMessage",
+        text: [
+          "Database schema generation has not been updated",
+          "for the latest requirement analysis.",
+          "Don't call the any tool function,",
+          "but say to re-process the database schema generation.",
+        ].join(" "),
+      },
+    ];
+  return null;
+};

package/src/orchestrate/interface/histories/transformInterfaceEndpointAuthorizationSection.ts

@@ -1,42 +1,42 @@
-import { AutoBeOpenApi } from "@autobe/interface";
-import { StringUtil } from "@autobe/utils";
-
-export const transformInterfaceEndpointAuthorizationSection = (
-  operations: AutoBeOpenApi.IOperation[],
-): string => {
-  if (operations.length === 0) return "";
-
-  const table: string = [
-    "| Actor | Endpoint | Authorization Type | Request Body | Response Body |",
-    "|-------|----------|--------------------|--------------|---------------|",
-    ...operations
-      .filter(
-        (op) =>
-          op.authorizationActor !== null &&
-          op.requestBody !== null &&
-          op.responseBody !== null,
-      )
-      .map((op) =>
-        [
-          op.authorizationActor ?? "",
-          `${op.method.toUpperCase()} ${op.path}`,
-          op.authorizationType ?? "",
-          op.requestBody?.typeName ?? "",
-          op.responseBody?.typeName ?? "",
-        ].join(" | "),
-      ),
-  ].join("\n");
-
-  return StringUtil.trim`
-    ## Already Generated Authorization Operations (DO NOT DUPLICATE)
-
-    The following authorization operations have already been generated 
-    by the Authorization Agent.
-    
-    Do NOT create any endpoints that duplicate these operations. All 
-    authentication-related operations are handled exclusively by 
-    the Authorization Agent. This is not your responsibility.
-
-    ${table}
-  `;
-};
+import { AutoBeOpenApi } from "@autobe/interface";
+import { StringUtil } from "@autobe/utils";
+
+export const transformInterfaceEndpointAuthorizationSection = (
+  operations: AutoBeOpenApi.IOperation[],
+): string => {
+  if (operations.length === 0) return "";
+
+  const table: string = [
+    "| Actor | Endpoint | Authorization Type | Request Body | Response Body |",
+    "|-------|----------|--------------------|--------------|---------------|",
+    ...operations
+      .filter(
+        (op) =>
+          op.authorizationActor !== null &&
+          op.requestBody !== null &&
+          op.responseBody !== null,
+      )
+      .map((op) =>
+        [
+          op.authorizationActor ?? "",
+          `${op.method.toUpperCase()} ${op.path}`,
+          op.authorizationType ?? "",
+          op.requestBody?.typeName ?? "",
+          op.responseBody?.typeName ?? "",
+        ].join(" | "),
+      ),
+  ].join("\n");
+
+  return StringUtil.trim`
+    ## Already Generated Authorization Operations (DO NOT DUPLICATE)
+
+    The following authorization operations have already been generated 
+    by the Authorization Agent.
+    
+    Do NOT create any endpoints that duplicate these operations. All 
+    authentication-related operations are handled exclusively by 
+    the Authorization Agent. This is not your responsibility.
+
+    ${table}
+  `;
+};

package/src/orchestrate/interface/histories/transformInterfaceGroupHistory.ts

@@ -1,103 +1,103 @@
-import { AutoBeDatabase } from "@autobe/interface";
-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";
-import { transformInterfaceCommonHistory } from "./transformInterfaceCommonHistory";
-
-export const transformInterfaceGroupHistory = (props: {
-  state: AutoBeState;
-  instruction: string;
-  preliminary: AutoBePreliminaryController<
-    | "analysisSections"
-    | "databaseSchemas"
-    | "previousAnalysisSections"
-    | "previousDatabaseSchemas"
-    | "previousInterfaceOperations"
-  >;
-}): IAutoBeOrchestrateHistory => {
-  const common = transformInterfaceCommonHistory(props.state);
-  if (common !== null)
-    return {
-      histories: [common[0], ...common.slice(1)],
-      userMessage: "Please wait for prerequisites to complete",
-    };
-  const app: AutoBeDatabase.IApplication | undefined =
-    props.state.database?.result.data;
-  return {
-    histories: [
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "systemMessage",
-        text: AutoBeSystemPromptConstant.INTERFACE_GROUP,
-      },
-      ...props.preliminary.getHistories(),
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "assistantMessage",
-        text: StringUtil.trim`
-          Here is the database grouping information you can reference.
-
-          However, database groups are your **STARTING POINT**, not your **STRICT BOUNDARY**:
-
-          - **Use database groups as your BASELINE**: Most API groups should align with database 
-                                                      groups (1:1 mapping)
-          - **API ≠ Database**: APIs serve different purposes than normalized database schemas
-            • APIs organize by **USER WORKFLOWS** (how users interact)
-            • Databases organize by **DATA NORMALIZATION** (how data is stored)
-          - **When to DIVERGE from database groups**:
-            • Cross-schema operations: Analytics/dashboards aggregating multiple database groups
-            • Workflow-based APIs: Checkout spanning Carts + Orders + Payments
-            • Pure computation: APIs that don't touch database at all
-            • External integrations: Webhooks, third-party API gateways
-          - **CRITICAL**: Don't create 1-2 mega-groups ignoring database organization. 
-                          Start with database groups, then add API-specific groups as needed.
-
-          Belonged Namespace | Table Name | Stance | Summary
-          -------------------|------------|--------|-----------
-          ${app?.files
-            .map((file) => file.models.map((model) => [file, model] as const))
-            .flat()
-            .map(([file, model]) =>
-              [
-                file.namespace,
-                model.name,
-                model.stance,
-                StringUtil.summary(model.description),
-              ].join(" | "),
-            )
-            .join("\n")}
-        `,
-      },
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "assistantMessage",
-        text: StringUtil.trim`
-          ## API Design Instructions
-
-          The following API-specific instructions were extracted from
-          the user's requirements. These focus on API interface design aspects
-          such as endpoint patterns, request/response formats, DTO schemas,
-          and operation specifications.
-
-          Follow these instructions when organizing API endpoints.
-          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: "Design API endpoint groups please",
-  };
-};
+import { AutoBeDatabase } from "@autobe/interface";
+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";
+import { transformInterfaceCommonHistory } from "./transformInterfaceCommonHistory";
+
+export const transformInterfaceGroupHistory = (props: {
+  state: AutoBeState;
+  instruction: string;
+  preliminary: AutoBePreliminaryController<
+    | "analysisSections"
+    | "databaseSchemas"
+    | "previousAnalysisSections"
+    | "previousDatabaseSchemas"
+    | "previousInterfaceOperations"
+  >;
+}): IAutoBeOrchestrateHistory => {
+  const common = transformInterfaceCommonHistory(props.state);
+  if (common !== null)
+    return {
+      histories: [common[0], ...common.slice(1)],
+      userMessage: "Please wait for prerequisites to complete",
+    };
+  const app: AutoBeDatabase.IApplication | undefined =
+    props.state.database?.result.data;
+  return {
+    histories: [
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "systemMessage",
+        text: AutoBeSystemPromptConstant.INTERFACE_GROUP,
+      },
+      ...props.preliminary.getHistories(),
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "assistantMessage",
+        text: StringUtil.trim`
+          Here is the database grouping information you can reference.
+
+          However, database groups are your **STARTING POINT**, not your **STRICT BOUNDARY**:
+
+          - **Use database groups as your BASELINE**: Most API groups should align with database 
+                                                      groups (1:1 mapping)
+          - **API ≠ Database**: APIs serve different purposes than normalized database schemas
+            • APIs organize by **USER WORKFLOWS** (how users interact)
+            • Databases organize by **DATA NORMALIZATION** (how data is stored)
+          - **When to DIVERGE from database groups**:
+            • Cross-schema operations: Analytics/dashboards aggregating multiple database groups
+            • Workflow-based APIs: Checkout spanning Carts + Orders + Payments
+            • Pure computation: APIs that don't touch database at all
+            • External integrations: Webhooks, third-party API gateways
+          - **CRITICAL**: Don't create 1-2 mega-groups ignoring database organization. 
+                          Start with database groups, then add API-specific groups as needed.
+
+          Belonged Namespace | Table Name | Stance | Summary
+          -------------------|------------|--------|-----------
+          ${app?.files
+            .map((file) => file.models.map((model) => [file, model] as const))
+            .flat()
+            .map(([file, model]) =>
+              [
+                file.namespace,
+                model.name,
+                model.stance,
+                StringUtil.summary(model.description),
+              ].join(" | "),
+            )
+            .join("\n")}
+        `,
+      },
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "assistantMessage",
+        text: StringUtil.trim`
+          ## API Design Instructions
+
+          The following API-specific instructions were extracted from
+          the user's requirements. These focus on API interface design aspects
+          such as endpoint patterns, request/response formats, DTO schemas,
+          and operation specifications.
+
+          Follow these instructions when organizing API endpoints.
+          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: "Design API endpoint groups please",
+  };
+};