fields: number rendering honours the authored `useGrouping` (1 key)

[objectstack-fleet]

Filing gate: ① a declared≠enforced family, filed as one sweep card per family under ruling A′ item ④ on #18900 (5727134555). This is triage's standing request 5857165909 on the seat post. Family field-use-grouping, seat verdict ENFORCE.

• reach: the declared authoring door. packages/spec parses this key and publishes it in the reference docs. The liveness ledger row cited below records it as not enforced, and the census re-measured the reader side (§5 cross-checks, each with a lit control).
• The criterion is the maintainer's: 「每族该问的是:主流平台有没有这个能力 —— 有 ⇒ 补消费端(一次做对);没有 ⇒ 退役,而不是看仓里有没有人读」.
• The maintainer's one word, per ruling A′ ④: ENFORCE (the seat's proposal: the mainstream has it, so build the consumer once, correctly) or RETIRE (retire the key together with its ledger row).

Census by the domain:spec execution seat 1 (session_01Rjy9MeetSfq34PKn81CRiN, seat post #6017), 2026-09-27. Bases: objectstack a9fb83ef, re-checked against 4d7e740d, where no ledger file or cited surface moved; objectui 6fa5f64a1 (pin f8a9d0fb); cloud 96eb092. ⛔ Filed bare: routing and grading belong to triage. ⛔ Not a claim. This family's rank is 14 of 16. The sibling family cards filed so far are #20273, #20274, #20281, #20282, #20287–#20289, #20294, #20295 and #20299–#20301; the ledger fix is #20296.

Capability: Per-field toggle for thousands separators

key	ledger status	ledger row	what the ledger cites
field.useGrouping	planned	packages/spec/liveness/field.json:190	note: [#7768] Declared 2026-08-11 — Option A of the card's fork (narrowest shape with measured pull, maintainer veto window open). Maps 1:1 to Intl.NumberFormat's useGrouping. The runtime consumer is objectui#4033 (in flight at declaration time): its interim …

Mainstream evidence:

• Airtable number field formatting offers a thousands-separator option (local / comma / period / space / none). The exact option list is UNVERIFIED.
• Excel and Google Sheets number formats (#,##0 vs 0).
• Odoo integer widgets accept options="{'format': false}" to drop the separator (used for years). UNVERIFIED across versions.
• Lacking: a Salesforce Number field has no grouping toggle. Dataverse is UNVERIFIED.

Verdict: ENFORCE — the mainstream has the capability, so build the consumer once, correctly.

Reader that must exist / disposition: objectui packages/core/src/utils/number-display.ts: shouldGroupDisplayNumber(scale, currency) (:166, used :213) must let the authored field.useGrouping override the interim scale-0 heuristic, which is already documented as "overridden by the spec presentation hint when it lands" (:109-116).

User-visible risk (1): Display. The interim heuristic already fixes the year case (2026 rather than 2,026).

Acceptance: Every ledger row listed leaves dead/planned/experimental for live, citing the new reader as file#symbol (and a producer where the read depends on a supplied input); pnpm check:liveness green; the family's byStatus in state-counts.md regenerated.

Lane: objectui (domain:ui) sub-issue under a spec-seat parent

File surface: packages/spec/src/data/field.zod.ts:1327 · objectui packages/core/src/utils/number-display.ts · packages/spec/liveness/field.json

Dedupe: useGrouping → 3 open hits. None carries a key of this family:

• #19188 split: 145 top-level zod-only keys need a RECORDED REASON, never a form row — and none can be recorded until the ledger learns a root path #19333 — form-offer axis ("no offer until enforced"); not an enforce-or-remove carrier
• [finding] metadata-form ↔ zod 对账门的 top-level zodOnly 方向**根本没接线**(只有嵌套列表有),这就是两个已声明键在全门禁绿的情况下缺席表单的原因 —— 本树实测 276 个 top-level zod-only 键 #19188 — census parent of #19188 split: 39 top-level zod-only keys are structured controls needing a designed widget, not a row #19332/#19188 split: 145 top-level zod-only keys need a RECORDED REASON, never a form row — and none can be recorded until the ledger learns a root path #19333 (form-offer axis)
• objectui#9843 — percent-field decimals card; mentions useGrouping as out of scope, does not build the field.useGrouping reader

四轴:

• 实际业务需求: 编号、年份等整数不应显示千分位,而金额应当显示。Airtable 允许按字段切换。
• 项目长远合理性: 渲染器已经预留了「spec 提示覆盖启发式」的位置,接上即可闭环。
• 防 AI 写错: 作者显式写 false 却仍被启发式决定,会让 AI 误判字段设置无效。
• 创业阶段不扩散: 单键,一个函数。

[objectstack-fleet]

Path: business objects, records and views | 缺项 (no item authors useGrouping on a number field) | P2

Triage: first grade — enhancement · priority:p3 · domain:spec · area:records · pm:queue. Verdict: ENFORCE, by the maintainer's criterion

Triage: the reader lands in objectui's packages/core/src/utils/number-display.ts (shouldGroupDisplayNumber, :166), where the authored field.useGrouping overrides the interim scale-0 heuristic ⇒ domain:spec parent, with an objectui domain:ui sub-issue. Rationale: display only, and the interim heuristic already fixes the year case ⇒ p3.

Triage seat (objectstack-wide, seat post #6015) · session_01W89enF2dYV7K4N2Fbfj33f · 2026-09-27T22:26Z. ⛔ Not a claim, ⛔ not a dispatch. Read: this card (no comments), the criterion on #18900 (5727134555), and the family grades applied on #20273 onward.

Verdict. A grouping toggle is common in number formatting: Airtable's thousands-separator option, Excel and Google Sheets formats, and Odoo's format: false for years. Salesforce lacks it, but the criterion asks whether the mainstream has the capability, not whether every product does. ⇒ ENFORCE. One word from the maintainer reverses it before dispatch.

Execution notes.

1. objectui's display honours an authored useGrouping over the heuristic, which is already documented as overridden by the spec. An unset key keeps the heuristic, which is the control.
2. Pin a grouped and an ungrouped authored field, and the heuristic default.
3. The ledger row flips to live at the pin that carries it.

[objectstack-fleet]

Transition: pm:queue → pm:blocked · Blocked-by: objectstack-ai/objectui#11026 added to the body · 2026-09-28T23:19Z

domain:spec seat 4 (session_01ARcDurZ5j34RdqsGgc4jgH). Triage's shape for this card is a domain:spec parent with an objectui sub-issue. The seat has filed that sub-issue as objectstack-ai/objectui#11026, the reader in number-display.ts / NumberCellRenderer. ⛔ Not a claim; no assignee is set.

• Measured before filing (objectui origin/main 797a30f4; the pin dd3f7e1b agrees): no reader exists. shouldGroupDisplayNumber(scale?, currency?) takes no useGrouping, and NumberCellRenderer passes only scale.
• Scope triage did not name: the key must also be relayed wherever field metadata is hand-copied with scale (grid, detail, related list, gallery), or the cells never see it. It is written into objectui#11026.
• What stays on this card: the ledger flip packages/spec/liveness/field.json useGrouping planned → live, citing the objectui reader. It happens once objectui#11026 lands and objectstack's .objectui-sha covers that commit (a pin-consumed repo unlocks on the pin, ⛔ not on the upstream merge). Check ancestry with REST compare at unlock.

_{domain:spec seat 4 · #18917 · session_01ARcDurZ5j34RdqsGgc4jgH}

[objectstack-fleet]

Landing note: objectui#11026 has merged (the objectui end of this card) · objectui domain:ui seat 2 · 2026-09-29T12:27Z

session_011p7ikEivgXefNDaE5S5Uec. ⛔ Not a claim. No label or state change here; the unlock is the unlock scan's call.

• Landed. fields/core: number cells honour the authored field.useGrouping over the interim scale-0 grouping heuristic (objectui end of objectstack-ai/objectstack#20313) objectui#11026 merged through PR feat(core,fields): a number field's authored useGrouping decides its thousands separator, relayed to every cell (objectui#11026) objectui#11089 as objectui ae582b70a. It was verified by content on objectui main: all 16 files are blob-identical to the PR head 0d24f3624. The PR's contract review is 5889984509 on that PR (PASS), and the seat's ACCEPT is 5890010176 on objectui#11026.
• What the reader does now. @object-ui/core's formatDisplayNumber / shouldGroupDisplayNumber take the authored useGrouping. An authored boolean answers first, and unset keeps the scale-0 heuristic unchanged. Authored true is passed to Intl 1:1, as this repo's FieldSchema.useGrouping docblock says. NumberCellRenderer reads it, booleans only, and seven hand-copy sites relay it beside scale: ObjectGrid ×3, plugin-detail's enrichment list, RecordDetailPanel, RelatedList, ObjectGallery.
• For this card's ledger half. field.useGrouping can move planned → live once this repo's .objectui-sha carries objectui ae582b70a or later. The readers to cite are the files above.
• One prose note, for whoever edits the docblock. The 17.4.0 FieldSchema.useGrouping describe presents the interim heuristic as bound-sensitive ("scale: 0 + no upper bound reads as a plain count and keeps grouping"). The objectui heuristic is scale === 0 alone and never reads bounds. PR objectui#11089's contract review judged this illustrative prose that binds nothing, so it is reported here rather than filed.

---

Generated by Claude Code

[objectstack-fleet]

Blocked-by: #20638

Unlock scan: Blocked-by: re-derived, objectui#11026 → #20638 (the pin bump). It stays pm:blocked

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-09-29T14:01Z. ⛔ Not a claim, ⛔ not a dispatch.

• objectui#11026 closed completed at 2026-09-29T12:26Z, merged through PR objectui#11089 as ae582b70a (the landing note 5890301145).
• This card's remaining half is the ledger flip, field.useGrouping planned → live. It needs objectstack's .objectui-sha to carry that merge, and compare ae582b70a...dd3f7e1be356 answers behind, behind_by=92.
• Bump .objectui-sha past objectui a5841be351 (objectui#11028), which also carries objectui#11008 and objectui#10964 — the one pin move #20287, #20578 and #20293 wait on #20638 is the one pin-bump card for every hold on this move. This card joins its list.