FA-4532 / Listener lifecycle / Member archive

Listener callback registration · case 02

The operation returns a result or retained state that violates this contract: Listeners have identity, event name, once flag, and registration order. Dispatch uses a snapshot; listener actions remove another listener or add a new one. Return callback identities in invocation order. A listener installed by a callback starts participating on the next dispatch and uses the action-specified event name.

Member previewVariant 2 · 3 implementations · 5 checks per implementation

Case scope

A controlled failure with recorded boundary checks.

Why this case matters

A controlled local-runtime regression for collection APIs, language semantics, or ownership wrappers. Fixtures include boundary and interaction cases.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
callback replaces existing target event	`["a", ["b"]]`	`["a", "b", ["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.