chore(release): move main on to 5.2.0-SNAPSHOT

[bernardladenthin]

Summary

main was still carrying 5.1.0, a version published on Central since 2026-08-29 — verified, not assumed: llama-parent, llama, llama-langchain4j and llama-kotlin all return HTTP 200 at 5.1.0. Leaving main there is exactly what the forward bump exists to prevent: a snapshot deploy collides with a released coordinate, and anyone building from main produces artifacts indistinguishable from the release.

• mvn versions:set -DnewVersion=5.2.0-SNAPSHOT -DgenerateBackupPoms=false — the four poms (root, llama, llama-langchain4j, llama-kotlin). llama-android needs no edit: its Gradle build parses the version out of the poms at configure time, which is the whole reason it was built that way.
• One doc change, and it was already stale before this bump. The "Snapshot builds" section advertised 5.0.7-SNAPSHOT as the snapshot channel — a version that never shipped, since 5.1.0 superseded it. That line tells a reader where to get the current development build, so it moves to 5.2.0-SNAPSHOT.

Every other version literal in the docs stays at 5.1.0 on purpose — they are consumer-facing dependency snippets (README.md, llama-langchain4j/README.md, llama-android/README.md, llama-kotlin/README.md), and what a consumer should depend on is the release.

Test plan

• All four poms carry 5.2.0-SNAPSHOT as project version and parent pointer; git grep "5\.1\.0" -- '*.xml' returns nothing tracked
• CI is green on this branch

No native rebuild is involved — this touches poms and one README line.

Related issues / PRs

Relevant beyond housekeeping: srcmorph's flashAttn knob is currently refused because ModelParameters.enableFlashAttn() cannot express the mandatory [on|off|auto] value llama.cpp has required since b10273. The fix is a value-taking setFlashAttn here, and 5.2.0 is the version that TODO names — so this bump puts main on the version that work will ship in.

Checklist

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

---

Generated by Claude Code

[claude]

✅ Review Summary

This version bump follows the documented process in CLAUDE.md correctly:

Version Changes:

• ✓ All four pom files updated: root pom.xml, llama/, llama-langchain4j/, llama-kotlin/
• ✓ llama-android/ correctly NOT modified (Gradle build parses version from poms)
• ✓ project.build.outputTimestamp updated in llama/pom.xml for reproducible builds
• ✓ Snapshot docs updated: README.md changed from 5.0.7-SNAPSHOT → 5.2.0-SNAPSHOT

Documentation:

• ✓ Consumer-facing dependency snippets intentionally remain at 5.1.0 (the released version)
• ✓ Only the snapshot channel documentation was updated
• ✓ Changelog.md correctly unchanged (historical record)

Correctness:

• ✓ Commit follows Conventional Commits format
• ✓ Rationale is sound: prevents snapshot/release coordinate collision
• ✓ No code changes, only version metadata updates

Approval: This PR is ready to merge. All version references are correctly synchronized per the documented procedure.

[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