overlord-cli 0.2607231225.0 → 0.2607241654.0

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

@@ -35,6 +35,7 @@ connector:
     - "skills/spawn.md"
     - "skills/overlord-mission/SKILL.md"
     - "skills/overlord-mission/reference/cli.md"
+    - "skills/overlord-mission/reference/record-work.md"
     - "skills/overlord-mission/reference/context.md"
     - "skills/overlord-mission/reference/devices.md"
     - "skills/overlord-mission/reference/mcp.md"

package/dist/connectors/adapters/antigravity/scripts/overlord-mcp.mjs

@@ -234,6 +234,33 @@ const tools = [
       },
       ['missionId', 'sessionKey', 'summary']
     )
+  },
+  {
+    name: 'overlord_record_work',
+    title: 'Record completed work as a mission',
+    description:
+      'Record work already completed in this chat as a mission that lands in review — one call, no attach/deliver cycle. Records file-change rationales and runs the delivery through the standard Gemini summarizer.',
+    inputSchema: objectSchema(
+      {
+        projectId: stringProperty('Overlord project id, slug, or name.'),
+        objective: stringProperty('What was asked and done, phrased as a completed objective.'),
+        summary: stringProperty('Reviewer-facing narrative of what changed and why.'),
+        title: stringProperty('Optional mission title.'),
+        changeRationales: {
+          type: 'array',
+          description: 'One entry per meaningful file change (filePath, label, summary, why, impact).'
+        },
+        changedFiles: {
+          type: 'array',
+          description: 'Optional extra touched files without a full rationale.'
+        },
+        artifacts: {
+          type: 'array',
+          description: 'Optional artifacts: next_steps, test_results, decision, note, or url.'
+        }
+      },
+      ['projectId', 'objective', 'summary']
+    )
   }
 ];
 
@@ -360,6 +387,21 @@ function callOverlordTool(name, args) {
         : {})
     });
   }
+  if (name === 'overlord_record_work') {
+    return runProtocol('record-work', {
+      'project-id': requiredString(args, 'projectId'),
+      payload: {
+        objective: requiredString(args, 'objective'),
+        summary: requiredString(args, 'summary'),
+        ...(optionalString(args, 'title') ? { title: requiredString(args, 'title') } : {}),
+        ...(Array.isArray(args.changeRationales)
+          ? { changeRationales: args.changeRationales }
+          : {}),
+        ...(Array.isArray(args.changedFiles) ? { changedFiles: args.changedFiles } : {}),
+        ...(Array.isArray(args.artifacts) ? { artifacts: args.artifacts } : {})
+      }
+    });
+  }
   if (name === 'attach') {
     return runProtocol('attach', { 'mission-id': args.mission_id });
   }

package/dist/connectors/adapters/antigravity/skills/record-work.md

@@ -4,10 +4,14 @@ description: Record completed-from-chat work as a mission in review, with a feed
 
 Immediately record the work you just completed in this chat as a new Overlord mission via `ovld protocol record-work`. No agent session is opened — the work is already done.
 
+This creates a mission with one completed objective, records the file changes with rationales, lands it in the review column, and runs the standard Gemini delivery summary.
+
 Synthesize from the current conversation:
 - `objective`: what was asked / what was done (1-3 sentences).
 - `summary`: reviewer-friendly narrative of what changed and why.
-- `changeRationales`: one entry per meaningful git-tracked file change (`label`, `file_path`, `summary`, `why`, `impact`, optional `hunks`). Use `git status` and `git diff` to enumerate changed files.
+- `changeRationales`: one entry per meaningful git-tracked file change (`file_path`, `label`, `summary`, `why`, `impact`, optional `hunks`). Use `git status` and `git diff` to enumerate changed files. Every listed file shows as "covered" in review.
+- `changedFiles` (optional): touched files without a full rationale (`filePath`, optional `vcsStatus`).
+- `title` (optional): mission title; defaults to a title derived from the objective.
 - `artifacts` (optional): `next_steps`, `test_results`, `decision`, `note`, `url`.
 
 If a command argument is present, treat it as additional context to weave into the summary.
@@ -21,5 +25,5 @@ After the command succeeds, report the new `MISSION_ID`.
 
 Rules:
 - Do NOT use this for in-progress work. Use `/prompt` for that.
