feat(account): define release notification consumption

docs/PMFLOW_PRODUCT_DELIVERY_STANDARD.md

@@ -807,6 +807,34 @@ P0 公共壳冻结已完成，下一批可以进入 `Batch P1` 三模块并行
 
 ## 8. 进度台账
 
+### 2026-04-26 / account-p3-release-notification-consumption-contract / implemented
+
+完成内容：
+
+- 在 `frontend/src/api/accountSettings.ts` 新增 `AccountReleaseNotificationEvent` 与 `getReleaseGateNotificationPreference(settings, event)` 轻量合同。
+- Release/Growth 后续页面可按事件类型消费偏好：`release_gate_blocked / release_gate_ready / release_validation_blocked / release_validation_needs_confirmation` 映射到 `releaseGate`，`failed_event` 映射到 `failureAlert`。
+- helper 明确返回 `inAppEnabled / desktopPreference / emailDigestPreference`，以及 `notificationKey / surface / reason`，用于后续 Main Flow 页面决定页面内提醒展示或静默。
+- 本轮只做 Account Settings API/helper 与测试，不改 `ReleaseGrowthPage`、PMFlow OS store、router、auth core，不新增后端字段，不接入真实邮件/桌面推送。
+
+涉及文件：
+
+- `frontend/src/api/accountSettings.ts`
+- `frontend/src/features/account-settings/accountSettings.test.ts`
+- `docs/architecture/CODE_REFERENCE_INDEX.md`
+- `docs/architecture/ARCHITECTURE_INVENTORY.md`
+- `docs/PMFLOW_PRODUCT_DELIVERY_STANDARD.md`
+
+验证：
+
+- `cd frontend && npm run test -- src/features/account-settings/accountSettings.test.ts` 通过：`9 passed`。
+- `cd frontend && npm run typecheck` 通过。
+- `cd frontend && npm run build` 通过；Vite 仍提示既有 manual chunk circular warning，但构建成功。
+
+未完成或风险：
+
+- Main Flow 尚未在 `ReleaseGrowthPage` 消费该 helper；后续应由 Main Flow lane 读取账号设置后按 release gate / release validation / failed event 类型调用。
+- `desktopPreference / emailDigestPreference` 仍只是偏好记录，不代表真实系统级桌面通知、邮件通知或通知中心已接入。
+
 ### 2026-04-26 / space-p3-validation-run-attention / implemented
 
 完成内容：

docs/architecture/ARCHITECTURE_INVENTORY.md

