@jigging/agent-acp 0.1.0-alpha.5 → 0.1.0-alpha.6

package/AGENTS.md

@@ -33,6 +33,8 @@ retains credential, process, and dispatch authority.
 - Jig consumers may select this declared dependency with `npm:@jigging/agent-acp`
   in a local Binding; the Binding still grants the exact native client.
   Contract-keyed project selection does not create that grant or choose a vendor.
+  The README teaches package-selected caller creation and offline contract import
+  from ordinary root/member installs; consumers do not name physical installer paths.
 - Reuse `@jigging/agent-method` for prompt preparation and result validation.
   Complete ACP dialogue and resource settlement are separate requirements.
 - Locally detected invalid ACP cancels the resource while preserving that

package/README.md

@@ -127,6 +127,30 @@ The example's client is a choice, not a Jig default; `codex`, `claude` and `pi`
 use the same grant interface. The operator configures the native installation, model and
 authentication described in [Choose an Agent](https://jig.md/guide/agents).
 
+To call this Agent from a new Flow, install the declared project dependency
+with `bun install`, then select its complete contract when creating the caller:
+
+```sh
+jig new worker --use agent=npm:@jigging/agent-acp
+```
+
+For an existing caller, create its `contracts/` parent and import the bundle:
+
+```sh
+mkdir -p flows/worker/contracts
+jig import-contract npm:@jigging/agent-acp flows/worker/contracts/agent
+```
+
+Declare `uses.agent.contract: './contracts/agent/FLOW.contract.json'` in that
+caller's metadata. Selection uses the nearest ordinary project or member-local
+installation, copies all referenced channel descriptors offline, and runs no
+package code. The copied contract belongs to the caller: an installation update
+does not replace it or grant new authority. An existing destination is refused;
+choose a new directory to inspect a changed contract before updating the caller.
+See the [conversation walkthrough](https://jig.md/guide/conversations) for a
+complete two-turn caller and the separate native turn grant. These authoring
+commands require the matching Jig source candidate until its alpha is published.
+
 ```sh
 jig review
 jig run binding:agent --input '{"instructions":"Explain one useful check."}' --receive events

package/dist/flow.js

@@ -1,9 +1,11 @@
 // ../agent-method/dist/errors.js
 class AgentMethodError extends Error {
   code;
-  constructor(code, message) {
+  details;
+  constructor(code, message, details) {
     super(message);
     this.code = code;
+    this.details = details;
     this.name = "AgentMethodError";
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jigging/agent-acp",
-  "version": "0.1.0-alpha.5",
+  "version": "0.1.0-alpha.6",
   "description": "An ordinary Agent Flow over a finite, host-authorized ACP resource",
   "license": "MPL-2.0",
   "repository": {
@@ -37,7 +37,7 @@
   ],
   "devDependencies": {
     "@jigging/flow": "0.1.0-alpha.13",
-    "@jigging/agent-method": "0.1.0-alpha.5",
+    "@jigging/agent-method": "0.1.0-alpha.6",
     "@types/node": "24.13.3",
     "typescript": "7.0.2"
   }