overlord-cli 0.2608170844.0 → 0.2608171622.0

package/dist/connectors/VERSION

@@ -1 +1 @@
-0.3.25
+0.3.26

package/dist/connectors/adapters/antigravity/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://antigravity.google/schemas/v1/plugin.json",
   "name": "overlord",
-  "version": "0.3.25",
+  "version": "0.3.26",
   "description": "Chat-driven access to Overlord mission protocol workflows through skills and MCP.",
   "author": {
     "name": "Cooperativ",

package/dist/connectors/adapters/claude/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.25",
+  "version": "0.3.26",
   "description": "Overlord mission protocol workflow for Claude Code — attach/update/ask/deliver, slash commands, and hook-driven activity capture.",
   "author": {
     "name": "Cooperativ",

package/dist/connectors/adapters/codex/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.25",
+  "version": "0.3.26",
   "description": "Chat-driven access to Overlord mission protocol workflows with hook-driven activity capture.",
   "author": {
     "name": "Cooperativ",

package/dist/connectors/adapters/cursor/.cursor-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.25",
+  "version": "0.3.26",
   "description": "Overlord mission protocol workflow for Cursor — attach/update/ask/deliver, slash commands, MCP bridge, and follow-up capture.",
   "author": {
     "name": "Cooperativ",

package/dist/connectors/core/overlord-mission/SKILL.md

@@ -13,9 +13,9 @@ Connector adapters may add harness-specific commands, hooks, MCP tools, or launc
 
 Use this mode when the prompt already contains a mission ID or explicitly says the session was launched by Overlord.
 
-**`<mission_id>` is always the short display id** — `coo:695`, `1:899`: a workspace prefix, a colon, and a number. It is the only identifier you ever pass to a `ovld protocol` command. Any UUID you encounter (objective id, session id, execution request id, internal mission uuid) is context, never the value for `--mission-id`. If the only id you can find is a bare UUID, you are missing the mission id — re-read the prompt or run `ovld protocol search-missions` rather than guessing.
+**`<mission_id>` is always the short display id** — `coo:695`, `1:899`: a workspace prefix, a colon, and a number. Pass it as `--mission-id`. **`<objective_id>`** is the objective display id (`coo:695.k7xm`) or UUID; pass it as `--objective-id` when you know which objective to execute. Never pass an objective id as `--mission-id`. If the prompt includes `OVERLORD_OBJECTIVE_ID` or an Objective ID line, include `--objective-id` on attach. If the only id you can find is a bare UUID with no mission display id, re-read the prompt or run `ovld protocol search-missions` rather than guessing.
 
-1. Attach first with `ovld protocol attach --mission-id <mission_id>`.
+1. Attach first with `ovld protocol attach --mission-id <mission_id> [--objective-id <objective_id>]`.
 2. The attach response prints JSON to stdout containing `session.sessionKey`. The CLI also persists this key automatically so subsequent `ovld protocol` commands in the same working directory resolve it without `--session-key`. If auto-resolution fails, pass `--session-key <sessionKey>` explicitly on every subsequent call.
 3. Treat the Overlord mission prompt as authoritative for the objective, constraints, and delivery target. Begin executing the current objective immediately after attach; do not wait for more instructions or ask for confirmation. This differs from `connect` or `load-context`, which only retrieve mission context and never imply the agent should act.
 4. Post updates while working: `ovld protocol update --session-key <sessionKey> --mission-id <mission_id> --summary "..." --phase execute`.

package/dist/connectors/core/overlord-mission/reference/cli.md

@@ -3,7 +3,7 @@
 ## Attach
 
 ```bash
-ovld protocol attach --mission-id $MISSION_ID
+ovld protocol attach --mission-id $MISSION_ID [--objective-id $OVERLORD_OBJECTIVE_ID]
 ```
 
 In a git workspace, `attach` records a VCS baseline (changed file paths from local `git status`) so delivery can compute the run-attributable delta automatically.

package/dist/connectors/core/scripts/overlord-mcp.mjs

@@ -214,10 +214,14 @@ const tools = [
   {
     name: 'overlord_attach_session',
     title: 'Attach to mission',
-    description: 'Attach an MCP-hosted agent session to a mission before update/ask/deliver.',
+    description:
+      'Attach an MCP-hosted agent session to a mission before update/ask/deliver. Pass objectiveId when the caller already knows which objective to execute.',
     inputSchema: objectSchema(
       {
         missionId: stringProperty('Mission UUID or workspace display id.'),
+        objectiveId: stringProperty(
+          'Optional objective UUID or display id (e.g. coo:756.k7xm). Pins attach to that objective.'
+        ),
         agent: stringProperty(`Agent identifier. Defaults to ${DEFAULT_AGENT}.`),
         model: stringProperty('Optional model identifier.'),
         executionTargetId: stringProperty(
@@ -442,6 +446,9 @@ function callOverlordTool(name, args) {
     return runProtocol('attach', {
       'mission-id': requiredString(args, 'missionId'),
       agent: optionalString(args, 'agent') ?? DEFAULT_AGENT,
+      ...(optionalString(args, 'objectiveId')
+        ? { 'objective-id': requiredString(args, 'objectiveId') }
+        : {}),
       ...(optionalString(args, 'model') ? { model: requiredString(args, 'model') } : {}),
       ...(optionalString(args, 'executionTargetId')
         ? { 'execution-target-id': requiredString(args, 'executionTargetId') }
@@ -575,7 +582,7 @@ process.stdin.on('data', async chunk => {
         result: {
           protocolVersion: PROTOCOL_VERSION,
           capabilities: { tools: { listChanged: false } },
-          serverInfo: { name: 'overlord-__OVERLORD_ADAPTER_KEY__', version: '0.3.25' }
+          serverInfo: { name: 'overlord-__OVERLORD_ADAPTER_KEY__', version: '0.3.26' }
         }
       });
       continue;