@autobe/agent 0.30.0-dev.20260315 → 0.30.0

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

@@ -20,96 +20,96 @@ const transformPrismaComponentsHistory = (state, props) => {
                 id: (0, uuid_1.v7)(),
                 created_at: new Date().toISOString(),
                 type: "assistantMessage",
-                text: utils_1.StringUtil.trim `
-          ## Database Component Skeleton
-
-          You are designing database tables for the following component:
-
-          **Filename**: \`${props.group.filename}\`
-          **Namespace**: \`${props.group.namespace}\`
-
-          **Component Reasoning**:
-          - **Thinking**: ${props.group.thinking}
-          - **Review**: ${props.group.review}
-          - **Rationale**: ${props.group.rationale}
-
-          Your task is to extract the detailed table names for THIS SINGLE COMPONENT ONLY.
-
-          **CRITICAL**: Use the EXACT filename and namespace provided above.
-          You are filling in the \`tables\` field to complete this component skeleton.
-
-          ## Prefix
-          
-          - Prefix provided by the user: ${props.prefix}
-          
-          The user wants all database schema (table) names to start with the prefix provided below.
-          
-          - DO: Use the provided prefix for all table names
-          - DO: Place special-purpose prefixes like \`mv\` (for materialized views) before the given prefix
-          - DO NOT: Apply prefix if it is \`null\`
-          
-          ## Prefix Example
-          
-          If the prefix is \`shopping\`, then table names are like:
-          
-          - \`shopping_sales\`
-          - \`shopping_sale_options\`
-          
-          In cases where a table is created for performance optimization purposes 
-          (e.g., materialized views), the \`mv_\` prefix must come first. For example:
-          
-          - \`mv_shopping_daily_stats\`
-          
+                text: utils_1.StringUtil.trim `
+          ## Database Component Skeleton
+
+          You are designing database tables for the following component:
+
+          **Filename**: \`${props.group.filename}\`
+          **Namespace**: \`${props.group.namespace}\`
+
+          **Component Reasoning**:
+          - **Thinking**: ${props.group.thinking}
+          - **Review**: ${props.group.review}
+          - **Rationale**: ${props.group.rationale}
+
+          Your task is to extract the detailed table names for THIS SINGLE COMPONENT ONLY.
+
+          **CRITICAL**: Use the EXACT filename and namespace provided above.
+          You are filling in the \`tables\` field to complete this component skeleton.
+
+          ## Prefix
+          
+          - Prefix provided by the user: ${props.prefix}
+          
+          The user wants all database schema (table) names to start with the prefix provided below.
+          
+          - DO: Use the provided prefix for all table names
+          - DO: Place special-purpose prefixes like \`mv\` (for materialized views) before the given prefix
+          - DO NOT: Apply prefix if it is \`null\`
+          
+          ## Prefix Example
+          
+          If the prefix is \`shopping\`, then table names are like:
+          
+          - \`shopping_sales\`
+          - \`shopping_sale_options\`
+          
+          In cases where a table is created for performance optimization purposes 
+          (e.g., materialized views), the \`mv_\` prefix must come first. For example:
+          
+          - \`mv_shopping_daily_stats\`
+          
           ${state.analyze.actors.length > 0
-                    ? utils_1.StringUtil.trim `
-                  ## ABSOLUTE PROHIBITION: Actor and Authorization Tables
-
-                  The requirements contain the following actors: ${state.analyze.actors.map((a) => a.name).join(", ")}
-
-                  **YOU MUST NOT CREATE ANY ACTOR OR AUTHENTICATION TABLES.**
-
-                  The **Database Authorization Agent** is responsible for generating all actor-related tables.
-                  That agent creates the \`schema-02-actors.prisma\` component with tables like:
-
+                    ? utils_1.StringUtil.trim `
+                  ## ABSOLUTE PROHIBITION: Actor and Authorization Tables
+
+                  The requirements contain the following actors: ${state.analyze.actors.map((a) => a.name).join(", ")}
+
+                  **YOU MUST NOT CREATE ANY ACTOR OR AUTHENTICATION TABLES.**
+
+                  The **Database Authorization Agent** is responsible for generating all actor-related tables.
+                  That agent creates the \`schema-02-actors.prisma\` component with tables like:
+
                   ${state.analyze.actors
-                        .map((actor) => `- ${props.prefix ? props.prefix + "_" : ""}${actor.name.toLowerCase()}s (FORBIDDEN - created by Authorization Agent)
+                        .map((actor) => `- ${props.prefix ? props.prefix + "_" : ""}${actor.name.toLowerCase()}s (FORBIDDEN - created by Authorization Agent)
 - ${props.prefix ? props.prefix + "_" : ""}${actor.name.toLowerCase()}_sessions (FORBIDDEN - created by Authorization Agent)`)
-                        .join("\n")}
-
-                  **What To Do Instead**:
-                  - Create business domain tables that REFERENCE actors via foreign keys
-                  - ASSUME actor tables already exist
-                  - NEVER create the actor table itself
-
-                  **If you receive an "Actors" component skeleton**, return an EMPTY tables array:
-                  \`{ type: "complete", analysis: "Actors handled by Authorization Agent", rationale: "Skipped", tables: [] }\`
+                        .join("\n")}
+
+                  **What To Do Instead**:
+                  - Create business domain tables that REFERENCE actors via foreign keys
+                  - ASSUME actor tables already exist
+                  - NEVER create the actor table itself
+
+                  **If you receive an "Actors" component skeleton**, return an EMPTY tables array:
+                  \`{ type: "complete", analysis: "Actors handled by Authorization Agent", rationale: "Skipped", tables: [] }\`
                 `
