@autobe/agent 0.30.0-dev.20260315 → 0.30.0

package/lib/orchestrate/interface/utils/fulfillJsonSchemaErrorMessages.js

@@ -22,12 +22,12 @@ const fulfillTypeAsArrayError = (e) => {
     isInvalidJsonSchema(e) &&
         (() => { const _io0 = input => Array.isArray(input.type) && input.type.every(elem => "string" === typeof elem); return input => "object" === typeof input && null !== input && _io0(input); })()(e.value) === true) {
         e.description =
-            "<!--\nfilename: INTERFACE_SCHEMA_MISSING_TYPE_ARRAY.md\n-->\n**Invalid Schema: Array-type \"type\" property is not allowed.**\n\nYou defined the \"type\" property as an array (e.g., \\`[\"number\", \"string\"]\\`),\nbut the JSON schema specification requires \"type\" to be a single string value.\n\nTo represent a union of multiple types, you must use the \"oneOf\" construct.\nConvert your schema to the following format:\n\n```json\n${{JSON}}\n```\n\nYou must make this correction. The validator will continue to reject your\nschema until you replace the array-type \"type\" with a proper \"oneOf\" structure." /* AutoBeSystemPromptConstant.INTERFACE_SCHEMA_MISSING_TYPE_ARRAY */.replace("${{JSON}}", utils_1.StringUtil.trim `
-        {
-          "oneOf": [
-        ${e.value.type.map((t) => `    { "type": ${JSON.stringify(t)}, ... },`).join("\n")}
-          ],${"description" in e.value ? `\n  "description": ${JSON.stringify(e.value.description)},` : ""}
-        }
+            "<!--\nfilename: INTERFACE_SCHEMA_MISSING_TYPE_ARRAY.md\n-->\n**Invalid Schema: Array-type \"type\" property is not allowed.**\n\nYou defined the \"type\" property as an array (e.g., \\`[\"number\", \"string\"]\\`),\nbut the JSON schema specification requires \"type\" to be a single string value.\n\nTo represent a union of multiple types, you must use the \"oneOf\" construct.\nConvert your schema to the following format:\n\n```json\n${{JSON}}\n```\n\nYou must make this correction. The validator will continue to reject your\nschema until you replace the array-type \"type\" with a proper \"oneOf\" structure." /* AutoBeSystemPromptConstant.INTERFACE_SCHEMA_MISSING_TYPE_ARRAY */.replace("${{JSON}}", utils_1.StringUtil.trim `
+        {
+          "oneOf": [
+        ${e.value.type.map((t) => `    { "type": ${JSON.stringify(t)}, ... },`).join("\n")}
+          ],${"description" in e.value ? `\n  "description": ${JSON.stringify(e.value.description)},` : ""}
+        }
       `);
         return true;
     }
@@ -39,25 +39,25 @@ const fulfillEnumInsteadOfConstError = (e) => {
     isInvalidJsonSchema(e) &&
         // biome-ignore lint: intended
         (() => { const _io0 = input => Array.isArray(input["enum"]); return input => "object" === typeof input && null !== input && _io0(input); })()(e.value) === true) {
-        e.description = utils_1.StringUtil.trim `
-      **Invalid Schema: "enum" keyword is not supported in AutoBE.**
-
-      The "enum" keyword is prohibited. AutoBE requires you to use the "oneOf"
-      construct with individual "const" values instead. This design ensures
-      better type safety and documentation clarity.
-
-      Convert your schema to the following format:
-
-      \`\`\`json
-      {
-        "oneOf": [
-      ${e.value.enum.map((t) => `    { "const": ${JSON.stringify(t)} },`).join("\n")}
-        ],${"description" in e.value ? `\n  "description": ${JSON.stringify(e.value.description)},` : ""}
-      }
-      \`\`\`
-
-      You must make this correction. The validator will continue to reject your
-      schema until you replace "enum" with the proper "oneOf" + "const" structure.
+        e.description = utils_1.StringUtil.trim `
+      **Invalid Schema: "enum" keyword is not supported in AutoBE.**
+
+      The "enum" keyword is prohibited. AutoBE requires you to use the "oneOf"
+      construct with individual "const" values instead. This design ensures
+      better type safety and documentation clarity.
+
+      Convert your schema to the following format:
+
+      \`\`\`json
+      {
+        "oneOf": [
+      ${e.value.enum.map((t) => `    { "const": ${JSON.stringify(t)} },`).join("\n")}
+        ],${"description" in e.value ? `\n  "description": ${JSON.stringify(e.value.description)},` : ""}
+      }
+      \`\`\`
+
+      You must make this correction. The validator will continue to reject your
+      schema until you replace "enum" with the proper "oneOf" + "const" structure.
     `;
         return true;
     }
@@ -80,40 +80,40 @@ const fulfillObjectMetadataMisplacement = (e) => {
         return false;
     const validate = (props) => {
         e.expected = "undefined";
-        e.description = utils_1.StringUtil.trim `
-      **Structural Error: "${props.key}" is in the wrong location**
-
-      You placed "${props.key}" inside the "properties" object, but it is a
-      metadata field that belongs at the object type level, outside of "properties".
-
-      - Your placement: \`${props.actual}\`
-      - Correct placement: \`${props.expected}\`
-
-      The "${props.key}" field describes ${props.purpose} and must be placed
-      at the schema's top level alongside "type" and "properties".
-
-      **Your current structure (incorrect)**:
-      \`\`\`json
-      {
-        "type": "object",
-        "properties": {
-          ...,
-          "${props.key}": ${JSON.stringify(e.value)}
-        }
-      }
-      \`\`\`
-
-      **Required structure**:
-      \`\`\`json
-      {
-        "type": "object",
-        "${props.key}": ${JSON.stringify(e.value)},
-        "properties": { ... }
-      }
-      \`\`\`
-
-      Move "${props.key}" from ${e.path} to ${props.place}. The validator will
-      continue to reject your schema until this structural correction is made.
+        e.description = utils_1.StringUtil.trim `
+      **Structural Error: "${props.key}" is in the wrong location**
+
+      You placed "${props.key}" inside the "properties" object, but it is a
+      metadata field that belongs at the object type level, outside of "properties".
+
+      - Your placement: \`${props.actual}\`
+      - Correct placement: \`${props.expected}\`
+
+      The "${props.key}" field describes ${props.purpose} and must be placed
+      at the schema's top level alongside "type" and "properties".
+
+      **Your current structure (incorrect)**:
+      \`\`\`json
+      {
+        "type": "object",
+        "properties": {
+          ...,
+          "${props.key}": ${JSON.stringify(e.value)}
+        }
+      }
+      \`\`\`
+
+      **Required structure**:
+      \`\`\`json
+      {
+        "type": "object",
+        "${props.key}": ${JSON.stringify(e.value)},
+        "properties": { ... }
+      }
+      \`\`\`
+
+      Move "${props.key}" from ${e.path} to ${props.place}. The validator will
+      continue to reject your schema until this structural correction is made.
     `;
         return true;
     };
@@ -165,23 +165,23 @@ const fulfillJsonSchemaFormat = (e) => {
         typeof e.value === "string" &&
         supported.every((s) => e.expected.includes(JSON.stringify(s)))) {
         e.expected = "undefined";
-        e.description = utils_1.StringUtil.trim `
-      **Invalid "format" Value: ${JSON.stringify(e.value)} is not supported.**
-
-      The "format" property value ${JSON.stringify(e.value)} is not supported in the
-      JSOn schema specification (type: \`AutoBeOpenApi.IJsonSchema.IString.format\`).
-
-      Supported values are:
-      
-      ${supported.map((s) => `- ${s}`).join("\n")}
-
-      If your intended format does not exactly match one of the above values,
-      you must remove the "format" property entirely from this schema.
-      Do not attempt to use similar or alternative format strings.
-      Simply delete the "format" property — it is optional.
-
-      The validator will continue to reject your schema until the "format"
-      property is either removed or set to an exactly matching supported value.
+        e.description = utils_1.StringUtil.trim `
+      **Invalid "format" Value: ${JSON.stringify(e.value)} is not supported.**
+
+      The "format" property value ${JSON.stringify(e.value)} is not supported in the
+      JSOn schema specification (type: \`AutoBeOpenApi.IJsonSchema.IString.format\`).
+
+      Supported values are:
+      
+      ${supported.map((s) => `- ${s}`).join("\n")}
+
+      If your intended format does not exactly match one of the above values,
+      you must remove the "format" property entirely from this schema.
+      Do not attempt to use similar or alternative format strings.
+      Simply delete the "format" property — it is optional.
+
+      The validator will continue to reject your schema until the "format"
+      property is either removed or set to an exactly matching supported value.
     `;
         return true;
     }

package/lib/orchestrate/prisma/histories/transformPrismaAuthorizationHistory.js

@@ -11,21 +11,21 @@ const transformPrismaAuthorizationHistory = (props) => {
         .map((actor) => {
         const actorName = utils_2.NamingConvention.snake(actor.name);
         if (actor.kind === "guest") {
-            return utils_1.StringUtil.trim `
-          ### ${actor.name} (${actor.kind})
-          1. \`${prefix}${(0, pluralize_1.plural)(actorName)}\` - Guest actor table with minimal identification fields (no password)
-          2. \`${prefix}${actorName}_sessions\` - Temporary session tokens for guest access
+            return utils_1.StringUtil.trim `
+          ### ${actor.name} (${actor.kind})
+          1. \`${prefix}${(0, pluralize_1.plural)(actorName)}\` - Guest actor table with minimal identification fields (no password)
+          2. \`${prefix}${actorName}_sessions\` - Temporary session tokens for guest access
         `;
         }
         else {
-            return utils_1.StringUtil.trim `
-          ### ${actor.name} (${actor.kind})
-          1. \`${prefix}${(0, pluralize_1.plural)(actorName)}\` - Actor table with email/password authentication fields
-          2. \`${prefix}${actorName}_sessions\` - JWT session table with access and refresh tokens
-
-          **Optional Tables** (add if requirements support):
-          - \`${prefix}${actorName}_password_resets\` - For password recovery
-          - \`${prefix}${actorName}_email_verifications\` - For email verification
+            return utils_1.StringUtil.trim `
+          ### ${actor.name} (${actor.kind})
+          1. \`${prefix}${(0, pluralize_1.plural)(actorName)}\` - Actor table with email/password authentication fields
+          2. \`${prefix}${actorName}_sessions\` - JWT session table with access and refresh tokens
+
+          **Optional Tables** (add if requirements support):
+          - \`${prefix}${actorName}_password_resets\` - For password recovery
+          - \`${prefix}${actorName}_email_verifications\` - For email verification
         `;
         }
     })
@@ -33,8 +33,8 @@ const transformPrismaAuthorizationHistory = (props) => {
     const mandatoryOutput = props.actors
         .map((actor) => {
         const actorName = utils_2.NamingConvention.snake(actor.name);
-        return utils_1.StringUtil.trim `
-        - **${actor.name}**: \`${prefix}${(0, pluralize_1.plural)(actorName)}\` + \`${prefix}${actorName}_sessions\`
+        return utils_1.StringUtil.trim `
+        - **${actor.name}**: \`${prefix}${(0, pluralize_1.plural)(actorName)}\` + \`${prefix}${actorName}_sessions\`
       `;
     })
         .join("\n");
@@ -51,79 +51,79 @@ const transformPrismaAuthorizationHistory = (props) => {
                 type: "systemMessage",
                 id: (0, uuid_1.v7)(),
                 created_at: new Date().toISOString(),
-                text: utils_1.StringUtil.trim `
-          ## Authorization Group Configuration
-
-          Your tables will be placed in the following authorization group:
-
-          - **Filename**: \`${props.group.filename}\`
-          - **Namespace**: \`${props.group.namespace}\`
-
-          This group was determined by the Database Group Agent and validated to be
-          the single authorization group for this application.
-
-          ---
-
-          ## Prefix Configuration
-
+                text: utils_1.StringUtil.trim `
+          ## Authorization Group Configuration
+
+          Your tables will be placed in the following authorization group:
+
+          - **Filename**: \`${props.group.filename}\`
+          - **Namespace**: \`${props.group.namespace}\`
+
+          This group was determined by the Database Group Agent and validated to be
+          the single authorization group for this application.
+
+          ---
+
+          ## Prefix Configuration
+
           ${props.prefix !== null
-                    ? `- Service Prefix: \`${props.prefix}\`
+                    ? `- Service Prefix: \`${props.prefix}\`
                  - All table names MUST start with: \`${prefix}\``
-                    : `- No prefix configured
-                 - Table names do NOT require a prefix`}
+                    : `- No prefix configured
+                 - Table names do NOT require a prefix`}
         `,
             },
             {
                 type: "assistantMessage",
                 id: (0, uuid_1.v7)(),
                 created_at: new Date().toISOString(),
-                text: utils_1.StringUtil.trim `
-          ## Database Design Instructions
-
-          The following database-specific instructions were extracted from the user's
-          requirements. These focus on database design aspects such as table naming,
-          field patterns, and authentication requirements.
-
-          Follow these instructions when designing authorization tables for ALL actors.
-          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 Actors Information
-
-          You are designing authentication/authorization tables for ALL of the following actors:
-
-          \`\`\`json
-          ${JSON.stringify(props.actors)}
-          \`\`\`
-
-          ---
-
-          ## Required Tables for Each Actor
-
-          You MUST create tables for EVERY actor listed above. Here are the minimum required tables:
-
-          ${requiredTables}
+                text: utils_1.StringUtil.trim `
+          ## Database Design Instructions
+
+          The following database-specific instructions were extracted from the user's
+          requirements. These focus on database design aspects such as table naming,
+          field patterns, and authentication requirements.
+
+          Follow these instructions when designing authorization tables for ALL actors.
+          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 Actors Information
+
+          You are designing authentication/authorization tables for ALL of the following actors:
+
+          \`\`\`json
+          ${JSON.stringify(props.actors)}
+          \`\`\`
+
+          ---
+
+          ## Required Tables for Each Actor
+
+          You MUST create tables for EVERY actor listed above. Here are the minimum required tables:
+
+          ${requiredTables}
         `,
             },
         ],
-        userMessage: utils_1.StringUtil.trim `
-      ## Your Task: Design Authorization Tables for ALL Actors
-
-      Design authentication and authorization tables for every actor in the system.
-
-      **MANDATORY OUTPUT** (for each actor, at minimum):
-      ${mandatoryOutput}
-      - Plus any additional auth support tables based on requirements
-
-      When ready, call \`process({ request: { type: "complete", analysis: "...", rationale: "...", tables: [...] } })\` with complete tables for ALL actors.
+        userMessage: utils_1.StringUtil.trim `
+      ## Your Task: Design Authorization Tables for ALL Actors
+
+      Design authentication and authorization tables for every actor in the system.
+
+      **MANDATORY OUTPUT** (for each actor, at minimum):
+      ${mandatoryOutput}
+      - Plus any additional auth support tables based on requirements
+
+      When ready, call \`process({ request: { type: "complete", analysis: "...", rationale: "...", tables: [...] } })\` with complete tables for ALL actors.
     `,
     };
 };

package/lib/orchestrate/prisma/histories/transformPrismaAuthorizationReviewHistory.js

@@ -32,60 +32,60 @@ const transformPrismaAuthorizationReviewHistory = (props) => {
                 id: (0, uuid_1.v7)(),
                 created_at: new Date().toISOString(),
                 type: "assistantMessage",
-                text: utils_1.StringUtil.trim `
-          ## Authorization Component to Review
-
-          ${props.prefix !== null ? `**Table Prefix**: \`${props.prefix}\`` : ""}
-
-          ### Target Component
-
-          - **Namespace**: \`${props.component.namespace}\`
-          - **Filename**: \`${props.component.filename}\`
-
-          ### Actors to Cover
-
-          The following actors must ALL have authentication tables:
-
-          \`\`\`json
-          ${JSON.stringify(props.actors)}
-          \`\`\`
-
-          ### Required Tables (Minimum)
-
-          Each actor MUST have at least:
-          ${requiredTables}
-
-          ### Current Tables
-
-          The following tables are currently assigned to this authorization component:
-
-          \`\`\`json
-          ${JSON.stringify(props.component.tables)}
-          \`\`\`
-
-          ### User Instructions
-
-          ${props.instruction}
+                text: utils_1.StringUtil.trim `
+          ## Authorization Component to Review
+
+          ${props.prefix !== null ? `**Table Prefix**: \`${props.prefix}\`` : ""}
+
+          ### Target Component
+
+          - **Namespace**: \`${props.component.namespace}\`
+          - **Filename**: \`${props.component.filename}\`
+
+          ### Actors to Cover
+
+          The following actors must ALL have authentication tables:
+
+          \`\`\`json
+          ${JSON.stringify(props.actors)}
+          \`\`\`
+
+          ### Required Tables (Minimum)
+
+          Each actor MUST have at least:
+          ${requiredTables}
+
+          ### Current Tables
+
+          The following tables are currently assigned to this authorization component:
+
+          \`\`\`json
+          ${JSON.stringify(props.component.tables)}
+          \`\`\`
+
+          ### User Instructions
+
+          ${props.instruction}
         `,
             },
         ],
