@autobe/agent 0.28.1 → 0.29.0

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

@@ -1,75 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { AutoBeAnalyzeActor, AutoBeAnalyzeHistory } from "@autobe/interface";
-import { StringUtil } from "@autobe/utils";
-import { v7 } from "uuid";
-
-import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
-import { AutoBeState } from "../../../context/AutoBeState";
-import { transformInterfaceAssetHistories } from "./transformInterfaceAssetHistories";
-
-export const transformInterfaceAuthorizationsHistories = (props: {
-  state: AutoBeState;
-  actor: AutoBeAnalyzeActor;
-  instruction: string;
-}): Array<
-  IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage
-> => {
-  const analyze: AutoBeAnalyzeHistory = props.state.analyze!;
-  return [
-    {
-      type: "systemMessage",
-      id: v7(),
-      created_at: new Date().toISOString(),
-      text: AutoBeSystemPromptConstant.INTERFACE_AUTHORIZATION,
-    },
-    ...transformInterfaceAssetHistories(props.state),
-    {
-      type: "systemMessage",
-      id: v7(),
-      created_at: new Date().toISOString(),
-      text: StringUtil.trim`
-        ## Service Prefix
-        - Original: ${analyze.prefix}
-        - PascalCase for DTOs: ${analyze.prefix
-          .split(/[-_]/)
-          .map((p) => p.charAt(0).toUpperCase() + p.slice(1))
-          .join("")}
-        - Expected DTO pattern: I${analyze.prefix
-          .split(/[-_]/)
-          .map((p) => p.charAt(0).toUpperCase() + p.slice(1))
-          .join("")}{EntityName}
-      `,
-    },
-    {
-      type: "assistantMessage",
-      id: v7(),
-      created_at: new Date().toISOString(),
-      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 designing authorization operations for ${props.actor.name}.
-        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}
-
-        ## Actor
-
-        You have to make API operations for the given actor:
-
-        \`\`\`json
-        ${JSON.stringify(props.actor)}
-        \`\`\`
-      `,
-    },
-  ];
-};

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

@@ -1,82 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { AutoBeOpenApi } from "@autobe/interface";
-import { StringUtil } from "@autobe/utils";
-import { v7 } from "uuid";
-
-import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
-import { AutoBeState } from "../../../context/AutoBeState";
-import { transformInterfaceAssetHistories } from "./transformInterfaceAssetHistories";
-
-export const transformInterfaceComplementHistories = (props: {
-  state: AutoBeState;
-  instruction: string;
-  missed: string[];
-  document: AutoBeOpenApi.IDocument;
-}): Array<
-  IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage
-> => [
-  {
-    type: "systemMessage",
-    id: v7(),
-    created_at: new Date().toISOString(),
-    text: AutoBeSystemPromptConstant.INTERFACE_OPERATION,
-  },
-  ...transformInterfaceAssetHistories(props.state),
-  {
-    type: "systemMessage",
-    id: v7(),
-    created_at: new Date().toISOString(),
-    text: AutoBeSystemPromptConstant.INTERFACE_SCHEMA,
-  },
-  {
-    type: "systemMessage",
-    id: v7(),
-    created_at: new Date().toISOString(),
-    text: AutoBeSystemPromptConstant.INTERFACE_COMPLEMENT,
-  },
-  {
-    type: "assistantMessage",
-    id: v7(),
-    created_at: new Date().toISOString(),
-    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 completing missing schema types.
-      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}
-
-      ## Operations
-
-      Here is the OpenAPI operations what you AI have made:
-
-      \`\`\`json
-      ${JSON.stringify(props.document.operations)}
-      \`\`\`
-
-      ## Schemas
-
-      Here is the OpenAPI schemas what you AI have made:
-
-      \`\`\`json
-      ${JSON.stringify(props.document.components.schemas)}
-      \`\`\`
-
-      ## Missed Types
-
-      However, you AI have missed below schema types:
-
-      ${props.missed.map((s) => `- ${s}`).join("\n")}
-    `,
-  },
-];

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

