@autobe/agent 0.30.0-dev.20260315 → 0.30.0

package/lib/orchestrate/interface/histories/transformInterfaceSchemaReviewHistory.js

@@ -29,75 +29,75 @@ const transformInterfaceSchemaReviewHistory = (props) => {
                 id: (0, uuid_1.v7)(),
                 type: "assistantMessage",
                 created_at: new Date().toISOString(),
-                text: utils_1.StringUtil.trim `
-        ## API Design Instructions
-
-        The following API-specific instructions were extracted from
-        the user's requirements. These focus on API interface design aspects
-        relevant to the review task.
-
-        Follow these instructions when reviewing and fixing schemas.
-        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 Schema)
-
-        Here are the API operations that directly use the schema under review.
-        These operations reference the target schema "${props.typeName}" via
-        requestBody.typeName or responseBody.typeName.
-
-        This FILTERED list helps you understand the exact usage context for
-        the schema you're reviewing:
-
-        \`\`\`json
-        ${JSON.stringify(props.reviewOperations)}
-        \`\`\`
-
+                text: utils_1.StringUtil.trim `
+        ## API Design Instructions
+
+        The following API-specific instructions were extracted from
+        the user's requirements. These focus on API interface design aspects
+        relevant to the review task.
+
+        Follow these instructions when reviewing and fixing schemas.
+        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 Schema)
+
+        Here are the API operations that directly use the schema under review.
+        These operations reference the target schema "${props.typeName}" via
+        requestBody.typeName or responseBody.typeName.
+
+        This FILTERED list helps you understand the exact usage context for
+        the schema you're reviewing:
+
+        \`\`\`json
+        ${JSON.stringify(props.reviewOperations)}
+        \`\`\`
+
         ${(0, transformInterfaceOperationParameterHistory_1.transformInterfaceOperationParameterHistory)({
                     typeName: props.typeName,
                     operations: props.reviewOperations,
-                })}
-
-        ## DTO type to review
-
-        Here is the SPECIFIC schema that needs review for type "${props.typeName}":
-
-        \`\`\`json
-        ${JSON.stringify(props.reviewSchema)}
-        \`\`\`
-
-        Also, here is the list of properties currently defined in this schema,
-        so you have to check them one by one:
-
+                })}
+
+        ## DTO type to review
+
+        Here is the SPECIFIC schema that needs review for type "${props.typeName}":
+
+        \`\`\`json
+        ${JSON.stringify(props.reviewSchema)}
+        \`\`\`
+
+        Also, here is the list of properties currently defined in this schema,
+        so you have to check them one by one:
+
         ${Object.keys(props.reviewSchema.properties)
                     .map((k) => `- ${k}`)
-                    .join("\n")}
-
-        ${transformDatabaseSchemaProperties({ everyModels, model })}
-
-        IMPORTANT: Only this schema needs review and potential modification.
-        Other schemas in the complete schema set are provided for reference
-        only.
+                    .join("\n")}
+
+        ${transformDatabaseSchemaProperties({ everyModels, model })}
+
+        IMPORTANT: Only this schema needs review and potential modification.
+        Other schemas in the complete schema set are provided for reference
+        only.
       `,
             },
         ],
-        userMessage: utils_1.StringUtil.trim `
-    Review the JSON schema for ${JSON.stringify(props.typeName)} type.
-
-    You MUST provide a revision for every single property in \`revises\`,
-    and declare DB properties not in this DTO in \`excludes\`:
+        userMessage: utils_1.StringUtil.trim `
+    Review the JSON schema for ${JSON.stringify(props.typeName)} type.
+
+    You MUST provide a revision for every single property in \`revises\`,
+    and declare DB properties not in this DTO in \`excludes\`:
     ${Object.keys(props.reviewSchema.properties)
             .map((k) => `- ${k}`)
-            .join("\n")}
-
-    ${transformDatabaseSchemaProperties({ everyModels, model })}
+            .join("\n")}
+
+    ${transformDatabaseSchemaProperties({ everyModels, model })}
   `,
     };
 };
@@ -119,21 +119,21 @@ function transformDatabaseSchemaProperties(props) {
         .filter((f) => f.relation.targetModel === props.model.name)
         .map((f) => f.relation.oppositeName))
         .filter((name) => name !== undefined);
