Ragnor Comerford c745dd69ae server: emit Retry-After header on 429 / 503 responses ... Closes the doc-vs-code gap at api.rs:343 and lib.rs:344-355: the documentation claims `Retry-After` is set on TooManyRequests / ServiceUnavailable responses, but `IntoResponse for ApiError` emitted only `(StatusCode, Json(ErrorOutput))` — no header. Wires a constant `RETRY_AFTER_SECONDS = "60"` for both 429 and 503 codes. Plumbing per-RejectReason durations through is a follow-up; the admission rejects we surface today recover bounded by request handler duration rather than calendar wait, so a constant suffices. Pinned by `ingest_per_actor_admission_cap_returns_429`. Test now fully green: 1+ of 8 concurrent /ingest under cap=1 receives 429 with Retry-After: 60. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-08 16:58:47 +02:00
..
omnigraph	engine: drop swap-restore in branch_create_from; operate on local coord	2026-05-08 16:48:17 +02:00
omnigraph-cli	mr-686: bundle PR 0/1a/1b foundation + PR 2 catalog/schema_source ArcSwap	2026-05-07 16:22:38 +02:00
omnigraph-compiler	release: bump version to 0.4.1	2026-05-02 23:20:50 +02:00
omnigraph-server	server: emit Retry-After header on 429 / 503 responses	2026-05-08 16:58:47 +02:00