89bf7657a2
Co-authored-by: nova28 <17953305+nova28@users.noreply.github.com> Co-authored-by: Carlos Florencio <carlosmflorencio@gmail.com>
2.0 KiB
2.0 KiB
id, title, status, wave, depends_on, plan, requirements, acceptance_criteria, system_design
| id | title | status | wave | depends_on | plan | requirements | acceptance_criteria | system_design | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 01-classify-proxy-gateway-failures | Classify proxy gateway failures | done | 1 | plan.md |
|
|
|
Task 01: Classify Proxy Gateway Failures
Summary
Map structured and exact ACP-wrapped upstream gateway failures to the shared transient provider-unavailable code. Map the explicit proxy all-credentials-refused envelope to the existing hard missing-credentials code.
Acceptance
- Exact 500, 502, and 504 gateway evidence is high-confidence transient provider unavailability and permits the existing dynamic policy evaluator.
- The explicit proxy credential-refusal envelope is a high-confidence hard credential failure.
- Generic prose and unrelated status text remain unclassified.
Verification
cd apps/backend && go test -tags fts5 ./internal/agent/runtime/routingerr
Files likely touched
apps/backend/internal/agent/runtime/routingerr/{routingerr,runtime_rules,rules}.goapps/backend/internal/agent/runtime/routingerr/*_test.go
Risks
Broad text matching could authorize replay after model-authored or local failure text. Rules must require the structured status or exact ACP/proxy envelope.
Results
- Structured HTTP 500, 502, and 504 now classify as transient
provider_unavailableerrors. - Exact ACP
API Error500/502/504 gateway envelopes classify as the same high-confidence transient failure. Generic server-error prose remains unclassified. - The explicit
proxy_errorall-credentials-refused envelope classifies as hardmissing_credentials. - Verification passed:
cd apps/backend && go test -tags fts5 ./internal/agent/runtime/routingerr.