@@ -196,7 +196,7 @@
 - 前端主包治理已切到“同步首屏最小集 + route/page-section lazy”模式：`frontend/src/router/index.tsx` 保留 `LoginPage / Layout` 这组同步入口，其余后台重页面通过 `React.lazy + Suspense` 懒加载；统一 fallback 在 `frontend/src/components/layout/LazyBoundary.tsx`。P0 公共壳冻结后，大模块 route 归属为：`/space` 归 Space lane，`/project-launch` 是启动层入口，`/pmflow-os` 与 `/command-center / /change-review / /execution-bridge / /release-growth` 归 Main Flow lane，`/me` 归 Account Settings lane，`/settings` 当前仅为 reserved route、尚未实现，新增必须由 Shell / Integration owner 串行处理。`frontend/src/features/personal-space/` 作为空间层入口，通过 `/space` 提供可直接打开的本地预览入口，承载继续推进、待我确认、AI 正在推进、暂存想法、草案箱与新建项目入口。`frontend/src/features/project-launch/` 作为首次进入页 / 新项目启动台产品域，通过 `/project-launch` 提供可直接打开的入口；Phase B 后默认调用真实 `pmflow-launch` draft/confirm API，创建成功态主动作跳转后端返回的 `/pmflow-os?projectId=<id>`，只有显式 `?demo=1` 或 `?dataSource=demo` 才启用本地 mock 状态机。`frontend/src/features/account-settings/` 作为 Account Settings 产品域，通过 `/me` 提供个人资料、默认语言、AI 回答深度、证据展示偏好、待确认/执行回写/发布门禁/失败提醒通知偏好和账户操作入口；该域通过 `frontend/src/api/accountSettings.ts` 建立前端合同，有 token 时优先调用已挂入 `backend/app/api/router.py` 的 `backend/app/api/account_settings_api/` `GET /account-settings/me` / `PUT /account-settings/me` 同步当前账号偏好，后端不可用时明确回落本机暂存，不修改 OAuth/JWT/auth core。`frontend/src/features/pmflow-os/` 作为新产品域，通过 `PMFlowOsProvider` 在应用根部挂载共享 truth store，并提供 `CommandCenter / ChangeReview / WorkGraph / ExecutionBridge / ReleaseGrowth / TeamLayer / ProjectMemory / Account` 主入口；当前 PMFlow OS 页面已切到专属轻壳，桌面端默认隐藏旧 TopBar，并由 `frontend/src/features/pmflow-os/components/PMFlowOsFrame.tsx` 统一承接“左侧稳定导航 + 顶部上下文条 + 中央视图 + 右侧 AI 副驾”的全局骨架，同时承接项目内 `个人空间 / 当前项目名` 面包屑和项目切换器；账号退出登录由 `frontend/src/features/pmflow-os/components/AccountControls.tsx` 统一承接桌面头像下拉、退出确认与移动端 bottom sheet，`frontend/src/features/pmflow-os/pages/AccountPage.tsx` 提供 `/me` 入口并委托 Account Settings 域渲染设置页；正式应用壳移动端底部导航统一由 `frontend/src/features/pmflow-os/components/MobileBottomNav.tsx` 承接，固定为 `空间 / 指挥台 / 待确认 / 动态 / 我的`，其中 `动态` 当前仍是 `/command-center` 占位。`/command-center` 额外提供免登录产品预览壳，`/pmflow-os` 是真实项目上下文 alias。主视觉按 `#2463EB + 白色` 的 Linear-like 高密度原型展开。`UsersPage` 把创建/删除/重置/导入/批量分配对话框拆为按需 chunk，`UserSkillsPage` 与 `WorkloadDetailPage` 的图表也分别拆到了 `frontend/src/pages/user-skills/components/UserSkillsRadarPanel.tsx` 与 `frontend/src/pages/workload-detail/components/WorkloadTrendChart.tsx`。
 - `frontend/src/features/personal-space/PersonalSpacePage.tsx` 是空间首页视图层，`frontend/src/api/space.ts` 是空间工作面只读聚合 API：从 `projects` summary、PMFlow OS `truth-state` 与 `execution-summary` 生成继续推进、待确认、发布关注、执行中 / AI 正在推进、暂存想法、草案箱、最近项目摘要；Space P3 的 `releaseAttention` 优先消费 `truth-state.releases` 中由 release validation run 投影出的 release 状态与检查项，把“发布验证阻塞 / 发布验证待确认”显示到 `/space`，没有发布验证投影时才回落到 `execution-summary.releaseGate` 的发布候选或发布门禁阻塞；发布验证缺失时显示明确空态，不虚构验证结果。项目主动作进入 `/pmflow-os?projectId=<id>`，待确认项进入 `/change-review?projectId=<id>&changeSetId=<id>`，发布关注项进入 `/release-growth?projectId=<id>`，执行中项进入 `/execution-bridge?projectId=<id>`；暂存想法后端只读聚合尚未接入时只显示 empty/warning，不使用 mock 数据冒充真实内容；移动端为空间首页独立 App 布局，不直接压缩桌面卡片，并保留最近项目区块；`frontend/src/pages/PersonalSpacePage.tsx` 是薄入口。该域只表达个人空间和主流程导航，不做团队空间强切换、企业组织管理、Project Memory 写入、ChangeSet 状态写入、ProgressEvent 写入、ReleaseValidationRun 写入或发布执行。
 - `frontend/src/features/project-launch/types.ts`、`mockData.ts`、`useProjectLaunchState.ts` 是新项目启动台状态层；默认真实模式通过 `frontend/src/api/pmflowLaunch.ts` 生成草案并确认创建真实项目，API 失败进入明确失败态，不静默 fallback 成 mock 成功；`mockData.ts` 仅在显式 `?demo=1` 或 `?dataSource=demo` 下作为演示状态机使用。`components/LaunchShell.tsx` 负责桌面/移动分流，桌面端复用 `frontend/src/features/personal-space/components/SpaceChrome.tsx` 的空间左侧栏和顶部条，`LaunchCanvases.tsx` 和 `MobileLaunchLayout.tsx` 承接高保真图中的意图输入、AI 工作、人类确认、草案修改、生成失败、创建成功过渡与移动端 bottom sheet 交互。
