FA-33822 / Menu interactions / Member archive

Menu usage metrics merge repeated command labels from different branches · case 02

Menu usage metrics merge repeated command labels from different branches.

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
path-dimension contract	`"2"`	`"root/tools/2"`	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.