FA-24215 / Client state / Member archive

Client offline mutation outbox: Effective backlog · case 05

Effective backlog.

Member previewVariant 5 · 3 implementations · 60 checks per implementation

Case contract

The client outbox is an ordered UI mutation log; commands use identity, not payload truthiness. Cancellation/acknowledgment remove only matching commands, offline mode retains unsent work, and a zero send budget sends nothing. Operation effective-backlog 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
effective-backlog scenario 1	`3`	`1`	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.