overlord-cli 0.2608250836.0 → 0.2608251110.0

package/dist/connectors/AGENTS.md

@@ -316,7 +316,7 @@ connectors/
   README.md              ← architectural overview
 ```
 
-No adapter implementations have landed yet. When they do, the Claude and Codex adapters serve as the reference implementations.
+The Claude and Codex adapters are the reference implementations; Cursor, Pi, Antigravity, and OpenCode adapters have also shipped. See `connectors/HARNESS-MATRIX.md` for the current per-adapter capability matrix.
 
 ---
 

package/dist/connectors/VERSION

@@ -1 +1 @@
-0.3.36
+0.3.37

package/dist/connectors/adapters/antigravity/conformance-manifest.yaml

@@ -1,4 +1,4 @@
-contractVersion: "117"
+contractVersion: "123"
 componentType: connector
 componentKey: antigravity
 label: "Antigravity Connector"

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

@@ -1,7 +1,7 @@
 {
   "$schema": "https://antigravity.google/schemas/v1/plugin.json",
   "name": "overlord",
-  "version": "0.3.36",
+  "version": "0.3.37",
   "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.36",
+  "version": "0.3.37",
   "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/claude/conformance-manifest.yaml

@@ -1,4 +1,4 @@
-contractVersion: "117"
+contractVersion: "123"
 componentType: connector
 componentKey: claude
 label: "Claude Code Connector"

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

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

package/dist/connectors/adapters/codex/conformance-manifest.yaml

@@ -1,4 +1,4 @@
-contractVersion: "117"
+contractVersion: "123"
 componentType: connector
 componentKey: codex
 label: "Codex Connector"

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

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.36",
+  "version": "0.3.37",
   "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/adapters/cursor/conformance-manifest.yaml

@@ -1,4 +1,4 @@
-contractVersion: "117"
+contractVersion: "123"
 componentType: connector
 componentKey: cursor
 label: "Cursor Connector"

package/dist/connectors/adapters/opencode/conformance-manifest.yaml

@@ -1,4 +1,4 @@
-contractVersion: "117"
+contractVersion: "123"
 componentType: connector
 componentKey: opencode
 label: "OpenCode Connector"

package/dist/connectors/adapters/pi/conformance-manifest.yaml

@@ -1,4 +1,4 @@
-contractVersion: "117"
+contractVersion: "123"
 componentType: connector
 componentKey: pi
 label: "PI Connector"

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

@@ -478,14 +478,14 @@ const tools = [
     name: 'overlord_manage_run_queue',
     title: 'Manage Run Queues',
     description:
-      "Use this only when the user explicitly asks to create, rename, pause, resume, delete, or reorder the project's Run Queue definitions. These are administrative project-configuration actions and require a full-scope token; adding, moving, or removing objectives inside a queue uses overlord_queue_objective and overlord_reorder_run_queue instead.",
+      "Use this only when the user explicitly asks to create, rename, pause, resume, delete, or reorder the project's Run Queue definitions, or to retry one held queue entry. The queue-definition actions are administrative project-configuration and require a full-scope token; adding, moving, or removing objectives inside a queue uses overlord_queue_objective and overlord_reorder_run_queue instead.",
     inputSchema: objectSchema(
       {
         action: {
           type: 'string',
-          enum: ['create', 'update', 'delete', 'reorder_queues'],
+          enum: ['create', 'update', 'delete', 'reorder_queues', 'retry_entry'],
           description:
-            'create a queue, update (rename/pause/resume) one, delete one, or reorder the queue definitions.'
+            'create a queue, update (rename/pause/resume) one, delete one, reorder the queue definitions, or retry_entry to clear one held entry\'s hold and attempt budget so the dispatcher tries it again.'
         },
         projectId: stringProperty(
           'Project UUID, slug, or name. Required for create and reorder_queues.'
@@ -498,6 +498,12 @@ const tools = [
         moveEntriesTo: stringProperty(
           'delete only: destination queue UUID or unambiguous name. Required when the queue still holds entries.'
         ),
+        entry: stringProperty(
+          'retry_entry only: entry UUID, objective UUID, or objective display id. One of entry or objectiveId is required.'
+        ),
+        objectiveId: stringProperty(
+          'retry_entry only: objective UUID or display id whose live entry should be retried.'
+        ),
         orderedQueues: {
           type: 'array',
           description:
@@ -953,6 +959,19 @@ async function callOverlordTool(name, args) {
       });
     }
 
+    if (action === 'retry_entry') {
+      const entry = optionalString(args, 'entry');
+      const objectiveRef = optionalString(args, 'objectiveId');
+      if (!entry && !objectiveRef) {
+        throw new Error("action 'retry_entry' requires entry or objectiveId");
+      }
+      return runProtocol('retry-queue-entry', {
+        ...(entry ? { entry } : {}),
+        ...(objectiveRef ? { 'objective-id': objectiveRef } : {}),
+        ...(projectRef ? { 'project-id': projectRef } : {})
+      });
+    }
+
     if (action === 'reorder_queues') {
       if (!projectRef) throw new Error("action 'reorder_queues' requires projectId");
       if (
@@ -1091,7 +1110,7 @@ process.stdin.on('data', async chunk => {
         result: {
           protocolVersion: PROTOCOL_VERSION,
           capabilities: { tools: { listChanged: false } },
-          serverInfo: { name: 'overlord-__OVERLORD_ADAPTER_KEY__', version: '0.3.36' }
+          serverInfo: { name: 'overlord-__OVERLORD_ADAPTER_KEY__', version: '0.3.37' }
         }
       });
       continue;

package/dist/connectors/docs/05-connectors-and-agent-plugins.md

@@ -132,7 +132,11 @@ Requirements:
 
 - Install local Cursor plugin/rules/commands.
 - Add `beforeSubmitPrompt` hook to record follow-ups.
-- Map `beforeShellExecution` and `beforeMCPExecution` onto the canonical observational `PermissionRequest` hook without overriding Cursor's permission decision.
+- Wire `beforeShellExecution`, `beforeMCPExecution`, and `preToolUse` to the Agent
+  Session Module's blocking Decide capability (`ovld agent-session request`) per
+  the descriptor — Cursor has no single universal `PermissionRequest` event, so
+  do not route all three through one shared hook. See
+  `connectors/adapters/cursor/CAPABILITIES.md` for current per-capability status.
 - Add `postToolUse` edit capture for file tools and shell-mediated changes.
 - Add a bounded `stop` hook for pending-delivery reminders.
 - Add permission allow rules for protocol commands.
@@ -212,13 +216,24 @@ Requirements:
 - Records native session/resume ID when the harness exposes one.
 - Does not restart execution by itself.
 
-### Permission Hook
+### Permission Hook (Decide capability)
+
+This is the Agent Session Module's **Decide** capability, not a one-way event
+push. See `planning/feature-plans/agent-session-module.md` and
+`docs/src/content/docs/docs-for-agents/agent-sessions.mdx` for the current
+architecture; `connectors/HARNESS-MATRIX.md` for live per-adapter status.
 
 Requirements:
 
-- Publishes `permission_request` with tool/request payload.
+- Creates an answerable request (`ovld agent-session request`) carrying the
+  tool/request payload, one of the four request kinds (`permission`,
+  `question`, `choice`, `retry`), and a decision window.
+- Blocks the harness's tool call until the request is answered, the window
+  elapses, or a fallback decision applies — it does not merely publish an
+  event and continue.
 - Does not leak secrets.
-- Works without requiring a web app.
+- Degrades gracefully without a web app open: the harness's own fallback
+  decision (allow/deny/ask) applies when no one answers in time.
 
 ### Stop Hook
 

package/dist/index.js

@@ -22176,6 +22176,21 @@ dequeue-objective:
   Returns:
     { removed, objectiveId }. Already-unqueued objectives return removed: false.
 
+retry-queue-entry:
+  Purpose:
+    Retry one held Run Queue entry: clears its hold and resets the attempt
+    budget so the dispatcher tries it again on the next tick.
+  Required (one of):
+    --objective-id <id>         Objective UUID or display id with a live entry
+    --entry <id>                Entry UUID, objective UUID, or display id
+  Optional:
+    --project-id <id|slug|name> Confirms the entry's project
+  Returns:
+    The RunQueueEntryDto, back in waiting with attempt_count reset to 0.
+  Rules:
+    An entry already dispatched or running cannot be retried \u2014 remove it with
+    \`dequeue-objective\` (or a forced entry delete) first.
+
 search:
   Purpose:
     Find grouped mission, objective, and delivery matches by keyword, status type, or project.
@@ -22576,6 +22591,7 @@ var init_protocol_help = __esm({
       "run-queue",
       "queue-objective",
       "resume-follow-up",
+      "retry-queue-entry",
       "search",
       "search-missions",
       "sync-changes",