[GH-ISSUE #53] Correct provider-neutral analysis error classification #41

New issue

Closed

opened 2026-10-15 18:20:20 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:20:20 +00:00

Owner

Originally created by @morluto on GitHub (Jul 12, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/53

Problem

AnalysisProtocolError exposes the tag HopperProtocolError, conflating application boundary failures with Hopper transport failures and mislabeling future providers.

Outcome

Give provider-neutral failures distinct stable tags while preserving provider-specific errors inside adapters.

Scope

Define and exhaustively project analysis input/output, unavailable-capability, evidence-integrity, provider-selection, cancellation, and provider-adapter errors. Preserve safe structured fields and causes internally without exposing payloads or environments.

Acceptance criteria

AnalysisProtocolError._tag is AnalysisProtocolError.
Hopper wire failures retain Hopper-specific tags.
CLI and MCP error projections remain structured and secret-safe.
Exhaustive tests cover every error variant and cancellation-first classification.
No compatibility alias silently preserves the incorrect tag.

Dependencies

Parent: #48. Coordinate with Evidence v2 as an intentional breaking contract.

Non-goals

Telemetry redesign or provider retry policy.

Originally created by @morluto on GitHub (Jul 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/53 ## Problem `AnalysisProtocolError` exposes the tag `HopperProtocolError`, conflating application boundary failures with Hopper transport failures and mislabeling future providers. ## Outcome Give provider-neutral failures distinct stable tags while preserving provider-specific errors inside adapters. ## Scope Define and exhaustively project analysis input/output, unavailable-capability, evidence-integrity, provider-selection, cancellation, and provider-adapter errors. Preserve safe structured fields and causes internally without exposing payloads or environments. ## Acceptance criteria - `AnalysisProtocolError._tag` is `AnalysisProtocolError`. - Hopper wire failures retain Hopper-specific tags. - CLI and MCP error projections remain structured and secret-safe. - Exhaustive tests cover every error variant and cancellation-first classification. - No compatibility alias silently preserves the incorrect tag. ## Dependencies Parent: #48. Coordinate with Evidence v2 as an intentional breaking contract. ## Non-goals Telemetry redesign or provider retry policy.

bsakaguchi

2026-10-15 18:20:20 +00:00