Previously a blocked join just dropped the socket, so the MC client
showed 'Internal Exception: SocketException: Connection reset'.
Now when next_state=2 (login), the proxy sends a proper Login
Disconnect (0x00) packet containing a JSON chat component, and the
client displays the message on its disconnect screen.
- block_message added to config (default Korean message); editable
in Settings UI as a textarea
- build_login_disconnect() encodes (varint length)+(0x00)+(JSON str)
- Status/ping (next_state=1) still silently dropped so the proxy
presence is not announced to scanners
- Backward-compat: load_config() backfills block_message on old files
Reviewer concerns:
1. POST /api/proxy/restart only saved config (reload), did not restart
the listener. Now it touches data/restart.signal; proxy watcher
polls that file separately and force-restarts the listener even
when config is unchanged.
2. Editing proxy.listen_port via UI could break Docker port mapping
(compose publishes 25565:25565 only). UI now shows it read-only;
README documents how to change it together with compose.
- proxy/main.py: ProxyState.check_restart_signal() + watcher uses it
- api/config_io.py: touch_restart_signal() helper
- api/routes/status.py: /api/proxy/restart -> touch_restart_signal()
- frontend Settings: disabled listen_port input + 프록시 재시작 button
- README + .gitignore updated