-        userMessage: utils_1.StringUtil.trim `
-      Review the "${props.component.namespace}" authorization component's table list and apply necessary revisions.
-
-      **IMPORTANT - Authorization Domain Rule**:
-      Only CREATE tables related to authentication and authorization.
-      Do NOT create business domain tables (orders, products, etc.).
-
-      **IMPORTANT - All Actors Must Be Covered**:
-      Verify that EVERY actor has: main actor table + session table + auth support tables.
-
-      Use revises to:
-      - **Create**: Add missing authentication tables (session tables, password reset, etc.)
-      - **Update**: Rename tables with naming convention issues
-      - **Erase**: Remove tables that are not related to authentication/authorization
-
-      When ready, call \`process({ request: { type: "complete", revises: [...] } })\` with your revisions.
-      If no changes are needed, return an empty revises array.
+        userMessage: utils_1.StringUtil.trim `
+      Review the "${props.component.namespace}" authorization component's table list and apply necessary revisions.
+
+      **IMPORTANT - Authorization Domain Rule**:
+      Only CREATE tables related to authentication and authorization.
+      Do NOT create business domain tables (orders, products, etc.).
+
+      **IMPORTANT - All Actors Must Be Covered**:
+      Verify that EVERY actor has: main actor table + session table + auth support tables.
+
+      Use revises to:
+      - **Create**: Add missing authentication tables (session tables, password reset, etc.)
+      - **Update**: Rename tables with naming convention issues
+      - **Erase**: Remove tables that are not related to authentication/authorization
+
+      When ready, call \`process({ request: { type: "complete", revises: [...] } })\` with your revisions.
+      If no changes are needed, return an empty revises array.
     `,
     };
 };