@@ -1,72 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { AutoBeOpenApi } from "@autobe/interface";
-import { AutoBeInterfaceGroup } from "@autobe/interface/src/histories/contents/AutoBeInterfaceGroup";
-import { StringUtil } from "@autobe/utils";
-import { v7 } from "uuid";
-
-import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
-import { AutoBeState } from "../../../context/AutoBeState";
-import { transformInterfaceAssetHistories } from "./transformInterfaceAssetHistories";
-
-export const transformInterfaceEndpointHistories = (props: {
-  state: AutoBeState;
-  group: AutoBeInterfaceGroup;
-  authorizations: AutoBeOpenApi.IOperation[];
-  instruction: string;
-}): Array<
-  IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage
-> => [
-  {
-    type: "systemMessage",
-    id: v7(),
-    created_at: new Date().toISOString(),
-    text: AutoBeSystemPromptConstant.INTERFACE_ENDPOINT,
-  },
-  ...transformInterfaceAssetHistories(props.state),
-  {
-    type: "assistantMessage",
-    id: v7(),
-    created_at: new Date().toISOString(),
-    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 designing endpoints for the ${props.group.name} group.
-      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}
-
-      ## Group Information
-
-      Here is the target group for the endpoints:
-
-      \`\`\`json
-      ${JSON.stringify(props.group)}
-      \`\`\`
-
-      ## Already Existing Operations
-
-      These operations already exist. Do NOT create similar endpoints:
-
-      \`\`\`json
-      ${JSON.stringify(
-        props.authorizations.map((op) => ({
-          path: op.path,
-          method: op.method,
-          name: op.name,
-          summary: op.summary,
-        })),
-      )}
-      \`\`\`
-    `,
-  },
-];

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

@@ -1,40 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { AutoBeOpenApi } from "@autobe/interface";
-import { v7 } from "uuid";
-
-import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
-import { AutoBeState } from "../../../context/AutoBeState";
-import { transformInterfaceAssetHistories } from "./transformInterfaceAssetHistories";
-
-export const transformInterfaceEndpointsReviewHistories = (
-  state: AutoBeState,
-  endpoints: AutoBeOpenApi.IEndpoint[],
-): Array<
-  IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage
-> => [
-  {
-    type: "systemMessage",
-    id: v7(),
-    created_at: new Date().toISOString(),
-    text: AutoBeSystemPromptConstant.INTERFACE_ENDPOINT,
-  },
-  ...transformInterfaceAssetHistories(state),
-  {
-    id: v7(),
-    type: "assistantMessage",
-    text: [
-      "Below are endpoints generated by your request.",
-      "",
-      "```json",
-      JSON.stringify(endpoints),
-      "```",
-    ].join("\n"),
-    created_at: new Date().toISOString(),
-  },
-  {
-    id: v7(),
-    type: "systemMessage",
-    text: AutoBeSystemPromptConstant.INTERFACE_ENDPOINTS_REVIEW,
-    created_at: new Date().toISOString(),
-  },
-];

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

@@ -1,78 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { AutoBeAnalyzeHistory, AutoBeOpenApi } from "@autobe/interface";
-import { StringUtil } from "@autobe/utils";
-import { v7 } from "uuid";
-
-import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
-import { AutoBeState } from "../../../context/AutoBeState";
-import { transformInterfaceAssetHistories } from "./transformInterfaceAssetHistories";
-
-export const transformInterfaceOperationHistories = (props: {
-  state: AutoBeState;
-  endpoints: AutoBeOpenApi.IEndpoint[];
-  instruction: string;
-}): Array<
-  IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage
-> => {
-  const analyze: AutoBeAnalyzeHistory = props.state.analyze!;
-  return [
-    {
-      type: "systemMessage",
-      id: v7(),
-      created_at: new Date().toISOString(),
-      text: AutoBeSystemPromptConstant.INTERFACE_OPERATION,
-    },
-    ...transformInterfaceAssetHistories(props.state),
-    {
-      type: "systemMessage",
-      id: v7(),
-      created_at: new Date().toISOString(),
-      text: StringUtil.trim`
-        ## Service Prefix
-        - Original: ${analyze.prefix}
-        - PascalCase for DTOs: ${analyze.prefix
-          .split(/[-_]/)
-          .map((p) => p.charAt(0).toUpperCase() + p.slice(1))
-          .join("")}
-        - Expected DTO pattern: I${analyze.prefix
-          .split(/[-_]/)
-          .map((p) => p.charAt(0).toUpperCase() + p.slice(1))
-          .join("")}{EntityName}
-      `,
-    },
-    {
-      type: "assistantMessage",
-      id: v7(),
-      created_at: new Date().toISOString(),
-      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 designing 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}
-
-        ## Operations
-
-        You have to make API operations for the given endpoints:
-
-        \`\`\`json
-        ${JSON.stringify(props.endpoints)}
-        \`\`\`
-
-        If there is a content in the failure, it is to explain why it failed before.
-        Please supplement or modify the Operation accordingly.
-      `,
-    },
-  ];
-};

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

