agent-embassy 4.3.0 → 4.4.1

package/docs/GATEWAY-ARCHITECTURE.md

@@ -8,10 +8,8 @@ pairs are supported. Sending is one `embassy send` command; receiving wakes the
 target through its native interface. A receipt proves delivery machinery, not
 model comprehension.
 
-The design optimizes for this steady state and deliberately excludes native
-Claude `SendMessage` advertisement helpers, shell-peer mailboxes, automatic
-Codex output forwarding, persistent remote mirrors, general activity streams,
-and migration compatibility.
+The design optimizes for this steady state; everything it deliberately leaves
+out is listed under [Responsibility exclusions](#responsibility-exclusions).
 
 ## Topology
 
@@ -31,8 +29,8 @@ Claude/Codex CLI
                                       remote broker ledger
 ```
 
-There is one broker per login user and host. The broker owns one schema-7 JSON
-document and one private control socket. It does not listen on a network port.
+There is one broker per login user and host. The broker owns one private JSON
+state document and one private control socket. It does not listen on a network port.
 launchd may supervise the same foreground `serve` entry point.
 
 ## Endpoint directory
@@ -139,8 +137,8 @@ guessing. The live host lease is checked before a transaction, before
 persistence, and immediately before rename.
 
 No-op transactions write nothing. Unsupported or corrupt state refuses before
-mutation. Valid schema 6 reads forward with all existing rows retained; writes use 7.
-The only added field is the private retention marker. Schema ≤5 still needs a reset.
+mutation. A valid schema-6 document from an earlier 4.x release reads forward
+with all existing rows retained; schema ≤5 needs a reset.
 
 ## Coordinator
 
@@ -239,9 +237,8 @@ reset.
 
 ## Local control and CLI
 
-The private control protocol is version 6. Each connection carries one bounded
-JSON request and one closed JSON response over the expected private Unix
-socket. A mutating request whose reply is lost after write reports
+Each private control connection carries one bounded JSON request and one
+closed JSON response over the expected private Unix socket. A mutating request whose reply is lost after write reports
 `CONTROL_WRITE_OUTCOME_AMBIGUOUS`; the CLI does not retry it.
 
 The public CLI is:
@@ -257,8 +254,9 @@ serve            service           peer-stdio
 `send` accepts exactly one of `--to` and `--conversation`; it has no `--from`.
 Human `status` is a rendering of the same closed body-free JSON shape. Its
 health word describes control/ledger health, local route rows expose their last
-native operation, and Codex rows expose busy, waiting, idle, dormant or unknown
-status, without parent references or registration-origin labels. The federation section
+native operation, and Codex rows expose busy, waiting, idle, dormant,
+systemError or unknown status, without parent references or
+registration-origin labels. The federation section
 exposes only the last bounded catalog observation. `health` is a control-path probe. `check` creates temporary
 private loopback endpoints and uses the real ledger/coordinator/receipt path,
 then retires them; no provider or model is contacted. It is not a
@@ -283,7 +281,7 @@ Startup order is ownership-sensitive:
 1. load the private node inventory, or derive a transient first-boot default,
    and load configuration;
 2. acquire the fixed host-wide kernel lease;
-3. open and validate schema-7 state without changing the inventory;
+3. open and validate the private state without changing the inventory;
 4. atomically install and reload the default inventory when first boot needs
    one;
 5. construct native and SSH adapters;
@@ -304,7 +302,7 @@ model interrupt.
 
 | Surface | Version | Compatibility policy |
 |---|---:|---|
-| Private state (`gateway-state.json`) | 7 | Reset only; older and unknown schemas refuse without mutation |
+| Private state (`gateway-state.json`) | 7 | A valid schema-6 document is read forward with rows retained; ≤5 and unknown refuse without mutation (reset) |
 | Private control (CLI ↔ broker) | 6 | CLI and broker must come from one installation |
 | Federation (`peer-stdio`) | 3 | Exact version and host handshake; no compatibility mode |
 | Consumed Claude peer protocol | 1 | Incompatible records are rejected in isolation |
@@ -314,10 +312,11 @@ each use boundary. Version or build metadata is never routing authority.
 
 ## Responsibility exclusions
 
-The v4 core intentionally has no shell-peer registration/token/mailbox/await
+The core intentionally has no shell-peer registration/token/mailbox/await
 system, no native Claude advertisement helper, no automatic provider-output
 reply capture, no persisted remote route mirror, no pair/selection graph, no
-dashboard/watch event system, no notice-mode machinery, and no v3 migration
-reader. The responsibilities that remain are endpoint identity, bounded
+dashboard/watch event system, no notice-mode machinery, and no old-state
+migration reader. Its responsibilities are endpoint identity, bounded
 delivery, native wake, exact replies, direct federation, status, retirement,
-service supervision, and loopback verification.
+service supervision, and loopback verification. The reasons are recorded in
+the repository's `docs/DECLINED.md`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-embassy",
-  "version": "4.3.0",
+  "version": "4.4.1",
   "description": "A local gateway for bidirectional messaging between Claude Code sessions and Codex tasks.",
   "license": "MIT",
   "repository": {
@@ -62,13 +62,18 @@
     "soak": "tsx --test test/soak/core-soak.test.ts"
   },
   "engines": {
-    "node": ">=20"
+    "node": ">=22"
   },
   "dependencies": {
+    "ink": "7.1.1",
+    "react": "19.2.8",
+    "string-width": "8.2.2",
+    "wrap-ansi": "10.0.1",
     "ws": "8.21.3"
   },
   "devDependencies": {
     "@types/node": "24.10.1",
+    "@types/react": "19.2.18",
     "@types/ws": "8.18.1",
     "tsx": "4.20.6",
     "typescript": "5.9.3"

package/skills/embassy-peer/SKILL.md

@@ -100,4 +100,4 @@ For operator-authorized removal use `embassy retire --alias <local-alias>`. It r
 
 When a name collides, operator-authorized `embassy retire --endpoint <public-id>` removes just that local endpoint using its opaque ID from status. Use exactly one of `--alias` or `--endpoint`; never substitute a native session ID. A partial discovery cannot clear a known collision; exact user-supplied UUID addressing remains available until a complete scan proves uniqueness.
 
-There is no shell-peer mailbox, await command, native sending advertisement, automatic output forwarding, reply alias, or unregister-codex command in v4. Do not fall back to removed commands or direct provider sockets; report the precise refusal.
+`embassy --help` lists the whole public CLI; do not fall back to a command that is not listed there or to direct provider sockets; report the precise refusal.