@autobe/agent 0.30.0-dev.20260315 → 0.30.1

package/src/orchestrate/test/histories/transformTestPrepareWriteHistory.ts

@@ -1,95 +1,95 @@
-import { AutoBeOpenApi } from "@autobe/interface";
-import { StringUtil } from "@autobe/utils";
-import { v7 } from "uuid";
-
-import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
-import { AutoBeContext } from "../../../context/AutoBeContext";
-import { IAutoBeOrchestrateHistory } from "../../../structures/IAutoBeOrchestrateHistory";
-import { getTestExternalDeclarations } from "../compile/getTestExternalDeclarations";
-import { AutoBeTestPrepareProgrammer } from "../programmers/AutoBeTestPrepareProgrammer";
-
-export async function transformTestPrepareWriteHistory(
-  ctx: AutoBeContext,
-  props: {
-    typeName: string;
-    schema: AutoBeOpenApi.IJsonSchema.IObject;
-    document: AutoBeOpenApi.IDocument;
-    instruction: string;
-  },
-): Promise<IAutoBeOrchestrateHistory> {
-  const dto: Record<string, string> =
-    await AutoBeTestPrepareProgrammer.writeStructures(ctx, props.typeName);
-  return {
-    histories: [
-      {
-        id: v7(),
-        type: "systemMessage",
-        created_at: new Date().toISOString(),
-        text: AutoBeSystemPromptConstant.TEST_PREPARE_WRITE,
-      },
-      {
-        id: v7(),
-        type: "assistantMessage",
-        created_at: new Date().toISOString(),
-        text: StringUtil.trim`
-          Here is the list of input material composition.
-
-          Generate a resource preparation function based on the following information.
-
-          ## Instructions
-
-          The following instructions were extracted from the user's requirements
-          and conversations. These instructions may contain specific guidance about
-          how generation functions should be implemented, including authentication
-          patterns, error handling approaches, and data transformation strategies.
-
-          Follow these instructions when implementing the generation function.
-          Carefully distinguish between:
-          
-          - Suggestions or recommendations (consider these as guidance)
-          - Direct specifications or explicit commands (these must be followed exactly)
-
-          
-          ${props.instruction}
-
-          ## Function Name
-
-          You have to make ${AutoBeTestPrepareProgrammer.getFunctionName(props.typeName)} function.
-
-          ## DTO Types
-
-          Here is the list of DTO types relevant with the ${props.typeName} type:
-
-          \`\`\`json
-          ${JSON.stringify(dto)}
-          \`\`\`
-
-          ### Properties
-
-          When you composing ${props.typeName} typed data, you have check those properties:
-          
-          ${Object.keys(props.schema.properties)
-            .map((s) => `- ${s}`)
-            .join("\n")}
-            
-          ## External Definitions
-
-          Here is the external declaration files (d.ts) you can reference.
-
-          \`\`\`json
-          ${JSON.stringify(await getTestExternalDeclarations(ctx))}
-          \`\`\`
-
-          ## Template Code
-
-          Here is the template code you have to implement.
-          
-          Reference the template code, and fill the proper code to each property.
-
-          ${AutoBeTestPrepareProgrammer.writeTemplateCode(props)}
-        `,
-      },
-    ],
-    userMessage: "Generate the test data preparation function for this DTO.",
-  };
-}
+import { AutoBeOpenApi } from "@autobe/interface";
+import { StringUtil } from "@autobe/utils";
+import { v7 } from "uuid";
+
+import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
+import { AutoBeContext } from "../../../context/AutoBeContext";
+import { IAutoBeOrchestrateHistory } from "../../../structures/IAutoBeOrchestrateHistory";
+import { getTestExternalDeclarations } from "../compile/getTestExternalDeclarations";
+import { AutoBeTestPrepareProgrammer } from "../programmers/AutoBeTestPrepareProgrammer";
+
+export async function transformTestPrepareWriteHistory(
+  ctx: AutoBeContext,
+  props: {
+    typeName: string;
+    schema: AutoBeOpenApi.IJsonSchema.IObject;
+    document: AutoBeOpenApi.IDocument;
+    instruction: string;
+  },
+): Promise<IAutoBeOrchestrateHistory> {
+  const dto: Record<string, string> =
+    await AutoBeTestPrepareProgrammer.writeStructures(ctx, props.typeName);
+  return {
+    histories: [
+      {
+        id: v7(),
+        type: "systemMessage",
+        created_at: new Date().toISOString(),
+        text: AutoBeSystemPromptConstant.TEST_PREPARE_WRITE,
+      },
+      {
+        id: v7(),
+        type: "assistantMessage",
+        created_at: new Date().toISOString(),
+        text: StringUtil.trim`
+          Here is the list of input material composition.
+
+          Generate a resource preparation function based on the following information.
+
+          ## Instructions
+
+          The following instructions were extracted from the user's requirements
+          and conversations. These instructions may contain specific guidance about
+          how generation functions should be implemented, including authentication
+          patterns, error handling approaches, and data transformation strategies.
+
+          Follow these instructions when implementing the generation function.
+          Carefully distinguish between:
+          
+          - Suggestions or recommendations (consider these as guidance)
+          - Direct specifications or explicit commands (these must be followed exactly)
+
+          
+          ${props.instruction}
+
+          ## Function Name
+
+          You have to make ${AutoBeTestPrepareProgrammer.getFunctionName(props.typeName)} function.
+
+          ## DTO Types
+
+          Here is the list of DTO types relevant with the ${props.typeName} type:
+
+          \`\`\`json
+          ${JSON.stringify(dto)}
+          \`\`\`
+
+          ### Properties
+
+          When you composing ${props.typeName} typed data, you have check those properties:
+          
+          ${Object.keys(props.schema.properties)
+            .map((s) => `- ${s}`)
+            .join("\n")}
+            
+          ## External Definitions
+
+          Here is the external declaration files (d.ts) you can reference.
+
+          \`\`\`json
+          ${JSON.stringify(await getTestExternalDeclarations(ctx))}
+          \`\`\`
+
+          ## Template Code
+
+          Here is the template code you have to implement.
+          
+          Reference the template code, and fill the proper code to each property.
+
+          ${AutoBeTestPrepareProgrammer.writeTemplateCode(props)}
+        `,
+      },
+    ],
+    userMessage: "Generate the test data preparation function for this DTO.",
+  };
+}

