acbridge 1.1.3 → 1.4.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "acbridge",
-  "version": "1.1.3",
+  "version": "1.4.0",
   "description": "Control AC Bridge from any terminal: sign in, run the bridge, and drive smart-home devices and Profiles.",
   "license": "UNLICENSED",
   "author": "AC BRIDGE LIMITED",

package/plugin/README.md

@@ -7,6 +7,12 @@ Profiles (see [`../docs/CLAUDE-SIGNALS.md`](../docs/CLAUDE-SIGNALS.md)). Install
 then loaded on every session with `claude --channels plugin:alexa@bridge` — **no `--dangerously-*`
 flag**. This directory is the *packaging* of the `channel/` workspace for that installed-plugin path.
 
+`signal.mjs` also CARRIES the agent device-brief (2026-08): at SessionStart it asks the hub
+(`GET /local/agent/brief`) whether the cwd's bound profile ticks "Make agent aware of devices in
+chat" and, if so, prints the brief as `hookSpecificOutput.additionalContext` — its only stdout,
+on that one event. For Codex the same brief rides the channel's MCP `instructions` instead
+(`acbridge setup` registers `[mcp_servers.acbridge]` in `~/.codex/config.toml`, env `ACB_AGENT=codex`).
+
 This same `plugins/alexa/scripts/` directory also carries `codex-signal.mjs` — the Codex CLI sibling
 of `signal.mjs` (below). It is **not** registered in this plugin's own `hooks/hooks.json`; Codex CLI
 has its own hooks engine entirely, and `acbridge setup` installs `codex-signal.mjs` directly into
@@ -17,11 +23,11 @@ Codex's `~/.codex/hooks.json` instead (§ below).
 | Path (under `plugin/`) | Role |
 |------------------------|------|
 | `.claude-plugin/marketplace.json` | Marketplace manifest — declares the marketplace `name: "bridge"` and lists its one plugin, `alexa` (`source: ./plugins/alexa`). |
-| `plugins/alexa/.claude-plugin/plugin.json` | Plugin manifest — `name: "alexa"`, `version 0.1.0`; declares a `channels` capability bound to the `alexa` MCP server. |
+| `plugins/alexa/.claude-plugin/plugin.json` | Plugin manifest — `name: "alexa"`, `version 0.4.0`; declares a `channels` capability bound to the `alexa` MCP server. |
 | `plugins/alexa/.mcp.json` | MCP server definition — spawns the channel as `node ${CLAUDE_PLUGIN_ROOT}/dist/channel.mjs`. |
 | `plugins/alexa/hooks/hooks.json` | Registers the `PreToolUse` gate (`→ scripts/gate.mjs`) **plus** the Profiles session-state signals on `SessionStart`/`SessionEnd`/`UserPromptSubmit`/`Stop`/`StopFailure`/`Notification`/`PreToolUse[AskUserQuestion\|ExitPlanMode\|Workflow]`/`PostToolUse`/`PostToolUseFailure`/`SubagentStart`/`SubagentStop`/`PreCompact`/`PostCompact`/`PermissionDenied`/`TaskCompleted` (all `→ scripts/signal.mjs`). |
 | `plugins/alexa/scripts/gate.mjs` | The PreToolUse permission gate (below). |
-| `plugins/alexa/scripts/signal.mjs` | The Profiles session-state signal — maps each lifecycle hook → one of the 28 wire states (+ on every POST: a transcript-tail `context` reading and the raw **mode/model ferry** — the last `permission-mode` record + assistant model id, which the hub diffs into the mode/`modelChanged` states) → `POST /local/session/state`; successful tools → a state-less tick on `POST /local/session/context` (below). |
+| `plugins/alexa/scripts/signal.mjs` | The Profiles session-state signal — maps each lifecycle hook → one of the 30 wire states (+ on every POST: a transcript-tail `context` reading and the raw **mode/model ferry** — the last `permission-mode` record + assistant model id, which the hub diffs into the mode/`modelChanged` states) → `POST /local/session/state`; successful tools → a state-less tick on `POST /local/session/context` (below). |
 | `plugins/alexa/scripts/statusline.mjs` | The statusline TEE — installed as Claude's `statusLine` command by `acbridge` (reversible; chains any existing statusline): POSTs the exact context % + rate-limit % + `model.id`/`display_name` to `/local/session/context` (the `usageHigh` data feed and the freshest `modelChanged` source), then renders. |
 | `plugins/alexa/scripts/codex-signal.mjs` | The Codex CLI sibling of `signal.mjs` (below) — installed into `~/.codex/hooks.json`, **not** this plugin's `hooks/hooks.json`. |
 | `plugins/alexa/dist/channel.mjs` | The bundled channel MCP server — **build artifact** copied from `../channel/` (gitignored; absent until built). |
@@ -173,9 +179,12 @@ Claude); the POST is bounded by a 2 s timeout.
 `scripts/codex-signal.mjs` is the Codex CLI sibling of `signal.mjs` above, for a repo bound to a
 **Codex** profile. It is installed by `acbridge setup` (`node-core/src/codex-setup/hooks.ts`,
 merge-safe/reversible — every foreign hook survives verbatim; off-switch `BRIDGE_CODEX_HOOKS=0` /
-`"autoCodexHooks": false`) directly into **Codex's own** `~/.codex/hooks.json`, registered against 9
+`"autoCodexHooks": false`) directly into **Codex's own** `~/.codex/hooks.json`, registered against 10
 lifecycle events: `SessionStart`, `UserPromptSubmit`, `Stop`, `PermissionRequest`, `PreCompact`,
