feat(深链会商): rwfx-A 复用单智能体 3q 预检闸门，未完成引导前往三情会商(3qfx-A)

- 抽出共用组件 RwfxSqReportGate（单/多智能体共用），targetGoPath 参数化「前往」目标
- 单智能体 TaskFxWorkspace 改为 import 共用组件（默认 3qfx），清理因抽离失效的 import
- 多智能体会商 RoundtablePlanningPage 深链 rwfx-A 挂同一闸门，目标 3qfx-A（三情会商）
- 改一处两处都生效，避免双份逻辑漂移

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

CLAUDE.md

@@ -89,7 +89,7 @@ The frontend (`frontend-web/`) is a React 19 + Vite SPA:
 - **LLM streaming**: `@langchain/langgraph-sdk` streams messages from the backend via SSE
 - **UI**: Radix UI primitives + TailwindCSS v4 + shadcn-style components in `src/components/ui/`
 - **Shims**: `src/shims/` provides `next/link` and `next/navigation` polyfills (original code was Next.js)
-- **Login URL params** (`LoginPage.tsx`, frontend-only — the backend never sees these): besides the auth params (`ticket`/`userId`/`env`/`theme`/`yUserId`/`token`/`access_token`/`authToken`/`password`), the page supports a **task deep-link** via `?taskId=&goPath=`. After login it calls the consumer API `GET {VITE_AIPI_CONSUMER_URL}/taskAnalyseSearch/cop-task-detail?taskId=` (header `Authorization: Bearer admin`, auto-injected by `utils/request.ts`), stashes the full `data` (`id/overview/taskDirection/taskName/taskContent`) into `sessionStorage["login.copTaskDetail"]`, then routes by `goPath`: base codes `3qfx`/`rwfx`/`xdfx` → that business's configured **single agent** Q&A inside a **任务工作区** (resolved via `/api/business-mapping`; `resolveTaskDeeplinkTarget` calls `persistTaskContext({taskId, agentId, openingText})` and navigates to the `…/chats` **index**, which opens the latest task conversation or 新建 — a 1:N task↔对话 workspace, NOT `pendingAgentMessage`); the `-A` suffix (`3qfx-A`/…) → **multi-agent roundtable** with `roundtablePrefill.businessCode` so the page auto-selects the configured 业务链条. **xdfx's deep-link `?taskId=` is actually an 行动id, not a 任务id** — `resolveDeeplinkTaskId(goPath, rawId)` (called in `LoginPage` before everything) detects `xdfx`/`xdfx-A` and resolves it via `GET {action_detail_url}/{actionId}` → `data.taskId` (`fetchTaskIdFromAction`; `action_test`+`mock.action_detail` for offline testing); the resolved 任务id then drives `cop-task-detail`, the purpose tree, and the 1:N binding (other businesses pass the id through unchanged). **xdfx additionally partitions its chat records by 行动id (action_id), NOT by task_id**: `resolveTaskDeeplinkTarget` sets `partitionByAction:true` + keeps the raw action_id as `TaskContext.actionId`, so new threads are tagged `metadata.{taskId,actionId}` (taskId kept only to preserve the backend「任务深链对话全局共享」semantics, which keys off `metadata.taskId`) and the conversation list filters by `actionId` (+`agent_id`) — different actions of the same task get separate lists. xdfx's first-question opening text also appends `行动id（action_id）为…` (see `buildOpeningText` / `taskThreadMetadata`). goPath→businessCode: `3qfx`→`3Q`, `rwfx`→`6BF`, `xdfx`→`7BF`. The roundtable target also threads the URL `taskId` into `roundtablePrefill.taskId` (`resolveTaskDeeplinkTarget(goPath, detail, taskId)`), which turns on two taskId-scoped behaviors: (1) **separate, unpartitioned per-task storage** — taskId 会商聊天记录 live in their **own** store/table (`roundtable_task_drafts`), keyed **only by `task_id`** (one taskId = many records, shared across users, **no user 分权** at all; `created_by` is audit-only), kept entirely out of the per-user personal store (`roundtable_drafts`, now strictly per-user) so the two never mix. Backend router `/api/roundtable-task-drafts` (`GET /by-task/{id}` + `/by-task/{id}/latest`, `POST`, `GET/PUT/DELETE /{id}` — all user-agnostic); frontend client `roundtable-planning/api/task-drafts.ts`, and `useDraftPersistence`/`useRoundtableDrafts` route **all** CRUD to it when a `taskId` is present (else the personal `drafts.ts`). The matching **background jobs** are shared by task too: `roundtable_jobs.task_id` marks a task job; reads/dedup/stream/resume/cancel pass `?task_id=` so any user opening the task sees the same running 研讨 (progress/flowchart), and the executor writes the final report back to the task-draft store. Existing rows are moved over by `scripts/migrate_roundtable_task_drafts.py` (migration `20260618_01`). The history dropdown filters to the task and 新建 keeps the binding; (2) **Step-3 auto structured output** — after the `roundtable-summary` agent writes the Markdown report it automatically runs a second round emitting a `flow-json` flowchart (`useStep3Summary` `autoFlow`+`chainLevels`), whose hierarchy follows the business chain's stage goals (任务 → 目的 → 行为体 → …; coordinatorPrompt-specified hierarchy wins) and whose nodes never carry 阶段编号/阶段名 (the prior bug). **Both targets render embedded under the 任务管理 layout** — nested routes under `task-management/<business-path>/{roundtable,agent/:agent_id/chats}` in `StrategyRoutes.tsx` (`<business-path>` = `plan-task-sentiment` / `plan-task/plan-task-fx` / `plan-task/plan-task-action`, matching the COH中任务 menu paths in `sidebar-menu.ts`) so the global sidebar keeps 任务管理 → COH中任务 → the matching business highlighted. **All three single-agent businesses share `TaskFxWorkspace`** (`task-components/TaskFxWorkspace.tsx`): left = a「当前任务」card (`readCopTaskDetail()` 任务名称 + 简介, desensitized, 留存 above 新建对话) + per-task 1:N conversation list (`useTaskThreads(taskId, agentId, actionId?)` — filtered by **both** `metadata.taskId` AND `metadata.agent_id` so the three businesses' conversations staLine truncated
+- **Login URL params** (`LoginPage.tsx`, frontend-only — the backend never sees these): besides the auth params (`ticket`/`userId`/`env`/`theme`/`yUserId`/`token`/`access_token`/`authToken`/`password`), the page supports a **task deep-link** via `?taskId=&goPath=`. After login it calls the consumer API `GET {VITE_AIPI_CONSUMER_URL}/taskAnalyseSearch/cop-task-detail?taskId=` (header `Authorization: Bearer admin`, auto-injected by `utils/request.ts`), stashes the full `data` (`id/overview/taskDirection/taskName/taskContent`) into `sessionStorage["login.copTaskDetail"]`, then routes by `goPath`: base codes `3qfx`/`rwfx`/`xdfx` → that business's configured **single agent** Q&A inside a **任务工作区** (resolved via `/api/business-mapping`; `resolveTaskDeeplinkTarget` calls `persistTaskContext({taskId, agentId, openingText})` and navigates to the `…/chats` **index**, which opens the latest task conversation or 新建 — a 1:N task↔对话 workspace, NOT `pendingAgentMessage`); the `-A` suffix (`3qfx-A`/…) → **multi-agent roundtable** with `roundtablePrefill.businessCode` so the page auto-selects the configured 业务链条. **xdfx's deep-link `?taskId=` is actually an 行动id, not a 任务id** — `resolveDeeplinkTaskId(goPath, rawId)` (called in `LoginPage` before everything) detects `xdfx`/`xdfx-A` and resolves it via `GET {action_detail_url}/{actionId}` → `data.taskId` (`fetchTaskIdFromAction`; `action_test`+`mock.action_detail` for offline testing); the resolved 任务id then drives `cop-task-detail`, the purpose tree, and the 1:N binding (other businesses pass the id through unchanged). **xdfx additionally partitions its chat records by 行动id (action_id), NOT by task_id**: `resolveTaskDeeplinkTarget` sets `partitionByAction:true` + keeps the raw action_id as `TaskContext.actionId`, so new threads are tagged `metadata.{taskId,actionId}` (taskId kept only to preserve the backend「任务深链对话全局共享」semantics, which keys off `metadata.taskId`) and the conversation list filters by `actionId` (+`agent_id`) — different actions of the same task get separate lists. xdfx's first-question opening text also appends `行动id（action_id）为…` (see `buildOpeningText` / `taskThreadMetadata`). goPath→businessCode: `3qfx`→`3Q`, `rwfx`→`6BF`, `xdfx`→`7BF`. The roundtable target also threads the URL `taskId` into `roundtablePrefill.taskId` (`resolveTaskDeeplinkTarget(goPath, detail, taskId)`), which turns on two taskId-scoped behaviors: (1) **separate, unpartitioned per-task storage** — taskId 会商聊天记录 live in their **own** store/table (`roundtable_task_drafts`), keyed **only by `task_id`** (one taskId = many records, shared across users, **no user 分权** at all; `created_by` is audit-only), kept entirely out of the per-user personal store (`roundtable_drafts`, now strictly per-user) so the two never mix. Backend router `/api/roundtable-task-drafts` (`GET /by-task/{id}` + `/by-task/{id}/latest`, `POST`, `GET/PUT/DELETE /{id}` — all user-agnostic); frontend client `roundtable-planning/api/task-drafts.ts`, and `useDraftPersistence`/`useRoundtableDrafts` route **all** CRUD to it when a `taskId` is present (else the personal `drafts.ts`). The matching **background jobs** are shared by task too: `roundtable_jobs.task_id` marks a task job; reads/dedup/stream/resume/cancel pass `?task_id=` so any user opening the task sees the same running 研讨 (progress/flowchart), and the executor writes the final report back to the task-draft store. Existing rows are moved over by `scripts/migrate_roundtable_task_drafts.py` (migration `20260618_01`). The history dropdown filters to the task and 新建 keeps the binding; (2) **Step-3 auto structured output** — after the `roundtable-summary` agent writes the Markdown report it automatically runs a second round emitting a `flow-json` flowchart (`useStep3Summary` `autoFlow`+`chainLevels`), whose hierarchy follows the business chain's stage goals (任务 → 目的 → 行为体 → …; coordinatorPrompt-specified hierarchy wins) and whose nodes never carry 阶段编号/阶段名 (the prior bug). **Both targets render embedded under the 任务管理 layout** — nested routes under `task-management/<business-path>/{roundtable,agent/:agent_id/chats}` in `StrategyRoutes.tsx` (`<business-path>` = `plan-task-sentiment` / `plan-task/plan-task-fx` / `plan-task/plan-task-action`, matching the COH中任务 menu paths in `sidebar-menu.ts`) so the global sidebar keeps 任务管理 → COH中任务 → the matching business highlighted. **All three single-agent businesses share `TaskFxWorkspace`** (`task-components/TaskFxWorkspace.tsx`): left = a「当前任务」card (`readCopTaskDetail()` 任务名称 + 简介, desensitized, 留存 above 新建对话) + per-task 1:N conversation list (`useTaskThreads(taskId, agentId, actionId?)` — filtered by **both** `metadata.taskId` AND `metadata.agent_id` so the three businesses' conversations staLine truncated
 - **iframe 嵌入模式 (外部系统用 iframe 套用深链问答/会商)** — 三个**按标签页**开关，全部由深链 URL 参数开启、存进同一份 `sessionStorage` 会话（`embed.session`，键名常量在 `core/embed/embed-session.ts`），跨登录跳转/刷新/页内导航存活，**绝不跨标签污染**同浏览器另开的正常系统页。核心隔离手法：用 `sessionStorage`（按标签页/浏览上下文隔离，iframe 即便同源也有独立一份）而非 `localStorage`（跨标签共享）。开关：(1) **`?embed=1`（可带 `&theme=`）** — 去全局 chrome（`PageLayout` 的 `pageSidebarAllowed && !isEmbedActive()` → 隐藏 Header + PageSidebar）+ 按外部主题色**强制**明/暗：走 next-themes 的 `forcedTheme`（`App.tsx` `AppProviders` 调 `resolveForcedEmbedTheme`，**不写** localStorage `strategy-theme`），离散映射 `dark-blue`/`dark`→深、其余→浅；嵌入侧**绝不**调 `setTheme`/`persistSidebarEnabled`（那俩落 localStorage 跨标签污染，`LoginPage` 据 `readEmbedParam` 跳过）。(2) **`?hideJump=1`** — 隐藏深链底部「快捷跳转」栏 `TaskJumpBar` 的两部分（底部「下一步」等按钮 + 右侧垂直居中悬浮菜单），单智能体问答 + 会商共用该栏，`isJumpBarHidden()` 为真时整条 `return null`。(3) **登录用户隔离** — 嵌入态下鉴权/身份键（`deerflow.auth` token、`userInfo`、`login.*`、`tools_token`、maxkey/userDetail token）全部经 `core/auth/scoped-storage.ts` 的 `authStorage()`（嵌入→sessionStorage / 正常→localStorage）读写，使 iframe 里登录的用户与正常登录用户**完全隔离**、互不覆盖；所有 token 读取都过 `getStoredAuth()`/`getAuthorizationHeaderValue()`（API 客户端 `core/api/*` 全走这俩），改中心函数即让全体调用方自动隔离；跨标签账号变更监听 `AuthSyncWatcher`（`core/auth/sync.tsx`）在嵌入态禁用。嵌入会话在 `main.tsx` 渲染前 `syncEmbedSessionFromCurrentUrl()` 同步启用（早于任何鉴权写入，避免首帧 effect 顺序漏写 localStorage）；`AppProviders` 的 effect 再按 SPA 导航同步。`embed=0`/`hideJump=0` 可显式关闭。正常（非嵌入）标签页所有 `isXxx()` 恒 false，行为**零变化**。第三个开关 `?isolate=1`（**独立登录会话**）把同一套**登录用户隔离**单独提供给**普通（带 chrome）标签页**——只切换鉴权存储、不去 chrome / 不强制主题 / 不动跳转栏：`authStorage()` 的条件从「仅嵌入」放宽为 `isEmbedActive() || isIsolatedSession()`，`AuthSyncWatcher` 的跨标签监听对嵌入态**或**独立态都即时忽略（handler 内实时判，运行时开关也即刻生效）。除 URL 参数外，**设置 → 外观 →「登录会话」** 有一个 Switch「独立登录会话（本标签页）」运行时切换（`setIsolatedSession`，`appearance-settings-page.tsx`）：**开启时先 `migrateAuthToSession()`**（`scoped-storage.ts`，把 localStorage 的受保护键 `deerflow.auth`/`userInfo`/`userId`/`tools_token` + `login.*` 前缀快照搬进 sessionStorage）再翻标志，故无感不登出；此后本标签页登录态独立——别处登录/换号影响不到它，它换号也影响不到别人，但关掉该标签即结束（需重登）。开启给 toast 提示。
 
 ### Configuration

frontend-web/src/roundtable-planning/pages/RoundtablePlanningPage.tsx

@@ -70,6 +70,7 @@ import { getAvatar, Man1Avatar, RobotAvatar } from "@/roundtable-planning/compon
 import { ImportRoundtableDraftDialog } from "@/components/workspace/roundtable-draft-share-dialogs";
 import { TaskPurposeDialog } from "@/strategy-components/components/task-components/TaskPurposeDialog";
 import { TaskJumpBar } from "@/strategy-components/components/task-components/TaskJumpBar";
+import { RwfxSqReportGate } from "@/strategy-components/components/task-components/RwfxSqReportGate";
 import type { TaskBusiness } from "@/core/auth/task-buttons";
 import {
   derivePurposeLevels,
@@ -2253,6 +2254,16 @@ export default function RoundtablePlanningPage() {
             roundtable
           />
         )}
+      {/* 任务分析会商（rwfx-A）深链：与单智能体共用 3q 预检闸门，未完成则引导前往三情**会商**（3qfx-A）。 */}
+      {prefillRef.current?.taskId &&
+        prefillRef.current?.businessCode &&
+        BUSINESS_CODE_TO_TASK_BUSINESS[prefillRef.current.businessCode] === "rwfx" && (
+          <RwfxSqReportGate
+            taskId={prefillRef.current.taskId}
+            targetGoPath="3qfx-A"
+            targetLabel="3qfx 会商"
+          />
+        )}
     </div>
   );
 }

