FA-23912 / Client state / Member archive

Component subscription registration: Topic recipient routing · case 02

Topic recipient routing.

Member previewVariant 2 · 3 implementations · 60 checks per implementation

Case contract

Registration handles differ from topic names. Removing a handle removes all its registrations while preserving other handles and topic reference counts; unmounted consumers receive nothing and discard buffered events. Operation topic-recipient-routing 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
topic-recipient-routing scenario 1	`["a", "b", "c"]`	`["a", "b"]`	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.