fix: support comma-separated bind addresses in host setting

[fqx]

Problem

#1526 introduced a pre-bind approach (uvicorn.Config + bind_socket()) to fail fast on port conflicts before model preload. This broke multi-address binding: bind_socket() calls sock.bind((host, port)) which requires a plain string, not a list — so users who had host: [127.0.0.1, 192.168.1.x] in their settings (or set a comma-separated value) now get a TypeError on startup.

Supersedes #908, which patched the old uvicorn.run() call that no longer exists.

Fix

omlx/settings.py — normalise legacy YAML list values (host: [a, b]) to a comma-separated string on load. Backward-compatible: single-string configs are unchanged.

omlx/cli.py (serve_command) — split the host string by comma, bind one socket per address (preserving the fail-fast guarantee from #1526), then pass all sockets to Server.run(sockets=[...]). uvicorn accepts a socket list and listens on all of them.

omlx/cli.py (launch_command) — pick the first bind address as the connect host; normalise wildcards (0.0.0.0, ::) to 127.0.0.1.

omlx/utils/network.py — add is_valid_bind_host(): accepts all valid IPs including 0.0.0.0 and ::, unlike is_valid_alias() which rejects unspecified addresses.

omlx/admin/routes.py — validate each comma-separated part on save, returning a readable 400 before an invalid value can crash the server on restart.

omlx/admin/static/js/dashboard.js — extract .msg from Pydantic error objects instead of joining raw objects (fixes [object Object] display). Two call sites.

omlx/admin/i18n/{en,zh,ja,ko,zh-TW}.json — add host_multi_hint string in all five languages; drop "(caution)" from host_custom label now that entering multiple addresses is a valid normal use case.

omlx/admin/templates/dashboard/_settings.html — show the host_multi_hint hint below the custom host input when custom mode is active.

Usage

Enter multiple bind addresses separated by commas in the Host field:

127.0.0.1, 100.64.0.1

Existing single-address settings and legacy YAML list values both continue to work without migration.

Testing

1. Set host to 127.0.0.1, ::1 in the web UI and save — both addresses should appear in startup output
2. Start with a settings.json containing "host": ["127.0.0.1", "192.168.1.x"] — should load cleanly and show both bind lines
3. Enter an invalid value (e.g. not a host!!) — should get a readable 400 error, not [object Object]
4. Single-address configs continue to work unchanged
5. omlx launch with a multi-address host connects via the first address

🤖 Generated with Claude Code