FA-7739 / Connection lifecycle / Member archive

Pool return requires complete message boundary · case 04

Pool return requires complete message boundary.

Member previewVariant 4 · 3 implementations · 4 checks per implementation

Case contract

Bounded offline decision model: pool return requires complete message boundary. Inputs are already validated protocol fields; the explicit fixtures define the supported policy, not a complete protocol implementation.

Why this case matters

This deterministic connection lifecycle model isolates the pool-return-requires-complete-message-boundary 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 1	`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.