fix: resolve symlinks in launcher script for npm global install

The shell launcher used ${0%/*} to find its lib/ directory, but when
npm installs globally it creates a symlink in the bin dir. ${0%/*}
resolves to the npm bin dir, not the package dir, causing:
  Cannot find module '.../lib/hyperagent-launcher.cjs'

Use readlink -f / realpath to resolve symlinks before computing the
relative path to the lib directory.

Tested: symlink from /tmp/ → prints version correctly; old approach
confirmed to fail with MODULE_NOT_FOUND.

Signed-off-by: Simon Davies <simongdavies@users.noreply.github.com>

Author: simongdavies

scripts/build-binary.js

@@ -318,7 +318,9 @@ console.log("📝 Creating launcher...");
 // We use a shell wrapper that invokes node with explicit CommonJS treatment
 const launcher = `#!/bin/sh
 # HyperAgent Launcher - resolves native addons from lib/ directory
-exec node --no-warnings "\${0%/*}/../lib/hyperagent-launcher.cjs" "$@"
+# Resolve symlinks so this works when npm links the bin globally
+SCRIPT_DIR="$(cd "$(dirname "$(readlink -f "$0" 2>/dev/null || realpath "$0" 2>/dev/null || echo "$0")")" && pwd)"
+exec node --no-warnings "\${SCRIPT_DIR}/../lib/hyperagent-launcher.cjs" "$@"
 `;
 
 // The actual launcher logic in CommonJS