@bugzy-ai/bugzy 1.18.4 → 1.19.0

package/dist/index.cjs

@@ -317,10 +317,6 @@ Extract the following from arguments:
 - **type**: Test type (exploratory, functional, regression, smoke) - defaults to functional
 - **focus**: Optional specific feature or section to focus on`
     },
-    // Step 4: Load Project Context (library)
-    "load-project-context",
-    // Step 5: Knowledge Base Read (library)
-    "read-knowledge-base",
     // Step 5: Gather Context (inline)
     {
       inline: true,
@@ -524,11 +520,7 @@ var generateTestPlanTask = {
       title: "Arguments",
       content: `Product description: $ARGUMENTS`
     },
-    // Step 4: Load Project Context (library)
-    "load-project-context",
-    // Step 5: Knowledge Base Read (library)
-    "read-knowledge-base",
-    // Step 6: Process Description (inline)
+    // Step 5: Process Description (inline)
     {
       inline: true,
       title: "Process the Product Description",
@@ -704,10 +696,6 @@ Process team messages and handle multi-turn conversations with the product team
       title: "Arguments",
       content: `Team message/thread context: $ARGUMENTS`
     },
-    // Step 4: Load Project Context (library)
-    "load-project-context",
-    // Step 5: Knowledge Base Read (library)
-    "read-knowledge-base",
     // Step 6: Detect Intent (inline - simplified, no handler file loading)
     {
       inline: true,
@@ -902,10 +890,6 @@ Process webhook events from integrated systems by analyzing event content, deter
       title: "Arguments",
       content: `Arguments: $ARGUMENTS`
     },
-    // Step 4: Load Project Context (library)
-    "load-project-context",
-    // Step 5: Knowledge Base Read (library)
-    "read-knowledge-base",
     // Step 5: Understand Event Context (inline)
     {
       inline: true,
@@ -1374,10 +1358,6 @@ Extract the following from arguments:
   - Specific file: path to a specific test file
   - All tests: "all" or "" \u2192 runs entire test suite`
     },
-    // Step 4: Load Project Context (library)
-    "load-project-context",
-    // Step 5: Knowledge Base Read (library)
-    "read-knowledge-base",
     // Step 5: Test Execution Strategy (library)
     "read-test-strategy",
     // Step 6: Clarification Protocol (library)
@@ -1526,10 +1506,6 @@ This task performs comprehensive change verification with:
 
 The input format determines the trigger source and context extraction strategy.`
     },
-    // Step 4: Load Project Context (library)
-    "load-project-context",
-    // Step 5: Knowledge Base Read (library)
-    "read-knowledge-base",
     // Step 5: Detect Trigger Source (inline)
     {
       inline: true,
@@ -1939,7 +1915,9 @@ Include in the message:
 - Any blocking issues or critical findings`,
       conditionalOnSubagent: "team-communicator"
     },
-    // Step 15: Documentation Research (conditional library step)
+    // Step 15: Knowledge Base Update (library)
+    "update-knowledge-base",
+    // Step 16: Documentation Research (conditional library step)
     {
       stepId: "gather-documentation",
       conditionalOnSubagent: "documentation-researcher"
@@ -1990,9 +1968,7 @@ Output to CI build log (print detailed results to stdout) and exit with appropri
 Post PR comment if GitHub context available.`,
       conditionalOnSubagent: "team-communicator"
     },
-    // Step 17: Knowledge Base Update (library)
-    "update-knowledge-base",
-    // Step 18: Handle Special Cases (inline)
+    // Step 17: Handle Special Cases (inline)
     {
       inline: true,
       title: "Handle Special Cases",
@@ -2044,8 +2020,6 @@ This command orchestrates the complete test coverage workflow in a single execut
       content: `Focus area: $ARGUMENTS`
     },
     // Phase 1: Setup
-    "load-project-context",
-    "read-knowledge-base",
     {
       stepId: "gather-documentation",
       conditionalOnSubagent: "documentation-researcher"
@@ -2114,9 +2088,6 @@ var exploreApplicationTask = {
 - **depth**: shallow (15-20 min) or deep (45-60 min, default)
 - **system**: target system (optional for multi-system setups)`
     },
-    // Setup
-    "load-project-context",
-    "read-knowledge-base",
     // Exploration Protocol (adaptive depth)
     "exploration-protocol",
     // Execute
@@ -2181,11 +2152,7 @@ This task is triggered automatically when test results are submitted to the Bugz
       title: "Arguments",
       content: `Arguments: $ARGUMENTS`
     },
-    // Step 4: Load Project Context (library)
-    "load-project-context",
-    // Step 5: Knowledge Base Read (library)
-    "read-knowledge-base",
-    // Step 6: Normalize Test Results (library — handles URL/inline results + manifest creation)
+    // Step 5: Normalize Test Results (library — handles URL/inline results + manifest creation)
     "normalize-test-results",
     // Step 7: Triage Failures (existing library step)
     "triage-failures",
