@autobe/agent 0.30.0-dev.20260315 → 0.30.0

package/lib/orchestrate/interface/programmers/AutoBeInterfacePrerequisiteProgrammer.js

@@ -10,17 +10,17 @@ var AutoBeInterfacePrerequisiteProgrammer;
         var _a, _b;
         const accessor = (_a = props.accessor) !== null && _a !== void 0 ? _a : "$input.request";
         const dict = (_b = props.dict) !== null && _b !== void 0 ? _b : AutoBeInterfacePrerequisiteProgrammer.associate(props.document.operations);
-        const table = new tstl_1.Singleton(() => utils_1.StringUtil.trim `
-        You have to select one of the endpoints below
-
-        Path | Method
-        -----|-------
+        const table = new tstl_1.Singleton(() => utils_1.StringUtil.trim `
+        You have to select one of the endpoints below
+
+        Path | Method
+        -----|-------
         ${props.document.operations
             .filter((o) => true === AutoBeInterfacePrerequisiteProgrammer.isPrerequisite(o) &&
             false ===
                 utils_1.AutoBeOpenApiEndpointComparator.equals(o, props.operation))
             .map((op) => `${op.path} | ${op.method}`)
-            .join("\n")}
+            .join("\n")}
       `);
         const errors = [];
         if (utils_1.AutoBeOpenApiEndpointComparator.equals(props.operation, props.complete.endpoint) === false)
@@ -31,40 +31,40 @@ var AutoBeInterfacePrerequisiteProgrammer;
                     method: props.operation.method,
                 }),
                 value: props.complete.endpoint,
-                description: utils_1.StringUtil.trim `
-          ## ERROR: Endpoint Mismatch
-
-          The endpoint in your response must EXACTLY match the target operation
-          you are analyzing.
-
-          ### Target Operation (What you should analyze)
-          
-          - Path: ${props.operation.path}
-          - Method: ${props.operation.method}
-
-          ### Your Response Endpoint (What you returned)
-          
-          - Path: ${props.complete.endpoint.path}
-          - Method: ${props.complete.endpoint.method}
-
-          ### Why This Matters
-          
-          You were asked to analyze the prerequisites for a SPECIFIC operation.
-          Returning a different endpoint means you analyzed the wrong operation.
-
-          ### How to Fix
-          
-          Set the \`endpoint\` field to match the target operation exactly:
-          
-          \`\`\`json
-          {
-            "endpoint": {
-              "path": "${props.operation.path}",
-              "method": "${props.operation.method}"
-            },
-            "prerequisites": [...]
-          }
-          \`\`\`
+                description: utils_1.StringUtil.trim `
+          ## ERROR: Endpoint Mismatch
+
+          The endpoint in your response must EXACTLY match the target operation
+          you are analyzing.
+
+          ### Target Operation (What you should analyze)
+          
+          - Path: ${props.operation.path}
+          - Method: ${props.operation.method}
+
+          ### Your Response Endpoint (What you returned)
+          
+          - Path: ${props.complete.endpoint.path}
+          - Method: ${props.complete.endpoint.method}
+
+          ### Why This Matters
+          
+          You were asked to analyze the prerequisites for a SPECIFIC operation.
+          Returning a different endpoint means you analyzed the wrong operation.
+
+          ### How to Fix
+          
+          Set the \`endpoint\` field to match the target operation exactly:
+          
+          \`\`\`json
+          {
+            "endpoint": {
+              "path": "${props.operation.path}",
+              "method": "${props.operation.method}"
+            },
+            "prerequisites": [...]
+          }
+          \`\`\`
         `,
             });
         props.complete.prerequisites.forEach((raw, i) => {
@@ -74,39 +74,39 @@ var AutoBeInterfacePrerequisiteProgrammer;
                     path: `${accessor}.prerequisites[${i}].endpoint`,
                     expected: "AutoBeOpenApi.IEndpoint",
                     value: raw.endpoint,
-                    description: utils_1.StringUtil.trim `
-            ## ERROR: Prerequisite Operation Does Not Exist
-
-            The prerequisite endpoint you specified does not exist in the API
-            specification. You can ONLY use prerequisites from the Available API
-            Operations list provided in your context.
-
-            ### Your Invalid Prerequisite [${i}]
-
-            \`${raw.endpoint.method} ${raw.endpoint.path}\`
-
-            ### Why This Is Wrong
-
-            - This endpoint does not exist in the document's operations
-            - You may have invented/hallucinated this endpoint
-            - You may have made a typo in the path or method
-            - You may have referenced an operation that was removed
-
-            ### Available POST Operations (Valid Prerequisites)
-
-            ${table.get()}
-
-            ### How to Fix
-            
-            Replace this prerequisite with an ACTUAL operation from the list above.
-            Double-check:
-            
-            1. The path matches EXACTLY (including slashes, braces, spelling)
-            2. The method is lowercase "post"
-            3. The operation exists in your Available API Operations context
-
-            Only use operations that you can SEE in your conversation context.
-            NEVER invent or guess operation endpoints.
+                    description: utils_1.StringUtil.trim `
+            ## ERROR: Prerequisite Operation Does Not Exist
+
+            The prerequisite endpoint you specified does not exist in the API
+            specification. You can ONLY use prerequisites from the Available API
+            Operations list provided in your context.
+
+            ### Your Invalid Prerequisite [${i}]
+
+            \`${raw.endpoint.method} ${raw.endpoint.path}\`
+
+            ### Why This Is Wrong
+
+            - This endpoint does not exist in the document's operations
+            - You may have invented/hallucinated this endpoint
+            - You may have made a typo in the path or method
+            - You may have referenced an operation that was removed
+
+            ### Available POST Operations (Valid Prerequisites)
+
+            ${table.get()}
+
+            ### How to Fix
+            
+            Replace this prerequisite with an ACTUAL operation from the list above.
+            Double-check:
+            
+            1. The path matches EXACTLY (including slashes, braces, spelling)
+            2. The method is lowercase "post"
+            3. The operation exists in your Available API Operations context
+
+            Only use operations that you can SEE in your conversation context.
+            NEVER invent or guess operation endpoints.
           `,
                 });
             else if (utils_1.AutoBeOpenApiEndpointComparator.equals(props.operation, raw.endpoint))
