@bugzy-ai/bugzy 1.19.2 → 1.20.0

package/dist/tasks/index.js

@@ -455,7 +455,7 @@ If intent is not in the payload, detect from message patterns:
 | Condition | Intent |
 |-----------|--------|
 | Keywords: "status", "progress", "how did", "results", "how many passed" | \`status\` |
-| Keywords: "bug", "issue", "broken", "doesn't work", "failed", "error" | \`feedback\` |
+| Keywords: "bug", "issue", "broken", "doesn't work", "failed", "error", "wrong triage", "incorrect classification", "dispute", "that was wrong" | \`feedback\` |
 | Question words: "what", "which", "do we have", "is there" about tests/project | \`question\` |
 | Default (none of above) | \`feedback\` |
 
@@ -491,7 +491,26 @@ Extract the following from the message:
 - \`suggestion\`: "should", "could we", "what if", "idea"
 - \`general\`: Default for unclassified feedback
 
-### Step 2: Update Test Case Specifications
+### Step 2: Check for Dispute Intent
+
+Before processing other feedback types, check if the message is disputing a prior triage finding (e.g., "that triage was wrong", "the login timeout is actually CI flakiness not a product bug", "incorrect classification for...").
+
+**If dispute detected:**
+1. Call \`bugzy-findings list\` to retrieve recent findings
+2. Match the customer's message to a specific finding by test name, description, or ID
+3. If ambiguous (multiple possible matches), list recent findings and ask the customer to clarify which one they're disputing
+4. Once matched, call:
+   \`\`\`bash
+   bugzy-findings dispute --finding-id <matched-finding-id> --explanation "<customer's explanation>"
+   \`\`\`
+5. Confirm the dispute was recorded: "Dispute recorded for [finding title]. A triage credit has been applied and the finding is now marked as disputed. This feedback will help improve future triages."
+6. Skip the remaining feedback steps (the dispute is the action)
+
+If \`bugzy-findings\` is not available (command not found), inform the customer that dispute functionality is not available for this project and suggest contacting support.
+
+**If NOT a dispute**, continue with the standard feedback flow below.
+
+### Step 3: Update Test Case Specifications
 
 **CRITICAL**: When feedback requests changes to test behavior (e.g., "change the expected result", "update the test to check for X", "the test should verify Y instead"), you MUST update the test case markdown files to reflect the requested changes.
 
@@ -503,7 +522,7 @@ For each actionable feedback item:
 
 This step updates the **specification** (markdown test case files) only. The \`sync-automation-from-feedback\` step that follows handles syncing the **implementation** (automation code) to match.
 
-### Step 3: Acknowledge and Confirm
+### Step 4: Acknowledge and Confirm
 
 Respond confirming: feedback received, summary of what was captured, actions taken (including any test case updates), and follow-up questions if needed.
 
@@ -788,7 +807,11 @@ Use these as reference patterns for common events. The webhook routing system al
 
 **Jira Events:**
 - **Status \u2192 "Ready to Test" / "In Testing" / "Ready for QA"**: Propose \`/verify-changes\` with issue context
-- **Resolution: "Not a Bug" / "Won't Fix" / "User Error"**: Update knowledge base directly with the learning (no queue needed)
+- **Resolution: "Not a Bug" / "Won't Fix" / "User Error"**: Update knowledge base directly with the learning (no queue needed). Additionally, if the issue was linked to a triage finding (check via \`bugzy-findings list\` matching by issue tracker key), auto-dispute the finding:
+  \`\`\`bash
+  bugzy-findings dispute --finding-id <matched-finding-id> --explanation "Issue resolved as Not a Bug/Won't Fix in issue tracker"
+  \`\`\`
+  This applies a triage credit automatically when the issue tracker confirms the triage was incorrect. If \`bugzy-findings\` is not available, skip the dispute and only update the knowledge base.
 - **Bug created with relevant labels**: Propose \`/generate-test-cases\` to update related test coverage, confirm with team
 - **Backlog \u2192 To Do**: No QA action needed, log to event history only