@@ -2196,57 +2163,13 @@ This task is triggered automatically when test results are submitted to the Bugz
       stepId: "log-product-bugs",
       conditionalOnSubagent: "issue-tracker"
     },
-    // Step 10: Update Knowledge Base (library)
-    "update-knowledge-base",
-    // Step 11: Notify Team (conditional — requires team-communicator)
+    // Step 10: Notify Team (conditional — requires team-communicator)
     {
       stepId: "notify-team",
       conditionalOnSubagent: "team-communicator"
     },
-    // Step 12: Generate Triage Report (inline)
-    {
-      inline: true,
-      title: "Generate Triage Report",
-      content: `## Generate Triage Report
-
-Create a structured triage report as the task output. This report is stored in \`task_executions.result\` and displayed in the Bugzy dashboard.
-
-**Report Structure:**
-\`\`\`json
-{
-  "summary": {
-    "total": <number>,
-    "passed": <number>,
-    "failed": <number>,
-    "skipped": <number>,
-    "duration_ms": <number or null>
-  },
-  "ci_metadata": {
-    "pipeline_url": "<from event payload>",
-    "commit_sha": "<from event payload>",
-    "branch": "<from event payload>"
-  },
-  "triage": {
-    "product_bugs": [
-      {
-        "test_name": "<name>",
-        "error": "<brief error>",
-        "reason": "<why this is a product bug>"
-      }
-    ],
-    "test_issues": [
-      {
-        "test_name": "<name>",
-        "error": "<brief error>",
-        "reason": "<why this is a test issue>"
-      }
-    ]
-  }
-}
-\`\`\`
-
-Output this JSON as the final result of the task.`
-    }
+    // Step 11: Knowledge Base Update (library)
+    "update-knowledge-base"
   ],
   requiredSubagents: ["browser-automation", "test-engineer"],
   optionalSubagents: ["issue-tracker", "team-communicator"],
@@ -2280,9 +2203,6 @@ var exploreTestCodebaseTask = {
 **Parse:**
 - **focus**: specific area to analyze (default: comprehensive)`
     },
-    // Setup
-    "load-project-context",
-    "read-knowledge-base",
     // Core analysis
     "analyze-test-codebase",
     // Generate results parser for normalizing test output
@@ -5378,38 +5298,6 @@ async function getAgentConfiguration(taskDefinitions, projectSubAgents) {
   };
 }
 
-// src/tasks/steps/setup/read-knowledge-base.ts
-var readKnowledgeBaseStep = {
-  id: "read-knowledge-base",
-  title: "Read Knowledge Base",
-  category: "setup",
-  content: `## Knowledge Base Context
-
-Before proceeding, read the curated knowledge base to inform your work:
-
-**Location:** \`.bugzy/runtime/knowledge-base.md\`
-
-**Purpose:** The knowledge base is a living collection of factual knowledge - what we currently know and believe to be true about this project, its patterns, and its context. This is NOT a historical log, but a curated snapshot that evolves as understanding improves.
-
-**How to Use:**
-1. Read the knowledge base to understand:
-   - Project-specific patterns and conventions
-   - Known behaviors and system characteristics
-   - Relevant context from past work
-   - Documented decisions and approaches
-
-2. Apply this knowledge to:
-   - Make informed decisions aligned with project patterns
-   - Avoid repeating past mistakes
-   - Build on existing understanding
-   - Maintain consistency with established practices
-
-3. **Relay to subagents**: Subagents do NOT read the knowledge base directly. When delegating work, you MUST include relevant KB patterns in your delegation message \u2014 especially testing patterns (timing, selectors, assertion approaches) that affect test reliability.
-
-**Note:** The knowledge base may not exist yet or may be empty. If it doesn't exist or is empty, proceed without this context and help build it as you work.`,
-  tags: ["setup", "context"]
-};
-
 // src/tasks/steps/setup/read-test-strategy.ts
 var readTestStrategyStep = {
   id: "read-test-strategy",
@@ -5431,38 +5319,6 @@ Apply the strategy guidance when determining which tests to run.
   tags: ["setup", "test-execution", "strategy"]
 };
 