-- `frontend/src/features/account-settings/AccountSettingsPanel.tsx` 是 `/me` 设置页实现：桌面端为个人资料摘要 + 分区设置面板，移动端为分组列表 + `MobileBottomSheet` 编辑；当前覆盖个人资料、默认语言、AI 回答深度、证据展示偏好、待确认、执行回写、发布门禁和失败提醒通知偏好，并在通知偏好区展示页面内提醒消费说明。`frontend/src/api/accountSettings.ts` 是前端合同层；有 token 时优先调用 `backend/app/api/account_settings_api/`，失败时回落浏览器本机暂存；P2 新增 `shouldShowAccountNotification` 与 `getAccountNotificationConsumption`，将四类通知偏好映射为本地 UI 的待确认、Execution Bridge、Release/Growth 和失败提醒显示/静默状态，不代表邮件、桌面推送或系统通知中心已接入。`backend/app/schemas/account_settings.py` 定义账号偏好合同，`backend/app/services/account_settings_service.py` 当前复用既有 `integrations` 表按 `tenant_id + user_id` 保存 `account_settings_preferences` 配置包，`backend/app/api/router.py` 已挂载该 API；未改用户表、OAuth/JWT/auth core 或 PMFlow OS truth store。
+- `frontend/src/features/account-settings/AccountSettingsPanel.tsx` 是 `/me` 设置页实现：桌面端为个人资料摘要 + 分区设置面板，移动端为分组列表 + `MobileBottomSheet` 编辑；当前覆盖个人资料、默认语言、AI 回答深度、证据展示偏好、待确认、执行回写、发布门禁和失败提醒通知偏好，并在通知偏好区展示页面内提醒消费说明。`frontend/src/api/accountSettings.ts` 是前端合同层；有 token 时优先调用 `backend/app/api/account_settings_api/`，失败时回落浏览器本机暂存；P2 新增 `shouldShowAccountNotification` 与 `getAccountNotificationConsumption`，将四类通知偏好映射为本地 UI 的待确认、Execution Bridge、Release/Growth 和失败提醒显示/静默状态；P3 新增 `getReleaseGateNotificationPreference(settings, event)`，把 Release/Growth 的 `release_gate_* / release_validation_*` 事件映射到 `releaseGate` 偏好，把 `failed_event` 映射到 `failureAlert` 偏好，并返回 `inAppEnabled / desktopPreference / emailDigestPreference` 供后续 Main Flow 页面消费。该合同不代表邮件、桌面推送或系统通知中心已接入。`backend/app/schemas/account_settings.py` 定义账号偏好合同，`backend/app/services/account_settings_service.py` 当前复用既有 `integrations` 表按 `tenant_id + user_id` 保存 `account_settings_preferences` 配置包，`backend/app/api/router.py` 已挂载该 API；未改用户表、OAuth/JWT/auth core 或 PMFlow OS truth store。
 - `frontend/src/features/pmflow-os/store.tsx` 当前是 PMFlow OS 共享 truth store：`?projectId=<id>` 时通过 React Query 调用 `frontend/src/api/pmflowOs.ts` 读取真实 `GET /pmflow-os/projects/{project_id}/truth-state` 与 `GET /pmflow-os/projects/{project_id}/execution-summary`，真实模式下项目内 message、`proposed_items` extraction、ChangeItem `accept/edit/defer`、ChangeSet commit、Execution Handoff create/consume 与 execution progress writeback 均调用 `/pmflow-os` 后端并 refetch；只有显式 `?demo=1` 或 `?dataSource=demo` 时才启用本地 mock 演示状态机。真实读取/动作失败会进入错误/空态，不静默 fallback 成 mock 成功。
 - `frontend/src/features/pmflow-os/store.tsx` 仍保留演示用项目内 AI 结构化闭环状态机：`command_idle / ai_extracting / extraction_ready / review_open / writeback_success`。`frontend/src/features/pmflow-os/pages/StructuredExtractionPage.tsx` 是本轮结构化提取页，`ChangeReviewPage.tsx` 是决策与待确认中心，`MemoryWritebackResultPage.tsx` 是项目记忆写入结果页，`WorkGraphPage.tsx` 是项目工作台关系总览与对象投影视图，`ExecutionBridgePage.tsx` 是执行桥上下文包、交接按钮、运行端领取确认、PR/测试与回写状态页；`ReleaseGrowthPage.tsx` 真实模式读取 `execution-summary.releaseGate`，从 branch、commit、PR、test、failed evidence 展示 `可发布 / 阻塞 / 需要人工确认 / 缺少证据` 判断、阻塞原因和下一步动作，不执行发布命令、不展示 mock 发布结果；静态发布/增长原型只保留在显式 demo 模式。A3 已接入后端 truth-state，C1 已接入真实 message/extraction/review 状态机，C2 已接入真实 ChangeSet commit，Phase D 已接入真实 execution-summary/dev-sync，D.2 已接入 `POST /execution-handoffs` 创建 PromptPackage + handoff_created progress event，P1 已接入 `POST /execution-handoffs/{prompt_package_id}/consume` 创建 handoff_consumed progress event 并把 execution status 投影为 coding，Release Growth P1 已接入 execution evidence gate；当前仍不调用真实 AI 提取，不把 mock 当真实失败 fallback。`ProjectMemoryPage.tsx` 在真实模式下展示后端 `truth_nodes + semantic_facts` 的 `projectMemory` 投影，accepted/edited ChangeItem 只有 commit 成功后才进入 Project Memory。`frontend/src/features/pmflow-os/components/ProjectStructuredLoop.tsx` 提供 `StatusLabel / EvidenceSnippet / ObjectChangeCard / ProjectConversationPanel / StructuredExtractionPanel / ProjectAICopilotPanel` 等闭环组件，并复用契约化 `InlineNotice` 表达“未确认不得写入”的局部提示。
 - PMFlow OS 后端入口位于 `backend/app/api/pmflow_os_api/`，projection service 位于 `backend/app/services/pmflow_os_projection_service.py`，Change Review / commit 服务位于 `backend/app/services/pmflow_change_review_service.py`，Pydantic 合同位于 `backend/app/schemas/pmflow_os.py`；当前聚合 `truth_nodes / tasks / semantic_facts / ai_project_control / dev_sync`，`Thread / Message` 来自 `pmflow_threads / pmflow_thread_messages`，`ChangeSet / ChangeItem / Approval / EvidenceLink` 来自 `backend/app/models/pmflow_change_review.py` 对应真实表。C1 已实现 message、`proposed_items` extraction、ChangeSet detail、ChangeItem `accept/edit/defer`；C2 backend/frontend 已实现 `POST /pmflow-os/change-sets/{change_set_id}/commit` 与真实模式前端接入，默认 atomic，将 `Requirement / Decision / Risk` 写入 `truth_nodes`，将 `Task` 写入 `truth_nodes(node_type='task') + tasks`，高风险项强制 approval gate；D.2 已实现 `POST /pmflow-os/projects/{project_id}/execution-handoffs`，校验 task/repo project 边界，生成/复用 `PromptPackage(package_kind='execution_handoff')` 并写 `ProgressEvent(event_type='handoff_created')` 起点；P1 已实现 `POST /pmflow-os/projects/{project_id}/execution-handoffs/{prompt_package_id}/consume`，校验 execution handoff package 后更新 `PromptPackage.package_payload.latest_handoff.handoff_state=consumed` 并写 `ProgressEvent(event_type='handoff_consumed', derived_task_status='coding')`；Release Growth P1 在 `ExecutionSummaryProjection.releaseGate` 中从 `ProgressEvent` 推导发布门禁状态，失败事件 fail-closed 阻塞发布，无证据返回 empty/warning；这些步骤都不直接执行本机命令或真实发布命令；`ModelDecision / MetricSignal` 在 C2 V1 仍 fail-closed。

