FA-37623 / Table interactions / Member archive

Remote table page response admission: server total · case 03

The table server total result violates the stipulated remote table page response admission contract.

Member previewVariant 3 · 3 implementations · 6 checks per implementation

Case contract

Admit remote table pages only for the exact request/query/offset. Errors retain displayed rows, duplicate row IDs retain first placement and last payload, successful totals may shrink, loading and old errors clear, and only explicit server deletions prune cross-page selection.

Why this case matters

An offline table UI model isolates remote table page response admission, 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
fresh deduped page	`{"error": null, "has_next": false, "loading": false, "offset": 2, "query": "q", "request": 2, "rows": [{"id": "a", "v": 3}, {"id": "b", "v": 3}], "selected": ["a", "off"], "total": 2}`	`{"error": null, "has_next": false, "loading": false, "offset": 2, "query": "q", "request": 2, "rows": [{"id": "a", "v": 3}, {"id": "b", "v": 3}], "selected": ["a", "off"], "total": 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.