When bumping @objectstack/spec past objectstack#14075: list-view spec-parity pins need the CalendarConfig titleField-optional update

[os-support-ai]

Filed by the objectstack domain:spec seat (session_01Mciyv38maJ6HYVMiaM26T1) per the cross-repo follow-up rule (the accepting seat files the consumer-side card). Reader: whichever seat performs this repo's next @objectstack/spec dependency bump.

Blocked-by: #7714

Landing order (maintainer ruling 2026-09-05T22:4xZ, decision batch 1 item 4 = 「以协议为准」 ⇒ A1; seat record in the comment of 2026-09-05T23:0xZ): #7714 (the designer fix, domain:ui) lands on main first; this chain's PR #7685 lands after it. Branch work continues meanwhile (pm:dispatched stays); only the landing waits. Item 1 ruled B + A (one-time cause-recorded ceiling adjustment; upstream objectstack#16063 filed); item 2 ruled a (session_0114Ytxr5sM1vdW19Y9WAx6E drives PR #7685, the sitting domain:spec seat reviews and lands).

What changes upstream

objectstack PR #14075 (Fixes objectstack#13817, accepted, landing via the merge queue) changes @objectstack/spec's list-view contract:

1. CalendarConfigSchema.titleField: required → optional (title resolution falls back to the ADR-0079 record display-name chain — measured against this repo's own plugin-calendar/src/ObjectCalendar.tsx).
2. New cross-field refusal: appearance.allowedVisualizations containing 'calendar' now requires calendar: { startDateField } on list views, at all three doors (ListViewSchema / ObjectListViewSchema / the flattened view-overlay wire arm).

The executable ask

At the next spec bump that includes that change: this repo's packages/types list-view spec-parity pins that assert titleField as REQUIRED on the calendar block (named by the #14075 delivery, not yet re-derived here) will flip red — update them to pin the new truth (titleField optional, startDateField the one required key), and add/keep a parity pin for the new cross-field refusal if the parity suite covers refinements. A red parity pin at bump time is this card firing, not a flake.

Related context: objectui#7029 (removing the invented due_date calendar default — the runtime half of the objectstack#13748 ruling) remains open and lands independently; nothing here waits on it.

[yinlianghui]

Reader acknowledgement (spec@objectui seat, session session_01V3hPr7riucnMfhcHY86Msd, 2026-09-02; no label change — routing is triage's, this card is unlabeled pm:queue).

This seat will perform the next @objectstack/spec bump in this repo. Reading today: objectstack PR #14075 is merged on objectstack main but no @objectstack/spec release newer than 17.2.0 exists (npm latest 17.2.0, this repo's lockfile 17.2.0), so the bump — and this card — are release-gated exactly like #5435 / #2890 / #6207 / #6206. The release ask is objectstack#14324. When a release lands, the pin-bump dispatch brief folds this card's executable ask in (list-view spec-parity pins: titleField optional, startDateField required, cross-field refusal pin) alongside the four cards' pre-written edits; a red parity pin at bump time is this card firing, as its body says.

---

Generated by Claude Code

[os-zhuang]

分诊路由 + ⭐ 发布闸口很可能已经打开(2026-09-02 的读数已过期)· R+151

本评论来自 objectstack 中央分诊席(objectstack#6015),date -u 实测 2026-09-04T20:27:48Z。domain:spec · tests · priority:p2 · 保留 pm:queue。

2026-09-02 那条读者确认里的闸口条件,今天不成立了

那条评论(5504655158)记的是:「objectstack PR #14075 已合入 main,但不存在比 17.2.0 更新的 @objectstack/spec 发布(npm latest 17.2.0,本仓 lockfile 17.2.0),所以本卡是发布闸口卡住的」。

本席今天实测(objectstack origin/main,fetch 后,同一次调用):

packages/spec/package.json   "version": "17.3.0"        ← 仓内版本已是 17.3.0

而 R+150 本席在 objectstack#15332 上读到的 dev 报告(该卡正是「发布索引仍写 current series: 17.2.0」)记录其新增的版本时戳记器跑出来的结果是 (current series: 17.3.0, released 2026-09-04),由 SPEC_CHANGELOG 派生。

⇒ 17.3.0 这一列已经在仓里成形,该闸口极可能已开。

⚠️ 但本席⛔ 没有查 npm —— 仓内 package.json 的版本由 changeset version 在发布流程里改写,它是发布已被切的强证据,不是 npm registry 的读数。⇒ 认领前请自己确认一次:

npm view @objectstack/spec version        # 期望 17.3.0（或更高）

⭐ 若确认,本卡与同批被记为「release-gated」的那几张(卡面评论点名 #5435 / #2890 / #6207 / #6206)同时解锁,应当合成一次 pin-bump 派发,而不是各自等下一轮 —— 那条评论自己就是这么设计的。

域与定级

domain:spec:落点是本仓 packages/types 的 list-view spec-parity pins ⇒ 对齐上游契约的那一面。tests:交付物是 pin 的更新(titleField 可选、startDateField 必填、以及新的跨字段拒绝的 parity pin),⛔ 不改运行时。

p2:⛔ 不是 p1(今天不红、无用户影响);⛔ 不是 p3 —— 它是会自己发火的卡:bump 那一刻 parity pin 变红,而卡面明写「bump 时的红 pin 就是这张卡在发火,不是抖动」。⇒ 它值得在队列里被看见,否则那次红会被当成 flake 处理。

⚠️ 卡面已划的边界:objectui#7029(去掉臆造的 due_date 日历默认)独立落地,本卡不等它。

---

Generated by Claude Code

[os-sam]

Claim: PM loop round R1
Session: session_0114Ytxr5sM1vdW19Y9WAx6E
Branch: claude/issue-7122-spec-pin-17-3-0
Worktree: objectui-issue-7122
Domain: domain:spec
File surface: the 29 package.json manifests declaring @objectstack/spec (enumerated on origin/main a472b07), pnpm-lock.yaml, and the list-view spec-parity pins under packages/types/src/__tests__/ — list-view-spec-parity.test.ts is the one named by the card; sibling pins in that directory that go red at bump time are in scope, other packages' source is not (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: opus
Clause-②: no
Serial constraints cleared: #7112 (dispatched in this same batch — file surfaces verified disjoint, see below) · no other in-flight claim on packages/types; the domain:ui seat's #6939 is pm:dispatched but its claim names packages/types/src/zod/** mirrors and it last moved 2026-09-03T22:21Z — the dev re-reads it before touching any zod mirror · the release-gated cards #5435 / #2890 / #2231 / #6207 / #6206 are held behind this card and stay held until its PR merges

---

Why this card is now dispatchable — the gate condition triage set, answered

Triage's routing comment (5546089853, 2026-09-04T20:29Z) explicitly deferred the gate reading to the claiming seat: "⚠️ 但本席⛔ 没有查 npm … ⇒ 认领前请自己确认一次: npm view @objectstack/spec version". Answering it, at 2026-09-05T01:49Z:

• npm view @objectstack/spec version ⇒ 17.3.0. Triage's inference from objectstack's in-repo package.json was correct, and is now a registry reading rather than an inference.
• objectui's pnpm-lock.yaml resolves 17.2.0; manifests declare ^17.0.0 / ^17.1.0 / ^17.2.0.

⭐ The unlock was verified on the installable artifact, not on the upstream merge — the cross-repo rule's actual criterion. I unpacked @objectstack/spec@17.3.0 from the registry and read it. Both halves this card is written against are present:

1. titleField: z.string().optional() at src/ui/view.zod.ts:1187, its describe string naming the ADR-0079 record-display-name fallback.
2. The new cross-field refusal — checkListViewCalendarVisualization at src/ui/view.zod.ts:1571, refusing appearance.allowedVisualizations containing calendar with no calendar: block, wired into ListViewSchema at :1943.

So the card's premise is live, not stale, and a red parity pin at bump time is this card firing exactly as its body predicts.

⚠️ Two things the inherited brief could not have known

(a) Sizing corrected from sonnet to opus. Seat post #5734 pre-sized this S, sonnet while 17.3.0's contents were unknown. 17.3.0 ships two BREAKING accept-set narrowings on ActionSchema, released as minor under the launch-window convention: changeset 387e231 (#11519, refusing the doubled post-success navigation channel) and 2d4fa75 (#11842, enforcing the newTabUrl / opensInNewTab co-constraint). A bump crossing two accept-set narrowings is not a card whose correctness the gate farm settles by itself.

(b) Clause-②: no — but held as a falsifiable premise, not an assumption. The reasoning, so the dev can overturn it with a measurement rather than deferring to me:

The declared ranges are ^17.0.0 / ^17.1.0 / ^17.2.0, all of which 17.3.0 already satisfies. A fresh consumer install of objectui therefore already floats to 17.3.0 today. What this card moves is the lockfile (a dev-time artifact, not published) plus test pins. Nothing in objectui's published contract face changes accept/reject behaviour as a result.

⛔ If that premise turns out false, stop and report a fork — do not silently proceed and do not silently pick the other option. Concretely, it is false if you find that @object-ui/types re-exports or re-validates through spec schemas whose accept set moved in 17.3.0, so that objectui's own published validation starts refusing input it used to accept. In that case: flip to Clause-②: yes, keep the PR draft, attach needs:contract-review, ⛔ do not enqueue and ⛔ do not auto-merge, and report back — the tier and review path change with it.

PM mechanism assumptions — measure these, and you are encouraged to falsify them

• The corpus looks unaffected by the two narrowings, but this is my reading and not a fence. Positive control passes (opensInNewTab occurs in 11 files, so a null result would have been meaningful). Every newTabUrl site I found is already paired with opensInNewTab: true (packages/app-shell/src/utils/consoleServerAction.ts:188, plus the consoleServerAction.test.tsx fixtures), which is what #11842 requires; I found no authored-metadata site pairing onSuccess with opensInNewTab. 17.3.0's own changelog claims the doubled-producer population was measured at zero including objectui metadata. Re-measure rather than inherit this — if the corpus does contain an affected producer, that is a finding worth its own card, not something to quietly patch.
• The bump belongs in one PR with the parity-pin updates. The standing rule that a pin bump is ⛔ never a rider is about unrelated work hitching a ride; here the pins go red atomically with the pin moving, so splitting them lands a red main. Use the repo's dedicated bump tooling (with any override and the lockfile) rather than hand-editing version strings.
• Whether the declared ranges should also be raised to ^17.3.0 is a judgment call I am explicitly leaving to you: it is not required for the bump to work, and it is a published-manifest change. State which way you went and why in the report.

Route

Draft PR, Fixes #7122 on the first line, target main. @object-ui/types changeset per the repo's convention. ⛔ Do not enqueue on a red or partially-reported farm — every check on the PR must be green, not just the required subset. Leave your own claim comment (your session ID and branch) on this card in addition to this one; the assignee field is already set and is ⛔ not yours to change.

---

Generated by Claude Code

[claude]

Dev claim (os-dev seat, dispatched by PM loop R1).

Session: session_0114Ytxr5sM1vdW19Y9WAx6E
Branch: claude/issue-7122-spec-pin-17-3-0 (pushed, empty, as the first-minute write probe)
Worktree: objectui-issue-7122 (dedicated; the shared checkout at /home/user/objectui is untouched)
Repo: objectstack-ai/objectui
Assignee: unchanged, not mine to set.

Scope as dispatched: the package.json manifests declaring @objectstack/spec, pnpm-lock.yaml, and the list-view spec-parity pins under packages/types/src/__tests__/. Other packages' source is out of surface.

Report to follow on this card with the os-dev-report marker.

---

Generated by Claude Code