Fix GitHub token configuration for user projects

[ryanmac]

Summary

• Fixes the "Input required and not supplied: github-token" error that users were experiencing
• Updates documentation to clarify that no manual token setup is required
• Ensures proper fallback to built-in GitHub token when custom tokens aren't configured

Problem

Users installing Code Conductor in their projects were getting errors from actions/github-script@v7 because:

1. The pr-review-tasks.yml workflow used ${{ secrets.CONDUCTOR_GITHUB_TOKEN }}
2. When this secret doesn't exist (which is normal for user projects), it becomes an empty value
3. actions/github-script requires the github-token parameter to have a value

Solution

• Updated pr-review-tasks.yml to use ${{ secrets.CONDUCTOR_GITHUB_TOKEN || github.token }}
  • Falls back to the built-in token if the custom secret doesn't exist
  • Maintains backward compatibility for projects that have set up the custom token
• Updated CLAUDE.md to clarify that most users don't need any token setup
• Added tests to verify workflow generation uses correct tokens

Test plan

• Run black on all Python files
• Verify tests pass: python tests/test_workflow_generation.py
• Manual testing of workflow execution with and without custom token

Impact

• User projects will work out-of-the-box without token configuration
• Existing projects with custom tokens continue to work as before
• No breaking changes

Fixes the issue reported where GitHub doesn't allow custom secrets with GITHUB_ prefix and users were getting workflow failures.

🤖 Generated with Claude Code

[ryanmac]

Updated PR with comprehensive documentation fixes

I've added additional changes to ensure users clearly understand that no GitHub token setup is required:

Documentation Updates:

1. README.md - Added explicit "No GitHub token setup required!" in 3 key locations:

   • In the Claude Code quick start section
   • After the setup instructions
   • In the troubleshooting section

2. conductor-init.sh - Added clarifications in installation output:

   • "✅ No GitHub token setup required" in the setup complete message
   • Added to Pro Tips: "No GitHub token setup needed—uses built-in authentication"
   • Added to upgrade message: "Token configuration (no manual setup needed)"

Complete Changes in this PR:

• ✅ Fixed pr-review-tasks.yml to fall back to github.token when custom token isn't available
• ✅ Updated CLAUDE.md to remove incorrect token setup instructions
• ✅ Added tests to verify workflow generation uses correct tokens
• ✅ Updated README.md with clear messaging about no token setup required
• ✅ Updated conductor-init.sh installation messages

This ensures users won't encounter the "Input required and not supplied: github-token" error and won't waste time trying to set up tokens they don't need.