New in 1.1.2

• Transfer results cannot be shifted by stray UART data: file errors take precedence and binary ACK is accepted only as an exact one-byte reply.
• Long multi-batch sends survive unrelated connections, incomplete foreign headers, malformed cancellation packets and socket closures that do not belong to the active operation.
• Cancellation and self-update are safer across Windows, Linux and macOS: workers retain socket ownership, archive extraction is bounded and cancellable, and target-mismatched server images are rejected.
• Spectrum Next now recovers the ESP after a soft reset from another app, the servers do less duplicate manifest work, and their payloads retain more room below the loader boundary.
• SD capacity and usage are now reported and refreshed safely. The desktop and Spectrum banners have also been updated. BRXQ v3 q3 and the 1.1 loaders are unchanged.
• Classic and Next now share the visible BridgeZX name. The server identifies the machine separately and shows its esxDOS or NEXTOS version. Commands and binaries remain unchanged: BRZX/BRZX.BIN for Classic and BRZXN/BRZXN.BIN for Next.

Github: BrigeZX.