fix: Termux installer stores binary in runtime/ and cleans old PATH entries

Binary is now at ~/.btch/runtime/btch instead of ~/.btch/bin/btch so
old PATH entries from previous installs don't shadow the wrapper at
$PREFIX/bin/btch (fixes "cannot execute: required file not found").
Also cleans stale .btch/bin PATH lines from shell configs on reinstall.

🤖 Generated with Codebuff
Co-Authored-By: Codebuff <noreply@codebuff.com>

Author: BOTCAHX

.github/workflows/release.yml

@@ -10,7 +10,7 @@ on:
   workflow_dispatch:
     inputs:
       version:
-        description: "Release tag to publish (for example btch-cli@3.0.14)"
+        description: "Release tag to publish (for example btch-cli@3.0.15)"
         required: true
 
 permissions:
@@ -186,7 +186,7 @@ jobs:
   # Publish the package to npm on every GitHub release. Requires the
   # NPM_TOKEN secret (Settings → Secrets and variables → Actions) with
   # publish permissions. The version is taken from the release tag, so
-  # just create a release like btch-cli@3.0.14 and the package is
+  # just create a release like btch-cli@3.0.15 and the package is
   # published as 1.0.4 automatically.
   npm-publish:
     if: github.event_name == 'release'

CHANGELOG.md

@@ -5,6 +5,13 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [3.0.15] - 2026-08-22
+
+### Fixed
+- Termux: binary now stored in `~/.btch/runtime/` (not `~/.btch/bin/`) so old PATH entries from previous installs don't shadow the wrapper and cause "cannot execute: required file not found"
+- Termux: old `~/.btch/bin` PATH entries cleaned from `.bashrc`/`.zshrc`/`.profile` on install
+- Termux: wrapper now shows a clear error message if proot-distro Debian fails to start
+
 ## [3.0.14] - 2026-08-18
 
 ### Fixed

README.md

