@autobe/agent 0.30.0-dev.20260315 → 0.30.0

package/lib/orchestrate/test/histories/transformTestOperationWriteHistory.js

@@ -35,164 +35,164 @@ function transformTestOperationWriteHistory(ctx, props) {
                     id: (0, uuid_1.v7)(),
                     created_at: new Date().toISOString(),
                     type: "assistantMessage",
-                    text: utils_1.StringUtil.trim `
-          Here is the list of input material composition.
-
-          Make e2e test functions based on the following information.
-
-          ## 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 data generation strategies,
-          assertion patterns, error handling approaches, and specific validation logic
-          that should be implemented in the test code.
-
-          Follow these instructions when implementing the e2e test function.
-          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}
-
-          ## Function Name
-
-          The e2e test function name must be ${JSON.stringify(props.scenario.functionName)}.
-
-          ## Scenario Plan
-
-          Here is the scenario plan what you have to implement.
-
-          \`\`\`json
-          ${JSON.stringify(props.scenario)}
-          \`\`\`
-
-          ## DTO Definitions
-
-          You can use these DTO definitions.
-
-          Never use the DTO definitions that are not listed here.
-
-          ${yield transformTestOperationWriteHistory.structures(ctx, props.artifacts)}
-
-          ## API (SDK) Functions
-
-          You can use these API functions.
-
-          Never use the functions that are not listed here.
-
-          ${transformTestOperationWriteHistory.functional(props.artifacts, functions)}
-
-          ## E2E Mockup Functions
-
-          Just reference, and never follow this code as it is.
-
-          \`\`\`json
-          ${JSON.stringify(props.artifacts.e2e)}
-          \`\`\`
-
-          ## Available Utility Functions
-
+                    text: utils_1.StringUtil.trim `
+          Here is the list of input material composition.
+
+          Make e2e test functions based on the following information.
+
+          ## 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 data generation strategies,
+          assertion patterns, error handling approaches, and specific validation logic
+          that should be implemented in the test code.
+
+          Follow these instructions when implementing the e2e test function.
+          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}
+
+          ## Function Name
+
+          The e2e test function name must be ${JSON.stringify(props.scenario.functionName)}.
+
+          ## Scenario Plan
+
+          Here is the scenario plan what you have to implement.
+
+          \`\`\`json
+          ${JSON.stringify(props.scenario)}
+          \`\`\`
+
+          ## DTO Definitions
+
+          You can use these DTO definitions.
+
+          Never use the DTO definitions that are not listed here.
+
+          ${yield transformTestOperationWriteHistory.structures(ctx, props.artifacts)}
+
+          ## API (SDK) Functions
+
+          You can use these API functions.
+
+          Never use the functions that are not listed here.
+
+          ${transformTestOperationWriteHistory.functional(props.artifacts, functions)}
+
+          ## E2E Mockup Functions
+
+          Just reference, and never follow this code as it is.
+
+          \`\`\`json
+          ${JSON.stringify(props.artifacts.e2e)}
+          \`\`\`
+
+          ## Available Utility Functions
+
           ${functions.length > 0
-                        ? utils_1.StringUtil.trim `
-          🚨 **CRITICAL: UTILITY FUNCTIONS HAVE ABSOLUTE PRIORITY OVER SDK FUNCTIONS** 🚨
-
-          When calling an API endpoint, you MUST:
-          1. **FIRST**: Check if a utility function exists for that endpoint (match by METHOD + PATH)
-          2. **SECOND**: Only if NO utility function exists, use SDK function (\`api.functional.*\`)
-
-          **ABSOLUTE RULE**: If a utility function is provided for an endpoint below, you **MUST** use that utility function.
-          Using \`api.functional.*\` directly for an endpoint that has a utility function is **FORBIDDEN**.
-
-          ### Authorization Functions
-          Use these to authenticate users. They update the connection's headers internally.
-          **You MUST create a NEW connection object** with \`{ host: connection.host }\` and pass it to the authorize function.
-
-          **MANDATORY Pattern:**
-          \`\`\`typescript
-          const adminConnection: api.IConnection = { host: connection.host };
-          await authorize_admin_login(adminConnection, { body: {...} });
-          // adminConnection.headers is now updated internally by authorize function
-          // Use adminConnection for all subsequent API calls
-          \`\`\`
-
-          | Function Name | Endpoint | Actor |
-          |---------------|----------|-------|
+                        ? utils_1.StringUtil.trim `
+          🚨 **CRITICAL: UTILITY FUNCTIONS HAVE ABSOLUTE PRIORITY OVER SDK FUNCTIONS** 🚨
+
+          When calling an API endpoint, you MUST:
+          1. **FIRST**: Check if a utility function exists for that endpoint (match by METHOD + PATH)
+          2. **SECOND**: Only if NO utility function exists, use SDK function (\`api.functional.*\`)
+
+          **ABSOLUTE RULE**: If a utility function is provided for an endpoint below, you **MUST** use that utility function.
+          Using \`api.functional.*\` directly for an endpoint that has a utility function is **FORBIDDEN**.
+
+          ### Authorization Functions
+          Use these to authenticate users. They update the connection's headers internally.
+          **You MUST create a NEW connection object** with \`{ host: connection.host }\` and pass it to the authorize function.
+
+          **MANDATORY Pattern:**
+          \`\`\`typescript
+          const adminConnection: api.IConnection = { host: connection.host };
+          await authorize_admin_login(adminConnection, { body: {...} });
+          // adminConnection.headers is now updated internally by authorize function
+          // Use adminConnection for all subsequent API calls
+          \`\`\`
+
+          | Function Name | Endpoint | Actor |
+          |---------------|----------|-------|
           ${props.authorizationFunctions
                             .map((f) => `| \`${f.name}\` | \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\` | ${f.actor} |`)
-                            .join("\n")}
-
+                            .join("\n")}
+
           ${props.authorizationFunctions
-                            .map((f) => utils_1.StringUtil.trim `
-          #### ${f.name}
-          - **Endpoint**: \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\`
-          - **Actor**: ${f.actor}
-          - **Auth Type**: ${f.authType}
-          - **Usage**: Call function, then create NEW connection with token from result
-          - ⚠️ **Do NOT use \`api.functional.*\` for \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\`** - use this function instead
-
-          \`\`\`typescript
-          ${f.content}
-          \`\`\`
+                            .map((f) => utils_1.StringUtil.trim `
+          #### ${f.name}
+          - **Endpoint**: \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\`
+          - **Actor**: ${f.actor}
+          - **Auth Type**: ${f.authType}
+          - **Usage**: Call function, then create NEW connection with token from result
+          - ⚠️ **Do NOT use \`api.functional.*\` for \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\`** - use this function instead
+
+          \`\`\`typescript
+          ${f.content}
+          \`\`\`
           `)
-                            .join("\n\n")}
-
-          ### Generation Functions
-          
-          Use these to create test resources. They handle data preparation and API calls internally.
-          **Pass actor-specific connection** (e.g., \`userConnection\`), NOT base \`connection\`.
-
-          | Function Name | Endpoint |
-          |---------------|----------|
+                            .join("\n\n")}
+
+          ### Generation Functions
+          
+          Use these to create test resources. They handle data preparation and API calls internally.
+          **Pass actor-specific connection** (e.g., \`userConnection\`), NOT base \`connection\`.
+
+          | Function Name | Endpoint |
+          |---------------|----------|
           ${props.generationFunctions
                             .map((f) => `| \`${f.name}\` | \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\` |`)
