FA-33501 / Menu interactions / Open access
Menu ownership transfer cancels an intentionally retained command · case 01
Menu ownership transfer cancels an intentionally retained command.
ROOT CAUSE
The menu-dismissal-policy model applies `[]` at its pending-command operation instead of the stipulated transformation.
THE FAILURE
The menu-dismissal-policy model applies `[]` at its pending-command operation instead of the stipulated transformation.
Unsuccessful approach: The attempted repair `p['pending'] if p['reason']=='command' else []` still violates the pending-command oracle.
Case contract
Menu dismissal reasons map to explicit close scopes; command completion, owner removal and outside dismissal do not share a universal policy.
Why this case matters
Cascading and context menus require coherent command and session state as content changes.
1 / The failure
Exit 1"""Failure Map reference implementation. Python standard library only."""
import json
import math
import unicodedata
N = 1
observations = []
def solve(action, p):
if action == 'leaf-scope':
return p['chain'][:p['depth']] if p['scope']=='branch' else []
if action == 'veto':
return p['requested'] and not p['vetoed']
if action == 'mandatory-teardown':
return p['owner_removed'] or not p['vetoed']
if action == 'reason-priority':
return next(x for x in ['owner-removed','command','outside'] if x in p)
if action == 'pending-command':
return []
if action == 'nested-boundary':
return p['chain'][:p['boundary']]
return {'error': 'unsupported menu operation'}
def check(label, actual, expected):
observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('leaf-scope contract', solve('leaf-scope', {'chain':['root','sub',str(N)],'depth':1,'scope':'branch'}), ['root'])
check('veto contract', solve('veto', {'requested':True,'vetoed':True,'owner':N}), False)
check('mandatory-teardown contract', solve('mandatory-teardown', {'owner_removed':True,'vetoed':True,'id':N}), True)
check('reason-priority contract', solve('reason-priority', ['outside','owner-removed','command']), 'owner-removed')
check('pending-command contract', solve('pending-command', {'pending':[N],'reason':'transfer'}), [N])
check('nested-boundary contract', solve('nested-boundary', {'chain':['outer','local','child'+str(N)],'boundary':1}), ['outer'])
check('unknown operation', solve('unknown', {}), {'error': 'unsupported menu operation'})
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| leaf-scope contract | ['root'] | ['root'] | Passed |
| veto contract | False | False | Passed |
| mandatory-teardown contract | True | True | Passed |
| reason-priority contract | owner-removed | owner-removed | Passed |
| pending-command contract | [] | [1] | Failed |
| nested-boundary contract | ['outer'] | ['outer'] | Passed |
| unknown operation | {'error': 'unsupported menu operation'} | {'error': 'unsupported menu operation'} | Passed |
SHA-256 / 1a446d3883d9fe5d94fac30b593fb5a52c19dca6832aae5c80677c4f6972c279
2 / The unsuccessful fix
Exit 1"""Failure Map reference implementation. Python standard library only."""
import json
import math
import unicodedata
N = 1
observations = []
def solve(action, p):
if action == 'leaf-scope':
return p['chain'][:p['depth']] if p['scope']=='branch' else []
if action == 'veto':
return p['requested'] and not p['vetoed']
if action == 'mandatory-teardown':
return p['owner_removed'] or not p['vetoed']
if action == 'reason-priority':
return next(x for x in ['owner-removed','command','outside'] if x in p)
if action == 'pending-command':
return p['pending'] if p['reason']=='command' else []
if action == 'nested-boundary':
return p['chain'][:p['boundary']]
return {'error': 'unsupported menu operation'}
def check(label, actual, expected):
observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('leaf-scope contract', solve('leaf-scope', {'chain':['root','sub',str(N)],'depth':1,'scope':'branch'}), ['root'])
check('veto contract', solve('veto', {'requested':True,'vetoed':True,'owner':N}), False)
check('mandatory-teardown contract', solve('mandatory-teardown', {'owner_removed':True,'vetoed':True,'id':N}), True)
check('reason-priority contract', solve('reason-priority', ['outside','owner-removed','command']), 'owner-removed')
check('pending-command contract', solve('pending-command', {'pending':[N],'reason':'transfer'}), [N])
check('nested-boundary contract', solve('nested-boundary', {'chain':['outer','local','child'+str(N)],'boundary':1}), ['outer'])
check('unknown operation', solve('unknown', {}), {'error': 'unsupported menu operation'})
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| leaf-scope contract | ['root'] | ['root'] | Passed |
| veto contract | False | False | Passed |
| mandatory-teardown contract | True | True | Passed |
| reason-priority contract | owner-removed | owner-removed | Passed |
| pending-command contract | [] | [1] | Failed |
| nested-boundary contract | ['outer'] | ['outer'] | Passed |
| unknown operation | {'error': 'unsupported menu operation'} | {'error': 'unsupported menu operation'} | Passed |
SHA-256 / b57fcbc78d60a67fc3d2c9157bb008322007ad6843e5038cebc386f432ef3cc0
HELD IN THE MEMBER ARCHIVE
The verified repair and its recorded checks are member-only.
This mechanism has 7 recorded checks per implementation. The open-access tier publishes the failure and the unsuccessful fix; the repaired source that passes every check, and the observations that prove it, are available to members.
Every case sharing this mechanism uses the same contract and the same repair, so this one record is held back for all of them.
Member access is invitation-based. Sign in with your invited account to inspect the repair.
Sign in to the archive ↗Verification & scope
Offline supplied-valid-payload model; excludes DOM, keyboard, focus, selection, announcements and browser conformance. This reproducer isolates one failure mechanism. Results cover the supplied fixtures. Variants within a family share a test contract and should remain grouped when constructing evaluation splits. Related mechanisms with a shared evaluation_group must also remain together; these controlled models are not independent production incidents.
Observations recorded using Python 3.12.14 at 2026-09-29T14:42:23.083724+00:00.
Case digest / d150e1def4a0c4b010772a8e77aeed431808118bd6f7f3d9f29d470868d97e17