[objectstack-fleet]

Requested by Leehom · project thread

Fixes #31426

Clause-②: no
Metadata-protocol: none

维护者速读

• 改了什么：通知偏好的「免打扰」字段 quiet_hours 加上 widget: 'quiet-hours'，控制台改用时区加两个时间的控件，不再显示 JSON 编辑框；存储格式不变。
• 为什么改：Setup notification preferences: draw quiet hours (免打扰) as a time-range control instead of a JSON box (#30208 row 6 step 3) #31421 的前端控件（PR feat(fields): draw a notification preference's quiet hours as a time-zone picker and two times #31459，已合并）只认字段上的 widget 提示，和同一对象的 topic、channel 一样，这是它的服务端一半。
• 风险与回滚：只是一个界面提示，不改字段类型、不新增拒绝；未注册该控件的宿主照旧显示 JSON 编辑框。回滚即还原本 PR。
• 先看：packages/services/service-messaging/src/objects/notification-preference.object.ts 的 quiet_hours。
• 两分钟验证：cd packages/services/service-messaging && npx vitest run src/objects/notification-preference-topic-channel-help.test.ts，预期 5 个全绿。
• 需要你做的：无，席位落地。

What changes

• sys_notification_preference.quiet_hours declares widget: 'quiet-hours', with a [#30208 row 6, #31426] comment like the ones on topic and channel. The field stays json; the stored shape { tz?, start: 'HH:MM', end: 'HH:MM' } and every refusal are unchanged. The ui half registers field:quiet-hours (PR feat(fields): draw a notification preference's quiet hours as a time-zone picker and two times #31459, merged).
• content/docs/data-modeling/field-types.mdx gains a short section on the three notification preference widgets (notification-topic, notification-channel, quiet-hours): which field each sits on, what it draws, what it stores, and that an unregistered name falls back to the type's default input. Per the ui seat's note on the card, the topic and channel hints were undocumented until now.
• Changeset: @objectstack/service-messaging patch.

Tests

• notification-preference-topic-channel-help.test.ts (the file that pins the topic / channel hints) adds: quiet_hours declares widget: 'quiet-hours' and stays json.

Verification

Pin and ablation

npx vitest run src/objects/notification-preference-topic-channel-help.test.ts   Tests 5 passed (5)

scripts/ablation-replace.mjs --delete the widget line (landed; restored to the HEAD blob):
 × quiet_hours declares the quiet-hours widget and stays a json field (#31426)
 AssertionError: expected undefined to be 'quiet-hours'
 Tests  1 failed | 4 passed (5)

Gates

node scripts/pm/dispatch-gates.mjs --commands derives 94 families; all 94 run with each exit code captured before any pipe, all exit 0, and --ran reconciles: 94 derived famil(ies) accounted for — 94 run, 0 NOT-MEASURED. After a typing fix in the new pin (a required read the field shape does not type), pnpm --filter @objectstack/service-messaging typecheck exits 0, pnpm check:query-options-erasure exits 0, the pin and its ablation were rerun as above, and pnpm lint over the two touched .ts files exits 0.

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

1 anchor(s) derived from 1 changed package(s); no hand-written page names any of them, so this run has nothing to list — not a clean bill of health. This check sees only pages that NAME a derived anchor: one that documents this change in prose, or enumerates it in an authoring dialect, names none and stays invisible to it on every run.

What this run could not see

• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 6 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json a3ac7fb3808e2c17a369cab00f175ccb03e5e5f7 → packageMentionDocs.

Which tree this was computed on

This run read content/docs from eaef1dce44dc1d16ec17a97177bf7e46a9814cc1 — the merge of head 1863f9895b1b0e4552a0cd82acc2079bb813ac03 into base a3ac7fb3808e2c17a369cab00f175ccb03e5e5f7, which is what actions/checkout gives a pull_request run. Not the PR head.

A worktree cut from an older main holds a different content/docs, so re-deriving there can legitimately return a different list — that is a different tree, not a wrong row. To answer on the same tree:

# while this PR is open — GitHub drops the merge commit once it closes
git fetch origin eaef1dce44dc1d16ec17a97177bf7e46a9814cc1 && git checkout eaef1dce44dc1d16ec17a97177bf7e46a9814cc1
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin a3ac7fb3808e2c17a369cab00f175ccb03e5e5f7 1863f9895b1b0e4552a0cd82acc2079bb813ac03 && git checkout -B drift-repro a3ac7fb3808e2c17a369cab00f175ccb03e5e5f7 && git merge --no-ff 1863f9895b1b0e4552a0cd82acc2079bb813ac03

node scripts/docs-audit/affected-docs.mjs --json a3ac7fb3808e2c17a369cab00f175ccb03e5e5f7

⚠️ That checkout carried uncommitted changes, so the commit above does not fully identify what was read.

[objectstack-fleet]

domain:server#3 · os-project-manager · session_01FEkQ5pXkgNXVpCn2GZDjyy

席位意见：ACCEPT · Head-sha 1863f9895b1b0e4552a0cd82acc2079bb813ac03 · 2026-11-08T13:59Z。正文「维护者速读」与席位读到的 diff 一致。本 PR 不在 governed 面上，由席位落地，维护者不需要操作。

席位核对

• 形态： draft，目标 main，首行 Fixes #31426；Clause-②: no、Metadata-protocol: none 都在行首，changeset 也写了。
• diff： quiet_hours 增加了 widget: 'quiet-hours'，注释写法和 topic、channel 一样带 [#30208 row 6]。字段仍是 json，存储格式不变，没有新增拒绝。FieldSchema.widget 是自由字符串，所以 Clause-②: no 成立。前端一半 PR feat(fields): draw a notification preference's quiet hours as a time-zone picker and two times #31459 已经合并。
• 文档： 按 ui 席位的留言（6719581791），field-types.mdx 新增一小节，用表格列出三个通知偏好控件：notification-topic、notification-channel、quiet-hours。
• 钉子： 钉子在 notification-preference-topic-channel-help.test.ts。删掉 widget 那一行，结果是 1 个失败、4 个通过。
• 门禁（check-runs @ 1863f989）： 39 个 success，20 个 skipped，0 个失败。被取消的 1 个是重复的 "Check Changeset"，同名的另外两次都成功了。dev 本地跑了 94 个门族，全部退出码 0。
• 落地条款： check-governed-merges --pr 31534：0 个 governed，+36/−0，走普通队列。席位把它转为 ready 并开启 auto-merge，合并后关闭 notification preference: quiet_hours declares the quiet-hours widget hint (server half of #31421) #31426。