MrHuangJser 1b7447b682 feat(cursor): implement StatusError for conductor cooldown integration ...

Cursor executor errors were plain fmt.Errorf — the conductor couldn't
extract HTTP status codes, so exhausted accounts never entered cooldown.

Changes:
- Add ConnectError struct to proto/connect.go: ParseConnectEndStream now
  returns *ConnectError with Code/Message fields for precise matching
- Add cursorStatusErr implementing StatusError + RetryAfter interfaces
- Add classifyCursorError() with two-layer classification:
  Layer 1: exact match on ConnectError.Code (gRPC standard codes)
    resource_exhausted → 429, unauthenticated → 401,
    permission_denied → 403, unavailable → 503, internal → 500
  Layer 2: fuzzy string match for H2 errors (RST_STREAM → 502)
- Log all ConnectError code/message pairs for observing real server
  error codes (we have no samples yet)
- Wrap Execute and ExecuteStream error returns with classifyCursorError

Now the conductor properly marks Cursor auths as cooldown on quota errors,
enabling exponential backoff and round-robin failover.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-27 11:42:22 +08:00

..

connect.go

feat(cursor): implement StatusError for conductor cooldown integration

2026-03-27 11:42:22 +08:00

decode.go

feat(cursor): conversation checkpoint + session_id for multi-turn context

2026-03-26 10:51:47 +08:00

descriptor.go

feat: stash code

2026-03-25 10:14:14 +08:00

encode.go

feat(cursor): conversation checkpoint + session_id for multi-turn context

2026-03-26 10:51:47 +08:00

fieldnumbers.go

feat: stash code

2026-03-25 10:14:14 +08:00

h2stream.go

feat(cursor): auto-migrate sessions to healthy account on quota exhaustion

2026-03-27 10:50:32 +08:00