Handle fatal Errors in WebSocketClient read loop

[liyifan9642-creator]

Summary

Closes #1460.

WebSocketImpl#decodeFrames rethrows fatal Errors (VirtualMachineError, ThreadDeath, LinkageError). The client read loop in WebSocketClient#run only caught IOException and RuntimeException, so such a fatal Error escaped run() and silently terminated the connect/read thread: no onError, no onClose, and no cleanup, leaving the socket half-open. The server-side WebSocketWorker already handles this (see #1223); this change brings the client to parity.

Changes

• Catch the same fatal trio in the client read loop, surface it through onError (wrapped, as elsewhere) and close the connection with CloseFrame.UNEXPECTED_CONDITION (1011).
• Add Issue1460Test, which uses a custom Draft that throws a LinkageError during translateFrame. The test fails before the change (no callbacks, thread dies) and passes after.

Notes

• Single-file production change; no public API change; normal I/O and protocol paths are untouched.
• Happy to adjust if maintainers would prefer a VirtualMachineError to be rethrown after cleanup instead.

[changeset-bot]

⚠️ No Changeset found

Latest commit: aed1160

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR