Found while bumping the console pin to objectui d8ec8d6d4f01 (#14027 / PR #14165). Out of scope there under pin-bump discipline, so recorded rather than ridden.
What is stale
Two places in packages/spec describe objectui's data-table column accessor as reading two spellings:
packages/spec/liveness/field.json (the columns entry's note): "the data-table accessor resolves accessorKey || name only"packages/spec/src/conversions/registry.ts (a comment, near line 7269): "the data-table accessor reads accessorKey || name"
At the pin PR #14165 moves to, objectui commit 41725898c retired that fallback. Its own changeset, verbatim:
Breaking for authored metadata: a data-table column spelled name no longer resolves its cells. Use the declared accessorKey.
So from this pin onward the accessor reads accessorKey only, and both notes describe a two-spelling resolution that no longer exists.
What is NOT affected
The verdicts those notes support are unchanged, and this is a citation-accuracy finding rather than a liveness re-grade:
- the spec declares no data-table column accessor named
name, so nothing authorable here is retired;
- the liveness note's actual conclusion — that a spec-canonical object form renders blank and is therefore refused at parse — still holds.
That is why this was not folded into the pin bump: nothing in the bump's diff depends on it, and the correct fix is prose in files the bump must not touch.
Prior art, same class
#7133 was the citation-repair bundle for exactly this shape: liveness entries whose verdict is right and whose cited objectui reader has moved. It is closed; this is a fresh instance, produced by a pin bump rather than found by a sweep. Worth asking whether a pin bump should carry a routine citation re-check, since the bump is the moment upstream readers move.
Suggested check
Re-read both notes against objectui at the pin in force and reword to the single surviving spelling, keeping the conclusion sentence intact.
Generated by Claude Code
Found while bumping the console pin to objectui
d8ec8d6d4f01(#14027 / PR #14165). Out of scope there under pin-bump discipline, so recorded rather than ridden.What is stale
Two places in
packages/specdescribe objectui's data-table column accessor as reading two spellings:packages/spec/liveness/field.json(thecolumnsentry's note): "the data-table accessor resolvesaccessorKey || nameonly"packages/spec/src/conversions/registry.ts(a comment, near line 7269): "the data-table accessor readsaccessorKey || name"At the pin PR #14165 moves to, objectui commit
41725898cretired that fallback. Its own changeset, verbatim:So from this pin onward the accessor reads
accessorKeyonly, and both notes describe a two-spelling resolution that no longer exists.What is NOT affected
The verdicts those notes support are unchanged, and this is a citation-accuracy finding rather than a liveness re-grade:
name, so nothing authorable here is retired;That is why this was not folded into the pin bump: nothing in the bump's diff depends on it, and the correct fix is prose in files the bump must not touch.
Prior art, same class
#7133 was the citation-repair bundle for exactly this shape: liveness entries whose verdict is right and whose cited objectui reader has moved. It is closed; this is a fresh instance, produced by a pin bump rather than found by a sweep. Worth asking whether a pin bump should carry a routine citation re-check, since the bump is the moment upstream readers move.
Suggested check
Re-read both notes against objectui at the pin in force and reword to the single surviving spelling, keeping the conclusion sentence intact.
Generated by Claude Code