Commit 34a76c4
docs(protocol): name the 429 backoff member what the runtime actually emits (#16938)
`content/docs/protocol/kernel/error-handling.mdx` taught `details.retry_after`
on three error envelopes and instructed clients to read
`data.error.details.retry_after`. No producer emits that member: both 429
emitters build `details: { retryAfterSeconds, resetAt }`
(`packages/runtime/src/endpoint-policy.ts`,
`packages/runtime/src/security/inbound-rate-limit.ts`), and two tests pin the
spelling. A client written from this page reads `undefined` on every real 429
and silently falls back to its own backoff against a service that just asked
it to wait.
Only `details`-bag members move. The `RetryStrategy` enum value `retry_after`
is a different, correct use of the same token and is untouched in all seven of
its sites (`content/docs/api/error-catalog.mdx` x4,
`content/docs/references/api/errors.mdx` x3).
Claude-Session: https://claude.ai/code/session_016N6xmWt5hYm94ffVEwGH8x
Co-authored-by: Claude <noreply@anthropic.com>1 parent 859ded3 commit 34a76c4
1 file changed
Lines changed: 4 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
420 | 420 | | |
421 | 421 | | |
422 | 422 | | |
423 | | - | |
| 423 | + | |
424 | 424 | | |
425 | 425 | | |
426 | 426 | | |
| |||
528 | 528 | | |
529 | 529 | | |
530 | 530 | | |
531 | | - | |
| 531 | + | |
532 | 532 | | |
533 | 533 | | |
534 | 534 | | |
| |||
652 | 652 | | |
653 | 653 | | |
654 | 654 | | |
655 | | - | |
| 655 | + | |
656 | 656 | | |
657 | 657 | | |
658 | 658 | | |
| |||
736 | 736 | | |
737 | 737 | | |
738 | 738 | | |
739 | | - | |
| 739 | + | |
740 | 740 | | |
741 | 741 | | |
742 | 742 | | |
| |||
0 commit comments