finding: four more private copies of the reference-bearing field family (kanban, detail x2, resolveActionParams) — each missing `user`/`tree` and each carrying the undeclarable `reference`

[claude]

Measured while implementing #5692 (the two plugin-dashboard copies). Out of that card's fence, which is the two plugin-dashboard files plus their tests — filed rather than widened into a cross-package diff.

What is there

@object-ui/core's EXPANDABLE_FIELD_TYPES (packages/core/src/utils/expand-fields.ts) is the published reference-bearing field family. Four MORE faces restate it inline, none deriving from it and none pinned against it:

file	the restatement
packages/plugin-kanban/src/ObjectKanban.tsx:346	def?.type === 'lookup' || def?.type === 'master_detail' || def?.type === 'reference'
packages/plugin-detail/src/RecordDetailDrawer.tsx:227	def.type === 'lookup' || def.type === 'master_detail' || def.type === 'reference'
packages/plugin-detail/src/HeaderHighlight.tsx:147	resolvedType === 'reference' || resolvedType === 'lookup' || resolvedType === 'master_detail' (inside a wider isWide disjunction)
packages/app-shell/src/utils/resolveActionParams.ts:489	resolvedType === 'lookup' || resolvedType === 'reference'

Why it is not merely duplication — every one of them diverges in BOTH directions

	core	these four
lookup	yes	yes
master_detail	yes	yes (3 of 4; resolveActionParams omits it)
user	yes	no
tree	yes	no
reference	no	yes

Two concrete consequences, same shape #4790 recorded for the form layer:

