FA-33578 / Menu interactions / Member archive

Secondary split-menu zone invokes the default instead of only showing alternatives · case 03

Secondary split-menu zone invokes the default instead of only showing alternatives.

Member previewVariant 3 · 3 implementations · 8 checks per implementation

Case contract

Split menu owners have separate primary command and secondary submenu zones. Their default command is explicit, direct and independently available; the owner label is stable.

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 fixture	Actual	Expected	Outcome
secondary contract	`{"command": "run3", "open": true}`	`{"command": null, "open": true}`	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.