feat(wecom): 数字员工与企业设置页新增批量删除工具功能，修复企微 Webhook 配置，企业微信多账号支持与智能机器人短链接修复。

[ThomasOscar]

任务概览

功能一：智能体工具的批量删除

• 涉及位置：
  • 数字员工详情页 → 工具 → 已安装工具栏
  • 企业设置 → 工具 → 智能体安装板块
• 新特性：
  • 支持批量勾选工具（复选框）
  • 后端接口支持批量删除 (DELETE /api/tools/agent-tools/bulk)
  • 增加二次确认弹窗
  • 权限校验（仅限管理员/超级管理员）
  • 租户隔离检查（确保数据安全）
  • 支持处理部分删除失败的机制
  • 记录操作日志

功能二：企业微信 Webhook 配置修复

• 遇到的问题：
  • 配置了 Webhook 模式后，界面仍然显示 WebSocket 状态。
  • Webhook 的 URL 无法正确显示。
• 解决方案：
  • 后端：优先处理前端指定的 connection_mode（连接模式）。
  • 后端：增加了消息发送的日志记录。
  • 前端：正确显示 Webhook 模式的状态。
  • 前端：优化了 API 请求失败时的处理逻辑。

企业微信多账号支持，支持三种通信模式新增功能

• 企业微信多账号支持，支持三种通信模式：
  • 智能机器人-长连接 (WebSocket)
  • 智能机器人-短链接 (Webhook)
  • 企业应用 (Webhook)
• 新增 WeComAccountManager 组件管理多账号
• 短链接模式添加测试按钮，可在保存前生成Webhook URL

Bug修复

• 修复智能机器人-短链接URL验证失败问题（HTTP 403）
  • 添加URL参数解码处理
  • 修复签名验证逻辑
• 修复消息回复方式，改用 response_url 主动回复（markdown格式）
• 修复消息格式解析，支持JSON和XML双格式

UI改进

• 删除按钮改用 ConfirmModal 组件替代原生alert/confirm弹窗
• 隐藏旧版配置UI（配置说明、Edit/Disconnect按钮），统一使用新组件
• 所有模式保存后统一关闭弹窗

i18n

• 添加中英文翻译键 wecomMultiAccount

文件变更：数字员工与企业设置页新增批量删除工具功能

• backend/app/api/tools.py - 实现批量删除接口
• frontend/src/pages/AgentDetail.tsx - 数字员工页面的批量删除 UI
• frontend/src/pages/EnterpriseSettings.tsx - 企业设置页面的批量删除 UI
• frontend/src/i18n/zh.json - 中文翻译文案
• backend/app/api/wecom.py - 优化连接模式的优先级逻辑
• frontend/src/components/ChannelConfig.tsx - Webhook 状态显示组件

文件变更：企业微信多账号支持，支持三种通信模式

• backend/app/api/wecom.py - URL验证、消息处理、签名验证
• backend/app/services/wecom_stream.py - 多账号WebSocket支持
• frontend/src/components/WeComAccountManager.tsx - 新增多账号管理组件
• frontend/src/components/ChannelConfig.tsx - 集成新组件
• frontend/src/pages/AgentCreate.tsx - 创建页面集成
• frontend/src/i18n/zh.json - 中文翻译
• frontend/src/i18n/en.json - 英文翻译

智能体工具批量删除测试

• 进入数字员工详情页或企业设置页。
• 勾选多个智能体工具。
• 点击“批量删除”按钮。
• 在弹窗中确认删除。
• 验证工具是否被成功删除。

企业微信多账号支持，支持三种通信模式测试

• 智能机器人-长连接 正常工作
• 智能机器人-短链接 URL验证和消息收发正常
• 企业应用 正常工作

[wisdomqin]

Thanks for the PR! The WeCom webhook fix looks good, but the bulk delete feature has several issues that need to be resolved before we can merge.

Required Fixes

1. Wrong role names — bulk delete endpoint returns 403 for all valid admins

