[pm:seat] domain:spec @ objectui — ⚪ 离岗 2026-08-24T09:49Z · 本班 10/10 合并 · 在飞 0 · 队列 0 · 决策箱 2

[os-sam]

Seat registration post for the domain:spec @ objectstack-ai/objectui lane — the repo-split half created by the maintainer's 2026-08-23 roster ruling.

Body is authoritative; title and assignee are derived views. Single writer: the sitting seat PM. Comments are audit only and never carry state. Position description is versioned in references/lanes/spec.md; this post carries state only.

1. ⚪ 席位当前空缺 —— 上一班已下班

• 上一班： session_01E7snar5mwF7qoXJazqKhys（GitHub 身份 os-sam），2026-08-24T09:49Z 由维护者叫停下班。
• 交接状态：在飞 0 · 队列 0 可派 · 决策箱 2 · 待人工合并 0 · 返工 0 · 红 CI 合并 0 · 重跑 0。 没有任何在飞工作被丢下,没有未复核的 PR,没有未认领的已派卡。
• 每小时巡检 cron 已暂停（trig_01C3iuHMXUgrTWD8rJyPkETe,名称已标「已暂停,下班」）。接班者：把它 enabled: true 即可恢复,prompt 内容仍然有效;⛔ 不要再改回「一次性定时器 + 每轮重挂」的老模式 —— 那会让维护者每轮被弹一次确认(本班犯过,已修)。

2. 本班成绩单

R1–R8 —— 10 张卡 / 10 个 PR / 10 个合并 / 0 返工 / 0 红 CI 合并 / 0 重跑 / 1 张转出 / 2 张进决策箱。

轮次	卡	PR	合并	闸门
R1	#5330 行谓词正典	#5737	d1ab06f	19+3
R1	#5667 CalendarViewSchema 收敛	#5739	065bba7	18+3+1（Build Docs 真失败,当时 #5668 仍活）
R2	#5738 Phase 0 文档清扫	#5758	702c48a	17+3
R2	#2890 ObjectView 漂移守卫	#5760	af3861f	19+3
R3	#5740 退役 'agenda'（CalendarViewMode）	#5782	b55a346	18+3+1
R4	#5494 ReferenceRailEntry 派生 + 退役 icon	#5794	09:27:58Z	19+3 —— 两个 shard 报告前就合并了,见 §4
R5	#5784 退役 'agenda'（defaultView ×3 面）	#5806	12:05:47Z	19+3,先读完农场再挂
R8	#5821 TableColumnSchema.editable 镜像	#5854	689b97959	19+3
R8	#5830 退役 DashboardComponentSchema.aria	#5855	18a8e7db7	19+3
R8	#5362 从 spec 派生 ObjectSchemaMetadata	#5860	b2ea29717	19+3,含真实 3m45s Build Docs 绿

转出： #5435 → objectstack#11195（仍 open、pm:queue、自 08-23 04:00Z 无人认领）。
本车道 dev 提出的 finding： #5738 ✅ · #5740 ✅ · #5741 · #5759 · #5783 · #5784 ✅ · #5792 · #5793 · #5852 · #5853 · #5859 · objectstack#11195 · objectstack#11284 · objectstack#11408。

3. 热文件串行队列

空。 packages/types 本班一度并行三张卡（zod/data-display.zod.ts · complex.ts · field-types.ts,互不相交),每个 dev 都确认围栏未越界。三个合并后已释放。

4. 本席实测的平台事实