-                    : ""}
-
-          ## Database Design Instructions
-
-          The following database-specific instructions were extracted from
-          the user's requirements. These focus on database schema design aspects
-          such as table structure, relationships, constraints, and indexing strategies.
-
-          Follow these instructions when designing namespace components and DB table names. 
-          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}
+                    : ""}
+
+          ## Database Design Instructions
+
+          The following database-specific instructions were extracted from
+          the user's requirements. These focus on database schema design aspects
+          such as table structure, relationships, constraints, and indexing strategies.
+
+          Follow these instructions when designing namespace components and DB table names. 
+          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}
         `,
             },
         ],
-        userMessage: utils_1.StringUtil.trim `
-      ## Your Task: Design Database Tables for This Component
-
-      Identify all entities belonging to this component's domain and generate complete table definitions covering them.
-
-      When ready, call \`process({ request: { type: "complete", ... } })\` with the table definitions.
+        userMessage: utils_1.StringUtil.trim `
+      ## Your Task: Design Database Tables for This Component
+
+      Identify all entities belonging to this component's domain and generate complete table definitions covering them.
+
+      When ready, call \`process({ request: { type: "complete", ... } })\` with the table definitions.
     `,
     };
 };

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

@@ -16,12 +16,12 @@ const transformPrismaCorrectHistory = (props) => ({
             id: (0, uuid_1.v7)(),
             created_at: new Date().toISOString(),
             type: "assistantMessage",
-            text: utils_1.StringUtil.trim `
-        Below are the list of errors what you have to fix:
-        
-        \`\`\`json
-        ${JSON.stringify(props.result.errors)}
-        \`\`\`
+            text: utils_1.StringUtil.trim `
+        Below are the list of errors what you have to fix:
+        
+        \`\`\`json
+        ${JSON.stringify(props.result.errors)}
+        \`\`\`
       `,
         },
     ],

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

@@ -20,31 +20,31 @@ const transformPrismaGroupHistory = (state, props) => {
                 id: (0, uuid_1.v7)(),
                 created_at: new Date().toISOString(),
                 type: "assistantMessage",
-                text: utils_1.StringUtil.trim `
-          ## Database Design Instructions
-
-          The following database-specific instructions were extracted from
-          the user's requirements. These focus on database schema design aspects
-          such as component organization, domain grouping, and structural patterns.
-
-          Follow these instructions when organizing database component groups.
-          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}
+                text: utils_1.StringUtil.trim `
+          ## Database Design Instructions
+
+          The following database-specific instructions were extracted from
+          the user's requirements. These focus on database schema design aspects
+          such as component organization, domain grouping, and structural patterns.
+
+          Follow these instructions when organizing database component groups.
+          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}
         `,
             },
         ],
-        userMessage: utils_1.StringUtil.trim `
-      ## Your Task: Organize Database Components into Logical Groups
-
-      Identify all business domains from the requirements and generate complete component groups covering them.
-
-      When ready, call \`process({ request: { type: "complete", ... } })\` with the group definitions.
+        userMessage: utils_1.StringUtil.trim `
+      ## Your Task: Organize Database Components into Logical Groups
+
+      Identify all business domains from the requirements and generate complete component groups covering them.
+
+      When ready, call \`process({ request: { type: "complete", ... } })\` with the group definitions.
     `,
     };
 };

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

