[lolgab]

Summary

• Bumps scalaVersion/scalaBinaryVersion to 2.13, drops cross-building and 2.12-only compiler flags.
• Fixes 2.13 collection API breakage across core, toolRepository-remote, and cli (breakOut, .to[X], mapValues, parallel collections module).
• Bumps guardrail to 1.0.0-M1 (0.75.2's akka-http codegen emits invalid Scala under 2.13) and pins scalameta to keep the meta-build classpath consistent.
• Bumps case-app to 2.1.0 (no 2.13 build exists below that) and rewrites CLIApp's CLI parsing off the removed case-app 1.x Command/CommandParser API onto the 2.x Parser/Help API. Splits Analyze's option case class into an AdvancedOptions group to stay under case-app's field-count ceiling.

Known issue - cli module does not compile

case-app 2.1.0's Parser/Help derivation macro crashes scalac 2.13 (LambdaLift, NoSuchElementException: key not found: package command) whenever derivation for two or more distinct option case classes happens in the same compiled package. Reproduced in isolation across many code shapes (nested/top-level, generic/non-generic, reduced field count, explicit/automatic derivation) - it is not fixable by restructuring this codebase. Also confirmed on Scala 2.13.18, so it isn't a scalac patch-version bug either.

Since the CLI needs to parse both analyze and validate-configuration, this blocks the cli module specifically. core, model, toolRepository-remote, and codacy-api-client all compile clean on 2.13.

Opening this to see what CI reports; the cli module build is expected to fail until case-app is replaced or the upstream bug is fixed.

Test plan

• CI build (expected: cli module compile failure, other modules green)
• Decide follow-up: replace case-app (scopt/decline) vs. wait on upstream fix

[codacy-production]

Up to standards ✅

🟢 Issues 1 high · 2 minor

Results:
3 new issues

Category	Results
ErrorProne	1 high
Comprehensibility	2 minor

View in Codacy

🟢 Metrics 0 complexity · 4 duplication

Metric	Results
Complexity	0
Duplication	4

View in Codacy

🟢 Coverage 98.13% diff coverage · +5.30% coverage variation

Metric	Results
Coverage variation	✅ +5.30% coverage variation (-0.50%)
Diff coverage	✅ 98.13% diff coverage (50.00%)

View coverage diff in Codacy

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (bd57cda)	Report Missing	Report Missing	Report Missing
Head commit (1635ee5)	738 (-547)	641 (-407)	86.86% (+5.30%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#557)	107	105	98.13%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

¹ Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

⚠️ Resolve issues before merging

The CLI does not compile under Scala 2.13 because the parser derivation still fails, so the migration is not usable as submitted. The top-level --help and -h flags also regress to an unknown-command error.

Several required build and CLI validation scenarios are missing, including successful compilation, removal of Scala 2.12 references, command parsing, error handling, and command execution.

Codacy also found:

• CLI complexity increased and four duplication findings were reported.
• CLI coverage is approximately 47%, including reduced changed-line coverage.
• An informational method-length finding was reported in Tool.run.

Test suggestions

• Compile all project modules successfully with Scala 2.13.
• Verify the build no longer cross-builds or references Scala 2.12 artifacts.
• Exercise migrated collection conversions and map transformations in core, CLI, and toolRepository-remote.
• Parse valid analyze and validate-configuration command arguments.
• Handle CLI version, help, unknown commands, invalid arguments, and malformed duration/commit UUID values.
• Verify CLI analysis and configuration command execution after the parser migration.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Compile all project modules successfully with Scala 2.13.
2. Verify the build no longer cross-builds or references Scala 2.12 artifacts.
3. Parse valid analyze and validate-configuration command arguments.
4. Handle CLI version, help, unknown commands, invalid arguments, and malformed duration/commit UUID values.
5. Verify CLI analysis and configuration command execution after the parser migration.

Make this review better

_{TIP Add Codacy review.md instructions or an AGENTS.md so the reviewer knows your conventions.}

_{TIP How was this review? Give us feedback}

[codacy-production]

_{🔴 HIGH RISK}

The CLI still relies on parser derivation that fails under Scala 2.13, leaving this module uncompilable. Replace the failing parser dependency or provide a compiling implementation before considering the migration complete.

_{TIP React 👍 if this review is right, or reply with what's wrong and how it could be better to help improve the reviewer.}

[codacy-production]

_{🟡 MEDIUM RISK}

Top-level --help and -h are rejected as unknown commands instead of displaying CLI help. Handle these flags before the unknown-command branch and add regression coverage.

_{TIP React 👍 if this review is right, or reply with what's wrong and how it could be better to help improve the reviewer.}