v0.1.3

Surface WebSocket upgrade failures and discovery info

The WS connect path previously collapsed any handshake failure into a
generic "Failed to connect" error, hiding the HTTP status that the
player returned. Capture the unexpected-response event so the status
code, status message, headers, and body (first 512 bytes) end up in the
logs and in the resulting CannotConnect message. Also log the discovery
result (playerId, householdId, websocketUrl) on success and emit a warn
if the discovery HTTP call itself fails. Bump to 0.1.3.