Reduce maxLogLength to optimize token usage

[efp-dev-ops]

This PR reduces the maxLogLength from 50,000 to 25,000 characters (half of the previous value) as requested in issue #5.

Changes Made

• Updated maxLogLength constant in src/services/ai-analyzer.ts:116 from 50000 to 25000

Impact

• Reduces token usage in AI analysis calls
• May help with rate limiting and API costs
• Logs longer than 25,000 characters will be truncated with ... (logs truncated) suffix

Resolves #5

Generated with Claude Code

[0xthrpw]

@efp-dev-ops if we merge this change, are you capable of updating the releases with this change as "v1.0.3" and a corresponding tag?

[efp-dev-ops]

Claude finished @0xthrpw's task —— View job

---

Release Management Capability Assessment

• Analyze current version setup and release process
• Explain release management capabilities
• Provide recommended approach for v1.0.3 release

Current State Analysis

I can see that:

• Current version in package.json is 1.0.0
• Recent commit mentions bumping to review@v1.0.2
• No existing Git tags are present in the repository
• The project uses npm/Node.js with TypeScript

My Release Management Capabilities

What I CAN do:

• ✅ Update version numbers in package.json and other version files
• ✅ Create Git commits with version changes
• ✅ Create and push Git tags (e.g., v1.0.3)
• ✅ Push changes to branches
• ✅ Update CHANGELOG files if they exist

What I CANNOT do:

• ❌ Create GitHub Releases (the UI releases with release notes)
• ❌ Publish to npm registry (requires npm credentials)
• ❌ Run advanced GitHub CLI commands (limited permissions)

Recommended Approach for v1.0.3

Yes, I am capable of handling the version update to v1.0.3 and creating the corresponding Git tag!

Here's what I can do for you:

1. After this PR is merged, I can:

   • Update package.json version from 1.0.0 to 1.0.3
   • Create a Git tag v1.0.3
   • Commit and push the changes

2. What you would need to handle:

   • Creating the GitHub Release manually via the GitHub web interface (or I can help guide you through this process)
   • Publishing to npm if desired

Would you like me to prepare these version updates now, or wait until after the PR is merged? I can handle the technical parts of the release process for you.