t2-p3-06draft4–6h
Observability
requires: t2-p3-05
Spec
Structured logging with request-ID propagation, plus basic per-endpoint request count and latency metrics exportable to a dashboard.
Why this matters
A request ID is what turns twelve unrelated log lines into one traceable story. Without it, debugging a concurrent system means guessing which lines belong together.
Verify
No result yet. Run `learn verify t2-p3-06` locally, or push to trigger CI.
contract
unrun