FA-23799 / Client state / Member archive

Client route-state projection: State cache key · case 04

State cache key.

Member previewVariant 4 · 3 implementations · 60 checks per implementation

Case contract

This route-state adapter models already-decoded query pairs. Repeated pairs and insertion order remain significant, first occurrence is used by single-value readers, explicit empty values override defaults, and fragment absence differs from empty. Operation state-cache-key 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
state-cache-key scenario 1	`"/a/4"`	`["/a/4", [["q", "a"], ["tag", "x"], ["tag", "y"]]]`	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.