FA-24407 / Client state / Member archive

Client attachment resource ownership: Submitted attachment retention · case 02

Submitted attachment retention.

Member previewVariant 2 · 3 implementations · 60 checks per implementation

Case contract

Attachment identity differs from file name and byte count. Zero-byte and same-name files remain separate. Preview URLs and selected IDs are cleaned by attachment identity; submitted files and read-only commands have separate lifetimes. Operation submitted-attachment-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 fixture	Actual	Expected	Outcome
submitted-attachment-retention scenario 1	`[["a", "one", 2], ["b", "two", 2]]`	`[["a", "one", 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.