-- The CLI validates that every changed git-tracked file is represented in `changeRationales` unless `--skip-file-change-check` is passed.
-- If project resolution fails, re-run with `--project-id <id-or-name>` or `--personal`.
+- If project resolution fails, re-run with `--project-id <id-or-name>`.
+- The exact submission format is documented in `skills/overlord-mission/reference/record-work.md`.

package/dist/connectors/adapters/claude/commands/record-work.md

@@ -1,15 +1,17 @@
 ---
-description: Record completed-from-chat work as a mission in review + feed post (no attach)
+description: Record completed-from-chat work as a mission in review (no attach)
 argument-hint: [optional additional context]
 disable-model-invocation: true
 ---
 
-Immediately record the work you just completed in this chat as a new Overlord mission via `ovld protocol record-work`. No agent session is opened — the work is already done.
+Immediately record the work you just completed in this chat as a new Overlord mission via `ovld protocol record-work`. No agent session is opened — the work is already done. This creates a mission with one completed objective, records the file changes with rationales, lands it in the review column, and runs the standard Gemini delivery summary.
 
 Synthesize from the current conversation:
 - `objective`: what was asked / what was done (1–3 sentences).
 - `summary`: reviewer-friendly narrative of what changed and why.
-- `changeRationales`: one entry per meaningful git-tracked file change (`label`, `file_path`, `summary`, `why`, `impact`, optional `hunks`). Use `git status` and `git diff` to enumerate changed files.
+- `changeRationales`: one entry per meaningful git-tracked file change (`file_path`, `label`, `summary`, `why`, `impact`, optional `hunks`). Use `git status` and `git diff` to enumerate changed files. Every listed file shows as "covered" in review.
+- `changedFiles` (optional): touched files you are not writing a full rationale for (`filePath`, optional `vcsStatus`).
+- `title` (optional): mission title; defaults to a title derived from the objective.
 - `artifacts` (optional): `next_steps`, `test_results`, `decision`, `note`, `url`.
 
 If `$ARGUMENTS` is non-empty, treat it as additional context to weave into the summary.
@@ -17,13 +19,15 @@ If `$ARGUMENTS` is non-empty, treat it as additional context to weave into the s
 Run:
 `ovld protocol record-work --payload-file -`
 
-and stream a JSON object `{ "objective": "...", "summary": "...", "artifacts": [...], "changeRationales": [...] }` on stdin via a single-quoted heredoc (`<<'EOF'`).
+and stream a single JSON object on stdin via a single-quoted heredoc (`<<'EOF'`):
+
+```
+{ "objective": "...", "summary": "...", "title": "...", "changeRationales": [...], "changedFiles": [...], "artifacts": [...] }
+```
 
 After the command succeeds, report the new `MISSION_ID`.
 
 Rules:
 - Do NOT use this for in-progress work. Use `/prompt` for that.
-- The CLI validates that every changed git-tracked file is represented in `changeRationales` unless `--skip-file-change-check` is passed.
-- If project resolution fails, re-run with `--project-id <id-or-name>` or `--personal`.
-
-
+- If project resolution fails, re-run with `--project-id <id-or-name>`.
+- The exact submission format is documented in `skills/overlord-mission/reference/record-work.md`.

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

@@ -41,6 +41,7 @@ connector:
     - "scripts/user-prompt-submit-hook.sh"
     - "skills/overlord-mission/SKILL.md"
     - "skills/overlord-mission/reference/cli.md"
+    - "skills/overlord-mission/reference/record-work.md"
     - "skills/overlord-mission/reference/context.md"
     - "skills/overlord-mission/reference/devices.md"
     - "skills/overlord-mission/reference/mcp.md"

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

@@ -32,6 +32,7 @@ connector:
     - "scripts/user-prompt-submit-hook.sh"
     - "skills/overlord-mission/SKILL.md"
     - "skills/overlord-mission/reference/cli.md"
+    - "skills/overlord-mission/reference/record-work.md"
     - "skills/overlord-mission/reference/context.md"
     - "skills/overlord-mission/reference/devices.md"
     - "skills/overlord-mission/reference/mcp.md"

