@open-agent-toolkit/cli 0.3.20 → 0.3.21

package/assets/bundle-metadata.json

@@ -1,4 +1,4 @@
 {
   "schemaVersion": 1,
-  "oatVersion": "0.3.20"
+  "oatVersion": "0.3.21"
 }

package/assets/public-package-versions.json

@@ -1,6 +1,6 @@
 {
-  "cli": "0.3.20",
-  "docs-config": "0.3.20",
-  "docs-theme": "0.3.20",
-  "docs-transforms": "0.3.20"
+  "cli": "0.3.21",
+  "docs-config": "0.3.21",
+  "docs-theme": "0.3.21",
+  "docs-transforms": "0.3.21"
 }

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.12
+  version: 1.2.13
 ---
 
 # Dispatching OAT Subagents

package/assets/skills/oat-dispatch-subagents/references/record-schema.md

@@ -283,6 +283,12 @@ so the loaded root is that home's `.agents`: expect `tier: loaded`,
 `canonicalPath: <user>/agents/<role>.md`. Another layout yields different but
 equally valid tier labels.
 
+Under a capped managed policy the reviewer targets the policy's cap cell
+(here `high`, so the Opus 5.5 high variant). In a repository whose policy caps at another tier the
+selected variant differs, and `dispatch record` rejects a `payload.variant`
+that is not the resolver's. Take `payload.variant` from the live resolution's
+`providers.claude.dispatchArgs.variant`, never from this example.
+
 ## Recon Wave
 
 ```yaml

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

@@ -7,7 +7,7 @@ disable-model-invocation: true
 user-invocable: true
 allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion, Task
 metadata:
-  version: 1.0.1
+  version: 1.0.2
 ---
 
 # Brief Project

package/assets/skills/oat-project-brief/references/brief-contract.md

@@ -631,6 +631,13 @@ the head the new `bound_revisions` binds for that member. A bound revision
 that disagrees with its member's `reviewed_head` is not fresh
 (`bound-revision-mismatch`).
 
+The unlock for those set-once fields, the delivery's own review-artifact set,
+is read only from the delivery's append-only Reviews rows, never from
+`integrated_review.artifact` or any other registry or brief field the judged
+commit can rewrite; bound revisions, member reviewed heads and the exit gate
+move only with that unlock. Negative controls for this rule run through the
+production scope builder and the built CLI, not a hand-assembled scope.
+
 The shared evaluator (`delivery/evidence.ts`) implements this rule for
 `delivery check`, `delivery refresh` and the closeout boundary. It accepts two
 deliberate leniencies:

package/package.json

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