docs/architecture/CODE_REFERENCE_INDEX.md

@@ -106,13 +106,13 @@
 - PMFlow OS 前端 MVP 产品域：参考 `frontend/src/features/pmflow-os/`
 - 个人空间首页 / 空间层入口前端产品域：参考 `frontend/src/features/personal-space/`、`frontend/src/api/space.ts` 与薄入口 `frontend/src/pages/PersonalSpacePage.tsx`；本地预览路由入口为 `/space`，覆盖继续推进、待我确认、发布关注、执行中 / AI 正在推进、暂存想法、草案箱与最近项目，点击项目主动作进入 `/pmflow-os?projectId=<id>`，待确认项进入 `/change-review?projectId=<id>&changeSetId=<id>`，执行中项进入 `/execution-bridge?projectId=<id>`，发布关注项进入 `/release-growth?projectId=<id>`；Space 只读聚合项目摘要、PMFlow OS `truth-state.releases / execution-summary.releaseGate`，发布验证缺失时显示明确空态，不虚构验证结果，不直接写 Project Memory、ChangeSet 状态、execution event 或 ReleaseValidationRun；暂存想法后端只读聚合尚未接入时必须显示 empty/warning，不得用 mock 数据冒充真实内容；空间层共享左侧栏、顶部条与空间用量组件在 `frontend/src/features/personal-space/components/SpaceChrome.tsx`，`/project-launch` 桌面首次新建壳也复用该组件
 - 新项目启动台 / 首次进入页前端产品域：参考 `frontend/src/features/project-launch/` 与薄入口 `frontend/src/pages/ProjectLaunchPage.tsx`；真实模式默认通过 `frontend/src/api/pmflowLaunch.ts` 调用后端 draft/confirm API，只有显式 `?demo=1` 或 `?dataSource=demo` 才启用 `mockData.ts` 本地演示状态机；本地预览路由入口为 `/project-launch`
