FAILURE MAP
← Case archive

FA-33498 / Menu interactions / Member archive

Simultaneous menu dismissal reasons use arrival order instead of policy · case 03

Simultaneous menu dismissal reasons use arrival order instead of policy.

Member previewVariant 3 · 3 implementations · 7 checks per implementation

Case contract

Menu dismissal reasons map to explicit close scopes; command completion, owner removal and outside dismissal do not share a universal policy.

Why this case matters

Cascading and context menus require coherent command and session state as content changes.

One recorded failure

Sample boundary fixture

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

Boundary fixtureActualExpectedOutcome
reason-priority contract"outside""owner-removed"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.

Sign in to the archive ↗