@@ -114,51 +114,51 @@ var AutoBeInterfacePrerequisiteProgrammer;
                     path: `${accessor}.prerequisites[${i}].endpoint`,
                     expected: "Different Operation Endpoint from Target Operation",
                     value: raw.endpoint,
-                    description: utils_1.StringUtil.trim `
-            ## CRITICAL ERROR: Self-Reference Detected
-
-            You added the target operation as its own prerequisite. This creates
-            a circular dependency and is logically invalid.
-
-            ### Target Operation
-
-            \`${props.operation.method} ${props.operation.path}\`
-
-            ### Your Prerequisite [${i}]
-
-            \`${raw.endpoint.method} ${raw.endpoint.path}\`
-
-            These are THE SAME operation!
-
-            ### Why This Is Wrong
-            
-            An operation cannot be its own prerequisite. This would mean:
-            
-            - To execute operation A, you must first execute operation A
-            - This creates an infinite loop / circular dependency
-            - E2E tests cannot be generated with circular dependencies
-
-            ### Common Mistake
-            
-            If you have a resource with parent-child relationships (e.g., articles
-            that reference parent articles), the prerequisite should create a
-            DIFFERENT instance of the resource, not reference itself.
-
-            Example:
-
-            - ❌ Wrong: \`POST /articles\` as prerequisite of \`POST /articles\`
-            - ✅ Correct: Remove the self-reference entirely, or if parent article
-              is truly needed, the system will handle it through data generation,
-              not through explicit prerequisites.
-
-            ### How to Fix
-            
-            Remove this prerequisite from your prerequisites array. Only include
-            operations that create DIFFERENT resources that this operation depends on.
-
-            ### Available POST Operations (Choose Different Operations)
-
-            ${table.get()}
+                    description: utils_1.StringUtil.trim `
+            ## CRITICAL ERROR: Self-Reference Detected
+
+            You added the target operation as its own prerequisite. This creates
+            a circular dependency and is logically invalid.
+
+            ### Target Operation
+
+            \`${props.operation.method} ${props.operation.path}\`
+
+            ### Your Prerequisite [${i}]
+
+            \`${raw.endpoint.method} ${raw.endpoint.path}\`
+
+            These are THE SAME operation!
+
+            ### Why This Is Wrong
+            
+            An operation cannot be its own prerequisite. This would mean:
+            
+            - To execute operation A, you must first execute operation A
+            - This creates an infinite loop / circular dependency
+            - E2E tests cannot be generated with circular dependencies
+
+            ### Common Mistake
+            
+            If you have a resource with parent-child relationships (e.g., articles
+            that reference parent articles), the prerequisite should create a
+            DIFFERENT instance of the resource, not reference itself.
+
+            Example:
+
+            - ❌ Wrong: \`POST /articles\` as prerequisite of \`POST /articles\`
+            - ✅ Correct: Remove the self-reference entirely, or if parent article
+              is truly needed, the system will handle it through data generation,
+              not through explicit prerequisites.
+
+            ### How to Fix
+            
+            Remove this prerequisite from your prerequisites array. Only include
+            operations that create DIFFERENT resources that this operation depends on.
+
+            ### Available POST Operations (Choose Different Operations)
+
+            ${table.get()}
           `,
                 });
             else if (AutoBeInterfacePrerequisiteProgrammer.isPrerequisite(it.second) === false)