@@ -22,50 +22,50 @@ const transformPrismaGroupReviewHistory = (props) => ({
             id: (0, uuid_1.v7)(),
             created_at: new Date().toISOString(),
             type: "assistantMessage",
-            text: utils_1.StringUtil.trim `
-        ## Component Groups to Review
-
-        The following component group skeletons were generated by the Database Group Agent.
-        Review them against the business requirements and apply necessary revisions.
-
-        ### Current Groups
-
-        \`\`\`json
-        ${JSON.stringify(props.groups)}
-        \`\`\`
-
-        ### User Instructions
-
-        ${props.instruction}
+            text: utils_1.StringUtil.trim `
+        ## Component Groups to Review
+
+        The following component group skeletons were generated by the Database Group Agent.
+        Review them against the business requirements and apply necessary revisions.
+
+        ### Current Groups
+
+        \`\`\`json
+        ${JSON.stringify(props.groups)}
+        \`\`\`
+
+        ### User Instructions
+
+        ${props.instruction}
       `,
         },
     ],
-    userMessage: utils_1.StringUtil.trim `
-    Review the component group structure and apply necessary revisions.
-
-    **🚨 CRITICAL: Authorization Group is PROTECTED**
-    - The authorization group (\`kind: "authorization"\`) is **IMMUTABLE**
-    - You can ONLY review and revise **domain groups** (\`kind: "domain"\`)
-    - ❌ Cannot create/update/erase authorization groups
-
-    **Group Structure Rules:**
-    - Exactly 1 group with \`kind: "authorization"\` - DO NOT MODIFY
-    - At least 1 group with \`kind: "domain"\` (for business domain tables)
-    - Each domain group should cover a focused business domain (3-15 estimated tables)
-    - Namespace must be PascalCase, filename must follow \`schema-{number}-{domain}.prisma\` format
-
-    **Steps:**
-    1. Understand business requirements and identify all business domains
-    2. Verify every business domain has a corresponding domain group
-    3. Check domain group boundaries and naming conventions (skip authorization group)
-    4. Call \`process({ request: { type: "complete", review: "...", revises: [...] } })\`
-
-    **Revisions (domain groups only):**
-    - **Create**: Add domain groups for missing business domains (\`kind: "domain"\` only)
-    - **Update**: Fix domain groups with naming or scope issues
-    - **Erase**: Remove redundant domain groups
-
-    If no changes are needed, return an empty revises array.
+    userMessage: utils_1.StringUtil.trim `
+    Review the component group structure and apply necessary revisions.
+
+    **🚨 CRITICAL: Authorization Group is PROTECTED**
+    - The authorization group (\`kind: "authorization"\`) is **IMMUTABLE**
+    - You can ONLY review and revise **domain groups** (\`kind: "domain"\`)
+    - ❌ Cannot create/update/erase authorization groups
+
+    **Group Structure Rules:**
+    - Exactly 1 group with \`kind: "authorization"\` - DO NOT MODIFY
+    - At least 1 group with \`kind: "domain"\` (for business domain tables)
+    - Each domain group should cover a focused business domain (3-15 estimated tables)
+    - Namespace must be PascalCase, filename must follow \`schema-{number}-{domain}.prisma\` format
+
+    **Steps:**
+    1. Understand business requirements and identify all business domains
+    2. Verify every business domain has a corresponding domain group
+    3. Check domain group boundaries and naming conventions (skip authorization group)
+    4. Call \`process({ request: { type: "complete", review: "...", revises: [...] } })\`
+
+    **Revisions (domain groups only):**
+    - **Create**: Add domain groups for missing business domains (\`kind: "domain"\` only)
+    - **Update**: Fix domain groups with naming or scope issues
+    - **Erase**: Remove redundant domain groups
+
+    If no changes are needed, return an empty revises array.
   `,
 });
 exports.transformPrismaGroupReviewHistory = transformPrismaGroupReviewHistory;

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

