Story Crater BotandClaude Opus 5
058f11cf2b
Baseline for the Kong replacement on api.riotpiao.com. Brings the working tree under version control for the first time: gateway source, the task board that drives the agent runs, test fixtures, and K8s manifests. Anchor the gateway ignore rule to the repo root. Unanchored, "gateway" also matched the cmd/gateway/ source directory, so the program entrypoint was excluded from every commit. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
1.5 KiB
1.5 KiB
4.3 — RFC 9457 problem+json rejections (RED)
Phase: 4 — Limits and budgets Stage: RED
Every rejection the gateway generates itself must be a machine-readable problem document. Upstream responses are passed through untouched — this covers only errors the gateway originates.
- Every gateway-originated rejection responds with
Content-Type: application/problem+json - The body carries at minimum
type,title,status, anddetail, andstatusequals the HTTP status line typeis a stable, distinct URI per rejection reason, so a client can branch on it without parsing prosedetailis human-useful and names the offending input where one existsRetry-Afteris set whenever a retry time is knowable — queue full, budget exhausted, upstream saturatedRetry-Afteris absent when no retry will help — unknown model, malformed body, oversized body- No token, credential, header value, or request body content appears in any field
- A rejection is emitted as a structured log line carrying the same reason identifier used in
type
Tests come first and must fail because the shape does not exist yet, not because a route is missing.
Verify
curl -s -D - -o /tmp/p.json -X POST localhost:8080/v1/chat/completions \
-H 'content-type: application/json' -d '{"model":"nope"}' | grep -i content-type
# expected: application/problem+json
python3 -c "import json;d=json.load(open('/tmp/p.json'));assert{'type','title','status','detail'}<=d.keys();assert d['status']==400;print('ok')"
# expected: ok