@@ -166,50 +166,50 @@ var AutoBeInterfacePrerequisiteProgrammer;
                     path: `${accessor}.prerequisites[${i}].endpoint`,
                     expected: "AutoBeOpenApi.IEndpoint",
                     value: raw.endpoint,
-                    description: utils_1.StringUtil.trim `
-            ## ERROR: Invalid Prerequisite Type
-
-            The operation you specified exists, but it CANNOT be used as a
-            prerequisite. Only POST operations without authentication can serve
-            as prerequisites.
-
-            ### Your Invalid Prerequisite [${i}]
-
-            \`${raw.endpoint.method} ${raw.endpoint.path}\`
-
-            - Method: ${it.second.method}
-            - Has Authentication: ${it.second.authorizationType !== null ? "YES" : "NO"}
-
-            ### Why This Is Wrong
-            
-            Prerequisites must be POST operations because they CREATE resources.
-            Other HTTP methods:
-            
-            - GET: Only reads data, doesn't create prerequisites
-            - PUT: Updates existing resources (resource must already exist)
-            - DELETE: Removes resources (opposite of creating prerequisites)
-            - PATCH: Loads pagination data (not a resource creation operation)
-
-            Operations requiring authentication cannot be prerequisites because
-            authentication is a separate concern from resource dependencies.
-
-            ### Valid Prerequisites Are
-
-            - ✅ POST operations (creates resources)
-            - ✅ No authentication required (authorizationType === null)
-
-            ### Available POST Operations (Valid Prerequisites)
-
-            ${table.get()}
-
-            ### How to Fix
-
-            Replace this prerequisite with a POST operation from the list above.
-            Make sure you understand:
-            
-            - Prerequisites CREATE resources that the target operation needs
-            - Only POST operations create resources
-            - GET/PUT/DELETE/PATCH operations are NEVER prerequisites
+                    description: utils_1.StringUtil.trim `
+            ## ERROR: Invalid Prerequisite Type
+
+            The operation you specified exists, but it CANNOT be used as a
+            prerequisite. Only POST operations without authentication can serve
+            as prerequisites.
+
+            ### Your Invalid Prerequisite [${i}]
+
+            \`${raw.endpoint.method} ${raw.endpoint.path}\`
+
+            - Method: ${it.second.method}
+            - Has Authentication: ${it.second.authorizationType !== null ? "YES" : "NO"}
+
+            ### Why This Is Wrong
+            
+            Prerequisites must be POST operations because they CREATE resources.
+            Other HTTP methods:
+            
+            - GET: Only reads data, doesn't create prerequisites
+            - PUT: Updates existing resources (resource must already exist)
+            - DELETE: Removes resources (opposite of creating prerequisites)
+            - PATCH: Loads pagination data (not a resource creation operation)
+
+            Operations requiring authentication cannot be prerequisites because
+            authentication is a separate concern from resource dependencies.
+
+            ### Valid Prerequisites Are
+
+            - ✅ POST operations (creates resources)
+            - ✅ No authentication required (authorizationType === null)
+
+            ### Available POST Operations (Valid Prerequisites)
+
+            ${table.get()}
+
+            ### How to Fix
+
+            Replace this prerequisite with a POST operation from the list above.
+            Make sure you understand:
+            
+            - Prerequisites CREATE resources that the target operation needs
+            - Only POST operations create resources
+            - GET/PUT/DELETE/PATCH operations are NEVER prerequisites
           `,
                 });
         });

