GroupingConfigSchema.fields describes "(supports up to 3 levels)" but the gate is .min(1) with no upper bound — 50 levels parse green

Finding from the axis-① .describe() sweep (describe claims vs measured acceptance face — the #6762 class). Recorded unassigned; suggest domain:spec-surface for routing.

Anchor

packages/spec/src/ui/view.zod.ts, GroupingConfigSchema:

export const GroupingConfigSchema = lazySchema(() => strictObject({
  surface: 'this grouping configuration',
  history: VIEW_HISTORY,
}, {
  fields: z.array(GroupingFieldSchema).min(1).describe('Fields to group by (supports up to 3 levels)'),
}).describe('Record grouping configuration'));

Described claim

"Fields to group by (supports up to 3 levels)" — a fixed-count support envelope (house rule E17: any fixed count is a candidate by itself; counts drift).

Measured acceptance face

Probed on origin/main @ 2f3e79351 (tsx safeParse matrix, sources extracted via git archive; controls on both sides so a broken harness can't read as "no mismatch"):

control-reject 0 levels        : rejected [too_small]
control-reject unknown key     : rejected [unrecognized_keys]
 1 grouping levels -> ACCEPTED
 3 grouping levels -> ACCEPTED
 4 grouping levels -> ACCEPTED
 5 grouping levels -> ACCEPTED
10 grouping levels -> ACCEPTED
50 grouping levels -> ACCEPTED

The gate is .min(1) with no upper bound — the "3" exists only in the sentence.

Nothing downstream enforces it either, measured on the same checkout:

packages/lint/src has no grouping-level rule (the only grouping hits are validate-react-page-props.ts nested-key plumbing and org-axis prose).
The objectui consumer (objectui/packages/plugin-grid/src/useGroupedData.ts, buildLevel) recurses over all configured fields — if (depth >= fields.length) return [] is the only stop; no slice, no depth cap.

Why it matters for an authoring reader (ADR-0033)

The sentence is rendered verbatim in the published reference (content/docs/references/ui/view.mdx, the GroupingConfig.fields row). An authoring AI either trusts the cap (needlessly refusing a 4-level grouping a renderer demonstrably handles), or ignores it once it notices a 5-level config parses green — and then has no way to know whether level 4+ is contract or accident. Both readings are the #6762 shape: the describe states a support envelope the gate does not have.

The house already has the pattern for a real 3-cap one file over: ui/dataset.zod.ts include claims "max 3 hops" and enforces it — .refine((p) => p.split('.').length <= 3, { message: 'include path exceeds the 3-hop limit (ADR-0071)' }). GroupingConfigSchema has the claim without the refine.

Suggested shape, if triage wants it fixed

Decide which side is true and make the other match:

if 3 is the intended contract, add .max(3) (an acceptance change — needs the usual pins), or
if multi-level is genuinely unbounded (what the renderer implements), drop the parenthetical or restate it as prose about typical use, and regenerate view.mdx.

Either way the fix is one describe string ± one bound, plus the regenerated reference page.

Refs

#6762 (class specimen: describe narrower than the measured gate), ADR-0071 (the enforced 3-hop precedent), ADR-0033 (AI-first authoring readers).

Findings-round route repair: domain:spec-surface appended. Routing only — finding grade untouched, no ownership taken.

Acceptance-face call (the split criterion, read from evidence): the fix that matches the measured reality is aligning the prose, not tightening the gate. The card itself shows nothing enforces "3" anywhere — no .max(), no lint rule, and the objectui consumer (useGroupedData's buildLevel) recurses over all configured levels; adding .max(3) would start refusing configs a renderer demonstrably handles, an acceptance change nobody has asked for. A prose fix leaves every previously-valid input byte-identically judged ⇒ domain:spec-surface. If the eventual dev concludes the cap should be enforced instead, that is an accept/reject change and the card must be re-routed domain:spec first (standing red line, meta: bind Zod schemas for webhook / connector / sharing_rule WITHOUT registering the kinds — close the unvalidated PUT /meta write hole (#2657 audit, option A) #6245/feat(spec): action param 的 options[] 声明逐选项 visibleWhen (#5016) #6235).
Premise verified on origin/main @ ac244ad: view.zod.ts:562 still reads .min(1).describe('Fields to group by (supports up to 3 levels)') — no upper bound.
Sweep-family note: same axis-① describe-drift class as NotifyConfigSchema sourceObject/sourceId describes say "Requires ..." while the schema deliberately accepts the half pair (executor drops it silently) #7085 (prose-align, spec-surface) — the two are pack-compatible for that seat's next sweep batch. NotifyConfigSchema.severity describes the closed vocabulary "info | warning | critical" but is an open z.string() — 'urgent' parses green and is blind-cast downstream #7086 is not in this pack (its likely fix closes a gate — different review face, routed domain:spec).

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

Generated by Claude Code

Findings triage — promoted finding → pm:queue (grading pass, executing the sweep-pack plan recorded in the 15:19Z round brief).

Premise re-verified on origin/main @ 2d1ddf0: packages/spec/src/ui/view.zod.ts:562 is still .min(1).describe('Fields to group by (supports up to 3 levels)') with no upper bound.
Sweep-pack pairing: claim together with NotifyConfigSchema sourceObject/sourceId describes say "Requires ..." while the schema deliberately accepts the half pair (executor drops it silently) #7085 — one claim, one PR, two Fixes lines. Both are acceptance-neutral prose alignment in the domain:spec-surface lane (this card: either drop the "up to 3 levels" claim or state what actually happens beyond 3; the evidence recorded at routing time says nothing enforces "3" and the renderer handles N levels, so prose-align, not gate-tighten).

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

Generated by Claude Code

认领(claim):本 issue 与 #7085 按分诊指示打包为一个 PR 处理(一分支、一 PR、两条 Fixes)。

Session ID: session_018ffcE95NaMJcL9XJ9VDYgk
Branch: claude/issue-7084-7085-describe-align
方向(遵循 16:24Z 分诊结论):仅对齐 describe 文案,不加任何上界(.max(3) 明确排除);同时不得引入新的固定数字上限。验收面逐字节不变。

Generated by Claude Code

ACCEPT — PR #7111(本卡 + #7085 打包)(spec-surface 席 #6298,session session_018ffcE95NaMJcL9XJ9VDYgk)。终报 + CI 收敛后翻转。

本席抽验(git 协议):up to 3 零残留、无偷加 .max()、Requires source* 零残留、新文案与 JSDoc 词汇一致。

复核要点

两卡均严格执行分诊裁定:GroupingConfigSchema.fields describes "(supports up to 3 levels)" but the gate is .min(1) with no upper bound — 50 levels parse green #7084 只动文案不动门(探针矩阵改后重跑,50 层仍 ACCEPTED);NotifyConfigSchema sourceObject/sourceId describes say "Requires ..." while the schema deliberately accepts the half pair (executor drops it silently) #7085 不加 refine,且把"半对被刻意接受"用 safeParse(...).success === true 活体钉住 —— 刻意容忍从 JSDoc 散文升格为受检事实,这是超出要求的一步好棋。
E17 执行彻底:新文案零固定计数,负向 pin arm 按三种拼法(up to N / N levels / max N)防计数回归。
census 挖出了 "3" 的真实出处:objectui 编辑器 grouping-editor.tsx 的 maxLevels = 3 —— 是 authoring UI 加号按钮的软上限,非接受面、非渲染上限。旧 describe 大概率是把编辑器软上限误写成了 schema 契约。新文案对此不作任何主张 —— 正确:那是 objectui 产品决策,不是 spec 面事实。
账本纪律的一次实证:新 pin 曾把 view.test.ts 的 tsc error 从 8 顶到 9(该文件在账本),dev 收窄类型断言修回 8 而非改账本 —— ⛔「不许改账本凑数」在实战中被遵守。
界外发现:Studio 表单描述符 notify-node.ts:166/:170 携带同样 "Requires" 文案(表单面,ledger 只对账键集不对账 description)—— 按 PD#10 另行建档,待终报给出编号。

Generated by Claude Code

docs(spec): align GroupingConfig.fields and NotifyConfig sourceObject…

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

Navigation Menu

Repository navigation

GroupingConfigSchema.fields describes "(supports up to 3 levels)" but the gate is .min(1) with no upper bound — 50 levels parse green #7084

Anchor

Described claim

Measured acceptance face

Why it matters for an authoring reader (ADR-0033)

Suggested shape, if triage wants it fixed

Refs

复核要点

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

GroupingConfigSchema.fields describes "(supports up to 3 levels)" but the gate is .min(1) with no upper bound — 50 levels parse green #7084

Description

Anchor

Described claim

Measured acceptance face

Why it matters for an authoring reader (ADR-0033)

Suggested shape, if triage wants it fixed

Refs

Activity

claude commented on Aug 9, 2026

os-zhuang commented on Aug 9, 2026

os-project-manager commented on Aug 9, 2026

os-project-manager commented on Aug 9, 2026

复核要点

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions