From 43bbe26ff9bde350311486c01d2c9cdc82faf788 Mon Sep 17 00:00:00 2001
From: matevip <matevip@mate.vip>
Date: Thu, 21 May 2026 14:44:06 +0800
Subject: [PATCH] fix(goal,agent): expose goal management tools to every agent
 by default

---
 .../agent/binding/service/AgentBindingService.java     | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/mateclaw-server/src/main/java/vip/mate/agent/binding/service/AgentBindingService.java b/mateclaw-server/src/main/java/vip/mate/agent/binding/service/AgentBindingService.java
index c634570c..511e48f9 100644
--- a/mateclaw-server/src/main/java/vip/mate/agent/binding/service/AgentBindingService.java
+++ b/mateclaw-server/src/main/java/vip/mate/agent/binding/service/AgentBindingService.java
@@ -566,6 +566,16 @@ public class AgentBindingService implements AgentBindingResolver {
             "delegateAsync",
             "taskOutput",
             "listAvailableAgents",
+            // Persistent-goal management (RFC 48). These are agent-wide
+            // primitives — the user can decide mid-conversation that this
+            // task is a multi-turn goal, and the assistant must be able to
+            // lock it in. Pre-fix, business agents like "数据分析师" with
+            // tight bindings rejected setGoal as "not in my toolset",
+            // observed during PR4 manual QA.
+            "setGoal",
+            "addGoalCriterion",
+            "completeGoal",
+            "getGoalStatus",
             // Document / media generation — agent-wide capabilities, never
             // declared inside any skill manifest. Pre-Phase-2b these were
             // universally visible; the new gate silently strips them whenever