Fork card: fork_too_large (422) for a list whose first entry, or a read whose entry, is past the reply cap #88
2026-11-11
fork-card.md: say the read form of fork_too_large is a target; Huginn answers ResponseTooLarge today
All checks were successful
CultMesh QUIC native / Build win32-x64 (pull_request) Has been skipped
CultMesh QUIC native / Build linux-x64 (pull_request) Has been skipped
CultMesh QUIC native / Release native binaries (pull_request) Has been skipped
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Successful in 17m20s
CultMesh QUIC native / Verify committed binaries match SHA256SUMS (pull_request) Successful in 41s
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Fork card: fork_too_large also refuses a read past the reply cap; door-fault bytes, 422 asserted in both judges
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Fork card: request_id_conflict is answer-only; a door conflict on read or list is 503 unavailable
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Fork card: short list pages and fork_too_large (422) for a first entry past the response budget
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>