Secpar 3.5.0 — three remote devices

Secpar now allows up to three simultaneous remote streaming devices per host.

• Windows and Linux: replace the one-device streaming gate with three independent reservations. A fourth connection receives a clear three-device limit message. Disconnects and failed starts release only their own capacity.
• Windows: each authenticated device retains its own virtual controllers; a three-device controller-isolation regression test verifies independent controller-zero inputs and disconnection.
• Android: replace phone-centric connection errors with device wording and show the new connection-limit message. Android remains client-only. PiP and the working video/audio player are preserved.
• Keep the 3.4 audio pause/resume and Wayland launch fixes.

These are optimized release packages only, with one host/client app per desktop OS and one Android client APK. Android retains its signing certificate and package identity (3.5.0, version code 521). Existing pairings and accounts remain.

Windows installation briefly disconnects Secpar sessions while the service restarts. Update the Windows host for multi-device streaming; update Android for the new limit wording. Physical three-device multiplayer testing is still needed. Desktop hardware-controller forwarding and native Linux virtual gamepads remain unfinished; do not treat the connection limit change as a completed cross-platform multiplayer implementation.

Linux hosting is still the initial LAN-owner implementation. Linux client launch, account sign-in and streaming to Windows are user-confirmed on CachyOS KDE Wayland. Native Linux hosting, remote/account hosting and guest access still need further work. macOS hosting remains unfinished.

The requested automatic same-account computer list/pairing and desktop UI overhaul are in progress separately and are not included in 3.5.0.

Validation: three racing-capacity/cleanup tests; 14 shared-host tests; ten native Linux host tests; Windows host regressions and controller isolation; 205 Android unit tests and minified release checks; actual AppImage native Wayland window creation/rendering; optimized installer payload verification. No physical phone was automatically modified.