overlord-cli 0.2609091647.0 → 0.2609091820.0

package/dist/connectors/VERSION

@@ -1 +1 @@
-0.3.44
+0.3.45

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

@@ -1,4 +1,4 @@
-contractVersion: "139"
+contractVersion: "140"
 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.44",
+  "version": "0.3.45",
   "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.44",
+  "version": "0.3.45",
   "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: "139"
+contractVersion: "140"
 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.44",
+  "version": "0.3.45",
   "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: "139"
+contractVersion: "140"
 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.44",
+  "version": "0.3.45",
   "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: "139"
+contractVersion: "140"
 componentType: connector
 componentKey: cursor
 label: "Cursor Connector"

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

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

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

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

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

@@ -33,7 +33,12 @@ never include Git operations or routine review/testing. Every human action needs
 and `category`; add `command`, `verify`, and `link` whenever they exist so the operator can act
 without re-reading the delivery (see **Delivery Evidence** below). Tradeoffs record the
 implementation decision, alternatives considered, and rationale. Each `deferredWork` item
-should name the component or file involved and say why the work was left. These fields improve
+must be a recommended new objective that is not part of this mission (for example a bug
+discovered here that belongs outside it). Name the component or file involved and say why
+the work was left. Never list work already covered by this mission's future objectives,
+leftover slices of the current objective (add an objective to this mission instead), or
+human implementation follow-up such as deploy, secrets, or migrations (those belong in
+`humanActions`). Use an empty array when nothing qualifies. These fields improve
 review visibility but never block delivery.
 
 For full command syntax, flags, phase values, and event types see **CLI Command Reference** below.
@@ -207,8 +212,13 @@ Only list a human action when a person must perform a concrete non-Git step outs
 agent's completed work (for example, add a secret, run a production migration, deploy, or
 configure an external integration). Never list committing, pushing, opening a pull request,
 reviewing code, or ordinary tests. A tradeoff must state the decision, alternatives considered,
-and rationale. Each `deferredWork` item should name the component or file involved and say why
-the work was left. Omit the report when none of these facts apply.
+and rationale. Each `deferredWork` item must be a recommended new objective that is not
+part of this mission (for example a bug discovered here that belongs outside it). Name
+the component or file involved and say why the work was left. Never list work already
+covered by this mission's future objectives, leftover slices of the current objective
+(add an objective to this mission instead), or human implementation follow-up such as
+deploy, secrets, or migrations (those belong in `humanActions`). Use an empty array when
+nothing qualifies. Omit the report when none of these facts apply.
 
 #### Writing a human action the operator can complete
 

package/dist/connectors/core/overlord-mission/reference/record-work.md

@@ -60,8 +60,12 @@ identical across the CLI (`--payload-file -`) and the hosted MCP tool
   or `decision`.
 - **`deliveryReport`** (optional) — you may include a `deliveryReport.agentReport`
   (`humanActions`, `tradeoffsMade`, `knownRisks`, `deferredWork`, `assumptions`) just as
-  in `deliver`. Each `deferredWork` item should name the component or file involved and say
-  why the work was left. It improves review visibility but never blocks the record.
+  in `deliver`. Each `deferredWork` item must be a recommended new objective that is not
+  part of this mission (for example a bug discovered here that belongs outside it). Name
+  the component or file involved and say why the work was left. Never list work already
+  covered by this mission's future objectives, leftover slices of the current objective,
+  or human implementation follow-up (those belong in `humanActions`). Use an empty array
+  when nothing qualifies. It improves review visibility but never blocks the record.
 
 ## CLI
 

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

@@ -656,7 +656,7 @@ const tools = [
         deferredWork: {
           type: 'array',
           description:
-            'Intentionally deferred work. Name the component or file involved and say why the work was left.'
+            'Recommended new objective outside this mission (for example an out-of-scope bug). Name the component or file and why it was left. Omit queued future objectives, leftover current-objective work, and human follow-up (those belong in humanActions).'
         },
         assumptions: { type: 'array', description: 'Material implementation assumptions.' }
       },
@@ -1209,7 +1209,7 @@ process.stdin.on('data', async chunk => {
         result: {
           protocolVersion: PROTOCOL_VERSION,
           capabilities: { tools: { listChanged: false } },
-          serverInfo: { name: 'overlord-__OVERLORD_ADAPTER_KEY__', version: '0.3.44' }
+          serverInfo: { name: 'overlord-__OVERLORD_ADAPTER_KEY__', version: '0.3.45' }
         }
       });
       continue;

package/dist/index.js

@@ -38575,8 +38575,11 @@ deliver:
     The payload may also include deliveryReport: { schemaVersion: 1, agentReport: {
       humanActions, tradeoffsMade, knownRisks, deferredWork, assumptions } }. Use empty arrays
     when none apply. Human actions exclude Git operations and routine review/testing.
-    Each deferredWork item should name the component or file involved and say why the work
-    was left.
+    Deferred work is only a recommended new objective that is not part of this mission
+    (for example an out-of-scope bug). Name the component or file involved and say why
+    the work was left. Never list work already covered by this mission's future
+    objectives, leftover slices of the current objective, or human implementation
+    follow-up (those belong in humanActions). Use an empty array when nothing qualifies.
   Human action shape (each item in agentReport.humanActions):
     {
       "action":   "Add GEMINI_API_KEY to the production backend service on Railway.", // required. one imperative sentence: what, where, which value.