-- Account Settings / `/me` 前端产品域与 P1/P2 偏好合同：参考 `frontend/src/features/account-settings/AccountSettingsPanel.tsx`、`frontend/src/features/pmflow-os/pages/AccountPage.tsx`、`frontend/src/api/accountSettings.ts`、`backend/app/api/account_settings_api/`、`backend/app/schemas/account_settings.py` 与 `backend/app/services/account_settings_service.py`；当前覆盖个人资料、默认语言、AI 回答深度、证据展示偏好、待确认、执行回写、发布门禁和失败提醒通知偏好，移动端使用分组列表与 bottom sheet，账户退出仍复用 `AccountControls.tsx`，不改 OAuth/JWT/auth core；P1 后端合同提供 `GET /account-settings/me` 与 `PUT /account-settings/me`，已由 `backend/app/api/router.py` 挂入核心路由组，按当前 `tenant_id + user_id` 保存账号偏好，前端有 token 时优先账号同步，后端不可用时明确回落 `仅本机暂存 / 保存失败`；P2 在 `frontend/src/api/accountSettings.ts` 提供 `shouldShowAccountNotification` 与 `getAccountNotificationConsumption`，把通知偏好映射为页面内提醒消费模型，只控制本地 UI 的待确认、执行回写、发布门禁和失败提醒展示，不代表真实邮件/桌面推送已接入
+- Account Settings / `/me` 前端产品域与 P1/P2/P3 偏好合同：参考 `frontend/src/features/account-settings/AccountSettingsPanel.tsx`、`frontend/src/features/pmflow-os/pages/AccountPage.tsx`、`frontend/src/api/accountSettings.ts`、`backend/app/api/account_settings_api/`、`backend/app/schemas/account_settings.py` 与 `backend/app/services/account_settings_service.py`；当前覆盖个人资料、默认语言、AI 回答深度、证据展示偏好、待确认、执行回写、发布门禁和失败提醒通知偏好，移动端使用分组列表与 bottom sheet，账户退出仍复用 `AccountControls.tsx`，不改 OAuth/JWT/auth core；P1 后端合同提供 `GET /account-settings/me` 与 `PUT /account-settings/me`，已由 `backend/app/api/router.py` 挂入核心路由组，按当前 `tenant_id + user_id` 保存账号偏好，前端有 token 时优先账号同步，后端不可用时明确回落 `仅本机暂存 / 保存失败`；P2 在 `frontend/src/api/accountSettings.ts` 提供 `shouldShowAccountNotification` 与 `getAccountNotificationConsumption`，把通知偏好映射为页面内提醒消费模型；P3 新增 `getReleaseGateNotificationPreference(settings, event)` 供 Release/Growth 后续消费：`release_gate_*` 与 `release_validation_*` 使用 `releaseGate` 偏好，`failed_event` 使用 `failureAlert` 偏好，返回 `inAppEnabled / desktopPreference / emailDigestPreference`；这些 helper 只控制本地 UI 提醒消费合同，不代表真实邮件、桌面推送或系统通知中心已接入
 - PMFlow OS 共享 truth store 与主链状态动作：参考 `frontend/src/features/pmflow-os/store.tsx`；当前支持 `?projectId=<id>` 走 React Query 读取真实 `truth-state` 与 `execution-summary`，真实模式下 thread message、`proposed_items` extraction、ChangeItem `accept/edit/defer`、ChangeSet commit、Execution Handoff create/consume、execution progress writeback 均调后端并 refetch，不本地 promote 入 Project Memory 或伪造 execution event；`?demo=1` 才启用本地 mock 演示状态机和本地动作；项目内 AI 结构化闭环状态机为 `command_idle / ai_extracting / extraction_ready / review_open / writeback_success`
 - PMFlow OS 产品页入口：参考 `frontend/src/features/pmflow-os/pages/CommandCenterPage.tsx`、`StructuredExtractionPage.tsx`、`ChangeReviewPage.tsx`、`MemoryWritebackResultPage.tsx`、`WorkGraphPage.tsx`、`ExecutionBridgePage.tsx`、`ReleaseGrowthPage.tsx`、`TeamLayerPage.tsx`、`ProjectMemoryPage.tsx`、`AccountPage.tsx`；`ReleaseGrowthPage.tsx` 真实模式只展示 `execution-summary.releaseGate`、execution evidence、阻塞原因和下一步动作，缺证据时显示 empty/warning，不展示 mock 发布结果，静态高保真发布/增长数据仅保留在显式 demo 模式
 - PMFlow OS 行为组件：参考 `frontend/src/features/pmflow-os/components/ProjectStructuredLoop.tsx`、`ProjectStageRail.tsx`、`ThreadComposer.tsx`、`ExtractionRail.tsx`、`ChangeGroupPanel.tsx`、`ObjectGraphSection.tsx`、`ContextPacketPanel.tsx`、`ExecutionTimeline.tsx`、`ReleaseGatePanel.tsx`、`TeamFeedPanel.tsx`、`ChangeReviewGroup.tsx`、`WorkbenchPanel.tsx`、`ExecutionBridgeCards.tsx`、`PMFlowOsFrame.tsx`、`AccountControls.tsx`、`FeedbackPrimitives.tsx`、`MobileBottomNav.tsx`；其中 `ProjectStructuredLoop.tsx` 承接 `StatusLabel / EvidenceSnippet / ObjectChangeCard / ProjectConversationPanel / StructuredExtractionPanel / ProjectAICopilotPanel`，`PMFlowOsFrame.tsx` 承接项目内面包屑和项目切换器，`AccountControls.tsx` 承接桌面头像菜单、退出登录确认与移动端 bottom sheet，`FeedbackPrimitives.tsx` 承接 `PageBanner / InlineNotice / HumanDecisionBar / ConfirmDialog / MobileBottomSheet`，`MobileBottomNav.tsx` 承接正式应用壳移动端固定底部导航
 - PMFlow OS 原型状态回归测试：参考 `frontend/src/features/pmflow-os/store.test.ts`；真实 API 动作回归参考 `frontend/src/features/pmflow-os/store.api.test.tsx`
 - Project Launch 真实/演示分支回归测试：参考 `frontend/src/features/project-launch/useProjectLaunchState.test.ts`
