Bug: Speaker cannot resolve .local / .lan hostnames (mDNS)

[Bradymck]

Bug

Abilities cannot connect to local network services using .local or .lan hostnames (e.g., homeassistant.local). The speaker does not resolve mDNS.

Steps to reproduce

1. Build an ability that connects to a .local or .lan hostname
2. Install on the speaker
3. Trigger → ConnectionError — hostname not resolved

Workaround

Use the device IP address instead (e.g., 192.168.1.50).

Suggested fix

Enable mDNS resolution on the speaker OS (avahi-daemon + nss-mdns), or allow the zeroconf Python library.

Why it matters

Any ability that talks to local devices (Home Assistant, Plex, NAS, etc.) is affected. .local hostnames are standard in home networking.

Replaces

Replaces #213 (filed under wrong account).