-    return utils_1.StringUtil.trim `
-    ## Database Schema Properties for \`${props.model.name}\`
-
-    Every DB property must be explicitly handled: either mapped to a DTO property
-    in \`revises\`, or declared in \`excludes\` with a reason. Use these as
-    \`databaseSchemaProperty\` values.
-
-    **Columns** (scalar fields):
-    ${columns.map((c) => `- \`${c}\``).join("\n")}
-
-    **Belongs-to Relations** (FK → object):
-    ${belongsTo.length > 0 ? belongsTo.map((r) => `- \`${r}\``).join("\n") : "- (none)"}
-
-    **Has-many/Has-one Relations** (reverse side):
-    ${hasRelations.length > 0 ? hasRelations.map((r) => `- \`${r}\``).join("\n") : "- (none)"}
+    return utils_1.StringUtil.trim `
+    ## Database Schema Properties for \`${props.model.name}\`
+
+    Every DB property must be explicitly handled: either mapped to a DTO property
+    in \`revises\`, or declared in \`excludes\` with a reason. Use these as
+    \`databaseSchemaProperty\` values.
+
+    **Columns** (scalar fields):
+    ${columns.map((c) => `- \`${c}\``).join("\n")}
+
+    **Belongs-to Relations** (FK → object):
+    ${belongsTo.length > 0 ? belongsTo.map((r) => `- \`${r}\``).join("\n") : "- (none)"}
+
+    **Has-many/Has-one Relations** (reverse side):
+    ${hasRelations.length > 0 ? hasRelations.map((r) => `- \`${r}\``).join("\n") : "- (none)"}
   `;
 }
 //# sourceMappingURL=transformInterfaceSchemaReviewHistory.js.map

package/lib/orchestrate/interface/histories/transformInterfaceSchemaWriteHistory.js

@@ -17,55 +17,55 @@ const transformInterfaceSchemaWriteHistory = (props) => {
                 type: "assistantMessage",
                 id: (0, uuid_1.v7)(),
                 created_at: new Date().toISOString(),
-                text: utils_1.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.
-
-          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)}
-          \`\`\`
-
-          ## Other DTO Type names you can reference
-
-          While creating the JSON schema for the target type, you can reference
-          other DTO types defined in the API. Here are their type names:
-
-          - ${props.otherTypeNames.map((name) => `- ${name}`).join("\n")}
-
-          ## DTO type to create
-          
-          Here is the specific type you need to create a JSON schema component for.
-          
-          - ${JSON.stringify(props.typeName)}
+                text: utils_1.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.
+
+          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)}
+          \`\`\`
+
+          ## Other DTO Type names you can reference
+
+          While creating the JSON schema for the target type, you can reference
+          other DTO types defined in the API. Here are their type names:
+
+          - ${props.otherTypeNames.map((name) => `- ${name}`).join("\n")}
+
+          ## DTO type to create
+          
+          Here is the specific type you need to create a JSON schema component for.
+          
+          - ${JSON.stringify(props.typeName)}
         `,
             },
         ],