package/src/orchestrate/test/histories/transformTestScenarioHistory.ts

@@ -1,120 +1,120 @@
-import { AutoBeInterfaceAuthorization, AutoBeOpenApi } from "@autobe/interface";
-import { MapUtil, 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 { IAutoBeTestScenarioAuthorizationActor } from "../structures/IAutoBeTestScenarioAuthorizationActor";
-import { getPrerequisites } from "../utils/getPrerequisites";
-
-/**
- * Transform test scenario generation context into conversational history.
- *
- * Following the InterfacePrerequisite pattern:
- *
- * - Provides system prompts
- * - Provides preliminary data histories
- * - Provides single target operation
- * - Provides prerequisites for the operation
- * - Provides authorization actors
- *
- * @param props - Configuration for history transformation
- * @returns Complete conversation history ready for LLM agent processing
- */
-export const transformTestScenarioHistory = (props: {
-  state: AutoBeState;
-  operation: AutoBeOpenApi.IOperation;
-  preliminary: AutoBePreliminaryController<
-    "analysisSections" | "interfaceOperations" | "interfaceSchemas"
-  >;
-  instruction: string;
-}): IAutoBeOrchestrateHistory => {
-  const document: AutoBeOpenApi.IDocument = props.state.interface!.document!;
-  const authorizations: AutoBeInterfaceAuthorization[] =
-    props.state.interface?.authorizations ?? [];
-  const authorizationActors: Map<
-    string,
-    IAutoBeTestScenarioAuthorizationActor
-  > = new Map();
-
-  for (const authorization of authorizations) {
-    for (const op of authorization.operations) {
-      if (op.authorizationType === null) continue;
-      const value: IAutoBeTestScenarioAuthorizationActor = MapUtil.take(
-        authorizationActors,
-        authorization.name,
-        () => ({
-          name: authorization.name,
-          join: null,
-          login: null,
-        }),
-      );
-      if (op.authorizationType === "join") value.join = op;
-      else if (op.authorizationType === "login") value.login = op;
-    }
-  }
-
-  // Find authorization actor for this operation
-  const operationAuthorizationActors = Array.from(
-    authorizationActors.values(),
-  ).filter((actor) => actor.name === props.operation.authorizationActor);
-
-  return {
-    histories: [
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "systemMessage",
-        text: AutoBeSystemPromptConstant.TEST_SCENARIO,
-      },
-      ...props.preliminary.getHistories(),
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "assistantMessage",
-        text: StringUtil.trim`
-          ## Instructions
-
-          The following e2e-test-specific instructions were extracted from
-          the user's requirements and conversations. These instructions focus
-          exclusively on test-related aspects such as test coverage priorities,
-          specific edge cases to validate, business logic verification strategies,
-          and critical user workflows that must be tested.
-
-          Follow these instructions when generating test scenario.
-          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}
-
-          ## Target Operation
-
-          Single operation requiring test scenario generation.
-
-          Generate 1-3 focused test scenarios for this operation that validate
-          the most critical business workflows. Focus on primary success paths
-          and important edge cases.
-
-          \`\`\`json
-          ${JSON.stringify({
-            operation: props.operation,
-            prerequisites: getPrerequisites({
-              endpoint: props.operation,
-              document,
-            }),
-            authorizationActors: operationAuthorizationActors,
-          })}
-          \`\`\`
-
-        `,
-      },
-    ],
-    userMessage: "Design test scenarios for the target operation please",
-  };
-};
+import { AutoBeInterfaceAuthorization, AutoBeOpenApi } from "@autobe/interface";
+import { MapUtil, 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 { IAutoBeTestScenarioAuthorizationActor } from "../structures/IAutoBeTestScenarioAuthorizationActor";
+import { getPrerequisites } from "../utils/getPrerequisites";
+
+/**
+ * Transform test scenario generation context into conversational history.
+ *
+ * Following the InterfacePrerequisite pattern:
+ *
+ * - Provides system prompts
+ * - Provides preliminary data histories
+ * - Provides single target operation
+ * - Provides prerequisites for the operation
+ * - Provides authorization actors
+ *
+ * @param props - Configuration for history transformation
+ * @returns Complete conversation history ready for LLM agent processing
+ */
+export const transformTestScenarioHistory = (props: {
+  state: AutoBeState;
+  operation: AutoBeOpenApi.IOperation;
+  preliminary: AutoBePreliminaryController<
+    "analysisSections" | "interfaceOperations" | "interfaceSchemas"
+  >;
+  instruction: string;
+}): IAutoBeOrchestrateHistory => {
+  const document: AutoBeOpenApi.IDocument = props.state.interface!.document!;
+  const authorizations: AutoBeInterfaceAuthorization[] =
+    props.state.interface?.authorizations ?? [];
+  const authorizationActors: Map<
+    string,
+    IAutoBeTestScenarioAuthorizationActor
+  > = new Map();
+
+  for (const authorization of authorizations) {
+    for (const op of authorization.operations) {
+      if (op.authorizationType === null) continue;
+      const value: IAutoBeTestScenarioAuthorizationActor = MapUtil.take(
+        authorizationActors,
+        authorization.name,
+        () => ({
+          name: authorization.name,
+          join: null,
+          login: null,
+        }),
+      );
+      if (op.authorizationType === "join") value.join = op;
+      else if (op.authorizationType === "login") value.login = op;
+    }
+  }
+
+  // Find authorization actor for this operation
+  const operationAuthorizationActors = Array.from(
+    authorizationActors.values(),
+  ).filter((actor) => actor.name === props.operation.authorizationActor);
+
+  return {
+    histories: [
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "systemMessage",
+        text: AutoBeSystemPromptConstant.TEST_SCENARIO,
+      },
+      ...props.preliminary.getHistories(),
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "assistantMessage",
+        text: StringUtil.trim`
+          ## Instructions
+
+          The following e2e-test-specific instructions were extracted from
+          the user's requirements and conversations. These instructions focus
+          exclusively on test-related aspects such as test coverage priorities,
+          specific edge cases to validate, business logic verification strategies,
+          and critical user workflows that must be tested.
+
+          Follow these instructions when generating test scenario.
+          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}
+
+          ## Target Operation
+
+          Single operation requiring test scenario generation.
+
+          Generate 1-3 focused test scenarios for this operation that validate
+          the most critical business workflows. Focus on primary success paths
+          and important edge cases.
+
+          \`\`\`json
+          ${JSON.stringify({
+            operation: props.operation,
+            prerequisites: getPrerequisites({
+              endpoint: props.operation,
+              document,
+            }),
+            authorizationActors: operationAuthorizationActors,
+          })}
+          \`\`\`
+
+        `,
+      },
+    ],
+    userMessage: "Design test scenarios for the target operation please",
+  };
+};

