FA-8033 / Undo and history / Member archive

Undo stack transitions: An unchanged edit creates an undo step and destroys redo · case 03

An unchanged edit creates an undo step and destroys redo.

Member previewVariant 3 · 3 implementations · 10 checks per implementation

Case contract

Distinct edits push the old present and clear redo; undo and redo transfer one state while preserving order; no-op edits and unavailable traversal preserve history.

Why this case matters

A deterministic model of undo stack transitions; this isolates one interface invariant without requiring a browser.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
noop retains redo	`[["a", "b"], "b", []]`	`[["a"], "b", ["c"]]`	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.