Setup notification preferences: topic and channel pickers from the preference-options list (#30208 row 6, ui half)

domain:server#2 · os-tesla · session_01L9qibyvxbrLP4jm4PargoH

Filing gate: ④ coordination child of #30208 (row 6, step 2 of ruling E's execution plan 6670396132; the server half landed as PR #31004, 4fae0be8).
Business reason: an administrator setting notification preferences or templates in Setup types the topic and channel into free-text boxes today. A typo (invoice.paid vs invoices.paid, emial) silently mutes or misroutes that person's notifications. The maintainer ruled pickers with a free-text fallback (E, #30527). The server now serves the lists, but nothing in the console uses them, so row 6 stays open until this lands.
Reader who acts: a domain:ui seat's card thread, in ui/ (the field registry and the record form), one PR.
Duplicate search: repo:objectstack-ai/objectstack is:issue "preference-options" OR "fillable dropdown" OR "quiet hours" → 22 hits, none open for this (#30208 is the parent; #30527 the closed decision; #25346 the closed original report).

What exists now (server half, #31004)

GET /api/v1/messaging/preference-options answers { success: true, data: { topics, channels } }. * comes first. Topics are the platform's fixed topics, the literal topics in this environment's flow notify steps, and the topics this organization has already sent. Channels are every known channel, with those whose service is not configured marked "not configured". It is scoped to the caller's organization: a topic stored in another organization is never listed.
sys_notification_preference.topic declares widget: 'notification-topic', .channel declares widget: 'notification-channel', and sys_notification_template.topic declares widget: 'notification-topic'. FieldSchema.widget is an existing free string, so an unregistered widget falls back to the text box. That is today's behaviour.

Ask (ruling E, step 2)

Register the two widgets as fillable dropdowns: a fillable arm on RegistryRefField, or a new field beside FlowReferenceField. The thread picks one and says why.
Each one reads its list from the route above. If the route fails or answers an empty list, it falls back to the plain text box.
A typed value that is not in the list is stored as typed and shown marked "not in the list". It is never refused and never rewritten.
A channel marked "not configured" is listed, labelled as such, and still selectable.
The template's channel keeps channel_renders_template as it is today. It is not in scope.

Acceptance

In Setup → Notification Preferences and Notification Templates, the topic and channel fields open a dropdown with the served list, * first, and still accept a typed value.
Tests: the list renders from the route; the fallback to the text box when the route fails; a value outside the list is saved and marked; a "not configured" channel is shown labelled.
On merge, row 6 of Setup: replace developer wording and hand-written JSON with fields a business administrator can use #30208 closes (Part of #30208). Quiet hours (step 3) and row 5 are not in this card.

triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

Path: none

Triage: audit · p3 kept · `domain:ui` · 2026-11-06T23:54Z

⛔ Not a claim.

Row 6 of Setup: replace developer wording and hand-written JSON with fields a business administrator can use #30208, the UI half: Setup's notification preference and template forms use the server's preference-options list (PR feat(service-messaging): serve the notification topics and channels a preference or template can name #31004) as topic and channel pickers with a free-text fallback, under the maintainer's ruling E ([Decision] 通知偏好 topic/channel: pickers, refuse unmatched values, or free text as ruled on #25346? #30527).
p3 kept, the same grade as its parent Setup: replace developer wording and hand-written JSON with fields a business administrator can use #30208. Lane domain:ui, pm:queue.
The widgets notification-topic and notification-channel are already declared on the fields (FieldSchema.widget is a free string), so the UI registers them. No spec change.

Generated by Claude Code

domain:ui#2 · os-tesla · session_01L9qibw7DekEe3wx5f3zphf

Claim: PM loop round 9 · 2026-11-07T00:02Z
Session: session_01L9qibzyvUbUU6pC3x3Amrx (card thread, dev) · seat session_01L9qibw7DekEe3wx5f3zphf
Account: os-tesla
Branch: claude/project-thread-sotebb (a cloud card thread can push only its designated branch; base main@23cf11a4)
Worktree: objectstack-issue-31062
Domain: domain:ui
Seat: domain:ui#2
File surface: the chosen widget file(s) and their registration in ui/packages/fields (or ui/packages/app-shell if beside FlowReferenceField), their tests, console i18n keys in ui/packages/i18n (all packs), root .changeset/
Container & model: M, mode:thread, model: default tier (dispatch-gates --tier: no path-derived mandate), effort: high
Clause-②: no
Metadata-protocol: none (the widget names already ship in metadata via #31004)
Responsibility: n/a — not a defect card (ruling E step 2: the console doesn't use the served lists yet)
Premise: holds as filed (triage 6699010961) · the dev measures Setup's text boxes and the route's answer live on main
Serial constraints: none known; the dev checks open PRs on ui/packages/fields/src/widgets/** and Flow*Field.tsx before the first commit. Out of scope: template channel, quiet hours, row 5 of #30208, any server change.
Order: /mnt/project-files/ui-seat-2/r2026-11-06/dispatch-31062.md

domain:ui#3 · os-tesla · session_01L9qibxW6qraU2Z3mwupUGp

Claim: PM loop round 11 · 2026-11-07T00:03Z
Session: session_01L9qibxW6qraU2Z3mwupUGp
Account: os-tesla (the card's assignee)
Branch: the card thread's designated claude/project-thread-* branch, named in a claim amendment once the thread reports it
Worktree: objectstack-issue-31062
Domain: domain:ui
Seat: domain:ui#3 (split notified to domain:ui#2 on mailbox #30817 in this round)
File surface: the two fillable dropdown widgets notification-topic and notification-channel in ui/packages/fields/src/widgets/ (a fillable arm on RegistryRefField.tsx or a new field beside it; the thread picks one and says why), their registration in the field registry (ui/packages/fields/src/index.tsx), their tests, and the console language-pack keys they need in all eleven packs (⛔ no ceiling raise on i18n-locale-en; no room → stop and report). Read the list from GET /api/v1/messaging/preference-options (PR #31004) through the existing client or adapter path; if no client method exists for it, stop and report (the seat files it to domain:server). Route failure or an empty list falls back to the plain text box; a typed value outside the list is stored as typed and marked "not in the list", never refused or rewritten; a "not configured" channel is listed, labelled, selectable. ⛔ The template's channel (channel_renders_template) stays as it is. ⛔ Quiet hours and row 5. ⛔ packages/**. Stop on breach and explain in the report.
Container & model: M, mode:thread, model: default (opus), effort: high
Clause-②: yes (widening) — new console keys in the published @object-ui/i18n packs and two newly registered widget names (if the PR adds no keys, the dev reports what it adds and the seat amends)
Metadata-protocol: none
Responsibility: n/a — not a defect card
Thread-read: 6699010961
Premise: holds as filed — triage audit 6699010961 (p3, domain:ui); #31004 merged 4fae0be8; the dev re-reads the route, the three widget: declarations and RegistryRefField.tsx on origin/main 23cf11a4b9 before the first edit.
Serial constraints cleared: open PRs read at claim time (REST, every non-mailbox, non-release PR's file list): none touches RegistryRefField.tsx, FlowReferenceField.tsx or ui/packages/fields/src/index.tsx.
Resume-from: origin/main

domain:ui#3 · os-tesla · session_01L9qibxW6qraU2Z3mwupUGp

席位核对 · Withdrawal · 2026-11-07T00:04Z · claim 6699186535 withdrawn

⛔ Not a claim. domain:ui#2's claim 6699169269 (2026-11-07T00:02Z) is earlier than this seat's 6699186535, and its card thread is already open, so domain:ui#2 owns #31062 and its claim stands. This seat leaves the labels and the assignee as domain:ui#2 set them.

domain:ui#2 · os-tesla · session_01L9qibw7DekEe3wx5f3zphf

Claim amendment (6699169269) · 2026-11-07T00:27Z · file surface widened by two drift-guard rows, at the dev's measured request (branch head 87fe1d0e):

ui/packages/app-shell/src/utils/paramValueShape.ts: two widgetHintOnly rows for notification-topic / notification-channel, beside position-ref / permission-ref (its VALUE_SHAPES must declare every FORM_FIELD_TYPES key).
ui/packages/plugin-detail/src/__tests__/inlineEditTypeCoverage.test.tsx: the two names added to the excluded bucket of the "four buckets, as landed" pin.

The same mechanical ripple position-ref took (objectui#7611), with no behaviour change. No open PR touches either file (seat checked at the time of this stamp). Everything else in the claim stands.

domain:ui#2 · os-tesla · session_01L9qibw7DekEe3wx5f3zphf

Claim amendment 2 (6699169269) · 2026-11-07T00:58Z · file surface widened by one generated file, at the dev's measured request: ui/packages/cli/src/utils/known-schema-types.ts. It is regenerated by node ui/scripts/regenerate-known-schema-types.mjs, with exactly two added lines, field:notification-channel and field:notification-topic, which is the same regen position-ref got. Hand edits are not allowed; the derivation pin known-schema-types-derivation-5115 checks the file. Everything else in the claim and in amendment 6699576193 stands.

domain:ui#2 · os-tesla · session_01L9qibzyvUbUU6pC3x3Amrx

os-dev-report

{
  "issue": 31062,
  "status": "done",
  "branch": "claude/project-thread-sotebb",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/31069",
  "session": "session_01L9qibzyvUbUU6pC3x3Amrx",
  "premise_still_valid": true,
  "summary": "Registered field:notification-topic and field:notification-channel in @object-ui/fields as a fillable arm on RegistryRefField (home a: it registers through fieldWidgetMap, which the record form consults for FieldSchema.widget). The list is read from GET /api/v1/messaging/preference-options through SchemaRendererContext.apiFetch, shared per page; no host fetch, a failed or malformed answer, or an empty list gives the plain text box with no notice; a typed value is committed verbatim and a stored value outside the list is shown marked 'not in the list'; a not-configured channel is labelled and selectable. Five fields.preferenceOption.* keys in all eleven packs (zh-Hant regenerated). Live before (main 23cf11a4): both Setup forms show INPUT type=text for topic and channel; route answers 28 topics, 5 channels with push configured:false. Live after: pickers list the route, '*' first; typed invoices.paid saved and marked; push (not configured) picked and saved; template channel stays a text box.",
  "tests": "head 1fc7c752 (gates/type-check at da4d45a2; the last commit adds only the regenerated known-schema-types.ts). RegistryRefField.preferenceOptions-31062.test.tsx 14 passed. Ripple run (fields/, i18n/, components form/, plugin-form 7611, app-shell form-type guards, cli ratchet): 8 reds before the ripple rows, all rerun green (361+367+48). ui scripts/ suite at 1fc7c752: 170 passed, 2 skipped. type-check fields, i18n, app-shell: exit 0. Ablation via scripts/ablation-replace.mjs (src import, no build in path): deleting the 'notification-topic' loader from fieldWidgetMap -> 1 failed / 12 passed ('expected undefined to be defined'); anchor 1->0, restore blob == HEAD 9ddd86c78ae7, git diff HEAD empty.",
  "gates": "dispatch-gates --commands: 38 families, all exit 0 (record /mnt/project-files/ui-seat-2/r2026-11-06/31062/gates-ran-1fc7c752.list); --ran: 38 derived, 38 run, 0 NOT-MEASURED. check-sdui-manifest exit 0. Re-derived at 1fc7c752: same 38. CI check-runs: in_progress at report time. check:eager-closure needs a Console build: CI's.",
  "line_budget": "23 files, +774/-28 at da4d45a2 plus 2 generated lines at 1fc7c752 (about 804 changed lines, under 3000)",
  "files_changed": ".changeset/31062-notification-topic-channel-pickers.md; ui/packages/fields/src/{index.tsx,FieldEditWidget.tsx,widgets/RegistryRefField.tsx,widgets/preferenceOptions.ts,widgets/useFieldTranslation.ts,widgets/__tests__/RegistryRefField.preferenceOptions-31062.test.tsx,__tests__/widget-aria-invalid-registry-e2e.test.tsx,__tests__/widget-dom-leak-e2e.test.tsx}; ui/packages/i18n/src/locales/{ar,de,en,es,fr,ja,ko,pt-BR,ru,zh-Hans,zh-Hant}.ts; ui/packages/i18n/src/__tests__/de-quote-pairing-3876.test.ts; ui/packages/app-shell/src/utils/paramValueShape.ts (amendment 6699576193); ui/packages/plugin-detail/src/__tests__/inlineEditTypeCoverage.test.tsx (amendment 6699576193); ui/packages/cli/src/utils/known-schema-types.ts (regenerated, amendment 6699989026)",
  "deviations": "Three out-of-surface files, each added to the claim by the seat before the edit (6699576193, 6699989026). The widget reads only the host apiFetch, no global-fetch fallback: the widget sweeps' network-escape guard caught a bare fetch, and the ruling names the console's authenticated path. Gate loop run outside the verify lock (check scripts), tests and type-check under it.",
  "dogfood_battery": "n/a — no ! in the PR title and no (narrowing) arm",
  "mcp_calls": "7 — reads only: issue_read x3, list_pull_requests x1, ToolSearch-loaded tools; 0 writes. Plus 5 gh api REST reads of PR file lists (reads, no writes).",
  "api_writes": "2 — relay pr_create (#31069); this os-dev-report comment via post-stamped",
  "open_questions": [
    {
      "question": "Clause-② is copied as 'no' from the claim, but the PR adds five keys to every published @object-ui/i18n pack and two registered widget keys; recent i18n-key changesets split between 'no' and 'yes (widening)'.",
      "options": [
        "A keep 'no' as claimed",
        "B amend to 'yes (widening)' in the PR body and changeset"
      ],
      "recommendation": "B, because the published packs and the field registry both gain names, which is the reading #30748 and #30329 took"
    }
  ],
  "security_findings": "none",
  "out_of_scope_findings": [
    "carrier: none · noted, not filed — open PR #31037 edits the same ten hand-written i18n packs in a different block; the second to land takes a textual merge"
  ]
}

domain:ui#2 · os-tesla · session_01L9qibw7DekEe3wx5f3zphf

ACCEPT → PR #31069 comment 6700398034 · 2026-11-07T01:33Z · head 43dd3c69 (notification topic and channel pickers from preference-options, free-text fallback; 804 lines, Tier S path, Clause-②: yes (widening) with TIER_DEFAULT record PASS 6700168365, Fixes #31062). Landing through the merge queue.

domain:ui#2 · os-tesla · session_01L9qibw7DekEe3wx5f3zphf

Landed (Setup's notification topic and channel fields are pickers fed from preference-options, with a free-text fallback) at 2026-11-07T01:59Z: PR #31069 merged as 3f61e4f8 (head 43dd3c69; Tier S; Clause-②: yes (widening) with TIER_DEFAULT record PASS 6700168365; seat ACCEPT 6700398034). The PR said Fixes #31062, so the card closed on merge.

probe	reading
`git ls-tree origin/main ui/packages/fields/src/widgets/preferenceOptions.ts`	present
`git grep -c "'notification-topic': () => import" origin/main -- ui/packages/fields/src/index.tsx`	1

Release: session_01L9qibw7DekEe3wx5f3zphf (domain:ui#2) · because the card is done · pm:dispatched removed in this stroke. Row 6 of #30208 is reported there.

Navigation Menu

Repository navigation

Setup notification preferences: topic and channel pickers from the preference-options list (#30208 row 6, ui half) #31062

What exists now (server half, #31004)

Ask (ruling E, step 2)

Acceptance

Triage: audit · p3 kept · `domain:ui` · 2026-11-06T23:54Z

席位核对 · Withdrawal · 2026-11-07T00:04Z · claim 6699186535 withdrawn

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Setup notification preferences: topic and channel pickers from the preference-options list (#30208 row 6, ui half) #31062

Description

What exists now (server half, #31004)

Ask (ruling E, step 2)

Acceptance

Activity

objectstack-fleet commented on Nov 6, 2026

Triage: audit · p3 kept · domain:ui · 2026-11-06T23:54Z

objectstack-fleet commented on Nov 7, 2026

objectstack-fleet commented on Nov 7, 2026

objectstack-fleet commented on Nov 7, 2026

席位核对 · Withdrawal · 2026-11-07T00:04Z · claim 6699186535 withdrawn

objectstack-fleet commented on Nov 7, 2026

objectstack-fleet commented on Nov 7, 2026

objectstack-fleet commented on Nov 7, 2026

objectstack-fleet commented on Nov 7, 2026

objectstack-fleet commented on Nov 7, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Triage: audit · p3 kept · `domain:ui` · 2026-11-06T23:54Z