npm - @sym-bot/mesh-channel - Versions diffs - 0.3.12 → 0.3.14 - Mend

@sym-bot/mesh-channel 0.3.12 → 0.3.14

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (10) hide show

package/.claude-plugin/plugin.json +50 -50
package/.mcp.json +16 -16
package/CHANGELOG.md +655 -627
package/LICENSE +201 -201
package/README.md +395 -381
package/SECURITY.md +89 -89
package/bin/install.js +694 -603
package/package.json +50 -50
package/server.js +1107 -1105
package/.claude-plugin/marketplace.json +0 -46

package/CHANGELOG.md CHANGED Viewed

@@ -1,627 +1,655 @@
-# Changelog
-## 0.3.11
-### Added
-- **Prompt-injection filter (security layer 3).** Every incoming CMB — all CAT7 fields and the opaque payload — is now scanned against a curated blocklist of injection patterns before `pushChannel()` is called. Patterns cover: instruction-override phrases ("ignore previous instructions", "forget everything you know"), role/persona hijacking ("you are now a new AI", "act as an unrestricted assistant"), system-prompt injection (`<system>`, `[SYSTEM]`, `## system prompt`), tool-call fabrication (`<tool_call>`, `<function_calls>`), and privilege-escalation language ("override safety filter", "jailbreak", "DAN mode"). Blocked CMBs are audit-logged to stderr with reason, peer name, and a truncated excerpt — never silently dropped.
-- **Per-peer rate limiting.** A sliding 60-second window caps each peer at `SYM_RATE_LIMIT` CMBs per minute (default: 30). CMBs exceeding the cap are blocked and audit-logged. Prevents flood attacks from a compromised or malfunctioning peer.
-- **Payload size cap.** Payloads larger than `SYM_MAX_PAYLOAD_BYTES` (default: 8 192 bytes) are rejected before context injection. Prevents oversized-payload attacks that could exhaust the context window.
-- **README security section updated** to document all four defence layers accurately.
-### Security model
-The full gate before any mesh signal reaches Claude's context is now:
-1. **Transport** — Ed25519 peer identity + relay-token auth.
-2. **Protocol** — SVAF per-field semantic relevance gate.
-3. **Safety** — prompt-injection filter + rate limiter + payload size cap (this release).
-4. **Application** — text-only injection; `claude/channel/permission` not declared.
-## 0.3.10
-### Fixed
-- **Live-identity-collision auto-suffix.** Two sessions wanting the same `SYM_NODE_NAME` previously hard-failed with `EIDENTITYLOCK`. The server now checks whether the name's lock file is held by a live process; if so, it appends `-2`, `-3`, … (up to 64) until it finds a free slot. Stale locks (dead holder) are still reclaimed by `@sym-bot/sym` on start — unchanged. Result: duplicate dev-agent sessions, or any two sessions sharing a fixed `SYM_NODE_NAME`, coexist instead of failing.
-## 0.3.9
-### Fixed
-- **stdout discipline — fixes `-32000 / Connection closed`.** The MCP JSON-RPC stream runs on stdout. Dependency load banners (e.g. `[encoder] Semantic encoder ready` from the semantic model) were printing to stdout, intermittently corrupting the handshake and causing Claude Code to log "Ignoring non-JSON line on stdout" or drop the connection with `-32000`. A stdout guard is now installed before any `require()`: lines that start with `{` (JSON-RPC frames) pass through to the real stdout; everything else is redirected to stderr. Verified: stdout is pure JSON after the fix.
-## 0.3.8
-### Added
-- **Per-session node identity.** Each Claude Code session now gets its own mesh identity derived from the working-directory slug and a session-unique suffix (e.g. `claude-symday-webapp-6e174e`), instead of all sessions sharing the machine hostname. Enables multiple Claude Code sessions on the same machine to appear as distinct peers on the mesh — confirmed working over loopback via Bonjour with no relay.
-- **`npx` launch path.** The plugin now launches via `npx @sym-bot/mesh-channel` rather than a global `node` path, so marketplace installs work without a prior `npm install -g`. The npx cache warms on first launch; subsequent sessions start in ~1 s.
-## 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
-- **Opaque payload on `sym_send` / `sym_observe`.** Both tools accept
-  an optional `payload` argument carrying data beyond CAT7 — any
-  JSON-serializable value. Forwarded to `SymNode.remember(fields, {
-  payload, … })` (requires `@sym-bot/sym` ≥ 0.5.8) and rides the wire
-  frame to peers. Used by substrate-level protocols that need to carry
-  structured data alongside CAT7 (e.g. LLM request/response, where the
-  prompt + request_id ride in `payload` rather than getting smuggled
-  through `motivation`).
-- **Channel notifications surface payload-bearing CMBs.** When an
-  incoming peer CMB carries `cmb.payload`, the header gains a
-  `[+payload Nb]` indicator and the body stored by `sym_fetch`
-  includes a `---PAYLOAD---` section with the serialized payload.
-  Receivers learn from the header that there's structured data beyond
-  CAT7 and call `sym_fetch` to consume it.
-- Base MCP instructions now teach agents to recognise the
-  `[+payload Nb]` header and to pass structured responses via the
-  `payload` argument when emitting substrate-level CMBs.
-### Compatibility
-- Omitting `payload` produces a v0.3.4-shaped CAT7 CMB byte-for-byte.
-- Old peers (without `cmb.payload`) surface unchanged headers — no
-  `[+payload …]` indicator, no PAYLOAD section in the body.
-## 0.3.4
-### Added
-- **`SYM_GROUP` is now first-class in the installer.** `init` accepts a
-  `--group <name>` flag and reads the `SYM_GROUP` env var; both paths
-  persist the chosen group into the `~/.claude.json` (or project
-  `.mcp.json`) env block so every Claude Code launch auto-joins the
-  named group instead of the global `_sym._tcp` mesh.
-  Resolution order is `--force`-aware:
-    - With `--force` and an explicit `--group`/`SYM_GROUP`: flag/env wins
-      (one-command group switch on a live entry).
-    - Without `--force`, or with `--force` but no explicit value:
-      preserved value from any existing entry > explicit > none (omit).
-  `--force --group default` (or `SYM_GROUP=default`) is the explicit
-  escape hatch to revert a node from a named group back to the global
-  mesh — removes `SYM_GROUP` from the env block entirely rather than
-  writing the literal string "default".
-  Both `--group` and `SYM_GROUP` env values are validated against the
-  same kebab-case regex; malformed values exit with a clear error
-  before any file write.
-- **`doctor` now reports the persisted group per entry** and warns when
-  user-global and project-scoped entries disagree on `SYM_GROUP`.
-  Group-mismatch is the most common cause of "peers never appear in
-  `sym_peers`" with no other failure signal — surfacing it inline saves
-  the diagnostic walk that motivated this release.
-- **README** gains a "Persisting your group across restarts" subsection
-  under Team mesh groups, plus a troubleshooting entry covering the
-  group-mismatch failure mode. Quick-start shows the `--group` flag.
-### Fixed
-- **Stale-entry heal preserves `SYM_GROUP` alongside `SYM_NODE_NAME`.**
-  Previously, healing a stale `claude-sym-mesh` entry (args[0] points at
-  a missing server.js) silently dropped any persisted `SYM_GROUP`,
-  reverting the node to the default mesh on next launch and stranding
-  teammates who stayed in the named group. The heal path now copies
-  both fields from the prior entry into the rewrite.
-  Same fix applied to project-scoped entry healing under
-  `claudeJson.projects[<path>].mcpServers`.
-### Why this matters
-Before 0.3.4, the only way to persist a group was to hand-edit
-`~/.claude.json`. The README pitched `sym_join_group` as the team-mesh
-UX, but that tool is runtime-only — the next Claude Code launch reverted
-the node to the default mesh, peer count dropped to zero, and the user
-saw no diagnostic signal. The 2026-05-02 SYM.BOT incident (CMO in
-`default`, COO in `sym-bot-team`, ~24h of silent duplex outage) traced
-directly to this gap.
-## 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
-- **Installer no longer silently ships a broken MCP config.** Previously,
-  if `~/.claude.json` already contained a `claude-sym-mesh` entry,
-  `npm install -g @sym-bot/mesh-channel` (via postinstall) and
-  `npx @sym-bot/mesh-channel init` both skipped with "already configured"
-  — even when the entry's `args[0]` server.js path no longer existed on
-  disk (common after moving or reinstalling the repo). Users saw
-  `/mcp` report "Failed to reconnect" with no diagnostic hint.
-  The installer now classifies entries whose `args[0]` is missing as
-  **stale** and rewrites them automatically without `--force`, preserving
-  `SYM_NODE_NAME` from the prior entry so mesh identity doesn't drift
-  back to the hostname-based default. Live entries continue to require
-  `--force` for overwrite.
-- **Stale project-scoped entries are now healed too.** `~/.claude.json`
-  can carry per-project `mcpServers` overrides under
-  `projects.<dir>.mcpServers`, and Claude Code prefers those over the
-  user-global entry when launched from that directory. A healthy
-  user-global entry was therefore being silently shadowed by stale
-  project entries. `init` now scans every project, rewrites any stale
-  `claude-sym-mesh` entry, and preserves each project's `SYM_NODE_NAME`.
-### Added
-- **`sym-mesh-channel doctor` subcommand.** Read-only diagnostic that
-  lists every `claude-sym-mesh` entry in `~/.claude.json` (user-global
-  and every project scope) with `[live]` or `[STALE]` plus its
-  `SYM_NODE_NAME` and configured path. Point users here when `/mcp`
-  reports "Failed to reconnect". No writes, safe to run any time.
-- **README troubleshooting section** covering the `/mcp` failure path,
-  how to run `doctor`, and when restart is needed after a config change.
-### Changed
-- `.claude-plugin/plugin.json` version field bumped to `0.3.1` to match
-  `package.json`. Previous drift (`plugin.json` stuck at `0.2.0`, package
-  at `0.3.0`) was caught by the in-repo version-parity test.
-## 0.3.0
-### Added
-- **Startup remix-memory primer — automates agent memory recall on
-  session/agent restart (MMP §4.2 O2, rejoin-without-replay).** As the
-  final step of plugin initialisation (after `node.start()` and before
-  the MCP transport connects), the plugin calls
-  `node.buildStartupPrimer()` and appends the returned text to the MCP
-  server's `instructions` field. A fresh Claude Code session wakes
-  with the agent's own remix memory — own observations plus peer
-  observations admitted by SVAF — already loaded into context. No
-  first-turn `sym_recall` required; agent acts from prior state
-  immediately.
-  Default caps: last 24 hours OR 20 most recent CMBs, whichever is
-  tighter. The primer lists each entry as `[timestamp] source · key —
-  focus` and surfaces a dropped-count line when caps elide older
-  entries. Empty store is a silent no-op.
-### Changed
-- **`@sym-bot/sym` dep bumped to `^0.5.0`** to pick up the
-  `buildStartupPrimer` helper and to keep every plugin on the
-  sym.day platform pinned to the same substrate SDK version
-  (no drift across mesh-channel / melotune-plugin / future
-  specialised plugins).
-## 0.2.0
-### Breaking
-- **`sym_send` tool signature change.** `sym_send` now emits a structured
-  CAT7 CMB (MMP §4.2) instead of a raw-text `type:'message'` frame, and
-  accepts an optional `to` parameter for targeted single-peer delivery
-  per MMP §4.4.4.
-  Old signature: `sym_send(message: string)`
-  New signature: `sym_send(focus: string (required), issue?, intent?,
-  motivation?, commitment?, perspective?, mood?, to?)`
-  Migration: agents that previously called `sym_send({message: "..."})`
-  should now pass the CAT7 fields explicitly, with `focus` carrying the
-  task anchor for the send. Prior ephemeral text-broadcast behaviour is
-  no longer exposed at the tool surface — `sym_send` and `sym_observe`
-  both emit CMBs now, receivers run SVAF per §9.2, and admitted CMBs are
-  remix-stored with lineage. The low-level `node.send(text)` SDK API is
-  unchanged but no longer surfaced as a tool.
-### Added
-- **Targeted CMB send.** `sym_send` resolves `to` against connected
-  peers by full nodeId first, then display name, then 8-char prefix.
-  Ambiguous matches return an error asking for the full nodeId; a
-  disconnected target returns an error and suggests `sym_peers`.
-- **Tool descriptions** for `sym_send` and `sym_observe` now explicitly
-  call out the SVAF receive path and lineage semantics, and the MCP
-  server's `instructions` string reflects the new division of labour.
-- **`@sym-bot/sym` dependency bumped to `^0.3.81`** for
-  `remember(fields, {to})` targeted variant and `peers().peerId`.
-## 0.1.23
-### Added
-- **`sym_join_group(group, relay_url?, relay_token?)`** — hot-swap this
-  node into a different mesh group at runtime, no Claude Code restart.
-  Stops the current SymNode, reconstructs it on the new service type
-  (and optional relay), re-registers event handlers, restarts. The
-  "smooth way to join" that was missing in 0.1.22.
-- **`sym_invite_create(group, relay_url?, relay_token?)`** — generate
-  a shareable invite URL for a named group. Two flavors:
-  - LAN-only: `sym://group/{name}` (Bonjour isolation only)
-  - Cross-network: `sym://team/{name}?relay=...&token=...` (routes via
-    a WebSocket relay so teammates on different networks can join).
-  Validates kebab-case group names, rejects token without URL.
-- **`sym_invite_info(url)`** extended to parse the new `sym://team/`
-  path and the `relay=` + `token=` query-string parameters.
-  Output now includes a ready-to-paste `sym_join_group` call as JSON.
-- **`sym_groups_discover()`** — enumerate SYM-mesh groups currently
-  advertising on the local LAN via Bonjour / mDNS. Shell-outs to
-  `dns-sd` (macOS/Windows) or `avahi-browse` (Linux) with a 2-second
-  timeout, filters to service types matching the SYM protocol family
-  (global `_sym._tcp`, named groups, `{app}-{id}` rooms). Peer-to-peer
-  means only groups with live members right now are visible — no
-  central directory.
-- **README — "Dev-team groups" walkthrough** with two concrete scenarios:
-  LAN dev-team group (single office) and cross-network team group via
-  the public `wss://sym-relay.onrender.com` relay. Shows exact tool
-  calls from both the team lead and each teammate.
-- **13 new tests** covering invite URL parse, generate, round-trip, and
-  validation (kebab-case, token-requires-URL guard). Test suite now at
-  35 tests total.
-### Changed
-- Module-level `node`, `GROUP`, `SERVICE_TYPE`, `RELAY_URL`,
-  `RELAY_TOKEN` declared as `let` (was `const`) so the hot-swap path
-  can re-bind them. All node event handlers (`identity-collision`,
-  `cmb-accepted`, `message`) extracted into a single
-  `registerNodeHandlers(n)` function so the hot-swap path re-attaches
-  them without duplicating logic.
-- Tool count in README corrected to 11 (was 8 in 0.1.22):
-  + sym_invite_create, sym_join_group, sym_groups_discover.
-## 0.1.22
-### Added
-- **Plugin marketplace distribution**: `.claude-plugin/marketplace.json`
-  enables direct install via the Claude Code plugin marketplace without
-  waiting on the Anthropic Plugin Directory propagation pipeline:
-  ```
-  /plugin marketplace add sym-bot/sym-mesh-channel
-  /plugin install sym-mesh-channel@sym-mesh-channel
-  ```
-  Validates cleanly with `claude plugin validate .` and installs
-  end-to-end with no manual steps.
-- **`LICENSE`** file (Apache-2.0). `package.json` already declared
-  Apache-2.0 but no LICENSE text was present in the repo; this
-  aligns the distribution with SPDX expectations.
-- **MMP §5.8 mesh-group support** — LAN isolation via Bonjour service
-  type so Claude Code sessions can join app-specific meshes (e.g.
-  MeloTune mood rooms on `_melotune._tcp`) instead of the global
-  `_sym._tcp` mesh. Enables cross-app CMB delivery without cross-app
-  noise: nodes in different groups never discover each other at mDNS.
-  Config surface (two equivalent paths):
-  - `SYM_GROUP=<name>`       → service type `_<name>._tcp`
-  - `SYM_SERVICE_TYPE=<st>`  → explicit override (`_foo._tcp` form)
-  Default remains `_sym._tcp` / `group=default` — backward compatible.
-- **Two new MCP tools for mesh-group operations**:
-  - `sym_group_info` — reports current group + service type + peer
-    roster scoped to this group.
-  - `sym_invite_info` — parses app-specific invite URLs
-    (`melotune://room/{id}/{name}`, `sym://group/{name}`) into service
-    type + group + room name. Read-only inspection; caller opens a
-    new session/env to join.
-  `sym_status` output now includes `Group` + service type.
-### Fixed
-- **`plugin.json` validation failure on install.** The three
-  `channels[0].userConfig` entries (`relay_url`, `relay_token`,
-  `allowed_peers`) were missing the required `type` and `title`
-  fields per the Claude Code plugin schema. Install failed with:
-  ```
-  channels.0.userConfig.relay_url.type: Invalid option
-  channels.0.userConfig.relay_url.title: expected string, received undefined
-  ```
-  Added `type: "string"` and a human-readable `title` to all three.
-  Likely one of the root causes of the 10 Apr 2026 submission
-  showing "Published" on the Anthropic submissions portal but not
-  propagating to the public `claude-plugins-official` marketplace.
-### Changed
-- **README**: self-hosted plugin-marketplace install path promoted to
-  the primary install recommendation (works today, independent of
-  Anthropic directory propagation). npm path kept as alternative.
-  Tool table updated 5 → 8 entries to reflect the current surface.
-  Clarified that plugin-directory approval and Channels-allowlist
-  inclusion are independent gates — the MCP tools work without the
-  `--dangerously-load-development-channels` flag; the flag is only
-  needed for the `<channel>` async-push behaviour.
-- Pairs with `@sym-bot/sym` ≥ 0.3.78 which added the
-  `discoveryServiceType` and `group` constructor params consumed by
-  the mesh-group tools.
-## 0.1.21
-### Changed
-- **README: accurate `sym_status` / `sym_peers` example output.** The
-  Quick Start sample output was a stylized one-line compression; the
-  real output is multi-line with additional fields (nodeId suffix,
-  Relay, Memories, one peer per line). Updated so users see in the
-  README exactly what their terminal will show. Doc-only — no code
-  changes.
-## 0.1.20
-### Added
-- **`sym-mesh-channel init --project`** — new flag to install the MCP
-  server at project scope (`<cwd>/.mcp.json` + merged
-  `<cwd>/.claude/settings.local.json`) instead of global
-  `~/.claude.json`. Enables multi-identity-per-machine workflows where
-  several Claude Code sessions run in parallel from distinct project
-  directories and each appears as its own peer on the mesh. Project
-  `.mcp.json` entries override the global `mcpServers` entry when
-  Claude Code launches from that directory, so `SYM_NODE_NAME` can
-  differ per project without siblings stepping on each other.
-- Project mode supports the same `--force` semantics as global install:
-  backs up existing `.mcp.json` and `settings.local.json` next to
-  themselves (`*.bak-<timestamp>`), merges `settings.local.json` so
-  unrelated keys (permissions, custom settings) are preserved, atomic
-  writes via tmp+rename, refuses to overwrite an existing
-  `claude-sym-mesh` entry without `--force`.
-- `--postinstall` always runs global install regardless of `--project`
-  (npm postinstall runs from npm's staging dir, not the user's
-  project). Keeps `npm install -g` auto-configure behavior unchanged.
-- **5 new tests** covering project-mode install: writes `.mcp.json`
-  and `settings.local.json`, merge preserves existing keys, refusal
-  path exits 2, `--force` overwrite creates backup, postinstall
-  fallback ignores `--project`. Test suite now 22 tests total.
-### Why
-Default mode (single mesh identity per machine, global install) is
-correct for most users and unchanged. `--project` exists for the
-small but real set of users who run multiple Claude Code sessions
-in parallel from distinct project directories and want each session
-to show up as its own peer on the mesh. Previously this workflow
-required hand-editing `.mcp.json` and `.claude/settings.local.json`
-per project; now it's one command per project.
-## 0.1.19
-### Added
-- **Claude Code plugin manifest** for Anthropic Channels allowlist
-  submission. `.claude-plugin/plugin.json` + `.mcp.json` following the
-  official single-repo pattern (Telegram/Discord). Submitted to
-  Anthropic Plugin Directory 10 Apr 2026.
-- **`SYM_ALLOWED_PEERS`** — optional peer allowlist (defense-in-depth).
-  Comma-separated node names; only listed peers can push to Claude's
-  context. Empty = accept all authenticated peers. SVAF still gates on
-  content relevance regardless.
-- **`SECURITY.md`** — 3-layer defense model documentation (transport
-  auth + SVAF content gate + peer allowlist) for Anthropic review.
-- **17 plugin tests** covering manifest validation, security checks
-  (no permission relay, no code execution, self-echo filtering, peer
-  allowlist), and lifecycle (shutdown handlers, identity collision).
-## 0.1.18
-### Changed
-- **Auto-configure on install.** `npm install -g` now runs `postinstall`
-  that writes the MCP server config to global `mcpServers` in
-  `~/.claude.json` automatically. No separate `sym-mesh-channel init`
-  step needed — two commands to mesh: install + launch.
-- **Global MCP config** — server entry is now written to top-level
-  `mcpServers` (available in all Claude Code sessions), not
-  project-scoped.
-- **Windows postinstall fixes** — `require.resolve` for server.js path
-  (handles npm staging directory on Windows), EBUSY handling when
-  Claude Code has `~/.claude.json` locked, graceful skip if Claude
-  Code not yet installed.
-- **README repositioned** — lead with capability ("first non-Anthropic
-  Claude Code Channels implementation"), not use case. Simplified
-  Quick Start to two commands.
-- **0 vulnerabilities** — fresh dependency rebuild resolves all 6
-  moderate hono/node-server advisories.
-- Windows mDNS: built-in on Windows 10+, no Bonjour install needed.
-## 0.1.7
-### Added
-- **`npx @sym-bot/mesh-channel init`** — interactive installer that
-  writes `~/.claude.json` for the current project, picks a sensible
-  default `SYM_NODE_NAME` (`claude-mac` / `claude-win` / `claude-linux`),
-  resolves the absolute path to `server.js`, and prints the launch
-  command including the `--dangerously-load-development-channels` flag.
-  Backs up the existing config to `~/.claude.json.bak-<timestamp>`,
-  validates JSON round-trip, atomic write via tmp+rename. Refuses to
-  overwrite an existing entry without `--force`.
-- **README rewritten for LAN-first install.** Quick start is two
-  minutes: install, init, launch. No relay required. Bonjour/mDNS
-  is the default discovery path. Cross-network setup (relay) is now
-  the optional advanced section.
-### Changed
-- `package.json` `bin` now exposes both `sym-mesh-channel` (server
-  entrypoint) and `sym-mesh-channel-init` (installer). The package
-  description leads with "LAN-first via Bonjour, no relay required."
-### Why
-The 0.1.5/0.1.6 install path required users to manually edit
-`~/.claude.json`, know about the Channels dev flag, set up a relay,
-and obtain a relay token. That gated the demo behind real friction.
-LAN-only mode has worked since day one in the underlying SymNode
-(`sym/lib/node.js:509-511` only connects to the relay if `SYM_RELAY_URL`
-is set; Bonjour discovery starts unconditionally), but no documentation
-or installer surfaced it. This release closes that gap: two users on
-the same wifi can join the same mesh in two minutes with three commands.
-## 0.1.6
-### Fixed
-- `sym_send` no longer double-delivers. Previously called both
-  `node.send()` (broadcast as `event_type=message`) AND `node.remember()`
-  (persist as CMB which gets gossiped as `event_type=cmb`), causing
-  the same payload to arrive twice on receivers and double the
-  context-window cost. Now broadcasts the message frame only. Hosts
-  that want CMB persistence should call `sym_observe` separately
-  with proper CAT7 fields.
-- `sym_send` now reports the actual delivered count, not
-  `peers().length`. Requires `@sym-bot/sym >= 0.3.70` where `send()`
-  returns the count of peer transports that successfully accepted
-  the broadcast. The two can disagree when peers are tracked but
-  have broken transports — the delivered count is the truth about
-  what was actually sent.
-### Changed
-- Bumped `@sym-bot/sym` dep `^0.3.69` → `^0.3.70`. 0.3.70 ships the
-  identity lockfile that prevents two SymNode processes from
-  claiming the same nodeId on a host (the cliHostMode-vs-MCP
-  collision that broke real-time push on Windows during the
-  2026-04-09 round-trip test).
-## 0.1.5
-### Changed
-- Bumped `@sym-bot/sym` dep `^0.3.68` → `^0.3.69` (0.3.68 deprecated;
-  same code in 0.3.69 with a cleaner published tarball).
-- Added `files` whitelist to `package.json` and `.npmignore` for
-  `*.bak`, `*.swp`, `.DS_Store` so future publishes can't accidentally
-  ship local backup files. First NPM publish of this package.
-## 0.1.4
-### Changed
-- Bumped `@sym-bot/sym` dep `^0.3.43` → `^0.3.68` to pick up
-  duplicate-identity refusal (close code 4004) and the new
-  `identity-collision` event.
-### Added
-- Wired `node.on('identity-collision', ...)` to `process.exit(2)` so
-  the MCP dies cleanly when the relay reports a duplicate-identity
-  race. Together with v0.1.3's clean shutdown, this fully resolves
-  the host-side half of the duplicate-identity bug.
-## 0.1.3
-### Added
-- Clean shutdown handlers (SIGTERM/SIGINT/SIGHUP) that call
-  `node.stop()` before exiting, so the SymNode disconnects from the
-  relay before the process dies. Without this, restarts left zombie
-  registrations on the relay until the next heartbeat tick (up to
-  30s), creating a duplicate-identity race window for the next MCP
-  spawn. Idempotent re-entry guard.
-## 0.1.2
-### Fixed
-- Suppressed `peer-joined` / `peer-left` events from being pushed to
-  Claude's context as `<channel>` notifications. Presence is high-
-  frequency and low-signal — a relay reconnect could fire one event
-  per peer per cycle, flooding the context window. CMBs and direct
-  messages still flow through.
-## 0.1.1
-### Changed
-- Replaced hardcoded `claude-code` / `claude-code-mac` literals with
-  a single `NODE_NAME` constant sourced from `process.env.SYM_NODE_NAME`
-  (default `claude-code-mac`). Enables platform-scoped naming per
-  MMP §3.1.2 without source edits. Fixed stale display strings in
-  the MCP instructions, `sym_send` perspective, `sym_status` header,
-  and the self-echo dedup filter.
-## 0.1.0
-### Added
-- Initial release. MCP server that runs a `SymNode` peer node inside
-  a Claude Code session — own identity, own relay connection, own
-  SVAF evaluation. Tools: `sym_send`, `sym_observe`, `sym_recall`,
-  `sym_peers`, `sym_status`. Mesh events arrive as `<channel>`
-  notifications when launched with
-  `claude --dangerously-load-development-channels server:claude-sym-mesh`
-  (allowlisted server name required by Claude Code Channels).
+# Changelog
+## 0.3.14
+### Added
+- **`sym-mesh-channel start` — one command to a live mesh session.** Configures the MCP server if needed, then launches Claude Code with the real-time Channels flag already on, so users never type `--dangerously-load-development-channels …` or have to choose between the `plugin:` and `server:` handle. `start --project --name <node> --group <team>` stands up a named mesh agent; `start --print` is a dry run; everything after `--` is forwarded to `claude`. Co-resident sessions don't collide (server.js auto-suffixes a live-identity clash since 0.3.10), so `start` in several terminals just works.
+### Fixed
+- **CLI subcommand dispatch via the published bin.** The `bin` entrypoint (`server.js`) only routed `init` to the installer, so `npx @sym-bot/mesh-channel doctor` silently fell through and started the MCP server instead. Now `init`, `doctor`, and `start` all route to the installer/launcher.
+- **`init --force` with an explicit `SYM_NODE_NAME` now relabels the entry** instead of always preserving the prior name (symmetric with how `--group` already behaves). A routine reinstall with no explicit name still preserves identity.
+## 0.3.13
+### Changed
+- **Track the latest released `@sym-bot/sym` (`^0.7.6`).** Pulls in the SVAF decision log (every evaluation — admit and reject — is now persisted and emitted) on top of the 0.7.5 replay-storm receive-path dedup. Additive; no API changes in mesh-channel.
+## 0.3.12
+### Changed
+- **Bump `@sym-bot/sym` to `^0.7.5`** — mesh replay-storm receive-path dedup (dedup received CMBs so a co-resident peer restart no longer triggers a replay storm).
+### Fixed
+- Align install commands + channel-flag handles with the actual marketplace (#13).
+- Fix 5 moderate Dependabot vulnerabilities (`npm audit fix`).
+## 0.3.11
+### Added
+- **Prompt-injection filter (security layer 3).** Every incoming CMB — all CAT7 fields and the opaque payload — is now scanned against a curated blocklist of injection patterns before `pushChannel()` is called. Patterns cover: instruction-override phrases ("ignore previous instructions", "forget everything you know"), role/persona hijacking ("you are now a new AI", "act as an unrestricted assistant"), system-prompt injection (`<system>`, `[SYSTEM]`, `## system prompt`), tool-call fabrication (`<tool_call>`, `<function_calls>`), and privilege-escalation language ("override safety filter", "jailbreak", "DAN mode"). Blocked CMBs are audit-logged to stderr with reason, peer name, and a truncated excerpt — never silently dropped.
+- **Per-peer rate limiting.** A sliding 60-second window caps each peer at `SYM_RATE_LIMIT` CMBs per minute (default: 30). CMBs exceeding the cap are blocked and audit-logged. Prevents flood attacks from a compromised or malfunctioning peer.
+- **Payload size cap.** Payloads larger than `SYM_MAX_PAYLOAD_BYTES` (default: 8 192 bytes) are rejected before context injection. Prevents oversized-payload attacks that could exhaust the context window.
+- **README security section updated** to document all four defence layers accurately.
+### Security model
+The full gate before any mesh signal reaches Claude's context is now:
+1. **Transport** — Ed25519 peer identity + relay-token auth.
+2. **Protocol** — SVAF per-field semantic relevance gate.
+3. **Safety** — prompt-injection filter + rate limiter + payload size cap (this release).
+4. **Application** — text-only injection; `claude/channel/permission` not declared.
+## 0.3.10
+### Fixed
+- **Live-identity-collision auto-suffix.** Two sessions wanting the same `SYM_NODE_NAME` previously hard-failed with `EIDENTITYLOCK`. The server now checks whether the name's lock file is held by a live process; if so, it appends `-2`, `-3`, … (up to 64) until it finds a free slot. Stale locks (dead holder) are still reclaimed by `@sym-bot/sym` on start — unchanged. Result: duplicate dev-agent sessions, or any two sessions sharing a fixed `SYM_NODE_NAME`, coexist instead of failing.
+## 0.3.9
+### Fixed
+- **stdout discipline — fixes `-32000 / Connection closed`.** The MCP JSON-RPC stream runs on stdout. Dependency load banners (e.g. `[encoder] Semantic encoder ready` from the semantic model) were printing to stdout, intermittently corrupting the handshake and causing Claude Code to log "Ignoring non-JSON line on stdout" or drop the connection with `-32000`. A stdout guard is now installed before any `require()`: lines that start with `{` (JSON-RPC frames) pass through to the real stdout; everything else is redirected to stderr. Verified: stdout is pure JSON after the fix.
+## 0.3.8
+### Added
+- **Per-session node identity.** Each Claude Code session now gets its own mesh identity derived from the working-directory slug and a session-unique suffix (e.g. `claude-symday-webapp-6e174e`), instead of all sessions sharing the machine hostname. Enables multiple Claude Code sessions on the same machine to appear as distinct peers on the mesh — confirmed working over loopback via Bonjour with no relay.
+- **`npx` launch path.** The plugin now launches via `npx @sym-bot/mesh-channel` rather than a global `node` path, so marketplace installs work without a prior `npm install -g`. The npx cache warms on first launch; subsequent sessions start in ~1 s.
+## 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
+- **Opaque payload on `sym_send` / `sym_observe`.** Both tools accept
+  an optional `payload` argument carrying data beyond CAT7 — any
+  JSON-serializable value. Forwarded to `SymNode.remember(fields, {
+  payload, … })` (requires `@sym-bot/sym` ≥ 0.5.8) and rides the wire
+  frame to peers. Used by substrate-level protocols that need to carry
+  structured data alongside CAT7 (e.g. LLM request/response, where the
+  prompt + request_id ride in `payload` rather than getting smuggled
+  through `motivation`).
+- **Channel notifications surface payload-bearing CMBs.** When an
+  incoming peer CMB carries `cmb.payload`, the header gains a
+  `[+payload Nb]` indicator and the body stored by `sym_fetch`
+  includes a `---PAYLOAD---` section with the serialized payload.
+  Receivers learn from the header that there's structured data beyond
+  CAT7 and call `sym_fetch` to consume it.
+- Base MCP instructions now teach agents to recognise the
+  `[+payload Nb]` header and to pass structured responses via the
+  `payload` argument when emitting substrate-level CMBs.
+### Compatibility
+- Omitting `payload` produces a v0.3.4-shaped CAT7 CMB byte-for-byte.
+- Old peers (without `cmb.payload`) surface unchanged headers — no
+  `[+payload …]` indicator, no PAYLOAD section in the body.
+## 0.3.4
+### Added
+- **`SYM_GROUP` is now first-class in the installer.** `init` accepts a
+  `--group <name>` flag and reads the `SYM_GROUP` env var; both paths
+  persist the chosen group into the `~/.claude.json` (or project
+  `.mcp.json`) env block so every Claude Code launch auto-joins the
+  named group instead of the global `_sym._tcp` mesh.
+  Resolution order is `--force`-aware:
+    - With `--force` and an explicit `--group`/`SYM_GROUP`: flag/env wins
+      (one-command group switch on a live entry).
+    - Without `--force`, or with `--force` but no explicit value:
+      preserved value from any existing entry > explicit > none (omit).
+  `--force --group default` (or `SYM_GROUP=default`) is the explicit
+  escape hatch to revert a node from a named group back to the global
+  mesh — removes `SYM_GROUP` from the env block entirely rather than
+  writing the literal string "default".
+  Both `--group` and `SYM_GROUP` env values are validated against the
+  same kebab-case regex; malformed values exit with a clear error
+  before any file write.
+- **`doctor` now reports the persisted group per entry** and warns when
+  user-global and project-scoped entries disagree on `SYM_GROUP`.
+  Group-mismatch is the most common cause of "peers never appear in
+  `sym_peers`" with no other failure signal — surfacing it inline saves
+  the diagnostic walk that motivated this release.
+- **README** gains a "Persisting your group across restarts" subsection
+  under Team mesh groups, plus a troubleshooting entry covering the
+  group-mismatch failure mode. Quick-start shows the `--group` flag.
+### Fixed
+- **Stale-entry heal preserves `SYM_GROUP` alongside `SYM_NODE_NAME`.**
+  Previously, healing a stale `claude-sym-mesh` entry (args[0] points at
+  a missing server.js) silently dropped any persisted `SYM_GROUP`,
+  reverting the node to the default mesh on next launch and stranding
+  teammates who stayed in the named group. The heal path now copies
+  both fields from the prior entry into the rewrite.
+  Same fix applied to project-scoped entry healing under
+  `claudeJson.projects[<path>].mcpServers`.
+### Why this matters
+Before 0.3.4, the only way to persist a group was to hand-edit
+`~/.claude.json`. The README pitched `sym_join_group` as the team-mesh
+UX, but that tool is runtime-only — the next Claude Code launch reverted
+the node to the default mesh, peer count dropped to zero, and the user
+saw no diagnostic signal. The 2026-05-02 SYM.BOT incident (CMO in
+`default`, COO in `sym-bot-team`, ~24h of silent duplex outage) traced
+directly to this gap.
+## 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
+- **Installer no longer silently ships a broken MCP config.** Previously,
+  if `~/.claude.json` already contained a `claude-sym-mesh` entry,
+  `npm install -g @sym-bot/mesh-channel` (via postinstall) and
+  `npx @sym-bot/mesh-channel init` both skipped with "already configured"
+  — even when the entry's `args[0]` server.js path no longer existed on
+  disk (common after moving or reinstalling the repo). Users saw
+  `/mcp` report "Failed to reconnect" with no diagnostic hint.
+  The installer now classifies entries whose `args[0]` is missing as
+  **stale** and rewrites them automatically without `--force`, preserving
+  `SYM_NODE_NAME` from the prior entry so mesh identity doesn't drift
+  back to the hostname-based default. Live entries continue to require
+  `--force` for overwrite.
+- **Stale project-scoped entries are now healed too.** `~/.claude.json`
+  can carry per-project `mcpServers` overrides under
+  `projects.<dir>.mcpServers`, and Claude Code prefers those over the
+  user-global entry when launched from that directory. A healthy
+  user-global entry was therefore being silently shadowed by stale
+  project entries. `init` now scans every project, rewrites any stale
+  `claude-sym-mesh` entry, and preserves each project's `SYM_NODE_NAME`.
+### Added
+- **`sym-mesh-channel doctor` subcommand.** Read-only diagnostic that
+  lists every `claude-sym-mesh` entry in `~/.claude.json` (user-global
+  and every project scope) with `[live]` or `[STALE]` plus its
+  `SYM_NODE_NAME` and configured path. Point users here when `/mcp`
+  reports "Failed to reconnect". No writes, safe to run any time.
+- **README troubleshooting section** covering the `/mcp` failure path,
+  how to run `doctor`, and when restart is needed after a config change.
+### Changed
+- `.claude-plugin/plugin.json` version field bumped to `0.3.1` to match
+  `package.json`. Previous drift (`plugin.json` stuck at `0.2.0`, package
+  at `0.3.0`) was caught by the in-repo version-parity test.
+## 0.3.0
+### Added
+- **Startup remix-memory primer — automates agent memory recall on
+  session/agent restart (MMP §4.2 O2, rejoin-without-replay).** As the
+  final step of plugin initialisation (after `node.start()` and before
+  the MCP transport connects), the plugin calls
+  `node.buildStartupPrimer()` and appends the returned text to the MCP
+  server's `instructions` field. A fresh Claude Code session wakes
+  with the agent's own remix memory — own observations plus peer
+  observations admitted by SVAF — already loaded into context. No
+  first-turn `sym_recall` required; agent acts from prior state
+  immediately.
+  Default caps: last 24 hours OR 20 most recent CMBs, whichever is
+  tighter. The primer lists each entry as `[timestamp] source · key —
+  focus` and surfaces a dropped-count line when caps elide older
+  entries. Empty store is a silent no-op.
+### Changed
+- **`@sym-bot/sym` dep bumped to `^0.5.0`** to pick up the
+  `buildStartupPrimer` helper and to keep every plugin on the
+  sym.day platform pinned to the same substrate SDK version
+  (no drift across mesh-channel / melotune-plugin / future
+  specialised plugins).
+## 0.2.0
+### Breaking
+- **`sym_send` tool signature change.** `sym_send` now emits a structured
+  CAT7 CMB (MMP §4.2) instead of a raw-text `type:'message'` frame, and
+  accepts an optional `to` parameter for targeted single-peer delivery
+  per MMP §4.4.4.
+  Old signature: `sym_send(message: string)`
+  New signature: `sym_send(focus: string (required), issue?, intent?,
+  motivation?, commitment?, perspective?, mood?, to?)`
+  Migration: agents that previously called `sym_send({message: "..."})`
+  should now pass the CAT7 fields explicitly, with `focus` carrying the
+  task anchor for the send. Prior ephemeral text-broadcast behaviour is
+  no longer exposed at the tool surface — `sym_send` and `sym_observe`
+  both emit CMBs now, receivers run SVAF per §9.2, and admitted CMBs are
+  remix-stored with lineage. The low-level `node.send(text)` SDK API is
+  unchanged but no longer surfaced as a tool.
+### Added
+- **Targeted CMB send.** `sym_send` resolves `to` against connected
+  peers by full nodeId first, then display name, then 8-char prefix.
+  Ambiguous matches return an error asking for the full nodeId; a
+  disconnected target returns an error and suggests `sym_peers`.
+- **Tool descriptions** for `sym_send` and `sym_observe` now explicitly
+  call out the SVAF receive path and lineage semantics, and the MCP
+  server's `instructions` string reflects the new division of labour.
+- **`@sym-bot/sym` dependency bumped to `^0.3.81`** for
+  `remember(fields, {to})` targeted variant and `peers().peerId`.
+## 0.1.23
+### Added
+- **`sym_join_group(group, relay_url?, relay_token?)`** — hot-swap this
+  node into a different mesh group at runtime, no Claude Code restart.
+  Stops the current SymNode, reconstructs it on the new service type
+  (and optional relay), re-registers event handlers, restarts. The
+  "smooth way to join" that was missing in 0.1.22.
+- **`sym_invite_create(group, relay_url?, relay_token?)`** — generate
+  a shareable invite URL for a named group. Two flavors:
+  - LAN-only: `sym://group/{name}` (Bonjour isolation only)
+  - Cross-network: `sym://team/{name}?relay=...&token=...` (routes via
+    a WebSocket relay so teammates on different networks can join).
+  Validates kebab-case group names, rejects token without URL.
+- **`sym_invite_info(url)`** extended to parse the new `sym://team/`
+  path and the `relay=` + `token=` query-string parameters.
+  Output now includes a ready-to-paste `sym_join_group` call as JSON.
+- **`sym_groups_discover()`** — enumerate SYM-mesh groups currently
+  advertising on the local LAN via Bonjour / mDNS. Shell-outs to
+  `dns-sd` (macOS/Windows) or `avahi-browse` (Linux) with a 2-second
+  timeout, filters to service types matching the SYM protocol family
+  (global `_sym._tcp`, named groups, `{app}-{id}` rooms). Peer-to-peer
+  means only groups with live members right now are visible — no
+  central directory.
+- **README — "Dev-team groups" walkthrough** with two concrete scenarios:
+  LAN dev-team group (single office) and cross-network team group via
+  the public `wss://sym-relay.onrender.com` relay. Shows exact tool
+  calls from both the team lead and each teammate.
+- **13 new tests** covering invite URL parse, generate, round-trip, and
+  validation (kebab-case, token-requires-URL guard). Test suite now at
+  35 tests total.
+### Changed
+- Module-level `node`, `GROUP`, `SERVICE_TYPE`, `RELAY_URL`,
+  `RELAY_TOKEN` declared as `let` (was `const`) so the hot-swap path
+  can re-bind them. All node event handlers (`identity-collision`,
+  `cmb-accepted`, `message`) extracted into a single
+  `registerNodeHandlers(n)` function so the hot-swap path re-attaches
+  them without duplicating logic.
+- Tool count in README corrected to 11 (was 8 in 0.1.22):
+  + sym_invite_create, sym_join_group, sym_groups_discover.
+## 0.1.22
+### Added
+- **Plugin marketplace distribution**: `.claude-plugin/marketplace.json`
+  enables direct install via the Claude Code plugin marketplace without
+  waiting on the Anthropic Plugin Directory propagation pipeline:
+  ```
+  /plugin marketplace add sym-bot/sym-mesh-channel
+  /plugin install sym-mesh-channel@sym-mesh-channel
+  ```
+  Validates cleanly with `claude plugin validate .` and installs
+  end-to-end with no manual steps.
+- **`LICENSE`** file (Apache-2.0). `package.json` already declared
+  Apache-2.0 but no LICENSE text was present in the repo; this
+  aligns the distribution with SPDX expectations.
+- **MMP §5.8 mesh-group support** — LAN isolation via Bonjour service
+  type so Claude Code sessions can join app-specific meshes (e.g.
+  MeloTune mood rooms on `_melotune._tcp`) instead of the global
+  `_sym._tcp` mesh. Enables cross-app CMB delivery without cross-app
+  noise: nodes in different groups never discover each other at mDNS.
+  Config surface (two equivalent paths):
+  - `SYM_GROUP=<name>`       → service type `_<name>._tcp`
+  - `SYM_SERVICE_TYPE=<st>`  → explicit override (`_foo._tcp` form)
+  Default remains `_sym._tcp` / `group=default` — backward compatible.
+- **Two new MCP tools for mesh-group operations**:
+  - `sym_group_info` — reports current group + service type + peer
+    roster scoped to this group.
+  - `sym_invite_info` — parses app-specific invite URLs
+    (`melotune://room/{id}/{name}`, `sym://group/{name}`) into service
+    type + group + room name. Read-only inspection; caller opens a
+    new session/env to join.
+  `sym_status` output now includes `Group` + service type.
+### Fixed
+- **`plugin.json` validation failure on install.** The three
+  `channels[0].userConfig` entries (`relay_url`, `relay_token`,
+  `allowed_peers`) were missing the required `type` and `title`
+  fields per the Claude Code plugin schema. Install failed with:
+  ```
+  channels.0.userConfig.relay_url.type: Invalid option
+  channels.0.userConfig.relay_url.title: expected string, received undefined
+  ```
+  Added `type: "string"` and a human-readable `title` to all three.
+  Likely one of the root causes of the 10 Apr 2026 submission
+  showing "Published" on the Anthropic submissions portal but not
+  propagating to the public `claude-plugins-official` marketplace.
+### Changed
+- **README**: self-hosted plugin-marketplace install path promoted to
+  the primary install recommendation (works today, independent of
+  Anthropic directory propagation). npm path kept as alternative.
+  Tool table updated 5 → 8 entries to reflect the current surface.
+  Clarified that plugin-directory approval and Channels-allowlist
+  inclusion are independent gates — the MCP tools work without the
+  `--dangerously-load-development-channels` flag; the flag is only
+  needed for the `<channel>` async-push behaviour.
+- Pairs with `@sym-bot/sym` ≥ 0.3.78 which added the
+  `discoveryServiceType` and `group` constructor params consumed by
+  the mesh-group tools.
+## 0.1.21
+### Changed
+- **README: accurate `sym_status` / `sym_peers` example output.** The
+  Quick Start sample output was a stylized one-line compression; the
+  real output is multi-line with additional fields (nodeId suffix,
+  Relay, Memories, one peer per line). Updated so users see in the
+  README exactly what their terminal will show. Doc-only — no code
+  changes.
+## 0.1.20
+### Added
+- **`sym-mesh-channel init --project`** — new flag to install the MCP
+  server at project scope (`<cwd>/.mcp.json` + merged
+  `<cwd>/.claude/settings.local.json`) instead of global
+  `~/.claude.json`. Enables multi-identity-per-machine workflows where
+  several Claude Code sessions run in parallel from distinct project
+  directories and each appears as its own peer on the mesh. Project
+  `.mcp.json` entries override the global `mcpServers` entry when
+  Claude Code launches from that directory, so `SYM_NODE_NAME` can
+  differ per project without siblings stepping on each other.
+- Project mode supports the same `--force` semantics as global install:
+  backs up existing `.mcp.json` and `settings.local.json` next to
+  themselves (`*.bak-<timestamp>`), merges `settings.local.json` so
+  unrelated keys (permissions, custom settings) are preserved, atomic
+  writes via tmp+rename, refuses to overwrite an existing
+  `claude-sym-mesh` entry without `--force`.
+- `--postinstall` always runs global install regardless of `--project`
+  (npm postinstall runs from npm's staging dir, not the user's
+  project). Keeps `npm install -g` auto-configure behavior unchanged.
+- **5 new tests** covering project-mode install: writes `.mcp.json`
+  and `settings.local.json`, merge preserves existing keys, refusal
+  path exits 2, `--force` overwrite creates backup, postinstall
+  fallback ignores `--project`. Test suite now 22 tests total.
+### Why
+Default mode (single mesh identity per machine, global install) is
+correct for most users and unchanged. `--project` exists for the
+small but real set of users who run multiple Claude Code sessions
+in parallel from distinct project directories and want each session
+to show up as its own peer on the mesh. Previously this workflow
+required hand-editing `.mcp.json` and `.claude/settings.local.json`
+per project; now it's one command per project.
+## 0.1.19
+### Added
+- **Claude Code plugin manifest** for Anthropic Channels allowlist
+  submission. `.claude-plugin/plugin.json` + `.mcp.json` following the
+  official single-repo pattern (Telegram/Discord). Submitted to
+  Anthropic Plugin Directory 10 Apr 2026.
+- **`SYM_ALLOWED_PEERS`** — optional peer allowlist (defense-in-depth).
+  Comma-separated node names; only listed peers can push to Claude's
+  context. Empty = accept all authenticated peers. SVAF still gates on
+  content relevance regardless.
+- **`SECURITY.md`** — 3-layer defense model documentation (transport
+  auth + SVAF content gate + peer allowlist) for Anthropic review.
+- **17 plugin tests** covering manifest validation, security checks
+  (no permission relay, no code execution, self-echo filtering, peer
+  allowlist), and lifecycle (shutdown handlers, identity collision).
+## 0.1.18
+### Changed
+- **Auto-configure on install.** `npm install -g` now runs `postinstall`
+  that writes the MCP server config to global `mcpServers` in
+  `~/.claude.json` automatically. No separate `sym-mesh-channel init`
+  step needed — two commands to mesh: install + launch.
+- **Global MCP config** — server entry is now written to top-level
+  `mcpServers` (available in all Claude Code sessions), not
+  project-scoped.
+- **Windows postinstall fixes** — `require.resolve` for server.js path
+  (handles npm staging directory on Windows), EBUSY handling when
+  Claude Code has `~/.claude.json` locked, graceful skip if Claude
+  Code not yet installed.
+- **README repositioned** — lead with capability ("first non-Anthropic
+  Claude Code Channels implementation"), not use case. Simplified
+  Quick Start to two commands.
+- **0 vulnerabilities** — fresh dependency rebuild resolves all 6
+  moderate hono/node-server advisories.
+- Windows mDNS: built-in on Windows 10+, no Bonjour install needed.
+## 0.1.7
+### Added
+- **`npx @sym-bot/mesh-channel init`** — interactive installer that
+  writes `~/.claude.json` for the current project, picks a sensible
+  default `SYM_NODE_NAME` (`claude-mac` / `claude-win` / `claude-linux`),
+  resolves the absolute path to `server.js`, and prints the launch
+  command including the `--dangerously-load-development-channels` flag.
+  Backs up the existing config to `~/.claude.json.bak-<timestamp>`,
+  validates JSON round-trip, atomic write via tmp+rename. Refuses to
+  overwrite an existing entry without `--force`.
+- **README rewritten for LAN-first install.** Quick start is two
+  minutes: install, init, launch. No relay required. Bonjour/mDNS
+  is the default discovery path. Cross-network setup (relay) is now
+  the optional advanced section.
+### Changed
+- `package.json` `bin` now exposes both `sym-mesh-channel` (server
+  entrypoint) and `sym-mesh-channel-init` (installer). The package
+  description leads with "LAN-first via Bonjour, no relay required."
+### Why
+The 0.1.5/0.1.6 install path required users to manually edit
+`~/.claude.json`, know about the Channels dev flag, set up a relay,
+and obtain a relay token. That gated the demo behind real friction.
+LAN-only mode has worked since day one in the underlying SymNode
+(`sym/lib/node.js:509-511` only connects to the relay if `SYM_RELAY_URL`
+is set; Bonjour discovery starts unconditionally), but no documentation
+or installer surfaced it. This release closes that gap: two users on
+the same wifi can join the same mesh in two minutes with three commands.
+## 0.1.6
+### Fixed
+- `sym_send` no longer double-delivers. Previously called both
+  `node.send()` (broadcast as `event_type=message`) AND `node.remember()`
+  (persist as CMB which gets gossiped as `event_type=cmb`), causing
+  the same payload to arrive twice on receivers and double the
+  context-window cost. Now broadcasts the message frame only. Hosts
+  that want CMB persistence should call `sym_observe` separately
+  with proper CAT7 fields.
+- `sym_send` now reports the actual delivered count, not
+  `peers().length`. Requires `@sym-bot/sym >= 0.3.70` where `send()`
+  returns the count of peer transports that successfully accepted
+  the broadcast. The two can disagree when peers are tracked but
+  have broken transports — the delivered count is the truth about
+  what was actually sent.
+### Changed
+- Bumped `@sym-bot/sym` dep `^0.3.69` → `^0.3.70`. 0.3.70 ships the
+  identity lockfile that prevents two SymNode processes from
+  claiming the same nodeId on a host (the cliHostMode-vs-MCP
+  collision that broke real-time push on Windows during the
+  2026-04-09 round-trip test).
+## 0.1.5
+### Changed
+- Bumped `@sym-bot/sym` dep `^0.3.68` → `^0.3.69` (0.3.68 deprecated;
+  same code in 0.3.69 with a cleaner published tarball).
+- Added `files` whitelist to `package.json` and `.npmignore` for
+  `*.bak`, `*.swp`, `.DS_Store` so future publishes can't accidentally
+  ship local backup files. First NPM publish of this package.
+## 0.1.4
+### Changed
+- Bumped `@sym-bot/sym` dep `^0.3.43` → `^0.3.68` to pick up
+  duplicate-identity refusal (close code 4004) and the new
+  `identity-collision` event.
+### Added
+- Wired `node.on('identity-collision', ...)` to `process.exit(2)` so
+  the MCP dies cleanly when the relay reports a duplicate-identity
+  race. Together with v0.1.3's clean shutdown, this fully resolves
+  the host-side half of the duplicate-identity bug.
+## 0.1.3
+### Added
+- Clean shutdown handlers (SIGTERM/SIGINT/SIGHUP) that call
+  `node.stop()` before exiting, so the SymNode disconnects from the
+  relay before the process dies. Without this, restarts left zombie
+  registrations on the relay until the next heartbeat tick (up to
+  30s), creating a duplicate-identity race window for the next MCP
+  spawn. Idempotent re-entry guard.
+## 0.1.2
+### Fixed
+- Suppressed `peer-joined` / `peer-left` events from being pushed to
+  Claude's context as `<channel>` notifications. Presence is high-
+  frequency and low-signal — a relay reconnect could fire one event
+  per peer per cycle, flooding the context window. CMBs and direct
+  messages still flow through.
+## 0.1.1
+### Changed
+- Replaced hardcoded `claude-code` / `claude-code-mac` literals with
+  a single `NODE_NAME` constant sourced from `process.env.SYM_NODE_NAME`
+  (default `claude-code-mac`). Enables platform-scoped naming per
+  MMP §3.1.2 without source edits. Fixed stale display strings in
+  the MCP instructions, `sym_send` perspective, `sym_status` header,
+  and the self-echo dedup filter.
+## 0.1.0
+### Added
+- Initial release. MCP server that runs a `SymNode` peer node inside
+  a Claude Code session — own identity, own relay connection, own
+  SVAF evaluation. Tools: `sym_send`, `sym_observe`, `sym_recall`,
+  `sym_peers`, `sym_status`. Mesh events arrive as `<channel>`
+  notifications when launched with
+  `claude --dangerously-load-development-channels server:claude-sym-mesh`
+  (allowlisted server name required by Claude Code Channels).