@open-agent-toolkit/cli 0.1.48 → 0.1.50

package/assets/docs/cli-utilities/configuration.md

@@ -381,6 +381,47 @@ has verified equivalent current-host controls for explicit inherit,
 managed-uncapped, or base-role behavior. Capped managed reviews still require
 the exact registered role, pinned child, or resolver-returned model argument.
 
+### Cursor validation pass and live evidence
+
+Config adoption and doctor validate Cursor candidates with one command-scoped
+pass context. Duplicate references to the same byte-for-byte candidate share
+one Task/subagent probe. If a decisive probe is unavailable, the pass resolves
+the broad catalog once, with at most one `--list-models` fallback. The cache
+ends with that adopt or doctor command; it is not process-global and has no
+TTL.
+
+A correlated Task start/completion pair that preserves the exact model argument
+and returns the sentinel establishes that the argument is eligible for that
+account and client. A structured rejection or exact allow-list exclusion can
+establish `unknown-value`. Neither result identifies the backend runtime model:
+`runtimeIdentity` remains `not-reported` unless trusted Cursor telemetry or
+Cursor support confirms it. Parent prose and broad catalog presence are
+diagnostic-only, so OAT preserves `unvalidated` when launcher evidence is
+absent instead of inferring capability from candidate spelling.
+
+The [dated GPT-5.6 Cursor verification evidence](https://github.com/voxmedia/open-agent-toolkit/blob/main/.oat/repo/reference/project-summaries/20260711-cursor-gpt-5-6-subagent-verification.md)
+preserves the original text-mode pass and a versioned stream-JSON second pass.
+The second pass ran a dynamic positive control and deliberate invalid control
+before candidates. Both parent runs completed without a Task event, making the
+controls inconclusive; the stop rule therefore executed zero of the 13
+recommended candidates and did not execute exploratory
+`gpt-5.6-sol-high-fast`. The recommendation remains unchanged and candidate
+eligibility remains unresolved.
+
+The tracked artifact's structured second-pass block contains only allowlisted
+event structure, derived outcomes, sanitized auth-presence context, and
+non-reversible identifier hashes. Exact request/session/tool-call IDs and
+credential-redacted unprojected streams from that pass stay under gitignored
+`.oat/projects/local/` storage for possible Cursor support diagnosis.
+
+The same public artifact intentionally retains the sanitized historical v1
+text-mode record for provenance. That older section includes command arguments
+and prompts, stdout and stderr, exit and duration data, and capture-environment
+details such as user-specific binary paths; it is not limited to the structured
+second-pass allowlist. Re-run after a Cursor client rollout exposes Task in
+headless mode or Cursor support confirms the private requests; review the open
+verification item by 2026-08-08.
+
 ### Legacy compatibility
 
 The command and docs path retain `dispatch-ceiling` for compatibility. Legacy

package/assets/docs/cli-utilities/workflow-gates.md

@@ -94,6 +94,23 @@ model that ran, and the reviewer must not replace them with self-identification.
 The CLI compares the copied values with its gate-owned record before it applies
 the severity threshold.
 
+### Gate dispatch report semantics
+
+When gate dispatch is represented in a `DispatchReportV1`, consumers require
+`schemaVersion: 1` and keep three facts independent:
+
+- `gateInvocation` is the immutable configured run ID, target, runtime, model,
+  reasoning effort, and source.
+- `runtimeIdentity` is observed or otherwise supported producer identity; it is
+  `not-reported` when no runtime evidence exists.
+- gate `diversity` describes producer/reviewer routing and achieved separation;
+  it does not overwrite either configured invocation or runtime identity.
+
+Configured target values, requested controls, producer stamps, and reviewer
+self-report are not interchangeable. The human report is rendered from the
+versioned object, and any parseable `Dispatch:` compatibility line is derived
+from that same report rather than rebuilt from target IDs or model names.
+
 ### Review project resolution and corroboration
 
 `--project <path-or-name>` is a declaration. OAT normalizes the declared path

package/assets/docs/provider-sync/providers.md

@@ -21,7 +21,11 @@ description: 'Provider-specific path mappings for Claude, Cursor, Copilot, Gemin
     - Subagent invocation in Cursor is prompt-driven (`/name` or natural mention), not `subagent_type`
     - OAT-controlled Cursor dispatch uses the generic `.cursor/agents/<name>.md` file plus the exact `providers.cursor.dispatchArgs.model` value selected from the candidate ladder. OAT passes it byte-for-byte as the actual Task-level `model`; a `model` frontmatter value is only a default/fallback mechanism.
     - Cursor model strings are opaque. OAT does not infer family, effort, cost, or capability from their spelling; the configured candidate position owns the named tier meaning.
-    - Cursor model validation checks whether the selected model is eligible for subagent Task dispatch; the broad `cursor-agent models` catalog alone is not enough proof.
+    - Cursor model validation checks whether the selected model is eligible for subagent Task dispatch. Each adopt/doctor command probes each distinct exact candidate once and shares one lazy broad-catalog lookup across that pass; the cache ends with the command.
+    - A correlated accepted Task carrying the exact model argument plus the child sentinel proves argument eligibility for that account/client. It does not prove backend runtime identity; that remains `not-reported` without trusted Cursor telemetry or support confirmation. Structured rejection can establish `unknown-value`, while parent prose and broad `cursor-agent models` catalog presence remain diagnostic-only.
+    - The [dated GPT-5.6 verification artifact](https://github.com/voxmedia/open-agent-toolkit/blob/main/.oat/repo/reference/project-summaries/20260711-cursor-gpt-5-6-subagent-verification.md) preserves the original probe and a stream-JSON control pass. The controls observed no Task events, so the stop rule ran zero recommendation or exploratory candidates and retained the recommendation unchanged.
+    - The artifact's structured second-pass block contains only allowlisted event fields, derived outcomes, sanitized auth presence, and identifier hashes. Exact request/session/tool-call IDs and credential-redacted unprojected streams from that pass remain in gitignored local project storage for support escalation.
+    - The same public artifact retains the sanitized historical v1 text-mode record for provenance. That older section includes command arguments and prompts, stdout and stderr, exit and duration data, and capture-environment details such as user-specific binary paths; it is not limited to the structured second-pass allowlist.
     - Rule files render as `.cursor/rules/*.mdc`
 
 === "Copilot"

package/assets/docs/workflows/projects/dispatch-ceiling.md

@@ -263,6 +263,33 @@ Reviewers use the final candidate at the configured review ceiling. Managed
 reviewer behavior. A timeout retry preserves the same exact role or complete
 Claude/Cursor model payload.
 
+### Cursor evidence authority
+
+Cursor resolution and runtime evidence answer different questions. Resolution
+proves which opaque candidate OAT requested. A stream-JSON Task start and
+correlated completion prove launcher behavior only when the model argument is
+preserved byte-for-byte. An accepted Task plus the child sentinel establishes
+argument eligibility for that account and client; a structured rejection can
+establish `unknown-value`. Runtime producer identity remains `not-reported`
+unless trusted Cursor telemetry or Cursor support independently confirms it.
+
+The [2026-07-11 GPT-5.6 evidence record](https://github.com/voxmedia/open-agent-toolkit/blob/main/.oat/repo/reference/project-summaries/20260711-cursor-gpt-5-6-subagent-verification.md)
+ran positive and negative controls before candidate probes. Neither control
+emitted a Task event, so the harness stopped without probing the 13 recommended
+arguments or exploratory `gpt-5.6-sol-high-fast`. This is a harness/account
+boundary, not model rejection, and it supports no recommendation change.
+
+The tracked artifact's structured second-pass block exposes only an allowlisted
+event projection and non-reversible identifier hashes. Exact
+request/session/tool-call IDs and credential-redacted unprojected streams from
+that pass stay in gitignored local project storage for support diagnosis.
+
+The same public artifact intentionally preserves the sanitized historical v1
+text-mode record for provenance. That older section includes command arguments
+and prompts, stdout and stderr, exit and duration data, and capture-environment
+details such as user-specific binary paths; it is not limited to the structured
+second-pass projection.
+
 ## Coordinator and Worker Layers
 
 `oat-phase-implementer` has two explicit modes:
@@ -279,19 +306,44 @@ Workers run serially in the same worktree. Parallelism remains limited to
 plan-declared phase worktrees. See
 [Implementation Execution](implementation-execution.md) for the full loop.
 
-## Producer Provenance
+## Dispatch Report V1 and Producer Provenance
+
+Resolver calls that pass `--report-scope` and `--report-action` include a
+`dispatchReport` object in JSON output. Consumers must require
+`dispatchReport.schemaVersion: 1` before dispatch. The report keeps four
+different decisions separate:
+
+| Report area                                                         | What it means                                                        |
+| ------------------------------------------------------------------- | -------------------------------------------------------------------- |
+| `policy`                                                            | The resolved managed/inherit policy, its status, name, and source    |
+| `selection.ceilingTier` / `selection.ceilingTarget`                 | The maximum allowed tier and its boundary target                     |
+| `selection.requestedCandidate` / `candidateTier` / `candidateIndex` | The exact candidate requested for this bounded task and its position |
+| `selection.exactSelectedTarget` / `route.target`                    | The compiled provider target and actual invocation route             |
+
+A named policy or ceiling is never a substitute for the requested candidate or
+exact selected target. `requestedControls` records what OAT put into the host
+payload. `configuredDefaults` records fallback configuration and is explicitly
+not a runtime observation.
+
+`gateInvocation` is an immutable copy of configured gate controls.
+`runtimeIdentity` is separate and stays `not-reported` until independently
+observed or otherwise supported runtime evidence exists. Requested controls,
+configured defaults, role-name parsing, and reviewer self-identification do not
+become observed runtime identity.
 
-Dispatch notes retain a parseable stamp for later review gates:
+Human output comes from `formatDispatchReport(dispatchReport)`. Dispatch notes
+also retain a parseable compatibility stamp for later review gates:
 
 ```text
 Dispatch: scope=p06-t03 action=implementation role=implementer producer=gpt-5.6-sol provenance=declared model_axis=selected:gpt-5.6-sol effort_axis=selected:high dispatch_policy=high dispatch_ceiling=high target=oat-phase-implementer-gpt-5-6-sol-high
 ```
 
-`producer` is the resolved model slug when OAT can establish it; otherwise it is
-`unknown`. `provenance` is `declared`, `observed`, `inferred`, or `unknown`.
-Concrete Claude/Cursor model arguments can declare identity. Codex roles retain
-exact model and effort axes from resolver output even when producer identity is
-not independently observable.
+The stamp must be derived through `toDispatchStampRecord(dispatchReport)` and
+`formatDispatchStamp`; callers must not reconstruct it from policy labels, role
+names, candidate strings, or target names. `producer` is the runtime model slug
+when OAT can establish it; otherwise it is `unknown`. `provenance` is
+`declared`, `observed`, `inferred`, or `unknown`. Selected model and effort axes
+can remain exact even when runtime producer identity is not reported.
 
 ## Legacy Compatibility
 

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

@@ -88,6 +88,18 @@ import performs the same readiness setup:
 
 See [Dispatch Policy](dispatch-ceiling.md) for ladder shapes and ownership.
 
+### Validating plan metadata
+
+Before building the phase schedule, implementation validates plan parallelism:
+
+```bash
+oat project validate-plan --project-path .oat/projects/shared/example
+```
+
+The command rejects malformed groups, unknown phase IDs, duplicate membership,
+and singleton groups. Invalid metadata blocks execution rather than silently
+falling back to a different schedule.
+
 Before phase work, implementation runs provider preflight:
 
 ```bash
@@ -204,6 +216,28 @@ If exact controls cannot be applied, fail closed. A transient retry reuses the
 same complete provider payload. Substantive escalation re-resolves another
 configured candidate within the same named maximum and bounded retry budget.
 
+## Dispatch Reports During Execution
+
+Every implementation, fix, and review resolver call supplies explicit report
+context:
+
+```text
+--report-scope <phase-or-task> --report-action <implementation|fix|review>
+```
+
+The completed JSON must contain `dispatchReport.schemaVersion: 1` before the
+provider invocation begins. The coordinator reads the requested candidate,
+candidate tier, ceiling, exact selected target, requested controls, configured
+defaults, and runtime identity from that report as distinct fields. It does not
+infer any of them from a materialized role name or opaque Cursor string.
+
+The human dispatch block is rendered from the report. The formal `Dispatch:`
+line is a compatibility view derived from the same report through the dispatch
+stamp adapter. It is not a second schema and must not be assembled by hand.
+Configured defaults and configured gate invocation remain distinct from runtime
+identity; when runtime identity is not observed, the report says so without
+weakening exact requested model or effort controls.
+
 ## Task Scope and Commit Verification
 
 Each worker receives only one task:

package/assets/public-package-versions.json

@@ -1,6 +1,6 @@
 {
-  "cli": "0.1.48",
-  "docs-config": "0.1.48",
-  "docs-theme": "0.1.48",
-  "docs-transforms": "0.1.48"
+  "cli": "0.1.50",
+  "docs-config": "0.1.50",
+  "docs-theme": "0.1.50",
+  "docs-transforms": "0.1.50"
 }

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

@@ -1,6 +1,6 @@
 ---
 name: oat-project-implement
-version: 2.0.33
+version: 2.0.34
 description: Use when plan.md is ready for execution. Dispatches phase coordinators that select one exact target-pinned worker per task; supports bounded fix loops and plan-declared worktree-isolated parallel phases.
 oat_gateable: true
 argument-hint: '[--retry-limit <N>] [--dry-run]'
@@ -193,13 +193,13 @@ Use the CLI resolver as the source of truth. The command name remains
 policy:
 
 ```bash
-oat project dispatch-ceiling resolve --provider <active-provider> --preflight --json
+oat project dispatch-ceiling resolve --provider <active-provider> --preflight --report-scope implementation-preflight --report-action implementation --json
 ```
 
 If `oat` is not in PATH, use:
 
 ```bash
-pnpm run cli -- project dispatch-ceiling resolve --provider <active-provider> --preflight --json
+pnpm run cli -- project dispatch-ceiling resolve --provider <active-provider> --preflight --report-scope implementation-preflight --report-action implementation --json
 ```
 
 Resolution order:
@@ -345,7 +345,7 @@ exists, rerun the resolver with non-interactive behavior and stop before work
 starts if it blocks:
 
 ```bash
-oat project dispatch-ceiling resolve --provider <active-provider> --preflight --non-interactive
+oat project dispatch-ceiling resolve --provider <active-provider> --preflight --non-interactive --report-scope implementation-preflight --report-action implementation
 ```
 
 ```text
@@ -390,6 +390,32 @@ an ordered matrix route:
   entry before retrying, up to the last available route entry and within
   `oat_orchestration_retry_limit`.
 
+#### Dispatch Report V1 contract
+
+Every implementation, fix, and review resolver invocation MUST pass explicit
+report context:
+
+- implementation: `--report-scope <phase-or-task> --report-action implementation`
+- fix: `--report-scope <phase-or-task> --report-action fix`
+- review: `--report-scope <phase-or-review-scope> --report-action review`
+
+Require `dispatchReport.schemaVersion: 1` in the completed resolver JSON before
+dispatch. Consume the report as the human/audit source: render the versioned
+block with `formatDispatchReport(dispatchReport)` semantics, and derive the
+formal compatibility line only through
+`formatDispatchStamp(dispatchReport)` / `toDispatchStampRecord(dispatchReport)`.
+Never hand-assemble a second `Dispatch:` schema from policy labels, role names,
+candidate strings, or target names.
+
+The exact provider invocation remains authoritative in
+`providers.<provider>.dispatchArgs` and `providers.<provider>.selection.target`;
+the report does not replace or weaken target-pinned dispatch. Add independently
+observed runtime identity to `dispatchReport.runtimeIdentity` only when such an
+observation exists. Requested/configured controls are not runtime observation.
+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.
+
 Axis states:
 
 - `selected:<value>` - host exposes the axis and the orchestrator chose a value.
@@ -422,8 +448,8 @@ fallback.
 3. For capped managed implementer/fix work, selected effort is `min(preferred, resolved_cap)`.
 4. For managed `Uncapped` implementer/fix work, selected effort is the preferred effort with no cap.
 5. For inherit/default mode, the resolver returns no selected dispatch args. Use the base/unpinned Codex role, log `Selected effort: provider-default`, display provider default effort when known, and do not describe this as managed uncapped behavior.
-6. For managed capped task-worker/fix dispatch, choose an exact configured candidate and call `oat project dispatch-ceiling resolve --provider codex --role implementer --ceiling-tier <project-or-phase-tier> --candidate-model <model> --candidate-effort <effort> --escalation-level <route-level> --json`. Read `providers.codex.dispatchArgs.variant` and `providers.codex.selection.target`; never reuse the coordinator role or a cap-only variant. `--preferred` remains compatibility behavior outside the exact task-worker path.
-7. For review dispatch: call `oat project dispatch-ceiling resolve --provider codex --role reviewer`; read `providers.codex.dispatchArgs.variant` and `providers.codex.selection.target`.
+6. For managed capped task-worker/fix dispatch, choose an exact configured candidate. For implementation, call `oat project dispatch-ceiling resolve --provider codex --role implementer --ceiling-tier <project-or-phase-tier> --candidate-model <model> --candidate-effort <effort> --escalation-level <route-level> --report-scope <task-id> --report-action implementation --json`. For a bounded fix, use `oat project dispatch-ceiling resolve --provider codex --role implementer --ceiling-tier <project-or-phase-tier> --candidate-model <model> --candidate-effort <effort> --escalation-level <route-level> --report-scope <task-id> --report-action fix --json`. Read `providers.codex.dispatchArgs.variant` and `providers.codex.selection.target`; never reuse the coordinator role or a cap-only variant. `--preferred` remains compatibility behavior outside the exact task-worker path.
+7. For review dispatch: call `oat project dispatch-ceiling resolve --provider codex --role reviewer --report-scope <phase-or-review-scope> --report-action review --json`; read `providers.codex.dispatchArgs.variant` and `providers.codex.selection.target`.
    - Capped managed policy: reviewer targets the configured cap for deterministic quality gate behavior.
    - Managed `Uncapped`: no reviewer target exists; use base/unpinned reviewer fallback and log `selectionMode=no-review-target`, `selectedValue=null`, and `effort_axis=provider-default`.
    - Inherit/default: no reviewer target exists; use base/unpinned reviewer fallback and log `selectionMode=inherit-default`, `selectedValue=null`, and `effort_axis=provider-default`.
@@ -440,7 +466,7 @@ Claude rules:
 - Review dispatch:
   - Capped managed policy: target the configured policy cap directly.
   - Managed `Uncapped` or inherit/default: no reviewer target exists; omit `model` and log inherited/default model behavior.
-- For managed capped task-worker/fix dispatch, call `oat project dispatch-ceiling resolve --provider claude --role implementer --ceiling-tier <project-or-phase-tier> --candidate-model <model> --orchestrator-tier <current-orchestrator-tier> --escalation-level <route-level> --json`; for review dispatch, call the resolver with `--role reviewer` and no candidate flags. Read `providers.claude.dispatchArgs.model` and pass it exactly on the actual Task invocation.
+- For managed capped task-worker/fix dispatch, call `oat project dispatch-ceiling resolve --provider claude --role implementer --ceiling-tier <project-or-phase-tier> --candidate-model <model> --orchestrator-tier <current-orchestrator-tier> --escalation-level <route-level> --report-scope <task-id> --report-action implementation --json` for implementation. For a bounded fix, call `oat project dispatch-ceiling resolve --provider claude --role implementer --ceiling-tier <project-or-phase-tier> --candidate-model <model> --orchestrator-tier <current-orchestrator-tier> --escalation-level <route-level> --report-scope <task-id> --report-action fix --json`. For review dispatch, call the resolver with `--role reviewer --report-scope <phase-or-review-scope> --report-action review --json` and no candidate flags. Read `providers.claude.dispatchArgs.model` and pass it exactly on the actual Task invocation.
 - Pass `model: "<value>"` when `model_axis=selected:<value>` on the Task tool call.
 - Keep `effort_axis=not-applicable`; Claude Code has no separate per-dispatch effort axis.
 
@@ -448,9 +474,10 @@ Cursor rules:
 
 - Treat every configured Cursor candidate string as opaque. Do not normalize it
   or infer capability from its spelling.
-- For managed capped task-worker/fix dispatch, call the resolver with
-  `--provider cursor --role implementer --ceiling-tier
-<project-or-phase-tier> --candidate-model <opaque-model> --json`.
+- For managed capped task-worker/fix dispatch, call
+  `oat project dispatch-ceiling resolve --provider cursor --role implementer --ceiling-tier <project-or-phase-tier> --candidate-model <opaque-model> --report-scope <task-id> --report-action implementation --json`
+  for implementation. For a bounded fix, call
+  `oat project dispatch-ceiling resolve --provider cursor --role implementer --ceiling-tier <project-or-phase-tier> --candidate-model <opaque-model> --report-scope <task-id> --report-action fix --json`.
 - Require `providers.cursor.dispatchArgs.model` and pass that exact byte-for-byte
   string as the actual Cursor invocation model. If the host cannot apply it,
   fail closed.
@@ -460,19 +487,17 @@ Payload-first invariant:
 - Build the actual host dispatch argument map before logging.
 - Do not emit `selected:<value>` unless the host invocation contains the corresponding role/model selection.
 - Derive `Dispatch target` and `Effort axis` / `Model axis` from the payload.
-- After the payload is built, append a formal dispatch stamp to Dispatch Notes
-  for every implementation, fix, and review dispatch. Use the p01 grammar
-  exactly:
+- After the payload is built, append the compatibility stamp returned from
+  `formatDispatchStamp(dispatchReport)` to Dispatch Notes for every
+  implementation, fix, and review dispatch. The derived line retains the p01
+  grammar exactly:
   `Dispatch: scope=<phase-or-task> action=<implementation|fix|review> role=<implementer|fix|reviewer> producer=<slug|unknown> provenance=<declared|observed|inferred|unknown> model_axis=<axis> effort_axis=<axis> dispatch_policy=<policy|unknown> dispatch_ceiling=<value|none> target=<target|unknown>`.
-  Derive `producer` and `provenance` from the resolver payload and actual host
-  arguments. Only concrete model arguments, including same-harness route model
-  args for model-arg providers, declare producer identity. Codex materialized
-  model+effort variants declare `model_axis=selected:<model>` and
-  `effort_axis=selected:<effort>` from resolver output, but keep
-  `producer=unknown provenance=unknown` unless an observed/inferred model
-  identity is available. Base/unpinned or deferred cross-harness paths are also
-  `producer=unknown provenance=unknown` unless an observed/inferred identity is
-  available. Do not write prose-only or legacy comma-separated stamp forms.
+  Populate the report from the completed resolver and actual host arguments.
+  Only independently observed or otherwise supported runtime evidence may
+  populate runtime producer identity. Codex materialized model+effort variants
+  retain selected model/effort controls while keeping runtime identity
+  not-reported unless evidence exists. Do not write prose-only, hand-built, or
+  legacy comma-separated stamp forms.
 
 Human-facing dispatch display rules:
 
@@ -1067,6 +1092,8 @@ For each task in dependency order, the coordinator must:
      --role implementer \
      --ceiling-tier <project-or-phase-named-tier> \
      --candidate-model <exact-model> \
+     --report-scope <task-id> \
+     --report-action implementation \
      --project-path "$PROJECT_PATH" \
      --json
    ```

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

@@ -1,6 +1,6 @@
 ---
 name: oat-project-review-provide
-version: 1.3.12
+version: 1.3.13
 description: Use when the user explicitly asks to review an OAT project — e.g. "review project", "review the project", "run project review", or confirms a previously offered review. Do NOT auto-invoke on completed work alone. Resolves a project review scope and offers before running.
 disable-model-invocation: false
 user-invocable: true
@@ -523,9 +523,25 @@ Before capability-tier selection, resolve the same reviewer contract used by
 plan artifact review and implementation phase/final review:
 
 ```bash
-oat project dispatch-ceiling resolve --provider "$ACTIVE_PROVIDER" --role reviewer --preflight --json
+oat project dispatch-ceiling resolve --provider "$ACTIVE_PROVIDER" --role reviewer --preflight --report-scope "$SCOPE_TOKEN" --report-action review --json
 ```
 
+Require `dispatchReport.schemaVersion: 1`. Render/consume the resolver's
+versioned report using `formatDispatchReport(dispatchReport)` semantics, and
+derive the formal compatibility line only with
+`formatDispatchStamp(dispatchReport)` / `toDispatchStampRecord(dispatchReport)`.
+Include that derived line in the review dispatch audit metadata; do not
+hand-assemble `Dispatch:` fields from a role name or model string.
+
+The exact managed provider target still comes from
+`providers.<provider>.dispatchArgs` plus
+`providers.<provider>.selection.target`, and the actual reviewer invocation
+must retain it byte-for-byte. The report is an audit/rendering surface, not a
+selection fallback. Configured invocation (including gate-owned immutable
+metadata), work-producer diversity, and independently observed reviewer runtime identity are distinct. Do not promote producer stamps, configured defaults, or
+reviewer self-report into `dispatchReport.runtimeIdentity`; leave it
+`not-reported` unless an independent observation exists.
+
 The reviewer resolver selects the final candidate of the configured review
 ceiling. Do not supply ephemeral implementer candidate requests for artifact,
 phase, project, or final review. A lower candidate is allowed only when a

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

@@ -1,6 +1,6 @@
 ---
 name: oat-project-review-provide-remote
-version: 1.0.2
+version: 1.0.3
 description: Use when reviewing a GitHub PR opened on another machine for an active OAT project and posting findings back as a single PR review. Resolves the project from the PR diff, reads project artifacts for mode-aware review, and posts via gh api.
 disable-model-invocation: true
 user-invocable: true
@@ -211,6 +211,33 @@ Guard outcomes:
 
 Mode-aware review against the project artifacts + the `oat-reviewer` checklist + severity model. Scope to the narrowing range when one was chosen; otherwise the full PR diff. Assign finding IDs per severity bucket (`C1`, `I1`, `M1`, `m1`), stable within the dispatch.
 
+**Step 5.0: Resolve and report the exact reviewer target.** Before capability
+probing, run:
+
+```bash
+oat project dispatch-ceiling resolve --provider "$ACTIVE_PROVIDER" --role reviewer --preflight --project-path "$PROJECT_PATH" --report-scope "$SCOPE_TOKEN" --report-action review --json
+```
+
+Require `dispatchReport.schemaVersion: 1`. Render/consume its versioned human
+block with `formatDispatchReport(dispatchReport)` semantics and derive the
+formal audit `Dispatch:` line only through
+`formatDispatchStamp(dispatchReport)` / `toDispatchStampRecord(dispatchReport)`.
+Never hand-build a parallel stamp schema.
+
+Retain the exact managed provider payload from
+`providers.<provider>.dispatchArgs` and
+`providers.<provider>.selection.target` in the actual Tier 1/2/3 invocation;
+the report does not authorize substitution or lowering. Configured gate
+invocation, work-producer diversity, and independently observed reviewer
+`dispatchReport.runtimeIdentity` remain separate. Do not treat PR markers, implementation
+producer stamps, configured defaults, or reviewer self-report as runtime
+confirmation. Leave report runtime identity not-reported unless independently
+observed.
+
+This resolver command is independent of lifecycle gates. Reusable `oat gate
+review` commands must remain provider-neutral and must not contain or add a
+provider/model `--target` argument.
+
 **Step 5a: Probe subagent availability** (mirrors `oat-project-review-provide` Step 6a):
 
 ```

package/dist/commands/config/index.d.ts

@@ -3,6 +3,7 @@ import { type PromptContext } from '../shared/shared.prompts.js';
 import { type OatConfig, type OatLocalConfig, type UserConfig } from '../../config/oat-config.js';
 import { type ResolvedConfig } from '../../config/resolve.js';
 import { type MatrixCellAvailabilityResponse, type ValidateMatrixCellOptions } from '../../providers/identity/availability.js';
+import { createDispatchValidationPassContext, validateDispatchMatrixRefs } from '../../providers/identity/dispatch-validation.js';
 import { Command } from 'commander';
 interface ConfigCommandDependencies {
     buildCommandContext: (options: Parameters<typeof buildCommandContext>[0]) => CommandContext;
@@ -19,6 +20,8 @@ interface ConfigCommandDependencies {
     readFile: (path: string) => Promise<string>;
     confirmAction: (message: string, ctx: PromptContext) => Promise<boolean>;
     validateMatrixCell: (provider: string, value: string, options: ValidateMatrixCellOptions) => Promise<MatrixCellAvailabilityResponse>;
+    createDispatchValidationPassContext: typeof createDispatchValidationPassContext;
+    validateDispatchMatrixRefs: typeof validateDispatchMatrixRefs;
     processEnv: NodeJS.ProcessEnv;
 }
 export declare function createConfigCommand(overrides?: Partial<ConfigCommandDependencies>): Command;

package/dist/commands/config/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/commands/config/index.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,mBAAmB,EAAE,KAAK,cAAc,EAAE,MAAM,sBAAsB,CAAC;AAEhF,OAAO,EAEL,KAAK,aAAa,EACnB,MAAM,iCAAiC,CAAC;AAQzC,OAAO,EAML,KAAK,SAAS,EACd,KAAK,cAAc,EAGnB,KAAK,UAAU,EAgBhB,MAAM,oBAAoB,CAAC;AAC5B,OAAO,EAEL,KAAK,cAAc,EAEpB,MAAM,iBAAiB,CAAC;AAGzB,OAAO,EAGL,KAAK,8BAA8B,EACnC,KAAK,yBAAyB,EAC/B,MAAM,kCAAkC,CAAC;AAC1C,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAkFpC,UAAU,yBAAyB;IACjC,mBAAmB,EAAE,CACnB,OAAO,EAAE,UAAU,CAAC,OAAO,mBAAmB,CAAC,CAAC,CAAC,CAAC,KAC/C,cAAc,CAAC;IACpB,kBAAkB,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,OAAO,CAAC,MAAM,CAAC,CAAC;IACrD,aAAa,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,OAAO,CAAC,SAAS,CAAC,CAAC;IACxD,cAAc,EAAE,CAAC,QAAQ,EAAE,MAAM,EAAE,MAAM,EAAE,SAAS,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;IACvE,kBAAkB,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,OAAO,CAAC,cAAc,CAAC,CAAC;IAClE,mBAAmB,EAAE,CACnB,QAAQ,EAAE,MAAM,EAChB,MAAM,EAAE,cAAc,KACnB,OAAO,CAAC,IAAI,CAAC,CAAC;IACnB,cAAc,EAAE,CAAC,aAAa,EAAE,MAAM,KAAK,OAAO,CAAC,UAAU,CAAC,CAAC;IAC/D,eAAe,EAAE,CAAC,aAAa,EAAE,MAAM,EAAE,MAAM,EAAE,UAAU,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;IAC9E,mBAAmB,EAAE,CACnB,QAAQ,EAAE,MAAM,EAChB,GAAG,EAAE,MAAM,CAAC,UAAU,KACnB,OAAO,CAAC,MAAM,CAAC,CAAC;IACrB,sBAAsB,EAAE,CACtB,QAAQ,EAAE,MAAM,EAChB,aAAa,EAAE,MAAM,EACrB,GAAG,EAAE,MAAM,CAAC,UAAU,KACnB,OAAO,CAAC,cAAc,CAAC,CAAC;IAC7B,iBAAiB,EAAE,MAAM,OAAO,CAAC,MAAM,CAAC,CAAC;IACzC,QAAQ,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,OAAO,CAAC,MAAM,CAAC,CAAC;IAC5C,aAAa,EAAE,CAAC,OAAO,EAAE,MAAM,EAAE,GAAG,EAAE,aAAa,KAAK,OAAO,CAAC,OAAO,CAAC,CAAC;IACzE,kBAAkB,EAAE,CAClB,QAAQ,EAAE,MAAM,EAChB,KAAK,EAAE,MAAM,EACb,OAAO,EAAE,yBAAyB,KAC/B,OAAO,CAAC,8BAA8B,CAAC,CAAC;IAC7C,UAAU,EAAE,MAAM,CAAC,UAAU,CAAC;CAC/B;AA45DD,wBAAgB,mBAAmB,CACjC,SAAS,GAAE,OAAO,CAAC,yBAAyB,CAAM,GACjD,OAAO,CAsKT"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/commands/config/index.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,mBAAmB,EAAE,KAAK,cAAc,EAAE,MAAM,sBAAsB,CAAC;AAEhF,OAAO,EAEL,KAAK,aAAa,EACnB,MAAM,iCAAiC,CAAC;AAezC,OAAO,EAGL,KAAK,SAAS,EACd,KAAK,cAAc,EAGnB,KAAK,UAAU,EAahB,MAAM,oBAAoB,CAAC;AAC5B,OAAO,EAEL,KAAK,cAAc,EAEpB,MAAM,iBAAiB,CAAC;AAGzB,OAAO,EAGL,KAAK,8BAA8B,EACnC,KAAK,yBAAyB,EAC/B,MAAM,kCAAkC,CAAC;AAC1C,OAAO,EACL,mCAAmC,EACnC,0BAA0B,EAC3B,MAAM,yCAAyC,CAAC;AACjD,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAkFpC,UAAU,yBAAyB;IACjC,mBAAmB,EAAE,CACnB,OAAO,EAAE,UAAU,CAAC,OAAO,mBAAmB,CAAC,CAAC,CAAC,CAAC,KAC/C,cAAc,CAAC;IACpB,kBAAkB,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,OAAO,CAAC,MAAM,CAAC,CAAC;IACrD,aAAa,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,OAAO,CAAC,SAAS,CAAC,CAAC;IACxD,cAAc,EAAE,CAAC,QAAQ,EAAE,MAAM,EAAE,MAAM,EAAE,SAAS,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;IACvE,kBAAkB,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,OAAO,CAAC,cAAc,CAAC,CAAC;IAClE,mBAAmB,EAAE,CACnB,QAAQ,EAAE,MAAM,EAChB,MAAM,EAAE,cAAc,KACnB,OAAO,CAAC,IAAI,CAAC,CAAC;IACnB,cAAc,EAAE,CAAC,aAAa,EAAE,MAAM,KAAK,OAAO,CAAC,UAAU,CAAC,CAAC;IAC/D,eAAe,EAAE,CAAC,aAAa,EAAE,MAAM,EAAE,MAAM,EAAE,UAAU,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;IAC9E,mBAAmB,EAAE,CACnB,QAAQ,EAAE,MAAM,EAChB,GAAG,EAAE,MAAM,CAAC,UAAU,KACnB,OAAO,CAAC,MAAM,CAAC,CAAC;IACrB,sBAAsB,EAAE,CACtB,QAAQ,EAAE,MAAM,EAChB,aAAa,EAAE,MAAM,EACrB,GAAG,EAAE,MAAM,CAAC,UAAU,KACnB,OAAO,CAAC,cAAc,CAAC,CAAC;IAC7B,iBAAiB,EAAE,MAAM,OAAO,CAAC,MAAM,CAAC,CAAC;IACzC,QAAQ,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,OAAO,CAAC,MAAM,CAAC,CAAC;IAC5C,aAAa,EAAE,CAAC,OAAO,EAAE,MAAM,EAAE,GAAG,EAAE,aAAa,KAAK,OAAO,CAAC,OAAO,CAAC,CAAC;IACzE,kBAAkB,EAAE,CAClB,QAAQ,EAAE,MAAM,EAChB,KAAK,EAAE,MAAM,EACb,OAAO,EAAE,yBAAyB,KAC/B,OAAO,CAAC,8BAA8B,CAAC,CAAC;IAC7C,mCAAmC,EAAE,OAAO,mCAAmC,CAAC;IAChF,0BAA0B,EAAE,OAAO,0BAA0B,CAAC;IAC9D,UAAU,EAAE,MAAM,CAAC,UAAU,CAAC;CAC/B;AAo0DD,wBAAgB,mBAAmB,CACjC,SAAS,GAAE,OAAO,CAAC,yBAAyB,CAAM,GACjD,OAAO,CAsKT"}