overlord-cli 0.2609091647.0 → 0.2609150845.0

package/dist/connectors/VERSION

@@ -1 +1 @@
-0.3.44
+0.3.46

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

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

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

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

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

@@ -1,4 +1,4 @@
-contractVersion: "139"
+contractVersion: "142"
 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.
@@ -77,9 +82,9 @@ Do not attach to a mission just because it was mentioned or opened in conversati
 
 Use this mode when the conversation starts normally and the user asks the agent to create, inspect, connect to, or otherwise use Overlord.
 
-1. If the user wants to create missions (and does not ask to start execution), run `ovld protocol create --agent <agent-identifier> --objectives-json '[{"objective":"..."}]'`.
+1. If the user wants to create missions (and does not ask to start execution), resolve the intended project and run `ovld protocol create --project-id <project-id> --agent <agent-identifier> --objectives-json '[{"objective":"..."}]'`.
    - When `--session-key` and `--mission-id` are provided, it creates a follow-up draft.
-   - When session flags are omitted, it resolves the project by matching current working directory (or `--working-directory`) to Overlord project resource directories, then creates a standalone draft.
+   - Creation never infers a project. If the user explicitly asks to capture work outside every project, use `--unassigned-to-project`; otherwise resolve a project first with `ovld protocol discover-project` and pass its id.
    - Pass multiple items in `--objectives-json` when creating ordered steps for the same feature or goal.
    - If the user wants to **add more objectives to an existing mission** (not create a new mission), use `ovld protocol add-objectives --mission-id <mission_id> --objectives-json '[{"objective":"..."}]'` instead.
 2. Default to `create` for new missions. Only use `ovld protocol prompt --agent <agent-identifier> --objectives-json '[{"objective":"..."}]'` when the user explicitly asks to create and execute immediately.
@@ -90,7 +95,7 @@ Use this mode when the conversation starts normally and the user asks the agent
 5. If the user wants to establish a persistent session with a mission by ID, run `ovld protocol attach --mission-id <mission_id>`.
 6. If the user wants to find a mission but does not know the ID, run `ovld protocol search-missions --query "..." --status execute,review` and ask the user to confirm.
 7. If you need to understand project routing before prompting, use `ovld protocol discover-project`.
-8. If the user wants to **record work that is already finished** in this chat (for example, something you just built in a chat app) as a completed mission, run `ovld protocol record-work` (or the hosted `overlord_record_work` MCP tool). This creates a mission with one completed objective, records explicitly supplied changed files and optional rationales, lands it in the review column, and runs the standard Gemini delivery summary — all in one call, with no `attach`/`deliver`. Do **not** use it for in-progress work. The exact submission format is in [reference/record-work.md](reference/record-work.md).
+8. If the user wants to **record work that is already finished** in this chat (for example, something you just built in a chat app) as a completed mission, run `ovld protocol record-work --project-id <project-id>` (or the hosted `overlord_record_work` MCP tool). This creates a mission with one completed objective, records explicitly supplied changed files and optional rationales, lands it in the review column, and runs the standard Gemini delivery summary — all in one call, with no `attach`/`deliver`. Do **not** use it for in-progress work. The exact submission format is in [reference/record-work.md](reference/record-work.md).
 9. If you need other lifecycle commands or flags, run `ovld protocol help` and use the real subcommand list instead of guessing.
 10. Once you attach to a mission, switch back to Mode 1 and follow the full mission lifecycle.
 
@@ -207,23 +212,28 @@ 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
 
 Human actions are collected across every mission into the Feed page's **Human actions** rail,
 where the operator reads them without the delivery context. Each item must stand alone:
 
-| Field      | Expected | What to write                                                                                  |
-| ---------- | -------- | ---------------------------------------------------------------------------------------------- |
-| `action`   | required | One imperative sentence naming the exact thing to do, where, and with what value.              |
-| `reason`   | expected | Why the step is needed and what breaks or stays incomplete until it is done.                   |
-| `category` | expected | `environment`, `database`, `deployment`, `codegen`, `packaging`, `external_service`, or `other`.|
-| `blocking` | optional | `true` when the delivered work does not function until this is done.                           |
+| Field      | Expected   | What to write                                                                                     |
+| ---------- | ---------- | ------------------------------------------------------------------------------------------------- |
+| `action`   | required   | One imperative sentence naming the exact thing to do, where, and with what value.                 |
+| `reason`   | expected   | Why the step is needed and what breaks or stays incomplete until it is done.                      |
+| `category` | expected   | `environment`, `database`, `deployment`, `codegen`, `packaging`, `external_service`, or `other`.  |
+| `blocking` | optional   | `true` when the delivered work does not function until this is done.                              |
 | `command`  | when known | The exact command, setting name, or value to apply, verbatim. Placeholders in `<angle brackets>`. |
