FA-33832 / Menu interactions / Member archive

Menu usage event leaks captured command arguments · case 02

Menu usage event leaks captured command arguments.

Member previewVariant 2 · 3 implementations · 7 checks per implementation

Case contract

Menu metrics distinguish impressions, command invocation and completed execution; root sessions and menu paths remain separate dimensions and sensitive arguments are excluded.

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
arguments contract	`{"arguments": {"doc": 2}, "command": "copy", "path": ["root"], "target": "doc"}`	`{"command": "copy", "path": ["root"]}`	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.