闲鱼封号专项应急预案

版本: v1.0 | 优先级: P0 | 状态: 🟢 可用 | 来源: DEF-37封号应急预案缺失

与cookie-manager紧急修复的区别

使用场景

1. unsent_retryer检测到account_banned关键词→自动触发
2. ban-detection-polling Cron检测到登录异常→自动触发
3. 人工发现账号被封→手动触发
4. 多账号同时被封→分别处理，互不影响

工作流

主流程: 封号应急响应(7步)

1. 封号检测

   • 接收封号事件: {account_id, platform, banned_reason, detected_at, detection_source}
   • 验证封号状态: 调用fishclaw-mcp check_cookie_validity确认
   • 记录封号信息到data/ban_events/{account_id}_{timestamp}.json
   • 执行: python d:/JueJin/skills/account-ban-emergency/scripts/ban_handler.py --action detect --account-id {account_id} --reason "{banned_reason}"

2. 自动暂停

   • 暂停该账号的所有Cron发布任务
   • 暂停该账号的xianyu-auto-reply客服回复
   • 暂停该账号的auto-delivery自动发货
   • 记录暂停状态到data/ban_events/{account_id}_paused.json
   • 执行: python d:/JueJin/skills/account-ban-emergency/scripts/ban_handler.py --action pause --account-id {account_id}

3. 客户通知

   • 通过QQBot发送封号告警给管理员
   • 告警内容: 封号账号/影响范围/当前状态/预计恢复时间
   • 告警模板: "🚨 闲鱼账号被封: {account_id}, 原因: {reason}, 已暂停该账号所有自动化操作。正在启动备用账号切换..."
   • 执行: python d:/JueJin/scripts/notification.py send_alert --level CRITICAL --message "告警内容"

4. 备用切换

   • 激活account-manager执行账号切换
   • 选择备用账号: 从data/account_pool.json中选择健康度最高的备用账号
   • 切换间隔≥17分钟(来源:01手册§十10.1多账号发布间隔)
   • 更新tenant_cookie_map.json映射
   • 执行: python d:/JueJin/skills/account-ban-emergency/scripts/ban_handler.py --action switch --account-id {account_id} --backup-account {backup_id}

5. 商品恢复

   • 在备用账号重新发布核心商品(优先级P0商品)
   • R6-014修复说明: exec脚本(action_republish)返回success:False+next_action=call_fishclaw_publish指引,不直接调用MCP(遵循R56层间依赖方向)。LLM编排器收到指引后调用fishclaw-mcp publish_item发布商品
   • 发布间隔≥17分钟(来源:01手册§十10.1)
   • 目标: 2小时内在备用账号重新发布核心商品
   • 执行: python d:/JueJin/skills/account-ban-emergency/scripts/ban_handler.py --action republish --backup-account {backup_id} → 返回REQUIRES_LLM_ORCHESTRATION → LLM编排调用fishclaw-mcp

6. 封号申诉

   • 根据封号原因生成申诉建议(策略+文本+证据清单+成功率预估)
   • 记录申诉事件到data/ban_events/{account_id}appeal{timestamp}.json
   • HL-009修复说明: exec脚本(action_appeal)返回success:False+next_action=call_xianyu_appeal_channel指引,不直接调用MCP(遵循R56层间依赖方向)。LLM编排器收到指引后调用闲鱼申诉渠道(人工客服/API)
   • 申诉策略按封号原因分类: 导流→承认整改 / 刷单→举证否认 / 侵权→授权证明 / 骚扰→道歉承诺 / 频率→承认整改 / 其他→通用申诉
   • 执行: python d:/JueJin/skills/account-ban-emergency/scripts/ban_handler.py --action appeal --account-id {account_id} [--reason "{banned_reason}"] → 返回REQUIRES_LLM_ORCHESTRATION → LLM编排调用申诉渠道

7. 事后分析

   • 记录封号原因+持续时间+影响范围
   • 分析风控策略是否需要调整
   • 更新MEMORY.md记录重大事件
   • 输出应急处理报告
   • 执行: python d:/JueJin/skills/account-ban-emergency/scripts/ban_handler.py --action analyze --account-id {account_id}

输入格式

{
  "account_id": "account_1",
  "platform": "xianyu",
  "banned_reason": "违反用户协议",
  "detected_at": "2026-06-02T10:00:00",
  "detection_source": "unsent_retryer"
}

输出格式

{
  "success": true,
  "data": {
    "banned_account": "account_1",
    "paused_services": ["cron-publish", "auto-reply", "auto-delivery"],
    "backup_account": "account_2",
    "republish_status": "in_progress",
    "republish_count": 5,
    "alert_sent": true,
    "analysis_report": "封号原因:违反用户协议,建议:降低发布频率"
  },
  "error": null,
  "code": null
}

异常处理

风控规则

示例

输入: unsent_retryer检测到账号被封

{
  "account_id": "account_1",
  "platform": "xianyu",
  "banned_reason": "违反用户协议",
  "detected_at": "2026-06-02T10:00:00",
  "detection_source": "unsent_retryer"
}

输出: 应急响应完成(暂停服务+切换备用账号+恢复商品)

{
  "success": true,
  "data": {
    "banned_account": "account_1",
    "paused_services": ["cron-publish", "auto-reply", "auto-delivery"],
    "backup_account": "account_2",
    "republish_status": "completed",
    "republish_count": 5,
    "alert_sent": true,
    "analysis_report": "封号原因:违反用户协议,建议:降低发布频率至每账号≤3次/天"
  },
  "error": null,
  "code": null
}

异常示例: 无可用备用账号

{
  "success": false,
  "data": {
    "banned_account": "account_1",
    "paused_services": ["cron-publish", "auto-reply", "auto-delivery"],
    "backup_account": null,
    "alert_sent": true
  },
  "error": "NO_BACKUP_ACCOUNT",
  "code": "NO_BACKUP_ACCOUNT"
}