FA-23500 / Client state / Member archive

Route loader ownership: Unmount write suppression · case 05

Unmount write suppression.

Member previewVariant 5 · 3 implementations · 60 checks per implementation

Case contract

A mounted route owns only its current route key and request generation. Empty mappings are successful data; null is no data; even an empty error string is an error. Old requests cannot settle current loading. Operation unmount-write-suppression 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
unmount-write-suppression scenario 4	`{"v": 5}`	`{}`	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.