-| `verify`   | when known | How the operator confirms it worked: a command to run, a URL to open, or the state to observe. |
-| `link`     | when known | An HTTP(S) URL or a repository-relative file path (never another URI scheme).                   |
+| `verify`   | when known | How the operator confirms it worked: a command to run, a URL to open, or the state to observe.    |
+| `link`     | when known | An HTTP(S) URL or a repository-relative file path (never another URI scheme).                     |
 
 Vague (the operator has to rediscover everything):
 
@@ -323,8 +333,8 @@ When creating missions from within a repository:
 
 - Prefer `create` by default for draft mission creation.
 - Use `prompt` only when the user explicitly asks to start execution immediately.
-- Both commands can resolve the project from the current working directory; use `--working-directory` to override or `--project-id` to be explicit.
-- 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`, `prompt`, and `record-work` require an explicit `--project-id`; use `discover-project` first when the project is known only from the checkout. They never infer a destination project.
+- Use `create --unassigned-to-project` only when the user deliberately requests an account-owned inbox capture. `--inbox` is a compatibility alias.
 - 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).
@@ -335,17 +345,18 @@ When creating missions from within a repository:
 - `create`, `prompt`, `create-mission`, and `record-work` accept `--assigned-to <member>` to set the mission's human owner. Accepts a username, an email, a user-id UUID, or the `orgid:username` member ID. When omitted, the assignee defaults to the mission creator.
 
 ```bash
-ovld protocol create --agent <agent-identifier> --objectives-json '[{"objective":"Capture follow-up work from this repository"}]'
+ovld protocol create --project-id <project-id> --agent <agent-identifier> --objectives-json '[{"objective":"Capture follow-up work from this repository"}]'
 ```
 
 ```bash
 # One call: a draft mission whose first objective is already assigned to Codex.
 ovld protocol create --agent <agent-identifier> \
+  --project-id <project-id> \
   --objectives-json '[{"objective":"Implement the API","agent":"codex","model":"gpt-5.6-terra"},{"objective":"Add CLI docs","agent":"claude"}]'
 ```
 
 ```bash
-ovld protocol prompt --agent <agent-identifier> --objectives-json '[{"objective":"Implement feature X"}]'
+ovld protocol prompt --project-id <project-id> --agent <agent-identifier> --objectives-json '[{"objective":"Implement feature X"}]'
 ```
 
 ```bash