package/lib/orchestrate/prisma/histories/transformPrismaComponentReviewHistory.js

@@ -22,63 +22,63 @@ const transformPrismaComponentReviewHistory = (props) => ({
             id: (0, uuid_1.v7)(),
             created_at: new Date().toISOString(),
             type: "assistantMessage",
-            text: utils_1.StringUtil.trim `
-        ## Component to Review
-
-        ${props.prefix !== null ? `**Table Prefix**: \`${props.prefix}\`` : ""}
-
-        ### Target Component
-
-        \`\`\`json
-        ${JSON.stringify(props.component)}
-        \`\`\`
-
-        ### Tables in Other Components (For Reference)
-
-        These tables belong to OTHER components' domains. Focus on YOUR domain only:
-
-        \`\`\`json
-        ${JSON.stringify(props.otherTables)}
-        \`\`\`
-
-        ### User Instructions
-
-        ${props.instruction}
+            text: utils_1.StringUtil.trim `
+        ## Component to Review
+
+        ${props.prefix !== null ? `**Table Prefix**: \`${props.prefix}\`` : ""}
+
+        ### Target Component
+
+        \`\`\`json
+        ${JSON.stringify(props.component)}
+        \`\`\`
+
+        ### Tables in Other Components (For Reference)
+
+        These tables belong to OTHER components' domains. Focus on YOUR domain only:
+
+        \`\`\`json
+        ${JSON.stringify(props.otherTables)}
+        \`\`\`
+
+        ### User Instructions
+
+        ${props.instruction}
       `,
         },
     ],
