docs: add background section to README with AI GitHub Actions overview

[cmungall]

Addresses issue #1 by adding comprehensive background information about AI GitHub Actions to the README.

Changes:

• Added new "Background" section with AI GitHub Actions overview
• Included key benefits, architecture, and cost considerations
• Added prerequisites and important usage warnings
• Enhanced context from ai4curation documentation

Generated with Claude Code

[claude]

Claude finished @cmungall's task —— View job

---

PR Review Progress

• Read and analyze the README.md changes
• Review documentation quality and accuracy
• Check for potential improvements
• Provide comprehensive feedback

PR Review: Documentation Quality and Recommendations

This PR adds a well-structured "Background" section to the README that significantly improves the project's documentation. Here's my detailed review:

✅ Strengths

Content Quality:

• Clear, comprehensive overview of AI GitHub Actions functionality
• Well-organized structure with logical flow from benefits to architecture to considerations
• Appropriate warning about costs (line 23) - important for user awareness
• Good use of formatting (headers, bullet points, warning emoji)

Technical Accuracy:

• Accurate description of the GitHub Actions trigger mechanism
• Correct representation of AI provider integrations
• Proper mention of configuration files (.config/goose/config.yaml, .goosehints)

User Experience:

• Prerequisites section helps users understand requirements upfront
• Links to external documentation provide additional context
• Maintains the existing "meta" explanation about dogfooding

🔍 Minor Suggestions for Improvement

1. Typo in Environment Variable (line 62):

   CLAUDE_CODE_OATH_TOKEN
   

   Should likely be CLAUDE_CODE_OAUTH_TOKEN (OAuth, not Oath)

2. Consider Adding Examples:
   The Background section would benefit from a brief example of what a user interaction might look like (e.g., "Comment '@claude fix this bug' on an issue")

3. Cost Management Guidance:
   While the cost warning is good, consider adding a brief note about monitoring or rate limiting strategies

4. Architecture Details:
   Consider mentioning which events specifically trigger the workflows (issues, PRs, comments) in the Architecture section for clarity

📊 Review Assessment

• Code Quality: N/A (documentation only)
• Potential Bugs: One typo identified (OATH vs OAUTH)
• Performance: N/A (documentation only)
• Security: Good practice with clear prerequisites and cost warnings
• Test Coverage: N/A (documentation only)

🎯 Overall Assessment

This is a high-quality documentation addition that addresses issue #1 effectively. The Background section provides valuable context for new users and helps them understand both the benefits and responsibilities of using AI GitHub Actions. The only concern is the potential typo in the environment variable name.

Recommendation: ✅ Approve with minor fix - Consider correcting the OATH_TOKEN typo before merging.