@directive-run/claude-plugin 1.21.0 → 1.22.0

package/README.md

@@ -6,14 +6,14 @@ The package has two install paths: **Claude Code's plugin marketplace** for end
 
 ## Install for Claude Code (canonical)
 
-Two steps in a Claude Code session — first register the marketplace, then install the plugin:
+Two steps in a Claude Code session – first register the marketplace, then install the plugin:
 
 ```
 /plugin marketplace add directive-run/directive
 /plugin install directive@directive-plugins
 ```
 
-After install, verify the plugin is active with `/plugins` — you should see `directive` in the list.
+After install, verify the plugin is active with `/plugins` – you should see `directive` in the list.
 
 ## Install for tool authors (npm)
 
@@ -36,7 +36,7 @@ import {
 const names = listSkills();
 // → ["building-ai-agents", "building-ai-orchestrators", ...]
 
-// One skill — manifest + supporting files
+// One skill – manifest + supporting files
 const skill = getSkill("building-ai-orchestrators");
 skill?.manifest;            // SKILL.md (with YAML frontmatter)
 skill?.files.get("examples"); // examples.md contents
@@ -48,7 +48,7 @@ const all = getAllSkills(); // Map<string, Skill>
 const ex = getSkillFile("building-ai-orchestrators", "examples");
 ```
 
-The npm install path is not a replacement for the Claude Code plugin install — it does not register the skills with Claude Code itself. It only exposes the same `skills/` directory as a typed module so other tools can read it.
+The npm install path is not a replacement for the Claude Code plugin install – it does not register the skills with Claude Code itself. It only exposes the same `skills/` directory as a typed module so other tools can read it.
 
 ## What happens after install
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@directive-run/claude-plugin",
-  "version": "1.21.0",
+  "version": "1.22.0",
   "description": "Claude Code plugin for Directive — 12 skills covering modules, constraints, resolvers, derivations, AI orchestration, and adapters. Installable via Claude Code's plugin marketplace or consumable programmatically as an npm package.",
   "license": "(MIT OR Apache-2.0)",
   "author": "Jason Comes",
@@ -52,7 +52,7 @@
     "tsx": "^4.19.2",
     "typescript": "^5.7.2",
     "vitest": "^3.0.0",
-    "@directive-run/knowledge": "1.21.0"
+    "@directive-run/knowledge": "1.22.0"
   },
   "scripts": {
     "build": "tsx scripts/build-skills.ts && tsup",

package/skills/getting-started-with-directive/choosing-primitives.md

@@ -156,7 +156,8 @@ seven pieces of work, zero `useEffect` hooks.
 - [`sources.md`](./sources.md) — the source primitive's full lifecycle
   and recipes.
 - [`constraints.md`](./constraints.md) — `when` predicates, requirement
-  shapes, and the `bind` / `owns` field-scoped CAS contract.
+  shapes, and the `abortOn` field-scoped CAS contract (v1; `bind:` is a
+  v2 reservation – see RFC 0003 Future Work).
 - [`resolvers.md`](./resolvers.md) — retry config, batch semantics, and
   the `ctx.set` write contract.
 - [`anti-patterns.md`](./anti-patterns.md) — the things to avoid that

package/skills/getting-started-with-directive/sitemap.md

@@ -63,7 +63,7 @@ Website: https://directive.run
 ### Advanced Patterns
 - [Overview](https://directive.run/docs/advanced/overview)
 - [Data-form Definitions](https://directive.run/docs/data-triggers)
-- [Resolver Binding (owns)](https://directive.run/docs/resolver-binding)
+- [Resolver Binding](https://directive.run/docs/resolver-binding)
 - [Multi-Module](https://directive.run/docs/advanced/multi-module)
 - [Runtime Dynamics](https://directive.run/docs/advanced/runtime)
 - [History & Snapshots](https://directive.run/docs/advanced/history)

package/skills/writing-directive-constraints/resolvers.md

@@ -1,6 +1,6 @@
 # Resolvers
 
-> Covers `@directive-run/core` — resolver definition: retry policies, batching, cancellation, custom dedup keys, `owns` binding.
+> Covers `@directive-run/core` — resolver definition: retry policies, batching, cancellation, custom dedup keys, `abortOn` binding.
 
 Resolvers fulfill requirements emitted by constraints. They are the supply side of the constraint-resolver pattern. Resolvers handle async work and mutate state through `context.facts`.
 
@@ -205,6 +205,31 @@ resolvers: {
 
 Failed items from `resolveBatchWithResults` can be individually retried if a retry policy is configured.
 
+## `abortOn` binding (constraint-side)
+
+Declared on the *constraint*, not the resolver. Lists facts whose values
+must remain unchanged between dispatch and the resolver's writes; if any
+of them changes mid-flight, the resolver's writes are dropped and its
+signal is aborted.
+
+```typescript
+constraints: {
+  finalizeKyc: {
+    when: (f) => f.kyc.status === "pending",
+    require: { type: "FINALIZE_KYC" },
+    abortOn: ["kyc.status"], // abort if `kyc.status` changes mid-flight
+  },
+},
+```
+
+`abortOn:` does **not** lock or gate other writers. It only protects this
+resolver from clobbering with stale data when its tail write attempts a
+value the world has since moved past. See
+[`/docs/resolver-binding`](https://directive.run/docs/resolver-binding)
+for the full lifecycle, ABA caveats, and the audit event
+(`resolver.write.rejected { reason: "clobbered" }`) that fires on a
+dropped write.
+
 ## Timeout
 
 ```typescript