-// src/tasks/steps/setup/load-project-context.ts
-var loadProjectContextStep = {
-  id: "load-project-context",
-  title: "Load Project Context",
-  category: "setup",
-  content: `## Load Project Context
-
-Check for existing project context to inform your work:
-
-**1. Check Project Context**
-- Read \`.bugzy/runtime/project-context.md\` if it exists
-- Check if it contains information relevant to: $ARGUMENTS
-- This file contains:
-  - Application overview and architecture
-  - Key user flows and features
-  - Technical patterns discovered
-  - Environment details
-
-**2. Check Test Execution Strategy**
-- Read \`./tests/docs/test-execution-strategy.md\` if it exists
-- Understand available test tiers and when to use them
-- Note default behaviors and time/coverage trade-offs
-
-**3. Document Findings**
-Note what context is available:
-\`\`\`
-Project Context: [exists/missing] - [relevant to focus area: yes/no/partial]
-Test Strategy: [exists/missing]
-\`\`\``,
-  tags: ["setup", "context"]
-};
-
 // src/tasks/steps/setup/security-notice.ts
 var securityNoticeStep = {
   id: "security-notice",
@@ -6681,40 +6537,6 @@ Notify the team about progress and results:
   tags: ["communication", "optional"]
 };
 
-// src/tasks/steps/maintenance/update-knowledge-base.ts
-var updateKnowledgeBaseStep = {
-  id: "update-knowledge-base",
-  title: "Update Knowledge Base",
-  category: "maintenance",
-  content: `## Knowledge Base Maintenance
-
-After completing your work, update the knowledge base with new insights.
-
-**Location:** \`.bugzy/runtime/knowledge-base.md\`
-
-**Process:**
-
-1. **Read the maintenance guide** at \`.bugzy/runtime/knowledge-maintenance-guide.md\` to understand when to ADD, UPDATE, or REMOVE entries and how to maintain a curated knowledge base (not an append-only log)
-
-2. **Review the current knowledge base** to check for overlaps, contradictions, or opportunities to consolidate existing knowledge
-
-3. **Update the knowledge base** following the maintenance guide principles:
-   - Favor consolidation over addition
-   - Update rather than append
-   - Resolve contradictions immediately
-   - Focus on quality over completeness
-
-**What to Add:**
-- New patterns discovered about the application
-- Behaviors that differ from expectations
-- Technical constraints or requirements
-- Useful selectors or navigation patterns
-- Error handling patterns
-
-**Remember:** Every entry should answer "Will this help someone working on this project in 6 months?"`,
-  tags: ["maintenance", "knowledge"]
-};
-
 // src/tasks/steps/maintenance/generate-final-report.ts
 var generateFinalReportStep = {
   id: "generate-final-report",
@@ -6886,13 +6708,45 @@ For each modified test case:
   tags: ["maintenance", "automation", "feedback"]
 };
 
+// src/tasks/steps/maintenance/update-knowledge-base.ts
+var updateKnowledgeBaseStep = {
+  id: "update-knowledge-base",
+  title: "Update Knowledge Base",
+  category: "maintenance",
+  content: `## Knowledge Base Maintenance
+
+After completing your work, update the knowledge base with new insights.
+
+**Location:** \`.bugzy/runtime/knowledge-base.md\`
+
+**Process:**
+
+1. **Read the maintenance guide** at \`.bugzy/runtime/knowledge-maintenance-guide.md\` to understand when to ADD, UPDATE, or REMOVE entries and how to maintain a curated knowledge base (not an append-only log)
+
+2. **Review the current knowledge base** to check for overlaps, contradictions, or opportunities to consolidate existing knowledge
+
+3. **Update the knowledge base** following the maintenance guide principles:
+   - Favor consolidation over addition
+   - Update rather than append
+   - Resolve contradictions immediately
+   - Focus on quality over completeness
+
+**What to Add:**
+- New patterns discovered about the application
+- Behaviors that differ from expectations
+- Technical constraints or requirements
+- Useful selectors or navigation patterns
+- Error handling patterns
+
+**Remember:** Every entry should answer "Will this help someone working on this project in 6 months?"`,
+  tags: ["maintenance", "knowledge"]
+};
+
 // src/tasks/steps/index.ts
 var STEP_LIBRARY = {
   // Setup
   "security-notice": securityNoticeStep,
-  "read-knowledge-base": readKnowledgeBaseStep,
   "read-test-strategy": readTestStrategyStep,
-  "load-project-context": loadProjectContextStep,
   "gather-documentation": gatherDocumentationStep,
   // Exploration
   "exploration-protocol": explorationProtocolStep,
@@ -6918,12 +6772,12 @@ var STEP_LIBRARY = {
   // Communication
   "notify-team": notifyTeamStep,
   // Maintenance
-  "update-knowledge-base": updateKnowledgeBaseStep,
   "generate-final-report": generateFinalReportStep,
   "update-exploration-artifacts": updateExplorationArtifactsStep,
   "cleanup-temp-files": cleanupTempFilesStep,
   "validate-test-artifacts": validateTestArtifactsStep,
-  "sync-automation-from-feedback": syncAutomationFromFeedbackStep
+  "sync-automation-from-feedback": syncAutomationFromFeedbackStep,
+  "update-knowledge-base": updateKnowledgeBaseStep
 };
 function getStep(id) {
   const step = STEP_LIBRARY[id];