Bug Description

forge update fails with a 404 error when attempting to download the new binary. The install script served at https://forgecode.dev/cli (which forge update invokes) still constructs download URLs using the old repository name tailcallhq/forge, but the repo has been renamed to tailcallhq/forgecode. GitHub does not redirect /releases/ URLs for renamed repositories.

Steps to Reproduce

1. Have Forge v2.9.3 installed
2. Run forge update
3. Confirm upgrade to v2.9.7

Expected Behavior

Binary downloads from https://github.com/tailcallhq/forgecode/releases/... and updates successfully.

Actual Behavior

Downloading Forge from https://github.com/tailcallhq/forge/releases/latest/download/forge-x86_64-unknown-linux-gnu...
curl: (22) The requested URL returned error: 404
curl: (22) The requested URL returned error: 404
Failed to download Forge.

Root Cause

The install script at https://forgecode.dev/cli hardcodes the old repo name in the download URL construction:

DOWNLOAD_URLS="https://github.com/tailcallhq/forge/releases/latest/download/forge-$TARGET$TARGET_EXT"

GitHub does not follow redirects for release asset URLs on renamed repos:

Additionally, the error message in the script still references the old repo:

printf "${BLUE}https://github.com/tailcallhq/forge#installation${NC}\n"

Suggested Fix

Replace all occurrences of tailcallhq/forge with tailcallhq/forgecode in:

1. Install script (https://forgecode.dev/cli) — the DOWNLOAD_URLS variable and the installation instructions URL
2. update-informer configuration in the Rust binary — the GitHub repo reference used for update checks

Workaround

Manually download and replace the binary:

curl -L -o ~/.local/bin/forge \
  "https://github.com/tailcallhq/forgecode/releases/download/v2.9.7/forge-x86_64-unknown-linux-gnu" \
  && chmod +x ~/.local/bin/forge

Environment

• Forge version: 2.9.3
• OS: Linux x86_64 (Ubuntu)
• Install method: curl -fsSL https://forgecode.dev/cli | sh