Fix Claude API release notes debugging

[gmorpheme]

Summary

Fix the Claude API release notes generation that's currently producing "null" output by adding comprehensive debugging and improving error handling.

Problem

The Claude API integration is failing silently, producing "null" in CHANGELOG.md instead of proper release notes. The API key is present but something in the request/response handling is broken.

Changes Made

• Comprehensive logging: Added step-by-step debugging output to trace the entire process
• Proper JSON escaping: Use jq to create API payload instead of string interpolation to avoid JSON syntax errors
• HTTP status logging: Show the actual HTTP response code from the API
• Full response tracing: Display the complete API response in build logs for debugging
• Improved error handling: Clear success/failure messages and proper fallback logic
• Output verification: Show the final CHANGELOG.md content for validation

Debugging Output

The new workflow will show:

• 🔍 Payload creation status
• 📏 Request size in bytes
• 🚀 API call initiation
• 📥 Complete API response
• ✅/❌ Success/failure status
• 📝 Final generated content

This will help identify whether the issue is authentication, malformed requests, unexpected response format, or parsing problems.

Test Plan

• Test workflow syntax locally
• Trigger release build to see full debugging output
• Analyze API response to identify root cause
• Apply fix based on debugging results

🤖 Generated with Claude Code