fix: install pi extension deps on user machine + add doctor command

[glittercowboy]

Summary

Fixes the empty-bubble / $0-cost bug for every macOS user. Adds gsd-cloud doctor for diagnostics.

Root cause: the release workflow ran npm ci --omit=dev on the Linux x64 GitHub runner and shipped the resulting node_modules to every user. The @anthropic-ai/claude-agent-sdk package selects its native binary via optionalDependencies, which only resolves correctly when npm runs on the target machine — so macOS users got the Linux x64 native binary and pi silently failed with "Native CLI binary for darwin-arm64 not found", producing empty assistant messages and $0 cost.

Fix:

1. release workflow stops bundling node_modules in the pi-extension tarball. Ships source + package-lock.json only.

2. install.sh runs npm ci --omit=dev --include=optional on the user's machine after extracting the extension. Each user gets the right platform-native SDK binary. Adds a need_cmd npm check so missing npm fails fast with a clear error.

3. cmd/doctor.go new gsd-cloud doctor command. Checks:

   • claude binary on PATH (with --version)
   • claude is logged in (spawns a trivial prompt, detects "Not logged in")
   • pi binary on PATH
   • pi extension installed with a platform-native claude SDK binary in node_modules
   • machine is paired (config.json present and complete)
   • daemon is running (socket reachable, relay connected)

   Each check prints ✓/✗ with a fix hint. Exits non-zero if any required check fails.

Updated post-install message prompts the user to install Claude Code ("if you don't have it yet") and points to gsd-cloud doctor.

Test plan

• go build ./... clean
• go test ./... all packages pass
• install.sh diff reviewed manually (shellcheck-clean structure, atomic install preserved)
• After merge: cut a release, install on a clean macOS arm64 machine, run gsd-cloud doctor, send a chat message, confirm non-zero token usage

Follow-ups (not in this PR)

• Bundle pi CLI itself into the tarball so users don't need a separate npm install -g @mariozechner/pi-coding-agent (228MB consideration — needs design)
• Add post-install CI smoke test that spawns the daemon and asserts a real assistant response (catches this bug class in CI before users)

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features

  • Added gsd-cloud doctor command to perform system diagnostics, verifying prerequisites, authentication status, platform-specific binaries, and daemon connectivity

• Improvements

  • Installer now automatically installs required platform-specific dependencies for the extension; updated setup documentation with additional configuration requirements

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 96c718e5-3a09-4215-8f0e-07dfaf7e4cfa

📥 Commits

Reviewing files that changed from the base of the PR and between e79a147 and 13368ca.

📒 Files selected for processing (3)

• .github/workflows/release-daemon.yml
• cmd/doctor.go
• scripts/install.sh

---

📝 Walkthrough

Walkthrough

The PR defers npm dependency installation from CI packaging to user install time to ensure platform-appropriate native binaries. A new doctor CLI command validates runtime component availability and configuration. The installer script now executes npm ci for platform-specific dependencies and updates post-installation instructions.

Changes

Cohort / File(s)	Summary
Installation Pipeline .github/workflows/release-daemon.yml, scripts/install.sh	Workflow now excludes node_modules from tarball and defers dependency installation. Installer runs npm ci --omit=dev --include=optional in pi-extension directory and adds npm as required command; updates next steps output with Claude Code instructions and gsd-cloud doctor validation step.
Diagnostic Command cmd/doctor.go	New doctor subcommand performs sequential verification checks: claude/pi binary availability, authentication status, pi-extension directory presence, machine pairing configuration validity, and daemon connectivity via socket. Returns per-check reports with fix hints and exits with code 1 on failure.

Sequence Diagram

sequenceDiagram
    actor User
    participant CLI as gsd-cloud doctor
    participant FS as File System
    participant Config as Config System
    participant Daemon as Daemon Socket

    User->>CLI: Invoke doctor command
    CLI->>FS: Check claude binary available
    FS-->>CLI: Found/Not found
    CLI->>FS: Check pi binary runnable
    FS-->>CLI: Runnable/Error
    CLI->>FS: Verify pi-extension directory exists
    FS-->>CLI: Exists/Missing
    CLI->>Config: Load machine pairing config
    Config-->>CLI: Config loaded or validation failed
    CLI->>Daemon: Resolve socket path & query sockapi status
    Daemon-->>CLI: Daemon healthy/Unhealthy
    CLI->>User: Print per-check report or summary

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~30 minutes

Possibly related PRs

• Fix pi provider extension resolution #41: Resolves pi-extension path validation and early error handling; directly complements this PR's packaging/installer changes that alter pi-extension availability and presence verification.

Poem

🐰 npm ci's deferred dance, doctor checks the stance,
Extensions packaged light, binaries checked just right,
Platform-perfect installs bloom, no dependency gloom! ✨

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/install-bundle-and-doctor

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}