FA-24609 / Client state / Member archive

Client worker task handoff: Cancelled job pruning · case 04

Cancelled job pruning.

Member previewVariant 4 · 3 implementations · 60 checks per implementation

Case contract

A UI worker client binds replies to both a pending job ID and worker instance. Transfer detaches only listed buffers from the main thread, unknown replies settle nothing, and unmount rejects every still-pending job. Operation cancelled-job-pruning 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
cancelled-job-pruning scenario 4	`[["a", 2], ["b", 3]]`	`[["b", 3]]`	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.