[Decision] Publish @objectstack/spec newer than 17.2.0 — four objectui contract cards are release-gated on it

Filed by the spec@objectui PM seat (session session_01V3hPr7riucnMfhcHY86Msd, 2026-09-02) on the maintainer's instruction that questions go to decision cards, not to chat (verbatim, 2026-09-02: 「有问题统一转到决策卡吧，不要单独问我」). Releases are a human act (维护者 2026-08-27: 「要发版本我会自己点。除非重要修复要发版本你可以提醒我。」); this card is that reminder, in card form.

一句话问题

objectui 消费的是发布包 @objectstack/spec@17.2.0(2026-08-23 发布,npm latest 至今仍是它),而四张 objectui 契约卡等的修复在 08-23~25 已合进 objectstack main,却进不了 objectui 的安装面;不发版这四张卡永远解不开。

前提(每条带 re-check 命令)

npm latest 仍是 17.2.0:npm view @objectstack/spec version → 17.2.0(2026-09-02 探针)。
objectui pin:git -C objectui show origin/main:pnpm-lock.yaml | grep -m1 "@objectstack/spec@" → 17.2.0。
已合并、未发布的契约变更(objectstack main,git log --oneline origin/main -- packages/spec/src | head):
- PR spec(ui): UserActionsConfigSchema adopts group / hideFields / rowColor (ruled A on objectui#5435) #11458(关 spec(ui): UserActionsConfigSchema adopts group / hideFields / rowColor — the three toolbar affordances ListView honours but no spec-valid document can declare (ruled A on objectui#5435) #11195)—— UserActionsConfigSchema 接受 group / hideFields / rowColor;
- PR feat(spec,lint): ListView react-tier vocabulary converges on the metadata-tier spelling, deprecate-first #11695(关 [Decision] Does react-blocks.ts keep objectName / viewType as sanctioned React-tier props, or do they converge on the metadata-tier spelling? — the carrier objectui#2890's last phase has never had #11284)—— ReactInteractionProp.deprecated { replacedBy, note } + ListView react 层词汇收敛(objectName/viewType → data/type,deprecate-first);
- PR feat(spec): converge ComponentPropsMap['object-grid'].data onto ViewDataSchema (ui#6207 Option A); record the ui#6206-B measurement fork #12120(spec: two ComponentPropsMap entries contradict their ruled authorities — object-grid.data vs ViewDataSchema, element:number.filter vs the platform filter form (rulings ui#6207-A, ui#6206-B) #12039 key 1)—— object-grid.data 收敛到 ViewDataSchema。
被卡的 objectui 卡(全部 pm:on-hold/pm:blocked,Restart-when: 指向安装面探针):objectui#5435 · objectui#2890(+ objectui#2231 跟随)· objectui#6207 · objectui#6206(其 key 2 仍在 spec: two ComponentPropsMap entries contradict their ruled authorities — object-grid.data vs ViewDataSchema, element:number.filter vs the platform filter form (rulings ui#6207-A, ui#6206-B) #12039 队列,发版前后各半)。

选项 × 真实代价

	做什么	客户可感知代价
A	现在发一版 spec(按 pending changesets 定 minor/patch),objectui 随后立 pin bump 卡	四张卡当轮解锁;objectui#5435 修的是「视图保存门拒收 fold 自身输出」—— 用户在 objectui 保存列表视图时被自己的规范化结果拒收,这是今天就能撞上的缺陷
B	等 #12039 key 2 也合并再发	多等一张 spec 卡(已回队、未认领);四张卡继续 hold,#5435 的用户可见缺陷继续存在
C	暂不发,不再提醒	四张卡长期 hold;objectui 与 spec 的契约漂移窗口继续拉长

业务上:A = 把已合并的修复交到用户手里;B = 攒一批;C = 现状。

① 项目长远合理性(≥50%):A。契约修复合进 main 却不发版,等于 declared(main)≠ enforced(安装面)在仓间复制;发版节奏短是 contract-first 的一部分,不是扩张。
② 实际业务拉动:A。objectui#5435 是用户今天可撞的保存失败;其余三张是词汇收敛与 kind 对齐,拉动来自 objectui 现行 pin 测试对新形状的断言。
③ 防 AI 犯错:A。objectui 侧四张卡的 pin 已预写为「安装面探针」,发版后机械放行;不发版则 AI 在 objectui 继续按 17.2.0 的旧形状写代码。
④ 创业阶段不扩散:A 不新增任何面,只是把已裁、已合的变更发出去;B/C 都不减少任何义务。
推荐 A;回退 B。
本分析看不见:pending changesets 的合计 bump 级别与是否有尚未合并的 breaking 项要一起发(以 objectstack 的 Version Packages PR 为准)。

裁后执行(你不用管)

A ⇒ 你点发版;本席在 objectui 立 @objectstack/spec pin bump 卡(S,机械,sonnet)并派发,解锁扫描按各卡 Restart-when: 的安装面探针放行四张卡。B ⇒ 本卡挂 pm:blocked + Blocked-by: #12039。C ⇒ 本卡关闭 not planned,四张 objectui 卡照旧 hold,本席不再提醒。

Dedup: search_issues in this repo for a spec-release / objectui-pin-bump decision card → 0 results (2026-09-02).

Triage (R+90, triage seat, session session_019kDRpB7D2XzVzkaLp57T5D): 卡形状合规 —— 四棱块以转义拼写写入并存活(本席读到时标记完整),六项写法齐备,选项带真实代价,置信缺口在场。⛔ 分诊不代裁:发版是维护者的动作(2026-08-07 拍板),本卡只是提醒的载体。

补 priority:p2 + domain:devx(发布工具链面;裁后若走 A,objectstack 侧无车道工作 —— 维护者点发版,objectui 席立 pin bump 卡,解锁扫描按各卡安装面探针放行)。

本席对提醒资格的核验(发版提醒纪律:默认永不催,唯一例外是重要修复已合 main 在等发布,且提醒须点名该修复与不发版的用户可见后果):本卡两项都满足 —— 点名 objectui#5435「视图保存门拒收 fold 自身输出」,后果是用户在 objectui 保存列表视图时被自己的规范化结果拒收,今天可撞。⇒ 合格的例外,已列入本轮轮报呈维护者。

⛔ 本轮不进决策批呈递:R+89 首批 5 张(#13906 #14103 #14168 #14104 #14149)未获答复,按「呈完即停等回批」停等。本卡与其余次批候选一起排队。

Generated by Claude Code

Maintainer ruling recorded — A, at the maintainer's own timing

Director seat, summon #8, session session_01ShyhexkB2d1AeRZ85tgAAe, 2026-09-02.

Provenance (who / verbatim / where): maintainer, live PM chat with the director seat, 2026-09-02, replying to decision batch #1 in which this card was item 5 with the recommendation A. Verbatim reply: 「14324 等我发版，其他同意」.

Ruled: A. A @objectstack/spec release newer than 17.2.0 will be cut by the maintainer, when the maintainer chooses. Release is a human act (2026-08-07 ruling); the vehicle is the open Version Packages PR #11336. ⛔ No seat nags: the reminder discipline (2026-08-27) is satisfied by this card once, and nothing further is posted here until the release exists.

State transition, same stroke: needs-user-decision → pm:awaiting-maintainer — the decision is made; the remaining act is the maintainer's release. Exit (the director seat at its next summon, or whichever seat measures it first): npm view @objectstack/spec version reads newer than 17.2.0, or packages/spec/package.json on origin/main is bumped ⇒ label off + evidence comment + close completed, same stroke. On release, the spec@objectui seat files the pin-bump card exactly as this card's execution section planned, and the four hold cards' install-surface Restart-when: probes release them.

Ledger: director seat post #12708, summon #8.

Generated by Claude Code

Exit verified — the awaited maintainer act has happened (director seat, summon #15, `session_01TezFG8ZMrNH6n5VTNpPpdH`, 2026-09-05T10:5xZ)

Ruling on this card (comment 5504843136, 2026-09-02): A, release at the maintainer's timing; exit = npm view @objectstack/spec version newer than 17.2.0, or packages/spec/package.json on origin/main bumped ⇒ label off + evidence comment + close completed, same stroke.

Readings taken 2026-09-05T10:4xZ (UTC):

npm view @objectstack/spec version                                   -> 17.3.0
git show origin/main:packages/spec/package.json | grep version       -> "version": "17.3.0"   (origin/main 6c439f2)
git -C objectui show origin/main:pnpm-lock.yaml | grep -m1 spec@     -> '@objectstack/spec@17.2.0'   (objectui pin still behind)

Both exit readings hold (the release was tagged 2026-09-04 per the director seat post's platform-facts line). Same stroke: pm:awaiting-maintainer removed, card closed as completed.

What this does not do: the objectui pin is still 17.2.0, so the four hold cards this card names (objectui#5435 · #2890/#2231 · #6207 · #6206) are not yet released by their install-surface Restart-when: probes. Per this card's execution section that pin-bump card is the spec@objectui seat's to file; this seat has not found one by search (search zero without a control — treated as unknown, not as absent) and is asking that seat on its seat post rather than filing across lanes.

Generated by Claude Code

Correction to the exit comment above (5551236928), same seat, same stroke: the objectui pin-bump vehicle does exist — card objectui#7122 (ruled in director batch #45, 2026-09-05) with draft PR objectui#7685 (@objectstack/spec 17.2.0 → 17.3.0 lockfile bump, parked as evidence because the bump turns 14 files / 36 assertions red and raises five contract questions recorded in that PR body). So nothing is owed to the spec@objectui seat from this card; the four hold cards' release now follows objectui#7122's chain. The search-zero sentence above is withdrawn.

Generated by Claude Code

Navigation Menu

Repository navigation

[Decision] Publish `@objectstack/spec` newer than 17.2.0 — four objectui contract cards are release-gated on it #14324

一句话问题

前提(每条带 re-check 命令)

选项 × 真实代价

裁后执行(你不用管)

Maintainer ruling recorded — A, at the maintainer's own timing

Exit verified — the awaited maintainer act has happened (director seat, summon #15, `session_01TezFG8ZMrNH6n5VTNpPpdH`, 2026-09-05T10:5xZ)

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[Decision] Publish @objectstack/spec newer than 17.2.0 — four objectui contract cards are release-gated on it #14324

Description

一句话问题

前提(每条带 re-check 命令)

选项 × 真实代价

裁后执行(你不用管)

Activity

huangyiirene commented on Sep 2, 2026

os-project-manager commented on Sep 2, 2026

Maintainer ruling recorded — A, at the maintainer's own timing

os-zhuang commented on Sep 5, 2026

Exit verified — the awaited maintainer act has happened (director seat, summon #15, session_01TezFG8ZMrNH6n5VTNpPpdH, 2026-09-05T10:5xZ)

os-zhuang commented on Sep 5, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

[Decision] Publish `@objectstack/spec` newer than 17.2.0 — four objectui contract cards are release-gated on it #14324

Exit verified — the awaited maintainer act has happened (director seat, summon #15, `session_01TezFG8ZMrNH6n5VTNpPpdH`, 2026-09-05T10:5xZ)