package/lib/orchestrate/interface/programmers/AutoBeInterfaceSchemaProgrammer.js

@@ -69,17 +69,17 @@ var AutoBeInterfaceSchemaProgrammer;
                     .map((m) => JSON.stringify(m.name))
                     .join(" | "),
                 value: props.design.databaseSchema,
-                description: utils_1.StringUtil.trim `
-          You set "databaseSchema" to ${JSON.stringify(props.design.databaseSchema)},
-          but no database model with that name exists.
-
-          Available database models are:
-          ${props.everyModels.map((m) => `- ${m.name}`).join("\n")}
-
-          Fix: Use one of the available model names above, or set to null
-          if this type does not map to a single database table (e.g.,
-          computed/aggregated types, types composed purely by business logic,
-          or embedded JSON structures).
+                description: utils_1.StringUtil.trim `
+          You set "databaseSchema" to ${JSON.stringify(props.design.databaseSchema)},
+          but no database model with that name exists.
+
+          Available database models are:
+          ${props.everyModels.map((m) => `- ${m.name}`).join("\n")}
+
+          Fix: Use one of the available model names above, or set to null
+          if this type does not map to a single database table (e.g.,
+          computed/aggregated types, types composed purely by business logic,
+          or embedded JSON structures).
         `,
             });
     };

package/lib/orchestrate/interface/programmers/AutoBeInterfaceSchemaPropertyReviseProgrammer.js

@@ -36,10 +36,10 @@ var AutoBeInterfaceSchemaPropertyReviseProgrammer;
                     path: `${props.path}.revises[]`,
                     value: undefined,
                     expected: `${props.unionTypeName} (key: ${JSON.stringify(key)})`,
-                    description: utils_1.StringUtil.trim `
-            Property ${JSON.stringify(key)} is defined in the schema, but not revised.
-
-            You MUST provide a revise for EVERY property in the object schema.
+                    description: utils_1.StringUtil.trim `
+            Property ${JSON.stringify(key)} is defined in the schema, but not revised.
+
+            You MUST provide a revise for EVERY property in the object schema.
           `,
                 });
         if (props.model === null)
@@ -61,23 +61,23 @@ var AutoBeInterfaceSchemaPropertyReviseProgrammer;
                     path: `${props.path}.excludes[]`,
                     value: undefined,
                     expected: `${"AutoBeInterfaceSchemaPropertyExclude"} (databaseSchemaProperty: ${JSON.stringify(key)}), or ${props.unionTypeName} (databaseSchemaProperty: ${JSON.stringify(key)})`,
