FAILURE MAP
← Case archive

FA-24803 / Client state / Member archive

Navigating between routes retains resource tags from the abandoned route · case 03

Navigating between routes retains resource tags from the abandoned route.

Member previewVariant 3 · 3 implementations · 6 checks per implementation

Case scope

Navigating between routes retains resource tags from the abandoned route.

Why this case matters

A bounded offline client-state transition with explicit lifecycle inputs.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixtureActualExpectedOutcome
remove outgoing retain side route{"a": ["x"], "b": ["y"], "side": ["s"]}{"b": ["y"], "side": ["s"]}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.

Sign in to the archive ↗