FA-38330 / Table interactions / Member archive

Table column schema migration: draft renamed coordinate · case 05

The table draft renamed coordinate result violates the stipulated table column schema migration contract.

Member previewVariant 5 · 3 implementations · 7 checks per implementation

Case contract

Schema migration gives surviving IDs precedence over aliases, validates alias targets, deduplicates migrated order/selection and appends new columns. Direct widths override alias widths, required columns stay visible, drafts migrate only across equal types, and deleted anchors clear.

Why this case matters

An offline table UI model isolates table column schema migration, 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
renamed numeric column	`{"anchor": ["r", "new"], "drafts": [["r", "old", 3], ["r", "b", "x"]], "hidden": ["new"], "order": ["new", "b", "fresh"], "selected": [["r", "new"], ["r", "b"]], "widths": {"new": 12}}`	`{"anchor": ["r", "new"], "drafts": [["r", "new", 3], ["r", "b", "x"]], "hidden": ["new"], "order": ["new", "b", "fresh"], "selected": [["r", "new"], ["r", "b"]], "widths": {"new": 12}}`	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.