-                    description: utils_1.StringUtil.trim `
-            Database property ${JSON.stringify(key)} exists in model
-            "${props.model.name}" but is not addressed in either "excludes"
-            or "revises".
-
-            Every database property must be explicitly accounted for. You have
-            two options:
-
-            1. If this property belongs in the DTO: add a revision in "revises"
-               with databaseSchemaProperty: ${JSON.stringify(key)}
-
-            2. If this property should NOT appear in the DTO: add an entry to
-               "excludes" with databaseSchemaProperty: ${JSON.stringify(key)}
-               and a reason explaining why (e.g., "internal field",
-               "aggregation relation", "handled by separate endpoint")
-
-            Do NOT omit database properties. Either map them or exclude them.
+                    description: utils_1.StringUtil.trim `
+            Database property ${JSON.stringify(key)} exists in model
+            "${props.model.name}" but is not addressed in either "excludes"
+            or "revises".
+
+            Every database property must be explicitly accounted for. You have
+            two options:
+
+            1. If this property belongs in the DTO: add a revision in "revises"
+               with databaseSchemaProperty: ${JSON.stringify(key)}
+
+            2. If this property should NOT appear in the DTO: add an entry to
+               "excludes" with databaseSchemaProperty: ${JSON.stringify(key)}
+               and a reason explaining why (e.g., "internal field",
+               "aggregation relation", "handled by separate endpoint")
+
+            Do NOT omit database properties. Either map them or exclude them.
           `,
                 });
         // check whether excluded are contained in revises
@@ -91,19 +91,19 @@ var AutoBeInterfaceSchemaPropertyReviseProgrammer;
                 path: `${props.path}.revises[${i}].databaseSchemaProperty`,
                 expected: `not ${JSON.stringify(revise.databaseSchemaProperty)}, or remove ${props.path}.excludes[${index}]`,
                 value: revise.databaseSchemaProperty,
-                description: utils_1.StringUtil.trim `
-          Database property ${JSON.stringify(revise.databaseSchemaProperty)}
-          appears in both "revises[${i}]" and "excludes[${index}]".
-
-          A database property must be either excluded OR revised, never both.
-          Choose one of the following actions:
-
-          1. If this property belongs in the DTO: remove it from "excludes"
-             and keep the revision in "revises"
-
-          2. If this property should NOT appear in the DTO: remove this
-             revision from "revises" (or set its databaseSchemaProperty
-             to null) and keep the "excludes" entry
+                description: utils_1.StringUtil.trim `
+          Database property ${JSON.stringify(revise.databaseSchemaProperty)}
+          appears in both "revises[${i}]" and "excludes[${index}]".
+
+          A database property must be either excluded OR revised, never both.
+          Choose one of the following actions:
+
+          1. If this property belongs in the DTO: remove it from "excludes"
+             and keep the revision in "revises"
+
+          2. If this property should NOT appear in the DTO: remove this
+             revision from "revises" (or set its databaseSchemaProperty
+             to null) and keep the "excludes" entry
         `,
             });
         });
@@ -118,10 +118,10 @@ var AutoBeInterfaceSchemaPropertyReviseProgrammer;
                     .map((s) => JSON.stringify(s))
                     .join(" | "),
                 value: props.revise.key,
