修复禅道Bug清单中的前端问题：好友申请source校验、群解散二次验证缺失、

群解散事件未处理、错误码翻译缺失、恢复登录页误导性提示

- 好友申请首次必失败30000（P0）：AddFriendModal把手机号搜索单独标记为
  source:"phone"上报，但后端serveIMFriendRequestCreate的source校验只认
  search/qr/group，命中default分支返回"invalid friend request source"。
  改为手机号搜索也统一上报source:"search"（后端本就不区分具体搜索渠道），
  用两个全新、此前无任何关系的测试账号验证首次申请200成功
- 解散群聊需要短信二次验证但完整流程从未实现（P0）：新增
  SecurityChallengeModal通用二次验证弹层（POST /security/challenges→
  验证码→verify→action_token）+ requestActionToken()（stores/
  securityChallenge.ts，与requestConfirm同一模式），接入解散群聊和转让
  群主（后者此前也因缺X-Action-Token必然404/400）。同时发现并修复
  imDelete对无body请求不显式传空对象体，导致携带Content-Type:
  application/json但请求体真正为空时后端JSON解码失败返回400——实测确认
  两个问题都解决后DELETE返回200
- 群聊被解散但当前正查看该群的用户界面不会跳转（P1）：新增
  topics.ts的subscribeTopicGone()监听SDK自身的onDeleteTopic回调，
  ConversationView据此在当前会话被解散时弹出提示并跳转回消息列表
- P2P会话发起方标题栏显示原始topic id、对方明明在线却显示离线：确认
  为上一轮已修复的isCommType()根因问题的同一症状，本轮实测（新建从未
  聊过天的账号对）已不再复现；群内消息发送者显示原始uid的关联描述同样
  实测未复现
- 好友关系冲突（已是好友/申请正在处理中）报错英文原文透出：翻译表补充
  FRIEND_REQUEST_CONFLICT
- 深链/刷新页面时的"改为重新登录"链接此前在任何恢复登录过程中都会
  立即显示（不管是否超时），造成短暂白屏时的误导性提示：改为仅在真正
  超时后才显示该链接，与其上方的提示文案保持一致的显示条件

web/src/stores/securityChallenge.ts

@@ -0,0 +1,39 @@
+import { create } from 'zustand';
+
+import type { SecurityChallengeScene } from '@/lib/api/security';
+
+/**
+ * Prompts for the protocol's sensitive-action SMS re-verification (docs/IM-前后端对接文档.md:762-766)
+ * and resolves with the resulting `action_token`, or `null` if the user cancels -- same Promise
+ * shape/global-store-plus-single-root-component pattern as `confirmDialog.ts`'s `requestConfirm`, for
+ * the same reason: this needs to be callable from a mutation's `mutationFn` (GroupDetailColumn's
+ * dissolve flow, currently the only caller) with no natural "own a piece of JSX for this" home.
+ */
+export interface SecurityChallengeOptions {
+  scene: SecurityChallengeScene;
+  /** What's about to happen if the user completes verification -- e.g. "解散群聊「群名」". */
+  actionDescription: string;
+}
+
+interface PendingChallenge extends SecurityChallengeOptions {
+  resolve: (token: string | null) => void;
+}
+
+interface SecurityChallengeState {
+  pending: PendingChallenge | null;
+  respond: (token: string | null) => void;
+}
+
+export const useSecurityChallengeStore = create<SecurityChallengeState>((set, get) => ({
+  pending: null,
+  respond: (token) => {
+    get().pending?.resolve(token);
+    set({ pending: null });
+  },
+}));
+
+export function requestActionToken(options: SecurityChallengeOptions): Promise<string | null> {
+  return new Promise((resolve) => {
+    useSecurityChallengeStore.setState({ pending: { ...options, resolve } });
+  });
+}