agents-can-communicate 0.7.1 → 0.8.1

package/docs/TROUBLESHOOTING.md

@@ -154,31 +154,35 @@ or a connected MCP server does not by itself establish automatic delivery. `life
 manual` can also mean the current version has no certified session-end hook; it does not
 prove that no hooks ran.
 
-For Claude Code, open a fresh interactive zsh after installation so its launcher
-is on PATH. Check Claude's **Channels startup notice for ACC**, and accept the
-development-channel warning when it appears. A successful bootstrap cache means the
-executable passed ACC's compatibility probe. `/mcp` showing `connected` and two tools
-means the MCP server connected. Even `runtime: active` in ACC's doctor JSON describes
-the local transport; none of these proves that Claude enabled inbound channel messages.
-
-If Claude says `--dangerously-load-development-channels ignored` or `Channels are not
-currently available`, it has not enabled that delivery path. On a fresh 2.1.266 test
-profile, the first launch showed those messages and the next launch showed the development
-warning; restarting once can recheck availability, but is not a guaranteed fix. If it
-remains unavailable, follow Claude's notice. Organization policy can also block Channels;
-an administrator must enable them where required. ACC does not override that policy.
-See [Claude's Channels documentation](https://code.claude.com/docs/en/channels).
-
-If `deliveryBindings` is empty, ACC has not bound a local transport either. Read the
+For Claude Code, use version 2.1.282 or newer on Apple Silicon macOS, and start it with
+your ordinary command. Each Claude Code session opens its own inbox socket. ACC reads the
+socket path from `CLAUDE_CODE_MESSAGING_SOCKET` in the hook environment. ACC then checks that
+path against Claude Code's session registry `<config>/sessions/<pid>.json`, where
+`<config>` is `CLAUDE_CONFIG_DIR` or `~/.claude`. The pid and the socket must match for the
+binding, and the session id must match too before each wake. Each turn hook binds the
+session again, so the next ordinary prompt retries a failed binding.
+
+- Claude Code 2.1.224 and later open the inbox, but ACC's captured minimum is 2.1.282. An
+  older version reports `below_minimum_version` and keeps next-turn delivery.
+- On native Windows, Claude Code serves its inbox on a named pipe that requires an auth
+  line. ACC has no capture of that inbox, so Windows keeps next-turn delivery.
+- Linux is uncaptured for live delivery. A Linux session keeps next-turn delivery.
+- A wake that reached the session can still wait for your approval. See
+  [the next section](#a-claude-code-session-holds-or-drops-acc-wakes).
+
+If `deliveryBindings` is empty, ACC has not bound a local transport. Read the
 per-session lines in `acc doctor`, or `nativeDelivery.sessions[].lastAttempt` in JSON:
 
-- An absent launch policy means that hook did not receive delivery consent, even if an
-  earlier bootstrap probe succeeded. For Claude, open a new terminal and client through
-  the installed launcher.
+- An absent or `off` policy means the installation record has no live-delivery consent
+  for that client. Run `acc install --adapter <adapter> --delivery actionable` (or `all`).
 - `client_process_unknown` means ACC could not identify the client process. A new client
   session repeats that lookup.
-- `handshake_failed` or `handshake_timeout` means the session could not bind the local
-  channel. Check the client's integration/channel setup; the next ordinary turn retries.
+- For Claude Code, `native_endpoint_unavailable` means the hook environment had no
+  `CLAUDE_CODE_MESSAGING_SOCKET`, or the socket failed ACC's safety checks.
+  `native_session_unavailable` means the session registry is missing or names another
+  session or socket.
+- `handshake_failed` or `handshake_timeout` means the session could not bind its local
+  transport. Check the client's integration. The next ordinary turn retries.
 - No attempt observed can mean no native hook ran, an older runtime wrote the owner, or
   diagnostic persistence failed. Check hook activation and the runtime versions in doctor.
 
@@ -190,6 +194,37 @@ Closing a Codex terminal can leave its daemon thread loaded and eligible. Use
 Already accepted queue entries remain with the vendor. Actual thread archive
 requires Codex's confirmation and produces `SessionEnd`.
 
+## A Claude Code session holds or drops ACC wakes
+
+Claude Code applies its own inbound controls to each ACC wake. These controls stay yours.
+ACC never attests a permission mode, never reads the session's messaging token or key file,
+and sends no auth line.
+
+- A session in a prompting mode (`default`, `auto`, `acceptEdits` or `dontAsk`) takes each
+  wake.
+- A session in `bypassPermissions` mode holds each wake for your approval. To let such a
+  session take wakes without approval, set Claude Code's `crossSessionInbound` setting to
+  `accept`.
+- A session with `crossSessionInbound` set to `refuse` drops each wake. ACC then sends
+  none: the message stays `queued` with `delivery_disabled` and arrives with the next turn.
+
+ACC reads the same inputs Claude Code reads: the hook's permission mode; before the first
+prompt, whose hook carries none, the `--permission-mode` or `--dangerously-skip-permissions`
+flag the session was started with, then `permissions.defaultMode`; and `crossSessionInbound`
+from managed, local, project and user settings in that order. A held wake is still sent, because Claude
+Code's approval dialog tells you a message is waiting, and the sender reads
+`sent a wake to <participant> via claude-inbox, which its session holds for approval`.
+
+The product re-run on 2.1.283 observed both the prompting case and a `bypassPermissions`
+session holding the wake. When live delivery is on and your user or managed settings do not
+say `accept`, `acc doctor` prints a `Claude Code inbound:` line naming the setting and the
+file.
+
+In every case the message stays durable. The receipt stays `queued` until the session's
+next-turn hook shows the body. The message arrives with the session's next turn, and
+`acc inbox` shows it at any time. The sender's `acc message` output still reports
+`woke <participant> via claude-inbox`, because the wake reached the inbox.
+
 ## Codex plugin is listed but inactive
 
 Open `/plugins` in Codex and check ACC is enabled. Open `/hooks`, review each ACC hook,
@@ -205,8 +240,8 @@ local socket permissions as well; a writable state directory alone is insufficie
 ## Gemini does not guard a write
 
 Default and `plan` modes expose no write tool to the model. `auto_edit` exposes edit tools;
-shell availability depends on approval mode. Only Gemini CLI 0.57.0 on `darwin-arm64` has
-package-shipped delivery certification; other versions still use inbox.
+shell availability depends on approval mode. Gemini CLI next-turn delivery is certified from
+0.57.0 onward, on every platform; an older client still uses inbox.
 
 From 0.55 onwards there is a quieter cause with the same symptom: an untrusted folder. The
 client prints `Approval mode overridden to "default" because the current folder is not
@@ -333,7 +368,7 @@ reported and retained. Remove those leftovers manually if desired.
 Runtime state is outside the repository by design. `ACC_DATA_HOME` can relocate it, but ACC
 refuses a path inside any workspace root. Relocate the whole data directory; a symlink for
 that directory is supported. Install rejects a symlink that moves only the internal
-`acc/runtime` tree, because runtime admission and the bootstrap cache need the same data home.
+`acc/runtime` tree, because the runtime launchers and their leases need the same data home.
 
 Next: [Getting started](GETTING_STARTED.md) · [Capabilities](CAPABILITIES.md) ·
 [Configuration](CONFIGURATION.md)
@@ -355,10 +390,11 @@ unrelated holds still require lifecycle cleanup or confirmed process exit; safet
 do not expire merely by elapsed time. See
 [maintenance and recovery](UPGRADING.md#confirmed-client-service-maintenance).
 
-If ACC 0.5.3 or 0.5.4 reports `acc-claude-channel; contract unknown` after an earlier
-0.4.x upgrade, its active pointer may have lost the contract field. This can affect newly
-opened Channels too. A pending old updater retries its downloaded release without looking
-for a newer fix. Install the current global CLI, then use that CLI to complete the update:
+If ACC 0.5.3 or 0.5.4 reports a Claude Code Channel process with `contract unknown` after
+an earlier 0.4.x upgrade, its active pointer may have lost the contract field. This can
+affect Channel processes opened after that upgrade too. A pending old updater retries its
+downloaded release without looking for a newer fix. Install the current global CLI, then use
+that CLI to complete the update:
 
 ```bash
 npm install -g agents-can-communicate@latest
@@ -366,9 +402,10 @@ acc update
 acc doctor
 ```
 
-The new reader can activate a compatible release while those Channels remain open.
+The new reader can activate a compatible release while those processes remain open.
 It still waits for different contracts, unknown native bindings, or generation files it
 cannot verify. See [legacy contract recovery](UPGRADING.md#recover-missing-runtime-contracts).
+Current releases retire the Channel path. See [upgrading from 0.7.x](UPGRADING.md#from-07x).
 
 Use `acc update` to retry a failed download or finish an interrupted integration refresh.
 A download failure keeps the working version. A partial integration refresh blocks

package/docs/UPGRADING.md

@@ -1,11 +1,52 @@
 # Upgrading to 0.5.0
 
+## From 0.7.x
+
+Claude Code live delivery wakes each session through the inbox socket that Claude Code opens
+for every session. The research-preview Channels path of 0.7.x is retired. Update as usual:
+
+```bash
+acc update
+acc version
+acc doctor
+```
+
+`acc update` and `acc install` retire these 0.7.x parts automatically:
+
+- the `claude` shim that 0.7.x put early on `PATH`, and its PATH block in `~/.zshrc`
+- the Channel entry `acc-channel` in the plugin `.mcp.json`, from every kept plugin copy
+- the `acc-bootstrap` and `acc-claude-channel` launchers
+- the bootstrap cache
+
+The shim and the `~/.zshrc` block are hash-checked. An edited shim or block is kept, and
+the command reports it. Remove a kept one by hand when you no longer need it. An old shim
+that is still on `PATH` launches the plain `claude` command, without
+`--dangerously-load-development-channels`.
+
+Live-delivery consent comes only from the installation record, and upgrading keeps the
+recorded policy. ACC ignores `ACC_NATIVE_DELIVERY_POLICY`, `ACC_BYPASS` and
+`ACC_BOOTSTRAP_DEBUG`. For Claude Code, the consent question now says that a session in
+`bypassPermissions` mode asks before each ACC wake.
+
+A Claude Code session that started through the old shim keeps its Channel until it exits.
+Its next turn binds the inbox. Start new sessions with your ordinary `claude` command.
+
+The Claude Code live-delivery minimum is now 2.1.282 on Apple Silicon macOS. With an older
+Claude Code, live delivery stays off and the recorded policy is kept. Update Claude Code and
+start a new session: the recorded policy applies to it, with nothing to install again.
+`acc doctor` reports the state. Native Windows keeps next-turn delivery.
+
+This release adds no new store event type or field, so a store it writes stays readable by
+0.7.x. The Channel captures remain as history in
+`packages/adapter-claude-code/COMPATIBILITY.md`.
+
 ## Recover missing runtime contracts
 
 ACC 0.5.5 fixes an upgrade defect that can leave 0.5.3 or 0.5.4 waiting for
 `acc-claude-channel` processes with `contract unknown`. The 0.4.x updater can activate
-a newer generation without copying its store contract into the active pointer. Channels
-started afterward copy that incomplete pointer even though their runtime declares a contract.
+a newer generation without copying its store contract into the active pointer. Claude Code
+Channel processes started afterward copy that incomplete pointer even though their runtime
+declares a contract.
 
 For an installation already waiting on an older pending release, run:
 
@@ -21,8 +62,8 @@ needed because the older updater retries its pending release before checking npm
 version. If a version pin selects an older release, clear it or select 0.5.5 first.
 
 The reader verifies the referenced generation's package identity, complete contents and
-file modes before recovering a missing contract. Compatible Channels can keep running on
-their original generation during activation. Explicit differing contracts and unknown
+file modes before recovering a missing contract. Compatible Channel processes can keep
+running on their original generation during activation. Explicit differing contracts and unknown
 native bindings still block. A generation without a contract, missing files, or changed
 contents remains unknown. ACC does not terminate these processes or edit their lease records.
 
@@ -51,15 +92,15 @@ policy is default or contains only ACC's legacy state root. Custom policies are
 and reported as unverified. See [outgoing permissions](CONFIGURATION.md#codex-outgoing-permissions).
 If doctor names a missing local service, follow its prerequisite or explicit install action
 before opening the new session. A supported explicit install can prepare the service. It
-does not make a session-bound channel ready.
+does not make a session-bound transport ready.
 
 Run `acc doctor` in the project after the new clients have started (or submitted a normal
-turn). Its per-session lines now explain missing launch consent, an unidentified client
+turn). Its per-session lines now explain missing consent, an unidentified client
 process and a failed or timed-out handshake. `nativeDelivery.sessions[].lastAttempt` in
 `acc doctor --json` provides the same closed metadata and timestamp. Existing owners may
 have no attempt record until a new hook runs; missing metadata does not prove hooks are
-disabled. A previous successful handshake and a connected MCP server do not prove that
-Claude admitted inbound Channels messages. See [delivery troubleshooting](TROUBLESHOOTING.md#i-enabled-live-delivery-but-got-fallback).
+disabled. A previous successful handshake does not prove that the session is reachable
+now. See [delivery troubleshooting](TROUBLESHOOTING.md#i-enabled-live-delivery-but-got-fallback).
 
 Upgrading preserves delivery consent. If doctor reports native delivery off and you want
 automatic peer requests, use `acc install --adapter codex --delivery actionable` (or the

package/docs/WHY_ACC.md

@@ -53,9 +53,11 @@ coordinate across machines.
 ACC also does not merge model memory, read raw conversations, guarantee agent choices,
 approve tools, operate CI,
 or make guarded claims immune to unrelated local processes. Experimental live delivery is
-available through Claude Code Channel and Codex LocalDaemon on supported versions and
-platforms, behind recipient opt-in and with possible token spend. Neither interrupts a
-turn in progress; messages wait for it to finish. See [Capabilities](CAPABILITIES.md).
+available through the Claude Code inbox wake and Codex LocalDaemon on supported versions and
+platforms, behind recipient opt-in and with possible token spend. Both work inside the
+session you opened with your ordinary command, and Claude Code needs no launcher shim.
+Neither interrupts a turn in progress. A busy Claude Code session takes the message between
+two tool calls, and Codex waits for the turn to finish. See [Capabilities](CAPABILITIES.md).
 
 If the sessions should remain yours and simply stop working in isolation, that is the
 product ACC is designed to be.

package/node_modules/@agents-can-communicate/adapter-antigravity/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agents-can-communicate/adapter-antigravity",
-  "version": "0.7.1",
+  "version": "0.8.1",
   "private": true,
   "type": "module",
   "exports": {

package/node_modules/@agents-can-communicate/adapter-antigravity/plugin/plugin.json

@@ -1,5 +1,5 @@
 {
   "name": "acc",
-  "version": "0.7.1",
+  "version": "0.8.1",
   "description": "Coordinate this Antigravity CLI session with other AI agent sessions working in the same workspace."
 }

package/node_modules/@agents-can-communicate/adapter-antigravity/src/adapter.mjs

@@ -76,9 +76,8 @@ export function createAntigravityAdapter() {
     // no retireNativeSession here: the hook runner retires and re-publishes the
     // binding on every turn, and must not take the relay with it.
     nativeDelivery: {
-      minimumByPlatform: { "darwin-arm64": ANTIGRAVITY_CLI_VERSION },
-      anchors: [{ platform: "darwin-arm64", version: ANTIGRAVITY_CLI_VERSION,
-        protocolContract: PROTOCOL_CONTRACT }],
+      minimum: ANTIGRAVITY_CLI_VERSION,
+      anchors: [{ version: ANTIGRAVITY_CLI_VERSION, protocolContract: PROTOCOL_CONTRACT }],
       knownBad: [], activationKinds: ["native-config"], policySource: "installation-record",
     },
     probeNativeDelivery, planNativeActivation, bindNativeSession, refreshNativeSession,

package/node_modules/@agents-can-communicate/adapter-claude-code/certification.json

@@ -142,85 +142,26 @@
     },
     {
       "client": "claude-code",
-      "version": "2.1.258",
+      "version": "2.1.282",
       "platform": "darwin-arm64",
-      "observedAt": "2026-09-02T21:20:11.676Z",
+      "observedAt": "2026-09-25T21:35:56.792Z",
       "capability": "delivery.livePush",
-      "fixture": "fixtures/delivery/claude-code-2.1.258.json",
+      "fixture": "fixtures/delivery/claude-code-2.1.282.json",
       "idleBehavior": "offered",
       "provenance": "fixtures/certification-provenance.json",
-      "provenanceId": "native-delivery-2-1-258",
-      "busyBehavior": "queued_after_turn",
+      "provenanceId": "native-delivery-2-1-282-inbox",
+      "busyBehavior": "presented_between_tool_calls",
       "authorityLevel": "experimental",
       "limitations": [
-        "captured on darwin-arm64 only; Linux and Windows remain uncaptured",
-        "the vendor development-channel warning stayed visible and was accepted by the operator by hand",
-        "the plugin .mcp.json must live in the marketplace source copy; the plugin cache copy alone is not read",
-        "acc_reply routed through the spike's explicit tool call; the spike created no durable ACC answer record",
-        "presentation after the busy turn was observed by the operator; the channel log records the write at 21:18:45Z and the explicit reply at 21:19:21Z"
-      ],
-      "result": "pass"
-    },
-    {
-      "client": "claude-code",
-      "version": "2.1.258",
-      "platform": "darwin-arm64",
-      "observedAt": "2026-09-02T21:20:11.676Z",
-      "capability": "delivery.replyRoute",
-      "fixture": "fixtures/delivery/claude-code-2.1.258.json",
-      "idleBehavior": "offered",
-      "provenance": "fixtures/certification-provenance.json",
-      "provenanceId": "native-delivery-2-1-258",
-      "busyBehavior": "queued_after_turn",
-      "authorityLevel": "experimental",
-      "limitations": [
-        "captured on darwin-arm64 only; Linux and Windows remain uncaptured",
-        "the vendor development-channel warning stayed visible and was accepted by the operator by hand",
-        "the plugin .mcp.json must live in the marketplace source copy; the plugin cache copy alone is not read",
-        "acc_reply routed through the spike's explicit tool call; the spike created no durable ACC answer record",
-        "presentation after the busy turn was observed by the operator; the channel log records the write at 21:18:45Z and the explicit reply at 21:19:21Z"
-      ],
-      "result": "pass"
-    },
-    {
-      "client": "claude-code",
-      "version": "2.1.260",
-      "platform": "darwin-arm64",
-      "observedAt": "2026-09-04T03:41:29.688Z",
-      "capability": "delivery.livePush",
-      "fixture": "fixtures/delivery/claude-code-2.1.260.json",
-      "idleBehavior": "offered",
-      "provenance": "fixtures/certification-provenance.json",
-      "provenanceId": "native-delivery-2-1-260",
-      "busyBehavior": "queued_after_turn",
-      "authorityLevel": "experimental",
-      "limitations": [
-        "captured on darwin-arm64 only; Linux and Windows remain uncaptured",
-        "the vendor development-channel warning stayed visible and was accepted by the operator by hand",
-        "two ordinary sessions in one workspace, each bound to its own client process; the earlier 2.1.259 attempt is what exposed the channel binding another session identity, and this run is the verification of that fix",
-        "duplicate was observed as one logical message id and one native offer: the repeated send took the durable path, so the channel was never asked to notify twice, and exactly one answer was recorded",
-        "busy was observed by the operator: the running turn completed before the channel presented the message, and the session named that order in its own answer"
-      ],
-      "result": "pass"
-    },
-    {
-      "client": "claude-code",
-      "version": "2.1.260",
-      "platform": "darwin-arm64",
-      "observedAt": "2026-09-04T03:41:29.688Z",
-      "capability": "delivery.replyRoute",
-      "fixture": "fixtures/delivery/claude-code-2.1.260.json",
-      "idleBehavior": "offered",
-      "provenance": "fixtures/certification-provenance.json",
-      "provenanceId": "native-delivery-2-1-260",
-      "busyBehavior": "queued_after_turn",
-      "authorityLevel": "experimental",
-      "limitations": [
-        "captured on darwin-arm64 only; Linux and Windows remain uncaptured",
-        "the vendor development-channel warning stayed visible and was accepted by the operator by hand",
-        "two ordinary sessions in one workspace, each bound to its own client process; the earlier 2.1.259 attempt is what exposed the channel binding another session identity, and this run is the verification of that fix",
-        "duplicate was observed as one logical message id and one native offer: the repeated send took the durable path, so the channel was never asked to notify twice, and exactly one answer was recorded",
-        "busy was observed by the operator: the running turn completed before the channel presented the message, and the session named that order in its own answer"
+        "Observed on darwin-arm64 with Claude Code 2.1.282 in the TUI, model Sonnet 5, auto permission mode, through a private candidate built from this branch and installed with an isolated ACC data home; the plugin registration in the real Claude config directory was restored byte for byte afterwards.",
+        "Every wake carried ACC wording and the message id only. The body reached the model through the UserPromptSubmit projection that each delivered wake fired, inside the untrusted acc-peer-message block.",
+        "An idle session started a turn with no user input. A wake sent while a Bash tool call ran was taken after that call returned and before the next one, and the turn continued.",
+        "The observed reply loop uses the installed acc reply CLI; native delivery.replyRoute remains false. The router reports a wake as outcome woken via claude-inbox and leaves the receipt queued until the hook's output carried the body, which records it offered via next-turn.",
+        "A repeated logical send kept its message id, took the durable path because the receipt was already acknowledged, and produced exactly one wake.",
+        "Two sessions in one workspace each bound their own inbox; a message addressed to one never woke the other.",
+        "An exited session left no registry entry; the next message stayed queued as recipient_unavailable.",
+        "A receiving session in bypassPermissions mode was not captured; Claude Code documents that such a session holds each wake whose sender does not attest bypass, and ACC never attests a mode.",
+        "Linux and native Windows remain uncaptured."
       ],
       "result": "pass"
     }

package/node_modules/@agents-can-communicate/adapter-claude-code/fixtures/certification-provenance.json

@@ -172,13 +172,13 @@
       ]
     },
     {
-      "id": "native-delivery-2-1-258",
+      "id": "native-delivery-2-1-282-inbox",
       "client": "claude-code",
-      "version": "2.1.258",
+      "version": "2.1.282",
       "platform": "darwin-arm64",
-      "observedAt": "2026-09-02T21:20:11.676Z",
-      "fixture": "fixtures/delivery/claude-code-2.1.258.json",
-      "sha256": "c68e84989c02fa0657d0a8669a774ab1e301088d8c7856346cc9739d0fbad228",
+      "observedAt": "2026-09-25T21:35:56.792Z",
+      "fixture": "fixtures/delivery/claude-code-2.1.282.json",
+      "sha256": "7e335f61df97edbd08304227be7335931dae3bc71e3dc639804b656ea2dae66a",
       "event": null,
       "tool": null,
       "claims": [
@@ -188,80 +188,38 @@
           "outcome": {
             "kind": "native-delivery-observed",
             "idle": "offered",
-            "busy": "queued_after_turn",
+            "busy": "presented_between_tool_calls",
             "authority": "experimental",
             "limitations": [
-              "captured on darwin-arm64 only; Linux and Windows remain uncaptured",
-              "the vendor development-channel warning stayed visible and was accepted by the operator by hand",
-              "the plugin .mcp.json must live in the marketplace source copy; the plugin cache copy alone is not read",
-              "acc_reply routed through the spike's explicit tool call; the spike created no durable ACC answer record",
-              "presentation after the busy turn was observed by the operator; the channel log records the write at 21:18:45Z and the explicit reply at 21:19:21Z"
-            ]
-          }
-        },
-        {
-          "capability": "delivery.replyRoute",
-          "result": "pass",
-          "outcome": {
-            "kind": "native-delivery-observed",
-            "idle": "offered",
-            "busy": "queued_after_turn",
-            "authority": "experimental",
-            "limitations": [
-              "captured on darwin-arm64 only; Linux and Windows remain uncaptured",
-              "the vendor development-channel warning stayed visible and was accepted by the operator by hand",
-              "the plugin .mcp.json must live in the marketplace source copy; the plugin cache copy alone is not read",
-              "acc_reply routed through the spike's explicit tool call; the spike created no durable ACC answer record",
-              "presentation after the busy turn was observed by the operator; the channel log records the write at 21:18:45Z and the explicit reply at 21:19:21Z"
+              "Observed on darwin-arm64 with Claude Code 2.1.282 in the TUI, model Sonnet 5, auto permission mode, through a private candidate built from this branch and installed with an isolated ACC data home; the plugin registration in the real Claude config directory was restored byte for byte afterwards.",
+              "Every wake carried ACC wording and the message id only. The body reached the model through the UserPromptSubmit projection that each delivered wake fired, inside the untrusted acc-peer-message block.",
+              "An idle session started a turn with no user input. A wake sent while a Bash tool call ran was taken after that call returned and before the next one, and the turn continued.",
+              "The observed reply loop uses the installed acc reply CLI; native delivery.replyRoute remains false. The router reports a wake as outcome woken via claude-inbox and leaves the receipt queued until the hook's output carried the body, which records it offered via next-turn.",
+              "A repeated logical send kept its message id, took the durable path because the receipt was already acknowledged, and produced exactly one wake.",
+              "Two sessions in one workspace each bound their own inbox; a message addressed to one never woke the other.",
+              "An exited session left no registry entry; the next message stayed queued as recipient_unavailable.",
+              "A receiving session in bypassPermissions mode was not captured; Claude Code documents that such a session holds each wake whose sender does not attest bypass, and ACC never attests a mode.",
+              "Linux and native Windows remain uncaptured."
             ]
           }
         }
-      ]
-    },
-    {
-      "id": "native-delivery-2-1-260",
-      "client": "claude-code",
-      "version": "2.1.260",
-      "platform": "darwin-arm64",
-      "observedAt": "2026-09-04T03:41:29.688Z",
-      "fixture": "fixtures/delivery/claude-code-2.1.260.json",
-      "sha256": "7513d13b6dc1c6b485d899550f43ae3577cd99fca108f06691f7ad07daf06f03",
-      "event": null,
-      "tool": null,
-      "claims": [
+      ],
+      "productEvidence": {
+        "fixture": "fixtures/delivery/claude-code-2.1.282-product-evidence.json",
+        "sha256": "1ac87ee547c6fdb38e0bdd62830f1fbd23bca51219a7ba906c7a0a1b2efd1346"
+      },
+      "historicalFixtures": [
         {
-          "capability": "delivery.livePush",
-          "result": "pass",
-          "outcome": {
-            "kind": "native-delivery-observed",
-            "idle": "offered",
-            "busy": "queued_after_turn",
-            "authority": "experimental",
-            "limitations": [
-              "captured on darwin-arm64 only; Linux and Windows remain uncaptured",
-              "the vendor development-channel warning stayed visible and was accepted by the operator by hand",
-              "two ordinary sessions in one workspace, each bound to its own client process; the earlier 2.1.259 attempt is what exposed the channel binding another session identity, and this run is the verification of that fix",
-              "duplicate was observed as one logical message id and one native offer: the repeated send took the durable path, so the channel was never asked to notify twice, and exactly one answer was recorded",
-              "busy was observed by the operator: the running turn completed before the channel presented the message, and the session named that order in its own answer"
-            ]
-          }
+          "fixture": "fixtures/inbox-wake-2.1.282.json",
+          "sha256": "247836aefd6e446670f53e63ed3a29483a9124bfc7b38fc69ba7cd5e866fa2e1"
         },
         {
-          "capability": "delivery.replyRoute",
-          "result": "pass",
-          "outcome": {
-            "kind": "native-delivery-observed",
-            "idle": "offered",
-            "busy": "queued_after_turn",
-            "authority": "experimental",
-            "limitations": [
-              "captured on darwin-arm64 only; Linux and Windows remain uncaptured",
-              "the vendor development-channel warning stayed visible and was accepted by the operator by hand",
-              "two ordinary sessions in one workspace, each bound to its own client process; the earlier 2.1.259 attempt is what exposed the channel binding another session identity, and this run is the verification of that fix",
-              "duplicate was observed as one logical message id and one native offer: the repeated send took the durable path, so the channel was never asked to notify twice, and exactly one answer was recorded",
-              "busy was observed by the operator: the running turn completed before the channel presented the message, and the session named that order in its own answer"
-            ]
-          }
+          "fixture": "fixtures/delivery/claude-code-2.1.258.json",
+          "sha256": "c68e84989c02fa0657d0a8669a774ab1e301088d8c7856346cc9739d0fbad228"
+        },
+        {
+          "fixture": "fixtures/delivery/claude-code-2.1.260.json",
+          "sha256": "7513d13b6dc1c6b485d899550f43ae3577cd99fca108f06691f7ad07daf06f03"
         }
       ]
     }