@agen-ai/acp-registry 0.4.0 → 0.4.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,7 +1,8 @@
1
1
  # @agen-ai/acp-registry
2
2
 
3
3
  Optional ACP catalog validation, search, immutable planning and verified installation for Node.js 22 or newer.
4
- The coordinated SDK version is `0.4.0`. The package is ESM, MIT licensed and side-effect-free on import.
4
+ The coordinated source SDK version is `0.4.1` and remains unpublished; the published
5
+ release is `0.4.0`. The package is ESM, MIT licensed and side-effect-free on import.
5
6
  The metadata graph depends only on `@agen-ai/validation` and exact `zod@4.4.3`. Explicit Node
6
7
  installation uses pinned tar, ZIP and bzip2 readers. Public contracts are plain TypeScript values
7
8
  and AgenAI validation issues, with no exposed Zod schemas or Agent Runtime dependency.
@@ -254,6 +255,32 @@ The provider launcher supplies no sandbox, account credentials or filesystem/net
254
255
  The registry is also usable without the provider package when another explicit process owner
255
256
  consumes the verified launch recipe.
256
257
 
258
+ The `0.4.1` session-interaction API extends the same dependency rule to decisions
259
+ outside a turn. Register the runtime handler before opening and retain the exact
260
+ installation reference while a decision is pending, after a local response receipt,
261
+ and through session close and callback/native cleanup. An `answered`, `expired`,
262
+ `session_closed` or uncertain terminal does not release the reference. An uncertain
263
+ choice must never be replayed as part of installation or process recovery.
264
+
265
+ The optional Node `grok-folder-trust-v1` mapping requires an explicitly supplied
266
+ `executionBoundary` before materialization. The registry verifies installation
267
+ identity and returns a launch recipe; it supplies no process containment or
268
+ session-interaction policy. Use the provider's
269
+ [execution ownership guidance](../provider-acp/README.md#reserved-execution-ownership)
270
+ and the maintained [Linux reference](../../examples/execution/linux/README.md)
271
+ when composing that selected profile. Its exact local native qualification does
272
+ not qualify all registry-installed agents or other platforms.
273
+
274
+ If registry construction fails before returning a registry, preserve the original
275
+ `AgentProviderRegistryError.cause`. A retained `NodeAcpExecutionCleanupError` there
276
+ keeps the startup cleanup callable; invoke its `retryCleanup()` and retain the
277
+ external host and installation reference until native shutdown and entered
278
+ callbacks have actually joined. For a failed session opening, retain the exact
279
+ `AgentProviderSessionCleanupError` associated with that input object; for a returned
280
+ session, retain its close owner. Releasing a reference or deleting the store cannot
281
+ repair incomplete provider cleanup, and serializing an error does not preserve
282
+ the callable owner.
283
+
257
284
  Installation and launch require the current OS/architecture to match the plan. The caller supplies
258
285
  an absent store directory under an existing owned parent, or reopens a valid owned store. Foreign
259
286
  and substituted roots fail closed. The library creates a private stage, verifies every retained file,
@@ -317,7 +344,7 @@ network confinement; execution of arbitrary install scripts is deliberately unsu
317
344
  4,096-byte paths, three download redirects, two-minute artifact/tool deadlines, 1 MiB combined tool
318
345
  output, 16 MiB receipts and 1,024 active references. Larger values remain bounded by package ceilings.
319
346
  Errors use `AcpInstallationError` with stable `code`; malformed plans retain registry validation issues.
320
- Registry and installation failures remain distinct from Agent Protocol V10 operational failures and
347
+ Registry and installation failures remain distinct from Agent Protocol V11 operational failures and
321
348
  provider retry observations. This package has no runtime dependency or policy for retrying an agent
322
349
  turn; retained installation integrity and process quiescence do not settle uncertain native execution.
323
350
 
@@ -212,7 +212,6 @@ class ArchiveRandomAccessReader extends RandomAccessReader {
212
212
  super();
213
213
  this.handle = handle;
214
214
  }
215
- handle;
216
215
  _readStreamForRange(start, end) {
217
216
  const handle = this.handle;
218
217
  return Readable.from((async function* () {
@@ -232,7 +231,6 @@ class TarBudget extends Transform {
232
231
  super();
233
232
  this.limit = limit;
234
233
  }
235
- limit;
236
234
  bytes = 0;
237
235
  tail = Buffer.alloc(0);
238
236
  _transform(chunk, _encoding, callback) {
@@ -9,7 +9,6 @@ class ArchiveSink {
9
9
  this.input = input;
10
10
  this.entries.set("", { path: "", kind: "directory", size: 0, mode: 448 });
11
11
  }
12
- input;
13
12
  entries = /* @__PURE__ */ new Map();
14
13
  explicitPaths = /* @__PURE__ */ new Set();
15
14
  casePaths = /* @__PURE__ */ new Map();
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@agen-ai/acp-registry",
3
- "version": "0.4.0",
3
+ "version": "0.4.1",
4
4
  "private": false,
5
5
  "description": "Bounded ACP registry metadata, immutable installation plans, and explicit Node operations.",
6
6
  "type": "module",
@@ -32,7 +32,7 @@
32
32
  "buffer-crc32": "1.0.0",
33
33
  "tar-stream": "3.2.2",
34
34
  "yauzl": "3.4.0",
35
- "@agen-ai/validation": "^0.4.0"
35
+ "@agen-ai/validation": "^0.4.1"
36
36
  },
37
37
  "devDependencies": {
38
38
  "tsup": "^8.5.0",