frontend-web/src/strategy-components/components/task-components/RwfxSqReportGate.tsx

@@ -0,0 +1,106 @@
+/**
+ * rwfx「3q 完成预检」闸门（**单智能体 + 多智能体会商共用**）：进入任务分析（rwfx / rwfx-A 会商）时
+ * 调研判情报报告接口（``selectSqReport``）。若报告为空（数组空 / 全 null，即 3q 未完成）→ 弹框提示
+ * 「3q 未完成，是否前往三情分析」，「前往」按 ``targetGoPath`` 解析深链目标后跳转（同一任务 taskId 重绑）：
+ *   - 单智能体：``targetGoPath="3qfx"``（``TaskFxWorkspace``，跳单智能体三情工作区）；
+ *   - 多智能体会商：``targetGoPath="3qfx-A"``（``RoundtablePlanningPage``，跳三情会商）。
+ * 报告正常 / 接口不可判定（缺地址、请求失败）时不打扰用户。
+ *
+ * **两处共用本组件**——改一处两处都生效（用户要求复用，避免双份逻辑漂移）。
+ * 见 [[dashboard-input]] / [[task-deeplink]]。
+ */
+
+import { useEffect, useState } from "react";
+import { useNavigate } from "react-router-dom";
+import { Loader2 } from "lucide-react";
+import { toast } from "sonner";
+
+import { Button } from "@/components/ui/button";
+import {
+  Dialog,
+  DialogContent,
+  DialogDescription,
+  DialogFooter,
+  DialogHeader,
+  DialogTitle,
+} from "@/components/ui/dialog";
+import { readCopTaskDetail, resolveTaskDeeplinkTarget } from "@/core/auth/task-deeplink";
+import { fetchSqReportStatus } from "@/core/auth/dashboard-input";
+
+export function RwfxSqReportGate({
+  taskId,
+  targetGoPath = "3qfx",
+  targetLabel = "3qfx",
+}: {
+  taskId: string;
+  /** 「前往」目标 goPath：单智能体 = ``"3qfx"``（默认）；多智能体会商 = ``"3qfx-A"``。 */
+  targetGoPath?: string;
+  /** 文案/按钮里展示的目标名（默认 ``3qfx``；会商可传 ``"3qfx 会商"``）。 */
+  targetLabel?: string;
+}) {
+  const navigate = useNavigate();
+  const [open, setOpen] = useState(false);
+  const [jumping, setJumping] = useState(false);
+
+  useEffect(() => {
+    if (!taskId) return;
+    let alive = true;
+    void fetchSqReportStatus(taskId).then((status) => {
+      // 仅「明确为空（3q 未完成）」才弹框；complete / unknown 静默放行。
+      if (alive && status === "incomplete") setOpen(true);
+    });
+    return () => {
+      alive = false;
+    };
+  }, [taskId]);
+
+  const handleGo = async () => {
+    const detail = readCopTaskDetail();
+    if (!detail || !taskId) {
+      toast.error("缺少任务信息，无法跳转");
+      return;
+    }
+    setJumping(true);
+    try {
+      // 复用深链解析：会清掉当前任务上下文并按目标业务（3qfx / 3qfx-A）重新绑定（同一 taskId）。
+      const target = await resolveTaskDeeplinkTarget(targetGoPath, detail, taskId);
+      if (target) {
+        setOpen(false);
+        navigate(target.path, { state: target.state });
+      } else {
+        toast.error(`未配置三情分析（${targetLabel}）对应的业务智能体`);
+      }
+    } catch {
+      toast.error("跳转失败，请稍后再试");
+    } finally {
+      setJumping(false);
+    }
+  };
+
+  return (
+    <Dialog open={open} onOpenChange={(o) => !jumping && setOpen(o)}>
+      <DialogContent>
+        <DialogHeader>
+          <DialogTitle>3q 未完成</DialogTitle>
+          <DialogDescription>
+            未查询到该任务的研判情报报告（3q 未完成），是否前往该任务的三情分析（{targetLabel}）？
+          </DialogDescription>
+        </DialogHeader>
+        <DialogFooter>
+          <Button variant="outline" onClick={() => setOpen(false)} disabled={jumping}>
+            暂不
+          </Button>
+          <Button
+            // 弹框经 Radix Portal 渲染到 body，在 `.strategy-data` 作用域之外，故用全局按主题
+            // 定义的品牌色 token（:root/.dark/.lightblue 都有），三套主题都能正确取色。
+            className="bg-[var(--workspace-brand)] text-[var(--workspace-brand-foreground)] hover:opacity-90"
+            onClick={handleGo}
+            disabled={jumping}
+          >
+            {jumping ? <Loader2 className="h-4 w-4 animate-spin" /> : `前往 ${targetLabel}`}
+          </Button>
+        </DialogFooter>
+      </DialogContent>
+    </Dialog>
+  );
+}