package/dist/connectors/adapters/codex/scripts/overlord-mcp.mjs

@@ -234,6 +234,33 @@ const tools = [
       },
       ['missionId', 'sessionKey', 'summary']
     )
+  },
+  {
+    name: 'overlord_record_work',
+    title: 'Record completed work as a mission',
+    description:
+      'Record work already completed in this chat as a mission that lands in review — one call, no attach/deliver cycle. Records file-change rationales and runs the delivery through the standard Gemini summarizer.',
+    inputSchema: objectSchema(
+      {
+        projectId: stringProperty('Overlord project id, slug, or name.'),
+        objective: stringProperty('What was asked and done, phrased as a completed objective.'),
+        summary: stringProperty('Reviewer-facing narrative of what changed and why.'),
+        title: stringProperty('Optional mission title.'),
+        changeRationales: {
+          type: 'array',
+          description: 'One entry per meaningful file change (filePath, label, summary, why, impact).'
+        },
+        changedFiles: {
+          type: 'array',
+          description: 'Optional extra touched files without a full rationale.'
+        },
+        artifacts: {
+          type: 'array',
+          description: 'Optional artifacts: next_steps, test_results, decision, note, or url.'
+        }
+      },
+      ['projectId', 'objective', 'summary']
+    )
   }
 ];
 
@@ -360,6 +387,21 @@ function callOverlordTool(name, args) {
         : {})
     });
   }
+  if (name === 'overlord_record_work') {
+    return runProtocol('record-work', {
+      'project-id': requiredString(args, 'projectId'),
+      payload: {
+        objective: requiredString(args, 'objective'),
+        summary: requiredString(args, 'summary'),
+        ...(optionalString(args, 'title') ? { title: requiredString(args, 'title') } : {}),
+        ...(Array.isArray(args.changeRationales)
+          ? { changeRationales: args.changeRationales }
+          : {}),
+        ...(Array.isArray(args.changedFiles) ? { changedFiles: args.changedFiles } : {}),
+        ...(Array.isArray(args.artifacts) ? { artifacts: args.artifacts } : {})
+      }
+    });
+  }
   if (name === 'attach') {
     return runProtocol('attach', { 'mission-id': args.mission_id });
   }

package/dist/connectors/adapters/cursor/commands/record-work.md

@@ -1,15 +1,17 @@
-Immediately record the work you just completed in this chat as a new Overlord mission via `ovld protocol record-work`. No agent session is opened — the work is already done.
+Immediately record the work you just completed in this chat as a new Overlord mission via `ovld protocol record-work`. No agent session is opened — the work is already done. This creates a mission with one completed objective, records the file changes with rationales, lands it in the review column, and runs the standard Gemini delivery summary.
 
 Synthesize from the current conversation:
 - `objective`: what was asked / what was done.
-- `summary`: reviewer-friendly narrative for the feed.
-- `changeRationales`: one entry per meaningful git-tracked file change (`label`, `file_path`, `summary`, `why`, `impact`, optional `hunks`). Use `git status` and `git diff` to enumerate changed files.
+- `summary`: reviewer-friendly narrative of what changed and why.
+- `changeRationales`: one entry per meaningful git-tracked file change (`file_path`, `label`, `summary`, `why`, `impact`, optional `hunks`). Use `git status` and `git diff` to enumerate changed files. Every listed file shows as "covered" in review.
+- `changedFiles` (optional): touched files without a full rationale (`filePath`, optional `vcsStatus`).
+- `title` (optional): mission title; defaults to a title derived from the objective.
 - `artifacts` (optional): `next_steps`, `test_results`, `decision`, `note`, `url`.
 
 If text was provided after `/record-work`, treat it as additional context for the summary.
 
-Run `ovld protocol record-work --payload-file -` and stream the JSON payload `{ "objective": "...", "summary": "...", "artifacts": [...], "changeRationales": [...] }` on stdin via a single-quoted heredoc.
+Run `ovld protocol record-work --payload-file -` and stream a single JSON object `{ "objective": "...", "summary": "...", "title": "...", "changeRationales": [...], "changedFiles": [...], "artifacts": [...] }` on stdin via a single-quoted heredoc.
 
 After the command succeeds, report the new MISSION_ID.
 