-                            .join("\n")}
-
+                            .join("\n")}
+
           ${props.generationFunctions
-                            .map((f) => utils_1.StringUtil.trim `
-          #### ${f.name}
-          - **Endpoint**: \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\`
-          - **Usage**: \`await ${f.name}(userConnection, { ... })\` - pass actor-specific connection
-          - ⚠️ **Do NOT use \`api.functional.*\` for \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\`** - use this function instead
-
-          \`\`\`typescript
-          ${f.content}
-          \`\`\`
+                            .map((f) => utils_1.StringUtil.trim `
+          #### ${f.name}
+          - **Endpoint**: \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\`
+          - **Usage**: \`await ${f.name}(userConnection, { ... })\` - pass actor-specific connection
+          - ⚠️ **Do NOT use \`api.functional.*\` for \`${f.endpoint.method.toUpperCase()} ${f.endpoint.path}\`** - use this function instead
+
+          \`\`\`typescript
+          ${f.content}
+          \`\`\`
           `)
-                            .join("\n\n")}
+                            .join("\n\n")}
           `
-                        : utils_1.StringUtil.trim `
-          No utility functions are available for this test scenario.
-          You will need to handle authentication and data creation directly using the API SDK functions.
-          `}
-
-          ## External Definitions
-
-          Here is the external declaration files (d.ts) you can reference.
-
-          \`\`\`json
-          ${JSON.stringify(yield (0, getTestExternalDeclarations_1.getTestExternalDeclarations)(ctx))}
-          \`\`\`
-
-          ## Template Code
-
-          Here is the template e2e test code what you must follow.
-
-          You're only allowed to modify the "<SCENARIO DESCRIPTION HERE>" and
-          code inside the function block marked as "// <E2E TEST CODE HERE>".
-          Change the template code by writing your scenario description to the
-          comment, and filling your implementation logic into the function.
-
-          Note that, you don't need to add any "import" statement more than
-          this template code. Everything you need is already imported, so
-          make your implementation code in the import scope.
-
-          \`\`\`typescript
-          ${AutoBeTestOperationProgrammer_1.AutoBeTestOperationProgrammer.writeTemplateCode(props.scenario)}
-          \`\`\`
+                        : utils_1.StringUtil.trim `
+          No utility functions are available for this test scenario.
+          You will need to handle authentication and data creation directly using the API SDK functions.
+          `}
+
+          ## External Definitions
+
+          Here is the external declaration files (d.ts) you can reference.
+
+          \`\`\`json
+          ${JSON.stringify(yield (0, getTestExternalDeclarations_1.getTestExternalDeclarations)(ctx))}
+          \`\`\`
+
+          ## Template Code
+
+          Here is the template e2e test code what you must follow.
+
+          You're only allowed to modify the "<SCENARIO DESCRIPTION HERE>" and
+          code inside the function block marked as "// <E2E TEST CODE HERE>".
+          Change the template code by writing your scenario description to the
+          comment, and filling your implementation logic into the function.
+
+          Note that, you don't need to add any "import" statement more than
+          this template code. Everything you need is already imported, so
+          make your implementation code in the import scope.
+
+          \`\`\`typescript
+          ${AutoBeTestOperationProgrammer_1.AutoBeTestOperationProgrammer.writeTemplateCode(props.scenario)}
+          \`\`\`
         `,
                 },
             ],