@@ -1,44 +0,0 @@
-import { IMicroAgenticaHistoryJson } from "@agentica/core";
-import { AutoBeOpenApi } from "@autobe/interface";
-import { StringUtil } from "@autobe/utils";
-import { ILlmSchema } from "@samchon/openapi";
-import { v7 } from "uuid";
-
-import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
-import { AutoBeContext } from "../../../context/AutoBeContext";
-import { transformInterfaceAssetHistories } from "./transformInterfaceAssetHistories";
-
-export function transformInterfaceOperationsReviewHistories<
-  Model extends ILlmSchema.Model,
->(
-  ctx: AutoBeContext<Model>,
-  operations: AutoBeOpenApi.IOperation[],
-): Array<IMicroAgenticaHistoryJson> {
-  return [
-    {
-      type: "systemMessage",
-      id: v7(),
-      created_at: new Date().toISOString(),
-      text: AutoBeSystemPromptConstant.INTERFACE_OPERATION,
-    },
-    ...transformInterfaceAssetHistories(ctx.state()),
-    {
-      type: "systemMessage",
-      id: v7(),
-      created_at: new Date().toISOString(),
-      text: AutoBeSystemPromptConstant.INTERFACE_OPERATION_REVIEW,
-    },
-    {
-      type: "assistantMessage",
-      id: v7(),
-      created_at: new Date().toISOString(),
-      text: StringUtil.trim`
-        Review the following API operations:
-
-        \`\`\`json
-        ${JSON.stringify(operations)}
-        \`\`\`
-      `,
-    },
-  ];
-}

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

@@ -1,118 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { AutoBeOpenApi } from "@autobe/interface";
-import { StringUtil } from "@autobe/utils";
-import { OpenApiTypeChecker } from "@samchon/openapi";
-import { v7 } from "uuid";
-
-import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
-import { getReferenceIds } from "../../test/utils/getReferenceIds";
-
-export const transformInterfacePrerequisitesHistories = (
-  document: AutoBeOpenApi.IDocument,
-  include: AutoBeOpenApi.IOperation[],
-): Array<
-  IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage
-> => {
-  const domainSchemas: Record<string, AutoBeOpenApi.IJsonSchemaDescriptive> =
-    {};
-  const visit = (key: string) =>
-    OpenApiTypeChecker.visit({
-      schema: {
-        $ref: `#/components/schemas/${key}`,
-      },
-      components: document.components,
-      closure: (next) => {
-        if (OpenApiTypeChecker.isReference(next))
-          domainSchemas[next.$ref.split("/").pop()!] =
-            document.components.schemas[next.$ref.split("/").pop()!];
-      },
-    });
-  for (const op of include) {
-    if (op.requestBody) visit(op.requestBody.typeName);
-    if (op.responseBody) visit(op.responseBody.typeName);
-  }
-
-  return [
-    {
-      type: "systemMessage",
-      id: v7(),
-      created_at: new Date().toISOString(),
-      text: AutoBeSystemPromptConstant.INTERFACE_PREREQUISITE,
-    },
-    {
-      type: "assistantMessage",
-      id: v7(),
-      created_at: new Date().toISOString(),
-      text: StringUtil.trim`
-        ## Document Overview
-
-        ### Entire API Operations
-        
-        All operations in this project for prerequisite references.
-
-        These are the complete list of API endpoints that can be used 
-        as prerequisites. You should select appropriate operations from 
-        this list when establishing dependency chains.
-
-        \`\`\`json
-        ${JSON.stringify({
-          operations: document.operations
-            .filter(
-              (op) => op.authorizationType === null && op.method === "post",
-            )
-            .map((op) => {
-              return {
-                ...op,
-                prerequisites: undefined,
-              };
-            }),
-        })}
-        \`\`\`
-
-        ### Entire Schema Definitions
-
-        Data structure definitions to understand entity relationships.
-
-        Use these schemas to identify parent-child relationships and 
-        data dependencies between operations.
-
-        \`\`\`json
-        ${JSON.stringify({
-          components: {
-            schemas: document.components.schemas,
-          },
-        })}
-        \`\`\`
-            
-        ## Target Operations and Schemas
-
-        ### Target Operations
-
-        Operations requiring prerequisite analysis.
-        
-        For each of these operations, analyze if they need any prerequisites 
-        from the available operations above. Add prerequisites only when there 
-        are genuine dependencies like resource existence checks or state validations.
-
-        \`\`\`json
-        ${JSON.stringify(
-          include.map((op) => {
-            return {
-              ...op,
-              requiredIds: getReferenceIds({ document, operation: op }),
-            };
-          }),
-        )}
-        \`\`\`
-
-        ### Domain Schemas
-
-        Schema definitions for the target operations.
-
-        \`\`\`json
-        ${JSON.stringify(domainSchemas)}
-        \`\`\`
-      `,
-    },
-  ];
-};

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