-Do NOT use for in-progress work — use `/prompt` for that.
+Do NOT use for in-progress work — use `/prompt` for that. The exact submission format is documented in `skills/overlord-mission/reference/record-work.md`.

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

@@ -42,6 +42,7 @@ connector:
     - "scripts/overlord-mcp.mjs"
     - "skills/overlord-mission/SKILL.md"
     - "skills/overlord-mission/reference/cli.md"
+    - "skills/overlord-mission/reference/record-work.md"
     - "skills/overlord-mission/reference/context.md"
     - "skills/overlord-mission/reference/devices.md"
     - "skills/overlord-mission/reference/mcp.md"

package/dist/connectors/adapters/cursor/scripts/overlord-mcp.mjs

@@ -234,6 +234,33 @@ const tools = [
       },
       ['missionId', 'sessionKey', 'summary']
     )
+  },
+  {
+    name: 'overlord_record_work',
+    title: 'Record completed work as a mission',
+    description:
+      'Record work already completed in this chat as a mission that lands in review — one call, no attach/deliver cycle. Records file-change rationales and runs the delivery through the standard Gemini summarizer.',
+    inputSchema: objectSchema(
+      {
+        projectId: stringProperty('Overlord project id, slug, or name.'),
+        objective: stringProperty('What was asked and done, phrased as a completed objective.'),
+        summary: stringProperty('Reviewer-facing narrative of what changed and why.'),
+        title: stringProperty('Optional mission title.'),
+        changeRationales: {
+          type: 'array',
+          description: 'One entry per meaningful file change (filePath, label, summary, why, impact).'
+        },
+        changedFiles: {
+          type: 'array',
+          description: 'Optional extra touched files without a full rationale.'
+        },
+        artifacts: {
+          type: 'array',
+          description: 'Optional artifacts: next_steps, test_results, decision, note, or url.'
+        }
+      },
+      ['projectId', 'objective', 'summary']
+    )
   }
 ];
 
@@ -360,6 +387,21 @@ function callOverlordTool(name, args) {
         : {})
     });
   }
+  if (name === 'overlord_record_work') {
+    return runProtocol('record-work', {
+      'project-id': requiredString(args, 'projectId'),
+      payload: {
+        objective: requiredString(args, 'objective'),
+        summary: requiredString(args, 'summary'),
+        ...(optionalString(args, 'title') ? { title: requiredString(args, 'title') } : {}),
+        ...(Array.isArray(args.changeRationales)
+          ? { changeRationales: args.changeRationales }
+          : {}),
+        ...(Array.isArray(args.changedFiles) ? { changedFiles: args.changedFiles } : {}),
+        ...(Array.isArray(args.artifacts) ? { artifacts: args.artifacts } : {})
+      }
+    });
+  }
   if (name === 'attach') {
     return runProtocol('attach', { 'mission-id': args.mission_id });
   }

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

@@ -21,6 +21,7 @@ connector:
     - "prompt-wrapper.md"
     - "skills/overlord-mission/SKILL.md"
     - "skills/overlord-mission/reference/cli.md"
+    - "skills/overlord-mission/reference/record-work.md"
     - "skills/overlord-mission/reference/context.md"
     - "skills/overlord-mission/reference/devices.md"
     - "skills/overlord-mission/reference/mcp.md"

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

@@ -82,10 +82,11 @@ 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 next-up,execute` and ask the user to confirm.
 7. If you need to understand project routing before prompting, use `ovld protocol discover-project`.
-8. If you need other lifecycle commands or flags, run `ovld protocol help` and use the real subcommand list instead of guessing.
-9. Once you attach to a mission, switch back to Mode 1 and follow the full mission lifecycle.
+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 the file changes with 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.
 
-For mission creation examples, project discovery, and `--objectives-json` format see **CLI Command Reference** below.
+For mission creation examples, project discovery, and `--objectives-json` format see **CLI Command Reference** below. For recording already-completed work, see [reference/record-work.md](reference/record-work.md).
 
 ## CLI Command Reference
 
@@ -299,7 +300,8 @@ 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`, `prompt`, and `record-work` 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.
+- `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.
+- `record-work` is different: it creates exactly one **completed** objective. It takes a single `--objective` (or positional / an `objective` field in `--payload-json`) plus a `--summary` and the file-change data — not `--objectives-json`. See [reference/record-work.md](reference/record-work.md).
 - `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
