FA-36864 / Table interactions / Member archive

Column track resolution: maximum width · case 04

The table maximum width result violates the stipulated column track resolution contract.

Member previewVariant 4 · 3 implementations · 6 checks per implementation

Case contract

Resolve unique schema IDs in saved order then append unlisted visible columns; clamp widths to per-column bounds, keep explicit zero, compute prefix starts, omit a terminal resize handle, and use None for no terminal column.

Why this case matters

An offline table UI model isolates column track resolution, 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
mixed schema	`{"handles": ["b"], "ids": ["b", "a", "c"], "last": "c", "resizable": ["b", "c"], "starts": {"a": 48, "b": 0, "c": 58}, "total": 88, "widths": {"a": 10, "b": 48, "c": 30}}`	`{"handles": ["b"], "ids": ["b", "a", "c"], "last": "c", "resizable": ["b", "c"], "starts": {"a": 48, "b": 0, "c": 58}, "total": 78, "widths": {"a": 10, "b": 48, "c": 20}}`	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.