Bump reactor to 1.2.0-SNAPSHOT for continued development

[bernardladenthin]

Summary

• v1.1.1 published successfully to Maven Central ("Deploy release" and "Attach Binaries" both green on run 29456928729) — srcmorph, srcmorph-cli, srcmorph-maven-plugin are live at 1.1.1, with the llamacpp-ai-index-maven-plugin relocation stub at 1.0.4 pointing to it.
• Bumps main forward to 1.2.0-SNAPSHOT so it no longer sits at a version matching a published release (a safety net for ongoing development, per request).
• mvn versions:set -DnewVersion=1.2.0-SNAPSHOT -Dexcludes=net.ladenthin:llamacpp-ai-index-maven-plugin for the three real modules. The relocation stub's own <version> stays at 1.0.4; its <relocation><version> target correctly remains 1.1.1 (the real last release) since versions:set doesn't touch that field and there's nothing newer published to point at yet.
• Docs updated carefully to distinguish two different things that both used to read "1.1.1":
  • Now tracks the dev snapshot (1.2.0-SNAPSHOT): CLAUDE.md's reactor-version line and repo-tree diagram, the local-build CLI jar-name examples, README.md's snapshot-builds line.
  • Stays at the real release (1.1.1): the Maven plugin quickstart snippet, the library dependency snippet, and every relocation-target callout — these describe what a consumer should actually depend on / where the stub redirects to, which is still 1.1.1 until the next real release ships.
• TODO.md's step-8/step-9 entries removed — they described the release as "still open"/"the user's own later action", which is now done; kept the still-relevant versions:set exclusion caveat as its own standing note.
• CHANGELOG.md gets a fresh, empty [Unreleased] section above [1.1.1].

Test plan

• Reactor version confirmed 1.2.0-SNAPSHOT; stub's own version confirmed still 1.0.4; stub's <relocation> target confirmed still net.ladenthin:srcmorph-maven-plugin:1.1.1
• Full repo-wide sweep of every 1.1.1/1.2.0 mention, classified as "real release" vs "dev snapshot" and verified each is on the correct side
• mvn clean verify from repo root — BUILD SUCCESS
• CI green on this branch (pending)

Related issues / PRs

Follow-up to #144–#147 — opens the next development cycle after the successful v1.1.1 release.

Checklist

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

---

Generated by Claude Code

[coveralls]

Coverage Report for CI Build 29458105050

Coverage remained the same at 90.779%

Details

• Coverage remained the same as the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	2567
Covered Lines:	2404
Line Coverage:	93.65%
Relevant Branches:	925
Covered Branches:	766
Branch Coverage:	82.81%
Branches in Coverage %:	Yes
Coverage Strength:	3.9 hits per line

---

💛 - Coveralls