overlord-cli 0.2608191901.0 → 0.2608200954.0

package/dist/connectors/VERSION

@@ -1 +1 @@
-0.3.29
+0.3.31

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

@@ -1,7 +1,7 @@
 {
   "$schema": "https://antigravity.google/schemas/v1/plugin.json",
   "name": "overlord",
-  "version": "0.3.29",
+  "version": "0.3.31",
   "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.29",
+  "version": "0.3.31",
   "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.29",
+  "version": "0.3.31",
   "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.29",
+  "version": "0.3.31",
   "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/reference/cli.md

@@ -179,9 +179,10 @@ When creating missions from within a repository:
 - Follow-up `create` calls under an active session inherit the current mission's project by default, but `--project-id` can override that when the follow-up belongs in a different project.
 - Create multiple missions when each prompt represents a different feature or goal.
 - Add objectives to the same mission when each prompt is a sequential step toward the same feature or goal; use `ovld protocol add-objectives --mission-id <mission_id> --objectives-json '[{"objective":"..."}]'`.
-- `create` and `prompt` require `--objectives-json` or `--objectives-file` with an ordered array of `{ "objective": "...", "title": "...", "autoAdvance": true }` objects. A single objective is just an array with one item. `--auto-advance` / `--no-auto-advance` set the default when an item omits `autoAdvance` (default off).
-- `add-objectives` uses the same per-item `autoAdvance` field and `--auto-advance` / `--no-auto-advance` default.
-- To change auto-advance on an existing objective: `ovld protocol update-objective --objective-id <id> --auto-advance` or `--no-auto-advance`.
+- `create` and `prompt` require `--objectives-json` or `--objectives-file` with an ordered array of `{ "objective": "...", "title": "...", "autoAdvance": true }` objects. A single objective is just an array with one item. `--auto-advance` / `--no-auto-advance` map each opted-in item to authoritative Run Queue membership (default off).
+- `add-objectives` uses the same per-item `autoAdvance` field and `--auto-advance` / `--no-auto-advance` mapping.
+- Use `ovld protocol queue-objective --objective-id <id> [--queue <id|name>] [--after <queued-entry|objective>|--front|--position <rank>]` to explicitly enqueue or move work, `dequeue-objective --objective-id <id>` to remove it, and `run-queue --project-id <id|slug|name>` to inspect every queue.
+- `ovld protocol update-objective --objective-id <id> --auto-advance` / `--no-auto-advance` is retained as an enqueue/dequeue compatibility mapping. `autoAdvance` is deprecated and derived from `queueEntry`; legacy writes retire next release and column removal requires a later contract bump.
 - `record-work` creates exactly one **completed** objective from a single `--objective` (or positional / an `objective` field in `--payload-json`) plus a `--summary` and file-change data — it does not take `--objectives-json`. See [record-work.md](record-work.md).
 
 ```bash

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

@@ -10,6 +10,6 @@
 - `overlord_record_work` (hosted MCP) and `ovld protocol record-work` (CLI) record already-completed chat work as a single review-column mission with a completed objective, file-change rationales, and the standard Gemini delivery summary — no `attach`/`deliver`. Hosted MCP requires `projectId` (it never chooses a project implicitly); the CLI resolves the project from the working directory or `--project-id`. The submission format is in [record-work.md](record-work.md). The route is `POST /api/protocol/record-work`.
 - `overlord_add_artifact` (hosted MCP) and `ovld protocol add-artifact` (CLI) create a mission artifact during a turn without delivering. Required: `type` / `--type`, `label` / `--label`, mission scope (`missionId` / `--mission-id`, or an objective display id as `objectiveId` / `--objective-id`), plus at least one of `contentText` / `--content-text`/`--content-text-file` or `externalUrl` / `--external-url`. Optional `sessionKey` / `--session-key` stamps session/objective provenance; `objectiveId` / `--objective-id` does the same when there is no live session, and the session key wins if both are given. Same service as REST `POST /api/missions/:id/artifacts`. The route is `POST /api/protocol/add-artifact`.
 - `overlord_update_artifact` (hosted MCP) and `ovld protocol update-artifact` (CLI) revise an existing mission artifact's label, Markdown content, and/or HTTP(S) URL in place. Required: `artifactId` / `--artifact-id`, `expectedRevision` / `--expected-revision`, and mission scope (`missionId` / `--mission-id`, or an objective display id as `objectiveId` / `--objective-id`). Provide at least one editable field. No session key is required. Same service as REST `PATCH /api/missions/:id/artifacts/:artifactId`. The route is `POST /api/protocol/update-artifact`.
-- `overlord_create_mission` / `overlord_add_objectives` accept optional `autoAdvance` (boolean; default false). `overlord_update_objective` (`objectiveId` plus optional `autoAdvance` and/or `instructionText`) and `ovld protocol update-objective --objective-id <id>` with `--auto-advance|--no-auto-advance` and/or `--instruction-text|--instruction-text-file` update an existing objective. Instruction text is editable only in `draft` or `future` state. The route is `POST /api/protocol/update-objective`.
+- `overlord_queue_objective` accepts `objectiveId`, optional `queue` / `after`, and `remove`; it forwards through Protocol to authoritative Run Queue membership and never directly launches work. `overlord_create_mission` / `overlord_add_objectives` optional `autoAdvance`, `overlord_update_objective.autoAdvance`, and `ovld protocol update-objective --auto-advance|--no-auto-advance` map to that same membership. `autoAdvance` is deprecated and derived from `queueEntry`; legacy storage writes retire next release and column removal requires a later contract bump. Instruction text remains editable only in `draft` or `future` state. The routes are `POST /api/protocol/queue-objective`, `dequeue-objective`, and `update-objective`.
 - Objective attachment tools follow the `<verb>_<noun>` MCP naming: `list_attachments`, `prepare_attachment_upload`, `finalize_attachment_upload`, `get_attachment_download_url`, `upload_attachment_file`. CLI commands use `attachment-*`. `mission_id` / `missionId` is optional for attachment calls when the objective or attachment id lets the server derive mission scope.
 - "Artifacts" may be published mid-turn with `add-artifact` / `overlord_add_artifact`, revised with `update-artifact` / `overlord_update_artifact`, or attached at `deliver` time (next_steps, test_results, migration, decision, note, url) — not user-uploaded files. Files attached by users live on objectives via the attachment tools above.

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

@@ -258,6 +258,58 @@ const tools = [
       []
     )
   },
+  {
+    name: 'overlord_list_deliveries',
+    title: 'List mission deliveries',
+    description:
+      'Use this to read a mission\'s delivered work after locating it. Returns newest-first normalized delivery records including summary, verification, follow-up notes, and authoritative delivery evidence; it never exposes raw delivery payloads.',
+    inputSchema: objectSchema({
+      missionId: stringProperty(
+        'Mission UUID or workspace display id. Optional when objectiveId is a display id such as coo:756.k7xm, which already names its mission.'
+      ),
+      objectiveId: stringProperty(
+        'Objective UUID or display id such as coo:756.k7xm. Use a display id when that is the only identifier available.'
+      )
+    })
+  },
+  {
+    name: 'overlord_launch_objective',
+    title: 'Launch objective execution',
+    description:
+      'Use this only when the user explicitly asks to start a particular objective. It queues the normal Overlord execution request; it does not attach this MCP agent to perform the work. An existing active request is returned instead of duplicated.',
+    inputSchema: objectSchema(
+      {
+        objectiveId: stringProperty('Objective UUID or display id such as coo:756.k7xm.'),
+        agent: stringProperty('Agent identifier to launch, such as codex or claude.'),
+        model: stringProperty('Optional model identifier to snapshot onto the execution request.'),
+        reasoningEffort: stringProperty(
+          'Optional reasoning-effort setting to snapshot onto the execution request.'
+        ),
+        executionTargetId: stringProperty(
+          'Optional eligible execution target id. Omit to use the project\'s normal target selection.'
+        )
+      },
+      ['objectiveId', 'agent']
+    )
+  },
+  {
+    name: 'overlord_reorder_future_objectives',
+    title: 'Reorder future objectives',
+    description:
+      'Use this only when the user explicitly asks to change future-objective order in one mission. Supply every future objective UUID in its complete desired top-to-bottom order; draft, active, and completed objectives cannot be moved by this tool.',
+    inputSchema: objectSchema(
+      {
+        missionId: stringProperty('Mission UUID.'),
+        orderedObjectiveIds: {
+          type: 'array',
+          description:
+            'Complete desired top-to-bottom UUID order of every objective currently in the future state.',
+          items: stringProperty('Future objective UUID.')
+        }
+      },
+      ['missionId', 'orderedObjectiveIds']
+    )
+  },
   {
     name: 'overlord_add_objectives',
     title: 'Add objectives',
@@ -305,6 +357,25 @@ const tools = [
       ['objectiveId']
     )
   },
+  {
+    name: 'overlord_queue_objective',
+    title: 'Queue objective',
+    description:
+      'Use this only when the user explicitly asks to add, move, or remove an objective in the project Run Queue. Queue membership is target-neutral and sequences delivery-driven launches; it does not directly launch the objective.',
+    inputSchema: objectSchema(
+      {
+        objectiveId: stringProperty('Objective UUID or display id such as coo:756.k7xm.'),
+        queue: stringProperty('Optional Run Queue UUID or unambiguous queue name.'),
+        after: stringProperty(
+          'Optional queued predecessor entry id, objective UUID, or objective display id. Its queue is used when queue is omitted.'
+        ),
+        remove: booleanProperty(
+          'When true, remove this objective from the Run Queue instead of adding or moving it.'
+        )
+      },
+      ['objectiveId']
+    )
+  },
   {
     name: 'overlord_attach_session',
     title: 'Attach to mission',
@@ -602,6 +673,31 @@ async function callOverlordTool(name, args) {
         : {})
     });
   }
+  if (name === 'overlord_list_deliveries') {
+    return runProtocol('list-deliveries', missionScopeFlags(args));
+  }
+  if (name === 'overlord_launch_objective') {
+    return runProtocol('launch-objective', {
+      'objective-id': requiredString(args, 'objectiveId'),
+      agent: requiredString(args, 'agent'),
+      ...(optionalString(args, 'model') ? { model: requiredString(args, 'model') } : {}),
+      ...(optionalString(args, 'reasoningEffort')
+        ? { 'reasoning-effort': requiredString(args, 'reasoningEffort') }
+        : {}),
+      ...(optionalString(args, 'executionTargetId')
+        ? { 'execution-target-id': requiredString(args, 'executionTargetId') }
+        : {})
+    });
+  }
+  if (name === 'overlord_reorder_future_objectives') {
+    if (!Array.isArray(args.orderedObjectiveIds)) {
+      throw new Error('orderedObjectiveIds must be an array');
+    }
+    return runProtocol('reorder-future-objectives', {
+      'mission-id': requiredString(args, 'missionId'),
+      'ordered-objective-ids-json': args.orderedObjectiveIds
+    });
+  }
   if (name === 'overlord_add_objectives') {
     if (!Array.isArray(args.objectives)) throw new Error('objectives must be an array');
     return runProtocol('add-objectives', {
@@ -625,6 +721,17 @@ async function callOverlordTool(name, args) {
       ...(hasInstructionText ? { 'instruction-text': requiredString(args, 'instructionText') } : {})
     });
   }
+  if (name === 'overlord_queue_objective') {
+    return runProtocol(args.remove === true ? 'dequeue-objective' : 'queue-objective', {
+      'objective-id': requiredString(args, 'objectiveId'),
+      ...(args.remove === true
+        ? {}
+        : {
+            ...(optionalString(args, 'queue') ? { queue: requiredString(args, 'queue') } : {}),
+            ...(optionalString(args, 'after') ? { after: requiredString(args, 'after') } : {})
+          })
+    });
+  }
   if (name === 'overlord_attach_session') {
     return runProtocol('attach', {
       ...missionScopeFlags(args),
@@ -762,7 +869,7 @@ process.stdin.on('data', async chunk => {
         result: {
           protocolVersion: PROTOCOL_VERSION,
           capabilities: { tools: { listChanged: false } },
-          serverInfo: { name: 'overlord-__OVERLORD_ADAPTER_KEY__', version: '0.3.29' }
+          serverInfo: { name: 'overlord-__OVERLORD_ADAPTER_KEY__', version: '0.3.31' }
         }
       });
       continue;

package/dist/index.js

@@ -21027,6 +21027,80 @@ load-context:
                                 rediscovering the mission's active objective. Required
                                 on a mission running objectives in parallel.
 
+list-deliveries:
+  Purpose:
+    Read one mission's newest-first normalized delivery records without exposing
+    arbitrary stored payload JSON.
+  Required:
+    --mission-id <id>            Or --objective-id with a display id
+  Optional:
+    --objective-id <id>         Supplies mission addressing when it is a display id
+  Returns:
+    DeliveryDto[] including summary, verification, follow-up notes, and normalized
+    delivery report evidence.
+
+launch-objective:
+  Purpose:
+    Queue the normal execution request for one objective. This does not attach the
+    calling agent; a runner or eligible execution target performs the requested launch.
+  Required:
+    --objective-id <id>         Objective UUID or display id
+    --agent <identifier>
+  Optional:
+    --model <identifier>
+    --reasoning-effort <value>
+    --execution-target-id <id>
+  Returns:
+    The queued or already-active ExecutionRequestDto. Existing launchability,
+    authorization, target resolution, sibling, and idempotency rules apply.
+
+reorder-future-objectives:
+  Purpose:
+    Change the order of one mission's future objectives without moving draft,
+    active, or complete objectives.
+  Required:
+    --mission-id <uuid>
+    --ordered-objective-ids-json <json>
+  Returns:
+    The mission's full ObjectiveDto[] list in its new order.
+  Rules:
+    Supply every future objective UUID in the complete desired top-to-bottom order.
+    Duplicate, missing, and non-future objective ids are rejected.
+
+run-queue:
+  Purpose:
+    Read every live Run Queue in one project, including queued, held, and running entries.
+  Required:
+    --project-id <id|slug|name>
+  Returns:
+    ProjectRunQueuesDto JSON. This reads sequencing state; it does not launch work.
+
+queue-objective:
+  Purpose:
+    Add or move one objective in the authoritative Run Queue without choosing a target.
+  Required:
+    --objective-id <id>         Objective UUID or display id
+  Optional:
+    --project-id <id|slug|name> Confirms the objective's project
+    --queue <id|name>           Queue UUID or unambiguous queue name
+    --after <entry|objective>   Queue after this queued entry/objective
+    --front                     Place first in the selected/default queue
+    --position <n>              One-based insertion rank
+  Rules:
+    Choose at most one of --after, --front, and --position. Without --queue,
+    --after selects its queue; otherwise the default queue is used. Re-running
+    without placement is idempotent.
+
+dequeue-objective:
+  Purpose:
+    Remove one objective from the authoritative Run Queue.
+  Required:
+    --objective-id <id>         Objective UUID or display id
+  Optional:
+    --project-id <id|slug|name> Confirms the objective's project
+  Returns:
+    { removed, objectiveId }. Already-unqueued objectives return removed: false.
+
 search:
   Purpose:
     Find grouped mission, objective, and delivery matches by keyword, status type, or project.
@@ -21099,7 +21173,7 @@ add-objectives:
 
 update-objective:
   Purpose:
-    Turn auto-advance on or off and/or edit instruction text on an existing objective.
+    Queue or dequeue compatibility auto-advance and/or edit instruction text on an existing objective.
   Required:
     --objective-id <id>
     At least one of:
@@ -21109,7 +21183,7 @@ update-objective:
     Instruction text may be edited only when the objective is in draft or future state.
     Blank instruction text is allowed in those states.
   Returns:
-    The updated objective JSON, including autoAdvance and instructionText.
+    The updated objective JSON. autoAdvance is deprecated and derived from live queueEntry membership.
 
 create:
   Purpose:
@@ -21124,7 +21198,7 @@ create:
     --inbox                     Force an account-owned inbox item instead of a project mission
     --assigned-to <id>          Workspace member to own the mission (meaningless on the inbox fallback)
     --auto-advance / --no-auto-advance
-        Queue the next objective after this one is delivered. Defaults to off.
+        Add matching objectives to the authoritative Run Queue. Defaults to off.
         Per-item override: "autoAdvance": true|false in --objectives-json items.
 
 prompt:
@@ -21140,7 +21214,7 @@ prompt:
     --external-session-id <id>
     --assigned-to <id>          Workspace member to own the mission
     --auto-advance / --no-auto-advance
-        Queue the next objective after this one is delivered. Defaults to off.
+        Add matching objectives to the authoritative Run Queue. Defaults to off.
         Per-item override: "autoAdvance": true|false in --objectives-json items.
   Returns:
     New mission/session JSON plus SESSION_KEY on stderr when available.
@@ -21404,17 +21478,23 @@ var init_protocol_help = __esm({
       "changes",
       "connect",
       "create",
+      "dequeue-objective",
       "deliver",
       "discover-project",
       "discuss-objective",
       "heartbeat",
       "hook-event",
+      "launch-objective",
+      "list-deliveries",
       "list-organizations",
       "load-context",
       "prompt",
       "read-context",
       "record-touched",
       "record-work",
+      "reorder-future-objectives",
+      "run-queue",
+      "queue-objective",
       "resume-follow-up",
       "search",
       "search-missions",
@@ -25038,7 +25118,8 @@ Agents:
   ${primaryCommand} launch <agent> --mission-id <missionId>
   Use ${primaryCommand} protocol help for the full mission lifecycle reference.
   Key protocol commands: auth-status, discover-project, create, prompt, attach,
-  connect, load-context, update, heartbeat, ask, deliver.
+  connect, load-context, list-deliveries, launch-objective, reorder-future-objectives,
+  update, heartbeat, ask, deliver.
 
 Protocol (JSON output by default):
   ${primaryCommand} protocol attach --mission-id <id> | --objective-id <display-id>
@@ -25049,6 +25130,9 @@ Protocol (JSON output by default):
   ${primaryCommand} protocol search --query "<text>" --status execute,review
   ${primaryCommand} protocol statuses --project-id <id|slug|name>
   ${primaryCommand} protocol load-context --mission-id <id>
+  ${primaryCommand} protocol list-deliveries --mission-id <id>
+  ${primaryCommand} protocol launch-objective --objective-id <id> --agent <agent>
+  ${primaryCommand} protocol reorder-future-objectives --mission-id <id> --ordered-objective-ids-json '["<id>"]'
   ${primaryCommand} protocol help
 
 After installation, run \`${primaryCommand} auth login\` to choose your backend.