-                description: utils_1.StringUtil.trim `
-          Property ${JSON.stringify(props.revise.key)} does not exist in schema.
-
-          To ${props.revise.type} a property, it must exist in the object type.
+                description: utils_1.StringUtil.trim `
+          Property ${JSON.stringify(props.revise.key)} does not exist in schema.
+
+          To ${props.revise.type} a property, it must exist in the object type.
         `,
             });
         // check schema correctness
@@ -163,27 +163,27 @@ var AutoBeInterfaceSchemaPropertyReviseProgrammer;
                     .map((p) => JSON.stringify(p.key))
                     .join(" | "),
                 value,
-                description: utils_1.StringUtil.trim `
-          You have defined "databaseSchemaProperty" property with value
-          ${JSON.stringify(value)} that does not match any property (column or relation)
-          in the database schema "${props.model.name}".
-
-          Available properties in "${props.model.name}" are:
-          ${databaseProperties.map((dp) => `- ${dp.key}`).join("\n")}
-
-          Choose one of the following actions:
-
-          1. If you made a typo and a similar property exists above, correct it
-          2. If this property is computed/aggregated or composed purely by
-             business logic (not from DB), set the value to null
-          3. If no similar property exists above, delete this property entirely
-            from the schema - the property itself should not exist
-
-          The database schema is the source of truth. If the column you expected
-          does not exist, the property design is incorrect. Do not insist on
-          non-existent columns or keep trying different names hoping one works.
-
-          Note that, this is not a recommendation, but an instruction you must follow.
+                description: utils_1.StringUtil.trim `
+          You have defined "databaseSchemaProperty" property with value
+          ${JSON.stringify(value)} that does not match any property (column or relation)
+          in the database schema "${props.model.name}".
+
+          Available properties in "${props.model.name}" are:
+          ${databaseProperties.map((dp) => `- ${dp.key}`).join("\n")}
+
+          Choose one of the following actions:
+
+          1. If you made a typo and a similar property exists above, correct it
+          2. If this property is computed/aggregated or composed purely by
+             business logic (not from DB), set the value to null
+          3. If no similar property exists above, delete this property entirely
+            from the schema - the property itself should not exist
+
+          The database schema is the source of truth. If the column you expected
+          does not exist, the property design is incorrect. Do not insist on
+          non-existent columns or keep trying different names hoping one works.
+
+          Note that, this is not a recommendation, but an instruction you must follow.
         `,
             });
         return found;
@@ -221,10 +221,10 @@ var AutoBeInterfaceSchemaPropertyReviseProgrammer;
                     "x-autobe-database-schema-property": props.revise.schema["x-autobe-database-schema-property"],
                 }), null, 2),
                 value: props.revise.schema,
-                description: utils_1.StringUtil.trim `
-          The database column "${props.property.key}" is nullable, but your
-          schema does not allow null. Wrap it with oneOf including
-          { type: "null" } as shown in the expected value above.
+                description: utils_1.StringUtil.trim `
+          The database column "${props.property.key}" is nullable, but your
+          schema does not allow null. Wrap it with oneOf including
+          { type: "null" } as shown in the expected value above.
         `,
             });
         else if (props.revise.type === "nullish")
@@ -232,9 +232,9 @@ var AutoBeInterfaceSchemaPropertyReviseProgrammer;
                 path: `${props.path}.nullable`,
                 expected: "true",
                 value: props.revise.nullable,
-                description: utils_1.StringUtil.trim `
-          The database column "${props.property.key}" is nullable, so
-          "nullable" must be true. You set it to false.
+                description: utils_1.StringUtil.trim `
+          The database column "${props.property.key}" is nullable, so
+          "nullable" must be true. You set it to false.
         `,
             });
         else
@@ -242,13 +242,13 @@ var AutoBeInterfaceSchemaPropertyReviseProgrammer;
                 path: props.path,
                 expected: "AutoBeInterfaceSchemaPropertyNullish | AutoBeInterfaceSchemaPropertyUpdate",
                 value: props.revise,
-                description: utils_1.StringUtil.trim `
-          The database column "${props.property.key}" is nullable, but the
-          current schema does not allow null.
-
-          Use "nullish" type with nullable: true to fix nullability only,
-          or use "update" type with a schema wrapped in oneOf including
-          { type: "null" } if you also need to change the schema.
+                description: utils_1.StringUtil.trim `
+          The database column "${props.property.key}" is nullable, but the
+          current schema does not allow null.
+
+          Use "nullish" type with nullable: true to fix nullability only,
+          or use "update" type with a schema wrapped in oneOf including
+          { type: "null" } if you also need to change the schema.
         `,
             });
     };