FA-32629 / Menu interactions / Member archive
Recoverable menu command failure loses retry state · case 04
Recoverable menu command failure loses retry state.
Case contract
Menu command transactions have explicit preparation, execution, success and failure phases; close policy and duplicate suppression are separate.
Why this case matters
Cascading and context menus require coherent command and session state as content changes.
One recorded failure
Sample boundary fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| failure contract | {"error": null, "retry": false, "state": "done"} | {"error": "e4", "retry": true, "state": "failed"} | 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.
Sign in to the archive ↗