@open-agent-toolkit/cli 0.2.67 → 0.2.69

package/assets/agents/oat-reviewer.md

@@ -1,6 +1,6 @@
 ---
 name: oat-reviewer
-version: 1.2.3
+version: 1.2.4
 description: Unified reviewer for OAT projects - mode-aware verification of requirements/design alignment and code quality. Writes a review artifact to disk by default, or returns structured findings in-memory when dispatched in structured-output mode.
 tools: Read, Bash, Grep, Glob, Write, Task
 color: yellow
@@ -235,6 +235,25 @@ Treat the artifact as a product deliverable. Verify it is:
    - Coverage of design/discovery: every in-scope design component or discovery decision is mapped to at least one task or explicitly deferred/out of scope.
    - Parallelism-claim sanity: any parallel phase group or parallelism statement is consistent with declared file boundaries and dependency order.
 
+6. **Necessary**
+   - Evaluate whether the proposed approach materially serves the requested
+     outcome. For substantial added machinery — a script, schema, persisted
+     record, gate, provider seam, or new document that someone will have to
+     own — identify its consumer (an agent acting on a named instruction, a
+     human reading a named surface, or code at a named call site) and consider
+     whether a smaller approach preserves the requirements.
+   - Judge prose by the behavior it meaningfully guides. An instruction whose
+     consumer is the agent that reads it is a real consumer; missing automated
+     enforcement of that instruction is not proof of uselessness.
+   - A mechanism whose only consumer is its own tests, its own plan, or a
+     deferred future reader is grounds to investigate, not an automatic
+     severity: grade the finding by wasted effort, maintenance burden, or
+     failure to meet the requested outcome, and say which.
+   - Report justified concerns in the existing findings sections. Do not
+     produce an inventory of unproblematic mechanisms, and do not override an
+     explicitly stated user requirement with a preference for simplicity;
+     name the conflict instead.
+
 ### Step 5: Verify Design Alignment
 
 This step applies to **code reviews** only.

package/assets/bundle-metadata.json

@@ -1,4 +1,4 @@
 {
   "schemaVersion": 1,
-  "oatVersion": "0.2.67"
+  "oatVersion": "0.2.69"
 }

package/assets/docs/provider-sync/scope-and-surface.md

@@ -109,8 +109,9 @@ child accepted by the native route that later returns `BLOCKED` are not
 role-selection rejection and do not permit fallback.
 
 Project workflows construct and redact the complete dispatch payload before
-the native call, then persist its accepted or `blocked-before-start` result
-immediately under the active project's `dispatch/` directory. The generic
+the native call, then record its accepted or `blocked-before-start` result in
+the project's run record; persisting it under the project's `dispatch/`
+directory is optional and off by default. The generic
 record remains provider-neutral. OAT-specific canonical role, rejection,
 fallback, and runtime facts live only under its `oat` namespace. A qualifying
 fallback is a fresh request that preserves exact target and controls and is

package/assets/docs/reference/cli-reference.md

@@ -153,7 +153,7 @@ Notable commands introduced in the current CLI surface:
 - `oat project complete-state <project-path>` - apply the canonical completed-state mutation to a project's `state.md`; used by `oat-project-complete` during lifecycle closeout
 - `oat project archive [project-path] [--project-recap-run <project-relative-path>] [--no-commit]` - archive a tracked project through the same local move, summary export, and configured S3 upload path used by completion. When omitted, the project path falls back to the active project. The optional recap path must identify a `project-recap` run inside the project's `explainers/` directory. Archive stages the selected complete package into `.oat/repo/reference/project-recaps/<YYYYMMDD-project-slug>/`, verifies every manifest-declared immutable file byte, then atomically installs the export before deleting the active project. Existing destinations, incomplete legacy hash coverage, stale bytes, path escapes, and recipe mismatches fail without removing the active project. For synced projects, a configured S3 upload must succeed before terminal cleanup. Successful closeout makes `refs/oat/completed/<project>` authoritative, deletes the tracked JSON record and nested checkout, and leaves archive metadata sufficient for an idempotent recordless retry. Legacy complete records receive a cleanup diagnosis rather than pull/open guidance. With `--json`, the terminal receipt reports `completedRef`, `verifiedSourceSha`, whether `activeAliasDisposition` was `retained` or `removed`, whether `recordRetired` completed, and the parent `lifecycleCommit`. `--no-commit` is a manual/library-only option: for a synced project it still removes the checkout but deliberately leaves `lifecycleCommit` null. Never pass it through `oat-project-complete`, which requires that receipt.
 - `oat repo archive sync [project-name]` - hydrate archived project snapshots from the configured repo-scoped S3 archive into `.oat/projects/archived/`. The old `oat project archive sync` path remains as a deprecated shim.
