FA-24639 / Client state / Member archive

Multiple client roots and portals: Root disposal isolation · case 04

Root disposal isolation.

Member previewVariant 4 · 3 implementations · 60 checks per implementation

Case contract

Portal event ownership follows the logical root rather than its physical host. Root disposal removes only that root and its owned portals; event paths are deduplicated in order and missing containers do not create roots implicitly. Operation root-disposal-isolation 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
root-disposal-isolation scenario 1	`{}`	`{"r1": ["a", "b"], "r2": ["c"]}`	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.