ospab 7704e0bdb1 §A.3: remove dead tun2socks code (native OSTP TUN is the only path) ... The "system" TUN stack that shelled out to a bundled tun2socks binary is long-dead — Flutter already hardcodes the native OSTP stack — and only bloats the build. - ostp-jni: drop the tun2socks spawn branch and the tun_child handle; the native TUN (run_native_tunnel_from_fd) is now unconditional. The JNI signature is kept ABI-stable (t2sBinPath/localProxy retained but ignored) to avoid breaking the Kotlin linkage without an Android build. - Delete the committed 10 MB tun2socks-arm64 asset; drop the tun2socks download steps from the Android build scripts. - Remove the dead tun2socks.exe entry from the desktop build_dist.js (it required a file nothing downloads, breaking the GUI dist build). - Reword stale tun2socks references in proxy.rs, the GUI config comment, install.ps1, the release workflow matrix, and CONTRIBUTING. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-06-27 16:29:55 +03:00
..
workflows	§A.3: remove dead tun2socks code (native OSTP TUN is the only path)	2026-06-27 16:29:55 +03:00