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.4 KiB
1.4 KiB
1.2 — Streaming passthrough (RED)
Phase: 1 — Proxy core Stage: RED Depends on: 1.1
- An SSE response from an upstream reaches the client unbuffered: each
data:event is readable by the client before the upstream has sent the next one - A chunked response reaches the client chunk by chunk, not accumulated and flushed at completion
- Response headers reach the client before the first body byte, not after
Content-Type: text/event-streamand the upstream'sCache-ControlandConnectionsemantics survive the proxy- No response body is written to memory or disk in full before forwarding
- The terminating
data: [DONE]sentinel and the final zero-length chunk pass through - A test asserts wall-clock ordering: the Nth event is observed at the client before the upstream emits the N+1th
The whole product is token streaming. If the gateway buffers, a caller waits minutes
for a response that should have started in seconds, and the user-visible behaviour of
the model API regresses versus Kong. nginx in front is already configured with
proxy-buffering: off; the gateway must not reintroduce buffering behind it.
Verify
go test ./internal/proxy/... -run TestSSEUnbuffered -v
# expected: passes — client observes each of 5 stub-emitted SSE events with the
# upstream still open, and total observed inter-event gaps match the stub's emit delays