@@ -0,0 +1,4 @@
+---
+---
+
+Test-only change in `@object-ui/plugin-form`; no package is released and the renderer is unchanged (objectui#11550). The `object-form` `fields` fixtures name their fields as strings: `fieldSecurityPayload`, `systemManagedPayload` and the flat drawer shape in `drawerFirstLoadWindow-10190` used `{ name, label }` entries whose `label` the form never read. The `{ name }` row in `objectFormFieldsMembers-8071` no longer pins a tolerated spelling. It now pins that the `ObjectFormSchema` mirror refuses the entry at `fields.0` while a STORED one still draws, and the master-detail hand-off row in `topLevelFieldsWarnCoverage-8847` is relabelled as the same stored read.
@@ -73,7 +73,7 @@ function heldRead() {
 }
 
 const SHAPES = [
-  ['flat fields', { fields: [{ name: 'title' }, { name: 'note' }] }],
+  ['flat fields', { fields: ['title', 'note'] }],
   ['sections', { sections: [{ name: 'basics', label: 'Basics', fields: ['title', 'note'] }] }],
 ] as const;
 
 
@@ -49,22 +49,30 @@
  * site changed — the ablation objectui#8071 ran on this file removed the
  * `typeof fieldName === 'string'` name resolution and reddened rows 1, 3 and 5.
  *
- * The `{ name }` spelling in row 5 is recorded as the renderer's tolerance, not
- * as a second contract (AGENTS.md #0.1): it is what `buildFlatFields` documents
- * ("field names or objects carrying one") and what the loop's
- * `(fieldName as any).name` fallback does. Pinned so that a future edit removing
- * it is a decision rather than an accident, and so the contrast with the
- * REJECTED `{ field }` spelling above it cannot quietly invert.
+ * Row 6 is the `{ name }` entry, and objectui#11550 TURNED IT AROUND (triage
+ * ruling 5969880008). It used to be pinned as a tolerated spelling, which every
+ * authoring face then taught. It is retired from authoring: the declared member
+ * is `string[]` (`ObjectFormSchema.fields`, whose zod mirror refuses the entry
+ * at `fields.0`), and the guide and the fixtures name fields as strings. What
+ * stays is the READ: the loop's `(fieldName as any).name` and `buildFlatFields`
+ * still draw an entry STORED that way, as objectui#11533 kept stored rules
+ * readable. So the row pins both halves, and the `{ field }` contrast above it
+ * stays exactly as it was.
  */
 
 import { describe, it, expect, vi } from 'vitest';
 import { render, waitFor } from '@testing-library/react';
 import React from 'react';
 import { registerAllFields } from '@object-ui/fields';
+import { ObjectFormSchema as ObjectFormMirror } from '@object-ui/types/zod';
 import { ObjectForm } from '../ObjectForm';
 
 registerAllFields();
 
+/** `{ code, path }` of what a parse refused, so row 6 names WHICH entry was refused and HOW. */
+const refusal = (result: { success: boolean; error?: { issues: Array<{ code: string; path: PropertyKey[] }> } }) =>
+  result.success ? [] : result.error!.issues.map((issue) => ({ code: issue.code, path: issue.path.join('.') }));
+
 const OBJECT_SCHEMA = {
   name: 'invoice',
   fields: {
@@ -162,7 +170,15 @@ describe('object-form `fields` members are BARE FIELD NAMES (objectui#8071)', ()
     ).toEqual(['Note']);
   });
 
-  it('6. tolerates the `{ name }` spelling — recorded as drift, not a second contract', async () => {
+  it('6. a STORED `{ name }` entry still draws, but the declared member refuses it (objectui#11550)', async () => {
+    // The authoring half: the mirror of the declared `string[]` refuses the
+    // entry, and ONLY the entry. The bare name beside it is the control.
+    const node = { type: 'object-form', objectName: 'invoice', mode: 'create' } as const;
+    expect(refusal(ObjectFormMirror.safeParse({ ...node, fields: [{ name: 'note' }] }))).toEqual([
+      { code: 'invalid_type', path: 'fields.0' },
+    ]);
+    expect(ObjectFormMirror.safeParse({ ...node, fields: ['note'] }).success).toBe(true);
+    // The read half: metadata already stored with the entry keeps drawing.
     expect(await renderedFieldLabels({ fields: [{ name: 'note' }] })).toEqual(['Note']);
   });
 });
 
@@ -50,7 +50,10 @@
  *     untyped stub. A DETAIL column name is the case this composition invites,
  *     because one node declares two field vocabularies. It renders nothing in
  *     the parent, while the line grid keeps that column;
- *   - `{ name }` is tolerated as the same member as the bare name;
+ *   - a STORED `{ name }` member still draws as its bare name. It is not an
+ *     authoring shape: objectui#11550 retired it from every authoring face, and
+ *     `objectFormFieldsMembers-8071.test.tsx` row 6 pins the declared refusal.
+ *     This row pins only that the hand-off keeps the stored read;
  *   - ⚠️ the key bounds what is DRAWN, not what the PARENT leg of the atomic
  *     batch WRITES: a seeded parent field it does not list is still written.
  *     That is the ruled behaviour (objectui#11114), not a defect: the
@@ -251,7 +254,7 @@ describe('object-master-detail-form `fields` — the member shape (objectui#8071
     ).toBeGreaterThan(0);
   });
 
