havm 0.3.1

What's new in v0.3.1

Fixed: guest IP resolution broke the "ready" detection

havm run could report Guest reachable at fe80:: and then time out
waiting for the Home Assistant web UI, because the hostname resolver
result was copied into a too-small buffer — IPv6 addresses came back
truncated (first 8 bytes plus stack garbage). macOS 15's mDNS resolver
returns the IPv6 link-local record for homeassistant.local first,
which surfaced the bug; it could in principle hit any macOS version.

The resolver now copies the address correctly, walks the full result
list, and prefers IPv4 — the address type the guest reliably gets
via DHCP. Link-local IPv6 (fe80::/10) results are skipped (they need
a scope ID to be usable); a global IPv6 address is used as a fallback
on IPv6-only setups, and the banner URL is bracketed accordingly
(http://[...]:8123).

If you were affected, the guest itself was always fine — only the
reported address/URL was wrong. As an interim workaround,
network.guest_hostname: <IPv4> in ~/.config/havm/config.yml skips
mDNS entirely.

Full Changelog: v0.3.0...v0.3.1