@@ -26,7 +26,7 @@ What the installer does:
 
 ```bash
 # Install a specific version (keep in sync with package.json)
-curl -fsSL https://raw.githubusercontent.com/hostinger-bot/btch-cli/main/install.sh | bash -s -- --version 3.0.14
+curl -fsSL https://raw.githubusercontent.com/hostinger-bot/btch-cli/main/install.sh | bash -s -- --version 3.0.15
 
 # Install from a local binary instead of downloading
 bash install.sh --binary /path/to/btch

install.sh

@@ -21,7 +21,7 @@ Install btch from GitHub Releases.
 
 Usage:
   curl -fsSL https://raw.githubusercontent.com/hostinger-bot/btch-cli/main/install.sh | bash
-  curl -fsSL https://raw.githubusercontent.com/hostinger-bot/btch-cli/main/install.sh | bash -s -- --version 3.0.14
+  curl -fsSL https://raw.githubusercontent.com/hostinger-bot/btch-cli/main/install.sh | bash -s -- --version 3.0.15
   bash install.sh --binary /path/to/btch
 
 Options:
@@ -108,7 +108,7 @@ EOF
     }
   fi
 
-  # Remove leftovers from previous installs (npm route, glibc binary, symlinks).
+  # Remove leftovers from previous installs (npm route, old binary, wrapper, stale PATH).
   rm -f "$HOME/.btch/bin/btch"
   rm -f "/usr/local/bin/btch"
   if [[ -n "${PREFIX:-}" ]]; then
@@ -117,10 +117,25 @@ EOF
   rm -rf "$HOME/.btch"
   mkdir -p "$INSTALL_DIR"
 
+  # Clean up old PATH entries pointing to ~/.btch/bin from shell config
+  # files (v3.0.13 and earlier). These would shadow the wrapper at
+  # $PREFIX/bin/btch and cause the glibc binary to be executed directly
+  # in Termux, producing "cannot execute: required file not found".
+  for config in "$HOME/.bashrc" "$HOME/.bash_profile" "$HOME/.profile" "$HOME/.zshrc" "$HOME/.zshenv"; do
+    if [[ -f "$config" ]]; then
+      sed -i "\|.btch/bin|d" "$config" 2>/dev/null || true
+      sed -i "\|# btch|d" "$config" 2>/dev/null || true
+    fi
+  done
+
   # 3) Inside Debian the full glibc + no seccomp means the standalone arm64
-  #    binary works. Resolve the version and download it to Termux home
-  #    (~/.btch/bin) — the wrapper bind-mounts it into Debian at runtime, so
-  #    `btch` runs inside Debian while the CLI stays visible in Termux home.
+  #    binary works. Resolve the version and download to ~/.btch/runtime/ —
+  #    NOT ~/.btch/bin/ (which might be on PATH from old installs and would
+  #    shadow the wrapper). The wrapper bind-mounts the runtime dir into
+  #    Debian at /usr/local/btch.
+  local RUNTIME_DIR="${USER_DIR}/runtime"
+  mkdir -p "$RUNTIME_DIR"
+
   ASSET_NAME="btch-linux-arm64"
   BINARY_NAME="btch"
   resolve_release_version
@@ -135,8 +150,8 @@ EOF
   curl -fsSL "${RELEASE_BASE_URL}/checksums.txt" -o "$checksum_file"
   verify_checksum "$binary_file" "$checksum_file"
 
-  cp "$binary_file" "${INSTALL_DIR}/${BINARY_NAME}"
-  chmod 755 "${INSTALL_DIR}/${BINARY_NAME}"
+  cp "$binary_file" "${RUNTIME_DIR}/${BINARY_NAME}"
+  chmod 755 "${RUNTIME_DIR}/${BINARY_NAME}"
   rm -rf "$tmp_dir"
 
   # Best-effort: also copy into the Debian rootfs so `btch` works when
@@ -147,22 +162,27 @@ EOF
     chmod 755 "$rootfs/usr/local/bin/${BINARY_NAME}" 2>/dev/null || true
   fi
 
-  # 4) Wrapper: bind-mount ~/.btch/bin into Debian and run the binary there,
-  #    so `btch` works from Termux even if the rootfs lives elsewhere.
+  # 4) Wrapper: bind-mount ~/.btch/runtime into Debian and run the binary
+  #    there. The wrapper lives at $PREFIX/bin/btch (already on PATH), so
+  #    typing `btch` finds the wrapper, not the glibc binary.
   #    `uninstall` is handled here in Termux (the binary runs inside Debian
   #    with HOME=/root, so it cannot see Termux's install.json).
   local wrapper="${PREFIX}/bin/btch"
   cat > "$wrapper" <<WRAPPER
 #!${PREFIX}/bin/bash
 if [[ "\${1:-}" == "uninstall" ]]; then
-  rm -f "${INSTALL_DIR}/btch"
+  rm -f "${RUNTIME_DIR}/btch"
   rm -f "${wrapper}"
   rm -rf "${USER_DIR}"
   echo "btch uninstalled."
   echo "To also remove the Debian environment, run: proot-distro remove debian"
   exit 0
 fi
-exec proot-distro login --bind "${INSTALL_DIR}:/usr/local/btch" debian -- /usr/local/btch/btch "\$@"
+if ! proot-distro login --bind "${RUNTIME_DIR}:/usr/local/btch" debian -- /usr/local/btch/btch "\$@"; then
+  echo "btch failed to start inside Debian." >&2
+  echo "Make sure your Debian environment is working: proot-distro login debian" >&2
+  exit 1
+fi
 WRAPPER
   chmod 755 "$wrapper"
 
@@ -181,8 +201,8 @@ WRAPPER
   "installMethod": "script",
   "version": "$(json_escape "$RESOLVED_VERSION")",
   "repo": "$(json_escape "$REPO")",
-  "binaryPath": "$(json_escape "${INSTALL_DIR}/${BINARY_NAME}")",
-  "installDir": "$(json_escape "$INSTALL_DIR")",
+  "binaryPath": "$(json_escape "${RUNTIME_DIR}/${BINARY_NAME}")",
+  "installDir": "$(json_escape "$RUNTIME_DIR")",
   "assetName": "$(json_escape "$ASSET_NAME")",
   "target": "android-arm64",
   "installedAt": "$(date -u +"%Y-%m-%dT%H:%M:%SZ")",
@@ -199,6 +219,8 @@ METAEOF
   echo "Run:"
   echo "  btch --help"
   echo ""
+  echo "If 'btch' is not found right away, run: hash -r"
+  echo ""
   echo "To uninstall later:"
   echo "  btch uninstall"
   echo "  proot-distro remove debian   # optional: also remove the Debian environment"

package.json

@@ -1,6 +1,6 @@
 {
   "name": "btch-cli",
-  "version": "3.0.14",
+  "version": "3.0.15",
   "description": "An open-source AI coding agent, built with Bun and OpenTUI.",
   "type": "module",
   "main": "dist/index.js",