Skip to content

Commit d7096f8

Browse files
committed
docs(devlog): record the trailer-status mapping as closed
020 listed the Connect trailer mapping as the deferred half of the cloud-direct work. It landed, along with the 501 retryability fix the review caught, so the doc records the outcome and the two accepted residuals.
1 parent 0e058cd commit d7096f8

1 file changed

Lines changed: 15 additions & 0 deletions

File tree

‎devlog/_plan/260912_devin_hardening/020_cloud_direct_hardening.md‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -76,3 +76,18 @@ already knows, with status 499.
7676
## Verification
7777

7878
bun test tests/providers/devin-adapter.test.ts tests/providers/devin-hardening.test.ts
79+
80+
## 5. A Connect trailer carries no status — closed
81+
82+
Landed in `connectTrailerHttpStatus`. The three EOS trailer throw sites now pass a status,
83+
so a cap delivered as `permission_denied` with "your limit will reset" reads as 429 rather
84+
than 403, an `unauthenticated` trailer reaches the auth path, and an unrecognised code still
85+
falls back to message inference. `unimplemented` maps to 501 and is explicitly non-retryable,
86+
because the blanket 5xx rule was telling clients to retry a call the service does not
87+
implement.
88+
89+
Accepted residuals: `internal`, `unknown` and `data_loss` map to 502 rather than Connect's
90+
500 — both are transient here and 502 is what this adapter already reported — and a genuine
91+
ACL denial whose text happens to contain the words "rate limit" would be read as a cap. The
92+
regex reads the raw trailer message, never the enriched text, so the tool-description
93+
blocklist wrapper cannot trip it.

0 commit comments

Comments
 (0)