@bugzy-ai/bugzy 1.9.3 → 1.9.5

package/dist/index.cjs

@@ -83,6 +83,7 @@ var MCP_SERVERS = {
         // Bot credentials (platform-level, from Bugzy's Azure Bot registration)
         TEAMS_BOT_APP_ID: "${TEAMS_BOT_APP_ID}",
         TEAMS_BOT_APP_PASSWORD: "${TEAMS_BOT_APP_PASSWORD}",
+        TEAMS_BOT_TENANT_ID: "${TEAMS_BOT_TENANT_ID}",
         // Conversation context (per-project, from stored conversation reference)
         TEAMS_SERVICE_URL: "${TEAMS_SERVICE_URL}",
         TEAMS_CONVERSATION_ID: "${TEAMS_CONVERSATION_ID}"
@@ -339,7 +340,9 @@ 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: Knowledge Base Read (library)
+    // Step 4: Load Project Context (library)
+    "load-project-context",
+    // Step 5: Knowledge Base Read (library)
     "read-knowledge-base",
     // Step 5: Gather Context (inline)
     {
@@ -638,10 +641,10 @@ var generateTestPlanTask = {
       title: "Arguments",
       content: `Product description: $ARGUMENTS`
     },
-    // Step 4: Knowledge Base Read (library)
-    "read-knowledge-base",
-    // Step 5: Load Project Context (library)
+    // Step 4: Load Project Context (library)
     "load-project-context",
+    // Step 5: Knowledge Base Read (library)
+    "read-knowledge-base",
     // Step 6: Process Description (inline)
     {
       inline: true,
@@ -863,7 +866,9 @@ Process team responses from Slack threads and handle multi-turn conversations wi
       title: "Arguments",
       content: `Team message/thread context: $ARGUMENTS`
     },
-    // Step 4: Knowledge Base Read (library)
+    // Step 4: Load Project Context (library)
+    "load-project-context",
+    // Step 5: Knowledge Base Read (library)
     "read-knowledge-base",
     // Step 5: Detect Intent (inline - task-specific)
     {
@@ -1002,7 +1007,9 @@ Process various types of events using intelligent pattern matching and historica
       title: "Arguments",
       content: `Arguments: $ARGUMENTS`
     },
-    // Step 4: Knowledge Base Read (library)
+    // Step 4: Load Project Context (library)
+    "load-project-context",
+    // Step 5: Knowledge Base Read (library)
     "read-knowledge-base",
     // Step 5: Understand Event Context (inline)
     {
@@ -1434,7 +1441,9 @@ Extract the following from arguments:
   - Specific file: "tests/specs/login.spec.ts"
   - All tests: "all" or "" \u2192 runs entire test suite`
     },
-    // Step 4: Knowledge Base Read (library)
+    // 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",
@@ -1589,7 +1598,9 @@ This task performs comprehensive change verification with:
 
 The input format determines the trigger source and context extraction strategy.`
     },
-    // Step 4: Knowledge Base Read (library)
+    // Step 4: Load Project Context (library)
+    "load-project-context",
+    // Step 5: Knowledge Base Read (library)
     "read-knowledge-base",
     // Step 5: Detect Trigger Source (inline)
     {
@@ -2082,6 +2093,7 @@ 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",
     // Phase 2: Exploration Protocol
     "exploration-protocol",
@@ -2148,8 +2160,8 @@ var exploreApplicationTask = {
 - **system**: target system (optional for multi-system setups)`
     },
     // Setup
-    "read-knowledge-base",
     "load-project-context",
+    "read-knowledge-base",
     // Exploration Protocol (adaptive depth)
     "exploration-protocol",
     // Execute
@@ -6005,42 +6017,6 @@ Test Strategy: [exists/missing]
   tags: ["setup", "context"]
 };
 
-// src/tasks/steps/setup/check-existing-artifacts.ts
-var checkExistingArtifactsStep = {
-  id: "check-existing-artifacts",
-  title: "Assess Existing Artifacts",
-  category: "setup",
-  content: `## Assess Existing Artifacts
-
-Before proceeding, check what already exists to determine which phases to skip.
-
-**1. Check Project Context**
-- Read \`.bugzy/runtime/project-context.md\` if it exists
-- Check if it contains information relevant to: $ARGUMENTS
-- **Decision**: If project context exists and covers the focus area -> Skip exploration
-
-**2. Check Test Plan**
-- Read \`test-plan.md\` if it exists
-- Check if it contains features related to: $ARGUMENTS
-- **Decision**: If test plan exists and covers the focus area -> Skip test plan generation
-
-**3. Check Existing Test Cases**
-- List files in \`./test-cases/\` for tests related to focus area
-- List files in \`./tests/specs/\` for automated tests
-- **Decision**: If test cases already exist for the focus area -> Skip to verification only
-
-**4. Document Assessment**
-Create a brief assessment summary:
-\`\`\`
-Assessment for: $ARGUMENTS
-- Project context: [exists/missing] - [covers focus area: yes/no]
-- Test plan: [exists/missing] - [covers focus area: yes/no]
-- Test cases: [count] existing for focus area
-- Phases to run: [list phases]
-\`\`\``,
-  tags: ["setup", "assessment"]
-};
-
 // src/tasks/steps/setup/security-notice.ts
 var securityNoticeStep = {
   id: "security-notice",
@@ -7304,7 +7280,6 @@ var STEP_LIBRARY = {
   "read-knowledge-base": readKnowledgeBaseStep,
   "read-test-strategy": readTestStrategyStep,
   "load-project-context": loadProjectContextStep,
-  "check-existing-artifacts": checkExistingArtifactsStep,
   // Exploration
   "exploration-protocol": explorationProtocolStep,
   // Clarification