fix: default to glibc for Linux downloads for better stability

The musl variant has known stability issues with binject (segfaults).
While musl theoretically works on both musl and glibc systems, glibc
provides better stability in practice.

This change affects all socket-btm binary downloads on Linux when
libc is not explicitly specified.

Author: jdalton

src/releases/socket-btm.ts

@@ -128,7 +128,7 @@ export interface SocketBtmBinaryConfig {
   targetArch?: Arch
   /**
    * Linux libc variant (musl or glibc).
-   * Defaults to musl for Linux for broader compatibility.
+   * Defaults to glibc for Linux for better stability.
    * Ignored for non-Linux platforms.
    */
   libc?: Libc
@@ -435,8 +435,9 @@ export async function downloadSocketBtmRelease(
     const platform = (targetPlatform || os.platform()) as Platform
     const arch = (targetArch || os.arch()) as Arch
 
-    // Default to musl for Linux for broader compatibility (works on both musl and glibc systems)
-    const libcType = libc || (platform === 'linux' ? 'musl' : undefined)
+    // Default to glibc for Linux for better stability
+    // (musl works on both musl and glibc systems, but has known stability issues with some tools like binject)
+    const libcType = libc || (platform === 'linux' ? 'glibc' : undefined)
 
     // Build asset name and platform-arch identifier
     const assetName = getBinaryAssetName(baseName, platform, arch, libcType)