-`PostCompact`, `SubagentStart`, `SubagentStop`, `PostToolUse`. Codex requires a one-time in-TUI
+`PostCompact`, `SubagentStart`, `SubagentStop`, `PostToolUse`, `SessionEnd` (the last is the 2026-08
+addition — upstream Codex shipped the hook mid-2026; it is appended LAST so a document written by the
+9-event installer gains exactly one new key on re-run, and Codex keys hook trust per event, so it
+ships untrusted until the user approves it via `/hooks`). Codex requires a one-time in-TUI
 `/hooks` review before a third-party hook actually runs — `acbridge setup` prints that reminder when
 it changes the file, since it can't bypass the gate.
 
@@ -191,26 +200,32 @@ suffix on a self-derived session. `PermissionRequest` is observe-and-abstain: cl
 device signal, but this script **never** writes to stdout (Codex reads a permission hook's stdout as
 an approve/deny decision).
 
-Codex has no `SessionEnd`/`Notification`/`StopFailure`/`PermissionDenied`/`TaskCompleted` hooks and
-no rate-limit data; this hook script reaches 17 states directly (the 16 originals plus `error`, from
-an error-shaped tool result on `PostToolUse`), and the adapter/voice surface reaches the rest of the
-23-state codex mask — `CODEX_EVENTS` (`contracts/src/profiles.ts`, 23 of the 28 wire states) — which
-is exactly what the Codex profile editor offers. Same activation
+Codex has no `Notification`/`StopFailure`/`PermissionDenied`/`TaskCompleted` hooks and no rate-limit
+data; this hook script reaches 18 states directly (the 16 originals, plus `error` from an
+error-shaped tool result on `PostToolUse`, plus `ended` from `SessionEnd`), and the adapter/voice
+surface reaches the rest of the 24-state codex mask — `CODEX_EVENTS` (`contracts/src/profiles.ts`, 24
+of the 30 wire states) — which is exactly what the Codex profile editor offers. Same activation
 ladder and fail-safes as `signal.mjs` (BRIDGE_* env → per-session handshake → self-derive when a hub
 is configured on this machine; `BRIDGE_AUTO_PROFILES=0` off-switch; any parse/IO/network error exits
-0) — with one structural difference and one lifecycle gap, both recorded in
-[`../docs/reviews/XPLAT-2026-07-28.md`](../docs/reviews/XPLAT-2026-07-28.md):
-
-- **Local home + fixed port only.** Unlike `signal.mjs`, this script does **not** resolve the
-  WSL↔Windows bridge home: it pins the local `~/.claude-bridge` (`BRIDGE_SECRET_DIR` aside) and the
-  env/config `hubPort` — no `resolveBridgeHome()`, no beacon-port pickup, and no
-  `hooks-last-error.json` breadcrumb on rejection. With the hub on the other side of a WSL↔Windows
-  split (or bound off 8790 without a matching `config.json`), hook-lane Codex Profiles silently no-op.
-- **No `ended`, ever.** No Codex hook can produce the `ended` state (Codex ships no `SessionEnd`),
-  and the hub keys Profile scene revert + arbiter stand-down on `ended` — so a hook-lane Codex session
-  that exits leaves its scene applied and its arbiter claim held on a daemon-kept hub until the next
-  session starts or the hub itself stops. The adapter lane (`acbridge run --agent codex`) does post
-  `ended` and is unaffected.
+0), and — since the 2026-07-29 XPLAT-HOME fix — the same **bridge-home resolution** as its Claude
+twins: `resolveBridgeHome()`, beacon-port-before-config ordering, and a `hooks-last-error.json`
+breadcrumb on rejection. A hub on the other side of a WSL↔Windows split, or bound off 8790, is
+therefore found rather than silently missed.
+
+Two structural differences remain, and neither is a bug:
+
+- **`started` is synthesized in the TUI.** Codex v0.146's TUI dispatches no `SessionStart` (live-
+  verified 2026-08-02: a TUI session sat open with zero hook dispatches while the same binary's
+  `codex exec` fired it), so the script synthesizes `started` from the first event it ever sees for a
+  session — POSTed before that event's own signal, audit-tagged `codex:SessionStart~synthesized`. The
+  start scene therefore fires with the first **message**, not at window-open. `exec` (and any future
+  TUI that dispatches `SessionStart` again) writes the handshake at start, so the workaround
+  self-disables.
+- **The hub's 30-minute idle close is a BACKSTOP, not the close.** `SessionEnd` → `ended` is the real
+  close and runs scene revert + arbiter stand-down the moment Codex exits; the synthesized idle close
+  (`hub/src/devices/session-idle.ts`) covers abnormal exits, pre-`SessionEnd` Codex builds, and hook
+  entries not yet trusted via `/hooks`. The adapter lane (`acbridge run --agent codex`) posts `ended`
+  itself and never needed either.
 
 Full detail: [`../docs/CLAUDE-SIGNALS.md`](../docs/CLAUDE-SIGNALS.md) §7a.