frontend-web/src/strategy-components/components/task-components/TaskFxWorkspace.tsx

@@ -33,10 +33,8 @@ import { deleteTaskPurpose, readTaskContext } from "@/core/auth/task-purpose";
 import {
   fetchActionDetail,
   readCopTaskDetail,
-  resolveTaskDeeplinkTarget,
   type ActionDetail,
 } from "@/core/auth/task-deeplink";
-import { fetchSqReportStatus } from "@/core/auth/dashboard-input";
 import { TASK_BUSINESSES, type TaskBusiness } from "@/core/auth/task-buttons";
 import { useTaskThreads } from "@/core/threads/use-task-threads";
 import { titleOfThread } from "@/core/threads/utils";
@@ -45,6 +43,7 @@ import { cn } from "@/lib/utils";
 import AgentChatPage from "@/pages/AgentChatPage";
 import { ChatRuntime } from "@/pages/WorkspaceRoutes";
 import { TaskJumpBar } from "@/strategy-components/components/task-components/TaskJumpBar";
+import { RwfxSqReportGate } from "@/strategy-components/components/task-components/RwfxSqReportGate";
 
 function useChatsBase(taskBase: string): {
   taskId: string;
@@ -293,82 +292,6 @@ function TaskClearButton({ taskId }: { taskId: string }) {
   );
 }
 
