Merge branch 'master' of http://192.168.0.200/knowledge-base-bj/deerflow-server into dhk-1

CLAUDE.md

@@ -88,7 +88,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). 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)` — filtered by **both** `metadata.taskId` AND `metadata.agent_id` so the three businesses' conversations stay isolated even though they share one taskId) + 新建对话; the `…/chats` index (`TaskFxIndexResolver`) opens the latest task thread or 新建. The right `:thread_id` host differs by business: **rwfx** → `TaskFxChat` (`AgentChatPage taskGate`) = full workspace (non-`lite`): 目的树闸门 panel + 清除记录 (placed under 新建对话); **xdfx** → also `TaskFxChat` (same 目的树闸门 query+display, same `purpose_detail_url`) but workspace passed `lite`; **3qfx** → `TaskBindChat` (`AgentChatPage taskBind`, `lite`) = 1:N list only, no gate, and 新建对话 **auto-sends** the task opening text (`taskAutoSendText`; gate Line 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/core/auth/task-deeplink.ts

@@ -233,12 +233,16 @@ export interface TaskDeeplinkTarget {
   state?: Record<string, unknown>;
 }
 
-/** 用 taskName / taskContent 拼出开场信息文本；末尾附上任务 id（task_id），供后端识别任务。 */
-function buildOpeningText(detail: CopTaskDetail, taskId: string): string {
+/**
+ * 用 taskName / taskContent 拼出开场信息文本；末尾附上任务 id（task_id），供后端识别任务。
+ * xdfx（行动分析）额外附上「行动id（action_id）」——传入 actionId 时追加该行。
+ */
+function buildOpeningText(detail: CopTaskDetail, taskId: string, actionId?: string): string {
   return [
     detail.taskName ? `任务名称：${detail.taskName}` : "",
     detail.taskContent ? `任务内容：${detail.taskContent}` : "",
     taskId ? `任务id（task_id）为${taskId}` : "",
+    actionId ? `行动id（action_id）为${actionId}` : "",
   ]
     .filter(Boolean)
     .join("\n");
@@ -312,11 +316,15 @@ export async function resolveTaskDeeplinkTarget(
   // 暂存任务上下文（taskId + agentId + 开场信息），跳到 chats 索引，由工作区按 taskId 决定
   // 开最新历史对话 / 新建。rwfx 在工作区里额外过「目的树闸门」；3qfx/xdfx 仅 1:N 列表，
   // 新建对话直接带开场信息自动发出（见 task-purpose / AgentChatPage 的 taskGate / taskBind）。
+  // xdfx（行动分析）：聊天记录按「行动id」划分（partitionByAction），且开场信息追加 action_id。
+  const isXdfx = parsed.businessCode === XDFX_BUSINESS_CODE;
+  const actionId = rawId || taskId;
   persistTaskContext({
     taskId,
     agentId,
-    openingText: buildOpeningText(detail, taskId),
-    actionId: rawId || taskId,
+    openingText: buildOpeningText(detail, taskId, isXdfx ? actionId : undefined),
+    actionId,
+    partitionByAction: isXdfx,
   });
   return { path: `${taskBase}/agent/${agentId}/chats` };
 }

frontend-web/src/core/auth/task-purpose.ts

@@ -41,6 +41,12 @@ export interface TaskContext {
   openingText: string;
   /** 深链原始 id（xdfx 为「行动id」，需追加行动id 的按钮用；其它业务等于 taskId）。 */
   actionId?: string;
+  /**
+   * xdfx（行动分析）专属：聊天记录按「行动id」(actionId) 而非「任务id」划分。
+   * 为 true 时，新建对话额外打 `metadata.actionId` 标签、对话列表按 actionId 过滤
+   * （仍保留 taskId 标签以维持任务深链对话「全局共享、不分用户」的后端语义）。
+   */
+  partitionByAction?: boolean;
 }
 
 const TASK_CONTEXT_STORAGE_KEY = "task.rwfxContext";
@@ -311,12 +317,29 @@ export function readTaskContext(): TaskContext | null {
       agentId: String(parsed.agentId),
       openingText: typeof parsed.openingText === "string" ? parsed.openingText : "",
       actionId: typeof parsed.actionId === "string" ? parsed.actionId : undefined,
+      partitionByAction: parsed.partitionByAction === true,
     };
   } catch {
     return null;
   }
 }
 
+/**
+ * 任务深链对话的 thread metadata 标签（既用于「新建对话」打标签，也用于对话列表过滤）。
+ *   - 普通业务（rwfx/3qfx）：`{ taskId }` —— 按任务划分（1:N）。
+ *   - xdfx（partitionByAction）：`{ taskId, actionId }` —— 额外按「行动id」划分聊天记录；
+ *     仍带 taskId 以保留后端「任务深链对话全局共享」的语义（后端据 metadata.taskId 跳过分用户过滤）。
+ * 无有效 taskId 时返回 undefined（调用方据此不打标签）。
+ */
+export function taskThreadMetadata(
+  ctx: TaskContext | null | undefined,
+): Record<string, unknown> | undefined {
+  if (!ctx?.taskId) return undefined;
+  return ctx.partitionByAction && ctx.actionId
+    ? { taskId: ctx.taskId, actionId: ctx.actionId }
+    : { taskId: ctx.taskId };
+}
+
 export function clearTaskContext(): void {
   try {
     sessionStorage.removeItem(TASK_CONTEXT_STORAGE_KEY);

frontend-web/src/core/threads/use-task-threads.ts

@@ -8,6 +8,10 @@
  * 同一个 taskId 可能挂在多条业务链上（rwfx / 3qfx / xdfx 共用任务 id），每条业务用各自的
  * 智能体。传入 ``agentId`` 时额外按 ``metadata.agent_id`` 过滤（后端 metadata 过滤是 AND/子集
  * 匹配），把不同业务的对话列表隔离开——否则三种业务的对话会混在一起。
+ *
+ * xdfx（行动分析）：聊天记录按「行动id」划分——传入 ``actionId`` 时额外按 ``metadata.actionId``
+ * 过滤（同一任务下的不同行动各自一份对话列表）；仍保留 taskId 过滤以命中后端「任务深链对话
+ * 全局共享」的判定（后端据 metadata.taskId 跳过分用户过滤）。
  */
 
 import { useThreadsPage } from "@/core/threads/hooks";
@@ -16,13 +20,16 @@ import type { AgentThread } from "@/core/threads/types";
 export function useTaskThreads(
   taskId: string | null | undefined,
   agentId?: string | null | undefined,
+  actionId?: string | null | undefined,
 ) {
   const enabled = !!taskId;
   // 任务工作区只在有 taskId 时渲染；无 taskId 时传一个不可能命中的过滤，返回空列表。
   const metadata = enabled
-    ? agentId
-      ? { taskId, agent_id: agentId }
-      : { taskId }
+    ? {
+        taskId,
+        ...(actionId ? { actionId } : {}),
+        ...(agentId ? { agent_id: agentId } : {}),
+      }
     : { taskId: "__none__" };
   const query = useThreadsPage({ page: 1, pageSize: 100, metadata });
   const threads: AgentThread[] = enabled ? (query.data?.threads ?? []) : [];

frontend-web/src/pages/AgentChatPage.tsx

@@ -31,7 +31,7 @@ import { saveLastAgentId, useThreadSettings } from "@/core/settings";
 import { stopThreadRun, useThreadStream } from "@/core/threads/hooks";
 import { textOfMessage } from "@/core/threads/utils";
 import { env } from "@/env";
-import { readTaskContext } from "@/core/auth/task-purpose";
+import { readTaskContext, taskThreadMetadata } from "@/core/auth/task-purpose";
 import { TaskPurposePanel } from "@/strategy-components/components/task-components/TaskPurposePanel";
 import { desensitize } from "@/lib/desensitize";
 
@@ -143,8 +143,9 @@ export default function AgentChatPage({
     threadId: isNewThread ? undefined : threadId,
     assistantId: agent_id,
     context: { ...settings.context, agent_id },
-    // 任务闸门：新建 thread 打 metadata.taskId 标签，供任务对话列表(1:N)按任务过滤。
-    threadMetadata: taskId ? { taskId } : undefined,
+    // 任务闸门：新建 thread 打 metadata.taskId 标签，供任务对话列表(1:N)按任务过滤；
+    // xdfx 额外打 metadata.actionId 标签，按「行动id」划分聊天记录（见 taskThreadMetadata）。
+    threadMetadata: taskId ? taskThreadMetadata(taskContext) : undefined,
     onStart: (createdThreadId) => {
       setThreadId(createdThreadId);
       setIsNewThread(false);

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

@@ -46,11 +46,19 @@ import AgentChatPage from "@/pages/AgentChatPage";
 import { ChatRuntime } from "@/pages/WorkspaceRoutes";
 import { TaskJumpBar } from "@/strategy-components/components/task-components/TaskJumpBar";
 
-function useChatsBase(taskBase: string): { taskId: string; agentId: string; chatsBase: string } {
+function useChatsBase(taskBase: string): {
+  taskId: string;
+  agentId: string;
+  /** xdfx（partitionByAction）：按「行动id」划分聊天记录用；其它业务为 ""（仍按 taskId 划分）。 */
+  actionId: string;
+  chatsBase: string;
+} {
   const { agent_id } = useParams<{ agent_id: string }>();
   const agentId = agent_id ?? "";
-  const taskId = readTaskContext()?.taskId ?? "";
-  return { taskId, agentId, chatsBase: `${taskBase}/agent/${agentId}/chats` };
+  const ctx = readTaskContext();
+  const taskId = ctx?.taskId ?? "";
+  const actionId = ctx?.partitionByAction ? (ctx.actionId ?? "") : "";
+  return { taskId, agentId, actionId, chatsBase: `${taskBase}/agent/${agentId}/chats` };
 }
 
 /**
@@ -142,19 +150,22 @@ function parseThreadId(pathname: string, chatsBase: string): string | null {
 function TaskConversationsList({
   taskId,
   agentId,
+  actionId,
   chatsBase,
   business,
   lite,
 }: {
   taskId: string;
   agentId: string;
+  /** xdfx：按「行动id」划分聊天记录；其它业务为 ""。 */
+  actionId: string;
   chatsBase: string;
   business: TaskBusiness;
   lite?: boolean;
 }) {
   const { pathname } = useLocation();
   const navigate = useNavigate();
-  const { threads, isLoading } = useTaskThreads(taskId, agentId);
+  const { threads, isLoading } = useTaskThreads(taskId, agentId, actionId);
   const currentThreadId = useMemo(() => parseThreadId(pathname, chatsBase), [pathname, chatsBase]);
   const businessName = desensitize(TASK_BUSINESSES.find((b) => b.code === business)?.name ?? "");
 
@@ -371,13 +382,14 @@ export function TaskFxWorkspace({
   business: TaskBusiness;
   lite?: boolean;
 }) {
-  const { taskId, agentId, chatsBase } = useChatsBase(taskBase);
+  const { taskId, agentId, actionId, chatsBase } = useChatsBase(taskBase);
   return (
     <div className="flex size-full min-h-0 flex-col overflow-hidden">
       <div className="flex min-h-0 flex-1 overflow-hidden">
         <TaskConversationsList
           taskId={taskId}
           agentId={agentId}
+          actionId={actionId}
           chatsBase={chatsBase}
           business={business}
           lite={lite}
@@ -395,9 +407,9 @@ export function TaskFxWorkspace({
 
 /** chats 索引：有历史对话 → 跳最新；否则 → 跳 new（rwfx 走闸门 / 3qfx/xdfx 直接带开场信息）。 */
 export function TaskFxIndexResolver({ taskBase }: { taskBase: string }) {
-  const { taskId, agentId, chatsBase } = useChatsBase(taskBase);
+  const { taskId, agentId, actionId, chatsBase } = useChatsBase(taskBase);
   const navigate = useNavigate();
-  const { isLoading, hasThreads, latestThreadId } = useTaskThreads(taskId, agentId);
+  const { isLoading, hasThreads, latestThreadId } = useTaskThreads(taskId, agentId, actionId);
 
   useEffect(() => {
     if (isLoading) return;