feat(roundtable): 第三步「数据入库」由结构化输出智能体自行调用技能
- 入库改为让 roundtable-structure 走完整 agent 运行时(ingest run policy) 自行挑选/读取/调用入库技能并传入 taskId,不再前端代调演示 - 新增 /api/flow-extract/ingest-eligibility(智能体判断当前业务场景是否有 合适入库技能,决定入库按钮是否显示)+ /api/multi-agent/structure/init - 入库前判断是否已生成流程图:无则发起「是否先生成流程图」用户协助 - 「知识库入库」更名为「数据入库」 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
a85d2480b4
commit
03c155f8a7
10 files changed
+507
-80
No files matched your search
@@ -1,38 +1,58 @@
|
||||
/**
|
||||
* 第三步「入库」功能门控。
|
||||
* 第三步「入库」功能门控 + 入库执行客户端。
|
||||
*
|
||||
* 入库询问 / 意图识别 / 手动入库按钮只有在**入库技能存在且启用**时才出现
|
||||
* (对应需求「如果有了调用技能入库的技能后…」)。当前是示例技能 `knowledge-base-ingest`
|
||||
* (演示用);后续替换为真实入库技能时只要沿用同一个 name,本门控即继续生效。
|
||||
* 入库不再由前端硬编码「有没有含『入库』关键字的技能」判定,而是让**结构化输出智能体**
|
||||
* (`roundtable-structure`)读它挂载的入库技能 + 当前业务场景,**自行判断**是否有适合本
|
||||
* 场景的入库技能(技能名可能含「六步法」等场景线索)。判定为可入库才显示「入库」按钮。
|
||||
*
|
||||
* 真正入库时,由结构化输出智能体走**完整 agent 运行时**(`POST /api/multi-agent/run/stream`,
|
||||
* role=ingest)**自己挑技能、读 SKILL.md 并调用**完成入库——而不是前端代它调技能。
|
||||
*/
|
||||
import { loadSkills } from "@/core/skills/api";
|
||||
import { apiFetch } from "@/core/api/fetch-client";
|
||||
import { getBackendBaseURL } from "@/core/config";
|
||||
|
||||
/** 示例入库技能名(真实技能可改名;门控按「入库相关」关键字判断,不写死此名)。 */
|
||||
export const INGEST_SKILL_NAME = "knowledge-base-ingest";
|
||||
|
||||
/**
|
||||
* 是否为「入库相关」技能:按 name / name_zh / description 含 `ingest` 或「入库」判断。
|
||||
* 这样示例技能(knowledge-base-ingest)与**后续改了名的真实入库技能**都能识别;
|
||||
* 而知识库**检索**类技能(如 knowledge-base-search「知识库检索」)不含「入库」/`ingest`,不会误命中。
|
||||
*/
|
||||
export function isIngestRelatedSkill(s: {
|
||||
name?: string;
|
||||
name_zh?: string | null;
|
||||
description?: string;
|
||||
}): boolean {
|
||||
const hay = `${s.name ?? ""} ${s.name_zh ?? ""} ${s.description ?? ""}`.toLowerCase();
|
||||
return hay.includes("ingest") || hay.includes("入库");
|
||||
/** `/ingest-eligibility` 返回:是否可入库 + 选中的技能名 + 一句话依据。 */
|
||||
export interface IngestEligibility {
|
||||
canIngest: boolean;
|
||||
skill: string;
|
||||
reason: string;
|
||||
}
|
||||
|
||||
/**
|
||||
* 是否**挂载了**可用的入库相关技能(存在且启用)。失败回退 false。
|
||||
* 为 false 时第三步不显示入库按钮、不触发任何入库操作。
|
||||
* 让结构化输出智能体判断「当前业务场景**是否有合适的入库技能**」(决定是否显示入库按钮)。
|
||||
*
|
||||
* 入参为业务场景线索(业务码 / 业务链名 / 总控编排提示 / 方案标题)+ taskId,由后端把挂在
|
||||
* `roundtable-structure` 上、且已启用的技能交给模型对照判断。失败 / 未配置入库技能 → 不可入库。
|
||||
*/
|
||||
export async function isIngestSkillAvailable(): Promise<boolean> {
|
||||
export async function checkIngestEligibility(req: {
|
||||
taskId?: string | null;
|
||||
businessCode?: string | null;
|
||||
chainName?: string | null;
|
||||
coordinatorPrompt?: string | null;
|
||||
reportTitle?: string | null;
|
||||
model?: string;
|
||||
}): Promise<IngestEligibility> {
|
||||
try {
|
||||
const skills = await loadSkills();
|
||||
return skills.some((s) => s.enabled && isIngestRelatedSkill(s));
|
||||
const res = await apiFetch(`${getBackendBaseURL()}/api/flow-extract/ingest-eligibility`, {
|
||||
method: "POST",
|
||||
headers: { "Content-Type": "application/json" },
|
||||
body: JSON.stringify({
|
||||
task_id: req.taskId ?? null,
|
||||
business_code: req.businessCode ?? null,
|
||||
chain_name: req.chainName ?? null,
|
||||
coordinator_prompt: req.coordinatorPrompt ?? null,
|
||||
report_title: req.reportTitle ?? null,
|
||||
model: req.model,
|
||||
}),
|
||||
});
|
||||
if (!res.ok) return { canIngest: false, skill: "", reason: "" };
|
||||
const data = (await res.json()) as { can_ingest?: boolean; skill?: string; reason?: string };
|
||||
return {
|
||||
canIngest: !!data.can_ingest,
|
||||
skill: data.skill ?? "",
|
||||
reason: data.reason ?? "",
|
||||
};
|
||||
} catch {
|
||||
return false;
|
||||
return { canIngest: false, skill: "", reason: "" };
|
||||
}
|
||||
}
|
||||
@@ -885,3 +885,29 @@ export async function initSummaryThread(
|
||||
const json = (await res.json()) as { agent_name: string; thread_id: string };
|
||||
return { agentName: json.agent_name, threadId: json.thread_id };
|
||||
}
|
||||
|
||||
/**
|
||||
* Create a thread for the Step 3「入库」structure agent (`roundtable-structure`,
|
||||
* a built-in singleton — the same agent that extracts the flowchart, but this run
|
||||
* uses the `ingest` run policy so its attached ingest skill actually executes).
|
||||
* Run it afterwards with {@link streamMultiAgent} (`agentType: "special"`,
|
||||
* `agentName: "roundtable-structure"`, `dAgentThreadId: { [agentName]: threadId }`):
|
||||
* the agent picks the suitable ingest skill (its name may contain「六步法」), reads
|
||||
* its SKILL.md and calls it — passing the taskId + summary report + structured flow.
|
||||
*/
|
||||
export async function initStructureThread(
|
||||
options: { signal?: AbortSignal } = {},
|
||||
): Promise<ReportThreadResponse> {
|
||||
const res = await apiFetch(`${getBackendBaseURL()}/api/multi-agent/structure/init`, {
|
||||
method: "POST",
|
||||
headers: { "Content-Type": "application/json" },
|
||||
body: "{}",
|
||||
signal: options.signal,
|
||||
});
|
||||
if (!res.ok) {
|
||||
const text = await res.text().catch(() => "");
|
||||
throw new Error(`init structure thread failed (${res.status}): ${text}`);
|
||||
}
|
||||
const json = (await res.json()) as { agent_name: string; thread_id: string };
|
||||
return { agentName: json.agent_name, threadId: json.thread_id };
|
||||
}
|
||||
Reference in new issue
Block a user