@myvillage/cli 1.85.0 → 1.85.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@myvillage/cli",
-  "version": "1.85.0",
+  "version": "1.85.2",
   "description": "MyVillageOS CLI for community developers",
   "type": "module",
   "bin": {

package/src/agent-runtime/loop.js

@@ -635,6 +635,25 @@ const ACTION_TOOLS = new Set([
   'task_assign',
   'task_complete',
   'task_retry',
+  // Curriculum actions — creating/assigning activities and projects is real,
+  // externally-visible work. Without these, a curriculum-generator agent that
+  // successfully creates and assigns activities scores zero successful action
+  // tools, so any incidental flagged result marks the whole task FAILED.
+  'activity_create',
+  'activity_assign',
+  'activity_update',
+  'activity_delete',
+  'project_create',
+  'project_update',
+  'project_delete',
+]);
+
+// Read-only lookups whose "not found" result is an expected empty read, not a
+// failure. A missing agent_memory_get key is normal the first time an agent
+// touches a villager and must not be treated as a task-failing tool error.
+const BENIGN_NOT_FOUND_TOOLS = new Set([
+  'agent_memory_get',
+  'agent_memory_list',
 ]);
 
 function flattenToolResultText(tr) {
@@ -666,6 +685,14 @@ function isToolResultError(tr) {
   // "the user was unauthorized to do X" because we anchor on word boundaries.
   const text = flattenToolResultText(tr);
   if (!text) return false;
+  // A memory/lookup read that misses is an expected empty result, not an
+  // error. agent_memory_get returns "Memory key ... not found" the first time
+  // an agent touches a villager; flagging that would fail the whole task even
+  // though nothing went wrong. Real transport errors on these tools still set
+  // the explicit isError flag handled above, so they are unaffected.
+  if (BENIGN_NOT_FOUND_TOOLS.has(tr.toolName) && /\bnot found\b/i.test(text)) {
+    return false;
+  }
   return /\b(40[0-9]|50[0-9])\b/.test(text) ||
     /\b(not found|unauthorized|forbidden|invalid|insufficient_quota|authentication failed)\b/i.test(text);
 }

package/src/utils/api.js

@@ -689,11 +689,24 @@ export async function claimAgentTask(villageAgentId, taskId) {
 // otherwise the task is marked COMPLETED with the given `output`.
 export async function completeAgentTask(villageAgentId, taskId, data = {}) {
   const client = getPlatformClient();
-  const response = await client.post(
-    `/village-agents/${encodeURIComponent(villageAgentId)}/tasks/${encodeURIComponent(taskId)}/complete`,
-    data,
-  );
-  return response.data;
+  try {
+    const response = await client.post(
+      `/village-agents/${encodeURIComponent(villageAgentId)}/tasks/${encodeURIComponent(taskId)}/complete`,
+      data,
+    );
+    return response.data;
+  } catch (err) {
+    // Idempotent completion. The task may already be terminal because the agent
+    // completed it itself via the `agent_task_complete` tool during its run (the
+    // daemon also completes the active task at the end of each iteration), or a
+    // retry raced. A 409 "already terminal" means the task reached the end state
+    // we wanted — treat it as success rather than a failure so the daemon doesn't
+    // log a spurious "Failed to mark task complete" error every run.
+    if (err?.response?.status === 409) {
+      return { alreadyTerminal: true, message: err.response?.data?.error };
+    }
+    throw err;
+  }
 }
 
 // Retry a single FAILED or CANCELLED task: resets it to PENDING so the