@@ -414,6 +416,7 @@ Field shape, inline vs stdin piping, and `record-change-rationales` syntax are i
 ## Reference
 
 - [reference/cli.md](reference/cli.md) — Full protocol command syntax, flags, phases, mission creation, and project discovery
+- [reference/record-work.md](reference/record-work.md) — Recording already-completed chat work as a review mission: the exact CLI/MCP submission format for `record-work` / `overlord_record_work`
 - [reference/mcp.md](reference/mcp.md) — MCP tool naming, key casing, hosted vs local shim defaults
 - [reference/devices.md](reference/devices.md) — Device fingerprints, project resources, and `--for-human`
 - [reference/context.md](reference/context.md) — Shared state, attachments, and large artifact policy

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

@@ -164,8 +164,8 @@ 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`, `prompt`, and `record-work` 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.
-- `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.
+- `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.
+- `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"}]'
@@ -179,6 +179,29 @@ ovld protocol prompt --agent <agent-identifier> --objectives-json '[{"objective"
 ovld protocol add-objectives --mission-id 1:899 --objectives-json '[{"objective":"Implement the API"},{"objective":"Add CLI docs"}]'
 ```
 
+### Record Completed Work
+
+Record already-finished chat work as a completed review mission in one call — no
+`attach`/`deliver`. Creates a mission with one completed objective, records the file
+changes with rationales, lands it in review, and runs the Gemini delivery summary.
+
+```bash
+ovld protocol record-work --payload-file - <<'EOF'
+{
+  "objective": "Add a CSV export button to the reports page.",
+  "summary": "Added a CSV export control and the serializer behind it.",
+  "changeRationales": [
+    { "file_path": "src/reports/export.ts", "label": "CSV serializer",
+      "summary": "New CSV serializer.", "why": "Users need offline reports.",
+      "impact": "Reports can be exported as CSV." }
+  ]
+}
+EOF
+```
+
+The full submission format (fields, MCP equivalent, `changedFiles`) is in
+[record-work.md](record-work.md).
+
 ### Local Durability For New Missions
 
 `create`, `prompt`, `add-objectives`, and `record-work` save the objective/mission text to a local draft (`~/.overlord/pending-missions/`) **before** sending it, and delete that draft only once the server confirms the write. If the network drops mid-call, your text is never lost — the failure message points at the saved file. Manage outstanding drafts with `pending-missions`:

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

@@ -6,5 +6,6 @@
 - `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.
 - `record_change_rationales` (MCP) and `ovld protocol record-change-rationales` (CLI) both write to the same `file_changes` table. The dedicated CLI route is `POST /api/protocol/record-change-rationales`.
+- `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`.
 - 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" in `deliver` are the structured records an agent submits at delivery 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/overlord-mission/reference/record-work.md

