Close P19 multi-channel alert routing
This commit is contained in:
@@ -408,6 +408,7 @@ candidate -> decision alert -> dispatcher -> 外部消息 -> delivery record
|
||||
- 2026-05-12 P16 已完成 `browser screenshot capture adapter` 本地闭环:visual snapshot capture 现在在保留 HTML/JSON artifact 的同时,可通过本机 Edge/Chrome headless 生成 PNG screenshot,并把 browser capture status、HTML path、screenshot path 接入脚本、API 与 workbench Visual Reviews。
|
||||
- 2026-05-12 P17 已完成 `visual trigger ROI router` 本地闭环:视觉触发策略现在区分 `triggered` / `skipped`,普通 observe/monitoring 状态不触发视觉复核,actionable、blocked、market degraded、broker/reconciliation degraded 与 council watch item 会输出可审计 trigger type / reason codes,并在 runtime、alert quality summary、脚本和 workbench 中暴露 trigger/skip/ROI 计数。
|
||||
- 2026-05-12 P18 已完成 `visual evidence media dispatch` 本地闭环:visual review 现在会生成稳定 `media_evidence` block,外部文本通道不支持文件时降级为 `media_linked`,workbench 可消费本地截图路径时标记 `media_attached`,无视觉证据时标记 `media_unavailable`;dispatcher、delivery summary、runtime、脚本和 workbench 均可见媒体证据状态。
|
||||
- 2026-05-12 P19 已完成 `multi-channel alert routing` 本地闭环:channel router 现在输出 workbench/webhook/WeCom/Email capability 与 health summary,WeCom/Email 在凭据缺失或 adapter 未实现时会以 disabled adapter 形式返回 `credential_missing` / `adapter_not_implemented`,dispatcher、delivery summary、runtime、脚本和 workbench 均可见 per-channel 状态。
|
||||
|
||||
### 验收
|
||||
- 非重大错误不打断主循环
|
||||
|
||||
@@ -107,6 +107,8 @@
|
||||
- `candidate_blocked` -> dashboard only
|
||||
- `runtime_degraded` -> Telegram + dashboard
|
||||
|
||||
2026-05-12 P19 已落地:当前 channel router 保持现有 workbench/webhook 行为,同时输出结构化 `channel_route`、channel capability 与 channel health summary。WeCom / Email 已预留为 disabled adapter;凭据缺失时暴露 `credential_missing`,凭据存在但 adapter 未实现时暴露 `adapter_not_implemented`,不会把未配置通道伪装为成功发送。dispatcher、delivery summary、runtime 与 workbench 均可查看 per-channel 状态。
|
||||
|
||||
#### `src/services/alerts/delivery_policy_service.py`
|
||||
职责:
|
||||
|
||||
|
||||
@@ -189,6 +189,13 @@
|
||||
- 凭据缺失时显示 `channel_disabled` 或 `credential_missing`,不伪装成功。
|
||||
- 现有 webhook/workbench 行为不回归。
|
||||
|
||||
### 当前进展
|
||||
|
||||
- 2026-05-12 P19 已完成 `Multi-Channel Alert Routing` 本地闭环:`ChannelRouterService` 现在输出结构化 `channel_route`、channel capability 与 channel health summary,覆盖 workbench、webhook、WeCom、Email。
|
||||
- 2026-05-12 P19 已将 WeCom/Email 预留为 disabled adapter:凭据缺失时显示 `credential_missing`,即使未来填入凭据但 adapter 未实现也会保持 `adapter_not_implemented`,不会伪装成成功发送。
|
||||
- 2026-05-12 P19 已在 dispatcher result、delivery payload、delivery summary、runtime `alert_dispatch` details、`run_alert_dispatcher.py` 与 workbench `Alert Quality` 中暴露 per-channel status、channel disabled count 与 channel health。
|
||||
- 2026-05-12 P19 本地闭环已验证:focused P19 tests 通过,`tests/unit` 全量 679 个测试通过,script static checks 与 `node --check src/web/app.js` 通过;dispatcher smoke 在无 pending alert 时安全 no-op 且 channel health 可见,quality-summary API 与 runtime smoke 均可见 channel counts/health 且 runtime blockers=none。
|
||||
|
||||
---
|
||||
|
||||
## 10. P20 Operator Digest And Review Queue
|
||||
|
||||
Reference in New Issue
Block a user