The permission check uses role names that don't exist in our system:

# Current (broken) — these roles don't exist
if current_user.role not in ("admin", "super_admin"):
    ...
if current_user.role != "super_admin" and ...:
    ...

Our platform uses org_admin and platform_admin. Please update both checks:

if current_user.role not in ("org_admin", "platform_admin"):
    ...
if current_user.role != "platform_admin" and ...:
    ...

2. Async lazy-loading crash (MissingGreenlet)

Accessing at.agent.tenant_id will crash at runtime because async SQLAlchemy does not support lazy loading. You need to eagerly load the agent relationship:

at_r = await db.execute(
    select(AgentTool)
    .where(AgentTool.id == agent_tool_id)
    .options(selectinload(AgentTool.agent))  # add this
)

3. N+1 query problem

The loop issues one DB query per ID (up to 50 sequential queries). Please batch-fetch all records in a single query:

# Fetch all in one query
results = await db.execute(
    select(AgentTool)
    .where(AgentTool.id.in_(valid_ids))
    .options(selectinload(AgentTool.agent))
)
agent_tools = results.scalars().all()

4. Missing English translations

The PR only adds zh.json entries. Please add the corresponding keys to en.json as well.

5. Emoji usage

The frontend uses 🔌, 🤖, and 🗑️ in the UI. Our project does not use emoji in the interface — please replace them with text labels or Tabler icons (which are used elsewhere in the codebase).

---

What's Good

• The WeCom connection_mode priority fix is correct and clean.
• Making onSuccess async and awaiting query invalidation before resetting the form is the right approach.
• The .catch(() => null) on the webhook URL query is a good defensive fix.
• The partial-failure errors response design in the bulk delete API is well thought out.

Please address the required fixes above and re-push to this branch — happy to re-review after.

[ThomasOscar]

感谢您反馈问题，我现在去解决这些问题。

[ThomasOscar]

Thanks for the PR! The WeCom webhook fix looks good, but the bulk delete feature has several issues that need to be resolved before we can merge.

Required Fixes

1. Wrong role names — bulk delete endpoint returns 403 for all valid admins

The permission check uses role names that don't exist in our system:

# Current (broken) — these roles don't exist
if current_user.role not in ("admin", "super_admin"):
    ...
if current_user.role != "super_admin" and ...:
    ...

Our platform uses org_admin and platform_admin. Please update both checks:

if current_user.role not in ("org_admin", "platform_admin"):
    ...
if current_user.role != "platform_admin" and ...:
    ...

2. Async lazy-loading crash (MissingGreenlet)

Accessing at.agent.tenant_id will crash at runtime because async SQLAlchemy does not support lazy loading. You need to eagerly load the agent relationship:

at_r = await db.execute(
    select(AgentTool)
    .where(AgentTool.id == agent_tool_id)
    .options(selectinload(AgentTool.agent))  # add this
)

3. N+1 query problem

The loop issues one DB query per ID (up to 50 sequential queries). Please batch-fetch all records in a single query:

# Fetch all in one query
results = await db.execute(
    select(AgentTool)
    .where(AgentTool.id.in_(valid_ids))
    .options(selectinload(AgentTool.agent))
)
agent_tools = results.scalars().all()

4. Missing English translations

The PR only adds zh.json entries. Please add the corresponding keys to en.json as well.

5. Emoji usage

The frontend uses 🔌, 🤖, and 🗑️ in the UI. Our project does not use emoji in the interface — please replace them with text labels or Tabler icons (which are used elsewhere in the codebase).

What's Good

• The WeCom connection_mode priority fix is correct and clean.
• Making onSuccess async and awaiting query invalidation before resetting the form is the right approach.
• The .catch(() => null) on the webhook URL query is a good defensive fix.
• The partial-failure errors response design in the bulk delete API is well thought out.

Please address the required fixes above and re-push to this branch — happy to re-review after.

我已经按照您的要求修改了代码，你看看还有没有问题。