• alfadb's avatar
    fix(ops): validate error_type against known whitelist before classification · ce006a7a
    alfadb authored
    
    
    Upstream proxies (account 4, 112) return `"<nil>"` as the error.type in
    their JSON responses — a Go fmt.Sprintf("%v", nil) artifact. Since
    `normalizeOpsErrorType` only checked for empty string, the literal
    "<nil>" passed through and poisoned the entire classification chain:
    error_phase was misclassified as "internal" (instead of "request"),
    severity was inflated to P2, and the stored error_type was meaningless.
    
    Add `isKnownOpsErrorType` whitelist so any unrecognised type falls
    through to the code-based or default "api_error" classification.
    Co-Authored-By: default avatarClaude Opus 4.6 <noreply@anthropic.com>
    ce006a7a
ops_error_logger.go 30.1 KB