FA-33057 / Menu interactions / Member archive

Private context command appears in the persistent recent menu · case 02

Private context command appears in the persistent recent menu.

Member previewVariant 2 · 3 implementations · 7 checks per implementation

Case contract

Recent command menus key history by command and context, rank by descending last-use time with use-count tie break, and exclude retired commands from presentation.

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
private-context contract	`[{"context": "secret", "id": 2, "private": true}, {"context": "public", "id": 3, "private": false}]`	`[{"context": "public", "id": 3, "private": false}]`	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.