FAILURE MAP
← Case archive

FA-24288 / Client state / Member archive

Local upload task presentation: Terminal task retention · case 03

Terminal task retention.

Member previewVariant 3 · 3 implementations · 80 checks per implementation

Case contract

This local upload view tracks parts and blob preview ownership, not a wire protocol. Accepted parts alone advance durable progress; cancellation aborts unaccepted sends; zero-byte parts still require acknowledgment; detached previews are released. Operation terminal-task-retention 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 fixtureActualExpectedOutcome
background upload survives detached preview: terminal-task-retentionfalsetrueFailed

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.

Sign in to the archive ↗