chore(build): enforce JaCoCo 80% coverage thresholds (#268)

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: nanotaboada

.claude/commands/pre-commit.md

@@ -3,13 +3,12 @@ Before running the checklist, run `git fetch origin`. If the current branch is b
 Run the pre-commit checklist for this project:
 
 1. Update `CHANGELOG.md` `[Unreleased]` section — add an entry under the appropriate subsection (Added / Changed / Fixed / Removed) describing the changes made, referencing the issue number.
-2. Run `./mvnw clean install` — must succeed with no compilation warnings and all tests passing.
-3. Remind me to open `target/site/jacoco/index.html` to verify coverage after the build completes.
-4. If Docker is running, run `docker compose build` — must succeed with no
+2. Run `./mvnw clean install` — must succeed with no compilation warnings, all tests passing, and the JaCoCo check reporting `All coverage checks have been met.` (80% instruction and branch coverage enforced by the build).
+3. If Docker is running, run `docker compose build` — must succeed with no
    errors. Skip this step with a note if Docker Desktop is not running.
-5. If `coderabbit` CLI is installed, run `coderabbit review --type uncommitted --prompt-only`:
+4. If `coderabbit` CLI is installed, run `coderabbit review --type uncommitted --prompt-only`:
    - If actionable/serious findings are reported, stop and address them before proposing the commit.
    - If only nitpick-level findings, report them and continue to the commit proposal.
    - If `coderabbit` is not installed, skip this step with a note.
 
-Run steps 1–4, report the results clearly, then run step 5 (CodeRabbit review) if available, then propose a branch name and commit message for my approval using the format `type(scope): description (#issue)` (max 80 chars; types: `feat` `fix` `chore` `docs` `test` `refactor` `ci` `perf`). Do not create the branch or commit until I explicitly confirm.
+Run steps 1–3, report the results clearly, then run step 4 (CodeRabbit review) if available, then propose a branch name and commit message for my approval using the format `type(scope): description (#issue)` (max 80 chars; types: `feat` `fix` `chore` `docs` `test` `refactor` `ci` `perf`). Do not create the branch or commit until I explicitly confirm.

pom.xml

@@ -310,6 +310,31 @@
                             <goal>report</goal>
                         </goals>
                     </execution>
+                    <execution>
+                        <id>check</id>
+                        <goals>
+                            <goal>check</goal>
+                        </goals>
+                        <configuration>
+                            <rules>
+                                <rule>
+                                    <element>BUNDLE</element>
+                                    <limits>
+                                        <limit>
+                                            <counter>INSTRUCTION</counter>
+                                            <value>COVEREDRATIO</value>
+                                            <minimum>0.80</minimum>
+                                        </limit>
+                                        <limit>
+                                            <counter>BRANCH</counter>
+                                            <value>COVEREDRATIO</value>
+                                            <minimum>0.80</minimum>
+                                        </limit>
+                                    </limits>
+                                </rule>
+                            </rules>
+                        </configuration>
+                    </execution>
                 </executions>
             </plugin>
         </plugins>