-        userMessage: utils_1.StringUtil.trim `
-      Design the JSON schema for ${JSON.stringify(props.typeName)} type.
+        userMessage: utils_1.StringUtil.trim `
+      Design the JSON schema for ${JSON.stringify(props.typeName)} type.
     `,
     };
 };

package/lib/orchestrate/interface/orchestrateInterfaceAuthorization.js

@@ -684,7 +684,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/IAutoBeInterfaceAuthorizationApplication.IProps"

package/lib/orchestrate/interface/orchestrateInterfaceEndpointReview.js

@@ -486,7 +486,7 @@ const orchestrateInterfaceEndpointReview = (ctx, props) => __awaiter(void 0, voi
                     parameters: [
                         {
                             name: "props",
-                            description: " Request containing either preliminary data request or endpoint\r\nreview completion",
+                            description: " Request containing either preliminary data request or endpoint\nreview completion",
                             required: true,
                             schema: {
                                 $ref: "#/components/schemas/IAutoBeInterfaceEndpointReviewApplication.IProps"

package/lib/orchestrate/interface/orchestrateInterfaceEndpointWrite.js

@@ -371,7 +371,7 @@ const orchestrateInterfaceEndpointWrite = (ctx, props) => __awaiter(void 0, void
                     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/IAutoBeInterfaceEndpointWriteApplication.IProps"

package/lib/orchestrate/interface/orchestrateInterfaceGroup.js

@@ -325,7 +325,7 @@ function orchestrateInterfaceGroup(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/IAutoBeInterfaceGroupApplication.IProps"
@@ -658,16 +658,16 @@ function createController(props) {
                             .join(" | "),
                         value: key,
                         path: `request.groups[${i}].databaseSchemas[${j}]`,
-                        description: utils_1.StringUtil.trim `
-              The database schema "${key}" does not exist in the current project.
-
-              Make sure to provide only the valid database schema names that are present in your project.
-
-              Here is the list of available database schemas in the project:
-
+                        description: utils_1.StringUtil.trim `
+              The database schema "${key}" does not exist in the current project.
+
+              Make sure to provide only the valid database schema names that are present in your project.
+
+              Here is the list of available database schemas in the project:
+
               ${Array.from(props.databaseSchemas)
                             .map((s) => `- ${s}`)
-                            .join("\n")}
+                            .join("\n")}
             `,
                     });
             });

package/lib/orchestrate/interface/orchestrateInterfaceOperation.js

@@ -713,7 +713,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/IAutoBeInterfaceOperationApplication.IProps"

package/lib/orchestrate/interface/orchestrateInterfaceOperationReview.js

@@ -433,7 +433,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/IAutoBeInterfaceOperationReviewApplication.IProps"

package/lib/orchestrate/interface/orchestrateInterfacePrerequisite.js

@@ -91,9 +91,9 @@ function process(ctx, props) {
             .split("/")
             .filter((p) => p && !p.startsWith(":") && !p.startsWith("{")))).join(", ");
         const paths = props.operation.path;
-        const queryText = `
-    Domains: ${domains}
-    Task: ${paths}
+        const queryText = `
+    Domains: ${domains}
+    Task: ${paths}
   `.trim();
         const ragSections = yield (0, RAGRetrieval_1.buildAnalysisContextSections)((0, getEmbedder_1.getEmbedder)(), allSections, queryText, "TOPK", { log: false, logPrefix: "interfacePrerequisite" });
         const preliminary = new AutoBePreliminaryController_1.AutoBePreliminaryController({
@@ -437,7 +437,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/IAutoBeInterfacePrerequisiteApplication.IProps"

package/lib/orchestrate/interface/orchestrateInterfaceSchemaCasting.js

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

package/lib/orchestrate/interface/orchestrateInterfaceSchemaComplement.js

@@ -105,10 +105,10 @@ function process(ctx, props) {
         });
         const opHint = relatedOp ? `${relatedOp.method} ${relatedOp.path}` : "";
         const task = props.instruction.replace(/\s+/g, " ").trim().slice(0, 200);
-        const queryText = `
-Type: ${props.typeName}
-Ops: ${opHint || "N/A"}
-Task: ${task}
+        const queryText = `
+Type: ${props.typeName}
+Ops: ${opHint || "N/A"}
+Task: ${task}
 `.trim();
         const ragSections = yield (0, RAGRetrieval_1.buildAnalysisContextSections)((0, getEmbedder_1.getEmbedder)(), allSections, queryText, "TOPK", { log: false, logPrefix: "interfaceComplement" });
         const preliminary = new AutoBePreliminaryController_1.AutoBePreliminaryController({
@@ -926,7 +926,7 @@ Task: ${task}
                         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/IAutoBeInterfaceSchemaComplementApplication.IProps"

package/lib/orchestrate/interface/orchestrateInterfaceSchemaRefine.js

@@ -1107,7 +1107,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/IAutoBeInterfaceSchemaRefineApplication.IProps"

package/lib/orchestrate/interface/orchestrateInterfaceSchemaReview.js

@@ -1210,7 +1210,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/IAutoBeInterfaceSchemaReviewApplication.IProps"

package/lib/orchestrate/interface/orchestrateInterfaceSchemaWrite.js

@@ -898,7 +898,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/IAutoBeInterfaceSchemaApplication.IProps"