feat：增加文件链接验证以判断目标是否完成

Author: Rasic2

agents/matmaster_agent/flow_agents/agent.py

@@ -809,8 +809,10 @@ async def _run_research_flow(
                 yield _plan_execute_event
 
             # 回顾历史执行
+            history_steps = ctx.session.state[HISTORY_STEPS]
+            session_files = await get_session_files(ctx.session.id)
             self.all_finished_agent.instruction = create_all_finished_instruction(
-                ctx.session.state[HISTORY_STEPS]
+                history_steps, session_files
             )
             async for _all_finished_event in self.all_finished_agent.run_async(ctx):
                 yield _all_finished_event

agents/matmaster_agent/flow_agents/all_finished_agent/prompt.py

@@ -1,21 +1,20 @@
 import json
 
 
-def create_all_finished_instruction(history_steps):
+def create_all_finished_instruction(history_steps, session_files):
     """
     Build an instruction prompt for an agent that decides whether the user's overall goal
     has been completed up to the current point in the tool-call history.
-
     The agent must output a structured JSON:
     {"finished": bool, "reason": str}
     """
     history_text = json.dumps(history_steps, ensure_ascii=False, indent=2)
+    session_files_text = json.dumps(session_files, ensure_ascii=False, indent=2)
 
     return f"""
 You are a "Goal Completion Judge" agent. Your task is to determine whether the user's
 overall final objective/task has been completed *as of now*, based solely on the provided
-tool-call history: history_steps.
-
+tool-call history: history_steps and the provided session_files list.
 # Input
 history_steps is a list. Each element is a past tool invocation record, typically including
 (but not limited to):
@@ -24,27 +23,34 @@ def create_all_finished_instruction(history_steps):
 - status: the step status (e.g., success/failed/running/cancelled/unknown, etc.)
 - other fields: such as result/output/error/args/time, etc.
 
+session_files is a list of file links (OSS URLs). Only files that were actually generated
+and persisted for this session will appear here. Use session_files as verifiable evidence
+that a file deliverable truly exists.
+
 Below is the raw history_steps data (JSON):
 {history_text}
 
+Below is the raw session_files data (JSON):
+{session_files_text}
+
 # Decision Rules (must follow)
 1) Use "whether the user's final goal is achieved" as the ONLY criterion, not whether all steps were executed.
 2) If there is clear evidence that the final deliverable/final outcome has been produced and is usable, set finished=true.
+   - For file deliverables, you MUST verify the file exists by checking that an appropriate OSS link is present in session_files.
 3) If any critical step failed, is missing, is still running, or the outputs are insufficient to prove goal completion, set finished=false.
-4) If the information in history_steps is insufficient to confirm completion (e.g., no final output, only partial logs),
+4) If the information in history_steps and session_files is insufficient to confirm completion (e.g., no final output, only partial logs,
+   or expected output file link is not present in session_files),
    you MUST return finished=false and explain what information is missing in reason.
 5) If there are contradictions in history_steps, prefer the later entries. If you still cannot decide, return finished=false
    and explain the contradiction in reason.
-6) Do NOT assume results that are not explicitly supported by history_steps. Judge only from verifiable evidence.
-
+6) Do NOT assume results that are not explicitly supported by history_steps or session_files. Judge only from verifiable evidence.
 # Output Format (very important)
 You must output ONLY ONE JSON object that strictly matches this schema:
 {{
   "finished": true|false,
-  "reason": "A brief, specific explanation in English that cites key evidence from history_steps (e.g., a tool_name status/output). If not finished, state the critical blocking reason(s) or missing info."
+  "reason": "A brief, specific explanation in English that cites key evidence from history_steps and/or session_files (e.g., a tool_name status/output or the presence/absence of an OSS link). If not finished, state the critical blocking reason(s) or missing info."
 }}
-
 # Output Constraints
 - Output ONLY valid JSON (no Markdown, no code fences, no extra commentary).
-- reason must be an English string and should reference concrete evidence from history_steps.
+- reason must be an English string and should reference concrete evidence from history_steps and/or session_files.
 """.strip()