package/src/orchestrate/test/histories/transformTestScenarioReviewHistory.ts

@@ -1,99 +1,99 @@
-import { AutoBeOpenApi, AutoBeTestScenario } 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 { getPrerequisites } from "../utils/getPrerequisites";
-
-/**
- * Transform test scenario review context into conversational history.
- *
- * Creates the complete conversation history for reviewing a single test
- * scenario, including system prompts, user instructions, and the scenario to be
- * reviewed.
- *
- * @param props - Configuration for history transformation
- * @param props.state - Current AutoBe state containing interface document
- * @param props.instruction - E2E-test-specific instructions from user
- *   requirements
- * @param props.scenario - Single test scenario to review and potentially
- *   improve
- * @param props.preliminary - Controller for RAG-based preliminary data requests
- * @returns Complete conversation history ready for LLM agent processing
- */
-export function transformTestScenarioReviewHistory(props: {
-  state: AutoBeState;
-  instruction: string;
-  scenario: AutoBeTestScenario;
-  preliminary: AutoBePreliminaryController<
-    "analysisSections" | "interfaceOperations" | "interfaceSchemas"
-  >;
-}): IAutoBeOrchestrateHistory {
-  const document: AutoBeOpenApi.IDocument | undefined =
-    props.state.interface?.document;
-  if (document === undefined) {
-    throw new Error(
-      "Cannot review test scenarios because there are no operations.",
-    );
-  }
-  return {
-    histories: [
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "systemMessage",
-        text: AutoBeSystemPromptConstant.TEST_SCENARIO,
-      },
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "systemMessage",
-        text: AutoBeSystemPromptConstant.TEST_SCENARIO_REVIEW,
-      },
-      ...props.preliminary.getHistories(),
-      {
-        id: v7(),
-        created_at: new Date().toISOString(),
-        type: "assistantMessage",
-        text: StringUtil.trim`
-          ## Instructions
-
-          The following e2e-test-specific instructions were extracted from
-          the user's requirements and conversations. These instructions focus
-          exclusively on test-related aspects such as test coverage priorities,
-          specific edge cases to validate, business logic verification strategies,
-          and critical user workflows that must be tested.
-
-          Follow these instructions when reviewing test scenarios.
-          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}
-
-          ## Test Scenario to Review
-
-          The following test scenario needs to be reviewed for quality and correctness.
-          Prerequisites are provided for reference to validate dependency completeness.
-
-          \`\`\`json
-          ${JSON.stringify({
-            scenario: props.scenario,
-            prerequisites: getPrerequisites({
-              document,
-              endpoint: props.scenario.endpoint,
-            }),
-          })}
-          \`\`\`
-        `,
-      },
-    ],
-    userMessage: "Review the test scenarios please",
-  };
-}
+import { AutoBeOpenApi, AutoBeTestScenario } 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 { getPrerequisites } from "../utils/getPrerequisites";
+
+/**
+ * Transform test scenario review context into conversational history.
+ *
+ * Creates the complete conversation history for reviewing a single test
+ * scenario, including system prompts, user instructions, and the scenario to be
+ * reviewed.
+ *
+ * @param props - Configuration for history transformation
+ * @param props.state - Current AutoBe state containing interface document
+ * @param props.instruction - E2E-test-specific instructions from user
+ *   requirements
+ * @param props.scenario - Single test scenario to review and potentially
+ *   improve
+ * @param props.preliminary - Controller for RAG-based preliminary data requests
+ * @returns Complete conversation history ready for LLM agent processing
+ */
+export function transformTestScenarioReviewHistory(props: {
+  state: AutoBeState;
+  instruction: string;
+  scenario: AutoBeTestScenario;
+  preliminary: AutoBePreliminaryController<
+    "analysisSections" | "interfaceOperations" | "interfaceSchemas"
+  >;
+}): IAutoBeOrchestrateHistory {
+  const document: AutoBeOpenApi.IDocument | undefined =
+    props.state.interface?.document;
+  if (document === undefined) {
+    throw new Error(
+      "Cannot review test scenarios because there are no operations.",
+    );
+  }
+  return {
+    histories: [
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "systemMessage",
+        text: AutoBeSystemPromptConstant.TEST_SCENARIO,
+      },
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "systemMessage",
+        text: AutoBeSystemPromptConstant.TEST_SCENARIO_REVIEW,
+      },
+      ...props.preliminary.getHistories(),
+      {
+        id: v7(),
+        created_at: new Date().toISOString(),
+        type: "assistantMessage",
+        text: StringUtil.trim`
+          ## Instructions
+
+          The following e2e-test-specific instructions were extracted from
+          the user's requirements and conversations. These instructions focus
+          exclusively on test-related aspects such as test coverage priorities,
+          specific edge cases to validate, business logic verification strategies,
+          and critical user workflows that must be tested.
+
+          Follow these instructions when reviewing test scenarios.
+          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}
+
+          ## Test Scenario to Review
+
+          The following test scenario needs to be reviewed for quality and correctness.
+          Prerequisites are provided for reference to validate dependency completeness.
+
+          \`\`\`json
+          ${JSON.stringify({
+            scenario: props.scenario,
+            prerequisites: getPrerequisites({
+              document,
+              endpoint: props.scenario.endpoint,
+            }),
+          })}
+          \`\`\`
+        `,
+      },
+    ],
+    userMessage: "Review the test scenarios please",
+  };
+}