@@ -204,14 +204,14 @@ function transformTestOperationWriteHistory(ctx, props) {
     function structures(ctx, artifacts) {
         return __awaiter(this, void 0, void 0, function* () {
             const compiler = yield ctx.compiler();
-            return utils_1.StringUtil.trim `
+            return utils_1.StringUtil.trim `
       ${Object.keys(artifacts.document.components.schemas)
                 .map((k) => `- ${k}`)
-                .join("\n")}
-
-      \`\`\`json
-      ${JSON.stringify(Object.assign(Object.assign({}, artifacts.dto), (yield compiler.test.getDefaultTypes())))}
-      \`\`\`
+                .join("\n")}
+
+      \`\`\`json
+      ${JSON.stringify(Object.assign(Object.assign({}, artifacts.dto), (yield compiler.test.getDefaultTypes())))}
+      \`\`\`
     `;
         });
     }
@@ -221,16 +221,16 @@ function transformTestOperationWriteHistory(ctx, props) {
         const app = utils_2.HttpMigration.application(document);
         const excludeEndpoints = new Set(excludeFunctions.map((f) => `${f.endpoint.method.toLowerCase()}:${f.endpoint.path}`));
         const filteredRoutes = app.routes.filter((r) => !excludeEndpoints.has(`${r.method.toLowerCase()}:${r.path}`));
-        return utils_1.StringUtil.trim `
-      Method | Path | Function Accessor
-      -------|------|-------------------
+        return utils_1.StringUtil.trim `
+      Method | Path | Function Accessor
+      -------|------|-------------------
       ${filteredRoutes
             .map((r) => [r.method, r.path, `api.functional.${r.accessor.join(".")}`].join(" | "))
-            .join("\n")}
-
-      \`\`\`json
-      ${JSON.stringify(artifacts.sdk)}
-      \`\`\`
+            .join("\n")}
+
+      \`\`\`json
+      ${JSON.stringify(artifacts.sdk)}
+      \`\`\`
     `;
     }
     transformTestOperationWriteHistory.functional = functional;

package/lib/orchestrate/test/histories/transformTestPrepareWriteHistory.js

@@ -29,62 +29,62 @@ function transformTestPrepareWriteHistory(ctx, props) {
                     id: (0, uuid_1.v7)(),
                     type: "assistantMessage",
                     created_at: new Date().toISOString(),
-                    text: utils_1.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_1.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:
-          
+                    text: utils_1.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_1.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(yield (0, getTestExternalDeclarations_1.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_1.AutoBeTestPrepareProgrammer.writeTemplateCode(props)}
+                        .join("\n")}
+            
+          ## External Definitions
+
+          Here is the external declaration files (d.ts) you can reference.
+
+          \`\`\`json
+          ${JSON.stringify(yield (0, getTestExternalDeclarations_1.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_1.AutoBeTestPrepareProgrammer.writeTemplateCode(props)}
         `,
                 },
             ],

