FA-24513 / Client state / Member archive

Nested client render failure boundaries: Capture path inside out · case 03

Capture path inside out.

Member previewVariant 3 · 3 implementations · 70 checks per implementation

Case contract

This bounded render boundary model walks ancestors inside-out, excludes a failing boundary from catching itself, and catches render failures only. Reset keys compare shape and scalar types; event and asynchronous failures propagate to their callers. Operation capture-path-inside-out 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
capture-path-inside-out scenario 5	`["outer", "inner"]`	`["inner", "outer"]`	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.