feat: add resilient error handling to analyze_issue_with_seer tool

[dcramer]

• Implement retry logic with exponential backoff for API calls
• Add proper error recovery during polling with up to 3 consecutive failures allowed
• Move retryWithBackoff utility to internal/fetch-utils for broader reuse
• Add comprehensive test coverage for error scenarios including network failures, 500 errors, and timeouts
• Prevent infinite polling by enforcing existing 5-minute timeout and error limits

This ensures the Seer analysis tool gracefully handles transient API failures and network issues without getting stuck in infinite loops.

🤖 Generated with Claude Code

[codecov]

Codecov Report

Attention: Patch coverage is 92.00000% with 8 lines in your changes missing coverage. Please review.

Project coverage is 62.40%. Comparing base (5cf76f4) to head (0d66255).
Report is 1 commits behind head on main.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
...es/mcp-server/src/tools/analyze-issue-with-seer.ts	88.88%	8 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #368      +/-   ##
==========================================
+ Coverage   60.19%   62.40%   +2.20%     
==========================================
  Files          77       77              
  Lines        6730     6817      +87     
  Branches      539      598      +59     
==========================================
+ Hits         4051     4254     +203     
+ Misses       2679     2563     -116     

Flag	Coverage Δ
unittests	62.40% <92.00%> (+2.20%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[cursor]

Bug: API Autofix Startup Fails Without Retry

The startAutofix API call lacks retryWithBackoff logic, unlike the getAutofixState calls in the same function. This inconsistency causes immediate failure on transient network errors or 5xx responses during analysis startup, while status polling gracefully handles such errors with retries.

packages/mcp-server/src/tools/analyze-issue-with-seer.ts#L118-L123

sentry-mcp/packages/mcp-server/src/tools/analyze-issue-with-seer.ts

Lines 118 to 123 in 0d66255

	output += `Starting new analysis...\n\n`;
	const startResult = await apiService.startAutofix({
	organizationSlug: orgSlug,
	issueId: parsedIssueId,
	instruction: params.instruction,
	});

Fix in Cursor • Fix in Web

---

Was this report helpful? Give feedback by reacting with 👍 or 👎