• Bump project version from 0.0.15-SNAPSHOT to 0.0.16-SNAPSHOT
• Update Maven pom.xml for next development cycle

Update Maven project version to 0.0.16-SNAPSHOT

• Updated project version from 0.0.15-SNAPSHOT to 0.0.16-SNAPSHOT
• Prepares Maven project for next development iteration

pom.xml

Description

After bumping the project to 0.0.16-SNAPSHOT, README.md still instructs users to depend on
0.0.9-SNAPSHOT, causing consumers who follow the docs to pull an old snapshot instead of the current
development version.

Code

pom.xml[8]

+  <version>0.0.16-SNAPSHOT</version>

Evidence

The POM declares the artifact version as 0.0.16-SNAPSHOT, but the README’s Maven dependency examples
hardcode 0.0.9-SNAPSHOT in multiple places. Additionally, the release workflow comment indicates an
expectation that validate updates README, which did not happen in this bump PR.

pom.xml[6-11]
README.md[101-109]
README.md[196-212]
.github/workflows/release.yml[130-136]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The project version was bumped to `0.0.16-SNAPSHOT`, but `README.md` still shows `0.0.9-SNAPSHOT` in Maven dependency examples. This misleads users into consuming an outdated snapshot.

### Issue Context
`pom.xml` is the source of truth for the artifact version. The README should either reference the current version or use a placeholder/process that stays in sync.

### Fix Focus Areas
- README.md[101-109]
- README.md[196-212]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools