overlord-cli 0.2610241050.0 → 0.2610261104.0

package/README.md

@@ -255,7 +255,7 @@ This module is the developer-facing home for three components defined in
 | Component      | Stable id  | What it owns                                                                                                                                                                        |
 | -------------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | CLI Layer      | `cli`      | Management command names/shapes, project linking & discovery, config file locations (`overlord.toml`, `.overlord/project.json`), human-readable output conventions                  |
-| Protocol Layer | `protocol` | `ovld protocol` subcommands and flags, session lifecycle (`attach → (update\|heartbeat)* → (ask\|deliver)`), context-assembly format, delivery payload + change-rationale recording |
+| Protocol Layer | `protocol` | `ovld protocol` subcommands and flags, session lifecycle (`attach → (update\|heartbeat)* → (ask\|deliver)`), context-assembly format, delivery payload + declared-path recording |
 | Runner Layer   | `runner`   | `execution_requests` queue claiming and launch, working-directory resolution, `ovld runner` commands, execution-target selection                                                    |
 
 These stay distinct components in the contract (separate interaction surfaces
@@ -273,7 +273,7 @@ colocation convention):
 - [03 — Agent Protocol](https://github.com/cooperativ-labs/OpenOverlord/blob/main/cli/docs/03-agent-protocol.md): `ovld protocol` lifecycle, context assembly, updates, delivery, attachments.
 - [04 — Runner and Launch Execution](https://github.com/cooperativ-labs/OpenOverlord/blob/main/cli/docs/04-runner-and-launch-execution.md): execution requests, local runner, launch command generation, auto-advance.
 - [06 — Core Domain and Lifecycle](https://github.com/cooperativ-labs/OpenOverlord/blob/main/cli/docs/06-core-domain-and-lifecycle.md): projects, missions, objectives, sessions, events, statuses, state transitions.
-- [11 — Review, Artifacts, and Change Tracking](https://github.com/cooperativ-labs/OpenOverlord/blob/main/cli/docs/11-review-artifacts-and-change-tracking.md): delivery review records, artifacts, objective-ledger evidence, and optional rationale annotations.
+- [11 — Review, Artifacts, and Change Tracking](https://github.com/cooperativ-labs/OpenOverlord/blob/main/cli/docs/11-review-artifacts-and-change-tracking.md): delivery review records, artifacts, objective-ledger evidence, and declared paths.
 - [Test Plan](https://github.com/cooperativ-labs/OpenOverlord/blob/main/cli/docs/testing.md): test plan for the `cli`, `protocol`, and `runner` components — management commands, protocol lifecycle/attach-shape/validation conformance, runner queue atomicity, and surface smoke tests. Part of the root [TEST_PLAN.md](https://github.com/cooperativ-labs/OpenOverlord/blob/main/TEST_PLAN.md).
 
 ### Code & Tests

package/dist/connectors/AGENTS.md

@@ -85,11 +85,28 @@ A connector may invoke `ovld protocol capture-change` from a native post-mutatio
 `OVERLORD_OBJECTIVE_ID` is explicit in the launch environment. Mission scope is recovered from
 that objective's exact active-session binding; cwd never selects it. The hook must remain silent
 and perform no write when the objective id or `ovld` is unavailable. A directly named native edit
-path records objective-bound, non-exclusive `declared_edit`/`direct` evidence only after the
-connector-owned codec normalizes it as `file.edited`. The hook must pass its connector key through
-`--agent`; generic payload path parsing is forbidden. Codec-normalized read, search, and fetch
-callbacks are silent no-ops. Mutation-capable callbacks without a normalized edit path, plus shell,
-generic, unknown, and unmapped callbacks, record unavailable evidence health. Every hook
+path records objective-bound, non-exclusive `declared_edit` evidence only after the
+connector-owned codec normalizes it as `file.edited` **and** its outcome is `ok`. The hook must
+pass its connector key through `--agent`; generic payload path parsing is forbidden.
+
+Outcome is decided in the codec, never guessed in capture:
+
+- `outcomePath` decodes a boolean, status word, or numeric exit code; `outcomeExitCodePrefix`
+  decodes a leading `<prefix><n>` line of a text result (Codex `apply_patch`: `Exit code: 0`).
+  Only the decoded value is kept.
+- `successOnly: true` declares that the harness emits this event only for successful calls and
+  routes failures elsewhere. It must cite source/binary evidence for the harness version in the
+  codec comment and be pinned by a normalized-event fixture; never infer it from an event name.
+- An absent or unrecognized result is unknown, never success.
+
+Capture then applies: `ok` with exact paths appends evidence; `blocked` appends nothing;
+`error`/`cancelled` append nothing and record sticky `outcome_partial` (a non-atomic edit may have
+partially applied, so the agent declares actual writes); unknown records `outcome_unavailable`;
+shell records `shell_activity_unverified` (coverage uncertainty, never a claimed write); other
+no-path, generic, and unmapped callbacks record `direct_path_unavailable`. Codec-normalized
+read, search, and fetch callbacks append no evidence but still record callback observation.
+Patch-text extraction reduces `*** Add|Update|Delete File:` and `*** Move to:` headers, so a
+rename keeps both endpoints. Every hook
 registration must be backed by a `script-io` fixture, and every mutation window claim must be
 backed by a `mutation-window` fixture. Claude, Codex, and Cursor render this callback from
 `connectors/core/scripts/capture-change-hook.sh`; their adapter directories own only the native

package/dist/connectors/VERSION

@@ -1 +1 @@
-0.3.53
+0.3.57

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

@@ -1,4 +1,4 @@
-contractVersion: "164"
+contractVersion: "167"
 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.53",
+  "version": "0.3.57",
   "description": "Chat-driven access to Overlord mission protocol workflows through skills and MCP.",
   "author": {
     "name": "Cooperativ",

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

@@ -9,8 +9,7 @@ This creates a mission with one completed objective, lands it in the review colu
 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` (optional): reviewer annotations for changes whose reason is not obvious (`filePath`, `label`, `summary`, `why`, `impact`, optional `hunks`).
-- `changedFiles` (optional, `record-work` only): files known from this completed chat work that have no rationale. Each entry is an object with canonical repository-relative `filePath` and optional `vcsStatus`; never infer ownership from a shared-worktree-wide status or diff.
+- `declaredPaths` (optional): repository-relative paths you know this work changed, as a JSON string array (deleted files and both rename endpoints are valid). They are recorded as Declared; never infer them from a shared-worktree-wide status or diff, and never explain files one by one.
 - `title` (optional): mission title; defaults to a title derived from the objective.
 - `artifacts` (optional): `next_steps`, `test_results`, `decision`, `note`, `url`.
 
@@ -19,7 +18,7 @@ If a command argument is present, treat it as additional context to weave into t
 Run:
 `ovld protocol record-work --agent antigravity --payload-file -`
 
-and stream a JSON object `{ "objective": "...", "summary": "...", "artifacts": [...], "changeRationales": [...], "changedFiles": [...] }` on stdin via a single-quoted heredoc (`<<'EOF'`).
+and stream a JSON object `{ "objective": "...", "summary": "...", "artifacts": [...], "declaredPaths": [...] }` on stdin via a single-quoted heredoc (`<<'EOF'`).
 
 After the command succeeds, report the new `MISSION_ID`.
 

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

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.53",
+  "version": "0.3.57",
   "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/codec/claude.codec.yaml

@@ -33,6 +33,11 @@ events:
     origin: agent
     toolPath: tool_name
     inputPath: tool_input
+    # Success-only by harness contract: Claude Code's hook table (verified in the shipped
+    # 2.1.310 binary) reads "PostToolUse — Run after successful tool" and routes failures to
+    # the separate PostToolUseFailure event, which Overlord does not register. A failed or
+    # denied Write therefore never reaches capture as native evidence.
+    successOnly: true
     # A file-mutating tool becomes `file.edited` instead, so the feed can show a change
     # timeline without the reader having to know which tool names mutate files.
     fileEditKind: file.edited

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

@@ -9,8 +9,7 @@ Immediately record the work you just completed in this chat as a new Overlord mi
 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` (optional): reviewer annotations for changes whose reason is not obvious (`filePath`, `label`, `summary`, `why`, `impact`, optional `hunks`).
-- `changedFiles` (optional, `record-work` only): files known from this completed chat work that have no rationale. Each entry is an object with canonical repository-relative `filePath` and optional `vcsStatus`; never infer ownership from a shared-worktree-wide status or diff.
+- `declaredPaths` (optional): repository-relative paths you know this work changed, as a JSON string array (deleted files and both rename endpoints are valid). They are recorded as Declared; never infer them from a shared-worktree-wide status or diff, and never explain files one by one.
 - `title` (optional): mission title; defaults to a title derived from the objective.
 - `artifacts` (optional): `next_steps`, `test_results`, `decision`, `note`, `url`.
 
@@ -22,7 +21,7 @@ Run:
 and stream a single JSON object on stdin via a single-quoted heredoc (`<<'EOF'`):
 
 ```
-{ "objective": "...", "summary": "...", "title": "...", "changeRationales": [...], "changedFiles": [...], "artifacts": [...] }
+{ "objective": "...", "summary": "...", "title": "...", "declaredPaths": [...], "artifacts": [...] }
 ```
 
 After the command succeeds, report the new `MISSION_ID`.

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

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

package/dist/connectors/adapters/claude/fixtures/normalize-post-tool-use-notebook.json

@@ -33,6 +33,7 @@
       "subject": "notebooks/analysis.ipynb",
       "detail": "26 bytes",
       "paths": ["notebooks/analysis.ipynb"],
+      "outcome": "ok",
       "formatterVersion": 1
     }
   },

package/dist/connectors/adapters/claude/fixtures/normalize-post-tool-use-shell.json

@@ -38,6 +38,7 @@
       "action": "Run a shell command",
       "subject": "yarn",
       "detail": "yarn test --silent",
+      "outcome": "ok",
       "formatterVersion": 1
     }
   },

package/dist/connectors/adapters/claude/fixtures/normalize-post-tool-use-write.json

@@ -36,6 +36,7 @@
       "paths": [
         "config/secrets.ts"
       ],
+      "outcome": "ok",
       "formatterVersion": 1
     }
   },

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

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.53",
+  "version": "0.3.57",
   "description": "Chat-driven access to Overlord mission protocol workflows with hook-driven activity capture.",
   "author": {
     "name": "Cooperativ",
@@ -38,7 +38,7 @@
     "defaultPrompt": [
       "Attach to Overlord mission 123 and summarize the context before editing code",
       "Post an execute update to this Overlord mission after a meaningful implementation step",
-      "Deliver this Overlord mission with artifacts and change rationales"
+      "Deliver this Overlord mission with a summary and any declared paths"
     ],
     "brandColor": "#1E6B5C",
     "composerIcon": "./assets/icon.png",

package/dist/connectors/adapters/codex/CAPABILITIES.md

@@ -6,7 +6,7 @@
 
 **Harness version verified** `0.147.0` · **range** `>=0.124.0` · **scheme** `semver`
 
-**Descriptor digest** `4d4908a81023cf7943ebbcb35d8477751f97d916597adc3bf3cec63bdb58dc4b`
+**Descriptor digest** `b3120edbb3f8a017801de0b9b085c42f05f1d7c335246e224cd283e874ddc542`
 
 > The tier is derived from passing fixtures, never authored. `unsupported` means the harness
 > cannot do it — do not attempt it. `not-implemented` means it is buildable and unbuilt: that is
@@ -59,7 +59,7 @@ path. Runtime file evidence is unavailable for this adapter.
 | `observe.prompt` | ✅ supported | `UserPromptSubmit` | fixtures: `fixtures/normalize-user-prompt.json` |
 | `observe.toolCall` | 🚧 not-implemented | `PreToolUse` | tracked as `latch-engine` |
 | `observe.toolResult` | 🚧 not-implemented | `PostToolUse` | tracked as `latch-engine` |
-| `observe.fileEdit` | ✅ supported | `PostToolUse` | fixtures: `fixtures/normalize-post-tool-use.json`, `fixtures/agent-session-hooks.json`, `fixtures/post-tool-use-hook.json`, `fixtures/post-tool-use-unbound.json` |
+| `observe.fileEdit` | ✅ supported | `PostToolUse` | fixtures: `fixtures/normalize-post-tool-use.json`, `fixtures/normalize-post-tool-use-failed.json`, `fixtures/normalize-post-tool-use-rename.json`, `fixtures/agent-session-hooks.json`, `fixtures/post-tool-use-hook.json`, `fixtures/post-tool-use-unbound.json` |
 | `observe.sessionLifecycle` | 🚧 not-implemented | `SessionStart` | tracked as `latch-engine` |
 | `decide.shell` | 🚧 not-implemented | `PermissionRequest` | tracked as `latch-engine` |
 | `decide.mcp` | 🚧 not-implemented | `PermissionRequest` | tracked as `latch-engine` |

package/dist/connectors/adapters/codex/codec/codex.codec.yaml

@@ -28,13 +28,22 @@ events:
     inputPath: tool_input
     callIdPath: tool_use_id
     turnIdPath: turn_id
+    # Codex runs PostToolUse after a handler returns a result, but apply_patch reports its own
+    # failure inside that result: `tool_response` is text whose first line is `Exit code: <n>`
+    # (upstream codex-rs hook test `post_tool_use_records_additional_context_for_apply_patch`
+    # asserts the `Exit code: 0` / `Success. Updated the following files:` shape). Only the
+    # leading exit code is decoded; the text is never retained. A missing or unrecognized
+    # line stays unknown, so capture records outcome_unavailable rather than native evidence.
+    outcomePath: tool_response
+    outcomeExitCodePrefix: 'Exit code: '
     fileEditKind: file.edited
     filePathPaths:
       - file_path
       - filePath
       - path
     # Codex apply_patch carries destinations in bounded patch headers rather
-    # than a standalone path field. The codec extracts only those headers.
+    # than a standalone path field. The codec extracts only Add/Update/Delete
+    # File and Move to headers, so a rename keeps both endpoints.
     filePathPatchTextPaths:
       - command
       - patch

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

@@ -1,4 +1,4 @@
-contractVersion: "164"
+contractVersion: "167"
 componentType: connector
 componentKey: codex
 label: "Codex Connector"
@@ -14,7 +14,7 @@ connector:
   harnessCapabilities:
     path: connectors/adapters/codex/harness-capabilities.yaml
     schemaVersion: 1
-    digest: "4d4908a81023cf7943ebbcb35d8477751f97d916597adc3bf3cec63bdb58dc4b"
+    digest: "b3120edbb3f8a017801de0b9b085c42f05f1d7c335246e224cd283e874ddc542"
   # ── END GENERATED ────────────────────────────────────────────────────────────
   installPath: "~/.codex/plugins/overlord"
   managedFiles:

package/dist/connectors/adapters/codex/fixtures/normalize-post-tool-use-failed.json

@@ -0,0 +1,42 @@
+{
+  "fixtureVersion": 1,
+  "kind": "normalized-event",
+  "description": "Codex PostToolUse for an apply_patch that ran and exited non-zero (`Exit code: 1`). The codec decodes outcome `error`, so capture appends no native evidence for the attempted path and records outcome_partial instead. The tool output (with a credential) never enters the envelope.",
+  "codec": "codec/codex.codec.yaml",
+  "occurredAt": "2026-08-01T00:00:00.000Z",
+  "payload": {
+    "session_id": "codex-session-1",
+    "turn_id": "turn-1",
+    "tool_use_id": "call-3",
+    "transcript_path": "/Users/jake/.codex/sessions/secret.jsonl",
+    "cwd": "/repo",
+    "hook_event_name": "PostToolUse",
+    "tool_name": "apply_patch",
+    "tool_input": {
+      "command": "*** Begin Patch\n*** Update File: /repo/src/attempted.ts\n@@\n-const a = 1;\n+const a = 'AKIAIOSFODNN7EXAMPLE';\n*** End Patch"
+    },
+    "tool_response": "Exit code: 1\nWall time: 0.1 seconds\nOutput:\nerror: hunk failed near postgres://user:hunter2@db/app\n"
+  },
+  "expect": {
+    "eventId": "ev_4f0111e1e5440a7f448e6fda0caaaf82",
+    "producerSequence": null,
+    "occurredAt": "2026-08-01T00:00:00.000Z",
+    "kind": "file.edited",
+    "severity": "info",
+    "nativeEvent": "PostToolUse",
+    "nativeTurnId": "turn-1",
+    "nativeCallId": "call-3",
+    "subagentId": null,
+    "correlationId": "codex-session-1",
+    "origin": "agent",
+    "summary": "Write a file",
+    "payload": {
+      "tool": "edit",
+      "action": "Write a file",
+      "paths": ["src/attempted.ts"],
+      "outcome": "error",
+      "formatterVersion": 1
+    }
+  },
+  "mustNotContain": ["AKIAIOSFODNN7EXAMPLE", "hunter2", "secret.jsonl", "/Users/jake"]
+}

package/dist/connectors/adapters/codex/fixtures/normalize-post-tool-use-rename.json

@@ -0,0 +1,42 @@
+{
+  "fixtureVersion": 1,
+  "kind": "normalized-event",
+  "description": "Codex PostToolUse for a successful apply_patch rename plus delete. `*** Move to:` is reduced alongside Update/Delete headers so both rename endpoints and the deleted path become exact evidence; hunk content never enters the envelope.",
+  "codec": "codec/codex.codec.yaml",
+  "occurredAt": "2026-08-01T00:00:00.000Z",
+  "payload": {
+    "session_id": "codex-session-1",
+    "turn_id": "turn-1",
+    "tool_use_id": "call-4",
+    "transcript_path": "/Users/jake/.codex/sessions/secret.jsonl",
+    "cwd": "/repo",
+    "hook_event_name": "PostToolUse",
+    "tool_name": "apply_patch",
+    "tool_input": {
+      "command": "*** Begin Patch\n*** Update File: /repo/src/old-name.ts\n*** Move to: /repo/src/new-name.ts\n@@\n-export const key = 'AKIAIOSFODNN7EXAMPLE';\n+export const key = process.env.KEY;\n*** Delete File: /repo/src/removed.ts\n*** End Patch"
+    },
+    "tool_response": "Exit code: 0\nWall time: 0.1 seconds\nOutput:\nSuccess. Updated the following files:\nM src/new-name.ts\nD src/removed.ts\n"
+  },
+  "expect": {
+    "eventId": "ev_93222a9e39bc13fdd124587e3a68962e",
+    "producerSequence": null,
+    "occurredAt": "2026-08-01T00:00:00.000Z",
+    "kind": "file.edited",
+    "severity": "info",
+    "nativeEvent": "PostToolUse",
+    "nativeTurnId": "turn-1",
+    "nativeCallId": "call-4",
+    "subagentId": null,
+    "correlationId": "codex-session-1",
+    "origin": "agent",
+    "summary": "Write a file",
+    "payload": {
+      "tool": "edit",
+      "action": "Write a file",
+      "paths": ["src/old-name.ts", "src/new-name.ts", "src/removed.ts"],
+      "outcome": "ok",
+      "formatterVersion": 1
+    }
+  },
+  "mustNotContain": ["AKIAIOSFODNN7EXAMPLE", "hunter2", "secret.jsonl", "/Users/jake"]
+}

package/dist/connectors/adapters/codex/fixtures/normalize-post-tool-use.json

@@ -1,7 +1,7 @@
 {
   "fixtureVersion": 1,
   "kind": "normalized-event",
-  "description": "Recorded Codex PostToolUse payload proving file edits are reduced to structural metadata and never leak written content or tool output.",
+  "description": "Codex PostToolUse apply_patch payload in the upstream hook shape (tool_input.command patch text; tool_response text whose first line is `Exit code: 0`). Proves the edit is reduced to structural metadata plus a decoded `ok` outcome and never leaks written content or tool output.",
   "codec": "codec/codex.codec.yaml",
   "occurredAt": "2026-08-01T00:00:00.000Z",
   "payload": {
@@ -12,8 +12,10 @@
     "cwd": "/repo",
     "hook_event_name": "PostToolUse",
     "tool_name": "apply_patch",
-    "tool_input": { "command": "*** Begin Patch\n*** Update File: /repo/src/token.ts\n+const key = 'AKIAIOSFODNN7EXAMPLE';\n*** End Patch" },
-    "tool_response": { "text": "changed with postgres://user:hunter2@db/app" }
+    "tool_input": {
+      "command": "*** Begin Patch\n*** Update File: /repo/src/token.ts\n+const key = 'AKIAIOSFODNN7EXAMPLE';\n*** End Patch"
+    },
+    "tool_response": "Exit code: 0\nWall time: 0.1 seconds\nOutput:\nSuccess. Updated the following files:\nM src/token.ts\nconnected with postgres://user:hunter2@db/app\n"
   },
   "expect": {
     "eventId": "ev_bf289659aca425896e8c26747d35c87e",
@@ -32,6 +34,7 @@
       "tool": "edit",
       "action": "Write a file",
       "paths": ["src/token.ts"],
+      "outcome": "ok",
       "formatterVersion": 1
     }
   },

package/dist/connectors/adapters/codex/harness-capabilities.yaml

@@ -75,6 +75,8 @@ capabilities:
     native: PostToolUse
     fixtures:
       - fixtures/normalize-post-tool-use.json
+      - fixtures/normalize-post-tool-use-failed.json
+      - fixtures/normalize-post-tool-use-rename.json
       - fixtures/agent-session-hooks.json
       - fixtures/post-tool-use-hook.json
       - fixtures/post-tool-use-unbound.json

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

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.53",
+  "version": "0.3.57",
   "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/codec/cursor.codec.yaml

@@ -68,6 +68,11 @@ events:
     toolPath: tool_name
     inputPath: tool_input
     callIdPath: call_id
+    # Success-only by harness contract. The shipped cursor-agent 2026.09.23 executor fires
+    # postToolUse from `fireSuccessAsync` only when the tool result `isSuccess` (or its stream
+    # succeeded); errors, aborts, and preToolUse/permission denials go to `postToolUseFailure`
+    # with `error_message`/`failure_type`, which Overlord does not register.
+    successOnly: true
     fileEditKind: file.edited
     # Live Cursor Write payloads use file_path; path/filePath match the write
     # formatter's key order so an alternate Cursor dialect still captures.

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

@@ -3,14 +3,13 @@ Immediately record the work you just completed in this chat as a new Overlord mi
 Synthesize from the current conversation:
 - `objective`: what was asked / what was done.
 - `summary`: reviewer-friendly narrative of what changed and why.
-- `changeRationales` (optional): reviewer annotations for changes whose reason is not obvious (`filePath`, `label`, `summary`, `why`, `impact`, optional `hunks`).
-- `changedFiles` (optional, `record-work` only): files known from this completed chat work that have no rationale. Each entry is an object with canonical repository-relative `filePath` and optional `vcsStatus`; never infer ownership from a shared-worktree-wide status or diff.
+- `declaredPaths` (optional): repository-relative paths you know this work changed, as a JSON string array (deleted files and both rename endpoints are valid). They are recorded as Declared; never infer them from a shared-worktree-wide status or diff, and never explain files one by one.
 - `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 a single JSON object `{ "objective": "...", "summary": "...", "title": "...", "changeRationales": [...], "changedFiles": [...], "artifacts": [...] }` on stdin via a single-quoted heredoc.
+Run `ovld protocol record-work --payload-file -` and stream a single JSON object `{ "objective": "...", "summary": "...", "title": "...", "declaredPaths": [...], "artifacts": [...] }` on stdin via a single-quoted heredoc.
 
 After the command succeeds, report the new MISSION_ID.
 

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

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

package/dist/connectors/adapters/cursor/fixtures/normalize-post-tool-use-write.json

@@ -34,6 +34,7 @@
       "subject": "config/secrets.ts",
       "detail": "99 bytes",
       "paths": ["config/secrets.ts"],
+      "outcome": "ok",
       "formatterVersion": 1
     }
   },

package/dist/connectors/adapters/cursor/rules/overlord-local.mdc

@@ -9,5 +9,5 @@ alwaysApply: true
 - If the user asks from chat to use Overlord, use `/prompt` for new missions, `/load` for read-only context by mission ID, `/connect` to route the session onto an existing mission, and `/attach` when the user explicitly wants execution.
 - If you need other protocol commands or flags, run `ovld protocol help` instead of guessing.
 
-Normal delivery is summary-only; the objective ledger syncs independently. Use `ovld protocol changes` only to inspect ledger sync and hook health, never to infer ownership from a shared worktree.
+Normal delivery is summary-only; the objective ledger syncs independently. Before delivering, read the captured paths once with `ovld protocol changes --objective-id <id>`, declare only files you know you changed that capture missed with `--paths` / `--paths-file`, and summarize by behavior or component. Never diff a shared worktree or infer ownership from it.
 **Never revert, restore, or delete file changes from other agents or missions.** Leave unrelated dirty files intact.

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

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

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

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

package/dist/connectors/core/README.md

@@ -21,7 +21,7 @@ follow:
 - treat mission context as authoritative
 - update or heartbeat while working
 - ask exactly one blocking question and stop
-- deliver last with artifacts and change rationales
+- deliver last with a behavior-level summary, declaring only paths native capture missed
 - use safe stdin/file flags for shell-special payloads
 - repair local auth/setup before asking the user to intervene