package/src/orchestrate/test/histories/transformTestValidateEvent.ts

@@ -1,11 +1,11 @@
-import { AutoBeTestValidateEvent } from "@autobe/interface";
-
-import { IAutoBeTestProcedure } from "../structures/IAutoBeTestProcedure";
-
-export const transformTestValidateEvent = <T extends IAutoBeTestProcedure>(
-  event: AutoBeTestValidateEvent,
-  item: T,
-): T => ({
-  ...item,
-  operationFunction: event.function,
-});
+import { AutoBeTestValidateEvent } from "@autobe/interface";
+
+import { IAutoBeTestProcedure } from "../structures/IAutoBeTestProcedure";
+
+export const transformTestValidateEvent = <T extends IAutoBeTestProcedure>(
+  event: AutoBeTestValidateEvent,
+  item: T,
+): T => ({
+  ...item,
+  operationFunction: event.function,
+});

package/src/orchestrate/test/index.ts

@@ -1,5 +1,5 @@
-export * from "./orchestrateTestScenario";
-export * from "./orchestrateTestAuthorize";
-export * from "./orchestrateTestPrepare";
-export * from "./orchestrateTestGenerate";
-export * from "./orchestrateTestOperation";
+export * from "./orchestrateTestScenario";
+export * from "./orchestrateTestAuthorize";
+export * from "./orchestrateTestPrepare";
+export * from "./orchestrateTestGenerate";
+export * from "./orchestrateTestOperation";