-    userMessage: utils_1.StringUtil.trim `
-    Review the "${props.component.namespace}" component and apply necessary revisions.
-
-    ## Your Task
-
-    1. **Analyze**: Understand requirements for this component's domain
-    2. **Compare**: Review Target Component tables against requirements AND "Tables in Other Components"
-    3. **Revise**: Apply CREATE/UPDATE/ERASE to Target Component ONLY
-
-    ## Critical Rules
-
-    **Target Component ONLY**: Your revises affect ONLY the Target Component ("${props.component.namespace}")
-
-    **Reference Other Tables**: Use "Tables in Other Components" to:
-    - Check if a table already exists elsewhere (→ do NOT create duplicates)
-    - Identify misplaced tables in Target Component (→ ERASE them)
-
-    **Validation Will FAIL If**:
-    - You CREATE a table that exists in "Tables in Other Components"
-    - You UPDATE a table name to one that exists in "Tables in Other Components"
-
-    ## Revises Operations
-
-    - **Create**: Add missing tables that belong to "${props.component.namespace}" domain
-    - **Update**: Fix naming convention issues (snake_case, plural, prefix)
-    - **Erase**: Remove tables that belong to other components' domains
-
-    ## Submit
-
-    Call \`process({ request: { type: "complete", review: "...", revises: [...] } })\`
-
-    If no changes needed, submit empty revises array: \`revises: []\`
+    userMessage: utils_1.StringUtil.trim `
+    Review the "${props.component.namespace}" component and apply necessary revisions.
+
+    ## Your Task
+
+    1. **Analyze**: Understand requirements for this component's domain
+    2. **Compare**: Review Target Component tables against requirements AND "Tables in Other Components"
+    3. **Revise**: Apply CREATE/UPDATE/ERASE to Target Component ONLY
+
+    ## Critical Rules
+
+    **Target Component ONLY**: Your revises affect ONLY the Target Component ("${props.component.namespace}")
+
+    **Reference Other Tables**: Use "Tables in Other Components" to:
+    - Check if a table already exists elsewhere (→ do NOT create duplicates)
+    - Identify misplaced tables in Target Component (→ ERASE them)
+
+    **Validation Will FAIL If**:
+    - You CREATE a table that exists in "Tables in Other Components"
+    - You UPDATE a table name to one that exists in "Tables in Other Components"
+
+    ## Revises Operations
+
+    - **Create**: Add missing tables that belong to "${props.component.namespace}" domain
+    - **Update**: Fix naming convention issues (snake_case, plural, prefix)
+    - **Erase**: Remove tables that belong to other components' domains
+
+    ## Submit
+
+    Call \`process({ request: { type: "complete", review: "...", revises: [...] } })\`
+
+    If no changes needed, submit empty revises array: \`revises: []\`
   `,
 });
 exports.transformPrismaComponentReviewHistory = transformPrismaComponentReviewHistory;