-- `oat project dispatch record --event-file <json-file-or-dash> [--project <project-path>]` - validate one generic dispatch record plus its namespaced OAT evidence event, and persist it into the project's append-only `dispatch/` journal. Omit `--project` to validate without persisting. Revision 1 is `dispatch/<request-id>.json` and every later revision is `dispatch/<request-id>@<NNNN>.json`; superseded revisions are never replaced or removed. The command validates and records evidence only — it never launches a provider. A `runtime-observation` event may carry either a finished `observation` or the provider `metadata` envelope (`provider`, `observedAt`, `entries`) to normalize, but not both. `entries` may be raw provider output: they are projected through the owning parser's allowlist, are never persisted, and both forms have their `match` derived from the record's configured invocation rather than trusted from the caller, with the observation's `provider` bound to the record's. With `--json`, the result adds `runtimeIdentity` with separate `configured` and `observed` objects plus a `match` of `matching`, `mismatching`, `not-comparable`, or `null`; observation is corroboration only and never overrides configured invocation. Error output is redacted on a best-effort basis; absolute paths in identity fields are rejected outright, while some prose forms (colon-prefixed, URL routes) can survive. See [Evidence Layers](../workflows/projects/evidence-layers.md).
+- `oat project dispatch record --event-file <json-file-or-dash> [--project <project-path>]` - validate one generic dispatch record plus its namespaced OAT evidence event, and persist it into the project's append-only `dispatch/` journal (optional; no lifecycle skill requires it). Omit `--project` to validate without persisting. Revision 1 is `dispatch/<request-id>.json` and every later revision is `dispatch/<request-id>@<NNNN>.json`; superseded revisions are never replaced or removed. The command validates and records evidence only — it never launches a provider. A `runtime-observation` event may carry either a finished `observation` or the provider `metadata` envelope (`provider`, `observedAt`, `entries`) to normalize, but not both. `entries` may be raw provider output: they are projected through the owning parser's allowlist, are never persisted, and both forms have their `match` derived from the record's configured invocation rather than trusted from the caller, with the observation's `provider` bound to the record's. With `--json`, the result adds `runtimeIdentity` with separate `configured` and `observed` objects plus a `match` of `matching`, `mismatching`, `not-comparable`, or `null`; observation is corroboration only and never overrides configured invocation. Error output is redacted on a best-effort basis; absolute paths in identity fields are rejected outright, while some prose forms (colon-prefixed, URL routes) can survive. See [Evidence Layers](../workflows/projects/evidence-layers.md).
 - `oat project validate-plan --project-path <path>` - validates `oat_plan_parallel_groups` metadata in `plan.md`; exits non-zero on invalid. Lite plans must contain exactly one phase, declare no parallel groups, and give every Validation Criteria bullet either a backticked command or a `manual:` instruction. See [Implementation Execution](../workflows/projects/implementation-execution.md#parallel-phase-groups).
 - `oat project log append|check|synthesize|rollup` - manage the optional append-only project observation log: append validated judgment or structural entries, inspect grammar and synthesis status, complete end-of-run synthesis, and roll observations into `summary.md` plus the configured repository ledger. See [Project Log](../cli-utilities/project-log.md).
 - `oat project set-mode` — deprecated no-op. Execution mode is no longer user-selectable; emits a deprecation warning and preserves the `--json` contract.

package/assets/docs/workflows/projects/evidence-layers.md

@@ -75,9 +75,12 @@ This layer maps to Dispatch Report V1 and its provenance record; see the
 [Dispatch Report V1 / producer provenance](dispatch-ceiling.md#dispatch-report-v1-and-producer-provenance)
 section.
 
-For project-aware work, OAT persists this native dispatch lineage as one
-generic record per request under the project's `dispatch/` directory. The
-generic snake-case fields remain authoritative. A namespaced `oat` block adds
+For project-aware work, the calling workflow records each launch in its run
+record in `implementation.md` (request ID, `Dispatch:` stamp, launch status,
+terminal outcome). Persisting one generic record per request under the
+project's `dispatch/` directory with `oat project dispatch record` is optional
+and off by default; no lifecycle skill or command consumes those files. When a
+host opts in, the generic snake-case fields remain authoritative. A namespaced `oat` block adds
 only canonical-role identity, proven pre-start rejection, fallback linkage,
 and optional runtime observation. `DispatchReportV1` and the parseable
 `Dispatch:` compatibility stamp keep their existing byte shape.

package/assets/docs/workflows/projects/implementation-execution.md

@@ -73,9 +73,10 @@ The root does not implement phase tasks while an accepted phase launch owns
 that scope.
 
 Before a native launch, the root constructs and redacts the complete generic
-dispatch record and OAT role event. Immediately after the host returns, it runs
-`oat project dispatch record --project <project-path> --event-file - --json`
-with the accepted or `blocked-before-start` result. An accepted launch closes
+dispatch record and OAT role event. When the host returns, it writes the
+request ID, the `Dispatch:` stamp, and the accepted or `blocked-before-start`
+result into the run record in `implementation.md`; persisting a per-dispatch
+file with `oat project dispatch record` is optional and off by default. An accepted launch closes
 replacement. Only an explicit rejection proving no child started permits one
 fresh request that preserves the exact target and controls and is labeled as
 an approximation. Timeout, `BLOCKED`, refusal after acceptance, runtime

package/assets/docs/workflows/projects/orchestration-model.md

@@ -123,10 +123,12 @@ launch.
 ## Native Dispatch Lineage
 
 The launcher constructs and redacts the complete generic record plus the
-namespaced OAT role event before it calls the native host. Immediately after
-the host returns, the project adapter validates and persists the accepted or
-`blocked-before-start` state with `oat project dispatch record`. The command is
-a recorder only; it never launches a provider or changes selection authority.
+namespaced OAT role event before it calls the native host. When the host
+returns, the calling workflow writes the accepted or `blocked-before-start`
+state into its run record in `implementation.md`. Persisting a per-dispatch
+file with `oat project dispatch record` is optional and off by default; the
+command is a recorder only and never launches a provider or changes selection
+authority.
 
 An accepted handle owns the scope and closes replacement. One fresh fallback
 record is legal only when the native wrapper proves no child started, links the

package/assets/public-package-versions.json

@@ -1,6 +1,6 @@
 {
-  "cli": "0.2.67",
-  "docs-config": "0.2.67",
-  "docs-theme": "0.2.67",
-  "docs-transforms": "0.2.67"
+  "cli": "0.2.69",
+  "docs-config": "0.2.69",
+  "docs-theme": "0.2.69",
+  "docs-transforms": "0.2.69"
 }

package/assets/skills/oat-dispatch-subagents/SKILL.md

@@ -5,7 +5,7 @@ disable-model-invocation: true
 user-invocable: false
 allowed-tools: Read
 metadata:
-  version: 1.2.7
+  version: 1.2.8
 ---
 
 # Dispatching OAT Subagents
@@ -175,7 +175,9 @@ terminal outcome, not a pre-start rejection, and must be recorded through
 `child_outcome`. If you cannot prove the child never existed, you cannot set
 `provesNoChildStarted: true`, and no fallback is authorized.
 
-Project-aware callers pass the validated record and event on standard input:
+The calling workflow records each launch in its own run record (request ID,
+`Dispatch:` stamp, launch status, terminal outcome). Writing a per-dispatch file with `oat project dispatch record` is optional and off by default: no lifecycle skill or command consumes those files, so do not write them unless the host has explicitly opted in. A host that has opted
+in passes the validated record and event on standard input:
 
 ```bash
 oat project dispatch record \

package/assets/skills/oat-project-autonomous/references/gate-inventory.md

@@ -82,7 +82,8 @@ artifact already owned by the calling workflow:
 
 - planning and artifact decisions: the relevant artifact plus its review row;
 - implementation and boundary decisions: `implementation.md`;
-- review and dispatch decisions: the dispatch record schema and the referenced
+- review and dispatch decisions: the run record in `implementation.md` (request
+  ID, `Dispatch:` stamp, launch status, terminal outcome) and the referenced
   review artifact;
 - gate execution: structured gate result, attempt count, and disposition;
 - documentation and completion decisions: `state.md` and the normal summary or

package/assets/skills/oat-project-dispatch-subagents/SKILL.md

@@ -5,7 +5,7 @@ disable-model-invocation: true
 user-invocable: false
 allowed-tools: Read, Bash
 metadata:
-  version: 1.1.5
+  version: 1.1.6
 ---
 
 # Dispatching OAT Project Subagents
@@ -152,12 +152,14 @@ For every lifecycle dispatch:
 9. Add lifecycle outcome metadata and let the calling workflow perform state,
    plan, implementation-log, commit, or review-table writes.
 
-### Persist native dispatch lineage
+### Record the launch
 
-For project-aware launches, apply the generic engine's native dispatch lineage
-contract. Construct and redact the complete generic record plus OAT event
-before the native host call. Immediately after the call returns accepted or
-`blocked-before-start`, persist the result with:
+For project-aware launches, construct and redact the complete generic record
+plus OAT event before the native host call. When the call returns accepted or
+`blocked-before-start`, the calling workflow writes the request ID, the
+`Dispatch:` stamp, the launch status, and later the terminal outcome into its
+run record in `implementation.md`. Writing a per-dispatch file with `oat project dispatch record` is optional and off by default: no lifecycle skill or command consumes those files, so do not write them unless the host has explicitly opted in. A host that has opted in persists the
+validated record with:
 
 ```bash
 oat project dispatch record \
@@ -166,7 +168,7 @@ oat project dispatch record \
   --json
 ```
 
-The accepted record closes replacement. A rejected record must include
+An accepted launch closes replacement. A rejected record must include
 `provesNoChildStarted: true` before one target-preserving canonical-instruction
 fallback may receive its own fresh request ID. Preserve exact provider, model,
 effort, reasoning mode, service tier, route, authority, payload controls,

package/assets/skills/oat-project-document/references/docs/autonomy-contract.md

@@ -82,7 +82,8 @@ artifact already owned by the calling workflow:
 
 - planning and artifact decisions: the relevant artifact plus its review row;
 - implementation and boundary decisions: `implementation.md`;
-- review and dispatch decisions: the dispatch record schema and the referenced
+- review and dispatch decisions: the run record in `implementation.md` (request
+  ID, `Dispatch:` stamp, launch status, terminal outcome) and the referenced
   review artifact;
 - gate execution: structured gate result, attempt count, and disposition;
 - documentation and completion decisions: `state.md` and the normal summary or

package/assets/skills/oat-project-implement/SKILL.md

@@ -7,7 +7,7 @@ disable-model-invocation: true
 user-invocable: true
 allowed-tools: Read, Write, Bash(git:*), Bash(oat:*), Bash(oat project log:*), Glob, Grep, AskUserQuestion, Task
 metadata:
-  version: 2.3.7
+  version: 2.3.8
 ---
 
 # Implementation Phase

package/assets/skills/oat-project-implement/references/dispatch-and-dry-run.md

@@ -393,16 +393,17 @@ For gate-originated review, keep `dispatchReport.gateInvocation`, existing
 work-producer `diversity`, and reviewer `runtimeIdentity` as three distinct
 facts; producer stamps or self-report never overwrite configured invocation.
 
-All project-aware launch paths preserve native dispatch lineage. Construct and
-redact the complete generic record plus OAT role event before the native host
-call. Immediately after the call returns `accepted` or
-`blocked-before-start`, run `oat project dispatch record --project
-"$PROJECT_PATH" --event-file - --json`. The rejected form must attest
-`provesNoChildStarted: true`; only it permits one exact-target approximation
-with a fresh request ID. Preserve exact model, effort, reasoning, service tier,
-route, authority, and provider controls. Timeout, `BLOCKED`, refusal after
-acceptance, runtime mismatch, missing telemetry, interruption, or malformed
-output never authorizes fallback or replacement.
+All project-aware launch paths record the launch in the project's run record.
+Construct and redact the complete generic record plus OAT role event before the
+native host call; when the call returns `accepted` or `blocked-before-start`,
+write the request ID, the `Dispatch:` stamp, the launch status, and later the
+terminal outcome into the run record in `implementation.md`. Writing a per-dispatch file with `oat project dispatch record` is optional and off by default: no lifecycle skill or command consumes those files, so do not write them unless the host has explicitly opted in. A rejected
+launch must attest `provesNoChildStarted: true`; only it permits one
+exact-target approximation with a fresh request ID. Preserve exact model,
+effort, reasoning, service tier, route, authority, and provider controls.
+Timeout, `BLOCKED`, refusal after acceptance, runtime mismatch, missing
+telemetry, interruption, or malformed output never authorizes fallback or
+replacement.
 
 Axis states:
 

package/assets/skills/oat-project-implement/references/docs/autonomy-contract.md

@@ -82,7 +82,8 @@ artifact already owned by the calling workflow:
 
 - planning and artifact decisions: the relevant artifact plus its review row;
 - implementation and boundary decisions: `implementation.md`;
-- review and dispatch decisions: the dispatch record schema and the referenced
+- review and dispatch decisions: the run record in `implementation.md` (request
+  ID, `Dispatch:` stamp, launch status, terminal outcome) and the referenced
   review artifact;
 - gate execution: structured gate result, attempt count, and disposition;
 - documentation and completion decisions: `state.md` and the normal summary or

package/assets/skills/oat-project-lite/references/docs/autonomy-contract.md

@@ -82,7 +82,8 @@ artifact already owned by the calling workflow:
 
 - planning and artifact decisions: the relevant artifact plus its review row;
 - implementation and boundary decisions: `implementation.md`;
-- review and dispatch decisions: the dispatch record schema and the referenced
+- review and dispatch decisions: the run record in `implementation.md` (request
+  ID, `Dispatch:` stamp, launch status, terminal outcome) and the referenced
   review artifact;
 - gate execution: structured gate result, attempt count, and disposition;
 - documentation and completion decisions: `state.md` and the normal summary or

package/assets/skills/oat-project-plan-writing/SKILL.md

@@ -5,7 +5,7 @@ disable-model-invocation: true
 user-invocable: false
 allowed-tools: Read, Write, Glob, Grep
 metadata:
-  version: 1.2.24
+  version: 1.2.25
 ---
 
 # Plan Writing Contract
@@ -261,11 +261,12 @@ unavailable in the current session. Base Codex roles are allowed only for
 explicit inherit/default behavior and the documented managed-uncapped reviewer
 fallback.
 
-Artifact-review launches preserve native dispatch lineage. Construct and
-redact the complete generic record plus OAT role event before the native call.
-Immediately after the call returns `accepted` or `blocked-before-start`, the
-calling project workflow runs `oat project dispatch record --project
-"$PROJECT_PATH" --event-file - --json`. Only a rejection attesting
+Artifact-review launches write no launch record. The only launch evidence is
+the `Dispatch:` stamp the reviewer already copies into its dispatch audit
+metadata; nothing is written to `implementation.md` (which may not exist yet
+during planning) and no request-id, launch-status, or outcome field is added to
+any artifact or ledger column. Construct and redact the complete generic record
+plus OAT role event before the native call. Writing a per-dispatch file with `oat project dispatch record` is optional and off by default: no lifecycle skill or command consumes those files, so do not write them unless the host has explicitly opted in. Only a rejection attesting
 `provesNoChildStarted: true` permits one exact-target approximation with a
 fresh request ID. Preserve exact model, effort, route, authority, and provider
 controls. Timeout, `BLOCKED`, refusal after acceptance, runtime mismatch,

package/assets/skills/oat-project-pr-final/references/docs/autonomy-contract.md

@@ -82,7 +82,8 @@ artifact already owned by the calling workflow:
 
 - planning and artifact decisions: the relevant artifact plus its review row;
 - implementation and boundary decisions: `implementation.md`;
-- review and dispatch decisions: the dispatch record schema and the referenced
+- review and dispatch decisions: the run record in `implementation.md` (request
+  ID, `Dispatch:` stamp, launch status, terminal outcome) and the referenced
   review artifact;
 - gate execution: structured gate result, attempt count, and disposition;
 - documentation and completion decisions: `state.md` and the normal summary or

package/assets/skills/oat-project-quick-start/references/docs/autonomy-contract.md

@@ -82,7 +82,8 @@ artifact already owned by the calling workflow:
 
 - planning and artifact decisions: the relevant artifact plus its review row;
 - implementation and boundary decisions: `implementation.md`;
-- review and dispatch decisions: the dispatch record schema and the referenced
+- review and dispatch decisions: the run record in `implementation.md` (request
+  ID, `Dispatch:` stamp, launch status, terminal outcome) and the referenced
   review artifact;
 - gate execution: structured gate result, attempt count, and disposition;
 - documentation and completion decisions: `state.md` and the normal summary or

package/assets/skills/oat-project-review-provide/SKILL.md

@@ -5,7 +5,7 @@ disable-model-invocation: false
 user-invocable: true
 allowed-tools: Read, Glob, Grep, Write, Edit, Bash(git:*), Bash(oat:*), Bash(pnpm:*), Bash(mkdir:*), Bash(date:*), Bash(realpath:*), Bash(awk:*), AskUserQuestion
 metadata:
-  version: 1.5.7
+  version: 1.5.8
 ---
 
 # Request Review
@@ -751,15 +751,16 @@ After constructing the complete provider payload, record the launcher-owned
 missing telemetry, missing reviewer self-report, or contradictory self-report
 must not populate, replace, or overwrite them and must not trigger fallback.
 
-Persist native dispatch lineage around the host-owned review launch. Construct
-and redact the complete generic record plus OAT role event before the native
-call. Immediately after the call returns `accepted` or
-`blocked-before-start`, run `oat project dispatch record --project
-"$PROJECT_PATH" --event-file - --json`. The rejected form must attest
-`provesNoChildStarted: true`; only it permits one exact-target approximation
-with a fresh request ID. Preserve the exact model, effort, route, authority,
-and provider controls. Timeout, `BLOCKED`, refusal after acceptance, runtime
-mismatch, missing telemetry, interruption, and malformed output never
+This rail writes no launch record. Its only launch evidence is the `Dispatch:`
+stamp it already copies into the review artifact's dispatch audit metadata
+(Step 6.0); it never writes `implementation.md` (this rail requires that file
+clean and never commits it) and adds no request-id, launch-status, or outcome
+field to any artifact or ledger column. Construct and redact the complete
+generic record plus OAT role event before the native call. Writing a per-dispatch file with `oat project dispatch record` is optional and off by default: no lifecycle skill or command consumes those files, so do not write them unless the host has explicitly opted in. A rejected launch must
+attest `provesNoChildStarted: true`; only it permits one exact-target
+approximation with a fresh request ID. Preserve the exact model, effort, route,
+authority, and provider controls. Timeout, `BLOCKED`, refusal after acceptance,
+runtime mismatch, missing telemetry, interruption, and malformed output never
 authorize fallback or replacement.
 
 Once the native host accepts a reviewer, every terminal result is an

package/assets/skills/oat-project-review-provide-remote/SKILL.md

@@ -5,7 +5,7 @@ disable-model-invocation: true
 user-invocable: true
 allowed-tools: Read, Write, Bash, Glob, Grep, Task, AskUserQuestion
 metadata:
-  version: 1.1.4
+  version: 1.1.5
 ---
 
 # Remote Review Provide (Project-Scoped GitHub PR)
@@ -319,11 +319,12 @@ route. After acceptance, continue only through the existing reviewer handle;
 timeout, interruption, malformed output, or `BLOCKED` never authorizes a
 replacement launch.
 
-Persist native dispatch lineage around the host-owned remote-review launch.
-Construct and redact the complete generic record plus OAT role event before the
-native call. Immediately after the call returns `accepted` or
-`blocked-before-start`, run `oat project dispatch record --project
-"$PROJECT_PATH" --event-file - --json`. The rejected form must attest
+This rail writes no launch record. Its only launch evidence is the `Dispatch:`
+stamp it already copies into the posted review's dispatch audit metadata; it
+never writes `implementation.md` (the remote rail runs in an ephemeral worktree
+and forbids that mutation) and adds no request-id, launch-status, or outcome
+field anywhere. Construct and redact the complete generic record plus OAT role
+event before the native call. Writing a per-dispatch file with `oat project dispatch record` is optional and off by default: no lifecycle skill or command consumes those files, so do not write them unless the host has explicitly opted in. A rejected launch must attest
 `provesNoChildStarted: true`; only it permits one exact-target approximation
 with a fresh request ID. Preserve exact model, effort, route, authority, and
 provider controls. Timeout, `BLOCKED`, refusal after acceptance, runtime

package/assets/skills/oat-wave-execute/SKILL.md

@@ -6,7 +6,7 @@ disable-model-invocation: false
 user-invocable: true
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Task
 metadata:
-  version: 1.9.2
+  version: 1.9.3
 ---
 
 # Execute a Wave of External Plans
@@ -235,9 +235,18 @@ writes and stay on the orchestrator's own model class, the same rule
 
 Run the cross-runtime artifact gate with a **bounded** prompt (rule 6): review the
 wrapper artifacts for plan invariants, contract consistency, frontmatter validity,
-and whether any task restates/narrows its source plan — the external plans are
-immutable inputs, NOT review targets. Disposition findings in-artifact
-(gate-invoked artifact review) and commit. A plan gate MAY PROCEED at
+and whether any task restates/narrows its source plan. The external plans'
+content is immutable to the wave (the gate never rewrites a plan), but a plan is
+a legitimate target for one question: whether its proposed mechanism materially
+serves the requested outcome. A reviewer who finds substantial machinery with no
+identifiable consumer — an agent acting on a named instruction, a human reading
+a named surface, or code at a named call site — or a smaller approach that
+preserves the requirements, reports it as a necessity finding. The root returns
+that plan to its author (`oat-repo-improve`) for disposition and defers it from
+this wave until dispositioned; it never silently drops or narrows it, and an
+explicitly stated user requirement is honored over a preference for simplicity.
+Disposition the remaining findings in-artifact (gate-invoked artifact review)
+and commit. A plan gate MAY PROCEED at
 `fixes_completed` per the wave-0/1 precedent, but that is a proceed point, not a
 terminal state. Every gate row MUST flip to `passed` once all fix dispositions
 carry the stored verification records required by the fix-disposition contract below;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@open-agent-toolkit/cli",
-  "version": "0.2.67",
+  "version": "0.2.69",
   "private": false,
   "description": "Open Agent Toolkit CLI",
   "homepage": "https://github.com/voxmedia/open-agent-toolkit/tree/main/packages/cli",
@@ -34,7 +34,7 @@
     "ora": "^9.0.0",
     "yaml": "2.8.2",
     "zod": "^3.25.76",
-    "@open-agent-toolkit/control-plane": "0.2.67"
+    "@open-agent-toolkit/control-plane": "0.2.69"
   },
   "devDependencies": {
     "@types/node": "^22.10.0",