-- Account Settings 前端合同回归测试：参考 `frontend/src/features/account-settings/accountSettings.test.ts`，覆盖默认偏好、账号同步 fallback、通知偏好消费模型和缺字段 fallback。
+- Account Settings 前端合同回归测试：参考 `frontend/src/features/account-settings/accountSettings.test.ts`，覆盖默认偏好、账号同步 fallback、通知偏好消费模型、Release/Growth 通知消费合同、失败事件映射和缺字段 fallback。
 - 网页问答显式锚点与 AI Steward URL 构造：参考 `frontend/src/components/ai-steward/qaPageAnchor.ts`
 - Inbox 页面入口：参考 `frontend/src/pages/inbox/`
 - Inbox `plan_mode` 展开卡片与映射：参考 `frontend/src/components/inbox/InboxListItem.tsx`、`frontend/src/lib/inbox.ts`、`frontend/src/api/aiPmo.ts`

frontend/src/api/accountSettings.ts

@@ -6,6 +6,12 @@ export type AccountAnswerDepth = "concise" | "balanced" | "deep";
 export type AccountEvidenceDisplay = "summary" | "inline" | "full";
 export type AccountNotificationKey = "pendingConfirmation" | "executionWriteback" | "releaseGate" | "failureAlert";
 export type AccountSettingsSaveScope = "local" | "account";
