Add development environment selection to installer

[ryanmac]

Summary

• Added development environment selection to the installer for better user onboarding
• Provides tailored instructions based on whether users prefer Conductor app, Terminal, or IDE
• Improves UX for Conductor app users who don't need the terminal workflow

Changes

1. Environment Selection Menu

Users now see:

🖥️  Select your primary development environment:

  1) Conductor (https://conductor.build - macOS only)
  2) Terminal (Warp, iTerm2, Windows Terminal, etc.)
  3) IDE (Cursor, Cline, Windsurf, VSCode, etc.)

2. Conductor App Flow

For Conductor users (macOS only):

• Direct instructions to open Conductor app
• Add workspace instructions
• Sample prompt: "Check available tasks and start working on the highest priority one."
• No bootstrap script execution needed
• Pro tips about Conductor's features

3. Terminal/IDE Flow

For Terminal and IDE users:

• Traditional bootstrap script flow
• Option to start dev agent immediately
• Same stash handling for uncommitted changes
• Contextual messaging based on choice

4. Contextual Final Messages

• Terminal/IDE users see full command reference
• Conductor users see simplified completion message
• Both get documentation links and issue reporting info

Benefits

• Better UX: Conductor app users get a streamlined experience without terminal commands
• Clear Guidance: Each environment type gets appropriate instructions
• Platform Aware: Detects macOS for Conductor app availability
• Maintains Compatibility: Terminal/IDE users get the same experience as before

Test plan

• Test installer with Conductor choice on macOS
• Test installer with Conductor choice on non-macOS (should redirect)
• Test installer with Terminal choice
• Test installer with IDE choice
• Verify bootstrap script runs correctly for Terminal/IDE
• Verify contextual messages display correctly

🤖 Generated with Claude Code