fix(installer): Add symlink support for custom PAI_DIR skill discovery

[banjoey]

Summary

Claude Code natively scans ~/.claude/skills/ for skills, but users with custom PAI_DIR settings (e.g., ~/PAI) couldn't have their skills auto-discovered. This fix:

• Updates the installer to use config.installDir instead of a hardcoded path
• Detects when PAI_DIR differs from ~/.claude and explains the skill discovery issue
• Offers to create a symlink from ~/.claude/skills → $PAI_DIR/skills
• Handles edge cases (existing symlinks, directories, conflicts)
• Updates INSTALL.md with a symlink question and creation step
• Updates VERIFY.md with symlink verification checklist and script
• Changes the default from ~/.config/pai to ~/.claude to match Claude Code's native path

Problem

When PAI_DIR is set to something other than ~/.claude, skills are installed to $PAI_DIR/skills/ but Claude Code only looks in ~/.claude/skills/ natively. This meant skills wouldn't be auto-discovered, leading to confusion about why skill routing wasn't working.

Solution

The installer now:

1. Detects if PAI_DIR differs from ~/.claude
2. Explains the Claude Code skill discovery behavior
3. Offers to create a symlink to bridge the gap
4. Provides manual instructions if the user declines

Test Plan

• Fresh install with default PAI_DIR (no symlink needed)
• Fresh install with custom PAI_DIR - accept symlink creation
• Fresh install with custom PAI_DIR - decline symlink, verify manual instructions shown
• Update mode preserves existing settings
• Symlink creation handles existing directory at target path
• Symlink creation handles existing symlink pointing elsewhere
• VERIFY.md script correctly reports symlink status

🤖 Generated with Claude Code

[peterlynch]

Naturally I wanted to isolate PAI from claude and the docs lead AI and me to believe PAI_DIR was the way.

I hit the problem described myself and thought I must be holding it wrong :)

[kaimagnus]

Thank you for the custom PAI_DIR symlink support, @banjoey! Smart approach to supporting non-default install locations.

v3.0 completely overhauled the installer and the Bundles/ and Packs/ directories no longer exist. Closing as the target paths no longer match. If you'd like to adapt this for the v3.0 installer, we'd welcome it!