[objectstack-fleet]

Requested by Bill · project thread

domain:ui#3 · os-bill · session_01Utp6CbPN5UYMnBaNJPJWfG

Fixes #30366

Clause-②: yes (widening)
Metadata-protocol: none

维护者速读

• 改了什么：忘记密码页在服务端报告 features.emailDelivery: false（没接邮件服务或只用 log 传输）时，提交后不再说「已发送重置链接」，改为「此处无法通过邮件发送重置链接，请联系管理员在 设置 → 用户 中为你设置新密码」，十种语言齐全。
• 为什么改：不发邮件的部署上，用户会一直等一封永远不来的邮件；服务端一半（Forgot password says the reset link was sent on a deployment with no email service #30107，PR fix(auth): say on /auth/config whether email leaves the deployment, so forgot-password can stop claiming a link was sent #30365）已经提供这个开关，这里是界面一半。
• 风险与回滚：只有明确的 false 才换文案；老服务端不带这个字段、或取配置失败，保持现在的文案。新文案不含地址、与提交结果无关，不会泄露账号是否存在。回滚即撤销本 PR。
• 先看：ui/packages/auth/src/ForgotPasswordForm.tsx（成功页分支）、ui/packages/auth/src/__tests__/forgot-password-success-message.test.tsx（新 describe 块）、ui/apps/console/src/pages/auth/ForgotPasswordPage.tsx（两行 label 传递）。
• 两分钟验证：pnpm --dir ui exec vitest run packages/auth/src/__tests__/forgot-password-success-message.test.tsx，预期 10/10 通过。
• 需要你做的：无，席位落地。

What changes

• ForgotPasswordForm reads features.emailDelivery from the /auth/config answer it already fetches (alongside phoneNumberOtp). On an explicit false the success screen shows noDeliveryTitle / noDeliveryDescription — "A reset link can't be emailed here" / "This deployment doesn't send email, so no password reset link can reach you. Ask an administrator: they can set a new password for you from Setup → Users." — with an amber icon instead of the green one. The submit still goes to the server, so a log-transport deployment keeps writing the link to its console.
• ForgotPasswordFormLabels gains noDeliveryTitle and noDeliveryDescription; AuthPublicConfig.features gains emailDelivery (the server half's AuthFeaturesConfigSchema.emailDelivery).
• New strings auth.forgotPassword.noDeliveryTitle and auth.forgotPassword.noDeliveryDescription in all ten locale packs, passed through by the Console's forgot-password page (label wiring only, per the claim's file-surface ruling) and by DefaultForgotPasswordPage in @object-ui/app-shell.
• Changeset: @object-ui/auth, @object-ui/i18n, @object-ui/app-shell, @object-ui/console, all patch (Metadata-protocol none).

Why

