No working installation path exists for new users; update mechanism is broken and documentation is misleading.

Title: [CRITICAL] No working installation path exists for new users; update mechanism is broken and documentation is misleading.

Labels: bug, critical, installer, release-pipeline, documentation

Body:

Summary

There is a critical flaw in the current release and installation pipeline that prevents all new users from successfully installing the latest, auto-updating version of the Claude Code CLI.

The official documentation at https://docs.anthropic.com/en/docs/claude-code/setup is misleading. It claims the tool "automatically keeps itself up to date," but methodical testing proves this is not true for any available installation path.

This creates a frustrating user journey where both the "Standard" and "Alternative" installation methods lead to a broken or permanently outdated state.

Evidence from Methodical Testing on a Clean System

Path 1: The "Standard" npm Installation

This is the method recommended first in the documentation.

$ npm install -g @anthropic-ai/claude-code
# Installs the LATEST version (v1.0.44)
$ claude doctor
# -> Currently running: npm-global (1.0.44)
# -> Auto-updates: No
# -> Recommendation: Run '/migrate-installer'

• Problem: The default installation path directly contradicts the documentation's promise of auto-updates. It provides the latest code but with a non-functional update mechanism, forcing the user to take corrective action immediately.

Path 2: The "Alternative" curl Script Installation

This is presented as an "Alpha" method in the documentation.

$ curl -fsSL claude.ai/install.sh | bash
# Installs an OLDER "stable" version (v1.0.38)
$ claude doctor
# -> Currently running: native (1.0.38)
# -> Auto-updates: Yes

• Problem: This path seems to provide a working updater. However, this is also misleading, as the update mechanism is broken.

The Critical Flaw: The "Working" Updater is Stuck on an Old Version

When attempting to manually update the "native" installation from Path 2, the tool fails to find the actual latest version available on npm.

$ claude --version
# -> 1.0.38 (Claude Code)
$ claude update
# -> Claude Code is up to date (1.0.38)

• Conclusion: The auto-update mechanism for the stable channel (used by the curl script and the post-migration installer) is pointing to a dead end. It is unaware of version 1.0.44 and incorrectly reports that 1.0.38 is the latest version. This means the "Auto updates" feature promised in the documentation does not currently function correctly for any new user.

Impact

1. Broken User Trust: The documentation makes a promise ("Claude Code automatically keeps itself up to date") that is demonstrably false for all installation paths.
2. User Segmentation: Users are unknowingly fragmented between a broken v1.0.44 installation and a permanently outdated v1.0.38 installation.
3. Critical Failure: There is no path for new users to receive new features, bug fixes, or security patches automatically.

Recommended Immediate Actions

1. Fix the Update Channel: The server-side pointer for the stable update channel must be updated to point to the actual latest version (1.0.44). This is the highest priority fix, as it will allow the auto-updater to function correctly for users who chose the curl path.
2. Update the Documentation:

• The curl script method should be promoted to the primary "Standard Installation" as it provides the only path to a correctly configured (even if temporarily outdated) auto-updater.
• The npm install -g method should be deprecated or clearly marked as a "bootstrap-only" method that requires an immediate migration step.
• The documentation must be updated to be transparent about the temporary version lag between the stable and latest channels until this process is streamlined.