package/lib/orchestrate/test/histories/transformTestScenarioHistory.js

@@ -53,34 +53,34 @@ const transformTestScenarioHistory = (props) => {
                 id: (0, uuid_1.v7)(),
                 created_at: new Date().toISOString(),
                 type: "assistantMessage",
-                text: utils_1.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
+                text: utils_1.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: (0, getPrerequisites_1.getPrerequisites)({
@@ -88,9 +88,9 @@ const transformTestScenarioHistory = (props) => {
                         document,
                     }),
                     authorizationActors: operationAuthorizationActors,
-                })}
-          \`\`\`
-
+                })}
+          \`\`\`
+
         `,
             },
         ],

package/lib/orchestrate/test/histories/transformTestScenarioReviewHistory.js

@@ -45,39 +45,39 @@ function transformTestScenarioReviewHistory(props) {
                 id: (0, uuid_1.v7)(),
                 created_at: new Date().toISOString(),
                 type: "assistantMessage",
-                text: utils_1.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
+                text: utils_1.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: (0, getPrerequisites_1.getPrerequisites)({
                         document,
                         endpoint: props.scenario.endpoint,
                     }),
-                })}
-          \`\`\`
+                })}
+          \`\`\`
         `,
             },
         ],

package/lib/orchestrate/test/orchestrateTestScenario.js

@@ -369,7 +369,7 @@ function process(ctx, props) {
                         parameters: [
                             {
                                 name: "props",
-                                description: " Request containing either preliminary data request or complete\r\ntask",
+                                description: " Request containing either preliminary data request or complete\ntask",
                                 required: true,
                                 schema: {
                                     $ref: "#/components/schemas/IAutoBeTestScenarioApplication.IProps"

package/lib/orchestrate/test/orchestrateTestScenarioReview.js

@@ -354,7 +354,7 @@ function process(ctx, props) {
                         parameters: [
                             {
                                 name: "props",
-                                description: " Request containing either preliminary data request or complete\r\ntask",
+                                description: " Request containing either preliminary data request or complete\ntask",
                                 required: true,
                                 schema: {
                                     $ref: "#/components/schemas/IAutoBeTestScenarioReviewApplication.IProps"