On a deployment with no mail transport, every reset request ended on "Check your email — we've sent a password reset link to …", and nothing arrived. The server half (#30107, PR #30365) now says whether mail leaves the deployment; this is the page reading it.

An absent key keeps today's text. The spec text for the flag says absent means not live, but on the wire an absent key means a server older than the flag, and most of those do send mail; telling their users to find an administrator would be the larger harm. A failed config fetch is the same unknown. So only emailDelivery === false swaps the screen, and both unknowns are pinned to keep the "check your email" text.

No account-existence oracle. The new text names no address and is chosen by the deployment flag alone, never by the reset request's answer (which is the same for known and unknown addresses server-side). A test submits a known and an unknown address on a no-mail deployment and asserts the two screens are byte-identical and carry no address.

Tests

• forgot-password-success-message.test.tsx — new top-level describe (objectstack#30366) in the existing harness file: no-mail screen text and no address; known vs unknown address read identically; caller-supplied labels used; emailDelivery: true, absent key, and failed fetch each keep the old screen.

Local runs (head 74302c6 after merging origin/main; the merge brought no ui/ paths)

• pnpm --dir ui exec vitest run packages/auth/src/__tests__/forgot-password-success-message.test.tsx …/identifier-trim.test.tsx …/phoneTouchTargets-29080.test.tsx — Test Files 3 passed, Tests 14 passed.
• pnpm --dir ui exec vitest run packages/i18n/ — Test Files 95 passed, Tests 1443 passed / 13 skipped (key parity included).
• pnpm exec turbo run type-check --filter=@object-ui/auth --filter=@object-ui/app-shell --filter=@object-ui/console --concurrency=2 — Tasks 76 successful, 76 total.
• eslint on the changed ts/tsx files — exit 0. pnpm check:new-line-citations (ui) — 0 new citations.
• Ablation via scripts/ablation-replace.mjs: setEmailDeliveryOff(config?.features?.emailDelivery === false); replaced by setEmailDeliveryOff(false); — 3 of the new tests fail (no-mail text, known/unknown parity, translated labels), 7 pass; restore verified blob == HEAD and git diff HEAD empty. (The three keep-old-text cases pass under the mutation by design.)

Verification

Derived gates

node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack: 35 commands, all run, each exit 0, including node scripts/check-sdui-manifest.mjs and pnpm --dir ui exec vitest run scripts/ (170 files passed). --ran reconciliation: 35 derived, 35 run, 0 NOT-MEASURED, 0 UNRUN; pnpm check:changeset-fixed also run (outside the derivation), exit 0. CI type-check lanes are left to CI.

Acceptance notes

• The server half PR fix(auth): say on /auth/config whether email leaves the deployment, so forgot-password can stop claiming a link was sent #30365 is open at this head. The UI only reads an optional key, so this compiles and runs against today's main (where the key is never sent, and the old text shows). origin/main gets merged again once fix(auth): say on /auth/config whether email leaves the deployment, so forgot-password can stop claiming a link was sent #30365 lands, before acceptance.
• File surface widened by the claim's ruling A: the two label-passing pages, label lines only. ui/packages/auth/src/types.ts (the emailDelivery declaration on AuthPublicConfig.features) is outside the listed surface: without it the read does not type-check.

Human Minimum

• 1. Schemas start as Zod; packages/spec holds no runtime logic. (not touched)
• 2. Every name I added uses the casing for its kind.
• 3. No formatter ran; pnpm lint passes. (eslint on changed files; full run is CI's)
• 4. One issue, one branch off an up-to-date main, one pull request.
• 5. A change that publishes carries a changeset, and both declaration lines are filled in here and in the changeset.
• 6. packages/spec touched: n/a.
• 7. No hand edits to content/docs/references/, packages/*/CHANGELOG.md or content/docs/releases/.
• 8. Title, body and comments are in English.
• The Before Submitting list in CONTRIBUTING.md is done.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Utp6CYv3DdXJ81i2yQpGKm

---

Generated by Claude Code

[objectstack-fleet]

domain:ui#3 · os-bill · session_01Utp6CbPN5UYMnBaNJPJWfG

维护者速读

• 改了什么：忘记密码页在服务端报告 features.emailDelivery: false（没接邮件服务）时，提交后不再说「已发送重置链接」，改为「此处无法通过邮件发送重置链接，请联系管理员在 设置 → 用户 中为你设置新密码」，十种语言。
• 为什么改：不发邮件的部署上，用户会一直等一封永远不来的邮件；服务端一半 fix(auth): say on /auth/config whether email leaves the deployment, so forgot-password can stop claiming a link was sent #30365 已提供这个开关，这里是界面一半（Forgot password page: read features.emailDelivery and say a reset link cannot be emailed here (ask an administrator) instead of saying it was sent #30366）。
• 风险与回滚：只有明确的 false 才换文案；老服务端不带这个字段或取配置失败时保持现在的文案。新文案不含地址、与提交结果无关，不会泄露账号是否存在。回滚即撤本 PR。
• 先看：ui/packages/auth/src/ForgotPasswordForm.tsx 的成功页分支，测试文件里新的 describe 块，ui/apps/console/src/pages/auth/ForgotPasswordPage.tsx 的两行 label 传递。
• 两分钟验证：pnpm --dir ui exec vitest run packages/auth/src/__tests__/forgot-password-success-message.test.tsx，预期 10/10 通过。
• 需要你做的：无，席位落地。
• 席位意见：可合。

席位核对 — ACCEPT · head 28a6cc3

• 形态：16 文件 +184/−8（表单 +43/−7、类型 +10、两个页面各 2–7 行 label 传递、十个语言包各 2 键、测试 +85、changeset）。check-governed-merges --pr 30406：NOT governed，192 行 ≤ 3000。Fixes #30366。
• 契约复审（TIER_DEFAULT，席位自审）：Clause-② yes (widening)。ForgotPasswordFormLabels 加两个可选 label，AuthPublicConfig.features 加可选 emailDelivery（与 fix(auth): say on /auth/config whether email leaves the deployment, so forgot-password can stop claiming a link was sent #30365 的 AuthFeaturesConfigSchema.emailDelivery，z.boolean().optional() 同形），@object-ui/i18n 加 auth.forgotPassword.noDeliveryTitle/Description，十包齐全。全部可选新增，已有调用方不受影响。Metadata-protocol none。
• 席位读码：文案只由部署开关决定，不看重置请求的回答，新文案不含地址；测试对已知和未知地址断言两屏逐字节相同（防探测规则）。缺省键与取配置失败都保持旧文案并已钉住，理由写在 PR：缺省键在线上意味着早于该开关的服务端，多数会发邮件。
• 前提实测：服务端 PR fix(auth): say on /auth/config whether email leaves the deployment, so forgot-password can stop claiming a link was sent #30365 已合（09720e2c），合 main 后 head 28a6cc3 上 check:spec-symbols 由红转绿，auth 4 文件 28/28，@object-ui/auth 类型检查通过。消融 3 红。
• 门禁 check-runs：head 上 55 个，44 success、11 skipped（Test Core、Build Core、Build Docs、Dogfood、Temporal、opt-in 冒烟等 server/core/opt-in 项，ui-only diff 的预期跳过），无红。74302c6d 上的 Live E2E UI 红（studio-customize-journey 的 ECONNRESET）在本 head 上为绿，未复现。
• 接受的偏差：两个 ForgotPasswordPage 文件按裁定 A 只加 label 传递，ui/apps/console/src/pages/auth/** 其余文件未碰（Mobile sign-in: a person who has to verify their email during the hand-off gets a mail link to 页面不存在, and the verify page drops the refusal time #30157）；ui/packages/auth/src/types.ts 不在列出文件面内但同包、类型检查所必需，席位放宽。门禁全集在 5e19b7f 上跑，之后只合入不含 ui/ 的 main，接受。
• 范围外去向：spec 说明「缺省即未启用」与界面「缺省即未知」的差异 → Acceptance notes（界面取保守读法，不立卡）。
• 落地条款：中继 pr_ready + automerge_enable；合并后清 pm:dispatched，在 Forgot password page: read features.emailDelivery and say a reset link cannot be emailed here (ask an administrator) instead of saying it was sent #30366 发落地评论。