FA-53595 / Accessibility interaction semantics / Member archive

Destroyed proxy retains sensitive value payload · case 05

Destroyed proxy retains sensitive value payload.

Member previewVariant 5 · 3 implementations · 8 checks per implementation

Case contract

Bounded accessibility proxy registry: input operations [kind,id,generation,value]. create installs a nonnegative generation only if newer than existing generation; retired generations remain recorded. destroy only applies to matching generation. get returns value only for matching generation live proxy. set changes matching live proxy and never creates objects. pin/unpin maintain nonnegative reference count; destroying a pinned proxy immediately makes reads unavailable but keeps tombstone until unpinned. Each operation returns a snapshot [id,generation,live,value,pins] for its ID, or None when absent; dead value is always None. Unknown operations do nothing.

Why this case matters

Offline accessibility bridge model with explicit policy; useful for testing semantic API adapters independently of browser implementations.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
retired proxy cannot revive	`[["a", 5, true, "x", 0], ["a", 5, false, "x", 0], ["a", 5, false, "x", 0], ["a", 5, false, "x", 0]]`	`[["a", 5, true, "x", 0], ["a", 5, false, null, 0], ["a", 5, false, null, 0], ["a", 5, false, null, 0]]`	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.