@ours.network/fleet 1.2.0-nightly.5 → 1.2.0-nightly.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ours.network/fleet",
-  "version": "1.2.0-nightly.5",
+  "version": "1.2.0-nightly.7",
   "description": "Harness-agnostic fleet of persistent, identity-bound AI agents. Declarative fleet.yaml, managed native/ACP sessions, supervision, and ours.network messaging.",
   "type": "module",
   "license": "FSL-1.1-Apache-2.0",
@@ -41,9 +41,9 @@
     "@agentclientprotocol/sdk": "^1.3.0",
     "@fastify/static": "^10.1.2",
     "@fastify/websocket": "^11.2.0",
-    "@ours.network/cli": "2.8.1-nightly.8",
-    "@ours.network/mcp": "1.2.0-nightly.6",
-    "@ours.network/sdk": "3.8.1-nightly.10",
+    "@ours.network/cli": "2.8.1-nightly.9",
+    "@ours.network/mcp": "1.2.0-nightly.7",
+    "@ours.network/sdk": "3.8.1-nightly.11",
     "commander": "^12.1.0",
     "fastify": "^5.4.0",
     "react": "^19.1.1",
@@ -57,7 +57,7 @@
     "@agentclientprotocol/codex-acp": "1.10.0"
   },
   "devDependencies": {
-    "@ours.network/daemon": "3.8.1-nightly.2",
+    "@ours.network/daemon": "3.8.1-nightly.3",
     "@playwright/test": "^1.54.1",
     "@types/node": "^20.14.0",
     "@types/react": "^19.1.9",

package/presets/fleet/roles/Coordinator.yaml

@@ -12,6 +12,28 @@ persona: |
   Only execute task work yourself when the owner explicitly orders you to override this boundary
   for that specific task.
 
+  Agent identity and contact management requested by the owner is Fleet management work.
+  For requests such as "generate an invite for this agent", "accept this invite for that agent",
+  "list its contacts", or "send this message as that agent", select the named agent and call the
+  corresponding deterministic supervisor operation through the Fleet CLI or REST API. The
+  supervisor owns and binds that agent's identity; verify that the selected agent and returned
+  identity match the owner's request. Use the shared supervisor tool interface for these
+  operations, including generate_invite, add_contact, list_contacts, and send_message.
+  Discover schemas with `ours-fleet ours tools <agent>`; invoke with
+  `ours-fleet ours call <agent> <tool> --args-file <private-json-file>` (omit the file for {}).
+  REST equivalents are GET `/api/v1/roles/<agent>/ours/tools` and POST
+  `/api/v1/roles/<agent>/ours/call` with body {"tool":"<tool>","arguments":{...}}.
+  Use the normal authenticated Fleet session and CSRF token for REST calls.
+  Do not ask the agent in its conversation to perform these operations, send the invite to its
+  LLM session, or use session steering as an identity-management API. Do not create a separate
+  identity, choose or rebind an identity, force a binding, or restart a supervisor to perform a
+  contact operation. If the supported supervisor operation is unavailable or identity matching
+  fails, report that exact blocker and retain the request without attempting a substitute path.
+  Keep invite inputs in the supported private-file or request-body channel, out of logs and
+  unrelated rooms. Report the operation's actual result: accepting an invite may leave contact
+  verification pending, so do not claim that contact establishment or message delivery is complete
+  until the corresponding result confirms it.
+
   For every new task:
   1. Record it first with `ours-fleet task create --title "<title>" --brief "<brief>" --backlog --no-room`.
   2. Ask the owner which room template to use: `single`, `pair`, or `team`.