+export type AccountReleaseNotificationEvent =
+  | "release_gate_blocked"
+  | "release_gate_ready"
+  | "release_validation_blocked"
+  | "release_validation_needs_confirmation"
+  | "failed_event";
 
 export interface AccountProfileSettings {
   displayName: string;
@@ -42,6 +48,17 @@ export interface AccountNotificationConsumption {
   detail: string;
 }
 
+export interface AccountReleaseGateNotificationPreference {
+  event: AccountReleaseNotificationEvent;
+  notificationKey: AccountNotificationKey;
+  surface: "release_growth" | "system_failure";
+  inAppEnabled: boolean;
+  desktopPreference: boolean;
+  emailDigestPreference: boolean;
+  title: string;
+  reason: string;
+}
+
 export interface AccountSettings {
   profile: AccountProfileSettings;
   aiPreferences: AccountAiPreferenceSettings;
@@ -117,6 +134,37 @@ const accountNotificationConsumptionMeta: Record<
   },
 };
 
+const releaseNotificationEventMeta: Record<
+  AccountReleaseNotificationEvent,
+  { notificationKey: AccountNotificationKey; surface: "release_growth" | "system_failure"; reason: string }
+> = {
+  release_gate_blocked: {
+    notificationKey: "releaseGate",
+    surface: "release_growth",
+    reason: "Release/Growth 发布门禁阻塞、缺少证据或需要人工处理时使用发布门禁偏好。",
+  },
+  release_gate_ready: {
+    notificationKey: "releaseGate",
+    surface: "release_growth",
+    reason: "Release/Growth 形成可发布候选或需要人工确认时使用发布门禁偏好。",
+  },
+  release_validation_blocked: {
+    notificationKey: "releaseGate",
+    surface: "release_growth",
+    reason: "真实发布验证记录存在未通过检查项时使用发布门禁偏好。",
+  },
+  release_validation_needs_confirmation: {
+    notificationKey: "releaseGate",
+    surface: "release_growth",
+    reason: "真实发布验证记录已生成、需要人工确认时使用发布门禁偏好。",
+  },
+  failed_event: {
+    notificationKey: "failureAlert",
+    surface: "system_failure",
+    reason: "Release/Growth 捕获 failed event、验证运行失败或执行链路失败时使用失败提醒偏好。",
+  },
+};
+
 export function createDefaultAccountSettings(seed: AccountSettingsSeed = {}): AccountSettings {
   return {
     profile: {
@@ -235,6 +283,26 @@ export function getAccountNotificationConsumption(
   });
 }
 
+export function getReleaseGateNotificationPreference(
+  settings: AccountSettings | Partial<AccountSettings> | null | undefined,
+  event: AccountReleaseNotificationEvent = "release_gate_blocked"
+): AccountReleaseGateNotificationPreference {
+  const normalized = mergeAccountSettings(createDefaultAccountSettings(), settings || null);
+  const meta = releaseNotificationEventMeta[event];
+  const preference = normalized.notifications[meta.notificationKey];
+  const enabled = Boolean(preference.enabled);
+  return {
+    event,
+    notificationKey: meta.notificationKey,
+    surface: meta.surface,
+    inAppEnabled: enabled,
+    desktopPreference: enabled && Boolean(preference.desktop),
+    emailDigestPreference: enabled && Boolean(preference.emailDigest),
+    title: accountNotificationLabels[meta.notificationKey].title,
+    reason: meta.reason,
+  };
+}
+
 export async function getAccountSettings(seed?: AccountSettingsSeed): Promise<AccountSettings> {
   const defaults = createDefaultAccountSettings(seed);
   const localSettings = mergeAccountSettings(defaults, readStoredAccountSettings());

frontend/src/features/account-settings/accountSettings.test.ts

@@ -3,6 +3,7 @@ import {
   createDefaultAccountSettings,
   getAccountNotificationConsumption,
   getAccountSettings,
+  getReleaseGateNotificationPreference,
   shouldShowAccountNotification,
   updateAccountSettings,
 } from "@/api/accountSettings";
@@ -87,6 +88,50 @@ describe("account settings api", () => {
     expect(release?.emailDigestPreference).toBe(true);
   });
 
+  it("maps release gate and release validation events to the releaseGate preference", () => {
+    const defaults = createDefaultAccountSettings();
+    const settings = {
+      ...defaults,
+      notifications: {
+        ...defaults.notifications,
+        releaseGate: { enabled: true, desktop: false, emailDigest: true },
+      },
+    };
+
+    const blockedGate = getReleaseGateNotificationPreference(settings, "release_gate_blocked");
+    const validation = getReleaseGateNotificationPreference(settings, "release_validation_needs_confirmation");
+
+    expect(blockedGate.notificationKey).toBe("releaseGate");
+    expect(blockedGate.surface).toBe("release_growth");
+    expect(blockedGate.inAppEnabled).toBe(true);
+    expect(blockedGate.desktopPreference).toBe(false);
+    expect(blockedGate.emailDigestPreference).toBe(true);
+    expect(blockedGate.reason).toContain("发布门禁");
+    expect(validation.notificationKey).toBe("releaseGate");
+    expect(validation.inAppEnabled).toBe(true);
+    expect(validation.reason).toContain("发布验证");
+  });
+
+  it("maps release failed events to failureAlert without enabling disabled channels", () => {
+    const defaults = createDefaultAccountSettings();
+    const settings = {
+      ...defaults,
+      notifications: {
+        ...defaults.notifications,
+        failureAlert: { enabled: false, desktop: true, emailDigest: true },
+      },
+    };
+
+    const failedEvent = getReleaseGateNotificationPreference(settings, "failed_event");
+
+    expect(failedEvent.notificationKey).toBe("failureAlert");
+    expect(failedEvent.surface).toBe("system_failure");
+    expect(failedEvent.inAppEnabled).toBe(false);
+    expect(failedEvent.desktopPreference).toBe(false);
+    expect(failedEvent.emailDigestPreference).toBe(false);
+    expect(failedEvent.reason).toContain("failed event");
+  });
+
   it("falls back missing notification fields to safe defaults", async () => {
     window.localStorage.setItem(
       "pmflow:account-settings:v1",