Files
d4d6f486ea fix(zap): mDNS opt-in (--mdns, ZAP_MDNS); hanzoai/tasks v1.53.2 so its ZAP clients stop listening (#54)
* fix(zap): make mDNS discovery opt-in

With ZAP on a non-loopback address, plugins/zap still ran mDNS unless
--no-mdns was passed: it announced _hanzo-base._tcp on the LAN, and
handlePeerEvent dialled any peer that announced it back. Hanzo nodes
reach each other through explicit peers, so discovery is now off unless
--mdns or ZAP_MDNS asks for it, and never on loopback. --no-mdns still
forces it off, so v1.5.93 configs keep their meaning.

Every other ZAP node in the repo already sets NoDiscovery.

Co-Authored-By: Claude Opus 5 <[email protected]>

* fix(tasks): take hanzoai/tasks v1.53.2, whose ZAP clients do not listen

plugins/tasks dials a Tasks server through hanzoai/tasks' SDK client.
At v1.52.9 that client, like pkg/tasks', started its node on Port 0,
listening on every interface, before dialling out. v1.53.2 dials
without starting a listener (hanzoai/tasks b4a8209c). zap-proto/zip
moves to v1.36.9 with it.

Co-Authored-By: Claude Opus 5 <[email protected]>

---------

Co-authored-by: Claude Opus 5 <[email protected]>
2026-09-10 21:12:42 -07:00
..