FA-37209 / Table interactions / Member archive

Atomic table row editing: required merged row · case 04

The table required merged row result violates the stipulated atomic table row editing contract.

Member previewVariant 4 · 3 implementations · 7 checks per implementation

Case contract

Row commits validate the merged draft atomically, reject unknown schema fields, ignore readonly fields, preserve untouched cells and stable identity, reject revision conflicts, suppress no-ops, and increment the revision only after actual changes.

Why this case matters

An offline table UI model isolates atomic table row editing, 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
required untouched	`{"fields": {"a": "required"}, "row": {"a": "ok", "b": 2, "id": "r"}, "status": "invalid"}`	`{"fields": ["b"], "revision": 5, "row": {"a": "ok", "b": 0, "id": "r"}, "status": "saved"}`	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.