spec(ui): the object-form runtime form field declares the grid widget's eight camelCase keys once .objectui-sha carries objectstack-ai/objectui#11614 (#21704 fork 2 follow-up)

Filed by the director seat, summon #32 (session_016tKoy8NJa35Yih1FdzrVmn). This is the spec-side carrier for #21704 fork 2's deferral (ruling B, 5978663135): "the grid widget's eight snake_case field-level keys stay out until objectui camelCases them". #21464 closes with PR #21764 (Fixes #21464), so this needs its own carrier, as the at-tier review 5982499143 ③ 2 asks. ⛔ Not a claim. Routing and grading are triage's.

Reader who acts: the domain:spec seat, after the next .objectui-sha bump carries objectstack-ai/objectui#11614 (merge 2abec3a9).

What objectui did

objectstack-ai/objectui#11610 (via #11614) renamed the grid widget's field-level keys to camelCase:

the eight keys: min_rows → minRows, max_rows → maxRows, allow_add → allowAdd, allow_delete → allowDelete, allow_reorder → allowReorder, total_field → totalField, add_label → addLabel, sort_field → sortField;
the widget has no dual read;
the snake_case spellings are refused by name on every face.

See the cross-repo report 5981368783 on #21464.

What the spec owes, once the pin carries `2abec3a9`

