FA-38179 / Table interactions / Member archive

Asynchronous table cell save acknowledgement: newer draft preservation · case 04

The table newer draft preservation result violates the stipulated asynchronous table cell save acknowledgement contract.

Member previewVariant 4 · 3 implementations · 7 checks per implementation

Case contract

A save acknowledgement belongs to an exact pending request and row, clears only that pending cell, preserves errors and newer edits, rejects older server revisions, installs canonical server values/revisions, and clears a draft only when the original edit ID still owns it.

Why this case matters

An offline table UI model isolates asynchronous table cell save acknowledgement, including adversarial row/column relationships.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
new edit same value	`{"draft": [], "error": null, "pending": [], "row": {"a": "ack", "id": "r", "revision": 4}}`	`{"draft": [[["r", "a"], {"edit_id": 10, "value": "v"}]], "error": null, "pending": [], "row": {"a": "ack", "id": "r", "revision": 4}}`	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.