deps(deps): bump @sym-bot/sym from 0.7.6 to 0.7.30 in the sym-family group across 1 directory

[dependabot]

Bumps the sym-family group with 1 update in the / directory: @sym-bot/sym.

Updates @sym-bot/sym from 0.7.6 to 0.7.30

Release notes

Sourced from @​sym-bot/sym's releases.

0.7.30 — cross-peer grounding fix + sym emit (MMP Class 1 emitter)

Fixed

Cross-peer grounding was silently broken. `remember()` with parents minted a root-scheme `cmb1-` key on a lineage-bearing CMB; receivers re-verify the content address by role (lineage present → remix scheme), so the recompute mismatched and every peer hard-rejected authored grounding CMBs as forged. Agent-authored `verified:`/`failed:` outcomes never landed cross-node in 0.7.29. Now minted under the remix scheme (§8.2.1 role dispatch); two-node regression test included.

Added

`sym emit` — the MMP Class 1 Emitter (spec §17.1). Emit signed CAT7 blocks into a running mesh without being a node: no daemon, no store, no identity lock, with the emitter's own persistent identity so provenance and earned trust accrue to the actual source (CI jobs, sensors, scripts).

```bash sym emit --server 192.168.1.10:52781 --group team --name github-ci
'{"focus":"build 4821 green","intent":"ground","commitment":"verified: full suite passed"}' ```

Programmatic: `require('sym').emit` → `emitOnce()` / `connect()`. LAN TCP today; relay emission lands with one-shot E2E (§18.2.1). Tested end-to-end over real sockets against a real node.

Dependencies

`@sym-bot/core` ^0.3.48 — tether attestations + kernel identity (§15.8), `recomputeKey` export, retroactive-audit evaluation, published conformance vectors + JSON schemas.

Suite: 280/280.

v0.7.27 — stop cross-node echo/replay storm

Fixes a cross-node echo/replay storm.

• Own-only anchors: anchors sent on peer connect are now the node's own emissions only, so a node no longer re-forwards CMBs it merely received from other peers (the A→B→C→A amplifier).
• Reload-durable receive dedup: the receive-path dedup cache now persists across a plugin reload / process restart, so already-seen CMBs no longer re-surface as new.

Suite 258/258. Published to npm as @​sym-bot/sym@​0.7.27.

v0.7.26 — nodes self-report memory stats

Each node emits a lightweight node-stats frame (emitted/admitted/memory) to the roster every 15s, so any observer can show real counts for every node — including cross-machine agents whose stores are unreadable locally. Metadata only (not a CAT7 CMB; no SVAF). 3 tests; suite 258/258.

v0.7.24 — roster key registry (EA5)

Verify attestations/grants relayed from peers never directly handshook. RosterKeyRegistry pins nodeId→key by source precedence (anchor > handshake > grant-vouched); keys ride the rooted grant chain (granteeKey), the relayer never vouches, unrooted grants vouch for nothing. 9 tests; suite 253/253.

v0.7.22 — durable attestation audit trail (survives restart)

The Admission Attestation trail (attestations + Merkle checkpoints + witness countersignatures) now persists append-only on disk and reloads on startup, so it survives a node restart; the per-attester chain cursor is restored so seq/prev keep linking across the boundary. Guarantee: tamper-evident + omission-evident to the last witnessed checkpoint, and durable across restarts. Core unchanged. Suite 227/227.

v0.7.21 — attestation gossip + omission-evidence (D1-D3)

D1 index + every-gate-attested + local omission-detection; D2 roster gossip (verify end-to-end, rate-limit, relay-once); D3 Merkle checkpoints + roster witnessing + reconcileChain. Guarantee: tamper-evident + omission-evident to the last witnessed checkpoint. Requires @​sym-bot/core ^0.3.43. Suite 223/223.

v0.7.20 — Admission Attestations persisted on the gated remix (Phase C)

Requires @sym-bot/core ^0.3.42.

On SVAF admit, the node signs an Admission Attestation and attaches it to the stored remix (cmb.admission): { of, by, at, roster, method, verdict, fields, role, seq, prev }, signed with the node's Ed25519 identity key. of binds the original gated CMB key; per-field fields come from the gate verdict (heuristic) or field_drifts mapped through computeFieldVerdicts (neural). A per-attester hash-chain (seq/prev) makes a dropped attestation a detectable gap. role is the node's claimed role — consumers verify it against the rooted role-grant chain. CMB-envelope sibling, so cmbKey and existing signatures are untouched.

Reject/redundant attestation, the queryable index, and mesh-wide gossip are the next phase. Suite 210/210.

v0.7.19 — opaque payload survives the SVAF-admit remix path

... (truncated)

Changelog

Sourced from @​sym-bot/sym's changelog.

0.7.30 (2026-07-07)

• fix (cross-peer grounding): remember() with parents now mints the REMIX-scheme cmb1- key (§8.2.1 role dispatch). Previously a lineage-bearing authored CMB carried a root-scheme key, failed the receiver's content re-verification, and was hard-rejected as forged — agent-authored grounding CMBs silently never landed on any peer. Two-node regression test included.
• feat (sym emit + sym/emit): MMP Class 1 Emitter (§17.1) — one-shot, signed CAT7 emission to a remote mesh node with the emitter's own persistent identity. No daemon, no store, no identity lock. CLI: sym emit --server <host:port> [--group] [--name] [--to] [--parents] '{...}'; programmatic: require('sym').emit → emitOnce() / connect(). LAN TCP; relay emission lands with one-shot E2E (§18.2.1). Real-TCP e2e tests.
• deps: @​sym-bot/core ^0.3.48 (tether attestations, recomputeKey export, retroactive-audit evaluation, conformance vectors + schemas).