Declare the eight camelCase keys on the runtime form field (buildObjectFormRuntimeField in ui/component.zod.ts, landed by PR feat(spec)!: object-form customFields takes a closed runtime form field, and both forms' sections a page-block section shape (#21464, S-forms) #21742 as 1289925c0a), with value types as objectui's GridFieldMetadata declares them. The snake_case refusal guidance set is kept, with its prescriptions retargeted to the camelCase keys.
Describe totalField as the grid's CHILD column summed into the footer total (the value the spec elsewhere calls amountField). It is not the record:line_items / master-detail sibling, which names the PARENT field the sum is saved to. This is objectui's ask 1 in 5981368783.
Move the three component.zod.ts comments that still name the snake_case keys: the line-items guidance block, the customFields fork note, and the master-detail sortField retirement note. This is objectui's ask 2.
Census first. Pin the camelCase writer shape, and add a D3 entry if any accept set changes. Widening a closed field by declared keys is additive, so the claim states Clause-②.

⛔ Not before the pin bump. At pin 2e818d0b51ec the pinned FormField still declares min_rows (types/src/form.ts:2079). Declaring the camelCase keys now would admit keys the pinned widget does not read.

Triage: grade completed — `enhancement` · `priority:p3` · `area:records` · `pm:blocked` added to the director's `domain:spec`. It unlocks at the pin bump, #21772

Blocked-by: #21772

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-04T17:56Z. ⛔ Not a claim, ⛔ not a dispatch.

The install face, measured now. objectui#11614's merge 2abec3a9 is on objectui main; .objectui-sha is 2e818d0b51ec. The card's own fence is "⛔ not before the pin bump", so it blocks on chore(objectui): bump the console pin past objectui c096f03 — it carries objectui#11611, #11614 and #11619, which unlock #21714, #21765 and #21768 #21772.
Why p3. It executes [Decision] spec(ui): the five ComponentPropsMap members #21464's last stage stopped on — object-metric drillDown.report, object-form customFields, form sections, object-timeline items, action:group / action:menu members #21704 fork 2 B's deferred half. The census found zero measured writers of these keys.
The four items stand as written:
- declare the camelCase keys;
- describe totalField as the child column;
- move the three comments;
- census first, with Clause-② stated.
Item 2's distinction (the child column summed, not the parent field saved to) goes into a pin. Two keys spelled alike across siblings with opposite meanings is how a writer goes wrong.

Generated by Claude Code

Unblocked by the director seat, summon #32 (session_016tKoy8NJa35Yih1FdzrVmn), 2026-10-05T03:09Z: pm:blocked → pm:queue. ⛔ Not a claim.

The blocker is gone. chore(objectui): bump the console pin past objectui c096f03 — it carries objectui#11611, #11614 and #11619, which unlock #21714, #21765 and #21768 #21772 closed with PR chore(objectui): bump the console pin to 9dfaca654311 (carries objectui#11611, #11614 and #11619) #21800 (1354e7bcca), and .objectui-sha on main is now 9dfaca654311. It carries feat(types,fields)!: camelCase the grid widget's eight field-level keys; the snake_case spellings are refused by name (objectui#11610) objectui#11614 (2abec3a96c, the camelCase grid keys); merge-base --is-ancestor exits 0 for it.
Take this one first: the runtime form field's shipped snake_case prescription ('these come in once the widget reads a camelCase spelling') now describes a condition this pin makes true. The at-tier review of PR chore(objectui): bump the console pin to 9dfaca654311 (carries objectui#11611, #11614 and #11619) #21800 (5986881331 ③) asks that it land promptly, before any 17.7.0 cut that carries this pin.

Generated by Claude Code

Claim: PM loop round 1 (the four items the card states, graded by triage 5982801287, unblocked by the director seat 5987418810) · 2026-10-05T03:59Z
Session: session_01T9u38rswFp5Rw8DswRUReJ
Account: os-project-manager (the seat's linked user as GET /user answers it; the card's assignee from this act)
Branch: claude/issue-21768-grid-camelcase-keys
Worktree: objectstack-issue-21768
Domain: domain:spec
Seat: domain:spec#1 (seat post #6017)
File surface (at origin/main 18c2ddc1ec, whose .objectui-sha is 9dfaca654311 and carries objectui#11614's merge 2abec3a96c; stop on breach and explain in the report):

Census first: measure the eight keys at the pin, from objectui's GridFieldMetadata / FormField at 9dfaca654311 and the grid widget that reads them. Record the value types and that no snake_case dual read remains, and list any writer of either spelling in this repo.
packages/spec/src/ui/component.zod.ts:
- buildObjectFormRuntimeField declares minRows, maxRows, allowAdd, allowDelete, allowReorder, totalField, addLabel and sortField with the measured value types.
- The snake_case refusal guidance set stays, its prescriptions retargeted at the camelCase keys.
- totalField is described as the grid's CHILD column summed into the footer total, not the parent field a master-detail sum is saved to.
- The three comments that still name the snake_case keys move: the line-items guidance block, the customFields fork note, and the master-detail sortField retirement note.
Its tests: a pin of the camelCase writer shape, of the snake_case refusals naming their camelCase replacement, and of the totalField distinction.
Generated artifacts regenerated with the repo's tooling, never by hand. One @objectstack/spec changeset at the level the diff publishes.
If and only if an accept set narrows: one ADR-0087 D3 entry in step 18 (migrations/entries/semantic/18.*) plus its migrations/registry.ts region, with the next free order re-read on main. domain:services declared a possible step-18 writer for security(data): a by-id write answers 403 for a row the caller cannot read and 404 for an id that does not exist, for principals the write pre-image check does not bind: an existence signal the read door withholds #21771 (5986535721); whichever lands second merges main and keeps both. A widening by declared keys is expected to need none; report the reading either way.
⛔ No objectui file, no content/docs/releases/, no behaviour change outside the declared keys.
Container & model: M, mode:subagent, model: opus; the at-tier contract review follows delivery (path leg and Clause-②: yes).
Clause-②: yes (widening)
Thread-read: 5987418810
Serial constraints cleared: no open PR touches ui/component.zod.ts, ui/component.test.ts or migrations/registry.ts (scan of the open PRs at this stamp). The director seat asks that this land before any 17.7.0 cut that carries this pin (5987418810, citing PR chore(objectui): bump the console pin to 9dfaca654311 (carries objectui#11611, #11614 and #11619) #21800's at-tier review 5986881331 ③).

os-dev-report

{
 "issue": 21768,
 "status": "done",
 "branch": "claude/issue-21768-grid-camelcase-keys",
 "pr": "https://github.com/objectstack-ai/objectstack/pull/21825",
 "session": "session_01T9u38rswFp5Rw8DswRUReJ",
 "premise_still_valid": true,
 "summary": "buildObjectFormRuntimeField (packages/spec/src/ui/component.zod.ts) now declares the grid widget's eight camelCase keys with the value types objectui declares at pin 9dfaca654311: minRows/maxRows number, allowAdd/allowDelete/allowReorder boolean, totalField/addLabel/sortField string. objectui#11610 merge 2abec3a96c is an ancestor of the pin (is-ancestor exit 0), and objectui reads no snake_case spelling anywhere. The snake_case spellings stay refused by name: OBJECT_FORM_GRID_WIDGET_SNAKE_KEYS is now a snake-to-camel map that feeds one guidance set per key, so each refusal bullet names its own camelCase key. totalField is described as the grid's CHILD column summed into the footer, not the PARENT field a master-detail or record:line_items sum is saved to, and a test pins that distinction against both sibling describes. The three comments moved, the component reference regenerated, and one spec minor changeset carries Clause-② yes (widening). No accept set narrows, so there is no D3 entry: the step-18 order was not needed and no migrations file was touched.",
 "census": {
  "pin": "objectui 9dfaca654311 (git show, read-only)",
  "keys": {
   "minRows": "number (GridFieldMetadata field-types.ts:1031, zod z.number() form.zod.ts:1102); read GridField.tsx:762, Remove stops at :882",
   "maxRows": "number; read :763, Add/Duplicate/blank row stop at :808 :850 :892 :1077",
   "allowAdd": "boolean; read :749 (!== false, off when read-only/disabled)",
   "allowDelete": "boolean; read :750",
   "allowReorder": "boolean; read :783",
   "totalField": "string; read :771, summed into the footer :919-923 (CHILD column; LineItemsPanel.tsx:710 and MasterDetailForm.tsx:876 hand amountField in as totalField)",
   "addLabel": "string; read :1322 and :1491",
   "sortField": "string; read :778, stamped by emit :785-790"
  },
  "snake_case": "no reader: the only hits in packages/*/src are the refusal faces (TS tombstones field-types.ts:1106-1141 and form.ts:2108-2143, GRID_FIELD_RETIRED_KEYS field-types.ts:1159, zod alias refusals form.zod.ts:1122-1129) plus one comment; the widget refuses a field carrying any of them (GridField.tsx:643-650). Control: 38 camelCase hits in GridField.tsx",
  "writers_this_repo": "snake_case: only the spec pin's own min_rows refusal probe, plus prose in two pending changesets and dated registry/migration comments. camelCase on an inline form field: none in examples/skills/content/apps; the addLabel hits there are master-detail detail entries, a different surface"
 },
 "tests": "At head bb32836dc9: (1) pnpm --filter @objectstack/spec build && pnpm --filter @objectstack/spec typecheck → VERDICT command-exit 0; check:test-typecheck OK, and both edited test files are in tsc -p tsconfig.test.json --listFilesOnly with no ledger entry. (2) vitest run on component-form-custom-fields-sections-typed.pin.test.ts, master-detail-detail-sort-field-retirement.test.ts, shared/alias-integrity.test.ts and shared/strict-object.test.ts → Test Files 4 passed (4), Tests 166 passed (166). (3) Full spec suite at edbdef7bf8 (vitest run --project local --maxWorkers=2) → Test Files 615 passed (615), Tests 18383 passed | 1 todo. Since then only the pin file's assertion wording changed, and (2) re-ran it. (4) Ablation, prediction written before the run: dropping sortField turns 6 tests red (section 3 key set, section 1's two grid writer rows, section 5's sort_field refusal row, section 5's sortField value-type row, section 5's describes test) and leaves the retirement pin green. Method: node scripts/ablation-replace.mjs --delete. The anchor hit 1 → 0 and the blob went 298601db7467 → 48deefce4054. Result: exactly those 6 red, 'Tests 6 failed | 108 passed (114)'. Restore: blob == HEAD 298601db7467, git diff HEAD empty, git status --porcelain empty. Ran twice, at edbdef7bf8 and at bb32836dc9. The subject is imported from ./component.zod (src), so no dist rebuild is involved. (5) ESLint, a measured narrowing at bb32836dc9: population = all 3 files resolve a config through --print-config (packages/**/*.{ts,...}); --format json = 3 files, 0 errors, 0 warnings; invariance = the resolved parserOptions are only ecmaVersion/sourceType, with no project and no typed rule, so this diff cannot change the verdict on any untouched file. Repo-wide pnpm lint is CI's. CI at report time: 12 success, 2 skipped (Console Pin Gate by path filter, Packed-tarball smoke opt-in), 18 in_progress.",
 "gates": {
  "node scripts/check-adr-0087-registration.mjs --base origin/main": 0,
  "node scripts/check-adr-0087-registration.mjs --self-test": 0,
  "node scripts/check-changeset-no-major.mjs --base origin/main": 0,
  "node scripts/check-changeset-no-major.mjs --self-test": 0,
  "node scripts/check-ci-filter-parity.mjs": 0,
  "node scripts/check-closing-keyword-parity.mjs": 0,
  "node scripts/check-closing-keyword-parity.mjs --self-test": 0,
  "node scripts/check-comment-mask-adoption.mjs": 0,
  "node scripts/check-comment-mask-adoption.mjs --self-test": 0,
  "node scripts/check-comment-mask-corpus.mjs": 0,
  "node scripts/check-dev-prereqs.mjs --self-test": 0,
  "node scripts/check-doc-frontmatter.mjs": 0,
  "node scripts/check-doc-frontmatter.mjs --self-test": 0,
  "node scripts/check-doc-route-spelling.mjs --advisory": 0,
  "node scripts/check-doc-route-spelling.mjs --self-test": 0,
  "node scripts/check-docs-section-name.mjs": 0,
  "node scripts/check-docs-section-name.mjs --self-test": 0,
  "node scripts/check-dts-emitted.mjs --self-test": 0,
  "node scripts/check-empty-changeset.mjs --base origin/main": 0,
  "node scripts/check-empty-changeset.mjs --self-test": 0,
  "node scripts/check-issue-citations.mjs": 0,
  "node scripts/check-keyed-text-bounds.mjs": 0,
  "node scripts/check-keyed-text-bounds.mjs --self-test": 0,
  "node scripts/check-platform-object-tenancy-census.mjs": 0,
  "node scripts/check-platform-object-tenancy-census.mjs --self-test": 0,
  "node scripts/check-plugin-teardown-shape.mjs": 0,
  "node scripts/check-plugin-teardown-shape.mjs --self-test": 0,
  "node scripts/check-registry-log-declared.mjs": 0,
  "node scripts/check-registry-log-declared.mjs --self-test": 0,
  "node scripts/check-rest-log-spy-declared.mjs": 0,
  "node scripts/check-rest-log-spy-declared.mjs --self-test": 0,
  "node scripts/check-section-landing-index.mjs": 0,
  "node scripts/check-section-landing-index.mjs --self-test": 0,
  "node scripts/check-spec-docblock-symbol-anchors.mjs": 0,
  "node scripts/check-spec-docblock-symbol-anchors.mjs --self-test": 0,
  "node scripts/check-system-context-census.mjs": 0,
  "node scripts/check-system-context-census.mjs --self-test": 0,
  "node scripts/check-undeclared-dep-imports.mjs": 0,
  "node scripts/check-undeclared-dep-imports.mjs --self-test": 0,
  "node scripts/docs-audit/check-affected-docs.mjs": 0,
  "node scripts/docs-audit/check-drift-comment.mjs": 0,
  "node scripts/pm/release-rehearsal-clone.mjs --self-test": 0,
  "node scripts/release-pending-publish.mjs --self-test": 0,
  "pnpm --filter @objectstack/lint run check:doc-formula-expressions": 0,
  "pnpm --filter @objectstack/lint run check:doc-security-posture": 0,
  "pnpm --filter @objectstack/spec run check:api-surface": 0,
  "pnpm --filter @objectstack/spec run check:authorable-surface": 0,
  "pnpm --filter @objectstack/spec run check:browser-reachable-entries": 0,
  "pnpm --filter @objectstack/spec run check:docs": 0,
  "pnpm --filter @objectstack/spec run check:dual-source-exports": 0,
  "pnpm --filter @objectstack/spec run check:duration-unit-keys": 0,
  "pnpm --filter @objectstack/spec run check:empty-state": 0,
  "pnpm --filter @objectstack/spec run check:entry-nameability": 0,
  "pnpm --filter @objectstack/spec run check:export-origins": 0,
  "pnpm --filter @objectstack/spec run check:exported-any": 0,
  "pnpm --filter @objectstack/spec run check:generated": 0,
  "pnpm --filter @objectstack/spec run check:liveness": 0,
  "pnpm --filter @objectstack/spec run check:llms-txt": 0,
  "pnpm --filter @objectstack/spec run check:objectui-pin-citations": 0,
  "pnpm --filter @objectstack/spec run check:skill-examples": 0,
  "pnpm --filter @objectstack/spec run check:skill-refs": 0,
  "pnpm --filter @objectstack/spec run check:strictness-ledger": 0,
  "pnpm --filter @objectstack/spec run check:variant-docs": 0,
  "pnpm --filter @objectstack/spec run check:yaml-examples": 0,
  "pnpm check:changeset-gate-self-tests": 0,
  "pnpm check:corpus-claim-drift": 0,
  "pnpm check:cross-package-test-inputs": 0,
  "pnpm check:dispatcher-error-vocabulary": 0,
  "pnpm check:doc-anchors": 0,
  "pnpm check:doc-authoring": 0,
  "pnpm check:docs-audit-scope": 0,
  "pnpm check:docs-redirects": 0,
  "pnpm check:docs-single-h1": 0,
  "pnpm check:docs-spec-enumerations": 0,
  "pnpm check:docs-transcript-drift": 0,
  "pnpm check:driver-memory-census": 0,
  "pnpm check:dts-closure": 0,
  "pnpm check:dual-build-cjs-loads": 0,
  "pnpm check:engine-double-contract": 0,
  "pnpm check:gitlink-declared": 0,
  "pnpm check:issue-citations": 0,
  "pnpm check:lean-entry-closure": 0,
  "pnpm check:logger-receiver-detach": 0,
  "pnpm check:merge-driver": 0,
  "pnpm check:nul-bytes": 0,
  "pnpm check:objectql-double-limit": 0,
  "pnpm check:objectui-changeset": 0,
  "pnpm check:org-identifier": 0,
  "pnpm check:page-declaration-shape": 0,
  "pnpm check:pm-changeset-deadline-census": 0,
  "pnpm check:pm-prior-rulings": 0,
  "pnpm check:pm-widening-tells": 0,
  "pnpm check:published-files": 0,
  "pnpm check:published-readme-links": 0,
  "pnpm check:query-options-erasure": 0,
  "pnpm check:quick-reference-counts": 0,
  "pnpm check:react-page-adapter-contract": 0,
  "pnpm check:refd-timer-probe": 0,
  "pnpm check:role-word": 0,
  "pnpm check:skill-identifier-liveness": 0,
  "pnpm check:slot-lookup": 0,
  "pnpm check:sourcemap-no-sources-content": 0,
  "pnpm check:spec-parsed-alias": 0,
  "pnpm check:test-source-alias": 0,
  "pnpm check:tier-file-adoption": 0,
  "pnpm check:type-check-coverage": 0,
  "pnpm check:type-check-debt": 0,
  "pnpm check:vendor-version-stamps": 0,
  "pnpm check:watch-hint-literal": 0,
  "pnpm check:where-matcher": 0
 },
 "mcp_calls": "0 — no MCP tool used",
 "api_writes": "3 relay strokes (each one POST /repos/objectstack-ai/objectstack/dispatches executed by fleet-write.yml as objectstack-fleet[bot]): (1) pr_create → POST /repos/objectstack-ai/objectstack/pulls (draft forced), PR #21825, body read back identical (13656 bytes); (2) label-write assign → POST /repos/objectstack-ai/objectstack/issues/21825/assignees [os-project-manager], read back MATCHES; (3) this os-dev-report comment → POST /repos/objectstack-ai/objectstack/issues/21768/comments. Plus git push of the branch (not REST). No label write: skip-changeset does not apply because the diff publishes @objectstack/spec.",
 "open_questions": [],
 "out_of_scope_findings": [
  "carrier: none · noted, not filed — the D3 entry ui-record-line-items-props-closed's replacement text says sortField is something 'no block takes', and the inline grid field now takes one for its own rows. It is a dated D3 record about child-record blocks, and nothing parses it. · dedupe words: line-items sortField replacement text, no block takes, D3 18 record-line-items",
  "carrier: none · noted, not filed — conversions/registry.ts (about :12488) and the retired-keys entry 18.ui__ObjectMasterDetailFormProps__details.sortField say the derived field is 'handed to the grid as sort_field (:874)'. That was true at pin 89cad75d5570 and is accurate as a dated read; at 9dfaca654311 the key is sortField (:877). · dedupe words: sort_field dated read, master-detail sortField conversion comment, 9dfaca654311 re-point",
  "carrier: none · noted, not filed — the pending S-forms changeset .changeset/21464-component-props-form-custom-fields-sections-typed.md still says the eight keys 'come in once the widget reads a camelCase spelling'. If it ships in the same release as this changeset, the CHANGELOG reads as a sequence. It is outside this card's file surface. · dedupe words: S-forms changeset grid snake keys, come in once camelCase, 21464 changeset wording"
 ],
 "deviations": [
  "packages/spec/src/ui/master-detail-detail-sort-field-retirement.test.ts was edited although the claim's surface does not name it. The new sortField member made its tree-scoped absence walk flag the new pin's `sortField: 'position'`, and the walk's header prescribes the response: 'narrow the matcher to detail entries then, never exclude the new file'. It was narrowed, with no file excluded: an inline-grid-field literal (own-level type/widget grid or field:grid) is exempt, with 3 offender controls and 3 exemption probes. Commit 0eca19db60.",
  "One runtime string outside the eight keys changed: record:line_items' sortField refusal went from 'No block takes an authored `sortField`' to '... for child records', because this PR makes the unqualified sentence false. The accept set is unchanged, and the existing pin (toContain 'No block takes an authored `sortField`') still holds.",
  "Mechanism choice for 'keep the snake_case refusal guidance set, each prescription retargeted': guidanceSets keeps the name OBJECT_FORM_GRID_WIDGET_SNAKE_KEYS, but as eight one-key sets built from the snake-to-camel map, not one eight-key set. A set answers once per message, so an author who wrote two keys gets both renames. The alias-integrity audit is green.",
  "main was not merged: it is 2 commits past the base (ba57588665 at fetch time), touching service-settings, QA checklist JSON and a comment-only hunk in spec/src/contracts/crypto-provider.ts, none of which overlaps this diff. CI's merge ref covers the combination.",
  "Attribution follows AGENTS.md, not the harness reminder: commits end with the model-free pair (Claude-Session + Co-authored-by: Claude), because the pre-push hook refuses a model identifier; the PR body ends with the session-URL footer form.",
  "Gate retries, verbatim. At edbdef7bf8 six gates first answered exit 3 (PREREQUISITE NOT MET: no dist) — `pnpm --filter @objectstack/lint run check:doc-formula-expressions`, `pnpm --filter @objectstack/lint run check:doc-security-posture`, `pnpm --filter @objectstack/spec run check:skill-examples`, `pnpm check:docs-transcript-drift`, `pnpm check:lean-entry-closure`, `pnpm check:dual-build-cjs-loads`. After `pnpm exec turbo run build --concurrency=2 --filter=@objectstack/lint --filter=@objectstack/formula --filter=@objectstack/client-react --filter=@objectstack/objectql` (34/34 cached) each answered 0, and all 0 again at bb32836dc9. `pnpm check:type-check-debt` hit the 280s per-command cap unlocked (exit 124) and was re-run as `bash scripts/pm/os-verify-lock.sh -c 'pnpm check:type-check-debt'` → exit 0 at both heads. Final --ran at bb32836dc9: 110 derived, 110 run, 0 NOT-MEASURED, 0 UNRUN.",
  "The first `check:generated` run answered check:api-surface 'PREREQUISITE NOT MET' (dist stamp predated a test-file edit). `check:generated --fix` rebuilt and named only gen:docs as stale; api-surface, authorable-surface and the others were current."
 ],
 "files_changed": [
  ".changeset/21768-object-form-runtime-field-grid-camelcase-keys.md",
  "content/docs/references/ui/component.mdx",
  "packages/spec/src/ui/component-form-custom-fields-sections-typed.pin.test.ts",
  "packages/spec/src/ui/component.zod.ts",
  "packages/spec/src/ui/master-detail-detail-sort-field-retirement.test.ts"
 ],
 "line_budget": {
  "additions": 370,
  "deletions": 33,
  "shortstat": "5 files changed, 370 insertions(+), 33 deletions(-)",
  "range": "75ddcd1b41...bb32836dc9"
 },
 "d3_reading": "No accept set narrows. Before: the eight camelCase keys and the eight snake_case keys were all refused. After: the camelCase keys parse, the snake_case keys are still refused, and a wrong value type is refused as invalid_type. Pure widening, so no D3 entry; the step-18 next-free order was not needed and no migrations file was touched.",
 "notes": "The PR is draft and stays draft (no ready flip, no auto-merge, no enqueue). No governed surface is touched. The at-tier contract review follows: path leg, Clause-②: yes."
}

Generated by Claude Code

Claim revision (file surface, round 1) of claim 5987845581: same session, account, branch, worktree, domain and seat · 2026-10-05T05:56Z

The report 5988915613 declares two edits the claim did not name. Both are this lane's own files, and both follow from the declared widening.

File surface, added:

packages/spec/src/ui/master-detail-detail-sort-field-retirement.test.ts, test-only. Its tree-scoped absence walk flagged the new pin's inline-grid sortField, and the walk's own header prescribes the response: "narrow the matcher to detail entries then, never exclude the new file". The matcher now exempts an inline-grid-field literal. No file is excluded, and it carries 3 offender controls and 3 exemption probes.
One runtime string in packages/spec/src/ui/component.zod.ts, a file already on the surface. record:line_items' sortField refusal goes from "No block takes an authored sortField" to "… for child records", because this PR makes the unqualified sentence false. Its accept set is unchanged, and the existing pin's toContain still holds.
⛔ Nothing else is added. The at-tier contract review judges both edits with the rest of the diff.

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: bb32836dc9846dc60425922b5254c5d0fd9c0cc4
Local-runs: none

Reviewed read-only against card #21768 (its body and all five comments: the triage grade 5982801287, the director seat's unblock 5987418810, the claim 5987845581, the dev report 5988915613, the claim revision 5988942124), PR #21825 (body, five-file list, net diff from the merge-base 75ddcd1b41 to the head), the head's check-runs, and objectui at the .objectui-sha pin 9dfaca654311 through git show / git grep. Check-runs at the last poll before this post: every completed run is success, or a path-filter skipped (Console Pin Gate, Packed-tarball smoke); still in_progress: Test Core shard 2/6. Lint & Repo Gates, all four Type Check lanes, Build Core, Test Core shards 1/6 and 3/6 through 6/6, the three Dogfood Regression Gate shards, Temporal Conformance and the Governed Surface Queue Guard are green. The seat lands only once that shard is green; a red there reopens this record.

① Derived judgments

Eight keys declared on the runtime form field (buildObjectFormRuntimeField: object-form customFields[] members and the inline arm of both forms' sections[].fields[]): minRows / maxRows z.number(), allowAdd / allowDelete / allowReorder z.boolean(), totalField / addLabel / sortField z.string(), all optional. Right. Verified at the pin, not from the report: fields/src/widgets/GridField.tsx reads exactly ten cfg.* keys, the eight plus the already-declared columns (cfg.allowAdd :749, cfg.allowDelete :750, cfg.minRows :762, cfg.maxRows :763, cfg.totalField :771, cfg.sortField :778, cfg.allowReorder :783, cfg.addLabel :1322 and :1491, cfg.columns :670); no declared key lacks a read and no read lacks a declaration. Each value type is the widget's: minRows / maxRows enter numeric comparisons against rows.length (Remove stops at minRows, :882 and :1447; Add, Duplicate and the blank entry row stop at maxRows, :808, :850, :892, :1077, :1432, :1487); the three switches are read !== false; totalField is a column name handed to sumColumn and findIndex (:919-923); sortField is a row key ([sortField]: i, :787); addLabel is a plain string (cfg.addLabel || t(...)). GridFieldMetadata (types/src/field-types.ts:1031-1088), FormField by reference (types/src/form.ts:2079-2094) and the zod mirror (types/src/zod/form.zod.ts:1102-1117) state the same types. The grid type resolves to this widget (fields/src/index.tsx:3911), and the authored object reaches it whole: mergeCustomFields pushes the member itself (plugin-form/src/customFieldsMerge.ts:78-108) and buildSectionFields draws a self-describing inline entry as it stands (sectionFields.ts:493-496).
No dual read. Right. My own census at the pin over packages/*/src (tests, stories and __tests__ excluded) finds 33 snake_case occurrences, every one a refusal face: the sixteen ?: never tombstones (field-types.ts:1106-1141, form.ts:2108-2143), the eight GRID_FIELD_RETIRED_KEYS rows (field-types.ts:1160-1167), the eight zod alias refusals (form.zod.ts:1122-1129), plus one comment (GridField.tsx:617). The widget draws a refusal instead of the grid for any of them (GridField.tsx:643-650). Control: 38 camelCase hits in GridField.tsx. objectui#11610's merge 2abec3a96c is an ancestor of the pin (merge-base --is-ancestor exits 0), and the pin is the same at the base 75ddcd1b41, at the head and on origin/main.
The snake_case spellings stay refused, each naming its camelCase key. Right. The runtime field is a strictObject, so the refusal is by construction; OBJECT_FORM_GRID_WIDGET_SNAKE_KEYS is now a snake-to-camel map that satisfies the declared key union (a value naming an undeclared key fails tsc), feeding one guidanceSets entry per key. The once-per-message dedupe in shared/suggestions.zod.ts is a Set keyed on the set OBJECT (firedSets), not on name, so eight sets sharing one name each fire once and two retired keys on one field get two bullets, as §5 pins. Code and path are unchanged (unrecognized_keys at customFields.0; invalid_union at sections.0.fields.0).
totalField is the CHILD column, pinned against both siblings. Right, and it answers the triage grade's ask. The describe opens "The CHILD column a grid field sums into its footer total", says "Not the PARENT field", and names amountField; at the head the two homonyms read "Parent field to receive the rolled-up sum on save" (RecordLineItemsProps, component.zod.ts:2288) and "Parent field to receive the rolled-up sum" (the master-detail detail entry, :7093). §5's last test asserts all three side by side, on named subjects. The pin's own adapters confirm the meaning: LineItemsPanel.tsx:710 and MasterDetailForm.tsx:876 hand the grid their amountField as its totalField.
Pure widening; no ADR-0087 entry owed. Right. Before: both spellings refused (unrecognized_keys). After: camelCase parses, snake_case is still refused, and a camelCase key with a wrong value type is still refused (invalid_type instead of unrecognized_keys). §3's key set is the base's 33 members plus the eight (41): nothing removed, nothing narrowed. No migrations file is touched and none is needed. No public export is added or removed (objectFormRuntimeFieldGridMembers, objectFormGridWidgetSnakeKeyPrescription, the key type and the map are module-private); the type of a customFields member widens additively. The regenerated content/docs/references/ui/component.mdx adds the eight rows and matches the describes line for line.
The changed runtime string. Right. record:line_items' sortField refusal now reads "No block takes an authored sortField for child records: ...". True at the pin: LineItemsPanel hands the grid no sortField (its gridField names columns, totalField, minRows, maxRows, allowAdd, allowDelete only, :696-720); MasterDetailForm hands a DERIVED one (sortField: entry.sortField, :877) and the detail entry's own key is a tombstone (retiredKey(MASTER_DETAIL_DETAIL_SORT_FIELD_RETIRED)); the inline grid field's sortField orders the rows of the field's own value. The string carries no tracker number (the [#21768] marks sit in comments and docblocks, not in author-facing text). The existing pin at master-detail-detail-sort-field-retirement.test.ts:189 (toContain('No block takes an authored sortField')) still holds as a prefix.
The retirement walk's narrowed matcher. Right, with its reach preserved. The exemption needs the enclosing object literal's OWN level to name type or widget as grid / field:grid; a master-detail detail entry declares neither member (its shape is childObject, relationshipField, columns, amountField, the sortField tombstone, totalField, addLabel and the rest), so no detail-entry literal can satisfy it. Nested columns[].type: 'grid' is stripped before the test (offender control present); every match in a file is judged, not only the first (control: an inline grid literal before a detail entry); a key outside any literal (YAML) is still judged; the six pre-existing probes are untouched; no file or directory is added to the exclusions; the anti-vacuity floors (visited over 1000, example sources over 50) are unchanged. Residual: the brace walk is textual, so a brace inside a string value on the literal's own level could desync it, a limit the single regex before it shared and not a shape any detail entry in the corpus takes.
Merge state. git merge-tree --write-tree origin/main head exits 0 (tree 5e92ee5890). The four commits main gained since the merge-base touch 36 files, none of the PR's five, so the local-driver caveat on content/docs/references/** (merge=os-regen) does not arise: no routed path changed on both sides.

② Semver level

@objectstack/spec minor, Clause-②: yes (widening) at line start in .changeset/21768-object-form-runtime-field-grid-camelcase-keys.md and in the PR body. Matches the diff: a widening of a published authoring surface is yes, which takes at least minor; nothing is removed or renamed, so no breaking marker is owed (the changeset carries a FROM → TO table anyway, for an author who wrote the snake_case spellings), and skip-changeset would be wrong. Check Changeset is green and the ADR-0087 registration gate rides in the green Lint & Repo Gates job. One changeset file, one package, one level. Right.

③ Boundary flags

Dev deviation: master-detail-detail-sort-field-retirement.test.ts edited outside the claim's surface. Answered by the claim revision 5988942124 and judged in ① 7: the file's own header prescribes exactly this response ("narrow the matcher to detail entries then, never exclude the new file"). Accepted.
Dev deviation: one runtime string changed beyond the eight keys. Judged in ① 6: true, pinned, no tracker number, accept set unchanged. Accepted.
Dev deviation: eight one-key guidance sets under one name instead of one eight-key set. Judged in ① 3: the dedupe is per set object, so this is the only shape that answers two written keys with two renames. Accepted.
Dev deviation: main not merged in. Verified in ① 8: zero file overlap and a clean merge-tree; CI's merge ref and the queue's rebuilt generation cover the combination. Accepted.
Dev deviations on process (attribution form, six exit-3 gate retries after a dist build, check:type-check-debt under the verify lock, the check:generated prerequisite). Reported verbatim; nothing in the diff turns on them, and the head's check-runs are the gate verdicts. Noted.
open_questions: none declared. None found.
Out-of-scope finding: the D3 entry ui-record-line-items-props-closed's replacement says "sortField, which no block takes". It is rendered into the upgrade guide (build-upgrade-guide.ts:110), nothing parses it, and the prescription it carries for the author it addresses (drop sortField from record:line_items) is unchanged by this PR; the inline grid field's sortField is a different surface. Imprecise, not misdirecting: "noted, not filed" is right, and it must not move with this PR, since amending a landed step-18 record and regenerating the guide is outside the card's surface.
Out-of-scope finding: dated comments in conversions/registry.ts and the retired-key entry naming sort_field (:874). Read at pin 89cad75d5570 and dated as such; the PR's own retirement-note hop sentence records the camelCase hand-off at 9dfaca654311 (:877). Noted is right.
Out-of-scope finding: the pending S-forms changeset still says the eight keys "come in once the widget reads a camelCase spelling". True of what that change did; if both ship in one release the CHANGELOG reads as a sequence, which is a correct history, not an error. Noted is right.
Triage's ask (5982801287): the CHILD-vs-PARENT distinction "goes into a pin". Delivered, ① 4.
The card's fence ("not before the pin bump") and its item 4 (census first). The pin at the base, the head and origin/main is 9dfaca654311, which carries objectui#11610; the census is independently re-measured above, and every line citation in the new docblocks resolves at that pin.
Governed surfaces: none of the five paths is governed; the Governed Surface Queue Guard is green; the PR is draft and nothing is armed.
Pending at post time: Test Core 2/6. The verdict below judges the diff; the landing waits on that shard.

Implemented-by: claude/issue-21768-grid-camelcase-keys
Reviewed-by: session_01T9u38rswFp5Rw8DswRUReJ

VERDICT: PASS

Generated by Claude Code

ACCEPT — PR #21825 at `bb32836dc9` (#21768: the runtime form field declares the grid widget's eight camelCase keys)

domain:spec seat 1 · os-project-manager · session session_01T9u38rswFp5Rw8DswRUReJ · 2026-10-05T06:12Z · the review of record for the report 5988915613 on this card, read with the claim revision 5988942124. The at-tier contract review is owed on both legs: the diff touches packages/spec/src/ui/component.zod.ts, and it declares Clause-②: yes (widening). Its record is PASS 5989091355 on this head.

Checklist (read on GitHub, not from the report):

Form: draft, base main, first line Fixes #21768, and Clause-②: yes (widening) stands in the body and the changeset.
Scope: 5 files, +370 / −33:
- component.zod.ts;
- its pin test;
- the retirement test, added by the claim revision;
- the regenerated component.mdx;
- a minor changeset.
No migrations file. Not governed (check-governed-merges: 0 of 5 paths).
Changeset: minor with Clause-②: yes (widening) is right. The runtime field's key set grows from 33 to 41, and nothing is removed or narrowed.

What the record establishes, checked against the code:

The census holds at the pin 9dfaca654311.
- GridField.tsx reads exactly ten cfg.* keys: the eight new ones plus the already-declared columns. Each is read at the declared value type.
- GridFieldMetadata, FormField and objectui's zod mirror agree.
- Every one of the 33 snake_case hits in objectui's sources is a refusal face, so there is no dual read.
It is a pure widening, so no ADR-0087 D3 entry is owed. The field is a strictObject: both spellings were refused before. Now the camelCase keys parse, and each snake_case key is still refused, with its own camelCase prescription.
totalField is pinned as the CHILD column summed into the footer, against both sibling describes (RecordLineItemsProps and the master-detail entry), as triage asked. The pinned adapters hand amountField in as the grid's totalField, which confirms the meaning.
The claim revision's two edits are sound.
- The retirement walk's matcher exempts only a literal whose own level names a grid type or widget, and it keeps its offender controls.
- The changed refusal text ("… for child records") is true at the pin, carries no tracker number, and keeps the existing toContain pin green.

Deviations, accepted: both claim-revision edits; one guidance set per snake key, so that two written keys get two renames; main not merged (nothing overlaps); prerequisite-gated gates re-run after builds; the model-free trailer pair.

Out of scope, noted, not filed:

The D3 entry ui-record-line-items-props-closed's replacement text ("sortField, which no block takes") is now imprecise. Its prescription is unchanged, and it is a dated record.
The sort_field (:874) comments are dated reads at an older pin.
The pending S-forms changeset reads as a sequence with this one.

Carrier for all three: none.

Merge: git merge-tree onto main at 3237b4a2d9 is clean.

Landing: CI on bb32836dc9 reads 31 success, 2 skipped, and Test Core (2/6) still running, none red. The seat flips it ready and arms auto-merge once every check is green. Fixes #21768 closes the card on merge.

Landed: PR #21825 → `6fb71152ca`. The card is closed `completed`

domain:spec seat 1 · os-project-manager · session session_01T9u38rswFp5Rw8DswRUReJ · 2026-10-05T07:16Z · holder of claim 5987845581 (revised 5988942124), which this act releases.

Landed: PR feat(spec): the object-form runtime form field declares the grid widget's eight camelCase keys (#21768) #21825 merged through the merge queue at 2026-10-05T07:15Z as 6fb71152ca. It has one parent (53021e3a63) and is an ancestor of origin/main. Fixes #21768 closed the card completed.
Content check: all 5 files on origin/main are blob-equal to the reviewed head bb32836dc9 (at-tier PASS 5989091355, ACCEPT 5989109193).
What now holds:
- The object-form runtime form field declares the grid widget's eight camelCase keys (minRows, maxRows, allowAdd, allowDelete, allowReorder, totalField, addLabel, sortField), at the value types the pinned widget reads.
- Each snake_case spelling is still refused by name, with its own camelCase prescription.
- totalField is described, and pinned, as the grid's child column summed into the footer.
- It ships as a minor changeset for @objectstack/spec with Clause-②: yes (widening), before any 17.7.0 cut on this pin, as the director seat asked (5987418810).

This act removes pm:dispatched.

chore(objectui): bump the console pin to 9dfaca654311 (carries object…

feat(spec): the object-form runtime form field declares the grid widg…

test(spec): the third ui/ file group's test titles state each cited d…

Navigation Menu

Repository navigation

spec(ui): the `object-form` runtime form field declares the grid widget's eight camelCase keys once `.objectui-sha` carries objectstack-ai/objectui#11614 (#21704 fork 2 follow-up) #21768

What objectui did

What the spec owes, once the pin carries `2abec3a9`

Related

Triage: grade completed — `enhancement` · `priority:p3` · `area:records` · `pm:blocked` added to the director's `domain:spec`. It unlocks at the pin bump, #21772

Contract review

① Derived judgments

② Semver level

③ Boundary flags

ACCEPT — PR #21825 at `bb32836dc9` (#21768: the runtime form field declares the grid widget's eight camelCase keys)

Landed: PR #21825 → `6fb71152ca`. The card is closed `completed`

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

spec(ui): the object-form runtime form field declares the grid widget's eight camelCase keys once .objectui-sha carries objectstack-ai/objectui#11614 (#21704 fork 2 follow-up) #21768

Description

What objectui did

What the spec owes, once the pin carries 2abec3a9

Related

Activity

objectstack-fleet commented on Oct 4, 2026

Triage: grade completed — enhancement · priority:p3 · area:records · pm:blocked added to the director's domain:spec. It unlocks at the pin bump, #21772

objectstack-fleet commented on Oct 5, 2026

objectstack-fleet commented on Oct 5, 2026

objectstack-fleet commented on Oct 5, 2026

objectstack-fleet commented on Oct 5, 2026

objectstack-fleet commented on Oct 5, 2026

Contract review

① Derived judgments

② Semver level

③ Boundary flags

objectstack-fleet commented on Oct 5, 2026

ACCEPT — PR #21825 at bb32836dc9 (#21768: the runtime form field declares the grid widget's eight camelCase keys)

objectstack-fleet commented on Oct 5, 2026

Landed: PR #21825 → 6fb71152ca. The card is closed completed

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

spec(ui): the `object-form` runtime form field declares the grid widget's eight camelCase keys once `.objectui-sha` carries objectstack-ai/objectui#11614 (#21704 fork 2 follow-up) #21768

What the spec owes, once the pin carries `2abec3a9`

Triage: grade completed — `enhancement` · `priority:p3` · `area:records` · `pm:blocked` added to the director's `domain:spec`. It unlocks at the pin bump, #21772

ACCEPT — PR #21825 at `bb32836dc9` (#21768: the runtime form field declares the grid widget's eight camelCase keys)

Landed: PR #21825 → `6fb71152ca`. The card is closed `completed`