feat(plugin-list)!: the renderers stop reading the list-view keys every door refuses (objectui#6152 round 14)

Retires classes A, B, C, E and F of the round-13 census on every route that
read them: ListView, app-shell's object-page relays, plugin-view's
generateViewSchema and ObjectTimeline's nested date rung.

- A: the pre-#2231 alias rungs (kanban groupField / cardFields, gallery
  imageField, timeline dateField, and calendar dateField read as a timeline
  axis) in ListView's branches and capability gate, the relays, the
  object-view element and ObjectTimeline.
- B: calendar.defaultView's lift and the ...restKanban / ...restCalendar
  spreads; the declared summarizeField, colorField and allDayField are read
  by name instead.
- C: the tree titleField label rung and the tree, gantt and options.grid
  spreads; gantt (and plugin-view's timeline) go through typed total tables
  of the spec block's keys. A block key named like a node key no longer
  overrides the node.
- E: the projection collectors list the blocks' spec keys only.
- F: the types prose, the refusal messages and two pending changesets' dated
  notes say the readers moved.

The core fold (normalize-list-view.ts) is parked until PR objectui#12036
lands. Class D (the legacy chart binding) is the next round.

Claude-Session: https://claude.ai/code/session_01CijGnfWLxTLUFcJkY2ouUw
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/6152-list-view-blocks-strict.md

@@ -43,3 +43,8 @@ before; only authored metadata meets the refusal. The legacy `options.KIND` bag
 unchanged. It is now the spec's list-overlay bag by reference, with these four blocks in it, so each
 refusal above also applies under `options.KIND`, with the same message; see
 `.changeset/6152-list-view-options-bag.md`. The renderers' reads still have not moved.
+
+**Note added 2026-10-09 (objectui#6152 round 14):** the renderers' reads have moved. No renderer reads
+the four aliases, `calendar.defaultView` or an undeclared key of these blocks any longer, so a view
+stored with one of them renders without what that key used to bind; see
+`.changeset/6152-list-view-readers-retired.md` for what changes on screen and what to write instead.

.changeset/6152-list-view-options-bag.md

@@ -70,3 +70,10 @@ chart, and no longer show the bag.
 What did not move: the renderers' reads. `ListView` still merges each `options.KIND` under the
 top-level block and still reads the legacy spellings, so a view stored before these doors closed
 renders as before; only authored metadata meets the refusal.
+
+**Note added 2026-10-09 (objectui#6152 round 14):** the renderers' reads have moved. `ListView`
+still merges each `options.KIND` under the top-level block, but it reads each kind's declared keys
+only: the legacy spellings, `options.grid` and the undeclared keys a bag carries are no longer read,
+so a view stored with one of them renders without what that key used to bind; see
+`.changeset/6152-list-view-readers-retired.md`. The legacy chart axes (`options.chart.xAxisField`
+and the rest) are still read until the next round on objectui#6152.

.changeset/6152-list-view-readers-retired.md

@@ -0,0 +1,49 @@
+---
+'@object-ui/plugin-list': minor
+'@object-ui/plugin-view': minor
+'@object-ui/app-shell': minor
+'@object-ui/plugin-timeline': minor
+'@object-ui/types': patch
+---
+
+feat(plugin-list)!: the renderers stop reading the list-view keys every door refuses: the pre-#2231 aliases, `calendar.defaultView`, and the undeclared keys a per-kind block carries (objectui#6152, round 14)
+
+Clause-②: no
+
+**Changed (breaking for a stored view that carries a refused key).** Rounds 11 and 12 of
+objectui#6152 closed the doors: `@object-ui/types`, `objectui validate` and `@objectstack/spec`'s
+view write door refuse these keys on a list view's per-kind blocks, top-level and under the legacy
+`options` bag. The renderers kept reading them, so a view stored before the doors closed still
+rendered as written. They no longer read them, on every route that did: `ListView`, the object
+page's relay (`@object-ui/app-shell`), `ObjectView`'s own views (`@object-ui/plugin-view`) and
+`ObjectTimeline`. A stored view that carries one of these keys still renders, without what the key
+used to bind. Write the spec's key instead:
+
+| stored key (either nesting) | what renders now | write instead |
+| :--- | :--- | :--- |
+| `kanban.groupField` | lanes from the object's declared lifecycle field, as for a view that names none | `kanban.groupByField` |
+| `kanban.cardFields` | cards show `kanban.columns`, or the view's own fields | `kanban.columns` |
+| `gallery.imageField` | no cover binding: `ObjectGallery` tries `image`, and the Gallery view is not offered | `gallery.coverField` |
+| `timeline.dateField`, and `calendar.dateField` read as a timeline axis | no timeline axis: the timeline's refusal names the keys to write, and the Timeline view is not offered | `timeline.startDateField` (or `calendar.startDateField`) |
+| `calendar.defaultView` | the calendar opens on its own default view | nothing on a list view: the initial mode is the `object-calendar` element's flat `defaultView` |
+| `kanban.swimlaneField` and any other undeclared kanban key | not drawn | nothing: the spec's kanban block has no swimlane |
+| `tree.titleField` | the tree labels by `name` | `tree.labelField` |
+| an undeclared key under `calendar`, `tree` or `gantt`, or anything under `options.grid` | not forwarded to the view | the block's declared key, or a top-level key of the view for a grid |
+
+The declared keys keep their route: `kanban.summarizeField`, `calendar.colorField` and
+`calendar.allDayField` are now read by name where the removed spreads used to carry them, and every
+`gantt` key the spec declares reaches the gantt through a typed table that `tsc` keeps total. A
+block key named like a node key (`objectName`, `filter`) can no longer override the node's own
+value. `ListView`'s projection collectors stop asking the server for the fields these keys named.
+
+**Not measured: production.** The census before this change (objectui#6152 round 13) found no
+writer and no stored row carrying these keys in any repository corpus a seat can reach, with
+positive controls; stored view and page metadata in deployments was not measured. A row that
+carries one of these keys renders as the table says until it is re-saved with the key on the
+right.
+
+Not in this change: the legacy chart axes (`chart.xAxisField`, `yAxisFields`, `categoryField`,
+`valueField`, `aggregation`), which `ListView` still reads until the next round on objectui#6152.
+
+- `@object-ui/types`: the refusal messages of these keys no longer say a stored view still renders
+  through the alias, and the kanban `groupBy` refusal no longer suggests the refused `groupField`.

apps/console/src/__tests__/timelineAxisRefusalReach-7070.test.tsx

@@ -159,13 +159,17 @@ describe('ListView → ObjectTimeline: an undeclared axis reaches the refusal (o
     expect(refusal()!.textContent ?? '').toContain('timeline.startDateField');
   });
 
-  it('CONTROL: the LEGACY `timeline.dateField` alias still renders', async () => {
-    // The alias is resolved by the face, not by a floor. If step ③ had taken it
-    // with the fabrication, a pre-#2231 view would start refusing — a regression
-    // the ruling did not order.
-    await mountListView({ ...LIST_BASE, timeline: { dateField: 'start_date' } });
-    await waitFor(() => expect(canvas()).not.toBeNull());
-    expect(refusal()).toBeNull();
+  it('a stored LEGACY `timeline.dateField` reaches the refusal too (objectui#6152 round 14)', async () => {
+    // Step ③ kept the alias (the ruling ordered no regression for a pre-#2231
+    // view), and this arm pinned that it still rendered. objectui#6152 round 14
+    // retired the alias reads on their own ruling: every list-view door refuses
+    // the key by name. A stored one now binds no axis, so it gets the refusal,
+    // which names the key to write. Written in the legacy `options` bag, which no
+    // fold reaches; the TOP-LEVEL spelling joins it with that round's core leg.
+    await mountListView({ ...LIST_BASE, options: { timeline: { dateField: 'start_date' } } });
+    await waitFor(() => expect(refusal()).not.toBeNull());
+    expect(canvas()).toBeNull();
+    expect(refusal()!.textContent ?? '').toContain('timeline.startDateField');
   });
 
   it('CONTROL: a CALENDAR-bound view still renders its timeline', async () => {
@@ -195,9 +199,10 @@ describe('ObjectView → ObjectTimeline: the second face reaches it too (objectu
     expect(screen.queryByText('Spring Launch')).toBeNull();
   });
 
-  it('CONTROL: the LEGACY `timeline.dateField` alias still renders here too', async () => {
+  it('a stored LEGACY `timeline.dateField` reaches the refusal here too (objectui#6152 round 14)', async () => {
     await mountObjectView({ timeline: { dateField: 'start_date' } });
-    await waitFor(() => expect(canvas()).not.toBeNull());
-    expect(refusal()).toBeNull();
+    await waitFor(() => expect(refusal()).not.toBeNull());
+    expect(canvas()).toBeNull();
+    expect(screen.queryByText('Spring Launch')).toBeNull();
   });
 });

packages/app-shell/src/views/ObjectView.galleryBinding-7547.test.tsx

@@ -102,19 +102,20 @@ describe('galleryViewOptions — the object page forwards, it does not invent (o
     expect(out).not.toHaveProperty('imageField');
   });
 
-  it('CONTROL: a stored legacy `imageField` still answers `coverField`', () => {
-    // The legacy READ is not this round's to retire: a row stored before the
-    // view write door judged it can still carry `imageField`, and its cover
-    // still binds. The block spread forwards the stored key as it was stored;
-    // nothing here SYNTHESIZES it.
+  it('a stored legacy `imageField` answers nothing (objectui#6152 round 14)', () => {
+    // Round 12 left the legacy READ in place for rows stored before the view
+    // write door judged the bag; round 14 retired it. The cover binding is read
+    // from `coverField` alone, so no `coverField` is synthesized from the alias.
+    // The block spread still forwards the stored key as it was stored (a
+    // carrier, not a reader): nothing downstream reads it any more.
     const out = galleryViewOptions({ gallery: { imageField: 'logo' } });
-    expect(out.coverField).toBe('logo');
+    expect(out).not.toHaveProperty('coverField');
     expect(out.imageField).toBe('logo');
   });
 
   it('CONTROL: both spellings stored — `coverField` keeps its own value', () => {
-    // `coverField` prefers itself, then the legacy spelling; the stored legacy
-    // key rides the spread unchanged.
+    // `coverField` is read from itself alone; the stored legacy key rides the
+    // spread unchanged.
     const out = galleryViewOptions({ gallery: { imageField: 'logo', coverField: 'photo' } });
     expect(out.coverField).toBe('photo');
     expect(out.imageField).toBe('logo');

packages/app-shell/src/views/ObjectView.kanbanGroupByRetired-8213.test.tsx

@@ -148,11 +148,13 @@ describe('the object page emits ONE lane spelling — the spec\'s (objectui#8213
     expect(refusedKeys(emitted)).not.toContain('groupBy');
   });
 
-  it('for a view that declared the LEGACY alias', () => {
-    // The alias READ is untouched by this card: the value arrives legacy and
-    // leaves canonical, and leaves under one key only.
-    const emitted = kanbanViewOptions({ kanban: { groupField: 'stage' } }, OBJECT_WITH_STAGE);
+  it('for a view that stored the retired LEGACY alias', () => {
+    // The alias READ was untouched by this card; objectui#6152 round 14 retired
+    // it. The lane is the detector's (a value the alias does not name), and it
+    // still leaves under one key only.
+    const emitted = kanbanViewOptions({ kanban: { groupField: 'name' } }, OBJECT_WITH_STAGE);
     expect(laneKeysOf(emitted)).toEqual(['groupByField']);
+    expect(emitted.groupByField).toBe('stage');
   });
 
   it('for a lane the ADR-0085 detector supplied', () => {
@@ -172,9 +174,10 @@ describe('the object page emits ONE lane spelling — the spec\'s (objectui#8213
 describe('the one reader of `groupBy` still gets the same value (objectui#8213)', () => {
   it('carries the lane under `groupByField`, the rung the collectors read first', () => {
     // The census question, stated as a property rather than as a claim about
-    // call sites. `ListView`'s two projection/expand collectors list
+    // call sites. `ListView`'s two projection/expand collectors listed
     // `v.groupByField, v.groupField, v.groupBy` as candidates for the SAME lane
-    // value; deleting the third is only safe because the first carries it. If a
+    // value; deleting the third was only safe because the first carries it, and
+    // since objectui#6152 round 14 the first is the only one they list. If a
     // future edit moved the value onto `groupBy` alone, this reddens.
     expect(kanbanViewOptions({}, OBJECT_WITH_STAGE).groupByField).toBe('stage');
   });

packages/app-shell/src/views/ObjectView.kanbanLane-8193.test.tsx

@@ -31,10 +31,11 @@
  * side of that boundary, so nothing folded it and the alias read was
  * load-bearing purely because of where this producer wrote.
  *
- * ⚠️ THE ALIAS IS NOT RETIRED AND NO ALIAS READ WAS TOUCHED. Stored metadata
- * still authors `groupField`; `ListView` resolving `groupByField || groupField`
- * is exactly why the sibling could drop the alias write. The arms below assert
- * what this face WRITES, never what any face reads.
+ * ⚠️ THIS CARD RETIRED NO ALIAS READ: it changed what this face WRITES. The
+ * reads went later, on their own ruling (objectui#6152 round 14): this face,
+ * `ListView` and `ObjectView` read the lane from `groupByField` alone now. The
+ * legacy-alias arm below was re-judged then: it pins that the alias names no
+ * lane, with a value the detector would never pick.
  *
  * ⚠️ `groupBy` WAS STILL WRITTEN WHEN THIS FILE LANDED, and is not any more:
  * objectui#8213 ran the producer census this file deferred and retired the
@@ -80,11 +81,12 @@ describe('the object page writes the SPEC lane key (objectui#8193)', () => {
     expect(out).not.toHaveProperty('groupField');
   });
 
-  it('emits `groupByField` for a view that declared the LEGACY alias', () => {
-    // Reading the alias is untouched — a view that authored `groupField` still
-    // resolves its lane. What changed is that the alias stops being propagated:
-    // the value comes in legacy and leaves canonical.
-    const out = kanbanViewOptions({ kanban: { groupField: 'stage' } }, OBJECT_WITH_STAGE);
+  it('a view that stored the retired LEGACY alias gets the detector\'s lane, not the alias\'s (objectui#6152 round 14)', () => {
+    // When this card landed the alias was still READ (the value came in legacy
+    // and left canonical), and this arm wrote `stage`, the very field the
+    // detector picks, so it could not tell a read alias from an ignored one.
+    // Re-judged with a value the detector never picks: the alias names no lane.
+    const out = kanbanViewOptions({ kanban: { groupField: 'name' } }, OBJECT_WITH_STAGE);
     expect(out.groupByField).toBe('stage');
     expect(out).not.toHaveProperty('groupField');
   });

packages/app-shell/src/views/ObjectView.timelineBinding.test.tsx

@@ -51,9 +51,12 @@ describe('timelineViewOptions — the object page forwards, it does not resolve
     expect(out.scale).toBe('month');
   });
 
-  it('promotes the legacy `dateField` alias onto the spec key', () => {
+  it('does NOT promote the retired `dateField` alias onto the spec key (objectui#6152 round 14)', () => {
+    // It used to: this face resolved `startDateField || dateField`. Every
+    // list-view door refuses the alias by name and `ListView` no longer reads
+    // it either, so the relay restates the spec key alone.
     expect(timelineViewOptions({ timeline: { dateField: 'start_date' } }).startDateField)
-      .toBe('start_date');
+      .toBeUndefined();
   });
 
   it('invents NO date field when the view declares none', () => {

packages/app-shell/src/views/ObjectView.titleFieldConvergence.test.tsx

@@ -297,13 +297,17 @@ describe('ObjectView view-config `titleField` — the middle rung is gone (objec
     });
   });
 
-  it("CONTROL: the tree's second view-declared rung (`tree.titleField`) still answers", async () => {
-    // The tree seam is the only one with TWO view-declared rungs; dropping the
-    // object rung must not have collapsed them into one.
+  it("the tree's retired `tree.titleField` rung answers nothing (objectui#6152 round 14)", async () => {
+    // The tree seam used to be the only one with TWO view-declared rungs, and
+    // this case pinned that dropping the object rung had not collapsed them. The
+    // second rung read a key the spec refuses by name on the tree block
+    // (objectui#8841), and objectui#6152 round 14 retired it, so a stored
+    // `tree.titleField` now floors at 'name' like an undeclared label. The
+    // declared `labelField` still wins (the CONTROL above).
     const seams = await resolveSeams(
       objectsWith({ titleField: REJECTED }, { tree: { titleField: 'v_tree_title' } }),
     );
-    expect(seams.tree).toBe('v_tree_title');
+    expect(seams.tree).toBe('name');
   });
 });