docs: enhance just setup-ai instructions with detailed explanation

[cmungall]

Fixes #12

Added comprehensive documentation explaining what just -f ai.just setup-ai does:

• Documented AI agent configuration step (symlink creation for Claude, Goose, Copilot)
• Documented GitHub repository setup step (topics and secrets configuration)
• Improved formatting with code blocks and clear task breakdown
• Enhanced context about when to run the command (after running copier)

Generated with Claude Code

[claude]

Claude finished @cmungall's task —— View job

---

PR Review: Documentation Enhancement

Tasks:

• Read and analyze the changed README.md file
• Review documentation quality, clarity, and technical accuracy
• Check formatting, grammar, and structure
• Provide comprehensive review feedback

---

Review Feedback

This PR significantly improves the documentation for the just -f ai.just setup-ai command. The changes are well-structured and provide valuable clarity for users.

✅ Strengths

1. Clear Command Structure: The addition of proper bash code block formatting for the command makes it much more readable and copy-paste friendly.

2. Comprehensive Task Breakdown: The two-step breakdown (AI Agent Configuration and GitHub Repository Setup) clearly explains what the command accomplishes.

3. Technical Accuracy: The documented symlink creation and repository configuration steps align with typical AI agent setup patterns.

4. Improved Context: The enhanced introduction properly sets expectations about when to run this command (after copier and environment setup).

5. Good Formatting: Proper use of markdown formatting with code blocks, numbered lists, and bullet points enhances readability.

📝 Minor Suggestions

1. Line 106: Consider adding a brief explanation of why symlinks are used instead of file copies (e.g., "for consistent agent instructions across different AI tools").

2. Line 112: The repository topics could benefit from a brief explanation of their purpose (e.g., "for project discoverability and categorization").

3. Consider adding: A note about required permissions or potential failure scenarios (e.g., if environment variables are missing).

🔍 Technical Review

• No Security Concerns: Documentation-only changes with no security implications
• No Performance Impact: Documentation changes don't affect runtime performance
• No Test Coverage Needed: Documentation improvements don't require automated testing
• No Code Quality Issues: Well-structured markdown with consistent formatting

📋 Summary

This is an excellent documentation improvement that addresses issue #12 effectively. The changes transform a minimal command reference into comprehensive setup instructions that will significantly help users understand the setup process.

Recommendation: ✅ Approve - This PR enhances user experience without introducing any risks.

---