FA-7599 / WebSocket and browser transport policies / Member archive

Websocket control frames must be final and at most 125 bytes · case 04

Websocket control frames must be final and at most 125 bytes.

Member previewVariant 4 · 3 implementations · 4 checks per implementation

Case contract

Bounded offline decision model: websocket control frames must be final and at most 125 bytes. Inputs are already validated protocol fields; the explicit fixtures define the supported policy, not a complete protocol implementation.

Why this case matters

This deterministic websocket and browser transport policies model isolates the websocket-control-frames-must-be-final-and-at-most-125-bytes policy at a network component boundary.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
fixture 2	`true`	`false`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.