fix: raw hold-cap 128x, full monitor-mode output scans, and a usage event for every request - #1238

Merged

jarvis9443 merged 8 commits into

mainfrom

fix/hold-cap-monitor-scan-rerank-usage

Sep 25, 2026

Commits on Sep 25, 2026

fix(guardrails): raise the raw hold-cap factor from 64 to 128
jarvis9443
committed
8317bf7
fix(guardrails): monitor-only output chains scan all of the generated text
jarvis9443
committed
e1e1a33
docs(guardrails): max_buffer_bytes also caps chat streaming tool-call arguments
jarvis9443
committed
8403bb9
fix(usage): every model-serving request emits its UsageEvent
jarvis9443
committed
3910aa0
docs(usage): drop comments describing the old 501 emission gate
jarvis9443
committed
b9e11f2
fix(mcp): record a tool call whose upstream result cannot be read back
jarvis9443
committed
4f1c5ce
test(e2e): size the unterminated-tail fixture past the 128x raw bound
jarvis9443
committed
a729bc2
fix(videos): the route's own 501 exports no upstream span
jarvis9443
committed
ab36d6d