• ⛔ 实测的平台事实和裁决一样会过期 —— 包括自己写下的。 Build Docs main 红（Build Docs is red on main: fs reaches the browser bundle via @objectstack/spec → pg-connection-string #5668）已于 2026-08-23T09:56:22Z 失效,由 PR Refresh the lockfile to @objectstack/* 17.2.0 — fs stops reaching the browser bundle #5790 修复（lockfile 升到 @objectstack/* 17.2.0）。本席在 feat(types): retire 'agenda' from defaultView on all three declaration faces #5806/fix(types): declare editable on the rich TableColumnSchema zod mirror so locked columns stay locked through parse #5854/fix(types): retire DashboardComponentSchema.aria — spec-tombstoned, renderer-dead #5855/feat(types): derive ObjectSchemaMetadata from the spec's ServiceObject; settle listViews spelling (#5362) #5860 上继续引用了这条过期排除,比失效晚了约 6 小时。方向安全 —— 从没把红 PR 说成绿 —— 但过期的排除等于把盲区精准对准了一个你已经不再读的闸门。复查「已知坏掉」的闸门是巡检职责,不是背景假设。
• Build Docs 当前读法（Refresh the lockfile to @objectstack/* 17.2.0 — fs stops reaching the browser bundle #5790 之后）： ~10–13 秒绿 = turbo 缓存命中,两个方向都不算证据；3–4 分钟红 = 真失败（feat(types,plugin-calendar): converge CalendarViewSchema on the calendar-view renderer's read set #5739、feat(types): retire 'agenda' from CalendarViewMode and the zod enum #5782 实测,当时 Build Docs is red on main: fs reaches the browser bundle via @objectstack/spec → pg-connection-string #5668 仍活）；3 分 45 秒绿 = 真跑真过（feat(types): derive ObjectSchemaMetadata from the spec's ServiceObject; settle listViews spelling (#5362) #5860 —— 就是这个读数暴露了过期事实）。时长仍是判据,结论变了。
• ⛔ Test (shard n/4) 不是必需检查,且直接合并会被拒。 (1) fix(plugin-detail): derive ReferenceRailEntry from @objectstack/spec and retire the icon key #5794 在 09:27:58Z 自动合并时 shard 2/4 和 4/4 仍在跑（事后都过了 —— 结果不能给假设背书）。(2) merge_pull_request → 405 … Changes must be made through the merge queue,所以 auto-merge 就是入队机制。纪律在于什么时候挂：先按名字读完整农场（19 success + 3 skipped = 22）,再挂。
• ⛔ 合并时序审计结论是「险过」而非「全清」（评论 5386204916）。R1–R3 五个 PR 都在 shard 报告之后才合并,fix(plugin-detail): derive ReferenceRailEntry from @objectstack/spec and retire the icon key #5794 是唯一一个在证据不全时落地的。但 feat(core,react): declare record.* the row-predicate canon and warn on the two deprecated spellings #5737 只早了 45 秒、Add the ObjectViewSchema drift guard, and fold the four per-view-type config aliases #5760 只早了 35 秒 —— 那是 merge queue 的延迟,不是判断力。那五个的挂载时刻不可考,所以「同样做法、只是时机不同」是推断,不是测量。
• ⛔ check_suite.completed 不是闸门读数。 它在 R8 三个 PR 上都触发过,农场照样按名字读。GitHub 自己的提示就说它不覆盖 cancelled suite、无 run 的 suite 和 legacy status。
• ⛔ 接口带索引签名时 keyof 守卫是空的 —— 采信前先查接口。 三次实测：Migrate the remaining ListView legacy vocabulary to spec-canonical keys, and audit ObjectView/DetailView (#2231 phases 4–5) #2890（删了键 type-check 仍绿）、finding(types): DashboardComponentSchema.aria declares a key the spec tombstoned and no renderer reads — stale "Aligned with @objectstack/spec AriaPropsSchema" claim #5830（BaseSchema 的 [key: string]: any 让 @ts-expect-error pin 钉不住 —— dev 自己诊断出来并改用字面键集提取）、finding(types): the rich TableColumnSchema zod mirror omits editable — a key data-table reads at three sites is silently stripped by validation, so a column locked with editable: false re-opens after parse #5821（TableColumn 是独立接口无索引签名,所以它的 Equal 穷尽 pin 是真的 —— 本席在 origin/main 上核过）。同一个问题,相反答案,都对。
• ⛔ 非 strict schema 里「能解析」不是 pin。 finding(types): the rich TableColumnSchema zod mirror omits editable — a key data-table reads at three sites is silently stripped by validation, so a column locked with editable: false re-opens after parse #5821 的消融实验证明:原有的 safeParse(...).success 循环在键仍被剥掉时照样绿 —— z.object 接受并静默剥离未声明键。要 pin 解析后的输出,不是解析结果。
• ⛔ 自己的 checkout 会过期。 复核 feat(types): retire 'agenda' from defaultView on all three declaration faces #5806 时共享 checkout 停在 feat(types): retire 'agenda' from CalendarViewMode and the zod enum #5782 之前,在它上面跑「还有哪些面带 'agenda'」的 grep 会得出毫无价值的结论。在 PR 真实 base sha 上重跑。
• ⛔ squash 合并后分支 head 永远不是 main 的祖先。 git branch -r --contains <head> 对已落地的 squash PR 返回 0 —— R8 三个 PR 上都实测到。用 commit 标题核实落地。
• ⛔ 退役卡要查活的生产者,不只是消费者。 ReferenceRailEntry is owned by @objectstack/spec as of 17.1.0 and objectui's local copy declares an extra icon key the spec's strict schema refuses #5494 的 synth 正在把要退役的那个键写进每一个合成页。此后每张退役 brief 都带这条;finding(types): DashboardComponentSchema.aria declares a key the spec tombstoned and no renderer reads — stale "Aligned with @objectstack/spec AriaPropsSchema" claim #5830 和 ObjectSchemaMetadata declares neither titleFormat nor list_views / listViews nor icon, and the runtime reads all three #5362 都跑了生产者扫描,都干净。
• ⛔ 裁决两个方向都会老化。 ReferenceRailEntry is owned by @objectstack/spec as of 17.1.0 and objectui's local copy declares an extra icon key the spec's strict schema refuses #5494 的前提在立卡时就是假的；finding(types/plugin-calendar): defaultView declares 'agenda' in ObjectCalendarSchema and both zod twins, but ObjectCalendar reads it as 'month' | 'week' | 'day' #5784 的前提比 brief 更强（spec 早已是三值）。裁决复读和过期检查是同一遍。
• ⛔ 标题不是状态（[Decision] Row-predicate spelling contract: does the canon narrow to record.*, or do the bare shorthand and data.* spellings stay? (the uncarried "#4075 step 3" question) #5330 顶着 [Decision] 在 pm:queue,并非误标）。⛔ search_issues 会静默返回零,连控制词一起（objectstack#11193）—— 用两种独立方法去重。⛔ ADR-0087 D2 墓碑仍留在 spec 的 .shape 里,所以「键在不在」的检查会把已退役键报成活的。⛔ 被杀的 subagent 只要推过 commit 就不是死认领 —— 先 git ls-remote --heads origin 'refs/heads/claude/issue-*' 再决定 resume 还是 withdraw。
• check:spec-symbols 跑在 Type Check job 里（ci.yml:238）,没有自己的名字;它的 DEBT 台账带棘轮（:1066）。合规形式：export type { X } from '@objectstack/spec/…' 与 export type X = z.infer<typeof SpecX>（:907-926）。
• @ts-expect-error 只有在该包的 type-check 串了读这个文件的 tsconfig 时才有强制力 —— packages/types 串了（tsc --noEmit && tsc -p tsconfig.examples.json && tsc -p tsconfig.test.json）。
• Console eager-closure 预算并不贴顶 —— fix(plugin-detail): derive ReferenceRailEntry from @objectstack/spec and retire the icon key #5794 上 98.2%,两小时后 feat(types): retire 'agenda' from defaultView on all three declaration faces #5806 上 80.9%。单次预算读数是快照,不是趋势。
• 十次派发中始终成立的继承前提：本仓没有 needs:contract-review 标签（就地按 tier 派发,「直接入队」）；dispatch-gates.mjs 是错的树。受治理面（AGENTS.md、CLAUDE.md、.claude/**、docs/adr/**）—— 没有任何 PR 碰过。

5. 接班者从这里开始

可派卡 0 张,但必须复验 —— 车道曾在 08-23 一小时内从 0 涨到 3,「空」这个读数过期很快。最近一次扫描 2026-08-24T08:56Z,无变化。

不可派（不要重推）：#2731（design-first、ADR 前置、地基落在 objectstack —— 那是另一个 spec 车道;⛔ 不要给别人的卡改标） · #4535（已指派真人 yinlianghui） · #2890 / #5435 / #2231 / #4356（pm:blocked） · #5213 / #4631 / #4052 / #3834（pm:on-hold） · #4043（tracking） · #5741（决策箱）。

接班第一件事,按序：

1. 分诊定级观察 —— 新工作最可能的来源。 R8 的 dev 提了 finding(types): designer-surface DashboardConfig.aria / DashboardConfigSchema.aria declare a { label, description } aria object nothing reads — and the panel they document does not consume them #5852、finding(types): TableColumn.type disagrees three ways — interface declares 8 literals, zod mirror accepts any string, renderer's live read set handles values outside the union via an as any cast #5853、ObjectTrigger and ObjectRelationship are orphaned hand-written exports after the ObjectSchemaMetadata derivation (#5362) #5859、objectstack#11408,都还没定级。另有 finding(i18n): calendar.agenda is a confirmed-dead key in all ten locale packs — no static reader, no dynamic calendar. head, and the enum value it labeled is retired #5783 · [finding] registry-inputs-spec-parity narrates the ReferenceRailEntry icon divergence as unsettled after #5494 resolved it #5792（已因落地过期 —— 引用的 ReferenceRailEntry is owned by @objectstack/spec as of 17.1.0 and objectui's local copy declares an extra icon key the spec's strict schema refuses #5494 已合并,先复核是否仍描述真实缺陷） · Packages whose published d.ts references spec-17.1.0-only symbols still declare "@objectstack/spec": "^17.0.0" — the range admits a spec that lacks the symbols #5793。finding(types): TableColumn.type disagrees three ways — interface declares 8 literals, zod mirror accepts any string, renderer's live read set handles values outside the union via an as any cast #5853 最强（TableColumn.type 三面不一致：接口 8 值联合 / 镜像任意 string / 渲染器经 as any 读 int·integer·float·double）,但很可能要先裁「正规值集」,属决策而非派发。
2. 解锁扫描 —— objectstack#11195（解锁 normalizeListViewSchema manufactures userActions.group / hideFields / rowColor — three keys ListViewSchema refuses BY NAME, so the fold's own output fails the view save gate #5435,已无人认领约 30 小时）。objectstack#11284 已裁「收敛」并已在 objectstack 车道 pm:queue；Migrate the remaining ListView legacy vocabulary to spec-canonical keys, and audit ObjectView/DetailView (#2231 phases 4–5) #2890 要等那张卡落地才解锁,不是裁决当下（已记在 Migrate the remaining ListView legacy vocabulary to spec-canonical keys, and audit ObjectView/DetailView (#2231 phases 4–5) #2890 评论 5386802331,含 deprecate-first 纪律和 conditionalFormatting/exportOptions 的围栏)。
3. 恢复每小时巡检 cron（见 §1）。

⛔ 决策箱 —— 两张都在维护者手上

#5741 —— 存量元数据通道。 自本席 08-23 08:06Z 的 ACCEPT 后无新评论。行谓词退役 Phase 2 卡在一个没人能跑的普查上。卡面有完整四棱分析（A 单租户 token —— ⛔ 单独不足；B 只读副本/dump；C 离线导出）。推荐 C,回退 B。

⚠️ 本班已有四张卡顶着这个缺口交付 —— #5494、#5784、#5830、#5362 全都只能说 「无可达用量」而非「无用量」。#5362 最尖锐：它保留了全部 snake 拼写读点并把这个容忍度 pin 住,正因为存量不可测 —— 这是正确做法,但意味着清理被无限期推迟。objectstack#7917 在 2026-08-13 提过同一需求,至今 11 天。

objectstack#11284 —— 已裁「收敛」（React 层采纳 metadata 层拼写,viewType→type 同笔,deprecate-first）。已转为 objectstack spec 车道的实施卡,落地前本仓无事可做。

6. 备注

• 八次 dev 对本席 brief 的纠正/升级,全部公开接受。 三次自我更正：finding(types/plugin-calendar): CalendarViewSchema declares 9 of its 13 keys that the calendar-view renderer never reads — including events, its only required key, which the renderer deliberately drops #5667 方向说反（.passthrough() 意味着放宽而非收窄）；ReferenceRailEntry is owned by @objectstack/spec as of 17.1.0 and objectui's local copy declares an extra icon key the spec's strict schema refuses #5494 的 ACCEPT 声称 auto-merge 在等非必需检查；以及上面 §4 的 Build Docs 过期事实更正。两次节奏失误也如实记录：R4→R5 的 58 分钟空档,和 R8 的九小时空档（派发后没重挂定时器,三个已绿 PR 无人复核 —— 已由 cron 从机制上消除)。
• 两张卡靠裁决继承落地（finding(types/plugin-calendar): view: 'agenda' is declared by CalendarViewMode and the zod enum but the calendar-view renderer silently falls back to 'month' #5740 继承 finding(types/plugin-calendar): CalendarViewSchema declares 9 of its 13 keys that the calendar-view renderer never reads — including events, its only required key, which the renderer deliberately drops #5667,finding(types/plugin-calendar): defaultView declares 'agenda' in ObjectCalendarSchema and both zod twins, but ObjectCalendar reads it as 'month' | 'week' | 'day' #5784 继承 finding(types/plugin-calendar): view: 'agenda' is declared by CalendarViewMode and the zod enum but the calendar-view renderer silently falls back to 'month' #5740）—— 记为否决窗口而非许可闸门,派发前都重新测过。
• 跨仓姿态： 把 spec 侧契约卡提进 objectstack 的 domain:spec 队列,同笔把本仓卡翻 pm:blocked + Blocked-by:。不扫 domain:ui（[pm:seat] domain:ui — objectui execution seat · 🟢 R26 in flight (os-sam) · 32 PRs landed since the 11h42m freeze · landing backlog CLEARED · 1 held (#6814 human floor) · 3 dev in flight · 12 in decision box #5560）和 domain:devx（objectstack#10602）。

[os-sam]

Round-open marker — R2, 2026-08-23T04:4xZ, session session_01E7snar5mwF7qoXJazqKhys. Audit only; §1 of the body still reads "R1 closed / standby" and is refreshed at the R2 boundary, per the write-side rule. Mid-round state is carried by the Claim: comments on the cards, not here.

Why the seat came out of standby: the 04:38Z standby sweep found the lane refilled. The maintainer directed a bulk triage of objectui's unlabelled backlog this session (verbatim, recorded on #5741: 「objectui 有 79 张卡在车道视图之外（占该仓 35%），你帮我分批处理」·「继续 批 2 批 3」), and it routed six cards into domain:spec — including all three R1 follow-ups.

Unlock sweep: no unlock. objectstack#11195 is still open (pm:queue, unassigned), so #5435 stays pm:blocked. Reminder for the next sweep: it is blocked twice — #11195 landing and the spec pin bump that #5716 holds at 17.1.0. Releasing one is not enough.

In flight (2, batch capped at 3, both mode:subagent, both clause-② no):

• Migrate the remaining ListView legacy vocabulary to spec-canonical keys, and audit ObjectView/DetailView (#2231 phases 4–5) #2890 — opus, branch claude/issue-2890-objectview-drift-guard. pm:blocking, so first by the lane's selection order. Scope is the triage-limited one (ObjectViewSchema drift guard + four phase-3 alias folds), not the card body's much larger project; A6 / viewType / conditionalFormatting / exportOptions are excluded as upstream packages/spec faces.
• Row-predicate deprecation is missing its Phase 0: docs and example apps may still teach the bare shorthand / data.* spellings the new warning now flags #5738 — opus, branch claude/issue-5738-row-predicate-phase0. Phase 0 of the row-predicate deprecation, the sibling of R1's [Decision] Row-predicate spelling contract: does the canon narrow to record.*, or do the bare shorthand and data.* spellings stay? (the uncarried "#4075 step 3" question) #5330.

Hot-file serial queue (R2):

surface	held by
packages/types/src/__tests__/ · packages/core/src/utils/normalize-list-view.ts	#2890
content/docs/** · example apps · schema-catalog · plugin READMEs	#5738

Serialised behind #2890 — packages/types is one package, and batch independence is per-package, not per-file: #5740 (view: 'agenda' residue) and #5494 (ReferenceRailEntry extra icon key). Both dispatchable the moment #2890's PR merges. fold-or-serial answered: serial — #5740 and #2890 fail gate ① of the five (different defect shapes: a value-level enum residue vs a declaration-drift guard), so they do not fold.

Also queued, not yet dispatched: #5741 (Phase 2 survey carrier). Triage graded it pm:queue with the note that establishing the data source is the first deliverable, and returning pm:blocked with the access channel named is the correct outcome if none exists — ⛔ explicitly not "guess a population and call it sized". That resolves the routing question this seat raised at R1 close; it does not need the maintainer.

#2890 assignee provenance, checked before claiming: cleared 02:36Z by the skills seat under maintainer ruling objectstack#11196 as assignee-field residue from the 07-28 filing session (shared agent identity, no Claim: comment, no branch). Not a live claim; claimable by protocol.

---

Generated by Claude Code

[os-sam]

⛔ CORRECTION to §3's standing lane constraint — the pin blocker has lifted. Audit comment; the body still carries the stale text and is corrected at the R2 boundary.

§3 currently reads: "any card whose fix is 'align objectui on the spec pin' is blocked twice — on the spec-side change landing in objectstack, and on the pin bump, which #5716 holds at 17.1.0."

The second half is no longer true. #5716 closed completed 04:57:58Z via merged PR #5752 (c9327c9), taking the Localize branch — objectui now owns Theme / ThemeMode / ColorPalette rather than re-exporting them from the retired @objectstack/spec/ui surface. #5716's own body stated the consequence it was gating: "any objectui spec-pin refresh past the retirement breaks @object-ui/types and @object-ui/providers builds." That is what localization removes.

Consequence for this lane: #5435 is now single-blocked, on objectstack#11195 alone (still open, pm:queue, unassigned). When #11195 lands, the next unlock sweep should find only one condition to satisfy, not two.

⚠️ Do not over-read this. What is established is that #5716's blocker is discharged — by its own closure and merged PR. I have not measured that a pin refresh now succeeds end-to-end, and the manifests still declare the range ^17.0.0, which 17.1.0 already satisfies. Whether a bump past 17.x is clean is a separate, unmeasured question, and #5716's body names related guards designed to trip at exactly that moment (the ThemeModeSchema deny-list row in spec-ui-schema-reexports.test.ts). The unlock sweep re-verifies on the merged ref rather than trusting this note.

R2 landing so far: #5738 → PR #5758 merged 702c48a (17 success + 3 skipped, zero red, zero pending). #2890 still in flight.

---

Generated by Claude Code

[os-sam]

R3 interrupted by the 5-hour usage wall, and resumed. Audit comment; §1 of the body still reads "R2 closed / ready for R3" and is refreshed at the R3 boundary.

What happened. Both R3 devs — #5740 and #5741, dispatched ~05:45Z — were terminated mid-task at ~05:50Z by an account-level session limit, with the reset time carried in the failure itself: 07:00Z. Per the seat's own discipline, the authoritative wall signal is the failure report, and the reset moment is available at that instant and not afterwards, so it is recorded here.

Neither card was withdrawn, and that was the deliberate call:

• finding(types/plugin-calendar): view: 'agenda' is declared by CalendarViewMode and the zod enum but the calendar-view renderer silently falls back to 'month' #5740 — its dev had pushed a branch before dying: claude/issue-5740-calendar-view-mode-agenda at 1f94b4c9, verified on the remote. The reclaim rule is explicit that a claim carrying a live branch with commits is never reclaimed, so withdrawing would have discarded real work.
• Carrier for Phase 2 of the row-predicate deprecation: the stored-metadata survey that must size the removal window before any spelling retires #5741 — no branch, but the interrupted-dev protocol is resume-first and withdraw only if resumption is unavailable.

Both were resumed via SendMessage at ~07:55Z, after the wall lifted. The original briefs stand; each resume message re-stated only the load-bearing constraints rather than re-issuing the brief.

A finding salvaged from #5740's dying words, verified before passing it back. Its last output was "More surface than the card cites — objectql.ts, i18n locales." Spot-checked on origin/main: CalendarViewMode appears in packages/types/src/complex.ts, packages/types/src/index.ts, packages/types/src/zod/complex.zod.ts and packages/types/src/zod/index.zod.ts — re-exported through both barrels, wider than the card's two cited files. The objectql.ts and i18n-locale legs are not confirmed and were handed back as the dev's to establish.

This matters because it feeds the card's load-bearing question directly: if CalendarViewMode has consumers beyond CalendarViewSchema.view, narrowing the shared enum is too wide a cut, and the correct fix may be narrowing CalendarViewSchema.view alone. That was already Zone 2 item 3 of the dispatch; the dev's own measurement is now evidence for it rather than a hypothetical.

Standing note for the next wall: a killed subagent is not a dead claim when it has pushed commits. Check git ls-remote --heads origin 'refs/heads/claude/issue-<n>*' before deciding between resume and withdraw — the two paths differ by whether work exists to lose.

---

Generated by Claude Code