@sym-bot/mesh-channel 0.3.1 → 0.3.3

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "sym-mesh-channel",
-  "version": "0.3.1",
+  "version": "0.3.3",
   "description": "Real-time Claude-to-Claude mesh. Agent-to-agent cognitive signals over Bonjour LAN or WebSocket relay.",
   "author": {
     "name": "Hongwei Xu",

package/CHANGELOG.md

@@ -1,5 +1,48 @@
 # Changelog
 
+## 0.3.3
+
+### Fixed
+
+- **Real-time duplex for CAT7 CMBs.** The `cmb-accepted` handler now
+  stores the rendered CMB body under an `[mNNN]` ID and includes that
+  ID in the channel notification, matching the contract stated in the
+  MCP instructions ("Messages arrive as compact headers with [mNNN] IDs
+  — use sym_fetch to read the full content") and the behaviour of the
+  raw-text `message` path.
+
+  Previously only the legacy raw-text `message` event persisted bodies
+  to `MESSAGE_STORE` — the primary `cmb-accepted` event (fired for
+  every structured CMB delivered via `sym_send` / `sym_observe`) pushed
+  a headline with no `[mNNN]` and left no retrievable body. Inbound
+  CMBs were admitted to the SVAF-backed memory store and surfaced by
+  `sym_recall` as compact headlines, but `sym_fetch` could not return
+  their content — the duplex was effectively headline-only for the 99%
+  case of real mesh traffic.
+
+  Symptom: after the 0.3.2 Mac↔Win fix restored bidirectional packet
+  flow, peers' structured replies appeared in `sym_recall` but returned
+  *"expired or invalid ID"* from `sym_fetch` — because `storeMessage()`
+  had never been called for them. Now both the raw-text and CAT7 paths
+  persist bodies identically.
+
+## 0.3.2
+
+### Fixed
+
+- **Pulls in `@sym-bot/sym` 0.5.1** — fixes Mac↔Windows peer connections
+  over LAN. Prior releases shipped a Bonjour advertisement whose SRV
+  target was the bare Windows NetBIOS hostname (e.g. `xmesh-hp.`) with
+  no `.local` suffix. macOS mDNSResponder only resolves `.local.` mDNS
+  names, so Macs could discover Windows peers via bonjour browse but
+  failed to open the outbound TCP connection. CMBs targeted at Windows
+  nodes never arrived; no replies came back. Full diagnosis in sym
+  0.5.1 CHANGELOG.
+
+  Upgrade required on both sides to restore Mac↔Windows traffic.
+  Existing Windows identities with a bare hostname are auto-migrated
+  on next node start; no manual config edit needed.
+
 ## 0.3.1
 
 ### Fixed

package/README.md

@@ -236,7 +236,7 @@ Clear-eyed about what's not there yet:
 - **Corporate networks often block mDNS multicast.** If LAN discovery fails on the same wifi, fall back to a relay.
 - **No offline directory of known groups.** `sym_groups_discover` only shows groups with at least one node currently online. For cross-network relay-backed groups, invite URLs must be shared out of band.
 - **One mesh identity per process.** Two Claude Code sessions on the same machine with the same `SYM_NODE_NAME` will collide — the second one exits with `EIDENTITYLOCK`. Use distinct `SYM_NODE_NAME`s or install per-project (above).
-- **No end-to-end encryption of CMB payloads.** Transport is authenticated (Ed25519, relay tokens) but relay operators can read message bodies. E2E encryption is on the MMP roadmap.
+- **E2E encryption is per-peer-pair, not universal.** CMB field content is encrypted with Curve25519 key agreement + AES-256-GCM between peers that both advertise an E2E public key on handshake. Peers without E2E support fall back to plaintext for backward compatibility. Outer frame metadata (sender ID, timestamp, lineage) stays plaintext — enough for relay forwarding and SVAF evaluation without seeing bodies.
 
 ## Troubleshooting
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sym-bot/mesh-channel",
-  "version": "0.3.1",
+  "version": "0.3.3",
   "description": "MCP server — real-time agent-to-agent cognition for Claude Code remote teams via the SYM mesh.",
   "main": "server.js",
   "bin": {
@@ -22,7 +22,7 @@
   ],
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.12.1",
-    "@sym-bot/sym": "^0.5.0"
+    "@sym-bot/sym": "^0.5.1"
   },
   "engines": {
     "node": ">=18"

package/server.js

@@ -240,7 +240,15 @@ function registerNodeHandlers(n) {
     if (!isPeerAllowed(source)) return;
     const focus = entry.cmb?.fields?.focus?.text || entry.content || '';
     const mood = entry.cmb?.fields?.mood?.text || '';
-    pushChannel('cmb', `[${source}] ${focus}${mood && mood !== 'neutral' ? ` (mood: ${mood})` : ''}`);
+    const moodSuffix = mood && mood !== 'neutral' ? ` (mood: ${mood})` : '';
+    // Store the rendered CMB body so the agent can sym_fetch it by [mNNN] ID,
+    // matching the contract stated in the MCP instructions and the behaviour
+    // of the raw-text `message` path. Without this, CAT7 CMBs (the primary
+    // traffic — sym_send / sym_observe) arrive as headlines with no
+    // retrievable body, degrading real-time duplex to headline-only.
+    const body = entry.content || focus;
+    const msgId = storeMessage(source, body);
+    pushChannel('cmb', `[${source}] ${focus}${moodSuffix} [${msgId}]`);
   });
 
   n.on('message', (from, content) => {