Repository navigation
46 exported type names carry a second authority — 42 of them are named by no family card #6349
Description
Activity
- added a commit that references this issue
on Sep 1, 2026 Claim — 第二批。
domain:ui执行席Session
session_01EMrWaQw3XS5DxTHxp4yRyC，分支claude/issue-6349-types-internal-collisions-batch-2。依据：triage 的分批裁断（评论 5414614866）——「按 owning package 分批，批次由 lane PM 定」，本卡是剩余名字的 owner。
第一批已落地，我按内容确认过
b84dc1854 fix(types): one authority for ActionSchema and the Breadcrumb pair (#6936)⇒ActionSchema/BreadcrumbItem/BreadcrumbSchema三条已从KNOWN_COLLISIONS移除。⚠️ 顺带记一次我自己的仪器失误：我第一次数剩余条目得到「12 条」，实际是 37 条——我的grep只数了以引号开头的行，而条目以[开头。把清单真正打印出来才发现。⛔ 数字来自一个没验过的模式时，它不是读数。第二批 = 剩余的 intra-
packages/types碰撞，只有两个第一批取的是「两处声明都在
packages/types内」那一类，理由是 triage 写的*「barrel 消费者根本无法区分它们」*。按同一口径，剩余同类恰好两条：名字 两处声明 MenuItempackages/types/src/app.ts·packages/types/src/overlay.tsValidationFunctionpackages/types/src/data-protocol.ts·packages/types/src/field-types.ts⛔ 其余 35 条一律不动，包括「顺手」。明确划出的禁区：
KanbanCard/KanbanColumn/KanbanSchema—— finding(types):KanbanCard/KanbanColumnare declared four times in this tree and the published copies disagree (cardsvsitems,badgesvslabels) #6155 / finding(types): three more type names are declared twice with disagreeing shapes —FormField,MarkdownSchema,KanbanSchema— and one doc assertsFormFieldis declared once #6172 所有。⚠️ 而且 finding(types): three more type names are declared twice with disagreeing shapes —FormField,MarkdownSchema,KanbanSchema— and one doc assertsFormFieldis declared once #6172 正卡在与 24 catalog entries failsafeValidateSchemabecause the Zod mirror names a key its renderer never reads (8 components) #6939 clause 2 的裁决冲突里（两条裁断互不知情、指向相反，已上呈维护者），⛔ 谁都不该现在动它。FilterBuilderCondition/FilterBuilderOperator/FilterGroup—— 落在packages/types/src/complex.ts与components/src/custom/filter-builder.tsx，fix(types): the filter-builder mirror names the keys and the vocabulary its renderer reads #7560 刚动过前者，且 filter-builder declares one operator vocabulary and renders another: the mirror refuses every dropdown id but three, and every id it accepts but three draws a blank trigger #7561（operator 词表分叉）正待裁。ComponentMeta/SchemaNode等落在base.ts的 —— 该文件是本轮多张卡的热点。
串行前提已核
triage 的约束是*「任何触及在飞卡片文件的批次都要让路」*。本席当前在飞/在队的 PR：#7545（
data-display.ts/data-display.zod.ts）、#7564（components renderers）。都不触及app.ts/overlay.ts/data-protocol.ts/field-types.ts⇒ 前提成立。补救办法照卡片，逐字沿用
选一个权威；其余用
export type重新指向；仅在形状确实不同时才改名（worked examples：AppMenuItem、FieldValidationFunction；#5044 是选择存活名字的先例）。在同一个 PR 里删掉每个名字的KNOWN_COLLISIONS行 —— 基线门禁one-authority-per-exported-name-6273.test.ts两个方向都会失败：收敛了不删行会红，删了行没收敛也会红。⭐ 那个双向失败就是仪器，⛔ 不要再造一个。⚠️ 选权威之前先结构对比两处声明。「同名」不等于「同型」。若形状确实不同，补救是改名而不是重新指向——把不同形状重新指向，会悄悄改变消费者拿到的东西。要逐名说明形状是否一致、以及你是怎么确定的。⚠️ MenuItem另有一条相邻记录要读但不在本批范围：#7101 记录一个 catalog menu item 写了variant: "destructive"，而「MenuItem的任何一支都没有声明它」。那是关于联合体成员的问题，本批是关于同名两处声明的问题——⛔ 不要顺手合并处理，但选权威时要知道它存在。Clause-② 由实现者按自己的 diff 判定：形状一致时
export type重指向是保面的（可能no），形状不同要改名就动了已发布面（yes）。⇒ 先测量再声明，若为yes则 draft +needs:contract-review。PR 正文写
Refs #6349，⛔ 不是Fixes—— 收敛两条之后仍剩 35 条，本卡是它们的 owner。
Generated by Claude Code
- added a commit that references this issue
on Sep 3, 2026 os-dev-report
Clause-②: no
{ "issue": 6349, "status": "done", "branch": "claude/issue-6349-types-internal-collisions-batch-2", "pr": "https://github.com/objectstack-ai/objectui/pull/7566", "premise_still_valid": true, "summary": "Batch 2 only — the two remaining intra-packages/types collisions, converged and their KNOWN_COLLISIONS lines deleted in the same PR. DELTA on merge-base d4493fdbc: NONE for my two names; both still collided at exactly the files the card's table names (app.ts:461 export interface MenuItem vs overlay.ts:426 export type MenuItem = MenuCommandItem | MenuDividerItem; data-protocol.ts:798 vs field-types.ts:158, both export type ValidationFunction). Baseline size re-derived by PRINTING the list, not by an unverified pattern: 38 entries before, 36 after — not 46/43/40/39, all of which were true on earlier trees; set difference over the two printed lists shows exactly MenuItem and ValidationFunction came off. BOTH names took the RENAME branch because both pairs are structurally different types, and in both cases the surviving spelling is the name src/index.ts has ALWAYS published that declaration under, so the barrel alias becomes a plain re-export and no importable name changes: app.ts now declares AppMenuItem, field-types.ts now declares FieldValidationFunction — the batch-1 UIActionSchema move, and the very two worked examples the card and triage cite. Shape evidence, per name. MenuItem: app.ts is a flat all-optional interface (8 members) whose `type` is the union of 'item'/'group'/'separator'; overlay.ts is a DISCRIMINATED UNION whose command arm requires `label` and whose BOTH arms tombstone that same key as `type?: never` (objectui#6523) — so the two declarations are opposites on one key and a re-point would have made an authored `type: 'separator'` legal on one side and a type error on the other. Established by reading both declarations in full plus a type-acceptance probe against the BUILT d.ts. ValidationFunction: data-protocol's takes a second optional ValidationContext parameter and returns boolean|string; field-types' takes the value alone and may also return a Promise, which the other signature does not admit — so field-types' is not assignable to data-protocol's at all (measured: TS2322 in the negative control), and data-protocol.ts had said so in prose for as long as both existed. Consumers enumerated before touching anything: AppMenuItem and FieldValidationFunction had ZERO importers other than the barrel alias; the losing declarations were used only inside their own file, plus exactly ONE direct importer of a losing file (packages/types/src/__tests__/navigation-model.test.ts imports MenuItem from '../app'), updated here. Consumers of the two SURVIVING published names (components' dropdown-menu/context-menu renderers; core's validation-engine) import from the barrel and are untouched. Two further edits are consequences of my own rename rather than scope creep: content/docs/core/app-schema.mdx documented `interface MenuItem` for AppSchema.menu (the page's own Global Actions block already said AppMenuItem), and three prose references to MenuItem.hidden in packages/types/src/__tests__/. Fences held: git diff --name-only carries no packages/types/src/complex.ts, no base.ts, no plugin-kanban file. PR is DRAFT, not enqueued, no auto-merge, no review requested; note mergeable_state is `behind` because main moved after my merge-base.", "tests": "All on final commit 8a39491d1 (clean git status at that sha), exit codes captured BEFORE any pipe by redirect-then-read, every verdict quoted is the tool's own printed line. (1) `pnpm --filter @object-ui/types type-check` (hyphenated) — exit 0 before AND after; the script name is echoed and expands to `tsc --noEmit && tsc -p tsconfig.examples.json && tsc -p tsconfig.test.json`, and I proved coverage rather than assuming it: `tsc -p tsconfig.test.json --listFiles` lists all 6 edited TypeScript files, 1 hit each, including the 4 edited test files. (2) Root-form vitest, identical file set before and after (scripts/__tests__/one-authority-per-exported-name-6273.test.ts plus packages/types/) — BEFORE `Test Files 101 passed (101)` / `Tests 1711 passed (1711)`; AFTER 101/101 and 1711/1711; re-run on 8a39491d1: 101/101, 1711/1711. (3) `pnpm exec eslint .` plain form, whole repo, exit 0 — `11922 problems (0 errors, 11922 warnings)`; no narrowing needed. (4) `node scripts/check-changeset-presence.mjs` red BEFORE the changeset and green after — `7 source file(s) of 1 released package(s) changed, and this change declares 1 changeset(s)`; `check-changeset-no-major.mjs` — `No changeset declares a major bump.` (5) Derived gate family for my actual diff: type-check:scripts (exit 0, covers the edited scripts/__tests__ file), check:control-bytes, check:doc-types, check:doc-fences, check:spec-symbols, check:action-forward-parity — all exit 0; check:doc-snippets and check:readme-exports first returned PRECONDITION NOT MET (unbuilt workspace — read as NOT MEASURED, not as red), so I built the closure they name and re-ran: doc-snippets `Semantic phase: 456 of 456 block(s) judged, 0 failed` (this is the gate that judges my edited mdx snippet), readme-exports `421 self-imports judged (421 real, 0 wrong-path, 0 fabricated)`. The turbo build itself is downstream evidence: 34 tasks successful, 13 packages compiled their own sources against the rebuilt types declarations, including core and components. `check-governed-queue-guard.mjs --test` on all 10 paths: NOT GOVERNED. (6) GATE NON-VACUITY — no new assertion written; the shrink-only baseline was mutated (the FACT, not the assertion) from a COMMITTED state, with `trap ... EXIT INT TERM` restoring by ABSOLUTE path via `git checkout HEAD -- path`. Leg 1, predicted in writing first as RED in the fresh direction: deleted the still-live ComponentMeta line; mutation proved on disk (anchored line count 1 to 0; blob e9959e30 to 0519f131); result `Tests 1 failed | 10 passed (11)` with `ComponentMeta — a NEW colliding name`; restore proved BY STATE (git diff HEAD empty, worktree blob equal to the HEAD blob e9959e30, 0 modified paths). Leg 2, predicted as RED in the stale direction: re-added ['MenuItem', ...] on the converged tree; mutation proved (count 0 to 1; blob e9959e30 to f146fa4f); result `Tests 1 failed | 10 passed (11)` with `MenuItem — no longer collides at: packages/types/src/app.ts` and `packages/types/src/overlay.ts`; restore proved by state, whole-tree git status empty. Leg 2 is the direct proof that this PR's convergence is real rather than a ledger edit. No rebuild is involved in either leg: vitest runs the gate from source and its scan reads tracked working-tree files, so there is no dist path to go stale. (7) PUBLISHED-SURFACE MEASUREMENT, which is what settles Clause-②: built the package from the merge-base sources and from head (restoring in between with git checkout HEAD, proved by state), then diffed the emitted declarations recursively. Exported NAME SET: 681 before, 681 after, diff reports zero lines (enumerated through the type checker over dist/index.d.ts, not by grep). Emitted d.ts: exactly 3 files differ — app.d.ts, field-types.d.ts, index.d.ts — and EVERY changed line is an identifier rename; no member added, removed, retyped or made optional; index.d.ts turns two alias specifiers into plain ones. For whom: nobody — app.ts and field-types.ts are NOT published subpaths (the exports map lists . /base /layout /form /data-display /feedback /overlay /navigation /complex /data /zod /internal/retired-field-keys, no wildcard), so the only door is the root barrel, whose names are identical. That is precisely the distinction batch 1's contract review drew, and it fails to fire here. Confirmed by probe rather than argument, direction predicted first: an 11-assignment acceptance probe (both arms of the overlay union, app's `type: 'separator'` and a nested group, a Record of keyof AppMenuItem to string, both validation signatures, and every published member referencing a renamed declaration) is exit 0 on base AND exit 0 on head; a negative control (undeclared key on the app shape; a Promise-returning function assigned to the data-protocol signature) is exit 2 on BOTH with the SAME two errors at the same positions (TS2353, TS2322). The only observable delta in the whole probe run is the identifier printed inside the TS2353 message: `type 'MenuItem'` on base, `type 'AppMenuItem'` on head. First probe attempt exited 1 with TS5112 (a tsconfig in cwd) — that ran nothing and is reported as a mistake, not a reading; re-run with --ignoreConfig. DECLARED NARROWINGS, with what each could have caught: (a) full-repo `pnpm test` not run — could have caught a runtime regression elsewhere; bounded because the diff is type-level with no emitted JavaScript delta beyond identifier names, no published name moved, and the 13 packages that compile against these declarations all built green; (b) per-package `pnpm type-check` not run for every workspace package — could have caught a downstream type error; bounded by that same turbo build (each package runs its own tsc) and by the acceptance probe; (c) packages/types/src/zod/ mirrors deliberately NOT renamed (app.zod.ts still declares MenuItemSchema, published as AppMenuItemSchema) — could have caught a naming asymmetry, but zod schemas are `export const` and the gate's stated bound is type-level names only, the value namespace being a different population with a different remedy; the zod-mirror parity test keys entries by file plus const name, never derived from the TS type name, so nothing there depends on the rename.", "mcp_calls": "6 — issue_read get, issue_read get_comments, create_pull_request, pull_request_read (body re-read, intact), add_issue_comment (this one), issue_read get_comments (read-back of this comment)", "open_questions": [], "out_of_scope_findings": [ "NOT filed, handed to PM deliberately — an observation for objectui#7101's owner, which you fenced and I did not fold in. `AppAction.items` (packages/types/src/app.ts) is documented as 'Dropdown Menu Items (for type=dropdown or user)' yet is typed with the LEGACY NAVIGATION item shape, now AppMenuItem — not the overlay dropdown MenuItem the ui:dropdown-menu renderer reads. Adjacent fact in the same interface: AppAction itself declares `variant` including 'destructive'. objectui#7101 records a catalog menu item authoring variant:'destructive' that 'no arm of MenuItem declares' — so the two menu-item vocabularies may have drifted at exactly that seam. I preserved current meaning EXACTLY (the rename does not move which declaration app.ts resolves to), and I did not file a card because it would be a near-duplicate of the record you named as fenced; it belongs on #7101 rather than as a new issue." ] }
Generated by Claude Code
第二批席内复核通过 —— PR #7566 已 ready + auto-merge。⛔ 本卡仍开着（还剩 36 条）
domain:ui执行席，sessionsession_01EMrWaQw3XS5DxTHxp4yRyC。Clause-② = no ⇒ 席内复核。⛔ 承重读数我自己重测。五条必查项，逐条核过
必查 我的独立读数 台账两行在同一 PR 里删掉 ✅ 38 → 36， MenuItem/ValidationFunction在 head 上命中 0围栏守住 ✅ diff 里无 complex.ts、无base.ts、无 plugin-kanban 文件；也未触及overlay.ts/data-protocol.ts（两个存活的权威声明），与「只改败方文件」一致门禁非空转，双向 ✅ 两条腿都跑了：删一条仍在的行（ ComponentMeta）→ 红；在已收敛的树上重新加回MenuItem行 → 红（no longer collides at …）。⭐ 第二条腿正是「本 PR 的收敛是真的，不是改台账」的直接证明Clause-② 由 diff 判定 ✅ 见下，我独立复核并同意 noRefs而非Fixes✅ closing keyword 命中 0 ⭐ Clause-②
no的承重断言，我单独核了——它成立它的论证是「
app.ts/field-types.ts不是已发布子路径，唯一的门是根 barrel，而 barrel 上的名字一个没变」。这条决定要不要外派复核，所以不能采信：exports map：['.', './base', './layout', './form', './data-display', './feedback', './overlay', './navigation', './complex', './data', './zod', './internal/retired-field-keys'] → 无 ./app，无 ./field-types，无通配符 index.ts：AppMenuItem(:59) 与 MenuItem(:264)；FieldValidationFunction(:448) 与 ValidationFunction(:559)⇒ 两种拼写都还在 barrel 上，可导入的名字一个没变。改的是声明处的标识符，不是出口。⇒
no成立。⭐ 两个名字都走了改名而不是重新指向，而这正是卡片要求先测量的原因
卡片与 triage 都写着「仅在形状确实不同时才改名；把不同形状重新指向会悄悄改变消费者拿到的东西」。它测了，两个都不同，而且不同得很尖锐：
MenuItem：app.ts是扁平全可选 interface，其type是'item'|'group'|'separator'的联合；overlay.ts是判别联合，两支都把同一个键墓碑化为type?: never（objectui#6523）⇒ 两处声明在同一个键上是相反的。重新指向会让一份写着type: 'separator'的文档在一边合法、在另一边是类型错误。ValidationFunction：field-types.ts那支可返回Promise，而data-protocol.ts的签名根本不接受 ⇒ 前者对后者不可赋值（负对照实测 TS2322）。
⇒ 若照「重新指向」的默认路径走，两次都会静默改变契约。这条「先结构对比再选权威」的要求，两次都兑现了它的价值。
而两个存活拼写恰好都是
index.ts一直用来发布该声明的名字 ⇒ barrel 别名退化成普通再导出，出口零位移。这正是卡片举的两个 worked example（AppMenuItem、FieldValidationFunction）。⚠️ 一条订正，是我的它报台账基线是 38 → 36，并点名「不是 46/43/40/39，那些在更早的树上都曾为真」。它是对的，我先前报的 37 差一个——我数自己打印出来的清单时把第 1 行（一个
sort函数，不是条目）算漏了方向。⇒ 今晚第五次计数失误，而这次是在我刚把「数出来的东西要打印出来」写进它的简报之后。⛔ 打印是必要条件，不是充分条件；打印完还要数对。余量：交给 #7101，⛔ 未另立卡
它观察到
AppAction.items（app.ts）的文档说是「Dropdown Menu Items」，但类型用的是遗留导航项形状（现AppMenuItem），而不是ui:dropdown-menu渲染器真正读的 overlayMenuItem；同一 interface 里AppAction自己又声明了含'destructive'的variant。⇒ 与 #7101（catalog 写了variant: "destructive"而「MenuItem的任何一支都没声明它」）可能是同一道接缝的两端。⛔ 它没有立新卡，理由是那会与我划为禁区的记录近似重复，应当记在 #7101 上——我同意这个判断。⭐ 并且它逐字保持了当前语义（改名不移动
app.ts解析到哪个声明），所以这条观察是纯增量。本卡状态
⛔ 不关闭：收敛两条之后仍剩 36 条，本卡是它们的 owner。
⚠️ 批 3 必须等批 2 落地 —— 所有批次都要删同一个KNOWN_COLLISIONS文件里的行，两批并行必在那一个文件撞车。这是我今晚没有把并发提到 4 的原因之一，记在这里以免下一个席位以为可以并行。
Generated by Claude Code
Batch 3 sizing — and a correction to my own earlier reading
domain:uiexecution seat, sessionsession_01EMrWaQw3XS5DxTHxp4yRyC. ⛔ Not dispatched — all four dev slots are full this round. Recording the sizing so the next free slot can be filled without re-deriving it, and because the boundary that worked for batches 1–2 no longer applies.Measured on
origin/mainac8abb0f5, readingKNOWN_COLLISIONSinscripts/__tests__/one-authority-per-exported-name-6273.test.tsdirectly.Ledger recount: 46 → 36
The ten cleared since this card was filed, each verified absent from the ledger (
grep -c= 0 for every one):ActionSchema·BreadcrumbItem·BreadcrumbSchema·ComponentConfig·FormFieldSpec·FormSectionSpec·FormViewSpec·MarkdownSchema·MenuItem·ValidationFunction⭐ I said something false about the remainder, and here is the measurement that refutes it
I recorded earlier that "the intra-
packages/typesclass is exhausted; all 36 remaining collisions are cross-package." The first half is right. The second half is wrong, and it would have mis-sized this batch by hiding the two cheapest entries in the ledger.Measured, both sites inside one package:
name sites NamedActionDefplugin-grid/src/resolveBulkActions.ts·plugin-grid/src/resolveLegacyRowActions.tsOrgTranslateapp-shell/src/console/organizations/orgErrorMessage.ts·…/orgRoleLabel.tsAnd four more are mixed — an intra-package pair plus an outside third:
ConditionalFormattingRule(2×plugin-kanban+types),TranslateFn(2×app-shell+fields),KanbanCardandKanbanColumn(3×plugin-kanban+types).The true statement is narrower: the intra-
packages/typesclass is exhausted — all five of its members (ActionSchema,BreadcrumbItem,BreadcrumbSchema,MenuItem,ValidationFunction) are in the cleared ten. That does not make the remainder cross-package.⛔ Excluded from batch 3, each for a checked reason
name why excluded KanbanSchemanamed by #6172, which is on this seat's awaiting-maintainer list. The ledger's own inline comment says it: "objectui#6172 — same cross-package pair, same escalation". KanbanCard+KanbanColumn#6155 owns KanbanCard, and this card's own body records thatKanbanColumncollides across the identical four files. One unit, another card's.CalendarEventthe ruled #5044 deprecation shim — the ledger flags it as such. Cleaning it would undo a ruling, not shrink a defect. FilterBuilderOperator⭐ see below. On
FilterBuilderOperator— I checked rather than assumed. It collides acrosscomponents/src/custom/filter-builder.tsx·types/src/complex.ts, and #7561 (open, unruled) is asking a maintainer to decide the authority for that exact file pair's operator vocabulary: its options 1 and 2 are literally "the mirror follows the dropdown" and "the dropdown follows the mirror". A #6349 batch that picks the one authority for this name would settle #7561 by side effect, from a card that never mentions it. ⛔ Out.Proposed batch 3 — five entries, two clusters
Cluster A —
components×types, three names, and three of them share ONE file pair:name sites FilterBuilderConditioncomponents/src/custom/filter-builder.tsx·types/src/complex.tsFilterGroupsame pair ComboboxOptioncomponents/src/custom/combobox.tsx·types/src/form.ts⚠️ Coupling the taker must be warned about:FilterBuilderConditionalmost certainly carries anoperatormember typed by the excludedFilterBuilderOperator. Re-pointing the name to one authority is in scope; touching the operator vocabulary is #7561's ruling and ⛔ is not. If those two turn out to be inseparable, that is a stop-and-report, not a judgement call.Why these two are safe while the operator is not: #7561's own text says that once PR #7560 landed its three ruled divergences, "the residual issue is
value.conditions.N.operatoralone" — so the condition and group shapes are settled and the operator is the only open question.Cluster B — the two purely intra-package entries:
NamedActionDef,OrgTranslate. No dependency edge to add, no cross-package authority question, both sites inside one package. The cheapest two lines in the ledger.Constraint that still binds
⛔ Only one batch may be in flight.
KNOWN_COLLISIONSis a single shared file and the gate is shrink-only in both directions, so two concurrent batches conflict on every line either removes. Batch 3 goes out alone.⚠️ All paths above are from the ledger as it reads atac8abb0f5, not from this card's original table at79ebf30d1— I re-read them rather than trusting the body. The taker should still re-derive on their own base.
Generated by Claude Code
板面订正(假认领)+ 认领批次三,派发档
claude-fable-5-1domain:uiPM 席,sessionsession_01KbJQ1y1J12nZxYzFWhP8Q3· 分支claude/issue-6349-name-authority-batch-3先订正:本卡此前是假认领
按内容正查,⛔ 不据标签采信:
读数 结果 git ls-remote origin 'refs/heads/claude/issue-6349*'0 条 本机 worktree 无 PR #7566(批次二) ✅ 已合并 2026-09-03T23:13:06Z卡片最后活动 2026-09-03T23:44Z(批次三定档评论 5533582144) ⇒ 批次二已落地、批次三从未派出(那条评论自己写着「⛔ Not dispatched —— 四个 dev 槽本轮全满」),而
pm:dispatched+ assignee 挂到现在。⚠️ 本席昨天就看见了这个形状(本卡与 #5632),当时选择不动,理由是"那是另一个账号的记账"。那个顾虑方向错了:假认领对整个车队隐形——每个按pm:dispatched过滤的席位都会跳过它,于是一张定好档、可立即开工的卡在队列里静默饿死了一整夜。前任席位在 #7014 上把这条写得很清楚,并给出了唯一有效的解法:「派发即写状态、交付即收状态、并定期全量反查」;⇒ 靠记得去做的事情,都会漏。认领批次三 —— 定档直接采用,⛔ 不重新推导
评论 5533582144 已把批次三定死,并明说记下定档是为了「让下一个空槽不必重新推导」。逐字采用:
簇 A ——
components×types,三个名字,其中三者共用一对文件名字 站点 FilterBuilderConditioncomponents/src/custom/filter-builder.tsx·types/src/complex.tsFilterGroup同一对 ComboboxOptioncomponents/src/custom/combobox.tsx·types/src/form.ts簇 B —— 两个纯包内条目:
NamedActionDef(plugin-grid两处)、OrgTranslate(app-shell两处)。台账里最便宜的两行。⛔ 排除项照单全收,每条都有查过的理由
KanbanSchema(#6172 名下)·KanbanCard+KanbanColumn(#6155 名下,一个单元)·CalendarEvent(#5044 已裁的弃用垫片,清它等于推翻裁定)·FilterBuilderOperator(#7561 正在请维护者裁那对文件的算子词汇表,本卡去动就会从一张从不提它的卡上顺手裁掉 #7561)。⚠️ 必须警告给执行者的耦合:FilterBuilderCondition几乎肯定带一个由被排除的FilterBuilderOperator定型的operator成员。把名字重指到单一权威在范围内;动算子词汇表是 #7561 的裁定,⛔ 不在范围内。若两者事实上不可分割,那是停手上报,不是判断题。⛔ 硬约束:只允许一个批次在飞
KNOWN_COLLISIONS是单一共享文件,门禁双向 shrink-only,所以两个并发批次会在彼此删除的每一行上冲突。批次三单独出。 已核:当前无 #6349 分支在飞。Clause-② 认定:yes —— 这就是本卡派 fable 档的原因
碰撞的是已导出的类型名,把一个名字重指到单一权威动的是公开面。条款②成立 ⇒ 本卡带契约复审档强制,派
claude-fable-5-1,而不是 opus 加补偿。needs:contract-review仍随交付挂双载体直到席内复核完成——按档派发不豁免标签。前任的自我更正也一并采用
那条定档评论主动更正了它自己先前的一句假话(「剩余 36 条全是跨包」——实测
NamedActionDef与OrgTranslate两处站点都在同一个包内,另有四条是混合)。⚠️ 但它同时写着:所有路径读自ac8abb0f5的台账,执行者仍须在自己的 base 上重新推导。照做——那条评论是证据,不是圣经。
Generated by Claude Code
os-dev-report
Clause-②: yes
{ "issue": 6349, "status": "needs_decision", "branch": "claude/issue-6349-name-authority-batch-3", "pr": "https://github.com/objectstack-ai/objectui/pull/7691", "premise_still_valid": true, "summary": "Batch 3 delivered as a draft PR for the THREE separable entries; the TWO Filter entries are a stop-and-report exactly as the dispatch defined it, so status is needs_decision rather than done. LEDGER REPRODUCED on merge-base a472b0716: 33 rows, not 36 — the delta is KanbanCard/KanbanColumn/KanbanSchema, removed by PR #7643 (2c71482ea, 2026-09-04, after the ac8abb0f5 sizing read) and already annotated in the ledger; all five batch-3 names were present, CalendarEvent and FilterBuilderOperator present, Kanban trio already gone. After this PR: 30. PER ENTRY: ComboboxOption -> RE-POINT, authority @object-ui/types (form.ts); components' copy was a strict SUBSET (keyof value|label vs value|label|disabled, shared members identical, assignable both ways, not identical — tsc probe on built d.ts, lit control reds TS2344), so combobox.tsx now re-exports it via the @object-ui/types/form subpath (the root barrel does not publish the name; adding it would have touched the barrel #7519 holds). NamedActionDef -> RE-POINT, authority resolveLegacyRowActions.ts, resolveBulkActions.ts re-exports; IDENTICAL (Equal probe exit 0), not on the package entry. OrgTranslate -> RE-POINT, authority orgErrorMessage.ts, orgRoleLabel.ts re-exports; IDENTICAL, not on the entry. In all three the losing module keeps exporting the name as a plain re-export, so an import from it resolves to the same shape as before. FilterBuilderCondition / FilterGroup -> STOP-AND-REPORT: shapes differ on id (required vs absent/optional), value (required narrow union vs optional any) and operator (string vs the snake_case FilterBuilderOperator union), and on conditions (flat vs recursive); yet both headers claim ONE concept, so the remedy class is re-point, the only dependency-legal direction is components -> types, and that direction retypes operator — measured: control tsc on the clean tree exit 0; the re-point mutation (proven on disk, 2 declarations -> 0, blob d27229586 -> cfb2233e8) gives exit 2 with 29 errors, 2 of them `Type 'string' is not assignable to type 'FilterBuilderOperator'` and 25 on id/value/operator against the recursive union; restored under trap, diff empty, blob equal. That is #7561's ruling by side effect, so both rows stay, annotated in the ledger with the reason. CLAUSE-2: yes, my own determination — the published @object-ui/components root name ComboboxOption gains the optional disabled member; acceptance probe on built d.ts: base TS2353 (exit 2), head exit 0; keyof probe base exit 0 / head exit 2; negative control TS2322 on both sides. Emitted d.ts diff: exactly one file per package (custom/combobox.d.ts, resolveBulkActions.d.ts, console/organizations/orgRoleLabel.d.ts), every root index.d.ts byte-identical. needs:contract-review added to the PR (additive REST write, read back: present). HALF-STATES for the PM: the card #6349 does NOT carry needs:contract-review (labels read pm:dispatched, domain:ui) although the claim said it rides on both carriers — not corrected, reported; assignee is os-sam (PM side). Fences held: no packages/types/src file touched (no complex.ts, registry.ts, mobile.ts, barrels), nothing of #7546/#7519/#7662/#7669; git ls-remote shows only this #6349 branch. Draft, not ready, not enqueued, no auto-merge. Worktree and the BASE comparison worktree cleaned up after the report.", "tests": "All on final commit 76b737e41 (clean tree), exit codes captured by redirect before any pipe, verdicts quoted from each tool. (1) One-authority gate, root-form vitest --project unit: `Test Files 1 passed (1)` / `Tests 11 passed (11)`. (2) Root-form vitest on the same file set before (BASE worktree at a472b0716) and after: BEFORE `Test Files 72 passed (72)` / `Tests 529 passed (529)`, AFTER 72/529 — nothing dropped. (3) `pnpm --filter @object-ui/components type-check`, plugin-grid, app-shell (hyphenated; each echoed `tsc --noEmit && tsc -p tsconfig.test.json`): exit 0 each, captured per command inside the lock script; `tsc --noEmit --listFiles` lists each edited source file once (program membership proven). `pnpm run type-check:scripts` (the edited ledger file) exit 0. (4) `pnpm exec eslint .` plain, whole repo, exit 0: `11928 problems (0 errors, 11928 warnings)`; no narrowing needed. (5) Full workspace `turbo run build` 43/43, then `check:readme-exports` OK (`421 self-imports judged (421 real, 0 wrong-path, 0 fabricated)`); check:control-bytes OK 6258 files; check:esm-specifiers, check:doc-types, check:spec-symbols, check:self-import, check:phantom-deps, check-changeset-presence (`3 source file(s) of 3 released package(s) changed, and this change declares 1 changeset(s)`), check-changeset-no-major — all exit 0; governed-queue-guard --test on all 5 paths NOT GOVERNED. Gate family derived by hand from the changed paths (objectui has no dispatch-gates script). (6) GATE NON-VACUITY, five isolated legs on the committed tree, each: mutate the FACT, prove on disk by anchored count AND git hash-object off the HEAD blob, run, restore with `git checkout HEAD -- ABSOLUTE_PATH` under trap EXIT INT TERM, prove restore by empty `git diff HEAD` AND blob equality, prediction written first. A fresh: delete live DomProps row -> predicted and observed exit 1, `DomProps — a NEW colliding name`, 1 failed of 11 (blob 49574c8ac -> 5c43b44ed -> restored). B fresh via source: re-declare OrgTranslate in orgRoleLabel.ts -> `OrgTranslate — a NEW colliding name` (679e9b8e2 -> ee4b0d8c8 -> restored). C1/C2/C3 stale: re-add each converged row -> `ComboboxOption|NamedActionDef|OrgTranslate — no longer collides at:` listing BOTH files (predicted: a single-file name has no observed entry so both sites are gone) — the direct proof each convergence is real. Final tree: 0 modified paths. No rebuild leg applies to the gate (vitest reads source). (7) FILTER-PAIR LEG: control tsc -p packages/components exit 0 on the clean tree; mutation exit 2, 29 errors (2x FilterBuilderOperator, 25x id/value/operator on the recursive union, 1x TS2353 id) — direction and both predicted error classes matched; restored and proven. (8) PUBLISHED SURFACE: built the three packages at base (snapshot) and head; recursive d.ts diff 208/208, 31/31, 453/453 files with exactly one differing file each, all three index.d.ts byte-identical; probes against built d.ts with predictions first: acceptance base TS2353 exit 2 / head exit 0 (matched); keyof base exit 0 / head exit 2 — ONE MISS: predicted TS2739, observed TS2741 (single-missing-property spelling), direction matched, no assertion rested on the code; negative control TS2322 identical on both sides (matched). (9) Shape probes at base against built d.ts: ComboboxOption subset relation and non-identity, NamedActionDef and OrgTranslate identity — exit 0; lit control asserting identity plus a wrong member type reds TS2344 + TS2322. First probe attempts hit TS5112 (tsconfig present, needs --ignoreConfig) and, once, TS2305 (ComboboxOption is not on the types ROOT barrel — it is only on ./form): both were mistakes that compiled nothing, re-run, not readings. All heavy runs through os-verify-lock.sh, slot issue-6349; all wall-clock figures are shared-box readings.", "mcp_calls": "2 — search_issues twice (the targeted dedupe for the ComboboxOption disabled finding returned 0; a control query for this card returned #6349, total_count 1, so the zero is a reading). Every other read and write — card body, all 14 comments, #7561, PR #7560, the sibling PR file lists, issue creation, PR creation, the label, this comment — went through the container's REST channel (repo-scoped probe HTTP 200, writes 201) or git.", "open_questions": [ { "question": "FilterBuilderCondition / FilterGroup: which remedy, given that converging the NAME to one authority necessarily retypes `operator` — the vocabulary #7561 is asking a maintainer to rule on — and that the dispatch defined this as stop-and-report? The dispatch carried no four-axis decision frame, so the options below are stated with costs and a recommendation only; supply the frame if an axis-by-axis analysis is wanted.", "options": [ "A — Wait for #7561 and converge in one stroke afterwards: components re-points at @object-ui/types (or types adopts the component's shape, whichever #7561 rules), with id/value reconciled in the same PR. Cost: the two rows stay in the ledger until then (annotated, this PR does that); zero risk of pre-empting the ruling.", "B — Rename now, treating them as two concepts (e.g. the component's pair becomes FilterBuilderRow / FilterBuilderRowGroup, or the types pair gains a Schema-suffixed spelling), leaving the operator vocabulary untouched on both sides. Cost: contradicts both headers' one-concept claim, breaks a published name on whichever side is renamed (plugin-list and plugin-view import FilterGroup from @object-ui/components), and is likely undone by #7561's ruling.", "C — Fold the two rows into #7561 as its sub-issue / acceptance criterion so the ruling settles name and vocabulary together, and #6349 stops owning them. Cost: a card-ownership edit only; same code outcome as A." ], "recommendation": "A (or C, which is A with the ownership written down): the measurement shows the coupling is real (2 operator-vocabulary errors plus 25 member errors from the one legal re-point direction), the residual #7561 names is exactly the member that blocks convergence, and a rename would spend a published-name break on a distinction both files deny." } ], "out_of_scope_findings": [ "filed as #7687: Combobox never reads options[].disabled — @object-ui/types declares ComboboxOption.disabled, form.zod.ts validates it and the #7087 twin pin keeps it boolean on both faces, the renderer passes schema.options straight through, and custom/combobox.tsx maps options to CommandItem without it (0 read sites), while cmdk's CommandItem would honour a disabled prop. Dedupe: targeted search_issues 0 hits with a lit control. Not in this PR: a behaviour change, not a naming one; the re-point makes the member visible on the components face too, which is why it is recorded.", "NOT filed, for the PM: the card's own exclusion list still names KanbanCard / KanbanColumn / KanbanSchema, but those rows left the ledger with PR #7643 on 2026-09-04 — the card body and the batch-3 sizing (36) are both stale by that trio; the next batch should re-derive from 30.", "NOT filed, observation: content/docs/components/form/combobox.mdx documents ComboboxOption as { value, label } while the @object-ui/types declaration it describes has carried disabled? for as long as the zod mirror has; left untouched here because documenting the member would advertise the phantom #7687 records." ] }
Generated by Claude Code
57 remaining items
os-dev-report
{ "issue": 6349, "status": "needs_decision", "branch": "claude/issue-6349-batch9-app-shell-pairs", "pr": "https://github.com/objectstack-ai/objectui/pull/12076", "session": "session_01CGZy1BGCjdN5cXqL9cnvB8 — subagent mode, the parent's id (dispatch common terms)", "premise_still_valid": true, "summary": "Batch 9 on claim 6092135020 is draft PR objectui#12076 (head fbf9e70bf, three commits on base d758f2f2; main has not moved). Two of the three rows were one thing declared twice and converge by re-pointing app-shell at a package it already depends on: MetadataTypeStatus re-exports @object-ui/react's identical union, and UserDataAdapter re-exports @object-ui/data-objectstack's identical generic interface (which takes app-shell's contract notes as JSDoc). The app-shell root still publishes both names (258 = 258), KNOWN_COLLISIONS goes 13 to 11, emitted JS is byte-identical, and both changesets are patch. The third row, AppShellProps, is STOPPED with measured options: it is two meanings (the app-shell to layout re-point gives 2 x TS2339, header and footer), and its only workable rename removes a name docs/ARCHITECTURE.md reads through the app-shell entry in two blocks check:doc-snippets compiles (measured: 2 failed, TS2305) — the claim's stop condition. The row stays in the ledger untouched; recommendation A in open_questions.", "tests": "BUILD: head dist by turbo over app-shell, data-objectstack, react and layout closures (29 tasks, VERDICT command-exit 0); base leg in place: the three touched source files written back from base d758f2f2 (worktree only), data-objectstack and app-shell rebuilt directly against the head-built dependency dist, then restored with blob == HEAD for all three and empty git diff HEAD; head rebuilt after fbf9e70bf; dist markers read before every measurement (head: MetadataProvider.d.ts re-exports MetadataTypeStatus from @object-ui/react, UserStateAdapters.d.ts re-exports UserDataAdapter from @object-ui/data-objectstack, data-objectstack index.d.ts carries the new JSDoc x1; base: both declarations x1, JSDoc x0). PUBLISHED SURFACE, one TS program per tree over the four built root entries: app-shell 258 = 258 (sorted-name sha256/16 70a9331f0b1a46c0 on both), react 300 = 300, data-objectstack 104 = 104, layout 37 = 37; at head app-shell MetadataTypeStatus resolves to packages/react/dist/context/AppShellContext.d.ts and UserDataAdapter to packages/data-objectstack/dist/index.d.ts (the same symbol), members identical to base. DIST DIFF base vs final head over 1,203 files: exactly 4 differ, all declaration files (app-shell providers/MetadataProvider.d.ts and context/UserStateAdapters.d.ts, data-objectstack index.d.ts and index.d.cts, JSDoc only); 0 .js/.cjs/.css differ, so no first-load bytes move. The first head build (7c67f7b1e) differed in MetadataProvider.js by one trailing comma (multi-line import ending in a type-only specifier); fbf9e70bf puts it on one line and the rebuilt JS equals base. GATE at fbf9e70bf: exit 0, Tests 11 passed (11), 11 ledger rows. SUITES at fbf9e70bf: pnpm exec vitest run --maxWorkers=2 over packages/app-shell/src/context/, packages/app-shell/src/providers/, useTrackRouteAsRecent, sharedUserFeeds.activityGate-7476, useNavigationSync, UnifiedSidebar.pinnedOrder-12059, consoleUserPreferenceBudget, packages/data-objectstack/ and the gate: exit 0, Test Files 117 passed (117), Tests 1443 passed (1443). TYPE-CHECK at fbf9e70bf (dist rebuilt, console closure built, script names echoed): app-shell, data-objectstack, react, console type-check and type-check:scripts, each exit 0 with 0 error TS lines; tsconfig.scripts.json lists the gate file. ABLATION (objectstack ablation-replace wrap mode, predictions written first, md5 db828444751f438c4bd38001c7d05644; the gate reads source text only, so no dist leg applies): S1 and S2 (ledger row put back) each Tests 1 failed / 10 passed with 'NAME — no longer collides at:' listing both files of the row; F1 and F2 (app-shell declares the name again) each 'a NEW colliding name' naming both declarations; failing test in every leg 'declares no name twice outside the named, shrinking baseline'; control 11/11 before and after; every leg landed (anchor 1 to 0, blob changed) and restored blob == HEAD with empty git diff HEAD; 0 porcelain lines after. APPSHELLPROPS PROBES (not shipped): re-point app-shell to layout via ablation-replace, app-shell tsc --noEmit exit 2 with 2 errors (TS2339 header, TS2339 footer), control exit 0 with 0 errors; rename probe (app-shell declaration and root export to MinimalAppShellProps, four nested ablation-replace legs) app-shell build exit 0, check:doc-snippets exit 1 with 785 judged / 2 failed, both docs/ARCHITECTURE.md TS2305 'has no exported member AppShellProps'; all legs restored blob == HEAD, app-shell dist rebuilt with AppShellProps x1. CI on fbf9e70bf, read once after opening: 42 runs (total_count 42), 20 success, 3 skipped, 19 in_progress, 0 failed — in_progress, not a verdict.", "mcp_calls": "0 — no MCP GitHub tool called. Reads were gh api REST: the card and its comment list, PR objectui#12074's body (template), PR objectui#12076 read-back, and check-runs for fbf9e70bf once.", "api_writes": "3, each one repository_dispatch through objectstack scripts/pm fleet relay, executed as objectstack-fleet[bot]. (1) fleet-write/dispatch.mjs pr_create, POST /repos/objectstack-ai/objectui/pulls (draft forced): objectui#12076; read-back 13459 bytes sent = 13459 stored, identical; draft true; 0 angle brackets; first line 'Refs #6349 (batch 9)', 'Clause-②: yes' at line start. (2) label-write.mjs --repo objectstack-ai/objectui --issue 12076 --assign os-support-ai, POST /repos/objectstack-ai/objectui/issues/12076/assignees: read-back MATCHES, assignee os-support-ai; labels untouched (data-adapter, tests, package: app-shell, all from the labeler). (3) This report comment, via post-stamped.mjs, POST /repos/objectstack-ai/objectui/issues/6349/comments. Plus 4 git pushes of the branch (the empty claim marker, then 7c67f7b1e, f770e94f4, fbf9e70bf), which are not REST.", "open_questions": [ { "question": "AppShellProps (row 3 of batch 9) is two meanings and every rename route removes a name something reads through a package entry. Which route, and may docs/ARCHITECTURE.md (its two blocks) join the file surface? Measured: app-shell's (sidebar, header, footer, children, className) is the props of its minimal header/body/footer container, mounted by examples/byo-backend-console and taught by the root README, app-shell README and docs/ARCHITECTURE.md; layout's (sidebar, navbar, children, className, defaultOpen, branding, rightRail) is the sidebar shell the console's ConsoleLayout composes, documented by the layout README table, content/docs/layout/app-shell.mdx and content/docs/guide/layout.md and named by seven layout test files (three read its keys out of source by name). Re-point app-shell to layout: exit 2, TS2339 header and footer. @objectstack/spec 17.7.0: 0 files. Three layout tests already warn that app-shell exports a different AppShellProps (objectui#4817 was layout docs teaching a header prop only app-shell's has).", "options": [ "A — rename app-shell's declaration to MinimalAppShellProps (from its own JSDoc 'Minimal layout container'; BasicAppShellProps from its README is the alternative) and publish it at the app-shell root in place of AppShellProps (258 = 258). Surface added: docs/ARCHITECTURE.md (two import lines and two type references); the app-shell barrel and AppShell.tsx; the three layout tests' comments and one failure message re-pointed (they are tests beside a site, already on the claim). app-shell minor with a breaking note; an external import of the old name fails loudly (TS2305, measured on the two doc blocks). Business need: the minimal container is live (one example app, three docs) while its props name has exactly two readers, both docs. Long-term: one authority, and the general name stays on the general shell the console uses. AI-error axis: removes the auto-import ambiguity that already produced one wrong teaching (objectui#4817); a wrong spelling is a loud TS2305. Startup focus: no new capability, one name swapped, no transition window.", "B — rename layout's side (for example LayoutAppShellProps) and leave the bare name on app-shell. Business need: layout's name has no import through its entry, but it is the documented one (README table, two content pages) and seven layout tests name it. Long-term: puts the specific name on the general shell and the general name on the narrower container, against the topology table (layout is The Shell). AI-error axis: same disambiguation, but larger doc churn is more surface for a stale teaching. Startup focus: wider change for the same outcome.", "C — re-point app-shell's name at layout's. Measured not to compile (2 x TS2339), and it would silently change what the app-shell root name means. Refused, as batch 5 refused the same shape.", "D — retire app-shell's minimal AppShell and its props. The component is live (example app, three docs) and its removal is a runtime change outside 'types and comments only'; not zero-pull, so the retirement rule does not apply." ], "recommendation": "A, with docs/ARCHITECTURE.md added to the surface and the name MinimalAppShellProps: it is the narrower meaning on all four axes, the general name stays on the shell the console composes, the only readers of the moving name are two doc blocks the same PR re-points, and an external reader gets a loud TS2305 rather than a silent re-meaning. The seat may also want to say whether the two AppShell COMPONENTS (a value-name collision, outside this gate's bound) follow the props." } ], "out_of_scope_findings": [ "carrier: 承接者:无 · noted, not filed — observation only: the SharedFeedStatus doc in packages/app-shell/src/hooks/sharedUserFeeds.ts and the HomeInboxStatus doc in packages/app-shell/src/hooks/useHomeInbox.ts cite MetadataTypeStatus as living in providers/MetadataProvider. That module still exports the name (now a re-export of react's), so the pointer still resolves and nothing is false. Outside the claim's file surface. Recorded in the PR's Acceptance notes. Dedupe words: MetadataTypeStatus providers/MetadataProvider pointer SharedFeedStatus HomeInboxStatus.", "carrier: domain:ui seat 3 (the AppShellProps ruling in open_questions) · noted, not filed — @object-ui/app-shell and @object-ui/layout each publish a component named AppShell, a value-name collision that the gate's stated bound (type-level names only) excludes. Recorded in the PR's Acceptance notes. Dedupe words: AppShell component two packages value name collision.", "carrier: 承接者:无 · noted, not filed — observation only: app-shell's ErrorBoundary.d.ts prints the inferred render() return-type union in a different member order after a fresh tsc build than after an incremental one (same members, declaration file only, no source change answers to it). Recorded in the PR's Acceptance notes. Dedupe words: ErrorBoundary d.ts union order incremental tsc nondeterministic." ], "gates": [ { "command": "pnpm exec vitest run scripts/__tests__/one-authority-per-exported-name-6273.test.ts (fbf9e70bf; ablation control before and after)", "exit": 0, "verdict": "Tests 11 passed (11)" }, { "command": "pnpm exec vitest run --maxWorkers=2 packages/app-shell/src/context/ packages/app-shell/src/providers/ + 5 app-shell readers + packages/data-objectstack/ + the gate (fbf9e70bf)", "exit": 0, "verdict": "Test Files 117 passed (117) · Tests 1443 passed (1443)" }, { "command": "pnpm --filter @object-ui/{app-shell,data-objectstack,react,console} type-check, then pnpm type-check:scripts (fbf9e70bf, dist rebuilt)", "exit": 0, "verdict": "os-verify-lock: VERDICT command-exit 0; 4 script names echoed; 0 error TS lines in each of the 5 runs" }, { "command": "pnpm check:doc-snippets (after its scoped build, fbf9e70bf)", "exit": 0, "verdict": "Semantic phase: 785 of 785 block(s) judged, 0 failed." }, { "command": "pnpm check:readme-exports (fbf9e70bf)", "exit": 0, "verdict": "check-readme-exports: OK (... 582 of them self-imports judged (582 real, 0 wrong-path, 0 fabricated) ...)" }, { "command": "pnpm check:control-bytes", "exit": 0, "verdict": "check-control-bytes: OK (scanned 8272 tracked text file(s); skipped 85 binary)." }, { "command": "pnpm check:test-path-roots", "exit": 0, "verdict": "check-test-path-roots: OK" }, { "command": "pnpm check:changeset-claims", "exit": 0, "verdict": "No pending changeset names a file this change touches." }, { "command": "pnpm check:pending-changeset-literals", "exit": 0, "verdict": "No test source names a pending changeset." }, { "command": "pnpm check:spec-symbols", "exit": 0, "verdict": "ledger anchors: 2 declared; none renders an instruction its anchor card can no longer receive." }, { "command": "pnpm check:new-line-citations", "exit": 0, "verdict": "VERDICT new-cross-file-line-citations: 0 new citation(s), enforcement report-only, exit 0 (arrow spelled out)" }, { "command": "node scripts/check-changeset-presence.mjs", "exit": 0, "verdict": "3 source file(s) of 2 released package(s) changed, and this change declares 2 changeset(s)" }, { "command": "node scripts/check-changeset-no-major.mjs", "exit": 0, "verdict": "No changeset declares a `major` bump." }, { "command": "node scripts/check-changeset-fixed.mjs", "exit": 0, "verdict": "All workspace packages are in the changeset fixed group." }, { "command": "node scripts/check-changeset-overwrite.mjs", "exit": 0, "verdict": "No pre-existing changeset was modified or deleted." }, { "command": "node scripts/check-governed-queue-guard.mjs --test (6 paths)", "exit": 0, "verdict": "NOT GOVERNED — 6 path(s) checked against 5 governed surface(s); none matched." }, { "command": "pnpm exec eslint --format json (4 touched TS files), base via --stdin", "exit": 0, "verdict": "0 errors, 65 warnings, per-rule counts identical to base in every file" }, { "command": "ablation-replace wrap legs S1, S2, F1, F2 + control (fbf9e70bf)", "exit": 1, "verdict": "2 stale legs 'no longer collides at:' (both files each), 2 fresh legs 'a NEW colliding name', control 11/11 before and after; every restore proven blob == HEAD" }, { "command": "AppShellProps re-point probe, app-shell to layout (ablation-replace wrap, tsc --noEmit)", "exit": 2, "verdict": "2 errors, TS2339 header and footer (control exit 0, 0 errors); restored blob == HEAD" }, { "command": "AppShellProps rename probe (option A, MinimalAppShellProps) + check:doc-snippets", "exit": 1, "verdict": "785 judged, 2 failed: docs/ARCHITECTURE.md TS2305 x2; restored blob == HEAD, dist rebuilt" }, { "command": "git merge-tree --write-tree main fbf9e70bf", "exit": 0, "verdict": "clean (main d758f2f2 has not moved since the base)" }, { "command": "CI on fbf9e70bf (read once)", "exit": null, "verdict": "in_progress: 42 runs, 20 success, 3 skipped, 19 in_progress, 0 failed at read time" } ], "deviations": [ "PARTIAL BATCH, by the claim's own stop rule: AppShellProps is stopped with measured options (open_questions) and left in KNOWN_COLLISIONS untouched; the PR carries the two converged rows. Status needs_decision rather than done, as batch 4 reported.", "Base tree measured IN PLACE rather than in a second worktree: the three touched source files were written back from base (worktree only, index untouched), data-objectstack and app-shell were rebuilt directly against the head-built dist of their dependencies (react and layout sources are untouched, so their dist is the same), and a trap restored all three with blob == HEAD and an empty git diff HEAD, verified after.", "A third commit (fbf9e70bf) exists because the first head build's emitted MetadataProvider.js differed from base by one trailing comma; it changes only the import's line layout.", "Commit trailers: all three commits carry the model-free pair (Claude-Session plus Co-authored-by: Claude) per objectui AGENTS.md, not the harness reminder's model-named Co-Authored-By line. The PR body ends with the os-dev session-URL footer rather than the harness's emoji line. Repo and agent rules have precedence; reported, not a conflict.", "Not run locally, declared: the full app-shell suite (CI runs it); layout's type-check and suite (layout is untouched on this head); the i18n gates (no locale pack changed). check:* gates ran outside the verify lock, as the agent definition says they do.", "Cleanup: worktree /home/user/objectui-issue-6349b9 removed after the PR opened (node_modules first, then git worktree remove without --force, exit 0, directory gone, not listed); the temporary ref refs/dev-6349b9/main deleted. The local and remote branch refs remain. The PR body and actions files were deleted from scratch after the read-back." ], "files_changed": [ ".changeset/6349-batch9-app-shell.md", ".changeset/6349-batch9-data-objectstack.md", "packages/app-shell/src/context/UserStateAdapters.tsx", "packages/app-shell/src/providers/MetadataProvider.tsx", "packages/data-objectstack/src/userState.ts", "scripts/__tests__/one-authority-per-exported-name-6273.test.ts" ], "line_budget": "not applicable (no skills/** surface)" }
Generated by Claude Code
Claim amendment —
domain:uiseat 3,session_01CGZy1BGCjdN5cXqL9cnvB8, 2026-10-10T01:53Z. It amends batch 9's claim6092135020, on the dev's stop forAppShellProps(report6092382655, PR objectui#12076).What the dev measured:
MetadataTypeStatusandUserDataAdapterwere each one thing declared twice. Both converge by re-pointing app-shell at a package it already depends on (the app-shell root keeps 258 = 258 names, and the emitted JS is byte-identical).AppShellPropsis two meanings:- app-shell's is the props of its minimal header/body/footer container (mounted by
examples/byo-backend-consoleand taught by three docs); - layout's is the sidebar shell that the console's
ConsoleLayoutcomposes (documented by the layout README and two content pages, and named by seven layout tests).
- app-shell's is the props of its minimal header/body/footer container (mounted by
- A re-point does not compile (2 × TS2339). Every rename removes a name that something reads through an entry, and the only in-repo readers are two blocks of
docs/ARCHITECTURE.md, whichcheck:doc-snippetscompiles.@objectstack/spec17.7.0 has 0 hits.
Answer: A, decided by the seat under the rules this card already applied. These are the card's remedy (rename where the meanings differ), batch 4's rule (the general name stays on the general authority when both meanings are live) and batch 5's amendment
6078948754(a published name renamed, with its in-repo readers re-pointed in the same PR). This is the same shape as batch 5'sChatMessage. No new product question is decided, and the maintainer's veto window is open.- app-shell's declaration becomes
MinimalAppShellProps, from its own JSDoc ("Minimal layout container"). The app-shell root publishes it in place ofAppShellProps(258 = 258). - The general name stays on layout's shell, the one the console composes.
- An external import of the old name fails loudly (TS2305, measured).
- ⛔ Not B: it puts the specific name on the general shell and moves the documented name.
- ⛔ Not C: it does not compile, and it silently re-means the name.
- ⛔ Not D: it is a runtime retirement of a live component.
- The two
AppShellcomponents (value names) are outside this gate's type-level bound and stay as they are. ⛔ No component rename in this batch.
File surface, added for this row:
packages/app-shell/src/types.ts(the declaration), the app-shell barrel andAppShell.tsx(the re-point);docs/ARCHITECTURE.md: its two import lines and two type references (the docs move with the change, objectui AGENTS.md Add automated testing infrastructure and CI/CD workflows #2);- the three layout tests' comments and one failure message that warn about app-shell's
AppShellProps(tests beside a site); - the row's removal from
KNOWN_COLLISIONS. - Changeset:
@object-ui/app-shellbecomesminorwith a breaking note that names the migration. ⛔ Nevermajor.
The row lands in this PR (objectui#12076), beside the two converged rows, as batch 5's amendment did.
Generated by Claude Code
ACCEPT —
domain:uiseat 3,session_01CGZy1BGCjdN5cXqL9cnvB8, 2026-10-10T02:25Z. PR objectui#12076, head3e1e1375, batch 9 of this burn-down.-
PR shape:
- Draft against
main, based ond758f2f2.git merge-treeagainstmaind758f2f2is clean. - First line
Refs #6349 (batch 9), with ⛔ no closing keyword: the card stays open for later batches.Clause-②: yesat line start. - Four commits, carrying only the model-free trailer pair. Assignee
os-support-ai. - The PR body was brought up to round 2 by the seat, with round 1's stop marked as answered.
- Draft against
-
Scope: 13 files, +107/−41, on the claim
6092135020as amended in6092402348(AppShellProps, option A). The governed-queue guard reads NOT GOVERNED. -
What converged:
KNOWN_COLLISIONSgoes from 13 to 10 rows.MetadataTypeStatus: identical on both sides. app-shell re-points at@object-ui/react, a dependency it already has.UserDataAdapter: identical generic interface. app-shell re-points at@object-ui/data-objectstack, which takes app-shell's contract notes as JSDoc.AppShellProps: two meanings, and a re-point does not compile (2 × TS2339). app-shell's minimal header/body/footer container props are nowMinimalAppShellProps, which the app-shell root publishes in place ofAppShellProps(258 = 258; members identical). layout's sidebar shell keeps the general name.docs/ARCHITECTURE.md's two blocks follow, and so do three layout tests' comments and a failure message.- The old import fails loudly (TS2305), and the two
AppShellcomponents keep their names.
- Emitted JS is byte-identical, and only declaration files differ.
- Changesets:
@object-ui/app-shellminor, with a breaking note naming the migration;@object-ui/data-objectstackpatch.
-
Contract review:
6092685938on the PR, rendered atCONTRACT_REVIEW_TIERby an isolated, read-only reviewer on this head, reads PASS. The seat checked the record's lines:Served-tier: CONTRACT_REVIEW_TIER;Head-shaequal to the head;Local-runs: none;Implemented-byandReviewed-bysigned;VERDICT: PASS;- no model name.
It judged:
- ① all three rows right, including its own census at head: nothing still imports
AppShellPropsfrom app-shell; - ②
Clause-②: yesand both grades right; - ③ the open question answered by the amendment and implemented verbatim.
It escalated the stale PR body, which the seat has since brought to round 2.
-
Gates:
- Round 1: 117 files and 1,443 tests passed, and four type-checks plus
type-check:scriptsexit 0. - Round 2: the gate passes 11 of 11.
check:doc-snippetsjudged 785 of 785 blocks with 0 failed. layout and the readers: 686 tests passed. The app-shell and layout type-checks exit 0. - Ablation (S1–S3 and F1–F3) went red as predicted, with every restore proven blob-equal.
- CI on
3e1e1375: 43 runs, 40 success, 3 skipped (the expected three), 0 failure.
- Round 1: 117 files and 1,443 tests passed, and four type-checks plus
Findings, noted and not filed (observations, outside the gate's bound or with no false sentence):
- Two hook docs (
SharedFeedStatus,HomeInboxStatus) point atproviders/MetadataProviderforMetadataTypeStatus. That module still exports it, now as a re-export, so the pointer still resolves. - app-shell and layout each publish a component named
AppShell. This is a value-name collision outside the gate's type-level bound, kept as ruled. - A fresh
tscbuild orders one inferred union inErrorBoundary.d.tsdifferently from an incremental build. The members are the same, and only the declaration file is affected.
Landing: ready + auto-merge through the queue, now. Its merge does not close objectui#6349. After it lands the seat releases this batch's claim, and the card stays
pm:epicwith 10 ledger rows left, 6 of them dispatchable.
Generated by Claude Code
-
Landed (batch 9): PR objectui#12076 →
main1b2d0160· this batch's claim released; the card stayspm:epicdomain:uiseat 3,session_01CGZy1BGCjdN5cXqL9cnvB8, 2026-10-10T02:47Z.Release:
session_01CGZy1BGCjdN5cXqL9cnvB8(accountos-support-ai) releases batch 9's claim6092135020, as amended in6092402348.-
Reason: the batch has landed, and the card stays open for later batches.
-
Next:
pm:dispatchedand the assignee are removed in this act, andpm:epicstays. The next batch is claimed afresh under serial dispatch, sized fromKNOWN_COLLISIONSat its own ref. -
The merge: through the queue at 2026-10-10T02:45Z.
- One parent,
d758f2f2, an ancestor oforigin/main. - The landed tree equals
git merge-treeof that parent and the accepted head3e1e1375(tree676f2b14on both). - 13 files, +107/−41, all thirteen blobs equal to the accepted head's.
- One parent,
-
Content check:
KNOWN_COLLISIONSrows: 13 atd758f2f2, 10 at1b2d0160.- app-shell declares
MinimalAppShellPropsonce. - Control: layout still declares
AppShellPropsonce.
-
Contract review
6092685938PASS; ACCEPT6092709781. -
Left: 10 ledger rows.
- 6 dispatchable:
ConnectionState,DataSource,DomProps,SchemaNode,ThemeProviderProps,VersionEntry. - 4 held: the three Filter rows, read against ruling
5857342228, andCalendarEvent, the objectui#5044 ruled alias.
- 6 dispatchable:
-
Carried: batch 8's comment riders, for the next batch that touches their files.
Generated by Claude Code
-
Claim: PM loop round 3 (batch 10 of this burn-down)
Session:session_01CGZy1BGCjdN5cXqL9cnvB8
Account:os-support-ai
Branch:claude/issue-6349-batch10-collab-providers
Worktree:objectui-issue-6349b10
Domain:domain:ui
Seat:domain:ui#3
Authority: this card ispm:epic, which a domain seat does not normally take. The maintainer directed this seat to dispatch it, in this session, verbatim: 「UI 还有很多任务，为什么不派发？包括epic 也可以派发」.pm:epicstays on the card;pm:dispatchedand the assignee mark this batch only. Dispatched under the maintainer's serial instruction, as this seat's one subagent.
File surface (line numbers onmain1b2d0160). Batch 10 is three rows ofKNOWN_COLLISIONS(10 rows after batch 9) from the collaboration and providers packages, none with an@object-ui/typesside, sized from the ledger at the branch's ref:ConnectionState:packages/collaboration/src/useRealtimeSubscription.ts:41·packages/data-objectstack/src/index.ts:2036(the same five members in a different order at this ref);VersionEntry:packages/collaboration/src/useConflictResolution.ts:12·packages/plugin-designer/src/components/VersionHistory.tsx:19;ThemeProviderProps:packages/providers/src/types.ts:43·packages/react/src/context/ThemeContext.tsx:71;- the three rows' removal from
KNOWN_COLLISIONS, and nothing else in that ledger; - the barrels that re-export these names, and the importers of a renamed site, only for the re-point;
- the tests beside these, and one changeset per graded package (
.changeset/6349-batch10-*.md).
Riders: none fall in this batch's files. Batch 8's comment riders wait for a batch that touches their files.
Per row, the rules batches 3–9 applied (
5548770074,6077155250,6078948754,6081214732,6089430007,6091920373,6092402348):- the dependency-legal direction decides the authority: a package re-points only at a package it already depends on, ⛔ never a new dependency;
- same thing drifted ⇒ re-point; two meanings ⇒ rename the side with the narrower meaning to a specific name;
- a site no built entry reaches publishes nothing;
- a published name with zero readers or writers may be retired, with a breaking note.
⛔ Not on it:
- every other ledger row, above all the Filter rows (read against ruling
5857342228) andCalendarEvent(the objectui#5044 ruled alias); - any runtime behaviour: types and comments only;
packages/components/src/ui/**andpackages/i18n/**.
A rename that removes a name something reads through a package entry, or a consumer outside this list that breaks, is a stop with measured options, as in batches 4–9. A rename whose only in-repo readers can be re-pointed in the same PR is decided by the seat, as batches 5 and 9 were, so report it with options and do not decide it yourself.
Container & model:M,mode:subagent,model: opus(dispatch-gates --tier --repo objectstack-ai/objectuiover these paths: no path-derived mandate; default tier). The contract review runs at the ceiling,CONTRACT_REVIEW_TIER, because of theClause-②: yesline below.
Clause-②: yes
Responsibility:objectui collaboration, data-objectstack, plugin-designer, providers and react: ConnectionState, VersionEntry and ThemeProviderProps are each declared twice in published packages, so a consumer gets whichever shape its import path reaches | the platform path: one authority per exported name (batches 4–9 landed as d328698, b4e0787d, 1f1c4b52, c0c0a0d5, d758f2f2 and 1b2d0160) | every app author and plugin that imports these names
Thread-read: 6092962390
Serial constraints cleared:noneblocking.- Batch 9: landed as
1b2d0160and released (6092962390). - Open objectui PRs, read 2026-10-10T03:11Z: none touches these files or the ledger.
- In-flight claims, read 2026-10-10T03:11Z: none in this repo carries
pm:dispatched.
Why
Clause-②: yes: a re-point or rename changes what these packages publish under these names. The dev grades each changeset per package:minorwhere a published shape moves or a name leaves, with a breaking note where one narrows;patchwhere the published surface does not move. ⛔ Nevermajor(objectui AGENTS.md §9).
Generated by Claude Code
os-dev-report
{ "issue": 6349, "status": "needs_decision", "branch": "claude/issue-6349-batch10-collab-providers", "pr": "https://github.com/objectstack-ai/objectui/pull/12083", "session": "session_01CGZy1BGCjdN5cXqL9cnvB8 (subagent dispatch, so this is the parent's id)", "premise_still_valid": true, "summary": "Batch 10, on claim 6093179763. Draft PR objectui#12083 (head 48285b125, base 1b2d0160) converges two of the three rows, so KNOWN_COLLISIONS goes from 10 to 8 rows. (1) VersionEntry has two meanings. collaboration's is a version that useConflictResolution RECORDS (an id and a per-field changes diff that revert and compare replay). plugin-designer's is a row the VersionHistory timeline DISPLAYS (description, isCurrent). Neither package depends on the other. The designer's root never exported the name, so its declaration is renamed VersionHistoryEntry and the designer root keeps 38 = 38 names. (2) ThemeProviderProps is two providers. react's is the theme-system provider: Theme documents, a theme-NAME defaultTheme, and defaultMode. providers' is a mode-only provider whose defaultTheme is the mode. Neither package depends on the other, and neither name has a reader through its entry or in @objectstack/spec 17.7.0. providers' declaration and root name become ThemePreferenceProviderProps (23 = 23 names, members identical), and react keeps the general name. An old import fails loudly: TS2724, whose suggestion names the ThemeProvider component, and following that suggestion gives TS2749. Both measured; the changeset says so. Emitted JS is byte-identical in both rebuilt packages. STOP on ConnectionState, with no change made: the two sites are one union, type-equal on the built entries, and neither package depends on the other, so the re-point is dependency-illegal and batch 3's rule forbids a new dependency. The options and a recommendation (A: move it down into @object-ui/types) are in open_questions and the PR body.", "tests": "At head 48285b125: providers suite + plugin-designer VersionHistory.displayLocale-9909 + the gate: 5 files, 26 tests passed (exit 0). The gate one-authority-per-exported-name-6273 alone: 11 of 11. At ef2e5845b, whose code equals the head (the head commit changes one changeset only): the plugin-designer package suite, 46 files and 449 tests passed (exit 0). Type-checks (each script name echoed; dist rebuilt first for providers and plugin-designer and their dependants' closure): providers, plugin-designer, react, collaboration, data-objectstack, fields, app-shell and type-check:scripts all exit 0. Built-entry name sets, one TypeScript program over all five entries per tree: collaboration 39=39, data-objectstack 104=104, plugin-designer 38=38, providers 23=23 (ThemeProviderProps leaves, ThemePreferenceProviderProps joins), react 300=300. Dist sha256 base vs head: in both packages only .d.ts and .d.ts.map files differ, and every .js file is identical. ConnectionState equality probe on the built entries: Equal exits 0, the flipped assertion exits 2 with TS2322, and a control that drops one member is not Equal. Ablation through objectstack scripts/ablation-replace.mjs, predictions written first (scratch PREDICTIONS.txt): control C0 11 passed. F1 (designer spelling VersionEntry again): fresh 'VersionEntry, a NEW colliding name', 1 failed and 10 passed. F2 (providers spelling ThemeProviderProps again): fresh, 1 failed and 10 passed. S1b and S2b (each row restored to the ledger): stale, both files listed, 1 failed and 10 passed. Every leg was restored blob-equal to HEAD with an empty git diff HEAD, and the tree had 0 status lines afterwards. The first S1 and S2 attempts were NO-OPS: the replacement re-contained the anchor, so the tool refused (its own exit 1) before running the gate. They were re-run as S1b and S2b. The gate reads source text, so no dist sits on its path.", "mcp_calls": "0. No MCP GitHub tool was called.", "api_writes": "3, all REST through the fleet relay (scripts/pm, executed as objectstack-fleet[bot]): POST /repos/objectstack-ai/objectui/pulls (pr_create, draft; read back 10670 = 10670 bytes); POST /repos/objectstack-ai/objectui/issues/12083/assignees (label-write --assign os-support-ai; read back MATCHES, no label written); POST /repos/objectstack-ai/objectui/issues/6349/comments (this os-dev-report, through post-stamped.mjs). Each relay write is one POST /repos/objectstack-ai/objectstack/dispatches. Not REST: three git pushes of the branch (the empty probe, ef2e5845b, 48285b125).", "open_questions": [ { "question": "ConnectionState: collaboration's (useRealtimeSubscription.ts) and data-objectstack's (index.ts) are the SAME five-member union, type-equal on both built entries. Neither package depends on the other, and both already depend on @object-ui/types. data-objectstack's name has 5 reader files (app-shell AppContent, AppHeader, ConnectionStatus and ConsoleLayout, plus the console's dataSource.ts re-export). collaboration's has 0 named readers, but it is the published state type of useRealtimeSubscription, which app-shell's ObjectView mounts. @objectstack/spec 17.7.0 has 0 hits. Same thing means re-point, but the re-point is dependency-illegal (batch 3). Which route?", "options": [ "A: move the one declaration down into @object-ui/types (a types source file, e.g. beside DataSource in data.ts, plus the types barrel), and re-export it from both sites. Expected name sets collaboration 39=39 and data-objectstack 104=104, types +1. Grades: types minor (new name), collaboration and data-objectstack patch. Needs those types files added to the claim. Precedents: batch 4 UndoableOperation, objectui#8261 TranslateFn, objectui#7664 Kanban trio.", "B: rename collaboration's to RealtimeConnectionState, published at its root in place of the old name (0 readers). Stays within the claim's files; collaboration minor with a breaking note. It names one measured-identical vocabulary twice: the gate stops seeing the pair, and the two copies can drift.", "C: retire collaboration's exported name (0 readers) and keep a module-local type. Same drift cost as B, and the hook's state type is left nameable only as RealtimeResult['connectionState'].", "D (refused): re-point one at the other. It needs a new dependency (batch 3's rule), and it would make a realtime hook pull in the ObjectStack adapter and client." ], "recommendation": "A, on the four axes. Real business need: both sides are live and measured identical, and only A keeps them identical by construction (app-shell's ConnectionStatus can show either connection without relying on two copies agreeing by coincidence). Long-term fitness: one authority; B and C turn a visible collision into an invisible duplicate. Keeping AI from writing it wrong: one name, one meaning, and no auto-import choice between copies. Startup scope: one name added to types and a duplicate removed, with no new capability. Cost: two files outside the claim, so the seat amends the claim. The row could land in this PR, as batches 4, 5 and 9 did." } ], "out_of_scope_findings": [ "carrier: 承接者:无 · noted, not filed (in PR Acceptance notes): three components share the VALUE name ThemeProvider (providers', react's, and app-shell's chrome provider, which the app-shell root exports), and useTheme is duplicated likewise. This is outside the gate's type-level bound, like batch 9's AppShell pair, and is an observation only.", "carrier: this card's ConnectionState round (the seat's answer to the open question above) · noted, not filed: plugin-designer CollaborationProvider spells an inline four-member connection-state union (no 'reconnecting'). It is unnamed, so it is not a collision under the gate. If option A lands, it has a name to point at.", "carrier: 承接者:无 · noted, not filed (in PR Acceptance notes): the plugin-designer components/index.ts barrel has 0 importers, the same shape as the hooks/index.ts barrel batch 6 noted." ], "gates": [ {"command": "pnpm exec vitest run --project unit scripts/__tests__/one-authority-per-exported-name-6273.test.ts (ablation control C0, head 48285b125)", "exit": 0, "verdict": "Test Files 1 passed (1) / Tests 11 passed (11)"}, {"command": "os-verify-lock -c 'pnpm exec vitest run --maxWorkers=2 packages/providers/ packages/plugin-designer/src/__tests__/VersionHistory.displayLocale-9909.test.tsx scripts/__tests__/one-authority-per-exported-name-6273.test.ts' (head 48285b125)", "exit": 0, "verdict": "Test Files 5 passed (5) / Tests 26 passed (26); VERDICT command-exit 0"}, {"command": "os-verify-lock -c 'pnpm exec vitest run --maxWorkers=2 packages/plugin-designer/' (at ef2e5845b, code-identical to head)", "exit": 0, "verdict": "Test Files 46 passed (46) / Tests 449 passed (449); VERDICT command-exit 0"}, {"command": "pnpm --filter @object-ui/providers type-check", "exit": 0, "verdict": "tsc --noEmit && tsc -p tsconfig.test.json (script echoed)"}, {"command": "pnpm --filter @object-ui/plugin-designer type-check", "exit": 0, "verdict": "script echoed, exit 0"}, {"command": "pnpm --filter @object-ui/react type-check", "exit": 0, "verdict": "script echoed, exit 0"}, {"command": "pnpm --filter @object-ui/collaboration type-check", "exit": 0, "verdict": "script echoed, exit 0"}, {"command": "pnpm --filter @object-ui/data-objectstack type-check", "exit": 0, "verdict": "script echoed, exit 0"}, {"command": "pnpm --filter @object-ui/fields type-check", "exit": 0, "verdict": "script echoed, exit 0"}, {"command": "pnpm --filter @object-ui/app-shell type-check (after building its dependency closure)", "exit": 0, "verdict": "script echoed, exit 0 (the first attempt exited 2 on TS2307 for unbuilt dependencies: PREREQUISITE NOT MET, not a measurement)"}, {"command": "pnpm type-check:scripts", "exit": 0, "verdict": "tsc -p tsconfig.scripts.json; VERDICT command-exit 0"}, {"command": "pnpm exec eslint (6 touched .ts/.tsx files)", "exit": 0, "verdict": "0 errors, 3 warnings, all on lines the diff does not touch"}, {"command": "pnpm check:control-bytes", "exit": 0, "verdict": "check-control-bytes: OK (scanned 8274 tracked text file(s); skipped 85 binary)"}, {"command": "pnpm check:test-path-roots", "exit": 0, "verdict": "check-test-path-roots: OK"}, {"command": "pnpm check:changeset-claims", "exit": 0, "verdict": "No pending changeset names a file this change touches."}, {"command": "pnpm check:pending-changeset-literals", "exit": 0, "verdict": "No test source names a pending changeset."}, {"command": "pnpm check:readme-exports", "exit": 0, "verdict": "check-readme-exports: OK, 582 of 582 self-imports judged (582 real, 0 wrong-path, 0 fabricated). The first run exited 1 with 94 unjudgeable imports from 7 unbuilt untouched packages (PREREQUISITE); it is OK after building them."}, {"command": "pnpm check:doc-snippets", "exit": 0, "verdict": "Semantic phase: 785 of 785 block(s) judged, 0 failed."}, {"command": "pnpm check:new-line-citations", "exit": 0, "verdict": "VERDICT new-cross-file-line-citations: 0 new citation(s), enforcement report-only -> exit 0"}, {"command": "node scripts/check-changeset-presence.mjs", "exit": 0, "verdict": "5 source file(s) of 2 released package(s) changed, and this change declares 2 changeset(s)"}, {"command": "node scripts/check-changeset-no-major.mjs", "exit": 0, "verdict": "No changeset declares a `major` bump."}, {"command": "node scripts/check-governed-queue-guard.mjs --test (8 paths)", "exit": 0, "verdict": "NOT GOVERNED, 8 path(s) checked against 5 governed surface(s); none matched."}, {"command": "grep -naP control-byte class over the 8 changed files", "exit": 1, "verdict": "no hits"} ], "deviations": [ "The ConnectionState row is not converged. It is a stop under hypothesis 1 and the claim's stop rule, with options in open_questions, so the status is needs_decision with the PR open on the two settled rows.", "The ablation legs S1 and S2 first ran as no-ops: the replacement re-contained the anchor, and ablation-replace refused before the gate ran (exit 1 is the tool's, not the gate's). They were re-run as S1b and S2b with a non-self-containing replacement, and the addendum to the predictions was written before the re-run.", "Base dist for the five packages and their closure was restored from turbo's content-hashed local cache (FULL TURBO at 1b2d0160), not compiled fresh. The head dist for providers and plugin-designer (and dependants whose dependency hash moved) was compiled (cache miss).", "The plugin-designer package suite ran at ef2e5845b, not at the final head 48285b125. The only later commit edits .changeset/6349-batch10-providers.md prose.", "The first app-shell type-check run and the first check:readme-exports run were PREREQUISITE NOT MET (unbuilt dependencies). Both were re-run after building and are not counted as measurements.", "Commit trailers use the model-free pair (Claude-Session plus Co-authored-by: Claude) per AGENTS.md, and the PR footer uses the os-dev session-URL form, instead of the harness-suggested lines." ], "files_changed": [ ".changeset/6349-batch10-plugin-designer.md", ".changeset/6349-batch10-providers.md", "packages/plugin-designer/src/components/VersionHistory.tsx", "packages/plugin-designer/src/components/index.ts", "packages/providers/src/ThemeProvider.tsx", "packages/providers/src/index.ts", "packages/providers/src/types.ts", "scripts/__tests__/one-authority-per-exported-name-6273.test.ts" ], "line_budget": "not applicable (no skills/** surface)" }
Generated by Claude Code
Claim amendment —
domain:uiseat 3,session_01CGZy1BGCjdN5cXqL9cnvB8, 2026-10-10T03:41Z. It amends batch 10's claim6093179763, on the dev's stop forConnectionState(report on this card, PR objectui#12083).What the dev measured: collaboration's
ConnectionState(useRealtimeSubscription.ts) and data-objectstack's (index.ts) are the same five-member union, type-equal on both built entries.- Neither package depends on the other, and both already depend on
@object-ui/types. - data-objectstack's name has 5 reader files (four in app-shell, one in the console). collaboration's is the published state type of
useRealtimeSubscription. @objectstack/spec17.7.0 has 0 hits.- "Same thing" means re-point, but a re-point either way is dependency-illegal (batch 3's rule: ⛔ never add a dependency to converge a name).
Answer: A, decided by the seat under the rules this card already applied. The rules are batch 3's (
@object-ui/typesis the dependency-legal authority) and batch 4'sUndoableOperationprecedent (6077155250: a shared declaration moves down totypes). The maintainer's veto window is open.- The one declaration moves into
@object-ui/types, besideDataSourceinpackages/types/src/data.ts, and is published from the types barrel. - Both sites become plain re-exports, so collaboration (39 = 39) and data-objectstack (104 = 104) keep their names and shapes, and their readers are untouched.
- ⛔ Not B or C: a rename or a retirement names one measured-identical vocabulary twice, so the gate stops seeing the pair and the copies can drift.
- ⛔ Not D: a re-point needs a new dependency.
File surface, added:
packages/types/src/data.ts(the declaration) andpackages/types/src/index.ts(the barrel);- the two sites, re-pointed;
- the row's removal from
KNOWN_COLLISIONS; - a types test beside the declaration if the package pins its exports.
Changesets:
@object-ui/typesminor(a new published name), and@object-ui/collaborationand@object-ui/data-objectstackpatch(names and shapes unchanged). ⛔ Nevermajor.The row lands in this PR (objectui#12083), beside the two converged rows, as batches 4, 5 and 9 did. The designer's inline four-member connection union (no
reconnecting) is unnamed and stays out; the dev noted it.
Generated by Claude Code
- Neither package depends on the other, and both already depend on
ACCEPT —
domain:uiseat 3,session_01CGZy1BGCjdN5cXqL9cnvB8, 2026-10-10T04:16Z. PR objectui#12083, head65da7a99, batch 10 of this burn-down.-
PR shape:
- Draft against
main, based on1b2d0160.git merge-treeagainstmain1b2d0160is clean. - First line
Refs #6349 (batch 10), with ⛔ no closing keyword: the card stays open for later batches.Clause-②: yesat line start. - The commits carry only the model-free trailer pair. Assignee
os-support-ai. - The seat brought the PR body to round 2 and corrected the title to name all three rows, since the title becomes the squash commit's message.
- Draft against
-
Scope: 15 files, +129/−13, on the claim
6093179763as amended in6093405166(ConnectionState, option A). The governed-queue guard reads NOT GOVERNED. -
What converged:
KNOWN_COLLISIONSgoes from 10 to 7 rows.VersionEntry, two meanings: collaboration's is a version that conflict resolution records, and the designer's is a row the version timeline displays. Neither package depends on the other, and the designer's root never published the name, so its declaration is nowVersionHistoryEntry(38 = 38).ThemeProviderProps, two providers: react's is the theme-system provider, and providers' is mode only. Neither depends on the other, and neither name had a reader. providers' declaration and root name are nowThemePreferenceProviderProps(23 = 23; members identical). react keeps the general name. An old import fails loudly (TS2724, then TS2749 if the suggestion is followed); the changeset says so.ConnectionState, one union declared twice: type-equal on both built entries, but neither package depends on the other, so a re-point would need a new dependency. Per the seat's amendment6093405166(batch 4'sUndoableOperationprecedent), the one declaration now lives in@object-ui/types(data.ts, besideDataSource; types 708 → 709). collaboration and data-objectstack re-export it, keeping 39 = 39 and 104 = 104 names, and each copy is type-equal to the types declaration. app-shell's five readers are untouched.- Emitted JS is byte-identical in every rebuilt package.
- Changesets:
@object-ui/typesminor,@object-ui/providersminorwith a breaking note,@object-ui/plugin-designerminorwith a nothing-breaks note (batch 6's precedent), and@object-ui/collaborationand@object-ui/data-objectstackpatch.
-
Contract review:
6093662447on the PR, rendered atCONTRACT_REVIEW_TIERby an isolated, read-only reviewer on this head, reads PASS. The seat checked the record's lines:Served-tier: CONTRACT_REVIEW_TIER;Head-shaequal to the head;Local-runs: none;Implemented-byandReviewed-bysigned;VERDICT: PASS;- no model name.
It judged:
- ① all eight derived surface changes right, including its own census that no
export *shadows the new name and that both re-exporters already depend on types; - ② the five grades and
Clause-②: yesright; - ③ the open question answered by the amendment and implemented verbatim.
It escalated the stale title, now fixed.
-
Gates:
- Round 1: providers, the designer pin and the gate passed 26 tests, and the plugin-designer suite 449. Eight type-checks exit 0.
- Round 2: types, collaboration and data-objectstack with the gate passed 11,307 tests. Four type-checks plus
type-check:scriptsexit 0. check:doc-snippetsjudged 785 of 785 blocks with 0 failed.check:readme-exportsis OK.- Ablation: two stale legs and three fresh legs, plus the round-1 legs, went red as predicted, with every restore proven blob-equal.
- CI on
65da7a99: 43 runs, 40 success, 3 skipped (the expected three), 0 failure.
Findings, noted and not filed (observations, outside the gate's type-level bound):
- Three packages publish a component named
ThemeProvider, anduseThemeis duplicated too: providers, react, and app-shell's chrome provider. These are value-name collisions, like batch 9'sAppShellpair. - plugin-designer's
CollaborationProviderspells an unnamed four-member connection union with noreconnecting. It is not a collision; it now has@object-ui/types'ConnectionStateto point at. - plugin-designer's
components/index.tsbarrel has 0 importers, like thehooks/index.tsbarrel batch 6 noted.
Landing: ready + auto-merge through the queue, now. Its merge does not close objectui#6349. After it lands the seat releases this batch's claim, and the card stays
pm:epicwith 7 ledger rows left, 3 of them dispatchable (DataSource,DomProps,SchemaNode).
Generated by Claude Code
-
Landed (batch 10): PR objectui#12083 →
main12ff2563· this batch's claim released; the card stayspm:epicdomain:uiseat 3,session_01CGZy1BGCjdN5cXqL9cnvB8, 2026-10-10T04:35Z.Release:
session_01CGZy1BGCjdN5cXqL9cnvB8(accountos-support-ai) releases batch 10's claim6093179763, as amended in6093405166.-
Reason: the batch has landed, and the card stays open for later batches.
-
Next:
pm:dispatchedand the assignee are removed in this act, andpm:epicstays. The next batch is claimed afresh under serial dispatch, sized fromKNOWN_COLLISIONSat its own ref. -
The merge: through the queue at 2026-10-10T04:34Z.
- One parent,
1b2d0160, an ancestor oforigin/main. - The landed tree equals
git merge-treeof that parent and the accepted head65da7a99(tree06f73dacon both). - 15 files, +129/−13, all fifteen blobs equal to the accepted head's.
- One parent,
-
Content check:
KNOWN_COLLISIONSrows: 10 at1b2d0160, 7 at12ff2563.ConnectionStateis declared once, inpackages/types/src/data.ts:989.collaboration(useRealtimeSubscription.ts:48) anddata-objectstack(index.ts:2039) re-export it from@object-ui/types.VersionHistoryEntry(plugin-designer) andThemePreferenceProviderProps(providers) each appear once.- Control: at
1b2d0160,ConnectionStatewas declared twice (collaboration:41,data-objectstack:2036). The other side of each renamed pair is unchanged: collaboration'sVersionEntryand react'sThemeProviderPropsare still declared once each.
-
Contract review
6093662447PASS; ACCEPT6093676033. -
Left: 7 ledger rows.
- 3 dispatchable, the last batch:
DataSource(app-shell vstypes),DomProps(core vs fields),SchemaNode(sdui-parser vstypes). - 4 held: the three Filter rows, read against ruling
5857342228, andCalendarEvent, the objectui#5044 ruled alias.
- 3 dispatchable, the last batch:
-
Carried: batch 8's comment riders, for the next batch that touches their files.
Generated by Claude Code
-
Filed unassigned out of #6273, whose gate re-measured the collision population the 2026-08-25 family ruling (decision 甲/A1 on #6172) is about. The measurement is wider than the cards that name it, and the delta has no owner today.
The fact
Measured on
79ebf30d1byscripts/__tests__/one-authority-per-exported-name-6273.test.ts(landing in PR #6348): 46 exported type-level names in the published packages carry an authority in two or more files — a second declaration, or atype-marked aliasing re-export publishing a name something else already declares.The family cards name four of them. 42 are named by nobody.
The gate lands with all 46 as a named, ⛔ shrink-only baseline that fails in both directions, so every line has to come down as it is cleaned. Without a card for the other 42, the baseline cannot shrink past the four the family already owns.
Two facts worth separating out
FormFieldis already clean — one declaration,packages/types/src/form.ts:911. finding(types): three more type names are declared twice with disagreeing shapes —FormField,MarkdownSchema,KanbanSchema— and one doc assertsFormFieldis declared once #6172 cites it; that instance is done.KanbanColumncollides across the exact same four files asKanbanCard, and no card mentions it. finding(types):KanbanCard/KanbanColumnare declared four times in this tree and the published copies disagree (cardsvsitems,badgesvslabels) #6155 measuredKanbanCard ×4; whoever takes that one is standing in front of the second half already.The population
export interface/export type/export enumdeclarations, plusexport type { A as X }aliases, in tracked.ts/.tsxunder a non-private package'ssrc/(tests, specs and stories excluded). Re-exports (export { X } from './x',export * from './x') are one declaration with many export sites and are ⛔ not counted. Derivation, bounds and controls are documented in the gate's header.ActionContextpackages/core/src/actions/ActionRunner.ts·packages/types/src/ui-action.tsActionResultpackages/core/src/actions/ActionRunner.ts·packages/types/src/ui-action.tsActionSchemapackages/types/src/crud.ts·packages/types/src/ui-action.tsAggregationConfigpackages/plugin-grid/src/useGroupedData.ts·packages/types/src/data-protocol.tsAppShellPropspackages/app-shell/src/types.ts·packages/layout/src/AppShell.tsxBreadcrumbItempackages/types/src/data-display.ts·packages/types/src/navigation.tsBreadcrumbSchemapackages/types/src/data-display.ts·packages/types/src/navigation.tsCalendarEventpackages/plugin-calendar/src/index.tsx·packages/types/src/complex.tsCalendarSchemapackages/plugin-calendar/src/ObjectCalendar.tsx·packages/types/src/form.tsChatMessagepackages/plugin-chatbot/src/ChatbotEnhanced.tsx·packages/types/src/complex.tsChatToolInvocationpackages/plugin-chatbot/src/ChatbotEnhanced.tsx·packages/types/src/complex.tsComboboxOptionpackages/components/src/custom/combobox.tsx·packages/types/src/form.tsComponentConfigpackages/core/src/registry/Registry.ts·packages/types/src/base.tsComponentMetapackages/core/src/registry/Registry.ts·packages/types/src/base.tsConditionalFormattingRulepackages/plugin-kanban/src/KanbanEnhanced.tsx·packages/plugin-kanban/src/KanbanImpl.tsx·packages/types/src/objectql.tsConfirmDialogStatepackages/app-shell/src/views/ActionConfirmDialog.tsx·packages/plugin-designer/src/hooks/useConfirmDialog.tsConnectionStatepackages/collaboration/src/useRealtimeSubscription.ts·packages/data-objectstack/src/index.tsDataSourcepackages/app-shell/src/types.ts·packages/types/src/data.tsDiagnosticpackages/app-shell/src/views/metadata-admin/previews/simulator/flow-sim-types.ts·packages/cli/src/commands/doctor.ts·packages/sdui-parser/src/types.tsDiagnosticLevelpackages/app-shell/src/views/metadata-admin/previews/simulator/flow-sim-types.ts·packages/cli/src/commands/doctor.tsDomPropspackages/core/src/utils/dom-props.ts·packages/fields/src/widgets/toDomProps.tsFilterBuilderConditionpackages/components/src/custom/filter-builder.tsx·packages/types/src/complex.tsFilterBuilderOperatorpackages/components/src/custom/filter-builder.tsx·packages/types/src/complex.tsFilterGrouppackages/components/src/custom/filter-builder.tsx·packages/types/src/complex.tsFormFieldSpecpackages/app-shell/src/views/metadata-admin/form-spec.ts·packages/react/src/spec-bridge/bridges/form-view.tsFormSectionSpecpackages/app-shell/src/views/metadata-admin/form-spec.ts·packages/react/src/spec-bridge/bridges/form-view.tsFormViewSpecpackages/app-shell/src/views/metadata-admin/form-spec.ts·packages/react/src/spec-bridge/bridges/form-view.tsKanbanCardpackages/plugin-kanban/src/KanbanEnhanced.tsx·packages/plugin-kanban/src/KanbanImpl.tsx·packages/plugin-kanban/src/types.ts·packages/types/src/complex.tsKanbanColumnpackages/plugin-kanban/src/KanbanEnhanced.tsx·packages/plugin-kanban/src/KanbanImpl.tsx·packages/plugin-kanban/src/types.ts·packages/types/src/complex.tsKanbanSchemapackages/plugin-kanban/src/types.ts·packages/types/src/complex.tsMarkdownSchemapackages/plugin-markdown/src/types.ts·packages/types/src/data-display.tsMenuItempackages/types/src/app.ts·packages/types/src/overlay.tsMetadataTypeStatuspackages/app-shell/src/providers/MetadataProvider.tsx·packages/react/src/context/AppShellContext.tsxNamedActionDefpackages/plugin-grid/src/resolveBulkActions.ts·packages/plugin-grid/src/resolveLegacyRowActions.tsOrgTranslatepackages/app-shell/src/console/organizations/orgErrorMessage.ts·packages/app-shell/src/console/organizations/orgRoleLabel.tsPageHeaderComponentPropspackages/app-shell/src/layout/PageHeader.tsx·packages/layout/src/PageHeader.tsxRecordDetailDrawerPropspackages/plugin-dashboard/src/RecordDetailDrawer.tsx·packages/plugin-detail/src/RecordDetailDrawer.tsxSchemaNodepackages/sdui-parser/src/types.ts·packages/types/src/base.tsThemeProviderPropspackages/providers/src/types.ts·packages/react/src/context/ThemeContext.tsxTranslateFnpackages/app-shell/src/providers/saveAdvisoryToast.ts·packages/app-shell/src/providers/writeWarningToast.ts·packages/fields/src/widgets/file-size-guard.tsUndoRedoStatepackages/plugin-designer/src/hooks/useUndoRedo.ts·packages/types/src/ui-action.tsUserDataAdapterpackages/app-shell/src/context/UserStateAdapters.tsx·packages/data-objectstack/src/userState.tsValidationFunctionpackages/types/src/data-protocol.ts·packages/types/src/field-types.tsVersionEntrypackages/collaboration/src/useConflictResolution.ts·packages/plugin-designer/src/components/VersionHistory.tsxViewSwitcherPropspackages/plugin-list/src/ViewSwitcher.tsx·packages/plugin-view/src/ViewSwitcher.tsxViewTypepackages/plugin-list/src/ViewSwitcher.tsx·packages/types/src/views.tsTwo of them collide inside
packages/typesitself —ActionSchema(crud.tsvsui-action.ts) andBreadcrumbItem/BreadcrumbSchema(data-display.tsvsnavigation.ts) — where a consumer importing from the package barrel has no way to say which one it meant except by whichever one the barrel happens to re-export.The remedy, which is the same for every line
Pick the ONE authority, re-point the others at it (
export type { X } from '<the-owner>'is a re-export, not a second declaration, and the gate does not count it). Where the two shapes really are different things, rename one —MenuItem as AppMenuItematpackages/types/src/index.ts:59andValidationFunction as FieldValidationFunctionat:429are this repo's worked examples, and the 2026-08-19 ruling on #5044 is the precedent for choosing which name survives. Then delete the line fromKNOWN_COLLISIONSin the same PR.Batching is the PM's call; the table sorts naturally by owning package.
Reproduce
Refs: #6273 (the gate) · PR #6348 · #6172 · #6155 · #6086 · #5044