@@ -22,40 +22,40 @@ const transformPrismaSchemaHistory = (props) => {
                 id: (0, uuid_1.v7)(),
                 created_at: new Date().toISOString(),
                 type: "assistantMessage",
-                text: utils_1.StringUtil.trim `
-          ## Database Design Instructions
-
-          The following database-specific instructions were extracted from
-          the user's requirements. These focus on database schema design aspects
-          such as table structure, relationships, constraints, and indexing strategies.
-
-          Follow these instructions when designing the DB 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}
-
-          ## Component Context
-
-          Here is the component context for generating DB schema.
-
-          \`\`\`json
+                text: utils_1.StringUtil.trim `
+          ## Database Design Instructions
+
+          The following database-specific instructions were extracted from
+          the user's requirements. These focus on database schema design aspects
+          such as table structure, relationships, constraints, and indexing strategies.
+
+          Follow these instructions when designing the DB 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}
+
+          ## Component Context
+
+          Here is the component context for generating DB schema.
+
+          \`\`\`json
           ${JSON.stringify({
                     targetComponent: props.component,
                     otherComponents: props.otherComponents,
-                })}
-          \`\`\`
-
-          ## Table Context
-
-          You are generating the database schema for the target table:
-
-          - Component Namespace: ${props.component.namespace}
-          - Target Table Name: ${props.design.name}
-          - Target Table Summary: ${props.design.description}
+                })}
+          \`\`\`
+
+          ## Table Context
+
+          You are generating the database schema for the target table:
+
+          - Component Namespace: ${props.component.namespace}
+          - Target Table Name: ${props.design.name}
+          - Target Table Summary: ${props.design.description}
         `,
             },
             ...(children.length !== 0
@@ -64,14 +64,14 @@ const transformPrismaSchemaHistory = (props) => {
                         id: (0, uuid_1.v7)(),
                         created_at: new Date().toISOString(),
                         type: "assistantMessage",
-                        text: utils_1.StringUtil.trim `
-                ## Child Table Collision Warning
-
-                The following child tables are already assigned to other
-                agents, so do NOT recreate them and your child table names
-                must NOT collide with any of them:
-
-                ${children.map((t) => `- ${t}`).join("\n")}
+                        text: utils_1.StringUtil.trim `
+                ## Child Table Collision Warning
+
+                The following child tables are already assigned to other
+                agents, so do NOT recreate them and your child table names
+                must NOT collide with any of them:
+
+                ${children.map((t) => `- ${t}`).join("\n")}
               `,
                     },
                 ]

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

@@ -35,21 +35,21 @@ const transformPrismaSchemaReviewHistory = (props) => {
                 id: (0, uuid_1.v7)(),
                 created_at: new Date().toISOString(),
                 type: "assistantMessage",
-                text: utils_1.StringUtil.trim `
-          Now, please review the target table "${props.model.name}"
-          in the "${props.component.namespace}" namespace.
-
-          Focus your review exclusively on the target table
-          "${props.model.name}".
-
-          When reviewing, ensure the model is correctly designed. If
-          the table needs additional child tables for 1NF decomposition
-          (repeating groups or non-atomic values), declare them as
-          newDesigns entries with names starting with the
-          "${(0, pluralize_1.singular)(props.model.name)}_" prefix.
-
-          If modifications are needed, return the corrected model
-          and any newDesigns, or null if no changes are required.
+                text: utils_1.StringUtil.trim `
+          Now, please review the target table "${props.model.name}"
+          in the "${props.component.namespace}" namespace.
+
+          Focus your review exclusively on the target table
+          "${props.model.name}".
+
+          When reviewing, ensure the model is correctly designed. If
+          the table needs additional child tables for 1NF decomposition
+          (repeating groups or non-atomic values), declare them as
+          newDesigns entries with names starting with the
+          "${(0, pluralize_1.singular)(props.model.name)}_" prefix.
+
+          If modifications are needed, return the corrected model
+          and any newDesigns, or null if no changes are required.
         `,
             },
             ...(children.length !== 0
@@ -58,14 +58,14 @@ const transformPrismaSchemaReviewHistory = (props) => {
                         id: (0, uuid_1.v7)(),
                         created_at: new Date().toISOString(),
                         type: "assistantMessage",
-                        text: utils_1.StringUtil.trim `
-                ## Child Table Collision Warning
-
-                The following child tables are already assigned to other
-                agents, so do NOT recreate them and your child table names
-                must NOT collide with any of them:
-
-                ${children.map((t) => `- ${t}`).join("\n")}
+                        text: utils_1.StringUtil.trim `
+                ## Child Table Collision Warning
+
+                The following child tables are already assigned to other
+                agents, so do NOT recreate them and your child table names
+                must NOT collide with any of them:
+
+                ${children.map((t) => `- ${t}`).join("\n")}
               `,
                     },
                 ]
@@ -76,24 +76,24 @@ const transformPrismaSchemaReviewHistory = (props) => {
                         id: (0, uuid_1.v7)(),
                         created_at: new Date().toISOString(),
                         type: "assistantMessage",
-                        text: utils_1.StringUtil.trim `
-                ## Parent Table Field Reference
-
-                Your target table "${props.model.name}" is a child of "${directParent.name}".
-
-                **Parent table fields (DO NOT duplicate these in child table)**:
-
-                ${directParent.plainFields.length > 0 ? `Plain fields:\n${directParent.plainFields.map((f) => `- ${f.name}: ${f.type}${f.nullable ? "?" : ""}`).join("\n")}` : ""}
-
-                ${directParent.foreignFields.length > 0 ? `Foreign key fields:\n${directParent.foreignFields.map((f) => `- ${f.name}: ${f.type} → ${f.relation.targetModel}`).join("\n")}` : ""}
-
-                **CRITICAL - Field Duplication Check**:
-                - If any field in "${props.model.name}" duplicates or mirrors a parent field, REMOVE it
-                - Child tables should only have:
-                  1. Own primary key (id)
-                  2. Foreign key to parent (${(0, pluralize_1.singular)(directParent.name)}_id)
-                  3. Child-specific attributes that don't exist in parent
-                - Access parent data via FK join, never by duplicating fields
+                        text: utils_1.StringUtil.trim `
+                ## Parent Table Field Reference
+
+                Your target table "${props.model.name}" is a child of "${directParent.name}".
+
+                **Parent table fields (DO NOT duplicate these in child table)**:
+
+                ${directParent.plainFields.length > 0 ? `Plain fields:\n${directParent.plainFields.map((f) => `- ${f.name}: ${f.type}${f.nullable ? "?" : ""}`).join("\n")}` : ""}
+
+                ${directParent.foreignFields.length > 0 ? `Foreign key fields:\n${directParent.foreignFields.map((f) => `- ${f.name}: ${f.type} → ${f.relation.targetModel}`).join("\n")}` : ""}
+
+                **CRITICAL - Field Duplication Check**:
+                - If any field in "${props.model.name}" duplicates or mirrors a parent field, REMOVE it
+                - Child tables should only have:
+                  1. Own primary key (id)
+                  2. Foreign key to parent (${(0, pluralize_1.singular)(directParent.name)}_id)
+                  3. Child-specific attributes that don't exist in parent
+                - Access parent data via FK join, never by duplicating fields
               `,
                     },
                 ]

package/lib/orchestrate/prisma/orchestratePrismaAuthorization.js

@@ -250,7 +250,7 @@ function process(ctx, props) {
                         parameters: [
                             {
                                 name: "props",
-                                description: " Request containing either preliminary data request or complete\r\ntable design for all actors",
+                                description: " Request containing either preliminary data request or complete\ntable design for all actors",
                                 required: true,
                                 schema: {
                                     $ref: "#/components/schemas/IAutoBeDatabaseAuthorizationApplication.IProps"

package/lib/orchestrate/prisma/orchestratePrismaAuthorizationReview.js

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

package/lib/orchestrate/prisma/orchestratePrismaComponent.js

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

package/lib/orchestrate/prisma/orchestratePrismaComponentReview.js

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

package/lib/orchestrate/prisma/orchestratePrismaCorrect.js

@@ -604,7 +604,7 @@ function execute(ctx, failure) {
                         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/IAutoBeDatabaseCorrectApplication.IProps"

package/lib/orchestrate/prisma/orchestratePrismaGroup.js

@@ -257,7 +257,7 @@ function orchestratePrismaGroup(ctx, instruction) {
                         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/IAutoBeDatabaseGroupApplication.IProps"

package/lib/orchestrate/prisma/orchestratePrismaGroupReview.js

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

package/lib/orchestrate/prisma/orchestratePrismaSchema.js

@@ -571,7 +571,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/IAutoBeDatabaseSchemaApplication.IProps"

package/lib/orchestrate/prisma/orchestratePrismaSchemaReview.js

@@ -599,7 +599,7 @@ function step(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/IAutoBeDatabaseSchemaReviewApplication.IProps"