FA-7768 / Connection lifecycle / Member archive

Connection attempt timeout is separate from read timeout · case 03

Connection attempt timeout is separate from read timeout.

Member previewVariant 3 · 3 implementations · 4 checks per implementation

Case contract

Given phase, connect_timeout, read_timeout, remaining, connection attempt timeout is separate from read timeout. Return the protocol decision or transformed value; fields are validated and fixtures state boundary outcomes.

Why this case matters

This deterministic connection lifecycle model isolates the connection-attempt-timeout-is-separate-from-read-timeout 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	`30`	`2`	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.