@@ -1,80 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { AutoBeOpenApi } from "@autobe/interface";
-import { StringUtil } from "@autobe/utils";
-import { v7 } from "uuid";
-
-import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
-import { AutoBeState } from "../../../context/AutoBeState";
-import { transformInterfaceAssetHistories } from "./transformInterfaceAssetHistories";
-
-export const transformInterfaceSchemaHistories = (props: {
-  state: AutoBeState;
-  operations: AutoBeOpenApi.IOperation[];
-  typeNames: string[];
-  instruction: string;
-}): Array<
-  IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage
-> => {
-  const schemas: Set<string> = new Set();
-  for (const op of props.operations) {
-    if (op.requestBody) schemas.add(op.requestBody.typeName);
-    if (op.responseBody) schemas.add(op.responseBody.typeName);
-  }
-  return [
-    {
-      type: "systemMessage",
-      id: v7(),
-      created_at: new Date().toISOString(),
-      text: AutoBeSystemPromptConstant.INTERFACE_SCHEMA,
-    },
-    ...transformInterfaceAssetHistories(props.state),
-    {
-      type: "assistantMessage",
-      id: v7(),
-      created_at: new Date().toISOString(),
-      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 creating JSON schema components.
-      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}
-
-      ## Operations (Filtered for Target Schemas)
-
-      Here is the list of API operations that directly use the schemas
-      you need to generate (via requestBody.typeName or responseBody.typeName).
-
-      These are the ONLY operations relevant to your current task - other
-      operations have been filtered out to reduce noise and improve focus:
-
-      \`\`\`json
-      ${JSON.stringify(props.operations)}
-      \`\`\`
-
-      ## Schemas
-
-      Here is the list of request/response bodies' type names from
-      OpenAPI operations.
-
-      Reference them when creating DTO schema components, especially
-      considering the DTO relationships.
-
-      ${Array.from(schemas)
-        .map((k) => `- \`${k}\``)
-        .join("\n")}
-
-    `,
-    },
-  ];
-};

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

@@ -1,55 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { StringUtil } from "@autobe/utils";
-import { v7 } from "uuid";
-
-import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
-
-export const transformInterfaceSchemaRenameHistories = (props: {
-  tableNames: string[];
-  typeNames: string[];
-}): Array<
-  IAgenticaHistoryJson.ISystemMessage | IAgenticaHistoryJson.IAssistantMessage
-> => {
-  return [
-    {
-      type: "systemMessage",
-      id: v7(),
-      created_at: new Date().toISOString(),
-      text: AutoBeSystemPromptConstant.INTERFACE_SCHEMA_RENAME,
-    },
-    {
-      type: "assistantMessage",
-      id: v7(),
-      created_at: new Date().toISOString(),
-      text: StringUtil.trim`
-        ## Prisma Table Names
-
-        Here is the complete list of table names from the Prisma database schema.
-        Use these as the source of truth for determining correct DTO type names.
-
-        Each table name should be converted to a DTO type name by:
-        1. Converting from snake_case to PascalCase
-        2. Preserving ALL words from the table name
-        3. Adding "I" prefix for interface types
-
-        **Table Names:**
-        ${props.tableNames.map((name) => `- \`${name}\``).join("\n")}
-
-        ## Current DTO Type Names
-
-        Here is the list of existing DTO type names currently in the OpenAPI specification.
-        Analyze these to identify which ones violate the naming rules by omitting
-        intermediate words or service prefixes from their corresponding table names.
-
-        **Current Type Names:**
-        ${props.typeNames.map((name) => `- \`${name}\``).join("\n")}
-
-        ## Your Task
-
-        Compare the table names with the current type names to identify violations.
-        For each type name that incorrectly omits words from its table name,
-        provide a refactoring entry with the correct name that preserves all components.
-      `,
-    },
-  ];
-};