FA-33117 / Menu interactions / Member archive

Provider error status row is treated as a menu command · case 02

Provider error status row is treated as a menu command.

Member previewVariant 2 · 3 implementations · 8 checks per implementation

Case contract

Lazy submenu presentation distinguishes first load, refresh, stale content, retryable failure and empty success without disguising provider state as commands.

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
status-actionable contract	`[{"id": 2, "kind": "error"}, {"id": 3, "kind": "command"}]`	`[{"id": 3, "kind": "command"}]`	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.