@directive-run/claude-plugin 1.19.1 → 1.19.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@directive-run/claude-plugin",
-  "version": "1.19.1",
+  "version": "1.19.2",
   "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.19.1"
+    "@directive-run/knowledge": "1.19.2"
   },
   "scripts": {
     "build": "tsx scripts/build-skills.ts && tsup",

package/skills/building-ai-agents/ai-sources.md

@@ -189,11 +189,13 @@ publish closure (if any) receives lifecycle events.
 > holder from two places (e.g., a Worker that mounts one Directive
 > system per tenant DO), a module-level `let publishRef` would be
 > SHARED — the second tenant's `attach` would silently overwrite the
-> first tenant's pipe. **Always declare the holder + adapter inside a
-> factory function** so each call yields an isolated closure pair.
-> The recipe below uses `makeOrchestrator(adapter)` for exactly this
-> reason; if you create the adapter outside the factory, pass it in
-> per call too.
+> first tenant's pipe. **Always construct BOTH the adapter AND the
+> module inside the same factory function** so the adapter's
+> `events` callbacks close over the same factory-local `publishRef`
+> as the source's `attach`. Sharing an adapter across factory calls
+> re-introduces the cross-contamination because the adapter's
+> `events.onConnect` was bound at construction time to whichever
+> factory's `publishRef` was in scope first.
 
 ```ts
 import { createSystem, createModule, t } from "@directive-run/core";