Releases: sym-bot/sym
v0.7.11 — node.inbox() (SDK send+pull)
Adds node.inbox({peek,limit}) / node.inboxGet(id) — the pull-based receive counterpart to remember() (send). The node buffers every delivered CMB so any consumer pulls received CMBs without subscribing to events; the SDK is now sufficient for send and pull standalone (used by the MCP wrapper, sym-swift, headless scripts). FIFO drain with a cursor (no skip past limit), non-destructive peek. +4 tests.
v0.7.10 — signed CMBs (authenticity + integrity)
Every CMB is now Ed25519-signed by its author. Receivers verify the signature against the sending peer's handshake-announced identity key and that the content-address key still matches the fields — a forged, tampered, or content-swapped CMB is rejected before it can surface or be stored (audit-metered cmb-signature-rejected). Unsigned CMBs pass for interop unless SYM_REQUIRE_SIGNED_CMB (strict mode). Cryptographic layer above transport identity + SVAF. New: signCMB/verifyCMB in @sym-bot/core ^0.3.38. +6 tests; 182 pass. Also fixes two latent svaf-heuristic cold-start bugs (crash on fresh-memory receive; temporal-drift bypass).
v0.7.9 — ingestion flag on surfaced CMBs
Surfaced CMBs now declare whether the receiver ingested the CMB (remixed into memory with lineage → remixed: true) or only delivered it (surfaced but not stored → remixed: false, the directed-but-SVAF-rejected case), alongside the SVAF decision. Consumers check remixed to tell a recallable directed request from a transient one (MMP §9.2.2). Four committed test cases in tests/inbound-cmb-surfacing.test.js; 176 tests pass.
v0.7.8 — directed (peer-bound) CMB delivery
Directed CMBs (sym_send to=X) now surface to the receiving agent unconditionally, regardless of the SVAF verdict (MMP §4.4.4 / §9.2.2). The send path marks the wire frame with to + directed; the receiver surfaces a directed CMB exactly once (admit path on SVAF accept, dedicated delivery path on reject/redundant). SVAF governs memory admission only for directed CMBs, never delivery. Group-bound broadcasts (sym_observe) stay fully SVAF-gated — unchanged. Fixes the mesh receive-blindness where a directed coordination CMB scored low by SVAF was silently dropped.
v0.7.6 — SVAF decision log (additive)
SVAF decision log — persist and emit every evaluation (admit AND reject).
- feat(svaf): decision log — persist + emit every evaluation (818a712)
Additive change; no breaking API.
v0.7.5 — mesh replay-storm receive-path dedup
v0.7.4 — same-host loopback discovery
Same-host loopback discovery path so co-resident nodes mesh with no network.
- discovery: same-host loopback path so co-resident nodes mesh with no network (e01939b)
- docs: README EN/ZH parity — sym.day surfaced, groups beacon, anonymous names
v0.7.3 — sym groups lists groups (cross-platform)
sym groups now lists live groups on every platform (incl. Windows) via a discovery beacon — each node advertises its group on a shared _symgroups._tcp (group in TXT) through the bundled pure-JS bonjour-service. Group names may be anonymous (opaque codes). Open-join in this release; invite-gated private groups are next. See CHANGELOG.md.
v0.7.2 — Windows green
sym ask is now deterministically clean on Windows (4/4, was 4/4 crash). The crash was process.exit(0) firing while the synthesis call's handles were mid-close → libuv UV_HANDLE_CLOSING (0xC0000409). sym ask now drains naturally instead of force-exiting. SYM is validated on Mac + Windows + cross-machine (Bonjour LAN). Install: npm i -g @sym-bot/sym. See CHANGELOG.md.
v0.7.1 — Windows fixes
Found by a real cross-machine Windows test. sym ask no longer leaves a named-pipe handle mid-close on exit (socket.destroy). sym groups degrades gracefully when Apple Bonjour's dns-sd is absent (Windows) — the node still meshes via bundled bonjour-service. See CHANGELOG.md.