START HERE — Rate-Limit Response & Retry-After Interpreter

PRESERVE-WHAT-WORKS — PRESERVE FIRST

Bounded change: add one interpretation call at the existing response-error decision boundary. Untouched: design, layout, navigation, routes, branding, content, responsive/accessibility behavior, SEO, analytics, auth, checkout, integrations, databases, API contracts, transport, credentials, quotas, counters, and unrelated code.

1. Confirm provider documentation and request replay safety.
2. Create a checkpoint or reversible commit.
3. Copy src/index.js and optionally src/index.d.ts.
4. Map explicit outcomes into existing host controls.
5. Run npm test plus existing request, error, auth, analytics, idempotency, responsive, and accessibility regressions.

Compatibility: Node 18+ ESM or a modern bundler. Failure/recovery: typed validation errors occur before side effects; retain the existing error path. Rollback: remove the import/call and restore the checkpoint. Unverified: real provider semantics, clock accuracy, distributed coordination, replay safety, UI announcements, and customer-environment behavior. Publish next: deploy only after targeted and regression tests pass.

PRESERVATION CONFLICT / REVIEW REQUIRED: stop if integration changes contracts, retries an unproven mutation, replaces transport, silently shortens a wait, or requires unrelated redesign/rearchitecture. Use the existing error branch as the smallest alternative.