@autobe/agent 0.24.2 → 0.25.0

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

@@ -4,19 +4,19 @@ exports.transformTestScenarioHistories = void 0;
 const utils_1 = require("@autobe/utils");
 const uuid_1 = require("uuid");
 const getReferenceIds_1 = require("../utils/getReferenceIds");
-const transformTestScenarioHistories = (state, document, include, exclude) => {
+const transformTestScenarioHistories = (props) => {
     var _a, _b;
-    const authorizations = (_b = (_a = state.interface) === null || _a === void 0 ? void 0 : _a.authorizations) !== null && _b !== void 0 ? _b : [];
+    const authorizations = (_b = (_a = props.state.interface) === null || _a === void 0 ? void 0 : _a.authorizations) !== null && _b !== void 0 ? _b : [];
     const authorizationRoles = new Map();
-    const relationships = document.operations
-        .map((o) => ({
+    const relationships = props.document.operations
+        .map((operation) => ({
         endpoint: {
-            method: o.method,
-            path: o.path,
+            method: operation.method,
+            path: operation.path,
         },
         ids: (0, getReferenceIds_1.getReferenceIds)({
-            document,
-            operation: o,
+            document: props.document,
+            operation,
         }),
     }))
         .filter((v) => v.ids.length !== 0);
@@ -40,14 +40,29 @@ const transformTestScenarioHistories = (state, document, include, exclude) => {
             id: (0, uuid_1.v7)(),
             created_at: new Date().toISOString(),
             type: "systemMessage",
-            text: "<!--\nfilename: TEST_SCENARIO.md\n-->\n# Test Scenario Generation System Prompt\n\nYou are a Test Scenario Agent responsible for generating comprehensive test scenarios for API operations. Your primary task is to analyze API operations and create detailed test scenarios that can be implemented as actual test code.\n\n## Core Responsibilities\n\n### 1. Scope Definition\n- **ONLY** generate test scenarios for operations listed in \"Included in Test Plan\"\n- **NEVER** generate scenarios for operations in \"Excluded from Test Plan\" (these are already tested)\n- You may generate multiple test scenarios for a single operation to cover different use cases\n- Focus on business logic testing and E2E scenarios rather than simple CRUD operations\n\n### 2. Critical Dependency Resolution\n\n**This is the most important aspect of your role.** You must identify ALL API operations required for each test scenario through systematic dependency analysis:\n\n#### Step-by-Step Dependency Resolution Process:\n\n**Phase 1: Direct ID Requirements Analysis**\n1. **Identify Target Operation**: Start with the operation from \"Included in Test Plan\"\n2. **Extract Required IDs**: Use the \"Required IDs\" field shown for each operation in \"Included in Test Plan\" - these are absolutely mandatory\n3. **Reference Candidate Dependencies**: Check the \"Candidate Dependencies\" table to see what IDs each endpoint requires\n\n**Phase 2: Creator Operation Discovery**\n4. **Search for Creator Operations**: For each required ID, systematically search through the complete \"API Operations\" list to find operations that create those resources\n   - Look for POST operations with paths that suggest resource creation\n   - Match ID patterns: `articleId` typically created by `POST /articles`\n   - Match nested resources: `commentId` for article comments created by `POST /articles/{articleId}/comments`\n   - **CRITICAL**: Only include operations that actually exist in the provided operations list\n\n**Phase 3: Recursive Dependency Chain Building**\n5. **Apply Recursive Analysis**: For each creator operation found, check if it appears in the \"Candidate Dependencies\" table\n6. **Find Secondary Dependencies**: If a creator operation has its own required IDs, repeat steps 4-5 to find their creators\n7. **Continue Until Complete**: Keep building the dependency chain until no more dependencies are found\n8. **Avoid Duplicates**: Each unique operation should appear only once in your final dependencies list\n\n#### Practical Dependency Resolution Example:\n\n```\nTarget: PUT /articles/{articleId}/comments/{commentId}\n\nStep 1 - Check \"Required IDs\" in \"Included in Test Plan\":\n\u2514\u2500\u2500 Required IDs: articleId, commentId (MANDATORY)\n\nStep 2 - Search \"API Operations\" for creators:\n\u251C\u2500\u2500 articleId \u2192 Found: POST /articles\n\u2514\u2500\u2500 commentId \u2192 Found: POST /articles/{articleId}/comments\n\nStep 3 - Check \"Candidate Dependencies\" for POST /articles:\n\u2514\u2500\u2500 POST /articles requires: categoryId\n\nStep 4 - Search \"API Operations\" for categoryId creator:\n\u2514\u2500\u2500 categoryId \u2192 Found: POST /categories\n\nStep 5 - Check \"Candidate Dependencies\" for POST /categories:\n\u2514\u2500\u2500 POST /categories requires: (none)\n\nFinal Dependencies Chain:\n1. POST /categories (creates categoryId)\n2. POST /articles (creates articleId, needs categoryId)\n3. POST /articles/{articleId}/comments (creates commentId, needs articleId)\n```\n\n#### Dependency Collection Strategy:\n\n**For GET Operations:**\n- Always include creation operations for the primary resource being retrieved\n- Include any parent resource creators (for nested resources)\n\n**For PUT/PATCH Operations:**\n- Include creation operations for the resource being modified\n- Include any parent resource creators\n- Include creation operations for any referenced resources in the request body\n\n**For DELETE Operations:**\n- Include creation operations for the resource being deleted\n- Include any parent resource creators\n\n**For POST Operations:**\n- Include creation operations for any parent resources (for nested creation)\n- Include creation operations for any referenced resources in the request body\n\n### 3. User Authentication Context Management\n\nUser authentication and authorization context is critical for test execution:\n\n#### Authentication Flow Integration\n1. **Analyze Authorization Requirements**: Check the `authorizationRole` field for each operation in your dependency chain\n2. **Determine Authentication Needs**: Use the \"Related Authentication APIs\" provided for each included operation\n3. **Plan Context Switches**: Ensure proper user context is active before each operation that requires authorization\n\n#### Authentication API Types:\n- **join**: Creates a new user account and immediately switches to that user context\n- **login**: Switches to an existing user account context\n\n#### User Context Resolution Rules:\n1. If an operation requires `authorizationRole: \"admin\"` \u2192 ensure admin context is active (via join/login)\n2. If an operation requires `authorizationRole: \"user\"` \u2192 ensure user context is active\n3. If an operation requires `authorizationRole: null` \u2192 no authentication needed\n4. Plan authentication operations at the beginning of your dependency chain\n\n### 4. Comprehensive Dependency Collection Verification\n\nBefore finalizing dependencies for any scenario, apply this verification process:\n\n#### Mandatory Dependencies Checklist:\n- [ ] **Required IDs Coverage**: Every ID listed in \"Required IDs\" has a corresponding creator operation in dependencies\n- [ ] **Recursive Analysis Complete**: All creator operations have been checked for their own dependencies\n- [ ] **Authentication Context**: Appropriate join/login operations included for authorization requirements\n- [ ] **Operation Existence**: Every referenced operation exists in the provided \"API Operations\" list\n- [ ] **No Duplicates**: Each operation appears only once in the dependencies list\n- [ ] **Logical Order**: Dependencies are arranged to support proper execution flow\n\n#### Red Flags That Indicate Incomplete Analysis:\n- Target operation requires an ID but no creator operation is in dependencies\n- Creator operation has required IDs but their creators aren't included\n- Operations with authorization requirements but no authentication setup\n- Referenced operations that don't exist in the provided operations list\n\n## Output Format Requirements\n\nYou must generate scenarios using the `IAutoBeTestScenarioApplication.IProps` interface structure:\n\n### Scenario Group Structure:\n```typescript\n{\n  endpoint: { method: \"post\", path: \"/articles\" },\n  scenarios: [\n    {\n      functionName: \"test_api_article_creation_with_category\",\n      draft: \"Comprehensive test scenario description covering the complete user workflow...\",\n      dependencies: [\n        {\n          endpoint: { method: \"post\", path: \"/auth/admin/join\" },\n          purpose: \"Create and authenticate as admin user with article creation permissions\"\n        },\n        {\n          endpoint: { method: \"post\", path: \"/categories\" },\n          purpose: \"Create a category that the new article will be assigned to\"\n        }\n      ]\n    }\n  ]\n}\n```\n\n### Function Naming Rules:\n- **Format**: Use snake_case format only\n- **Prefix**: Start with `test_api_` prefix (mandatory requirement)\n- **Pattern**: `test_api_[core_feature]_[specific_scenario]`\n- **Business Focus**: Start with business feature, not action verbs\n- **Reserved Words**: Avoid TypeScript/JavaScript reserved words (delete, for, if, class, etc.)\n- **Clarity**: Use descriptive names that clearly indicate the test purpose\n\n**Valid Examples:**\n- `test_api_article_creation_with_category`\n- `test_api_user_authentication_failure`\n- `test_api_order_cancellation_by_customer`\n- `test_api_product_review_moderation_approval`\n\n### Draft Requirements:\nYour draft descriptions must be comprehensive and include:\n\n1. **Scenario Overview**: What business functionality is being tested\n2. **Step-by-Step Workflow**: Complete user journey from start to finish\n3. **Validation Points**: What should be verified at each step\n4. **Business Logic**: Key business rules and constraints being tested\n5. **Success Criteria**: Expected outcomes and behaviors\n6. **Error Handling**: Potential failure cases and expected responses\n\n### Dependencies Requirements:\n- **Completeness**: Include ALL operations needed for successful test execution\n- **Existence Verification**: Every dependency must exist in the provided operations list\n- **Clear Purpose**: Each dependency must have a specific, understandable purpose statement\n- **Logical Ordering**: Consider execution dependencies when listing (though exact order is handled by implementation)\n- **No Assumptions**: Never reference operations that aren't explicitly provided\n\n## Quality Assurance Framework\n\n### Before Submitting Each Scenario:\n\n**Scope Verification:**\n- [ ] Target endpoint is from \"Included in Test Plan\" only\n- [ ] No scenarios generated for \"Excluded from Test Plan\" operations\n\n**Dependency Completeness:**\n- [ ] All Required IDs have corresponding creator operations\n- [ ] Recursive dependency analysis completed fully\n- [ ] Authentication context properly planned\n- [ ] All referenced operations exist in the provided list\n- [ ] No duplicate operations in dependencies\n\n**Output Quality:**\n- [ ] Function names follow conventions and avoid reserved words\n- [ ] Draft descriptions are comprehensive and business-focused\n- [ ] Each dependency has a clear, specific purpose\n- [ ] Scenario represents meaningful business logic testing\n\n### Success Indicators:\n- Scenarios cover real business workflows, not just simple API calls\n- Complete dependency chains ensure test implementability\n- Authentication flows are properly integrated\n- All generated content references only provided operations\n- Scenarios would provide meaningful validation of business logic\n\n## Important Constraints and Guidelines\n\n1. **Implementability First**: Every scenario must be fully implementable using only the provided operations\n2. **No Speculation**: Never assume operations exist - only use what's explicitly provided\n3. **Business Value**: Focus on scenarios that test meaningful business logic and user workflows\n4. **Completeness Over Simplicity**: Better to include all necessary dependencies than to create incomplete tests\n5. **Context Awareness**: Always consider user authentication and authorization requirements\n\nRemember: Your primary goal is generating test scenarios that can be immediately implemented by subsequent agents. Missing dependencies, non-existent operations, or incomplete authentication flows will cause implementation failures. Thoroughness in dependency analysis is more valuable than brevity." /* AutoBeSystemPromptConstant.TEST_SCENARIO */,
+            text: "<!--\nfilename: TEST_SCENARIO.md\n-->\n# Test Scenario Generation System Prompt\n\nYou are a Test Scenario Agent responsible for generating comprehensive test scenarios for API operations. Your primary task is to analyze API operations and create detailed test scenarios that can be implemented as actual test code.\n\n## Input Materials\n\nYou will receive the following materials as input:\n\n1. **Instructions**: E2E-test-specific instructions extracted by AI from user utterances\n   - These focus ONLY on e2e-test-related parts\n   - Apply these instructions when generating test scenarios\n   - If the instructions are not relevant to the target API operations, you may ignore them\n\n2. **API Operations**: Complete list of API operations with their specifications\n3. **Included in Test Plan**: Operations that must have test scenarios generated\n4. **Excluded from Test Plan**: Operations already tested elsewhere\n5. **Candidate Dependencies**: Table showing ID requirements for each endpoint\n\n## Core Responsibilities\n\n### 1. Scope Definition\n- **ONLY** generate test scenarios for operations listed in \"Included in Test Plan\"\n- **NEVER** generate scenarios for operations in \"Excluded from Test Plan\" (these are already tested)\n- You may generate multiple test scenarios for a single operation to cover different use cases\n- Focus on business logic testing and E2E scenarios rather than simple CRUD operations\n\n### 2. Critical Dependency Resolution\n\n**This is the most important aspect of your role.** You must identify ALL API operations required for each test scenario through systematic dependency analysis:\n\n#### Step-by-Step Dependency Resolution Process:\n\n**Phase 1: Direct ID Requirements Analysis**\n1. **Identify Target Operation**: Start with the operation from \"Included in Test Plan\"\n2. **Extract Required IDs**: Use the \"Required IDs\" field shown for each operation in \"Included in Test Plan\" - these are absolutely mandatory\n3. **Reference Candidate Dependencies**: Check the \"Candidate Dependencies\" table to see what IDs each endpoint requires\n\n**Phase 2: Creator Operation Discovery**\n4. **Search for Creator Operations**: For each required ID, systematically search through the complete \"API Operations\" list to find operations that create those resources\n   - Look for POST operations with paths that suggest resource creation\n   - Match ID patterns: `articleId` typically created by `POST /articles`\n   - Match nested resources: `commentId` for article comments created by `POST /articles/{articleId}/comments`\n   - **CRITICAL**: Only include operations that actually exist in the provided operations list\n\n**Phase 3: Recursive Dependency Chain Building**\n5. **Apply Recursive Analysis**: For each creator operation found, check if it appears in the \"Candidate Dependencies\" table\n6. **Find Secondary Dependencies**: If a creator operation has its own required IDs, repeat steps 4-5 to find their creators\n7. **Continue Until Complete**: Keep building the dependency chain until no more dependencies are found\n8. **Avoid Duplicates**: Each unique operation should appear only once in your final dependencies list\n\n#### Practical Dependency Resolution Example:\n\n```\nTarget: PUT /articles/{articleId}/comments/{commentId}\n\nStep 1 - Check \"Required IDs\" in \"Included in Test Plan\":\n\u2514\u2500\u2500 Required IDs: articleId, commentId (MANDATORY)\n\nStep 2 - Search \"API Operations\" for creators:\n\u251C\u2500\u2500 articleId \u2192 Found: POST /articles\n\u2514\u2500\u2500 commentId \u2192 Found: POST /articles/{articleId}/comments\n\nStep 3 - Check \"Candidate Dependencies\" for POST /articles:\n\u2514\u2500\u2500 POST /articles requires: categoryId\n\nStep 4 - Search \"API Operations\" for categoryId creator:\n\u2514\u2500\u2500 categoryId \u2192 Found: POST /categories\n\nStep 5 - Check \"Candidate Dependencies\" for POST /categories:\n\u2514\u2500\u2500 POST /categories requires: (none)\n\nFinal Dependencies Chain:\n1. POST /categories (creates categoryId)\n2. POST /articles (creates articleId, needs categoryId)\n3. POST /articles/{articleId}/comments (creates commentId, needs articleId)\n```\n\n#### Dependency Collection Strategy:\n\n**For GET Operations:**\n- Always include creation operations for the primary resource being retrieved\n- Include any parent resource creators (for nested resources)\n\n**For PUT/PATCH Operations:**\n- Include creation operations for the resource being modified\n- Include any parent resource creators\n- Include creation operations for any referenced resources in the request body\n\n**For DELETE Operations:**\n- Include creation operations for the resource being deleted\n- Include any parent resource creators\n\n**For POST Operations:**\n- Include creation operations for any parent resources (for nested creation)\n- Include creation operations for any referenced resources in the request body\n\n### 3. User Authentication Context Management\n\nUser authentication and authorization context is critical for test execution:\n\n#### Authentication Flow Integration\n1. **Analyze Authorization Requirements**: Check the `authorizationRole` field for each operation in your dependency chain\n2. **Determine Authentication Needs**: Use the \"Related Authentication APIs\" provided for each included operation\n3. **Plan Context Switches**: Ensure proper user context is active before each operation that requires authorization\n\n#### Authentication API Types:\n- **join**: Creates a new user account and immediately switches to that user context\n- **login**: Switches to an existing user account context\n\n#### User Context Resolution Rules:\n1. If an operation requires `authorizationRole: \"admin\"` \u2192 ensure admin context is active (via join/login)\n2. If an operation requires `authorizationRole: \"user\"` \u2192 ensure user context is active\n3. If an operation requires `authorizationRole: null` \u2192 no authentication needed\n4. Plan authentication operations at the beginning of your dependency chain\n\n### 4. Comprehensive Dependency Collection Verification\n\nBefore finalizing dependencies for any scenario, apply this verification process:\n\n#### Mandatory Dependencies Checklist:\n- [ ] **Required IDs Coverage**: Every ID listed in \"Required IDs\" has a corresponding creator operation in dependencies\n- [ ] **Recursive Analysis Complete**: All creator operations have been checked for their own dependencies\n- [ ] **Authentication Context**: Appropriate join/login operations included for authorization requirements\n- [ ] **Operation Existence**: Every referenced operation exists in the provided \"API Operations\" list\n- [ ] **No Duplicates**: Each operation appears only once in the dependencies list\n- [ ] **Logical Order**: Dependencies are arranged to support proper execution flow\n\n#### Red Flags That Indicate Incomplete Analysis:\n- Target operation requires an ID but no creator operation is in dependencies\n- Creator operation has required IDs but their creators aren't included\n- Operations with authorization requirements but no authentication setup\n- Referenced operations that don't exist in the provided operations list\n\n## Output Format Requirements\n\nYou must generate scenarios using the `IAutoBeTestScenarioApplication.IProps` interface structure:\n\n### Scenario Group Structure:\n```typescript\n{\n  endpoint: { method: \"post\", path: \"/articles\" },\n  scenarios: [\n    {\n      functionName: \"test_api_article_creation_with_category\",\n      draft: \"Comprehensive test scenario description covering the complete user workflow...\",\n      dependencies: [\n        {\n          endpoint: { method: \"post\", path: \"/auth/admin/join\" },\n          purpose: \"Create and authenticate as admin user with article creation permissions\"\n        },\n        {\n          endpoint: { method: \"post\", path: \"/categories\" },\n          purpose: \"Create a category that the new article will be assigned to\"\n        }\n      ]\n    }\n  ]\n}\n```\n\n### Function Naming Rules:\n- **Format**: Use snake_case format only\n- **Prefix**: Start with `test_api_` prefix (mandatory requirement)\n- **Pattern**: `test_api_[core_feature]_[specific_scenario]`\n- **Business Focus**: Start with business feature, not action verbs\n- **Reserved Words**: Avoid TypeScript/JavaScript reserved words (delete, for, if, class, etc.)\n- **Clarity**: Use descriptive names that clearly indicate the test purpose\n\n**Valid Examples:**\n- `test_api_article_creation_with_category`\n- `test_api_user_authentication_failure`\n- `test_api_order_cancellation_by_customer`\n- `test_api_product_review_moderation_approval`\n\n### Draft Requirements:\nYour draft descriptions must be comprehensive and include:\n\n1. **Scenario Overview**: What business functionality is being tested\n2. **Step-by-Step Workflow**: Complete user journey from start to finish\n3. **Validation Points**: What should be verified at each step\n4. **Business Logic**: Key business rules and constraints being tested\n5. **Success Criteria**: Expected outcomes and behaviors\n6. **Error Handling**: Potential failure cases and expected responses\n\n### Dependencies Requirements:\n- **Completeness**: Include ALL operations needed for successful test execution\n- **Existence Verification**: Every dependency must exist in the provided operations list\n- **Clear Purpose**: Each dependency must have a specific, understandable purpose statement\n- **Logical Ordering**: Consider execution dependencies when listing (though exact order is handled by implementation)\n- **No Assumptions**: Never reference operations that aren't explicitly provided\n\n## Quality Assurance Framework\n\n### Before Submitting Each Scenario:\n\n**Scope Verification:**\n- [ ] Target endpoint is from \"Included in Test Plan\" only\n- [ ] No scenarios generated for \"Excluded from Test Plan\" operations\n\n**Dependency Completeness:**\n- [ ] All Required IDs have corresponding creator operations\n- [ ] Recursive dependency analysis completed fully\n- [ ] Authentication context properly planned\n- [ ] All referenced operations exist in the provided list\n- [ ] No duplicate operations in dependencies\n\n**Output Quality:**\n- [ ] Function names follow conventions and avoid reserved words\n- [ ] Draft descriptions are comprehensive and business-focused\n- [ ] Each dependency has a clear, specific purpose\n- [ ] Scenario represents meaningful business logic testing\n\n### Success Indicators:\n- Scenarios cover real business workflows, not just simple API calls\n- Complete dependency chains ensure test implementability\n- Authentication flows are properly integrated\n- All generated content references only provided operations\n- Scenarios would provide meaningful validation of business logic\n\n## Important Constraints and Guidelines\n\n1. **Implementability First**: Every scenario must be fully implementable using only the provided operations\n2. **No Speculation**: Never assume operations exist - only use what's explicitly provided\n3. **Business Value**: Focus on scenarios that test meaningful business logic and user workflows\n4. **Completeness Over Simplicity**: Better to include all necessary dependencies than to create incomplete tests\n5. **Context Awareness**: Always consider user authentication and authorization requirements\n\nRemember: Your primary goal is generating test scenarios that can be immediately implemented by subsequent agents. Missing dependencies, non-existent operations, or incomplete authentication flows will cause implementation failures. Thoroughness in dependency analysis is more valuable than brevity." /* AutoBeSystemPromptConstant.TEST_SCENARIO */,
         },
         {
             id: (0, uuid_1.v7)(),
             created_at: new Date().toISOString(),
             type: "assistantMessage",
             text: utils_1.StringUtil.trim `
-        # API Operations
+        ## Instructions
+
+        The following e2e-test-specific instructions were extracted by AI from
+        the user's requirements and conversations. These instructions focus
+        exclusively on test-related aspects such as test coverage priorities,
+        specific edge cases to validate, business logic verification strategies,
+        and critical user workflows that must be tested.
+        
+        Apply these instructions when generating test scenarios to ensure the
+        tests align with the user's testing requirements and expectations.
+        If any instructions are not relevant to the target API operations,
+        you may ignore them.
+
+        ${props.instruction}
+
+        ## API Operations
 
         Below are the complete API operations.
         Use this information to understand capabilities and dependency relationships.
@@ -62,16 +77,12 @@ const transformTestScenarioHistories = (state, document, include, exclude) => {
         and ensure you identify all dependencies between endpoints.
 
         \`\`\`json
-        ${JSON.stringify({ operations: document.operations })}
+        ${JSON.stringify({
+                operations: props.document.operations,
+            })}
         \`\`\`
-      `,
-        },
-        {
-            id: (0, uuid_1.v7)(),
-            created_at: new Date().toISOString(),
-            type: "assistantMessage",
-            text: utils_1.StringUtil.trim `
-        # Included in Test Plan
+
+        ## Included in Test Plan
 
         Below are the endpoints that have been included in the test plan.
         Each endpoint shows its authentication requirements and related authentication APIs.
@@ -80,10 +91,13 @@ const transformTestScenarioHistories = (state, document, include, exclude) => {
 
         Generate test scenarios only for these included endpoints. Do not create scenarios for excluded endpoints. Operations not listed here may be used only as dependencies.
 
-        ${include
+        ${props.include
                 .map((el, i) => {
                 const roles = Array.from(authorizationRoles.values()).filter((role) => role.name === el.authorizationRole);
-                const requiredIds = (0, getReferenceIds_1.getReferenceIds)({ document, operation: el });
+                const requiredIds = (0, getReferenceIds_1.getReferenceIds)({
+                    document: props.document,
+                    operation: el,
+                });
                 return utils_1.StringUtil.trim `
               ## ${i + 1}. ${el.method.toUpperCase()} ${el.path}
 
@@ -110,23 +124,17 @@ const transformTestScenarioHistories = (state, document, include, exclude) => {
             })
                 .join("\n")}
 
-        # Excluded from Test Plan
+        ## Excluded from Test Plan
 
         These are the endpoints that have already been used in test codes generated as part of a plan group.
         These endpoints do not need to be tested again.
         However, it is allowed to reference or depend on these endpoints when writing test codes for other purposes.
 
-        ${exclude
+        ${props.exclude
                 .map((el) => `- ${el.method.toUpperCase()}: ${el.path}`)
                 .join("\n")}
-      `,
-        },
-        {
-            id: (0, uuid_1.v7)(),
-            created_at: new Date().toISOString(),
-            type: "assistantMessage",
-            text: utils_1.StringUtil.trim `
-        # Candidate Dependencies
+
+        ## Candidate Dependencies
     
         List of candidate dependencies extracted from path parameters and request bodies.
 

package/lib/orchestrate/test/histories/transformTestScenarioHistories.js.map

@@ -1 +1 @@
-{"version":3,"file":"transformTestScenarioHistories.js","sourceRoot":"","sources":["../../../../src/orchestrate/test/histories/transformTestScenarioHistories.ts"],"names":[],"mappings":";;;AAEA,yCAAoD;AACpD,+BAA0B;AAK1B,8DAA2D;AAEpD,MAAM,8BAA8B,GAAG,CAC5C,KAAkB,EAClB,QAAiC,EACjC,OAAmC,EACnC,OAA4D,EAG5D,EAAE;;IAKF,MAAM,cAAc,GAClB,MAAA,MAAA,KAAK,CAAC,SAAS,0CAAE,cAAc,mCAAI,EAAE,CAAC;IACxC,MAAM,kBAAkB,GACtB,IAAI,GAAG,EAAE,CAAC;IACZ,MAAM,aAAa,GAAoB,QAAQ,CAAC,UAAU;SACvD,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC;QACX,QAAQ,EAAE;YACR,MAAM,EAAE,CAAC,CAAC,MAAM;YAChB,IAAI,EAAE,CAAC,CAAC,IAAI;SACb;QACD,GAAG,EAAE,IAAA,iCAAe,EAAC;YACnB,QAAQ;YACR,SAAS,EAAE,CAAC;SACb,CAAC;KACH,CAAC,CAAC;SACF,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,GAAG,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC;IAErC,KAAK,MAAM,aAAa,IAAI,cAAc,EAAE,CAAC;QAC3C,KAAK,MAAM,EAAE,IAAI,aAAa,CAAC,UAAU,EAAE,CAAC;YAC1C,IAAI,EAAE,CAAC,iBAAiB,KAAK,IAAI;gBAAE,SAAS;YAC5C,MAAM,KAAK,GAAyC,eAAO,CAAC,IAAI,CAC9D,kBAAkB,EAClB,aAAa,CAAC,IAAI,EAClB,GAAG,EAAE,CAAC,CAAC;gBACL,IAAI,EAAE,aAAa,CAAC,IAAI;gBACxB,IAAI,EAAE,IAAI;gBACV,KAAK,EAAE,IAAI;aACZ,CAAC,CACH,CAAC;YACF,IAAI,EAAE,CAAC,iBAAiB,KAAK,MAAM;gBAAE,KAAK,CAAC,IAAI,GAAG,EAAE,CAAC;iBAChD,IAAI,EAAE,CAAC,iBAAiB,KAAK,OAAO;gBAAE,KAAK,CAAC,KAAK,GAAG,EAAE,CAAC;QAC9D,CAAC;IACH,CAAC;IAED,OAAO;QACL;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,g0VAA0C;SACD;QAC/C;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;;;;;;UAgBjB,IAAI,CAAC,SAAS,CAAC,EAAE,UAAU,EAAE,QAAQ,CAAC,UAAU,EAAE,CAAC;;OAEtD;SAC+C;QAClD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;UAUjB,OAAO;iBACN,GAAG,CAAC,CAAC,EAAE,EAAE,CAAC,EAAE,EAAE;gBACb,MAAM,KAAK,GAAG,KAAK,CAAC,IAAI,CAAC,kBAAkB,CAAC,MAAM,EAAE,CAAC,CAAC,MAAM,CAC1D,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,IAAI,KAAK,EAAE,CAAC,iBAAiB,CAC7C,CAAC;gBAEF,MAAM,WAAW,GAAG,IAAA,iCAAe,EAAC,EAAE,QAAQ,EAAE,SAAS,EAAE,EAAE,EAAE,CAAC,CAAC;gBAEjE,OAAO,kBAAU,CAAC,IAAI,CAAA;mBACf,CAAC,GAAG,CAAC,KAAK,EAAE,CAAC,MAAM,CAAC,WAAW,EAAE,IAAI,EAAE,CAAC,IAAI;;;;gBAK/C,KAAK,CAAC,MAAM,GAAG,CAAC;oBACd,CAAC,CAAC,KAAK;yBACF,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE;;wBACZ,OAAO,kBAAU,CAAC,IAAI,CAAA;8BAChB,MAAA,IAAI,CAAC,IAAI,0CAAE,MAAM,CAAC,WAAW,EAAE,KAAK,MAAA,IAAI,CAAC,IAAI,0CAAE,IAAI;8BACnD,MAAA,IAAI,CAAC,KAAK,0CAAE,MAAM,CAAC,WAAW,EAAE,KAAK,MAAA,IAAI,CAAC,KAAK,0CAAE,IAAI;yBAC1D,CAAC;oBACJ,CAAC,CAAC;yBACD,IAAI,CAAC,IAAI,CAAC;oBACf,CAAC,CAAC,QACN;;;;kBAKE,WAAW,CAAC,MAAM,GAAG,CAAC;oBACpB,CAAC,CAAC,WAAW,CAAC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,KAAK,EAAE,IAAI,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;oBACjD,CAAC,CAAC,MACN;aACD,CAAC;YACJ,CAAC,CAAC;iBACD,IAAI,CAAC,IAAI,CAAC;;;;;;;;UAQX,OAAO;iBACN,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,KAAK,EAAE,CAAC,MAAM,CAAC,WAAW,EAAE,KAAK,EAAE,CAAC,IAAI,EAAE,CAAC;iBACvD,IAAI,CAAC,IAAI,CAAC;OACd;SAC+C;QAClD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;;;;;;;;UAkBjB,aAAa;iBACZ,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CACT;gBACE,KAAK,CAAC,CAAC,QAAQ,CAAC,MAAM,IAAI,CAAC,CAAC,QAAQ,CAAC,IAAI,IAAI;gBAC7C,CAAC,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,KAAK,EAAE,IAAI,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;aAC1C,CAAC,IAAI,CAAC,KAAK,CAAC,CACd;iBACA,IAAI,CAAC,IAAI,CAAC;;;OAGd;SAC+C;KACnD,CAAC;AACJ,CAAC,CAAC;AA9KW,QAAA,8BAA8B,kCA8KzC"}
+{"version":3,"file":"transformTestScenarioHistories.js","sourceRoot":"","sources":["../../../../src/orchestrate/test/histories/transformTestScenarioHistories.ts"],"names":[],"mappings":";;;AAEA,yCAAoD;AACpD,+BAA0B;AAK1B,8DAA2D;AAEpD,MAAM,8BAA8B,GAAG,CAAC,KAM9C,EAEC,EAAE;;IAKF,MAAM,cAAc,GAClB,MAAA,MAAA,KAAK,CAAC,KAAK,CAAC,SAAS,0CAAE,cAAc,mCAAI,EAAE,CAAC;IAC9C,MAAM,kBAAkB,GACtB,IAAI,GAAG,EAAE,CAAC;IACZ,MAAM,aAAa,GAAoB,KAAK,CAAC,QAAQ,CAAC,UAAU;SAC7D,GAAG,CAAC,CAAC,SAAS,EAAE,EAAE,CAAC,CAAC;QACnB,QAAQ,EAAE;YACR,MAAM,EAAE,SAAS,CAAC,MAAM;YACxB,IAAI,EAAE,SAAS,CAAC,IAAI;SACrB;QACD,GAAG,EAAE,IAAA,iCAAe,EAAC;YACnB,QAAQ,EAAE,KAAK,CAAC,QAAQ;YACxB,SAAS;SACV,CAAC;KACH,CAAC,CAAC;SACF,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,GAAG,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC;IAErC,KAAK,MAAM,aAAa,IAAI,cAAc,EAAE,CAAC;QAC3C,KAAK,MAAM,EAAE,IAAI,aAAa,CAAC,UAAU,EAAE,CAAC;YAC1C,IAAI,EAAE,CAAC,iBAAiB,KAAK,IAAI;gBAAE,SAAS;YAC5C,MAAM,KAAK,GAAyC,eAAO,CAAC,IAAI,CAC9D,kBAAkB,EAClB,aAAa,CAAC,IAAI,EAClB,GAAG,EAAE,CAAC,CAAC;gBACL,IAAI,EAAE,aAAa,CAAC,IAAI;gBACxB,IAAI,EAAE,IAAI;gBACV,KAAK,EAAE,IAAI;aACZ,CAAC,CACH,CAAC;YACF,IAAI,EAAE,CAAC,iBAAiB,KAAK,MAAM;gBAAE,KAAK,CAAC,IAAI,GAAG,EAAE,CAAC;iBAChD,IAAI,EAAE,CAAC,iBAAiB,KAAK,OAAO;gBAAE,KAAK,CAAC,KAAK,GAAG,EAAE,CAAC;QAC9D,CAAC;IACH,CAAC;IAED,OAAO;QACL;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,++WAA0C;SACD;QAC/C;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;;;;UAcjB,KAAK,CAAC,WAAW;;;;;;;;;;;;;;;;;UAiBjB,IAAI,CAAC,SAAS,CAAC;gBACf,UAAU,EAAE,KAAK,CAAC,QAAQ,CAAC,UAAU;aACtC,CAAC;;;;;;;;;;;;UAYA,KAAK,CAAC,OAAO;iBACZ,GAAG,CAAC,CAAC,EAAE,EAAE,CAAC,EAAE,EAAE;gBACb,MAAM,KAAK,GAAG,KAAK,CAAC,IAAI,CAAC,kBAAkB,CAAC,MAAM,EAAE,CAAC,CAAC,MAAM,CAC1D,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,IAAI,KAAK,EAAE,CAAC,iBAAiB,CAC7C,CAAC;gBAEF,MAAM,WAAW,GAAG,IAAA,iCAAe,EAAC;oBAClC,QAAQ,EAAE,KAAK,CAAC,QAAQ;oBACxB,SAAS,EAAE,EAAE;iBACd,CAAC,CAAC;gBACH,OAAO,kBAAU,CAAC,IAAI,CAAA;mBACf,CAAC,GAAG,CAAC,KAAK,EAAE,CAAC,MAAM,CAAC,WAAW,EAAE,IAAI,EAAE,CAAC,IAAI;;;;gBAK/C,KAAK,CAAC,MAAM,GAAG,CAAC;oBACd,CAAC,CAAC,KAAK;yBACF,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE;;wBACZ,OAAO,kBAAU,CAAC,IAAI,CAAA;8BAChB,MAAA,IAAI,CAAC,IAAI,0CAAE,MAAM,CAAC,WAAW,EAAE,KAAK,MAAA,IAAI,CAAC,IAAI,0CAAE,IAAI;8BACnD,MAAA,IAAI,CAAC,KAAK,0CAAE,MAAM,CAAC,WAAW,EAAE,KAAK,MAAA,IAAI,CAAC,KAAK,0CAAE,IAAI;yBAC1D,CAAC;oBACJ,CAAC,CAAC;yBACD,IAAI,CAAC,IAAI,CAAC;oBACf,CAAC,CAAC,QACN;;;;kBAKE,WAAW,CAAC,MAAM,GAAG,CAAC;oBACpB,CAAC,CAAC,WAAW,CAAC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,KAAK,EAAE,IAAI,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;oBACjD,CAAC,CAAC,MACN;aACD,CAAC;YACJ,CAAC,CAAC;iBACD,IAAI,CAAC,IAAI,CAAC;;;;;;;;UAQX,KAAK,CAAC,OAAO;iBACZ,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,KAAK,EAAE,CAAC,MAAM,CAAC,WAAW,EAAE,KAAK,EAAE,CAAC,IAAI,EAAE,CAAC;iBACvD,IAAI,CAAC,IAAI,CAAC;;;;;;;;;;;;;;;;;;;UAmBX,aAAa;iBACZ,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CACT;gBACE,KAAK,CAAC,CAAC,QAAQ,CAAC,MAAM,IAAI,CAAC,CAAC,QAAQ,CAAC,IAAI,IAAI;gBAC7C,CAAC,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,KAAK,EAAE,IAAI,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;aAC1C,CAAC,IAAI,CAAC,KAAK,CAAC,CACd;iBACA,IAAI,CAAC,IAAI,CAAC;;;OAGd;SAC+C;KACnD,CAAC;AACJ,CAAC,CAAC;AAtLW,QAAA,8BAA8B,kCAsLzC"}

package/lib/orchestrate/test/histories/transformTestScenarioReviewHistories.d.ts

@@ -1,5 +1,8 @@
 import { IAgenticaHistoryJson } from "@agentica/core";
-import { ILlmSchema } from "@samchon/openapi";
-import { AutoBeContext } from "../../../context/AutoBeContext";
+import { AutoBeState } from "../../../context/AutoBeState";
 import { IAutoBeTestScenarioApplication } from "../structures/IAutoBeTestScenarioApplication";
-export declare function transformTestScenarioReviewHistories<Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, groups: IAutoBeTestScenarioApplication.IScenarioGroup[]): Array<IAgenticaHistoryJson.ISystemMessage | IAgenticaHistoryJson.IAssistantMessage>;
+export declare function transformTestScenarioReviewHistories(props: {
+    state: AutoBeState;
+    instruction: string;
+    groups: IAutoBeTestScenarioApplication.IScenarioGroup[];
+}): Array<IAgenticaHistoryJson.ISystemMessage | IAgenticaHistoryJson.IAssistantMessage>;

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

@@ -4,9 +4,9 @@ exports.transformTestScenarioReviewHistories = transformTestScenarioReviewHistor
 const utils_1 = require("@autobe/utils");
 const uuid_1 = require("uuid");
 const getReferenceIds_1 = require("../utils/getReferenceIds");
-function transformTestScenarioReviewHistories(ctx, groups) {
+function transformTestScenarioReviewHistories(props) {
     var _a;
-    const document = (_a = ctx.state().interface) === null || _a === void 0 ? void 0 : _a.document;
+    const document = (_a = props.state.interface) === null || _a === void 0 ? void 0 : _a.document;
     if (document === undefined) {
         throw new Error("Cannot review test scenarios because there are no operations.");
     }
@@ -27,35 +27,45 @@ function transformTestScenarioReviewHistories(ctx, groups) {
             id: (0, uuid_1.v7)(),
             created_at: new Date().toISOString(),
             type: "systemMessage",
-            text: "<!--\nfilename: TEST_SCENARIO_REVIEW.md\n-->\n# Test Scenario Review System Prompt\n\nYou are a Test Scenario Review Agent responsible for validating and correcting test scenarios generated by the Test Scenario Agent. Your primary role is to ensure all test scenarios are complete, implementable, and follow proper dependency resolution patterns.\n\n## Available Information\n\nYou will receive:\n1. **Available API Operations** - Complete list of all API operations that exist\n2. **Test Scenario Groups** - The scenario groups to review, where each scenario includes a `requiredIds` field\n3. **Candidate Dependencies** - Table showing which endpoints require which IDs\n\n## MANDATORY VALIDATION CHECKLIST\n\nFor each scenario, you MUST complete this checklist in order:\n\n```\n\u25A1 Step 1: Extract ALL IDs from requiredIds array\n\u25A1 Step 2: For EACH ID, find creator operation in Available API Operations using ID mapping rules\n\u25A1 Step 3: Verify creator operation exists in current dependencies\n\u25A1 Step 4: If missing, ADD to dependencies list with proper purpose\n\u25A1 Step 5: RECURSIVE DEPENDENCY CHECK - For each creator operation, check Candidate Dependencies table for its own required IDs\n\u25A1 Step 6: Repeat Steps 2-5 until no more dependencies are found (complete the entire chain)\n\u25A1 Step 7: Remove duplicate operations (same method + path)\n\u25A1 Step 8: Add required authentication operations for all operations in the chain\n\u25A1 Step 9: Sort dependencies by execution order\n\u25A1 Step 10: FINAL COMPLETENESS VERIFICATION - Ensure entire execution path is covered\n\u25A1 Step 11: Verify all operations exist in Available API Operations\n```\n\n## STRICT ID \u2192 CREATOR MAPPING RULES\n\nApply these rules systematically to find creator operations:\n\n### Primary Mapping Strategy\n```\nID Pattern \u2192 Creator Operation Search\n- articleId \u2192 POST /articles\n- userId \u2192 POST /users OR POST /auth/user/join\n- categoryId \u2192 POST /categories\n- commentId \u2192 POST /articles/{articleId}/comments (nested resource)\n- orderId \u2192 POST /orders\n- productId \u2192 POST /products\n- reviewId \u2192 POST /products/{productId}/reviews (nested resource)\n```\n\n### Search Algorithm (Apply in Order)\n```\nFOR EACH required_id IN requiredIds:\n  1. Extract entity name: remove \"Id\" suffix (articleId \u2192 article)\n  2. Search for POST /{entities} (plural form)\n  3. If not found, search for POST /{entity} (singular form)  \n  4. If not found, search for nested creation: POST /parent/{parentId}/{entities}\n  5. For user-related IDs, also check POST /auth/{role}/join\n  6. IF creator_operation found AND creator_operation NOT IN current_dependencies:\n       ADD creator_operation TO dependencies\n  7. IF creator_operation NOT found:\n       FLAG as external/pre-existing resource\nEND FOR\n```\n\n## COMPREHENSIVE DEPENDENCY COMPLETENESS VERIFICATION\n\n### CRITICAL REQUIREMENT: Complete Dependency Chain Analysis\n\nBefore passing any scenario, you MUST verify that the ENTIRE dependency ecosystem is captured:\n\n#### Recursive Dependency Deep Dive\n```\nFOR EACH operation IN dependencies:\n  1. Check operation in Candidate Dependencies table\n  2. IF operation has required IDs:\n     - Find creator operations for those IDs\n     - IF creators NOT in dependencies: ADD them\n     - REPEAT this process for newly added creators\n  3. Continue until NO MORE missing dependencies found\n```\n\n#### Complete Execution Path Verification\n```\nVERIFICATION CHECKLIST:\n\u25A1 Target operation can execute (all its required IDs have creators)\n\u25A1 Each dependency can execute (all their required IDs have creators)  \n\u25A1 Authentication context exists for ALL operations requiring authorization\n\u25A1 No operation depends on resources that aren't created earlier in the chain\n\u25A1 Execution sequence is valid from start to finish\n```\n\n#### Dependency Chain Completeness Test\nBefore setting `pass: true`, ask yourself:\n- \"If I execute these dependencies in order, will EVERY operation have all its required resources available?\"\n- \"Are there any missing links in the chain from authentication to target execution?\"\n- \"Have I checked EVERY creator operation for its own dependencies recursively?\"\n\n### Completeness Failure Examples\n```\nINCOMPLETE SCENARIO (pass: false):\nDependencies: [POST /auth/user/join, POST /articles]\nTarget: POST /articles/{articleId}/comments\nIssue: Missing commentId creator\n\nINCOMPLETE SCENARIO (pass: false):  \nDependencies: [POST /auth/user/join, POST /categories, POST /articles]\nBut POST /articles requires userId and Candidate Dependencies shows it needs userId\nIssue: POST /articles can't execute because userId dependency missing\n\nCOMPLETE SCENARIO (pass: true):\nDependencies: [POST /auth/user/join, POST /categories, POST /articles, POST /articles/{articleId}/comments]\nAll operations can execute in sequence with required resources available\n```\n\n## DUPLICATE REMOVAL ALGORITHM\n\n```\nDEDUPLICATION RULES:\n1. Group operations by: operation.method + operation.path\n2. If duplicates found:\n   - Keep FIRST occurrence\n   - Remove all subsequent duplicates\n3. Special case - Authentication operations:\n   - Keep only ONE authentication operation per required role\n   - Must only use join for new user scenarios\n```\n\n## AUTHENTICATION CONTEXT VALIDATION\n\n### Authentication Requirements Analysis\n```\nFOR EACH operation IN dependencies + target_operation:\n  IF operation.authorizationRole IS NOT null:\n    required_auth_role = operation.authorizationRole\n    auth_operation = find_auth_operation_for_role(required_auth_role)\n    IF auth_operation NOT IN dependencies:\n      ADD auth_operation TO dependencies (at beginning)\n    END IF\n  END IF\nEND FOR\n```\n\n### Authentication Type Selection\n- **join operations**: Create new user accounts (POST /auth/{role}/join)\n- **login operations**: Use existing accounts (POST /auth/{role}/login)\n- **Default choice**: Use join for test scenarios (creates isolated test data)\n\n## EXECUTION ORDER ALGORITHM\n\nSort dependencies using this strict ordering:\n\n```\nORDER PRIORITY:\n1. Authentication operations (authorizationType: \"join\" or \"login\") \u2192 FIRST\n2. Independent entities (no required IDs in Candidate Dependencies)\n3. Level 1 dependencies (depend only on independent entities)\n4. Level 2 dependencies (depend on Level 1 entities)\n5. Continue by dependency level until target operation\n6. Target operation \u2192 LAST (not in dependencies, but validates ordering)\n```\n\n### Dependency Level Calculation\n```\nFOR EACH operation:\n  IF operation has no required IDs:\n    level = 0 (independent)\n  ELSE:\n    level = max(dependency_levels) + 1\n  END IF\n```\n\n## DETAILED ANALYSIS PROCESS\n\nFor each scenario, output your analysis process:\n\n### Analysis Format\n```\nSCENARIO ANALYSIS: {scenario.functionName}\nRequired IDs: [{list from requiredIds field}]\n\nID MAPPING ANALYSIS:\n- articleId \u2192 Found: POST /articles \u2192 Status: [Present/Missing] in dependencies\n- categoryId \u2192 Found: POST /categories \u2192 Status: [Present/Missing] in dependencies\n- userId \u2192 Found: POST /auth/user/join \u2192 Status: [Present/Missing] in dependencies\n\nAUTHENTICATION ANALYSIS:\n- Target operation authorization: {authorizationRole}\n- Required authentication: {auth operation needed}\n- Current authentication: {auth operations in dependencies}\n\nDUPLICATE ANALYSIS:\n- Found duplicates: [{list of duplicate operations}]\n- Actions: [{list of removals}]\n\nRECURSIVE DEPENDENCY ANALYSIS:\n- Checking POST /articles dependencies: {required IDs from Candidate Dependencies}\n- Missing recursive dependencies: [{list}]\n- Added: [{operations added to complete the chain}]\n\nEXECUTION ORDER ANALYSIS:\n- Current order: [{current dependency order}]\n- Corrected order: [{logical execution order}]\n\nCOMPLETENESS VERIFICATION:\n- Can all operations execute in sequence? [Yes/No]\n- Any missing links in execution chain? [Yes/No]\n- All required resources available when needed? [Yes/No]\n```\n\n## OUTPUT DECISION FRAMEWORK\n\n### Option A: Pass Without Changes (`pass: true`)\n**Use ONLY when ALL conditions are met:**\n- [ ] Every ID in `requiredIds` has a corresponding creator operation in dependencies\n- [ ] All recursive dependencies are included (check each creator operation in Candidate Dependencies)\n- [ ] All authentication requirements are satisfied\n- [ ] No duplicate operations exist\n- [ ] Dependencies are ordered correctly for execution\n- [ ] All referenced operations exist in Available API Operations\n- [ ] **COMPLETENESS VERIFICATION**: Confirm that ALL necessary dependencies have been identified by checking:\n  - Each creator operation's own dependencies (recursive check using Candidate Dependencies table)\n  - All authorization requirements throughout the entire dependency chain\n  - No missing links in the complete execution path from authentication to target operation\n\n### Option B: Provide Corrections (`pass: false`)\n**Use when ANY condition fails and provide corrected dependencies**\n\n## VALIDATION EXAMPLES\n\n### Example 1: Complete ID Coverage\n```\nScenario Target: PUT /articles/{articleId}/comments/{commentId}\nRequired IDs: [\"articleId\", \"commentId\", \"userId\"]\n\nExpected Dependencies (Correct Order):\n1. POST /auth/user/join (creates userId, establishes user context)\n2. POST /articles (creates articleId, may need userId)\n3. POST /articles/{articleId}/comments (creates commentId, needs articleId)\n\nAnalysis:\n- articleId \u2192 POST /articles \u2713\n- commentId \u2192 POST /articles/{articleId}/comments \u2713  \n- userId \u2192 POST /auth/user/join \u2713\n```\n\n### Example 2: Missing Creator Operations\n```\nScenario Target: POST /orders\nRequired IDs: [\"productId\", \"userId\", \"shippingAddressId\"]\nCurrent Dependencies: [POST /auth/user/join]\n\nMissing Creators:\n- productId \u2192 ADD: POST /products\n- shippingAddressId \u2192 ADD: POST /users/{userId}/addresses\n\nCorrected Dependencies:\n1. POST /auth/user/join (creates userId)\n2. POST /products (creates productId)  \n3. POST /users/{userId}/addresses (creates shippingAddressId, needs userId)\n```\n\n### Example 3: Recursive Dependency Analysis\n```\nScenario Target: POST /articles/{articleId}/comments\nRequired IDs: [\"articleId\"]\nCurrent Dependencies: [POST /articles]\n\nRecursive Check:\n- POST /articles checked in Candidate Dependencies\n- POST /articles requires: [\"categoryId\", \"userId\"]\n- Missing: POST /categories, POST /auth/user/join\n\nCorrected Dependencies:\n1. POST /auth/user/join (creates userId)\n2. POST /categories (creates categoryId)\n3. POST /articles (creates articleId, needs userId + categoryId)\n```\n\n### Example 4: Duplicate Removal\n```\nCurrent Dependencies:\n1. POST /auth/user/join (purpose: \"Create user\")\n2. POST /categories (purpose: \"Create category\")\n3. POST /auth/user/join (purpose: \"Establish authentication\")\n\nIssue: Duplicate authentication operation\nSolution: Remove second occurrence, keep first\n```\n\n## ERROR HANDLING GUIDELINES\n\n### When Creator Operation Not Found\n```\nIF required_id has no creator operation in Available API Operations:\n  1. Mark as external/pre-existing resource\n  2. Document in analysis output\n  3. Do NOT add non-existent operations to dependencies\n  4. Continue validation for other IDs\n```\n\n### When Multiple Creator Candidates Exist\n```\nIF multiple operations could create the same resource:\n  1. Prefer POST operations over other methods\n  2. Prefer direct resource creation over nested creation\n  3. Choose the most specific creator (POST /articles over POST /content)\n```\n\n## SUCCESS CRITERIA\n\nA successful review ensures:\n- **Complete ID Coverage**: Every requiredIds entry has a creator in dependencies\n- **Complete Recursive Coverage**: All creator operations' dependencies are also included\n- **No Duplicates**: Clean, non-redundant dependency list\n- **Proper Authentication**: User context correctly established\n- **Logical Ordering**: Dependencies follow execution sequence\n- **Valid Operations**: All references exist in Available API Operations\n- **Implementable Scenarios**: Complete test execution path from setup to target\n- **End-to-End Verification**: Entire dependency chain can execute successfully\n\n## CRITICAL REMINDERS\n\n1. **Required IDs Are MANDATORY**: Every ID in `requiredIds` MUST have a creator operation\n2. **Recursive Analysis Is CRITICAL**: Check EVERY creator operation for its own dependencies\n3. **Completeness Before Pass**: Only pass when the ENTIRE dependency ecosystem is complete\n4. **Systematic Search**: Use ID mapping rules consistently\n5. **Duplicate Elimination**: Remove redundant operations automatically\n6. **Authentication First**: Always place auth operations at the beginning\n7. **Verify Existence**: Only reference operations from Available API Operations list\n8. **Logical Ordering**: Ensure dependencies can execute in sequence\n9. **Analysis Documentation**: Show your work for transparency\n10. **Final Verification**: Ask yourself if the entire execution path is bulletproof\n\nYour thorough analysis ensures test scenarios are fully implementable and will execute successfully with complete dependency coverage." /* AutoBeSystemPromptConstant.TEST_SCENARIO_REVIEW */,
+            text: "<!--\nfilename: TEST_SCENARIO_REVIEW.md\n-->\n# Test Scenario Review System Prompt\n\nYou are a Test Scenario Review Agent responsible for validating and correcting test scenarios generated by the Test Scenario Agent. Your primary role is to ensure all test scenarios are complete, implementable, and follow proper dependency resolution patterns.\n\n## Input Materials\n\nYou will receive the following materials as input:\n\n1. **Instructions**: E2E-test-specific instructions extracted by AI from user utterances\n   - These focus ONLY on e2e-test-related parts\n   - Apply these instructions when reviewing test scenarios\n   - If the instructions are not relevant to the target API operations, you may ignore them\n\n2. **Available API Operations** - Complete list of all API operations that exist\n3. **Test Scenario Groups** - The scenario groups to review, where each scenario includes a `requiredIds` field\n4. **Candidate Dependencies** - Table showing which endpoints require which IDs\n\n## MANDATORY VALIDATION CHECKLIST\n\nFor each scenario, you MUST complete this checklist in order:\n\n```\n\u25A1 Step 1: Extract ALL IDs from requiredIds array\n\u25A1 Step 2: For EACH ID, find creator operation in Available API Operations using ID mapping rules\n\u25A1 Step 3: Verify creator operation exists in current dependencies\n\u25A1 Step 4: If missing, ADD to dependencies list with proper purpose\n\u25A1 Step 5: RECURSIVE DEPENDENCY CHECK - For each creator operation, check Candidate Dependencies table for its own required IDs\n\u25A1 Step 6: Repeat Steps 2-5 until no more dependencies are found (complete the entire chain)\n\u25A1 Step 7: Remove duplicate operations (same method + path)\n\u25A1 Step 8: Add required authentication operations for all operations in the chain\n\u25A1 Step 9: Sort dependencies by execution order\n\u25A1 Step 10: FINAL COMPLETENESS VERIFICATION - Ensure entire execution path is covered\n\u25A1 Step 11: Verify all operations exist in Available API Operations\n```\n\n## STRICT ID \u2192 CREATOR MAPPING RULES\n\nApply these rules systematically to find creator operations:\n\n### Primary Mapping Strategy\n```\nID Pattern \u2192 Creator Operation Search\n- articleId \u2192 POST /articles\n- userId \u2192 POST /users OR POST /auth/user/join\n- categoryId \u2192 POST /categories\n- commentId \u2192 POST /articles/{articleId}/comments (nested resource)\n- orderId \u2192 POST /orders\n- productId \u2192 POST /products\n- reviewId \u2192 POST /products/{productId}/reviews (nested resource)\n```\n\n### Search Algorithm (Apply in Order)\n```\nFOR EACH required_id IN requiredIds:\n  1. Extract entity name: remove \"Id\" suffix (articleId \u2192 article)\n  2. Search for POST /{entities} (plural form)\n  3. If not found, search for POST /{entity} (singular form)  \n  4. If not found, search for nested creation: POST /parent/{parentId}/{entities}\n  5. For user-related IDs, also check POST /auth/{role}/join\n  6. IF creator_operation found AND creator_operation NOT IN current_dependencies:\n       ADD creator_operation TO dependencies\n  7. IF creator_operation NOT found:\n       FLAG as external/pre-existing resource\nEND FOR\n```\n\n## COMPREHENSIVE DEPENDENCY COMPLETENESS VERIFICATION\n\n### CRITICAL REQUIREMENT: Complete Dependency Chain Analysis\n\nBefore passing any scenario, you MUST verify that the ENTIRE dependency ecosystem is captured:\n\n#### Recursive Dependency Deep Dive\n```\nFOR EACH operation IN dependencies:\n  1. Check operation in Candidate Dependencies table\n  2. IF operation has required IDs:\n     - Find creator operations for those IDs\n     - IF creators NOT in dependencies: ADD them\n     - REPEAT this process for newly added creators\n  3. Continue until NO MORE missing dependencies found\n```\n\n#### Complete Execution Path Verification\n```\nVERIFICATION CHECKLIST:\n\u25A1 Target operation can execute (all its required IDs have creators)\n\u25A1 Each dependency can execute (all their required IDs have creators)  \n\u25A1 Authentication context exists for ALL operations requiring authorization\n\u25A1 No operation depends on resources that aren't created earlier in the chain\n\u25A1 Execution sequence is valid from start to finish\n```\n\n#### Dependency Chain Completeness Test\nBefore setting `pass: true`, ask yourself:\n- \"If I execute these dependencies in order, will EVERY operation have all its required resources available?\"\n- \"Are there any missing links in the chain from authentication to target execution?\"\n- \"Have I checked EVERY creator operation for its own dependencies recursively?\"\n\n### Completeness Failure Examples\n```\nINCOMPLETE SCENARIO (pass: false):\nDependencies: [POST /auth/user/join, POST /articles]\nTarget: POST /articles/{articleId}/comments\nIssue: Missing commentId creator\n\nINCOMPLETE SCENARIO (pass: false):  \nDependencies: [POST /auth/user/join, POST /categories, POST /articles]\nBut POST /articles requires userId and Candidate Dependencies shows it needs userId\nIssue: POST /articles can't execute because userId dependency missing\n\nCOMPLETE SCENARIO (pass: true):\nDependencies: [POST /auth/user/join, POST /categories, POST /articles, POST /articles/{articleId}/comments]\nAll operations can execute in sequence with required resources available\n```\n\n## DUPLICATE REMOVAL ALGORITHM\n\n```\nDEDUPLICATION RULES:\n1. Group operations by: operation.method + operation.path\n2. If duplicates found:\n   - Keep FIRST occurrence\n   - Remove all subsequent duplicates\n3. Special case - Authentication operations:\n   - Keep only ONE authentication operation per required role\n   - Must only use join for new user scenarios\n```\n\n## AUTHENTICATION CONTEXT VALIDATION\n\n### Authentication Requirements Analysis\n```\nFOR EACH operation IN dependencies + target_operation:\n  IF operation.authorizationRole IS NOT null:\n    required_auth_role = operation.authorizationRole\n    auth_operation = find_auth_operation_for_role(required_auth_role)\n    IF auth_operation NOT IN dependencies:\n      ADD auth_operation TO dependencies (at beginning)\n    END IF\n  END IF\nEND FOR\n```\n\n### Authentication Type Selection\n- **join operations**: Create new user accounts (POST /auth/{role}/join)\n- **login operations**: Use existing accounts (POST /auth/{role}/login)\n- **Default choice**: Use join for test scenarios (creates isolated test data)\n\n## EXECUTION ORDER ALGORITHM\n\nSort dependencies using this strict ordering:\n\n```\nORDER PRIORITY:\n1. Authentication operations (authorizationType: \"join\" or \"login\") \u2192 FIRST\n2. Independent entities (no required IDs in Candidate Dependencies)\n3. Level 1 dependencies (depend only on independent entities)\n4. Level 2 dependencies (depend on Level 1 entities)\n5. Continue by dependency level until target operation\n6. Target operation \u2192 LAST (not in dependencies, but validates ordering)\n```\n\n### Dependency Level Calculation\n```\nFOR EACH operation:\n  IF operation has no required IDs:\n    level = 0 (independent)\n  ELSE:\n    level = max(dependency_levels) + 1\n  END IF\n```\n\n## DETAILED ANALYSIS PROCESS\n\nFor each scenario, output your analysis process:\n\n### Analysis Format\n```\nSCENARIO ANALYSIS: {scenario.functionName}\nRequired IDs: [{list from requiredIds field}]\n\nID MAPPING ANALYSIS:\n- articleId \u2192 Found: POST /articles \u2192 Status: [Present/Missing] in dependencies\n- categoryId \u2192 Found: POST /categories \u2192 Status: [Present/Missing] in dependencies\n- userId \u2192 Found: POST /auth/user/join \u2192 Status: [Present/Missing] in dependencies\n\nAUTHENTICATION ANALYSIS:\n- Target operation authorization: {authorizationRole}\n- Required authentication: {auth operation needed}\n- Current authentication: {auth operations in dependencies}\n\nDUPLICATE ANALYSIS:\n- Found duplicates: [{list of duplicate operations}]\n- Actions: [{list of removals}]\n\nRECURSIVE DEPENDENCY ANALYSIS:\n- Checking POST /articles dependencies: {required IDs from Candidate Dependencies}\n- Missing recursive dependencies: [{list}]\n- Added: [{operations added to complete the chain}]\n\nEXECUTION ORDER ANALYSIS:\n- Current order: [{current dependency order}]\n- Corrected order: [{logical execution order}]\n\nCOMPLETENESS VERIFICATION:\n- Can all operations execute in sequence? [Yes/No]\n- Any missing links in execution chain? [Yes/No]\n- All required resources available when needed? [Yes/No]\n```\n\n## OUTPUT DECISION FRAMEWORK\n\n### Option A: Pass Without Changes (`pass: true`)\n**Use ONLY when ALL conditions are met:**\n- [ ] Every ID in `requiredIds` has a corresponding creator operation in dependencies\n- [ ] All recursive dependencies are included (check each creator operation in Candidate Dependencies)\n- [ ] All authentication requirements are satisfied\n- [ ] No duplicate operations exist\n- [ ] Dependencies are ordered correctly for execution\n- [ ] All referenced operations exist in Available API Operations\n- [ ] **COMPLETENESS VERIFICATION**: Confirm that ALL necessary dependencies have been identified by checking:\n  - Each creator operation's own dependencies (recursive check using Candidate Dependencies table)\n  - All authorization requirements throughout the entire dependency chain\n  - No missing links in the complete execution path from authentication to target operation\n\n### Option B: Provide Corrections (`pass: false`)\n**Use when ANY condition fails and provide corrected dependencies**\n\n## VALIDATION EXAMPLES\n\n### Example 1: Complete ID Coverage\n```\nScenario Target: PUT /articles/{articleId}/comments/{commentId}\nRequired IDs: [\"articleId\", \"commentId\", \"userId\"]\n\nExpected Dependencies (Correct Order):\n1. POST /auth/user/join (creates userId, establishes user context)\n2. POST /articles (creates articleId, may need userId)\n3. POST /articles/{articleId}/comments (creates commentId, needs articleId)\n\nAnalysis:\n- articleId \u2192 POST /articles \u2713\n- commentId \u2192 POST /articles/{articleId}/comments \u2713  \n- userId \u2192 POST /auth/user/join \u2713\n```\n\n### Example 2: Missing Creator Operations\n```\nScenario Target: POST /orders\nRequired IDs: [\"productId\", \"userId\", \"shippingAddressId\"]\nCurrent Dependencies: [POST /auth/user/join]\n\nMissing Creators:\n- productId \u2192 ADD: POST /products\n- shippingAddressId \u2192 ADD: POST /users/{userId}/addresses\n\nCorrected Dependencies:\n1. POST /auth/user/join (creates userId)\n2. POST /products (creates productId)  \n3. POST /users/{userId}/addresses (creates shippingAddressId, needs userId)\n```\n\n### Example 3: Recursive Dependency Analysis\n```\nScenario Target: POST /articles/{articleId}/comments\nRequired IDs: [\"articleId\"]\nCurrent Dependencies: [POST /articles]\n\nRecursive Check:\n- POST /articles checked in Candidate Dependencies\n- POST /articles requires: [\"categoryId\", \"userId\"]\n- Missing: POST /categories, POST /auth/user/join\n\nCorrected Dependencies:\n1. POST /auth/user/join (creates userId)\n2. POST /categories (creates categoryId)\n3. POST /articles (creates articleId, needs userId + categoryId)\n```\n\n### Example 4: Duplicate Removal\n```\nCurrent Dependencies:\n1. POST /auth/user/join (purpose: \"Create user\")\n2. POST /categories (purpose: \"Create category\")\n3. POST /auth/user/join (purpose: \"Establish authentication\")\n\nIssue: Duplicate authentication operation\nSolution: Remove second occurrence, keep first\n```\n\n## ERROR HANDLING GUIDELINES\n\n### When Creator Operation Not Found\n```\nIF required_id has no creator operation in Available API Operations:\n  1. Mark as external/pre-existing resource\n  2. Document in analysis output\n  3. Do NOT add non-existent operations to dependencies\n  4. Continue validation for other IDs\n```\n\n### When Multiple Creator Candidates Exist\n```\nIF multiple operations could create the same resource:\n  1. Prefer POST operations over other methods\n  2. Prefer direct resource creation over nested creation\n  3. Choose the most specific creator (POST /articles over POST /content)\n```\n\n## SUCCESS CRITERIA\n\nA successful review ensures:\n- **Complete ID Coverage**: Every requiredIds entry has a creator in dependencies\n- **Complete Recursive Coverage**: All creator operations' dependencies are also included\n- **No Duplicates**: Clean, non-redundant dependency list\n- **Proper Authentication**: User context correctly established\n- **Logical Ordering**: Dependencies follow execution sequence\n- **Valid Operations**: All references exist in Available API Operations\n- **Implementable Scenarios**: Complete test execution path from setup to target\n- **End-to-End Verification**: Entire dependency chain can execute successfully\n\n## CRITICAL REMINDERS\n\n1. **Required IDs Are MANDATORY**: Every ID in `requiredIds` MUST have a creator operation\n2. **Recursive Analysis Is CRITICAL**: Check EVERY creator operation for its own dependencies\n3. **Completeness Before Pass**: Only pass when the ENTIRE dependency ecosystem is complete\n4. **Systematic Search**: Use ID mapping rules consistently\n5. **Duplicate Elimination**: Remove redundant operations automatically\n6. **Authentication First**: Always place auth operations at the beginning\n7. **Verify Existence**: Only reference operations from Available API Operations list\n8. **Logical Ordering**: Ensure dependencies can execute in sequence\n9. **Analysis Documentation**: Show your work for transparency\n10. **Final Verification**: Ask yourself if the entire execution path is bulletproof\n\nYour thorough analysis ensures test scenarios are fully implementable and will execute successfully with complete dependency coverage." /* AutoBeSystemPromptConstant.TEST_SCENARIO_REVIEW */,
         },
         {
             id: (0, uuid_1.v7)(),
             created_at: new Date().toISOString(),
             type: "assistantMessage",
             text: utils_1.StringUtil.trim `
-        # Available API Operations for Reference
+        ## Instructions
+
+        The following e2e-test-specific instructions were extracted by AI from
+        the user's requirements and conversations. These instructions focus
+        exclusively on test-related aspects such as test coverage priorities,
+        specific edge cases to validate, business logic verification strategies,
+        and critical user workflows that must be tested.
+        
+        Apply these instructions when reviewing test scenarios to ensure the
+        tests align with the user's testing requirements and expectations.
+        If any instructions are not relevant to the target API operations,
+        you may ignore them.
+
+        ${props.instruction}
+
+        ## Available API Operations for Reference
 
         Below are all available API operations and interface schemas for validation purposes.
         Match each operation with its corresponding schema.
 
         \`\`\`json
-        ${JSON.stringify({ operations: document.operations })}
+        ${JSON.stringify({
+                operations: document.operations,
+            })}
         \`\`\`
-      `,
-        },
-        {
-            id: (0, uuid_1.v7)(),
-            created_at: new Date().toISOString(),
-            type: "assistantMessage",
-            text: utils_1.StringUtil.trim `
 
-      # Test Scenario Groups
+        ## Test Scenario Groups
 
-      Please review the following test scenario groups:
+        Please review the following test scenario groups:
 
-      \`\`\`json
-      ${JSON.stringify(groups.map((g) => {
+        \`\`\`json
+        ${JSON.stringify(props.groups.map((g) => {
                 return Object.assign(Object.assign({}, g), { scenarios: g.scenarios.map((s) => {
                         const requiredId = [];
                         s.dependencies.forEach((dep) => {
@@ -70,18 +80,14 @@ function transformTestScenarioReviewHistories(ctx, groups) {
                                 }
                             });
                         });
-                        return Object.assign(Object.assign({}, s), { requiredIds: requiredId.length > 0 ? Array.from(new Set(requiredId)) : [] });
+                        return Object.assign(Object.assign({}, s), { requiredIds: requiredId.length > 0
+                                ? Array.from(new Set(requiredId))
+                                : [] });
                     }) });
             }))}
-      \`\`\`
-      `,
-        },
-        {
-            id: (0, uuid_1.v7)(),
-            created_at: new Date().toISOString(),
-            type: "assistantMessage",
-            text: utils_1.StringUtil.trim `
-        # Candidate Dependencies
+        \`\`\`
+
+        ## Candidate Dependencies
     
         List of candidate dependencies extracted from path parameters and request bodies.
 

package/lib/orchestrate/test/histories/transformTestScenarioReviewHistories.js.map

@@ -1 +1 @@
-{"version":3,"file":"transformTestScenarioReviewHistories.js","sourceRoot":"","sources":["../../../../src/orchestrate/test/histories/transformTestScenarioReviewHistories.ts"],"names":[],"mappings":";;AAWA,oFAgJC;AAzJD,yCAA2C;AAE3C,+BAA0B;AAK1B,8DAA2D;AAE3D,SAAgB,oCAAoC,CAGlD,GAAyB,EACzB,MAAuD;;IASvD,MAAM,QAAQ,GACZ,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,SAAS,0CAAE,QAAQ,CAAC;IAElC,IAAI,QAAQ,KAAK,SAAS,EAAE,CAAC;QAC3B,MAAM,IAAI,KAAK,CACb,+DAA+D,CAChE,CAAC;IACJ,CAAC;IAED,MAAM,aAAa,GAAoB,QAAQ,CAAC,UAAU;SACvD,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC;QACX,QAAQ,EAAE;YACR,MAAM,EAAE,CAAC,CAAC,MAAM;YAChB,IAAI,EAAE,CAAC,CAAC,IAAI;SACb;QACD,GAAG,EAAE,IAAA,iCAAe,EAAC;YACnB,QAAQ;YACR,SAAS,EAAE,CAAC;SACb,CAAC;KACH,CAAC,CAAC;SACF,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,GAAG,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC;IAErC,OAAO;QACL;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,opaAAiD;SACtD;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;UAOjB,IAAI,CAAC,SAAS,CAAC,EAAE,UAAU,EAAE,QAAQ,CAAC,UAAU,EAAE,CAAC;;OAEtD;SACF;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;QAOnB,IAAI,CAAC,SAAS,CACd,MAAM,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE;gBACf,uCACK,CAAC,KACJ,SAAS,EAAE,CAAC,CAAC,SAAS,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE;wBAC/B,MAAM,UAAU,GAAa,EAAE,CAAC;wBAEhC,CAAC,CAAC,YAAY,CAAC,OAAO,CAAC,CAAC,GAAG,EAAE,EAAE;4BAC7B,QAAQ,CAAC,UAAU,CAAC,OAAO,CAAC,CAAC,EAAE,EAAE,EAAE;gCACjC,IACE,CAAC,CAAC,QAAQ,CAAC,MAAM,KAAK,EAAE,CAAC,MAAM;oCAC/B,CAAC,CAAC,QAAQ,CAAC,IAAI,KAAK,EAAE,CAAC,IAAI,EAC3B,CAAC;oCACD,UAAU,CAAC,IAAI,CACb,GAAG,IAAA,iCAAe,EAAC,EAAE,QAAQ,EAAE,SAAS,EAAE,EAAE,EAAE,CAAC,CAChD,CAAC;gCACJ,CAAC;gCAED,IACE,EAAE,CAAC,MAAM,KAAK,GAAG,CAAC,QAAQ,CAAC,MAAM;oCACjC,EAAE,CAAC,IAAI,KAAK,GAAG,CAAC,QAAQ,CAAC,IAAI,EAC7B,CAAC;oCACD,UAAU,CAAC,IAAI,CACb,GAAG,IAAA,iCAAe,EAAC,EAAE,QAAQ,EAAE,SAAS,EAAE,EAAE,EAAE,CAAC,CAChD,CAAC;gCACJ,CAAC;4BACH,CAAC,CAAC,CAAC;wBACL,CAAC,CAAC,CAAC;wBAEH,uCACK,CAAC,KACJ,WAAW,EACT,UAAU,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,IAAI,CAAC,IAAI,GAAG,CAAC,UAAU,CAAC,CAAC,CAAC,CAAC,CAAC,EAAE,IAC9D;oBACJ,CAAC,CAAC,IACF;YACJ,CAAC,CAAC,CACH;;OAEA;SACF;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;;;;;;;;UAkBjB,aAAa;iBACZ,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CACT;gBACE,KAAK,CAAC,CAAC,QAAQ,CAAC,MAAM,IAAI,CAAC,CAAC,QAAQ,CAAC,IAAI,IAAI;gBAC7C,CAAC,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,KAAK,EAAE,IAAI,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;aAC1C,CAAC,IAAI,CAAC,KAAK,CAAC,CACd;iBACA,IAAI,CAAC,IAAI,CAAC;;;OAGd;SAC+C;KACnD,CAAC;AACJ,CAAC"}
+{"version":3,"file":"transformTestScenarioReviewHistories.js","sourceRoot":"","sources":["../../../../src/orchestrate/test/histories/transformTestScenarioReviewHistories.ts"],"names":[],"mappings":";;AAUA,oFAoJC;AA5JD,yCAA2C;AAC3C,+BAA0B;AAK1B,8DAA2D;AAE3D,SAAgB,oCAAoC,CAAC,KAIpD;;IAQC,MAAM,QAAQ,GACZ,MAAA,KAAK,CAAC,KAAK,CAAC,SAAS,0CAAE,QAAQ,CAAC;IAClC,IAAI,QAAQ,KAAK,SAAS,EAAE,CAAC;QAC3B,MAAM,IAAI,KAAK,CACb,+DAA+D,CAChE,CAAC;IACJ,CAAC;IAED,MAAM,aAAa,GAAoB,QAAQ,CAAC,UAAU;SACvD,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC;QACX,QAAQ,EAAE;YACR,MAAM,EAAE,CAAC,CAAC,MAAM;YAChB,IAAI,EAAE,CAAC,CAAC,IAAI;SACb;QACD,GAAG,EAAE,IAAA,iCAAe,EAAC;YACnB,QAAQ;YACR,SAAS,EAAE,CAAC;SACb,CAAC;KACH,CAAC,CAAC;SACF,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,GAAG,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC;IAErC,OAAO;QACL;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,w9aAAiD;SACtD;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;;;;UAcjB,KAAK,CAAC,WAAW;;;;;;;;UAQjB,IAAI,CAAC,SAAS,CAAC;gBACf,UAAU,EAAE,QAAQ,CAAC,UAAU;aAChC,CAAC;;;;;;;;UAQA,IAAI,CAAC,SAAS,CACd,KAAK,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE;gBACrB,uCACK,CAAC,KACJ,SAAS,EAAE,CAAC,CAAC,SAAS,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE;wBAC/B,MAAM,UAAU,GAAa,EAAE,CAAC;wBAEhC,CAAC,CAAC,YAAY,CAAC,OAAO,CAAC,CAAC,GAAG,EAAE,EAAE;4BAC7B,QAAQ,CAAC,UAAU,CAAC,OAAO,CAAC,CAAC,EAAE,EAAE,EAAE;gCACjC,IACE,CAAC,CAAC,QAAQ,CAAC,MAAM,KAAK,EAAE,CAAC,MAAM;oCAC/B,CAAC,CAAC,QAAQ,CAAC,IAAI,KAAK,EAAE,CAAC,IAAI,EAC3B,CAAC;oCACD,UAAU,CAAC,IAAI,CACb,GAAG,IAAA,iCAAe,EAAC,EAAE,QAAQ,EAAE,SAAS,EAAE,EAAE,EAAE,CAAC,CAChD,CAAC;gCACJ,CAAC;gCAED,IACE,EAAE,CAAC,MAAM,KAAK,GAAG,CAAC,QAAQ,CAAC,MAAM;oCACjC,EAAE,CAAC,IAAI,KAAK,GAAG,CAAC,QAAQ,CAAC,IAAI,EAC7B,CAAC;oCACD,UAAU,CAAC,IAAI,CACb,GAAG,IAAA,iCAAe,EAAC,EAAE,QAAQ,EAAE,SAAS,EAAE,EAAE,EAAE,CAAC,CAChD,CAAC;gCACJ,CAAC;4BACH,CAAC,CAAC,CAAC;wBACL,CAAC,CAAC,CAAC;wBAEH,uCACK,CAAC,KACJ,WAAW,EACT,UAAU,CAAC,MAAM,GAAG,CAAC;gCACnB,CAAC,CAAC,KAAK,CAAC,IAAI,CAAC,IAAI,GAAG,CAAC,UAAU,CAAC,CAAC;gCACjC,CAAC,CAAC,EAAE,IACR;oBACJ,CAAC,CAAC,IACF;YACJ,CAAC,CAAC,CACH;;;;;;;;;;;;;;;;;;;;UAoBC,aAAa;iBACZ,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CACT;gBACE,KAAK,CAAC,CAAC,QAAQ,CAAC,MAAM,IAAI,CAAC,CAAC,QAAQ,CAAC,IAAI,IAAI;gBAC7C,CAAC,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,KAAK,EAAE,IAAI,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;aAC1C,CAAC,IAAI,CAAC,KAAK,CAAC,CACd;iBACA,IAAI,CAAC,IAAI,CAAC;;;OAGd;SACF;KACF,CAAC;AACJ,CAAC"}

package/lib/orchestrate/test/histories/transformTestWriteHistories.d.ts

@@ -3,7 +3,11 @@ import { AutoBeTestScenario } from "@autobe/interface";
 import { ILlmSchema } from "@samchon/openapi";
 import { AutoBeContext } from "../../../context/AutoBeContext";
 import { IAutoBeTestScenarioArtifacts } from "../structures/IAutoBeTestScenarioArtifacts";
-export declare function transformTestWriteHistories<Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, scenario: AutoBeTestScenario, artifacts: IAutoBeTestScenarioArtifacts): Promise<Array<IAgenticaHistoryJson.ISystemMessage | IAgenticaHistoryJson.IAssistantMessage>>;
+export declare function transformTestWriteHistories<Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, props: {
+    instruction: string;
+    scenario: AutoBeTestScenario;
+    artifacts: IAutoBeTestScenarioArtifacts;
+}): Promise<Array<IAgenticaHistoryJson.ISystemMessage | IAgenticaHistoryJson.IAssistantMessage>>;
 export declare namespace transformTestWriteHistories {
     function structures(artifacts: IAutoBeTestScenarioArtifacts): string;
     function functional(artifacts: IAutoBeTestScenarioArtifacts): string;