docs: add baseline open issues snapshot at commit 49be664

[bernardladenthin]

Summary

• Added docs/history/49be664_open_issues.md documenting all 37 open issues on the upstream kherud/java-llama.cpp repository at the time of fork (baseline commit 49be664)
• Each issue includes its number, title, original URL, reporter, creation date, and a concise summary
• Issues are listed in descending order (newest first) with a cross-reference table for easy categorization
• Provides a baseline for tracking which issues have been fixed, deferred, or closed as not-applicable in this fork

Test plan

N/A — documentation only

Related issues / PRs

None

Checklist

• I have read CONTRIBUTING.md and CODE_OF_CONDUCT.md
• My commits follow Conventional Commits
• No security-sensitive changes

https://claude.ai/code/session_011a3cXj7d6nUkLR8HnWmU6G

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[claude]

Review: Baseline Open Issues Documentation

Thank you for adding this comprehensive issues snapshot. This is valuable documentation for tracking which upstream issues have been resolved or remain relevant in the fork.

✅ Strengths

• Well-organized structure: Issues listed in descending order with consistent formatting
• Comprehensive categorization: The cross-reference table makes issues easy to scan by category
• Clear summaries: Each issue summary is concise and captures the essential problem/request
• Good documentation intent: Provides a clear baseline for tracking resolved vs. deferred issues

⚠️ Issue Found: Date Inconsistency

The header states the baseline commit 49be664 was from 2025-06-20, but several issues in the list were created after that date:

• Upgrade llama.cpp to b9103 and cpp-httplib to v0.44.0 #123 (2025-11-18)
• Upgrade llama.cpp from b9094 to b9102 #121 (2025-10-28)
• chore: migrate CI to unified publish.yml with Sonatype Central Portal #120 (2025-10-12)
• chore(deps): bump actions/download-artifact from 6 to 8 #119 (2025-08-19)
• chore(deps): bump actions/checkout from 4 to 6 #117 (2025-07-10)
• Update Maven configuration for Central Repository publishing #116 (2025-07-01)

This suggests either:

1. The baseline commit date is inaccurate, or
2. The issue snapshot was taken after the baseline commit date

Recommendation: Please verify and correct the baseline commit date in the header to match when the issue snapshot was actually taken. This is important for historical accuracy.