FAILURE MAP
← Case archive

FA-32619 / Menu interactions / Member archive

A prepared menu transaction launches twice while pending · case 04

A prepared menu transaction launches twice while pending.

Member previewVariant 4 · 3 implementations · 7 checks per implementation

Case contract

Menu command transactions have explicit preparation, execution, success and failure phases; close policy and duplicate suppression are separate.

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
pending contracttruefalseFailed

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 ↗