吸收数字员工跨设备路由干预冲突预览

qimingclaw/crates/agent-electron-client/scripts/check-digital-employee.js

@@ -1191,6 +1191,55 @@ function checkDigitalAdminPolicySnapshots() {
   const qimingOpsPath = path.join(qimingRoot, "src", "pages", "SystemManagement", "Content", "DigitalEmployeeOps", "index.tsx");
   const qimingServicePath = path.join(qimingRoot, "src", "services", "systemManage.ts");
   const qimingTypesPath = path.join(qimingRoot, "src", "types", "interfaces", "systemManage.ts");
+  const backendServicePath = path.join(
+    backendRoot,
+    "app-platform-modules",
+    "app-platform-agent",
+    "app-platform-agent-core-application",
+    "src",
+    "main",
+    "java",
+    "com",
+    "xspaceagi",
+    "agent",
+    "core",
+    "application",
+    "service",
+    "DigitalEmployeeSyncApplicationServiceImpl.java",
+  );
+  const backendDtoPath = path.join(
+    backendRoot,
+    "app-platform-modules",
+    "app-platform-agent",
+    "app-platform-agent-core-adapter",
+    "src",
+    "main",
+    "java",
+    "com",
+    "xspaceagi",
+    "agent",
+    "core",
+    "adapter",
+    "dto",
+    "digital",
+    "DigitalEmployeePolicySnapshotRowDto.java",
+  );
+  const backendTestPath = path.join(
+    backendRoot,
+    "app-platform-modules",
+    "app-platform-agent",
+    "app-platform-agent-core-application",
+    "src",
+    "test",
+    "java",
+    "com",
+    "xspaceagi",
+    "agent",
+    "core",
+    "application",
+    "service",
+    "DigitalEmployeeSyncApplicationServiceImplTest.java",
+  );
   const backendControllerPath = path.join(
     backendRoot,
     "app-platform-modules",
@@ -1213,6 +1262,9 @@ function checkDigitalAdminPolicySnapshots() {
   const qimingOps = fs.readFileSync(qimingOpsPath, "utf8");
   const qimingService = fs.readFileSync(qimingServicePath, "utf8");
   const qimingTypes = fs.readFileSync(qimingTypesPath, "utf8");
+  const backendService = fs.readFileSync(backendServicePath, "utf8");
+  const backendDto = fs.readFileSync(backendDtoPath, "utf8");
+  const backendTest = fs.readFileSync(backendTestPath, "utf8");
   const backendController = fs.readFileSync(backendControllerPath, "utf8");
   const requiredSnippets = [
     [syncService, "policySnapshotBusinessView", "client policy snapshot business view"],
@@ -1224,13 +1276,24 @@ function checkDigitalAdminPolicySnapshots() {
     [syncTest, "event-route-policy-pull", "route policy snapshot sync test"],
     [syncTest, "event-risk-policy-pull", "risk policy snapshot sync test"],
     [backendController, "/snapshots", "backend policy snapshot endpoint"],
+    [backendService, "routeInterventionConflictStatus", "backend route intervention conflict aggregation"],
+    [backendService, "route_intervention_state", "backend route intervention conflict key"],
+    [backendDto, "intervention_conflict_status", "backend route intervention conflict status field"],
+    [backendDto, "route_decision_count", "backend route decision count field"],
+    [backendTest, "queryAdminPolicySnapshotsSummarizesRouteInterventionConflicts", "backend route intervention conflict test"],
     [qimingService, "apiDigitalEmployeeAdminPolicySnapshots", "qiming policy snapshot service"],
     [qimingService, "/api/digital-employee/admin/policies/snapshots", "qiming policy snapshot endpoint"],
     [qimingTypes, "DigitalEmployeePolicySnapshotRow", "qiming policy snapshot row type"],
     [qimingTypes, "policy_conflicts", "qiming policy conflicts view type"],
+    [qimingTypes, "intervention_conflict_status", "qiming route intervention conflict type field"],
     [qimingOps, "策略冲突", "qiming policy conflict tab text"],
     [qimingOps, "conflict_keys", "qiming conflict key display"],
+    [qimingOps, "跨设备路由干预冲突", "qiming route intervention conflict copy"],
+    [qimingOps, "不恢复执行", "qiming route recovery guard copy"],
+    [qimingOps, "不绕过审批", "qiming approval guard copy"],
+    [qimingOps, "不远程改策略", "qiming remote policy edit guard copy"],
     [docs, "跨设备策略冲突视图", "docs policy conflict absorption"],
+    [docs, "跨设备路由干预冲突可视化", "docs route intervention conflict absorption"],
   ];
   const missing = requiredSnippets
     .filter(([content, snippet]) => !content.includes(snippet))

qimingclaw/docs/digital-employee-frontend-integration-plan.md

@@ -599,8 +599,8 @@ GET /api/digital-employee/approvals
 
 10. **入口路由 / 任务分流（路由业务视图与通知联动已开始）**
     - 已吸收：管理端通过 `/computer/chat` 进入 qimingclaw 后会生成本地任务事实；embedded `/api/ingress/route`、`/api/route-decisions` 和 `/api/digital-employee/route-decisions` 已由 qimingclaw adapter 接管。
-    - 当前能力：入口请求会按上下文、ready PlanStep、调度、查询和控制动作生成 route decision，并写入 `digital_events.kind = route_decision` 与现有 event outbox；路由时间线优先从 qimingclaw 本地事件读取；低风险 route decision 已开始映射为明确的本地 governance command，并把 `created_command_id` 回填到 route decision；自动映射前会执行低风险/受保护高风险 action guard，未允许的控制动作会记录 `route_action_policy_blocked` 或 `route_action_missing_context`，避免静默创建命令；入口路由策略可从管理端远端下发，支持按 intent 阻断、按 intent 要求审批、限制自动创建 governance command，并在策略干预时先记录 route decision 再停止本地命令执行；首页已展示路由干预队列和治理审计摘要，审批通过/拒绝会写入本地 approval decision 并回写管理端，管理端审批更新拉取后会自动扫描已批准 route approval 并按幂等规则恢复执行；scheduler check 已接入 ready PlanStep 安全派发，首页立即执行后会触发一次派发 sweep 并展示派发结果；路由决策本地业务视图、首页摘要、治理审计、策略来源/拉取错误、阻断/待审/待干预/已恢复计数和通知联动已开始闭环。管理端正式路由 UI 预览已开始吸收，“策略中心”会把入口路由策略纳入统一拉取与状态展示。正式管理端策略中心预览已开始吸收，qiming 运营台可从 `policy_center` 查看入口路由策略快照和拉取状态。正式管理端路由治理预览已开始吸收，qiming-backend 的 `route_governance` 运营台视图会聚合 route blocked / approval required / missing context / not mapped / governance audit，qiming“数字员工运营台”的“路由治理”tab 只开放标记已看、忽略和重试策略检查等低风险动作意图。
-    - 后续缺口：路由策略编辑、跨设备路由干预冲突可视化和高风险恢复执行策略 UI 仍待吸收。
+    - 当前能力：入口请求会按上下文、ready PlanStep、调度、查询和控制动作生成 route decision，并写入 `digital_events.kind = route_decision` 与现有 event outbox；路由时间线优先从 qimingclaw 本地事件读取；低风险 route decision 已开始映射为明确的本地 governance command，并把 `created_command_id` 回填到 route decision；自动映射前会执行低风险/受保护高风险 action guard，未允许的控制动作会记录 `route_action_policy_blocked` 或 `route_action_missing_context`，避免静默创建命令；入口路由策略可从管理端远端下发，支持按 intent 阻断、按 intent 要求审批、限制自动创建 governance command，并在策略干预时先记录 route decision 再停止本地命令执行；首页已展示路由干预队列和治理审计摘要，审批通过/拒绝会写入本地 approval decision 并回写管理端，管理端审批更新拉取后会自动扫描已批准 route approval 并按幂等规则恢复执行；scheduler check 已接入 ready PlanStep 安全派发，首页立即执行后会触发一次派发 sweep 并展示派发结果；路由决策本地业务视图、首页摘要、治理审计、策略来源/拉取错误、阻断/待审/待干预/已恢复计数和通知联动已开始闭环。管理端正式路由 UI 预览已开始吸收，“策略中心”会把入口路由策略纳入统一拉取与状态展示。正式管理端策略中心预览已开始吸收，qiming 运营台可从 `policy_center` 查看入口路由策略快照和拉取状态。正式管理端路由治理预览已开始吸收，qiming-backend 的 `route_governance` 运营台视图会聚合 route blocked / approval required / missing context / not mapped / governance audit，qiming“数字员工运营台”的“路由治理”tab 只开放标记已看、忽略和重试策略检查等低风险动作意图。跨设备路由干预冲突可视化已开始吸收，qiming-backend 的策略快照读模型会把 route blocked / approval required / missing context / not mapped 汇总为 `intervention_conflict_status` 和干预计数，qiming“策略冲突”tab 可展示跨设备路由干预冲突，但不恢复执行、不绕过审批、不远程改策略。
+    - 后续缺口：路由策略编辑和高风险恢复执行策略 UI 仍待吸收。
     - 建议：下一轮围绕管理端正式路由 UI 和跨设备冲突可视化，把 embedded 批量干预入口推进到管理端运营台。
 
 11. **诊断 / 成本 / 审计视图**