FA-24165 / Client state / Member archive

Visibility-aware client polling: Remaining delay clamp · case 05

Remaining delay clamp.

Member previewVariant 5 · 3 implementations · 60 checks per implementation

Case contract

Only one poll may be in flight. Foreground polling pauses offline or hidden; a background policy permits hidden work. Missed ticks coalesce into one catch-up request and scheduling restarts relative to the current clock. Operation remaining-delay-clamp has the six explicit input/output oracles below.

Why this case matters

An offline client lifecycle model that isolates a state-management defect without DOM rendering or network services.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
remaining-delay-clamp scenario 2	`-4`	`0`	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.