Skip to content

fix: preserve provider operation failures (#163) - #181

Merged
atomantic merged 4 commits into
mainfrom
claim/issue-163
Aug 30, 2026
Merged

fix: preserve provider operation failures (#163)#181
atomantic merged 4 commits into
mainfrom
claim/issue-163

Conversation

@atomantic

Copy link
Copy Markdown
Owner

Summary

  • distinguish verified logged-out and empty-tree states from browser or provider scraper failures
  • return structured HTTP 503 errors with provider and operation context, including partial aggregate-session results
  • keep provider-session failures visible in the UI with browser-settings and retry remediation

Tests

  • npm test -- --run tests/unit/services/providerService.spec.ts tests/integration/api/providers.spec.ts (11 passed)
  • npm test -- --run (186 passed, 2 skipped)
  • npm run build
  • npm run check:file-sizes

Review

  • Claude local review at medium effort completed for the configured one-round cap
  • addressed both findings: aggregate result preservation and aggregate failure coverage

Closes #163

@atomantic
atomantic merged commit 96aa938 into main Aug 30, 2026
4 checks passed
@atomantic
atomantic deleted the claim/issue-163 branch August 30, 2026 23:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Preserve provider-operation failures instead of reporting empty success

1 participant