FA-38495 / Tree accessibility / Member archive

Lazy tree branch request lifecycle: Branch request identity omits an epoch or token · case 05

Branch request identity omits an epoch or token produces the wrong hierarchical widget state in a regression fixture.

Member previewVariant 5 · 3 implementations · 8 checks per implementation

Case contract

A request is accepted only for a live open branch with matching epoch and token. Accepted pages replace a placeholder with deduplicated child IDs, clear busy/error state, and derive completeness from a next cursor. Rejected responses preserve all branch state.

Why this case matters

Offline executable model of a hierarchical accessibility interaction; inputs are bounded and valid as stipulated. No browser, assistive technology, or normative ARIA conformance is claimed.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
old epoch	`[["z", "c0", "c1", "c2", "c3", "c4"], false, null, null, true, false, null, "z"]`	`[["old"], true, "old-error", "oldcursor", false, true, "t", "placeholder"]`	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.