beads/internal/httpapi/apigen
CI Bot c2a9522016 feat(httpapi): require Problem.request_id and declare RFC 9457 type
request_id was optional in the document and unconditional on the wire. Every
non-2xx flows through the fail path, which mints the id in the outermost
middleware — the panic path included — and 5xx `detail` is a fixed static
string by design, so request_id is the only actionable member of a 5xx. The
schema was the only place not saying so.

The description now splits contract from implementation note, so a
multi-instance deployment can satisfy the contract with an edge trace id
instead of this server's per-process one.

Regen consequence, expected: apigen.Problem.RequestId is a non-pointer string,
so WithRequestID loses its pointer assignment and its empty-string guard. An
id this server failed to mint now travels as an empty string rather than as a
missing required member.

`type` is declared but never emitted, so `about:blank` stays implied here. It
is counter-specified rather than left open: one stable URI per status+code
pair, never a dispatch key, never subdividing a code — a deployment that hosts
problem documentation may supply it without forking error identity away from
`code`. It stays out of `required`; a profile requiring it is a legal
tightening. RFC `instance` stays undeclared — request_id is the occurrence
identifier.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-01 15:38:01 +00:00
..
doc.go feat(httpapi): OpenAPI v0 spec, types-only codegen, and the drift gates (bd-ilb) 2026-07-31 08:37:34 +00:00
types.gen.go feat(httpapi): require Problem.request_id and declare RFC 9457 type 2026-08-01 15:38:01 +00:00