@@ -0,0 +1,110 @@
+# Recording Completed Work (`record-work`)
+
+Use `record-work` to log work that is **already finished** — for example, something you
+just built for the user in a chat app — as a completed Overlord mission. It is the
+after-the-fact equivalent of `create` + `attach` + `deliver`, collapsed into one call:
+
+1. Creates a mission with a **single completed objective** matching the work done.
+2. Records each file change with its rationale.
+3. Lands the mission in the **review** column.
+4. Runs the delivery through the **standard Gemini delivery summarizer**, so the result
+   reads like any other delivered (in-review) mission.
+
+There is **no agent session** — do not `attach`. Do not use this for in-progress work
+(use `create`/`prompt` for that).
+
+## Submission format (authoritative)
+
+Submit **one JSON envelope** on stdin. This is the efficient, quoting-safe path and is
+identical across the CLI (`--payload-file -`) and the hosted MCP tool
+(`overlord_record_work`).
+
+```jsonc
+{
+  "objective": "What was asked and what you did, phrased as a completed objective (1–3 sentences).",
+  "summary": "Reviewer-facing narrative of what changed and why. This is what the PM reads first.",
+  "title": "Optional mission title; defaults to a title derived from the objective.",
+  "changeRationales": [
+    {
+      "file_path": "src/widget.ts",   // repository-relative path
+      "label": "Add widget",          // short reviewer title
+      "summary": "New widget module.", // what changed in this file
+      "why": "User asked for a widget.", // why it changed
+      "impact": "Widget now renders on the dashboard." // behavioral impact
+    }
+  ],
+  "changedFiles": [
+    { "filePath": "src/generated.ts", "vcsStatus": "M" } // optional; touched files without a rationale
+  ],
+  "artifacts": [
+    { "type": "next_steps", "label": "Next steps", "content": "…" } // optional
+  ]
+}
+```
+
+### Field rules
+
+- **`objective`** (required) — the completed objective text. May also be passed as
+  `--objective`/positional on the CLI; a flag always wins over the envelope.
+- **`summary`** (required) — narrative, not a command list.
+- **`title`** (optional) — omit to derive from the objective.
+- **`changeRationales`** (one per meaningful file change) — same shape as `deliver`. All
+  five string fields (`file_path`, `label`, `summary`, `why`, `impact`) are required per
+  entry. `filePath` (camelCase) is accepted as an alias for `file_path`. Do **not** wrap
+  entries under a `rationale` key. Skip formatting-only noise.
+  - Every rationale's `file_path` is automatically recorded as a **changed file** and
+    shows as **covered** in the review file panel — you do not list it twice.
+- **`changedFiles`** (optional) — additional touched files you are *not* writing a full
+  rationale for. They appear as **missing_rationale** in review, exactly like a live
+  delivery. Uses `filePath` (camelCase) + optional `vcsStatus`.
+- **`artifacts`** (optional) — `next_steps`, `test_results`, `migration`, `note`, `url`,
+  or `decision`.
+- **`deliveryReport`** (optional) — you may include a `deliveryReport.agentReport`
+  (`humanActions`, `tradeoffsMade`, `knownRisks`, `deferredWork`, `assumptions`) just as
+  in `deliver`. It improves review visibility but never blocks the record.
+
+Enumerate changed files from `git status` / `git diff` before writing rationales.
+
+## CLI
+
+Stream the envelope on stdin with a single-quoted heredoc (safe for backticks/`$vars`):
+
+```bash
+ovld protocol record-work --payload-file - <<'EOF'
+{
+  "objective": "Add a CSV export button to the reports page.",
+  "summary": "Added a CSV export control and the serializer behind it.",
+  "changeRationales": [
+    { "file_path": "src/reports/export.ts", "label": "CSV serializer",
+      "summary": "New CSV serializer.", "why": "Users need offline reports.",
+      "impact": "Reports can be exported as CSV." }
+  ]
+}
+EOF
+```
+
+- Project resolution: matches the current directory to a project resource. Pass
+  `--project-id <id-or-name>` when running outside a linked checkout or to be explicit.
+- The command prints the new mission (and `MISSION_ID`); report it back to the user.
+- Inline `--*-json` flags are capped (~8 KB) — prefer `--payload-file -` on stdin.
+
+## Hosted MCP
+
+Call `overlord_record_work` with the same fields as first-class arguments
+(`projectId` **required** — hosted MCP never chooses a project implicitly):
+
+```jsonc
+{
+  "projectId": "acme-web",
+  "objective": "Add a CSV export button to the reports page.",
+  "summary": "Added a CSV export control and the serializer behind it.",
+  "changeRationales": [
+    { "filePath": "src/reports/export.ts", "label": "CSV serializer",
+      "summary": "New CSV serializer.", "why": "Users need offline reports.",
+      "impact": "Reports can be exported as CSV." }
+  ]
+}
+```
+
+The tool returns the created review-column mission and the `deliveryId` whose Gemini
+summary is composing asynchronously.

package/dist/index.js

@@ -14808,19 +14808,30 @@ prompt:
 
 record-work:
   Purpose:
-    Record work already completed in chat as a mission in review without a session.
-    Use instead of create + attach + deliver when logging past work.
+    Record work already completed in chat as a completed mission in review, in one
+    call \u2014 no attach/deliver cycle. Creates a mission with a single completed
+    objective, records the file changes and their rationales, lands it in the review
+    column, and runs the delivery through the standard Gemini summarizer so it reads
+    like any other delivered mission. Use instead of create + attach + deliver.
   Required:
