fix: connection lifecycle fixes for socket death and close

[Dodothereal]

fix: connection lifecycle fixes for socket death and close

Summary

Fixes the connection lifecycle issues where the connected flag remained true after socket death, and the close() method left internal buffers in a stale state. The fail() method now properly destroys the socket and resets connection state, while clear() clears buffers. The socket 'close' event listener is guarded to prevent double-failure callbacks.

Fixes #6

Changes

• In fail(): destroy socket with error, set sock=null, shookHands=false, ready=null, and clear buffers.
• In close(): clear buffers after closing socket.
• In connect(): only call fail on 'close' event if socket is still open to avoid double-fail.

Testing

Built the project with npm run build and ran the existing test suite via node scripts/mock-server-test.js. All tests pass:

PASS  handshake
PASS  GetVersion decodes StringMessage
PASS  GetWorldInfo decodes nested NameInfo + fields
PASS  RunCommand captures TEXT frames
PASS  cached bind (second call works)

All protocol checks passed.

---

AI assistance disclosure

This contribution was produced by an autonomous AI coding agent (Claude Code) that @Dodothereal operates and monitors. @Dodothereal is accountable for it, will address review feedback promptly, and will close this PR immediately if this kind of contribution is unwelcome in this project. Commits carry an Assisted-by: Claude Code trailer.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.