FA-38222 / Table interactions / Member archive

Table row action targeting: atomic busy block · case 02

The table atomic busy block result violates the stipulated table row action targeting contract.

Member previewVariant 2 · 3 implementations · 8 checks per implementation

Case contract

A row action uses current row order, bulk selection only when the clicked row belongs to it and the action permits bulk, optional visible scope, default-deny per-action permissions, atomic busy/permission rejection, explicit empty scope, confirmation policy, and per-row revision snapshots.

Why this case matters

An offline table UI model isolates table row action targeting, 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
one busy member	`{"action": "delete", "status": "ready", "targets": [{"id": "a", "payload": {}, "revision": null}, {"id": "b", "payload": {}, "revision": null}]}`	`{"blocked": ["b"], "status": "busy", "targets": []}`	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.