@@ -403,8 +414,8 @@ When you need a project ID for a protocol command and the mission prompt did not
 **Locally (CLI inside a shell on the user's machine):**
 
 1. `--project-id` if explicitly provided.
-2. Otherwise, let the CLI match the current working directory (the default behavior of `create`, `prompt`, `discover-project`).
-3. If working-directory resolution returns nothing, read `.overlord/project.json` from the cwd (or any ancestor you have access to). Select the `projects[]` entry with `isPrimary: true` and pass its id via `--project-id`. If the array or primary entry is missing, treat the metadata as invalid and run `ovld doctor`; do not fall back to a top-level projection. To associate missions with a different linked project, pass that project's id explicitly.
+2. Otherwise, run `ovld protocol discover-project` for the current working directory, then pass its returned id via `--project-id`.
+3. If discovery returns nothing, read `.overlord/project.json` from the cwd (or any ancestor you have access to). Select the `projects[]` entry with `isPrimary: true` and pass its id via `--project-id`. If the array or primary entry is missing, treat the metadata as invalid and run `ovld doctor`; do not fall back to a top-level projection. To associate missions with a different linked project, pass that project's id explicitly.
 
 **Over MCP (web agents and hosted tools, where the server cannot see the agent's cwd):**
 

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

@@ -175,8 +175,8 @@ When creating missions from within a repository:
 
 - Prefer `create` by default for draft mission creation.
 - Use `prompt` only when the user explicitly asks to start execution immediately.
-- Both commands can resolve the project from the current working directory; use `--working-directory` to override or `--project-id` to be explicit.
-- 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`, `prompt`, and `record-work` require an explicit `--project-id`; use `discover-project` first when the project is known only from the checkout. They never infer a destination project.
+- Use `create --unassigned-to-project` only when the user deliberately requests an account-owned inbox capture. `--inbox` is a compatibility alias.
 - 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` map each opted-in item to authoritative Run Queue membership (default off).
@@ -186,17 +186,18 @@ When creating missions from within a repository:
 - `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
-ovld protocol create --agent <agent-identifier> --objectives-json '[{"objective":"Capture follow-up work from this repository"}]'
+ovld protocol create --project-id <project-id> --agent <agent-identifier> --objectives-json '[{"objective":"Capture follow-up work from this repository"}]'
 ```
 
 ```bash
 # One call: a draft mission whose first objective is already assigned to Codex.
 ovld protocol create --agent <agent-identifier> \
+  --project-id <project-id> \
   --objectives-json '[{"objective":"Implement the API","agent":"codex","model":"gpt-5.6-terra"},{"objective":"Add CLI docs","agent":"claude"}]'
 ```
 
 ```bash
-ovld protocol prompt --agent <agent-identifier> --objectives-json '[{"objective":"Implement feature X"}]'
+ovld protocol prompt --project-id <project-id> --agent <agent-identifier> --objectives-json '[{"objective":"Implement feature X"}]'
 ```
 
 ```bash
@@ -277,8 +278,8 @@ When you need a project ID for a protocol command and the mission prompt did not
 **Locally (CLI inside a shell on the user's machine):**
 
 1. `--project-id` if explicitly provided.
-2. Otherwise, let the CLI match the current working directory (the default behavior of `create`, `prompt`, `discover-project`).
-3. If working-directory resolution returns nothing, read `.overlord/project.json` from the cwd (or any ancestor you have access to). Select the `projects[]` entry with `isPrimary: true` and pass its id via `--project-id`. If the array or primary entry is missing, treat the metadata as invalid and run `ovld doctor`; do not fall back to a top-level projection. To associate missions with a different linked project, pass that project's id explicitly.
+2. Otherwise, run `ovld protocol discover-project` for the current working directory, then pass its returned id via `--project-id`.
+3. If discovery returns nothing, read `.overlord/project.json` from the cwd (or any ancestor you have access to). Select the `projects[]` entry with `isPrimary: true` and pass its id via `--project-id`. If the array or primary entry is missing, treat the metadata as invalid and run `ovld doctor`; do not fall back to a top-level projection. To associate missions with a different linked project, pass that project's id explicitly.
 
 **Over MCP (web agents and hosted tools, where the server cannot see the agent's cwd):**
 

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

@@ -7,7 +7,8 @@
 - `permission-request` is invoked by connector permission hooks installed by adapter bundles. Agents do not normally call it directly.
 - Execution request tools (`request_execution`, `claim_execution`, `list_execution_requests`, `clear_execution_requests`, `complete_execution_launch`, `fail_execution_launch`) back the local runner queue. Agents normally work missions with `attach`/`update`/`deliver`; runner processes use these queue tools.
 - Change rationales are optional annotations attached to `update` or `deliver` (`--change-rationales-json` / `--change-rationales-file`, or `changeRationales` over MCP) and stored as `change_rationales` rows. Normal delivery requires only a summary; objective-ledger evidence is captured locally and synchronized independently.
-- `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, explicitly supplied changed files, optional 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_create_mission` requires `projectId` for a mission, unless `unassignedToProject: true` deliberately requests an account-owned inbox item; omission of both is rejected. `overlord_create_inbox_item` is also explicit by name.
+- `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, explicitly supplied changed files, optional rationales, and the standard Gemini delivery summary — no `attach`/`deliver`. Both require an explicit project reference. 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_delete_missions` / `overlord_delete_objectives` (hosted MCP) and `ovld protocol delete-missions` / `delete-objectives` (CLI) bulk soft-delete one to 100 mission or objective UUID/display-id references atomically. They require `confirm: true` / `--confirm`; before setting it, agents must show the resolved list to the user and receive affirmative approval. A missing, duplicate, deleted, or unauthorized target rejects the entire request. Mission deletion includes live child objectives; objective deletion removes live Run Queue membership.

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

@@ -257,10 +257,15 @@ const tools = [
     name: 'overlord_create_mission',
     title: 'Create Overlord mission',
     description:
-      'Create a draft mission in projectId, or an account-owned inbox item when projectId is omitted. This connector never chooses a project implicitly.',
+      'Create a draft mission with projectId. To intentionally create an account-owned inbox item, set unassignedToProject to true; omission of both is rejected.',
     inputSchema: objectSchema(
       {
-        projectId: stringProperty('Optional Overlord project id, slug, or name.'),
+        projectId: stringProperty(
+          'Overlord project id, slug, or name. Required unless unassignedToProject is true.'
+        ),
+        unassignedToProject: booleanProperty(
+          'Set true only to intentionally create an account-owned inbox item instead of a project mission. Cannot be combined with projectId.'
+        ),
         objective: stringProperty('Initial objective text.'),
         title: stringProperty('Optional mission title.'),
         resourceKey: stringProperty('Optional logical project resource key for the objective.'),
@@ -271,7 +276,7 @@ const tools = [
           'Optional model identifier for the assigned agent. Requires agent; rejected without it.'
         ),
         assignedTo: stringProperty(
-          'Optional workspace member to own the mission (workspace_users.id, profile UUID, orgid:username, bare username, or email). Rejected when the member is not in the workspace; meaningless on the inbox fallback.'
+          'Optional workspace member to own the mission (workspace_users.id, profile UUID, orgid:username, bare username, or email). Rejected when the member is not in the workspace; meaningless for an unassigned inbox item.'
         ),
         autoAdvance: booleanProperty(
           'When true, Overlord queues the next objective for execution after this one is delivered. Defaults to false.'
@@ -634,14 +639,27 @@ const tools = [
           items: {
             type: 'object',
             properties: {
-              action: { type: 'string', description: 'Required. One imperative sentence: what, where, which value.' },
-              reason: { type: 'string', description: 'Expected. Why it is needed and what stays broken until done.' },
+              action: {
+                type: 'string',
+                description: 'Required. One imperative sentence: what, where, which value.'
+              },
+              reason: {
+                type: 'string',
+                description: 'Expected. Why it is needed and what stays broken until done.'
+              },
               category: {
                 type: 'string',
-                description: 'Expected. environment, database, deployment, codegen, packaging, external_service, or other.'
+                description:
+                  'Expected. environment, database, deployment, codegen, packaging, external_service, or other.'
+              },
+              blocking: {
+                type: 'boolean',
+                description: 'True when the delivered work does not function until this is done.'
+              },
+              command: {
+                type: 'string',
+                description: 'Exact command, setting, or value to apply, verbatim.'
               },
-              blocking: { type: 'boolean', description: 'True when the delivered work does not function until this is done.' },
-              command: { type: 'string', description: 'Exact command, setting, or value to apply, verbatim.' },
               verify: { type: 'string', description: 'How the operator confirms it worked.' },
               link: { type: 'string', description: 'HTTP(S) URL or repository-relative file path.' }
             },
@@ -656,7 +674,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.' }
       },
@@ -852,7 +870,8 @@ async function callOverlordTool(name, args) {
     return runProtocol('create', {
       ...(optionalString(args, 'projectId')
         ? { 'project-id': requiredString(args, 'projectId') }
-        : { inbox: true }),
+        : {}),
+      ...(args.unassignedToProject === true ? { 'unassigned-to-project': true } : {}),
       objective: requiredString(args, 'objective'),
       ...(optionalString(args, 'title') ? { title: requiredString(args, 'title') } : {}),
       ...(optionalString(args, 'resourceKey')
@@ -873,7 +892,7 @@ async function callOverlordTool(name, args) {
   }
   if (name === 'overlord_create_inbox_item') {
     return runProtocol('create', {
-      inbox: true,
+      'unassigned-to-project': true,
       title: requiredString(args, 'title'),
       objective: requiredString(args, 'objective')
     });
@@ -1209,7 +1228,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.46' }
         }
       });
       continue;

package/dist/index.js

@@ -38450,15 +38450,16 @@ delete-objectives:
 
 create:
   Purpose:
-    Create a draft mission without attaching. Without --project-id and
-    without a resolvable working-directory project, falls back to an
-    account-owned inbox item instead of failing.
+    Create a draft mission without attaching. A project must be named
+    explicitly; use --unassigned-to-project only for deliberate account-owned
+    inbox capture.
   Required:
     --objective "<text>" or --objectives-json / --objectives-file <path|->
   Optional:
     --title <text>
-    --project-id <id>           Skips working-directory project resolution
-    --inbox                     Force an account-owned inbox item instead of a project mission
+    --project-id <id>           Required for a project mission; never inferred
+    --unassigned-to-project     Intentionally create an account-owned inbox item
+    --inbox                     Compatibility alias for --unassigned-to-project
     --assigned-to <id>          Workspace member to own the mission (meaningless on the inbox fallback)
     --auto-advance / --no-auto-advance
         Add matching objectives to the authoritative Run Queue. Defaults to off.
@@ -38475,9 +38476,9 @@ prompt:
     Create a mission and attach to it in one call.
   Required:
     --objective "<text>" or --objectives-json / --objectives-file <path|->
+    --project-id <id>
   Optional:
     --title <text>
-    --project-id <id>
     --agent <identifier>
     --model <identifier>
     --external-session-id <id>
@@ -38501,9 +38502,9 @@ record-work:
   Required:
     --objective "<text>" (or positional, or an "objective" field in --payload-json)
     --summary or --summary-file <path|->
+    --project-id <id>
   Optional:
     --title <text>
-    --project-id <id>
     --assigned-to <id>          Workspace member to own the mission
     --artifacts-json / --artifacts-file <path|->
     --change-rationales-json / --change-rationales-file <path|->
@@ -38575,8 +38576,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.