• user is missing from all four. A user column carries the same foreign-key storage as lookup and resolves through the same expand path (the reason fix(core): $expand user/tree reference columns in list & grid views (not just lookup/master_detail) #2032 put it in the family). On these faces it is not treated as a relation.
• reference is present in all four, and no producer can emit it. Measured on finding(plugin-dashboard): two more private copies of the reference-bearing field family — #5312's "LAST private copy" claim is false #5692's branch against @objectstack/spec's closed FieldType vocabulary, with lookup / master_detail / user / tree as live controls and the retired owner plus a nonsense spelling as dead ones: reference is absent from the vocabulary and FieldSchema.safeParse({ type: 'reference' }) is refused. It sits at exactly the level owner sat at before owner widget 拿不到表单下发的 dataSource,而 plugin-grid 认为它需要 —— 且 owner 根本不在 spec 的 FieldType 里(enforce-or-remove 待判) #4814 retired it. So these four branches are dead weight that reads as live capability.

Deliberately NOT this issue

• packages/app-shell/src/views/ActionParamDialog.tsx:351 — a different rule (degraded-hint, not reference-bearing) and already filed as finding(app-shell): ActionParamDialog's isLookupParam restates the picker family over RAW param spellings, so a degraded master_detail param loses the #3405 affordances #5654.
• The two plugin-dashboard copies — finding(plugin-dashboard): two more private copies of the reference-bearing field family — #5312's "LAST private copy" claim is false #5692.

Direction

Same treatment as #4770 / #4790 / #4815 / #5312 / #5692: read EXPANDABLE_FIELD_TYPES and carry an identity pin (a spy on its .has) so a member-identical private copy fails rather than quietly re-forking. Each face needs its own call on whether gaining user / tree is the intended behaviour there — on the four above it looks like restoration rather than widening, but that is a per-face judgement and this card does not pre-empt it. Do NOT copy the set.

Related: #4770, #4790, #4815, #5312, #5692, #5654, #4914.

---

Generated by Claude Code

[claude]

Finding concentration round (triage seat, session session_01Kktexqp6uVuFMztvvTMf3V, 2026-08-24, maintainer-invoked): promoted → pm:queue (domain:ui), Task. Converge the four restatements (kanban, detail ×2, resolveActionParams) onto EXPANDABLE_FIELD_TYPES and pin each against the canonical set — each site also gains the user/tree members it is missing and sheds the undeclarable reference special-casing per the family's canonical home. Fold candidate with #5875 (the false "fourth and last" claims — one PR can fix the copies AND the claim); ui seat answers fold-or-serial in the chain-head claim.

---

Generated by Claude Code

[yinlianghui]

Claim: PM loop round 38 (refill slot) — CHAIN HEAD, folded with #5875
Session: session_01CSoz9uGhaaSgiq3hshtN7L
Branch: claude/issue-5874-expandable-field-family-convergence
Worktree: objectui-issue-5874
Domain: domain:ui
File surface: packages/plugin-kanban/src/ObjectKanban.tsx, packages/plugin-detail/src/RecordDetailDrawer.tsx, packages/plugin-detail/src/HeaderHighlight.tsx, packages/app-shell/src/utils/resolveActionParams.ts, packages/app-shell/src/utils/paramToField.ts + .test.ts (the #5875 prose), their tests, + a changeset. ⛔ packages/core/src/utils/expand-fields.ts is READ-ONLY — it is the canonical home and #5692 already corrected it.
Container & model: L, mode:subagent, model: opus
Clause-②: yes — each face's accepted field set changes (gains user/tree, sheds reference), which is a behaviour change a host can observe. Declared; Opus under this seat's recorded Fable-quota exemption.
Serial constraints cleared: all five files free. Concurrent siblings: #5903 (packages/types + packages/plugin-gantt), #5725 (packages/app-shell/src/views/metadata-admin/previews/ — ⚠️ same package, different subtree; you are in src/utils/, ⛔ stay out of views/), #5676 (packages/data-objectstack), #5883 (apps/console/src/components/FormPage.tsx).

⛔ FOLD RULING — triage asked the ui seat to answer fold-or-serial; the answer is FOLD

Triage, 2026-08-24: "Fold candidate with #5875 (the false 'fourth and last' claims — one PR can fix the copies AND the claim); ui seat answers fold-or-serial in the chain-head claim."

Folded. Five gates, answered:

① Same defect shape — and tighter than usual. #5875's false claim is about the very copies #5874 converges. Fixing the copies changes the count the claim states, so landing #5874 alone leaves paramToField.ts asserting "fourth and last" while the true answer has just moved again — wrong a second time, in the file the next consolidation reads first. ⭐ That is not a coincidence of timing; it is the same defect at two levels (the copies, and the record of how many there are).
② One changeset, one family, one canonical home.
③ Both graded pm:queue / Task in the same 2026-08-24 concentration round; neither is in the decision box.
④ Independently checkable — #5874 by identity pins, #5875 by grep on the prose.
⑤ Exclusion list: #5692 is landed (it corrected the canonical home); #5654 is a different rule (degraded-hint, not reference-bearing) and stays out; #5312 / #4770 / #4790 / #4815 are prior landed sweeps. Neither card is claimed by another session.

Fixes #5874 and Fixes #5875 both.

The convergence

@object-ui/core's EXPANDABLE_FIELD_TYPES (packages/core/src/utils/expand-fields.ts) is the published reference-bearing field family. Four faces restate it inline, none deriving from it, none pinned against it:

file	restatement
plugin-kanban/src/ObjectKanban.tsx:346	lookup || master_detail || reference
plugin-detail/src/RecordDetailDrawer.tsx:227	lookup || master_detail || reference
plugin-detail/src/HeaderHighlight.tsx:147	reference || lookup || master_detail (inside a wider isWide disjunction)
app-shell/src/utils/resolveActionParams.ts:489	lookup || reference (⚠️ also omits master_detail)

⭐ Every one diverges in BOTH directions, which is why this is not mere duplication:

• user missing from all four — it carries the same foreign-key storage as lookup and resolves through the same expand path (fix(core): $expand user/tree reference columns in list & grid views (not just lookup/master_detail) #2032 put it in the family). On these faces a user column is not treated as a relation.
• tree missing from all four.
• reference present in all four, and no producer can emit it — measured on finding(plugin-dashboard): two more private copies of the reference-bearing field family — #5312's "LAST private copy" claim is false #5692's branch against @objectstack/spec's closed FieldType vocabulary, with lookup/master_detail/user/tree as live controls and retired owner plus a nonsense spelling as dead ones: reference is absent, and FieldSchema.safeParse({ type: 'reference' }) is refused. It sits exactly where owner sat before owner widget 拿不到表单下发的 dataSource,而 plugin-grid 认为它需要 —— 且 owner 根本不在 spec 的 FieldType 里(enforce-or-remove 待判) #4814 retired it. Dead weight that reads as live capability.

Shape: read EXPANDABLE_FIELD_TYPES and carry an identity pin — a spy on its .has — so a member-identical private copy fails rather than quietly re-forking. ⛔ Do NOT copy the set. That instruction is the whole point of the family's five prior sweeps.

The #5875 half

packages/app-shell/src/utils/paramToField.ts says "This face held the fourth and last private copy of it"; paramToField.test.ts says "This module held the FOURTH and last hand-maintained answer to one question." Both were true-as-measured when written and are now known false — there were at least six, and this card adds four more.

Prose only, no behaviour. Replace "fourth and last" with what is measured — this face was the fourth converted, not the last copy — and ⛔ point at expand-fields.ts's falsification note rather than restating a count locally. ⭐ Hand-kept counts of this table are exactly what keeps going stale; the mechanical fact is the identity pins. ⚠️ So do not write a new number. If you write "the seventh and last", you have re-created the defect with a bigger integer.

PM mechanism assumptions — measure, do not assume

1. Both cards are from 2026-08-23 and four of the five files sit in packages this seat merged into today (fix(plugin-detail): give record:path one stage classification both rows read #6015/fix(plugin-detail,i18n): localize record:path's container labels and announce its goal terminus #6000 in plugin-detail, refactor(app-shell): type RecordDetailView's confirm handler as the published ConfirmationHandler #6035 in app-shell, fix(components): bind current_user on form section/field visibleWhen predicates #6037 in components). ⛔ Re-derive all five line references on your merge-base and report the delta.
2. ⚠️ "Each face needs its own call on whether gaining user/tree is the intended behaviour there." The card says so and explicitly does not pre-empt it: "on the four above it looks like restoration rather than widening, but that is a per-face judgement." ✅ Make that call per face, with the read site as evidence. ⛔ If any face would be widened rather than restored by gaining user/tree — i.e. it would start treating as a relation something it deliberately does not — stop and report that face rather than converging it. Converging three and reporting one is a better outcome than converging four on an assumption.
3. ⚠️ resolveActionParams.ts:489 is the odd one — it omits master_detail too. So it diverges on three members, not two. Treat it as its own judgement, not as "the same as the other three".
4. ⚠️ HeaderHighlight.tsx:147 sits inside a wider isWide disjunction. Converging the reference-bearing part must not change what the rest of that disjunction decides. Measure the surrounding condition before touching it.
5. ⛔ ActionParamDialog.tsx:351 is NOT this card — a different rule (degraded-hint), already filed as finding(app-shell): ActionParamDialog's isLookupParam restates the picker family over RAW param spellings, so a degraded master_detail param loses the #3405 affordances #5654. A sweep for the three-way disjunction will catch it; the sweep is wrong.

Verification

The identity pin is the deliverable. A spy on EXPANDABLE_FIELD_TYPES.has per converged face, so a future hand-copy that happens to be member-identical still fails. ⛔ Asserting the resulting member set is not sufficient — that is exactly what let five prior sweeps re-fork.

Direction predicted before running: replace one converged face with a member-identical private copy and show its identity pin goes red (the member-set assertion will stay green — say so, that contrast is the proof the pin is doing work the set assertion cannot).

Counter-probes required: (a) a user field is now treated as reference-bearing on each converged face — the restoration half, which must be able to fail; (b) a field of a type genuinely outside the family is still not treated as reference-bearing — otherwise convergence is satisfiable by treating everything as a relation.

Prove every mutation on disk by grepping the injected text and separately the removed text; ⚠️ print the landing site, and ⚠️ assert anchor uniqueness before writing — ⚠️ especially here: four of these five restatements are near-identical disjunctions, which is the exact terrain where an anchor hits three sites (measured on #5927 today). Restore under trap … EXIT INT TERM, and ⚠️ make the restore command cwd-independent — a trap that fires is not a trap that restored (measured on #5926 today). Confirm git diff HEAD --stat empty afterwards.

Gates by name with exit codes: type-check for plugin-kanban, plugin-detail, app-shell (⚠️ hyphenated; echo the script name; distinguish the unbuilt-closure red from the missing-node_modules red — both were hit today), root-form vitest over each affected package's paths (⚠️ app-shell path-filtered — whole-package vitest is ~784 s and holds the shared lock; ⛔ do not run it; and the guard refuses --filter forms — use pnpm exec vitest run <paths> from the repo root), node scripts/check-phantom-dependencies.mjs if any package gains an import of @object-ui/core, and eslint on changed files with merge-base delta. ⚠️ Plain eslint . per package — ⛔ no --no-inline-config.

Changeset required. Draft PR, Fixes #5874 and Fixes #5875. ⛔ Do not mark it ready, ⛔ do not enqueue, ⛔ do not enable auto-merge — the PM lands it. Post the terminal report here (plain-text first-line marker os-dev-report; ⛔ avoid short angle-bracket placeholders in prose — the sanitizer ate one on #5926 today) and return it.

---

Generated by Claude Code