-    --objective "<text>" (or positional objective text)
+    --objective "<text>" (or positional, or an "objective" field in --payload-json)
     --summary or --summary-file <path|->
   Optional:
     --title <text>
     --project-id <id>
     --artifacts-json / --artifacts-file <path|->
     --change-rationales-json / --change-rationales-file <path|->
+    --changed-files-json / --changed-files-file <path|->
+    --payload-json / --payload-file <path|->   (single envelope; see Notes)
   Notes:
+    Efficient form: stream one JSON object on stdin via \`--payload-file -\` carrying
+    { objective, summary, title?, changeRationales, changedFiles?, artifacts? }.
+    Explicit flags always win over fields inside --payload-json.
     Change-rationale entries use the same shape documented under \`deliver\`
     (file_path, label, summary, why, impact; summary is named "summary", not "rationale").
+    Every rationale's file_path is recorded as a changed file (shown "covered" in
+    review); add --changed-files-json for touched files without a rationale. The
+    full submission format lives in reference/record-work.md.
 
 update:
   Purpose:
@@ -17157,6 +17168,43 @@ async function runManagementCommand({
       else console.log(`Linked ${sourceUrl} to project ${projectId}`);
       return;
     }
+    case "add-et": {
+      const name = flagValue(parsed.flags, "--name") ?? parsed.positional.join(" ");
+      const protocolFlags = {};
+      if (name) protocolFlags["--name"] = name;
+      const workspaceId = flagValue(parsed.flags, "--workspace-id");
+      if (workspaceId) protocolFlags["--workspace-id"] = workspaceId;
+      const result = await runtime.backend.post({
+        path: "/api/protocol/register-target",
+        body: { args: rest, positional: parsed.positional, flags: protocolFlags, fileInputs: {} }
+      });
+      const record = asRecord2(result);
+      if (record.status === "workspace_selection_required") {
+        if (json) {
+          printJson({ result });
+        } else {
+          const workspaces = Array.isArray(record.workspaces) ? record.workspaces : [];
+          console.log(
+            "You belong to more than one workspace. Re-run with --workspace-id set to one of:"
+          );
+          for (const entry of workspaces) {
+            const ws = asRecord2(entry);
+            console.log(`  - ${ws.name ?? ws.id} (${ws.slug ?? ws.id})`);
+          }
+        }
+        return;
+      }
+      if (json) {
+        printJson({ result });
+      } else {
+        const target = asRecord2(record.executionTarget);
+        const ws = asRecord2(record.workspace);
+        console.log(
+          `Registered execution target ${target.label ?? name ?? ""} (${target.executionTargetId ?? "unknown"}) in workspace ${ws.name ?? ws.id ?? ""}`
+        );
+      }
+      return;
+    }
     case "create":
     case "prompt": {
       const objectivesJson = flagValue(parsed.flags, "--objectives-json");
@@ -17780,6 +17828,7 @@ var COMMAND_FLAGS = {
   ],
   "add-cwd": ["--directory", "--key", "--project-id", "--primary", "--access"],
   "add-url": ["--url", "--project-id", "--key", "--primary", "--access"],
+  "add-et": ["--name", "--workspace-id"],
   create: ["--objectives-json", "--objective", "--prompt", "--project-id", "--title", "--resource"],
   prompt: [
     "--objectives-json",
@@ -17912,6 +17961,10 @@ Projects:
                                                  (prompts to pick a project when --project-id is omitted)
   ${primaryCommand} add-url --url <git-url> --project-id <id> [--key <resourceKey>] [--primary true|false] [--access read|read_write]
 
+Execution targets:
+  ${primaryCommand} add-et --name "<name>" [--workspace-id <id-or-name>] [--json]
+                                                 (announce this machine as an execution target)
+
 Missions:
   ${primaryCommand} create "<objective>" [--objectives-json '[...]'] [--json]
   ${primaryCommand} prompt "<objective>" [--json]
@@ -17982,6 +18035,7 @@ var KNOWN_COMMANDS = /* @__PURE__ */ new Set([
   "org-setup",
   "add-cwd",
   "add-url",
+  "add-et",
   "create",
   "prompt",
   "attach",