@sym-bot/mesh-channel 0.3.5 → 0.3.7

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "sym-mesh-channel",
-  "version": "0.3.5",
+  "version": "0.3.7",
   "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,18 @@
 # Changelog
 
+## 0.3.7
+
+### Changed
+
+- **Bumped `@sym-bot/sym` dependency `^0.5.8` → `^0.7.4`** to track the current sym stack. The range had drifted: sym moved through 0.6.x/0.7.x (mesh groups, Windows portability) while this wrapper still declared `^0.5.8`, so an installed sym ≥0.6 showed as `invalid` and a reinstall could nest a stale 0.5.x that shadows the global. Pinning `^0.7.4` makes the dependency honest and, in particular, **requires the loopback-capable sym (≥0.7.4)** — co-resident nodes mesh over `127.0.0.1` with no network interface (Wi-Fi off). No code change in this package; dependency-range correctness only.
+
+## 0.3.6
+
+### Added
+
+- **Group discovery beacon.** This MCP node now advertises its mesh group on a shared `_symgroups._tcp` service (group name in TXT) via the pure-JS `bonjour-service` — published on start, re-published on `sym_join_group` hot-swap, torn down on shutdown. Makes the Claude/MCP node discoverable by the `sym` CLI's `sym groups` command **cross-platform, including Windows** (where Apple's `dns-sd` is absent), so CLI-daemon and Claude/MCP nodes list together. Discovery-only — comms stay isolated on the group's own `_<group>._tcp`. `bonjour-service` pinned as a direct dependency. Validated on Windows 11.
+- **Operational note:** a session started before 0.3.6 must restart to begin beaconing.
+
 ## 0.3.5
 
 ### Added

package/README.md

@@ -103,6 +103,8 @@ With the Channels flag enabled, real-time push is bidirectional: peer events arr
 
 By default every `sym-mesh-channel` node joins the global `_sym._tcp` mesh — every peer on the network sees every other peer. For a company with multiple teams, that's too noisy. Mesh groups (MMP §5.8) isolate each team at the mDNS layer so `backend-team` and `frontend-team` can't see each other's signals at all.
 
+> **Discoverable by the `sym` CLI (since 0.3.6).** This node advertises its group on a shared `_symgroups._tcp` discovery beacon, so the [`sym` CLI](https://www.npmjs.com/package/@sym-bot/sym)'s `sym groups` lists this Claude/MCP node alongside CLI-daemon nodes — cross-platform, including Windows (where Apple's `dns-sd` is absent). Discovery-only; comms stay isolated on the group's own service type. *(A restart is needed for sessions started before 0.3.6 to begin beaconing.)*
+
 ### Same office (LAN)
 
 **Team lead creates the group from any Claude Code session:**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sym-bot/mesh-channel",
-  "version": "0.3.5",
+  "version": "0.3.7",
   "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,8 @@
   ],
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.12.1",
-    "@sym-bot/sym": "^0.5.8"
+    "@sym-bot/sym": "^0.7.4",
+    "bonjour-service": "^1.3.0"
   },
   "engines": {
     "node": ">=18"

package/server.js

@@ -763,6 +763,8 @@ mcp.setRequestHandler(CallToolRequestSchema, async (request) => {
       RELAY_URL = relayUrl;
       RELAY_TOKEN = relayToken;
 
+      publishGroupBeacon();   // re-advertise the new group on _symgroups._tcp
+
       return {
         content: [{
           type: 'text',
@@ -887,6 +889,7 @@ let shuttingDown = false;
 async function shutdown(signal) {
   if (shuttingDown) return;
   shuttingDown = true;
+  stopGroupBeacon();
   try {
     await node.stop();
   } catch {
@@ -899,12 +902,37 @@ process.on('SIGTERM', () => shutdown('SIGTERM'));
 process.on('SIGINT',  () => shutdown('SIGINT'));
 process.on('SIGHUP',  () => shutdown('SIGHUP'));
 
+// ── Group discovery beacon (MMP §5.8) ──────────────────────────
+// Mirror the sym CLI daemon: advertise this node's group on the shared
+// `_symgroups._tcp` service (group name in TXT) via the pure-JS bonjour-service,
+// so `sym groups` lists this Claude/MCP node cross-platform alongside
+// CLI-daemon nodes. Discovery-only — comms stay on the group's own
+// `_<group>._tcp`. Re-published on group hot-swap; torn down on shutdown.
+let groupBeacon = null;
+function publishGroupBeacon() {
+  try {
+    const { Bonjour } = require('bonjour-service');
+    if (groupBeacon) { try { groupBeacon.unpublishAll(); groupBeacon.destroy(); } catch {} groupBeacon = null; }
+    groupBeacon = new Bonjour();
+    groupBeacon.publish({ name: NODE_NAME, type: 'symgroups', port: (node && node._port) || 7777, txt: { group: GROUP, node: NODE_NAME } });
+  } catch (e) {
+    process.stderr.write(`group beacon unavailable: ${e?.message || e}\n`);
+  }
+}
+function stopGroupBeacon() {
+  if (!groupBeacon) return;
+  try { groupBeacon.unpublishAll(() => { try { groupBeacon.destroy(); } catch {} }); } catch {}
+  groupBeacon = null;
+}
+
 async function main() {
   // Start SymNode — connects to relay as a peer. The startup primer is
   // computed at module-load time (see BASE_INSTRUCTIONS above) and is
   // already embedded in the MCP server's initialize-response payload.
   await node.start();
 
+  publishGroupBeacon();
+
   // Start MCP server — communicates with Claude Code via stdio
   const transport = new StdioServerTransport();
   await mcp.connect(transport);