-  it('`{ name }` is tolerated as the same member as the bare name', async () => {
+  it('a STORED `{ name }` member still draws as its bare name — read only, not authoring (objectui#11550)', async () => {
     const { container } = await mountMembers({ fields: [{ name: 'note' }, 'status'] });
     expect(parentFields(container)).toEqual(['note', 'status']);
   });
 
@@ -127,15 +127,7 @@ const DENIED = ['score', 'adjusted_score'] as const;
  */
 const UNCHANGED_ALLOWED = { indicator_name: 'Revenue', target_value: 100, weight: 20 };
 
-const FIELDS = [
-  { name: 'sheet', label: 'Sheet' },
-  { name: 'indicator_name', label: 'Indicator' },
-  { name: 'target_value', label: 'Target' },
-  { name: 'weight', label: 'Weight' },
-  { name: 'actual_value', label: 'Actual' },
-  { name: 'score', label: 'Score' },
-  { name: 'adjusted_score', label: 'Adjusted' },
-];
+const FIELDS = ['sheet', 'indicator_name', 'target_value', 'weight', 'actual_value', 'score', 'adjusted_score'];
 
 const makeDataSource = () => {
   const update = vi.fn(async (_o: string, _id: string, d: any) => ({ id: 'LINE1', ...d }));
 
@@ -214,11 +214,7 @@ describe('form write payloads — server-owned columns (objectui#10108)', () =>
             // Business fields only — no ownership or audit column is declared
             // in any section, which is what makes an emitted one an INJECTION
             // rather than a displayed field being echoed.
-            fields: [
-              { name: 'plan_indicator', label: 'Indicator' },
-              { name: 'actual_value', label: 'Actual' },
-              { name: 'remark', label: 'Remark' },
-            ],
+            fields: ['plan_indicator', 'actual_value', 'remark'],
           } as any}
           dataSource={ds}
         />,
-Original file line number
+Diff line change
@@ @@ -0,0 +1,4 @@ @@
 +---
 +---
++
 +Test-only change in `@object-ui/plugin-form`; no package is released and the renderer is unchanged (objectui#11550). The `object-form` `fields` fixtures name their fields as strings: `fieldSecurityPayload`, `systemManagedPayload` and the flat drawer shape in `drawerFirstLoadWindow-10190` used `{ name, label }` entries whose `label` the form never read. The `{ name }` row in `objectFormFieldsMembers-8071` no longer pins a tolerated spelling. It now pins that the `ObjectFormSchema` mirror refuses the entry at `fields.0` while a STORED one still draws, and the master-detail hand-off row in `topLevelFieldsWarnCoverage-8847` is relabelled as the same stored read.
Original file line number	Diff line number	Diff line change
`@@ -73,7 +73,7 @@ function heldRead() {`
`73`	`73`	`}`
`74`	`74`
`75`	`75`	`const SHAPES = [`
`76`		`- ['flat fields', { fields: [{ name: 'title' }, { name: 'note' }] }],`
	`76`	`+ ['flat fields', { fields: ['title', 'note'] }],`
`77`	`77`	`['sections', { sections: [{ name: 'basics', label: 'Basics', fields: ['title', 'note'] }] }],`
`78`	`78`	`] as const;`
`79`	`79`