FA-33685 / Menu interactions / Member archive

Fatal malformed menu definition is replaced with unsafe stale content · case 05

Fatal malformed menu definition is replaced with unsafe stale content.

Member previewVariant 5 · 3 implementations · 7 checks per implementation

Case contract

A failed menu provider is isolated to its owned section; fallback content and error records are distinct, and recovery clears only that provider error.

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
fatal contract	`[5]`	`[]`	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.