-/**
- * rwfx 专用「3q 完成预检」闸门：进入任务分析工作区时调研判情报报告接口
- * （``GET {VITE_AIPI_CONSUMER_URL}/cop/selectSqReport?taskId=``）。若该任务的报告为空
- * （数组为空 / 内容全为 null，即 3q 未完成）→ 弹框提示「3q 未完成，是否进行 3qfx」，
- * 并提供「前往 3qfx」按钮切换到**同一任务**的三情分析工作区（复用深链解析重绑任务上下文）。
- * 报告正常 / 接口不可判定（缺地址、请求失败）时不打扰用户。见 [[dashboard-input]] / [[task-deeplink]]。
- */
-function RwfxSqReportGate({ taskId }: { taskId: string }) {
-  const navigate = useNavigate();
-  const [open, setOpen] = useState(false);
-  const [jumping, setJumping] = useState(false);
-
-  useEffect(() => {
-    if (!taskId) return;
-    let alive = true;
-    void fetchSqReportStatus(taskId).then((status) => {
-      // 仅「明确为空（3q 未完成）」才弹框；complete / unknown 静默放行。
-      if (alive && status === "incomplete") setOpen(true);
-    });
-    return () => {
-      alive = false;
-    };
-  }, [taskId]);
-
-  const handleGo3qfx = async () => {
-    const detail = readCopTaskDetail();
-    if (!detail || !taskId) {
-      toast.error("缺少任务信息，无法跳转");
-      return;
-    }
-    setJumping(true);
-    try {
-      // 复用深链解析：会清掉当前 rwfx 任务上下文并按 3qfx 业务重新绑定（同一 taskId）。
-      const target = await resolveTaskDeeplinkTarget("3qfx", detail, taskId);
-      if (target) {
-        setOpen(false);
-        navigate(target.path, { state: target.state });
-      } else {
-        toast.error("未配置三情分析（3qfx）对应的业务智能体");
-      }
-    } catch {
-      toast.error("跳转失败，请稍后再试");
-    } finally {
-      setJumping(false);
-    }
-  };
-
-  return (
-    <Dialog open={open} onOpenChange={(o) => !jumping && setOpen(o)}>
-      <DialogContent>
-        <DialogHeader>
-          <DialogTitle>3q 未完成</DialogTitle>
-          <DialogDescription>
-            未查询到该任务的研判情报报告（3q 未完成），是否前往该任务的三情分析（3qfx）？
-          </DialogDescription>
-        </DialogHeader>
-        <DialogFooter>
-          <Button variant="outline" onClick={() => setOpen(false)} disabled={jumping}>
-            暂不
-          </Button>
-          <Button
-            // 弹框经 Radix Portal 渲染到 body，在 `.strategy-data` 作用域之外，故不能用
-            // 局部的 `--color-main`（红主题侥幸有值、蓝主题失效→按钮消失）。改用全局按主题
-            // 定义的品牌色 token（:root/.dark/.lightblue 都有），三套主题都能正确取色。
-            className="bg-[var(--workspace-brand)] text-[var(--workspace-brand-foreground)] hover:opacity-90"
-            onClick={handleGo3qfx}
-            disabled={jumping}
-          >
-            {jumping ? <Loader2 className="h-4 w-4 animate-spin" /> : "前往 3qfx"}
-          </Button>
-        </DialogFooter>
-      </DialogContent>
-    </Dialog>
-  );
-}
-
 /**
  * 任务工作区布局：左列表 + 右 Outlet。
  * ``lite``（3qfx/xdfx）= 精简版：左列表无跳转按钮、无底部任务操作面板。