吸收数字员工管理端记忆技能审计预览
This commit is contained in:
baiyanyun
@@ -1449,6 +1449,102 @@ function checkDigitalAdminApprovalGovernanceWorkbench() {
|
||||
console.log("[DigitalEmployeeCheck] admin approval governance workbench hooks OK");
|
||||
}
|
||||
|
||||
function checkDigitalAdminMemorySkillWorkbench() {
|
||||
console.log("\n[DigitalEmployeeCheck] Verify admin memory governance and skill audit workbench hooks");
|
||||
const backendRoot = path.resolve(packageRoot, "..", "..", "..", "qiming-backend");
|
||||
const qimingRoot = path.resolve(packageRoot, "..", "..", "..", "qiming");
|
||||
const servicePath = 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 dtoPath = path.join(
|
||||
backendRoot,
|
||||
"app-platform-modules",
|
||||
"app-platform-agent",
|
||||
"app-platform-agent-core-adapter",
|
||||
"src",
|
||||
"main",
|
||||
"java",
|
||||
"com",
|
||||
"xspaceagi",
|
||||
"agent",
|
||||
"core",
|
||||
"adapter",
|
||||
"dto",
|
||||
"digital",
|
||||
"DigitalEmployeeAdminWorkbenchRowDto.java",
|
||||
);
|
||||
const testPath = 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 qimingOpsPath = path.join(qimingRoot, "src", "pages", "SystemManagement", "Content", "DigitalEmployeeOps", "index.tsx");
|
||||
const qimingTypesPath = path.join(qimingRoot, "src", "types", "interfaces", "systemManage.ts");
|
||||
const docsPath = path.resolve(packageRoot, "..", "..", "docs", "digital-employee-frontend-integration-plan.md");
|
||||
const service = fs.readFileSync(servicePath, "utf8");
|
||||
const dto = fs.readFileSync(dtoPath, "utf8");
|
||||
const test = fs.readFileSync(testPath, "utf8");
|
||||
const qimingOps = fs.readFileSync(qimingOpsPath, "utf8");
|
||||
const qimingTypes = fs.readFileSync(qimingTypesPath, "utf8");
|
||||
const docs = fs.readFileSync(docsPath, "utf8");
|
||||
const requiredSnippets = [
|
||||
[service, "memory_governance", "backend memory governance view"],
|
||||
[service, "skill_audits", "backend skill audits view"],
|
||||
[service, "isMemoryGovernanceRow", "backend memory governance matcher"],
|
||||
[service, "isSkillAuditRow", "backend skill audit matcher"],
|
||||
[service, "skill_call_", "backend skill call classifier"],
|
||||
[service, "tool_call_audit", "backend tool audit classifier"],
|
||||
[service, "token_cost", "backend token cost classifier"],
|
||||
[dto, "memory_id", "backend memory id row field"],
|
||||
[dto, "memory_key", "backend memory key row field"],
|
||||
[dto, "skill_id", "backend skill id row field"],
|
||||
[dto, "tool_name", "backend tool name row field"],
|
||||
[dto, "server_id", "backend server id row field"],
|
||||
[test, "queryAdminWorkbenchMemoryGovernanceReturnsMemoryRowsOnly", "backend memory governance test"],
|
||||
[test, "queryAdminWorkbenchSkillAuditsReturnsSkillAndToolAuditRowsOnly", "backend skill audits test"],
|
||||
[qimingTypes, "memory_governance", "qiming memory governance view type"],
|
||||
[qimingTypes, "skill_audits", "qiming skill audits view type"],
|
||||
[qimingOps, "记忆治理", "qiming memory governance tab"],
|
||||
[qimingOps, "技能审计", "qiming skill audits tab"],
|
||||
[qimingOps, "批量归档", "qiming memory archive action"],
|
||||
[qimingOps, "批量恢复", "qiming memory restore action"],
|
||||
[qimingOps, "重复候选", "qiming memory duplicate copy"],
|
||||
[docs, "正式管理端记忆治理预览", "docs memory governance absorption"],
|
||||
[docs, "正式管理端技能审计预览", "docs skill audit absorption"],
|
||||
];
|
||||
const missing = requiredSnippets
|
||||
.filter(([content, snippet]) => !content.includes(snippet))
|
||||
.map(([, , label]) => label);
|
||||
if (missing.length > 0) {
|
||||
throw new Error(`Missing admin memory governance and skill audit hooks: ${missing.join(", ")}`);
|
||||
}
|
||||
console.log("[DigitalEmployeeCheck] admin memory governance and skill audit hooks OK");
|
||||
}
|
||||
|
||||
function checkDigitalAdminServiceOperationsWorkbench() {
|
||||
console.log("\n[DigitalEmployeeCheck] Verify admin service operations workbench hooks");
|
||||
const backendRoot = path.resolve(packageRoot, "..", "..", "..", "qiming-backend");
|
||||
@@ -2053,6 +2149,7 @@ function main() {
|
||||
checkDigitalBackendMaterializedFacts();
|
||||
checkDigitalAdminRecordBillingArchiveShell();
|
||||
checkDigitalAdminApprovalGovernanceWorkbench();
|
||||
checkDigitalAdminMemorySkillWorkbench();
|
||||
checkDigitalAdminServiceOperationsWorkbench();
|
||||
checkDigitalAdminRouteGovernanceWorkbench();
|
||||
checkDigitalAdminNotificationWorkbench();
|
||||
|
||||
@@ -562,8 +562,8 @@ GET /api/digital-employee/approvals
|
||||
|
||||
3. **MemoryEntry / 长期记忆（已开始）**
|
||||
- 已吸收：qimingclaw `memoryService` 已投射为数字员工本地 `digital_memories`，支持从主客户端记忆列表同步、桥接新增和软删除；本地兜底记忆仍可在 memory 服务未初始化时工作。
|
||||
- 当前能力：embedded `/api/memory` 已由 qimingclaw adapter 接管，GET / POST / DELETE 会通过 preload bridge 读写 `digital_memories`；记忆新增、更新和删除会进入 `digital_sync_outbox`，entity type 为 `memory`，同步业务视图会提炼 key、category、source、status 和 content preview。记忆归档/恢复 UI、管理端长期记忆业务视图和记忆治理审计链已开始吸收，embedded 新增“记忆治理”入口，可从 runtime memories 派生 key/category/source/status/content preview、重复候选和同步状态，并通过本地 overlay/audit 批量归档、恢复或标记复核。
|
||||
- 后续缺口：真实合并执行、远端记忆策略下发和外部管理端长期记忆工作台仍待吸收。
|
||||
- 当前能力：embedded `/api/memory` 已由 qimingclaw adapter 接管，GET / POST / DELETE 会通过 preload bridge 读写 `digital_memories`；记忆新增、更新和删除会进入 `digital_sync_outbox`，entity type 为 `memory`，同步业务视图会提炼 key、category、source、status 和 content preview。记忆归档/恢复 UI、管理端长期记忆业务视图和记忆治理审计链已开始吸收，embedded 新增“记忆治理”入口，可从 runtime memories 派生 key/category/source/status/content preview、重复候选和同步状态，并通过本地 overlay/audit 批量归档、恢复或标记复核。正式管理端记忆治理预览已开始吸收，qiming-backend 新增 `memory_governance` 运营台视图聚合 memory fact、归档/恢复/复核事件和重复候选摘要，qiming“数字员工运营台”的“记忆治理”tab 可记录批量归档、批量恢复和标记复核等低风险动作意图。
|
||||
- 后续缺口：真实合并执行、远端记忆策略下发和更完整的外部管理端长期记忆策略工作台仍待吸收。
|
||||
- 建议：下一轮围绕管理端视图和记忆治理，把长期记忆从本地事实继续扩展到人工可审计、可归档、可合并的运营闭环。
|
||||
|
||||
4. **治理命令完整生命周期**
|
||||
@@ -578,8 +578,8 @@ GET /api/digital-employee/approvals
|
||||
- 建议：先沉淀安全重启审计和人工确认体验，再评估更细粒度的服务恢复策略。
|
||||
|
||||
6. **技能生命周期与策略**
|
||||
- 已吸收：ACP / MCP / GUI / file server 能力已投射到 Skill Catalog，技能库不再使用 demo fallback；Skill Library 启用/禁用已写入 qimingclaw 本地 `digital_employee_skill_policies_v1.local_skills`，管理端下发策略写入 `remote_skills`，远端禁用优先生效且不会被本地按钮覆盖；入口路由候选技能会按有效策略过滤；MCP 注入 Agent 前会应用有效技能策略，ACP permission / tool update 会写入 `skill_call_allowed` / `skill_call_rejected` / `skill_call_observed` 审计事件，`policy_snapshot` 会包含本地/远端策略命中字段；embedded 已提供 `/api/digital-employee/skill-call-audits` 只读投影、`POST /api/skill/policies/pull` 手动拉取入口，技能调用策略与审计已开始闭环。管理端调用审计视图已开始吸收，embedded 新增“技能审计”入口，将 skill call audit、tool_call_audit、sandbox_audit 和 token_cost 统一成可筛选列表，技能库可按 skill id 跳转聚焦。
|
||||
- 缺口：仍缺少技能安装、版本管理、细粒度权限范围和正式外部管理端调用审计工作台。
|
||||
- 已吸收：ACP / MCP / GUI / file server 能力已投射到 Skill Catalog，技能库不再使用 demo fallback；Skill Library 启用/禁用已写入 qimingclaw 本地 `digital_employee_skill_policies_v1.local_skills`，管理端下发策略写入 `remote_skills`，远端禁用优先生效且不会被本地按钮覆盖；入口路由候选技能会按有效策略过滤；MCP 注入 Agent 前会应用有效技能策略，ACP permission / tool update 会写入 `skill_call_allowed` / `skill_call_rejected` / `skill_call_observed` 审计事件，`policy_snapshot` 会包含本地/远端策略命中字段；embedded 已提供 `/api/digital-employee/skill-call-audits` 只读投影、`POST /api/skill/policies/pull` 手动拉取入口，技能调用策略与审计已开始闭环。管理端调用审计视图已开始吸收，embedded 新增“技能审计”入口，将 skill call audit、tool_call_audit、sandbox_audit 和 token_cost 统一成可筛选列表，技能库可按 skill id 跳转聚焦。正式管理端技能审计预览已开始吸收，qiming-backend 新增 `skill_audits` 运营台视图聚合 skill call、tool、sandbox 和 token/cost 安全摘要，qiming“数字员工运营台”的“技能审计”tab 只开放标记复核和忽略意图，不安装技能、不变更权限范围。
|
||||
- 缺口：仍缺少技能安装、版本管理和细粒度权限范围。
|
||||
- 建议：下一轮围绕管理端审计消费、技能安装和权限范围，把本地调用审计推进到更完整的跨端治理闭环。
|
||||
|
||||
7. **产物交付闭环**
|
||||
|
||||
Reference in New Issue
Block a user