mDNS service not discoverable with correct hostname

[j0nl1]

Description

The mDNS service publication was missing an explicit host configuration, which caused the service to not be
properly discoverable with the opencode.local hostname on the local network.

Current Behavior

• The mDNS service is published without a host field, so it uses the system's default hostname instead of
  opencode.local
• The CLI displays opencode.local without the port number, which is misleading

Expected Behavior

• The mDNS service should be discoverable at opencode.local
• The CLI should display the full address including the port (e.g., opencode.local:3000)

Steps to Reproduce

1. Start the web server with mDNS enabled
2. Try to discover the service using dns-sd -B _http._tcp or a Bonjour browser
3. Notice the service is not advertised with opencode.local as the hostname

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

[github-actions]

This issue might be related to existing issues about hostname configuration and mDNS service discovery. Please check:

• mDNS fails to initialize: 'Object is not a constructor' error with bonjour-service #6422: mDNS fails to initialize: 'Object is not a constructor' error with bonjour-service (CLOSED - may provide context on mDNS issues)
• fix(desktop): Custom server.hostname config ignored - always connects to 127.0.0.1 #7971: fix(desktop): Custom server.hostname config ignored - always connects to 127.0.0.1 (OPEN - related hostname configuration issues)
• Bug: Web terminal fails when accessing via network IP instead of localhost #5844: Bug: Web terminal fails when accessing via network IP instead of localhost (OPEN - related network/hostname handling)

Feel free to ignore if none of these address your specific case.