0.7.27 — 2026-07-01

Fixed

• Stop a cross-node echo/replay storm — own-only anchors + reload-durable dedup. Two in-memory safeguards that a plugin reload or process restart wiped, plus a missing origin filter, let already-seen CMBs re-circulate across a multi-node mesh:
  • Origin filter on anchor exchange (node.js). On peer connect a node sent its 5 most-recent store entries as SVAF anchors with no origin check, so it re-forwarded CMBs it had merely received from other peers — the A→B→C→A amplifier. Anchors are now the node's own emissions only (peerId == null); a peer learns each node's state from that node directly, so own-origin anchors suffice.
  • Reload-durable receive dedup (frame-handler.js). The receive-path dedup cache (_seenCmbKeys) was in-memory only, so a reload made every already-processed CMB look new again. It now persists to a dotfile beside the store (TTL-pruned on load, throttled write, best-effort — any FS error degrades to in-memory), so reloads and version skew are non-fatal.
  • Verified: own-only anchors forward 0 peer CMBs; the dedup cache rehydrates across a simulated reload; expired keys prune on load. Suite 258/258.

0.7.26 — 2026-06-30

Added

• Nodes self-report their memory stats over the mesh. A node is sovereign over its store, so an observer on another machine can never read it — it could only see a node's broadcasts, never what it admitted. Each node now EMITS its own tally to the roster as a lightweight node-stats frame (metadata, NOT a CAT7 CMB — it never enters a cognition stream or SVAF): emitted = CMBs it authored (store local count), admitted = CMBs it accepted from peers (store peer count), memory = total. Gossiped on start and every statsInterval (default 15s). frame-handler ingests a peer's node-stats and the node re-emits it as a node-stats event for hosts (e.g. the Mesh Edge observer) to render. Self-reported and unsigned — a convenience metric, not stored or treated as authority. Lets any observer show real emitted/admitted counts for every node, including cross-machine agents whose stores are unreadable locally. 3 tests; suite 258/258.

0.7.25 — 2026-06-29

Added

• Earned-authority-weighted attestation aggregation (EA6). node.aggregateAttestations(cmbKey) folds every attestation about a CMB into a single roster verdict weighted by who actually holds rank. Each attestation is signature-gated against the attester's key from the roster registry (unverifiable ones are excluded as evidence, never weighted), then its attester's role is resolved at its own attestation time (role-at-time) from the rooted grant chain; weight is 2^rank (participant 1, validator 2, anchor 4). Overall and per-CAT7-field verdicts become weighted tallies with a deterministic dominant + confidence (dominant's share of total weight); over-claims (claimed role ≠ resolved) are down-weighted to the resolved rank and surfaced in mismatches. So an anchor's admit outweighs a participant's and a node asserting unearned authority cannot inflate consensus. With no anchor pinned, every attester resolves to participant (uniform weight 1) and this reduces to an unweighted tally — it sharpens the moment authority is activated. 2 tests; suite 255/255.

0.7.24 — 2026-06-29

Added

• Roster key registry (EA5) — verify signatures from peers you never directly met. A nodeId is a uuidv7, independent of its Ed25519 key, so until now a node could only verify CMBs/attestations/grants from direct handshake peers; a relayed frame from a non-adjacent node failed as unknown-key (invisible on a fully connected LAN, but it capped the protocol at direct connectivity).
  • lib/roster-keys.js — RosterKeyRegistry pins nodeId→publicKey by source precedence (anchor > handshake > grant-vouched). A weaker-or-equal source can never repoint a stronger binding; equal-strength key conflicts are refused and recorded as evidence; duck-types Map get/set so it drops in where the raw key map was used. Persisted append-only.
  • Keys ride the rooted authority chain. A grant now binds the grantee's key into its signed payload (granteeKey, @sym-bot/core 0.3.45), so a node that never handshook the grantee learns its key from a rooted grant — tamper-evidently, because swapping the key breaks the grantor's signature (the relayer never vouches). The store pins a grantee key only when the grant is role-effective (grantor actually held the rank), so an unrooted or over-reaching grant vouches for nothing and cannot poison the registry.
  • Node wiring — handshake pins at handshake strength (_pinPeerKey, writing both the legacy CMB map and the registry); attestation / checkpoint / witness verification now resolves keys via _identityKey (registry first, covering relayed + persisted bindings); grantRole binds the grantee's known key. 9 tests; suite 253/253.

0.7.23 — 2026-06-29

Added

... (truncated)

Commits

• e6b6cfd release: 0.7.30 — cross-peer grounding fix + sym emit (Class 1); core ^0.3.48
• 4ded0b1 feat: sym/emit — MMP Class 1 emitter (§17.1) + sym emit CLI verb
• 10cedf8 fix: remember() with parents mints the REMIX-scheme cmb1- key — authored grou...
• 5907fc8 feat: retroactive lineage-tether audit — §15.8 applied to stored chains
• 232e0e1 feat: cmb-fetch — content-addressed retrieval + self-verifying fetchCMB()
• a077564 feat: sign + verify §15.8 tether attestations on the remix path
• bb11181 release: 0.7.29 — depends on @​sym-bot/core ^0.3.47
• a0d5792 feat: MMP §15.8 lineage tether severance on the remix path (on by default)
• d2867b0 feat: accept repeat groundings — §6.7 redundancy waiver eligibility (MMP 1.1....
• d2089eb fix: resolve CMB signature keys through the roster registry
• Additional commits viewable in compare view

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[dependabot]

Looks like @sym-bot/sym is no longer updatable, so this is no longer needed.