[bpamiri]

Summary

Moves the develop pin to wheels-dev/LuCLI 0.6.2.4 (release). It is 0.6.2.3 plus dependency updates (LuCLI#30, ported from upstream cybersonic/LuCLI#157): Jackson 2.18.11, JLine 3.30.15, and the transitive Tomcat (9.0.121) and Commons Lang (3.18.0) jars on the CLI's classpath. No behaviour change is intended.

• tools/lucli.json: version 0.6.2.4 and the published sha256s (they match the release's checksums_sha256.txt). The CI setup-lucli action, the Linux packaging and distribution-install-smoke read this file.
• changelog.d/lucli-0-6-2-4.changed.md.
• tools/lucli-tested.json is unchanged: the 4.2 line stays on 0.6.2.3 until it is tested on 0.6.2.4, and 4.1 stays at max 0.6.2.2.

Verification (sandboxed: own LUCLI_HOME and -Duser.home, real homes inventoried)

• Fork release run: build plus unit/integration tests on Linux/macOS/Windows, then install-validation on both the candidate and the published assets, green on all three OSes.
• Against develop e57ee44, A/B between the published 0.6.2.3 and 0.6.2.4 jars:

Suite	0.6.2.3	0.6.2.4 (published)
core (Lucee 7 + SQLite)	7317 passed	7317 passed
CLI suite	2448 / 0 / 0	2448 / 0 / 0
stdio MCP (wheels mcp wheels)	17 tools, generate type=app refused	same

• The onboarding harness was run on both the candidate and 0.6.2.3, with identical results.
• No writes to the real ~/.wheels, ~/.lucli or ~/.lucee.

🤖 Generated with Claude Code

[bpamiri]

rev1-r3 review @ 407b0fc: APPROVE

The SHA-256s are verified two ways.

• The new values match v0.6.2.4's checksums_sha256.txt: lucli-0.6.2.4-{linux,macos} = 2edbda21d158…, and lucli-0.6.2.4.jar = 3515390bb479….
• I downloaded those three assets and hashed them myself, with the same results.

Provenance.

• The v0.6.2.4 tag points at 4ae9cae, the merge commit of build: prepare fork release 0.6.2.4 LuCLI#31 (the 0.6.2.4 release prep). It is releases/latest, and not a draft or prerelease.
• The jar's lucli/version.properties reads lucli.version=0.6.2.4 and lucli.build.commit=4ae9cae.

Nothing else changes. The PR touches only tools/lucli.json (version plus the three SHAs) and one changelog fragment. tools/lucli-tested.json is untouched, so 4.2 stays on 0.6.2.3 and 4.1 at a maximum of 0.6.2.2 until they're tested. The fragment's wording is neutral (dependency updates, no behaviour change).

PR CI on the new runtime: 17 pass, 2 skipping, 0 fail.

• The CLI jobs install it and check it: LuCLI Version: 0.6.2.4 (sha256 2edbda21d158…).
• The CLI suite runs 2449 passed, 0 failed, 0 errors, in both Lucee 7 + SQLite (LuCLI) and Deploy CLI tests + verb smoke.

Up to date with develop, MERGEABLE.