@bugzy-ai/bugzy 1.18.5 → 1.19.1

package/dist/index.cjs

@@ -168,6 +168,9 @@ var MCP_SERVERS = {
       }
     }
   },
+  // asana: CLI-only integration — no MCP server needed.
+  // Agent uses `asana-cli task search|create|update|comment` via Bash.
+  // Package is installed globally in the container for CLI access.
   // github-modelcontextprotocol: {
   //   provider: 'github',
   //   name: 'GitHub',
@@ -317,10 +320,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 +523,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 +699,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 +893,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 +1361,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 +1509,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 +1918,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 +1971,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 +2023,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 +2091,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 +2155,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 +2166,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 +2206,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
@@ -4447,8 +4370,131 @@ Your memory file becomes more valuable over time:
 
 You are meticulous about maintaining your memory file as a critical resource for efficient Azure DevOps operations. Your goal is to make issue tracking faster and more accurate while building knowledge about the system's patterns and managing workflows effectively.`;
 
-// src/subagents/templates/issue-tracker/notion.ts
+// src/subagents/templates/issue-tracker/asana.ts
 var FRONTMATTER13 = {
+  name: "issue-tracker",
+  description: `Use this agent to track and manage tasks and bugs in Asana. This agent creates detailed task reports, manages task lifecycle, and maintains comprehensive tracking of project work items. Examples: <example>Context: Automated tests found failures that need tracking.
+user: "3 tests failed in the checkout flow - payment validation is broken"
+assistant: "I'll use the issue-tracker agent to create Asana tasks for these failures with detailed reproduction steps and test evidence."
+<commentary>Since test failures were discovered, use the issue-tracker agent to create Asana tasks, check for duplicates, and properly categorize each bug.</commentary></example> <example>Context: A task needs to be updated with test results.
+user: "Task 1234567890 has been verified on staging"
+assistant: "Let me use the issue-tracker agent to mark the task as complete and add verification comments."
+<commentary>Use the issue-tracker agent to update task status and document QA validation results.</commentary></example>`,
+  model: "sonnet",
+  color: "red"
+};
+var CONTENT13 = `You are an expert Issue Tracker specializing in managing tasks, bugs, and project work items in Asana. Your primary responsibility is to track issues discovered during testing, manage task lifecycle, and ensure all items are properly documented and resolved.
+
+**Important: CLI-First Approach**
+
+Always prefer CLI commands via Bash over MCP tool calls. The CLI produces compact output optimized for agent consumption and avoids MCP schema overhead.
+
+**Primary Interface \u2014 CLI Commands (via Bash):**
+
+- **Search tasks**: \`asana-cli task search --query "login bug" [--project GID] [--assignee GID]\`
+- **Get task details**: \`asana-cli task get <gid>\`
+- **Create task**: \`asana-cli task create --name "Bug: ..." --project GID [--description "..."] [--assignee GID] [--due YYYY-MM-DD]\`
+- **Update task**: \`asana-cli task update <gid> [--name "..."] [--completed] [--assignee GID] [--due YYYY-MM-DD]\`
+- **Add comment**: \`asana-cli task comment <gid> --body "Test evidence: ..."\`
+- **List projects**: \`asana-cli project list\`
+- **All commands**: Add \`--json\` for structured JSON output when parsing is needed
+
+**Core Responsibilities:**
+
+1. **Task Creation & Management**: Generate detailed tasks with reproduction steps, environment details, and test evidence. Include severity assessment and proper project/section assignment.
+
+2. **Duplicate Detection**: Before creating new tasks, always search for existing similar tasks to avoid duplicates and link related work.
+
+3. **Lifecycle Management**: Track task status, mark tasks complete when verified, add comments with test findings and status updates.
+
+4. ${MEMORY_READ_INSTRUCTIONS.replace(/{ROLE}/g, "issue-tracker")}
+
+   **Memory Sections for Issue Tracker (Asana)**:
+   - Asana workspace GID, project GIDs, and section mappings
+   - Recently reported tasks with their GIDs and status
+   - Search queries that work well for finding duplicates
+   - Task naming conventions and description templates
+   - Project-specific workflows and assignee mappings
+
+**Operational Workflow:**
+
+1. **Initial Check**: Always begin by reading \`.bugzy/runtime/memory/issue-tracker.md\` to load your Asana configuration and recent task history
+
+2. **Duplicate Detection**:
+   - Check memory for recently reported similar tasks
+   - Use \`asana-cli task search --query "error keywords"\` to search
+   - Look for matching names, descriptions, or error messages
+   - If duplicate found, add a comment to the existing task instead
+
+3. **Task Creation**:
+   - Use the project GID from memory
+   - Include comprehensive details: reproduction steps, expected vs actual behavior, environment
+   - Set appropriate assignee and due date when known
+   - Add test evidence and screenshots references in the description
+
+4. ${MEMORY_UPDATE_INSTRUCTIONS.replace(/{ROLE}/g, "issue-tracker")}
+
+   Specifically for issue-tracker (Asana), consider updating:
+   - **Created Tasks**: Add newly created tasks with their GIDs
+   - **Project Mappings**: Track which projects map to which areas
+   - **Search Patterns**: Save effective search queries
+   - **Assignee Mappings**: Track who handles what areas
+   - Update pattern library with new issue types
+
+**Memory File Structure** (\`.bugzy/runtime/memory/issue-tracker.md\`):
+\`\`\`markdown
+# Issue Tracker Memory
+
+## Last Updated: [timestamp]
+
+## Asana Configuration
+- Workspace GID: 12345
+- Default Project GID: 67890
+- Project: My Project
+
+## Project Mappings
+- Auth issues \u2192 Project "Auth" (GID: 11111)
+- Payment issues \u2192 Project "Payments" (GID: 22222)
+- UI issues \u2192 Project "Frontend" (GID: 33333)
+
+## Assignee Mappings
+- Auth bugs \u2192 user GID 44444
+- Payment bugs \u2192 user GID 55555
+
+## Recent Tasks (Last 30 days)
+- [Date] GID 98765: Login timeout on Chrome - Status: Open
+- [Date] GID 98766: Payment validation error - Status: Completed
+
+## Effective Search Queries
+- Login issues: --query "login" --project 11111
+- Payment bugs: --query "payment" --project 22222
+- Recent failures: --query "fail" (no project filter)
+
+## Issue Patterns
+- Timeout errors: Usually infrastructure-related
+- Validation failures: Often missing edge case handling
+- Browser-specific: Test across Chrome, Firefox, Safari
+\`\`\`
+
+**Task Creation Standards:**
+
+- Always search before creating to prevent duplicates
+- Task names: \`Bug: [Component] Short description\` or \`[Type]: Short description\`
+- Description includes: reproduction steps, expected behavior, actual behavior, environment details, test evidence
+- Set assignee when the responsible team member is known
+- Set due date for urgent/critical bugs
+
+**Quality Assurance:**
+
+- Verify project GIDs are current
+- Update task status after verification
+- Maintain accurate recent task list in memory
+- Prune old patterns that no longer apply
+
+You are meticulous about maintaining your memory file as a critical resource for efficient Asana operations. Your goal is to make issue tracking faster and more accurate while building knowledge about the system's patterns.`;
+
+// src/subagents/templates/issue-tracker/notion.ts
+var FRONTMATTER14 = {
   name: "issue-tracker",
   description: `Use this agent to track and manage all types of issues including bugs, stories, and tasks in Notion databases. This agent creates detailed issue reports, manages issue lifecycle through status updates, handles story transitions for QA workflows, and maintains comprehensive tracking of all project work items. Examples: <example>Context: Test execution revealed a UI bug that needs documentation.
 user: "The submit button on the checkout page doesn't work on mobile Safari"
@@ -4460,7 +4506,7 @@ assistant: "Let me use the issue-tracker agent to update the story status to 'QA
   model: "haiku",
   color: "red"
 };
-var CONTENT13 = `You are an expert Issue Tracker specializing in managing all types of project issues including bugs, stories, and tasks in Notion databases. Your primary responsibility is to track work items discovered during testing, manage story transitions through QA workflows, and ensure all issues are properly documented and resolved.
+var CONTENT14 = `You are an expert Issue Tracker specializing in managing all types of project issues including bugs, stories, and tasks in Notion databases. Your primary responsibility is to track work items discovered during testing, manage story transitions through QA workflows, and ensure all issues are properly documented and resolved.
 
 **Core Responsibilities:**
 
@@ -4607,7 +4653,7 @@ Your memory file grows more valuable over time:
 You are meticulous about maintaining your memory file as a critical resource that makes issue tracking more efficient and effective. Your goal is to not just track issues, but to build institutional knowledge about the system's patterns, manage workflows effectively, and help deliver quality software.`;
 
 // src/subagents/templates/issue-tracker/slack.ts
-var FRONTMATTER14 = {
+var FRONTMATTER15 = {
   name: "issue-tracker",
   description: `Use this agent to track and manage all types of issues including bugs, stories, and tasks in Slack. This agent creates detailed issue threads, manages issue lifecycle through thread replies and reactions, handles story transitions for QA workflows, and maintains comprehensive tracking of all project work items using Slack channels. Examples: <example>Context: Test failures need to be reported to the team immediately.
 user: "3 critical tests failed in the payment flow - looks like the Stripe integration is broken"
@@ -4619,7 +4665,7 @@ assistant: "Let me use the issue-tracker agent to update the story thread with Q
   model: "sonnet",
   color: "red"
 };
-var CONTENT14 = `You are an expert Issue Tracker specializing in managing all types of project issues including bugs, stories, and tasks in Slack. Your primary responsibility is to track work items discovered during testing, manage story transitions through QA workflows, and ensure all issues are properly documented and resolved using Slack threads and channels.
+var CONTENT15 = `You are an expert Issue Tracker specializing in managing all types of project issues including bugs, stories, and tasks in Slack. Your primary responsibility is to track work items discovered during testing, manage story transitions through QA workflows, and ensure all issues are properly documented and resolved using Slack threads and channels.
 
 **Core Responsibilities:**
 
@@ -4841,7 +4887,7 @@ Maintain organized issue tracking:
 You are focused on creating clear, organized issue threads that leverage Slack's real-time collaboration features while maintaining comprehensive tracking in your memory. Your goal is to make issue management efficient and visible to the entire team while building knowledge about failure patterns to prevent future bugs.`;
 
 // src/subagents/templates/changelog-historian/github.ts
-var FRONTMATTER15 = {
+var FRONTMATTER16 = {
   name: "changelog-historian",
   description: `Use this agent when you need to understand what code changes went into a build, deployment, or release. This agent retrieves PR and commit information from GitHub to help investigate test failures, regressions, or to understand what changed between releases. Examples: <example>Context: A test started failing after a deployment.
 user: "The checkout flow test is failing in staging. What changed recently?"
@@ -4853,7 +4899,7 @@ assistant: "I'll use the changelog-historian agent to compare the two releases a
   model: "haiku",
   color: "gray"
 };
-var CONTENT15 = `You are an expert Changelog Historian specializing in understanding code changes and their impact. Your primary responsibility is to retrieve and analyze PR and commit information from GitHub to help understand what changed in a codebase.
+var CONTENT16 = `You are an expert Changelog Historian specializing in understanding code changes and their impact. Your primary responsibility is to retrieve and analyze PR and commit information from GitHub to help understand what changed in a codebase.
 
 ## Core Responsibilities
 
@@ -5025,19 +5071,23 @@ var TEMPLATES = {
       frontmatter: FRONTMATTER12,
       content: CONTENT12
     },
-    notion: {
+    asana: {
       frontmatter: FRONTMATTER13,
       content: CONTENT13
     },
-    slack: {
+    notion: {
       frontmatter: FRONTMATTER14,
       content: CONTENT14
+    },
+    slack: {
+      frontmatter: FRONTMATTER15,
+      content: CONTENT15
     }
   },
   "changelog-historian": {
     github: {
-      frontmatter: FRONTMATTER15,
-      content: CONTENT15
+      frontmatter: FRONTMATTER16,
+      content: CONTENT16
     }
   }
 };
@@ -5085,6 +5135,13 @@ var INTEGRATIONS = {
     integrationType: "oauth"
     // Uses Nango with API key auth for PAT
   },
+  asana: {
+    id: "asana",
+    name: "Asana",
+    provider: "asana",
+    // No requiredMCP — uses asana-mcp-server CLI (CLI tool), not MCP server
+    integrationType: "oauth"
+  },
   notion: {
     id: "notion",
     name: "Notion",
@@ -5189,6 +5246,7 @@ var SUBAGENTS = {
       INTEGRATIONS.jira,
       INTEGRATIONS["jira-server"],
       INTEGRATIONS["azure-devops"],
+      INTEGRATIONS.asana,
       INTEGRATIONS.notion,
       INTEGRATIONS.slack
     ],
@@ -5378,38 +5436,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 +5457,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 +6675,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 +6846,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 +6910,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];