fix(deps): follow trac-msb to hyperdht 6.29.6

[TracSystems]

Companion to Trac-Systems/main_settlement_bus#802. Re-pins trac-msb to ea72a9c, which moves hyperdht 6.27.0 → 6.29.6.

Why

A long-running peer aborts roughly every few days:

TypeError: Cannot read properties of null (reading 'buffer')
    at crypto_generichash_update (sodium-native/index.js:445)
    at crypto_generichash_batch (sodium-native/index.js:405)
    at annSignable (hyperdht/lib/persistent.js:275)
    at Persistent.onunannounce (hyperdht/lib/persistent.js:62)

hyperdht installs its persistent request handlers on a once('persistent') listener and never tears them down, while dht.id returns null for as long as the node is ephemeral — and an adaptive node returns to ephemeral on every wakeup or network change. In 6.27.0 the dispatcher only checked that the handlers existed, so an inbound UNANNOUNCE reached onunannounce, which passes that null id into sodium.crypto_generichash_batch, where it is dereferenced in C.

Fixed upstream in hyperdht 6.29.4 — holepunchto/hyperdht#242, 8f66a11:

- if (this._persistent === null) return false
+ if (this._persistent === null || this.id === null) return false

Why this pin has to move too, not just the consumer's

This is the part worth catching. trac-peer depends on trac-msb at its own exact sha. A consumer (e.g. intercom) that bumps only its trac-msb pin ends up with a second, nested trac-msb under node_modules/trac-peer/ — still carrying hyperdht 6.27.0. The lockfile then looks fixed while the peer keeps crashing, because the nested copy is what resolves at runtime.

Verified both ways on the lockfile:

	before	after
node_modules/hyperdht	6.20.5	6.29.6
node_modules/trac-msb/node_modules/hyperdht	6.27.0	removed (deduped)

Net lockfile change is 8 insertions / 39 deletions — the bump plus the removal of that nested subtree. node_modules/pear-runtime/node_modules/hyperdht stays at 6.33.0, unchanged and pre-existing.

Notes

• 6.29.6 is the last release of the 6.29 line: the guard plus two small fixes, no new dependencies. Deliberately not 6.30.0+, which adds the "closest nodes in key" feature, a new hyperdht-address dependency, and parallel pre-connect on FIND_PEER.
• Version left at 0.4.9; consumers pin this repo by sha.
• Merge order: main_settlement_bus#802 first, then this, then the consumer re-pins both.

🤖 Generated with Claude Code