build: prepare fork release 0.6.2.3

[bpamiri]

Release prep for fork release 0.6.2.3 (FORK.md "Release", step 1). This PR doesn't tag or publish anything.

What 0.6.2.3 ships

wheels @ 959abb0 = v0.6.2.2 + FORK.md rows 8-15, all merged and reviewed: #19, #21, #22, #23, #24, #26, #27, #28.

This PR

• pom.xml → 0.6.2.3. The Windows file/product version follows ${project.version}.
• .github/workflows/install-validation.yml: the default version → 0.6.2.3.
• FORK.md:
  • "Next queue (unreleased)" becomes 0.6.2.3 queue;
  • adds the row-8 compatibility note: a Wheels build must handle __lucliMcpCall before it pins 0.6.2.3. Wheels develop does (wheels#3980); Wheels 4.1.x stays at max 0.6.2.2;
  • adds a new empty "Next queue".
• CHANGELOG.md is unchanged: fork entries stay under ## Unreleased, as they did for 0.6.2.2.

Checks

mvn test with -Duser.home pointed at an empty sandbox: 788 run, 0 failures, nothing written to ~/.lucli.

Next (after merge; nothing is published without the release owner's go)

1. release.yml -f publish=false dry run, then install-validation.yml on the retained assets (Linux, macOS, Windows).
2. Test the candidate against Wheels:
   • develop core suite (Lucee 7 + SQLite);
   • CLI suite;
   • onboarding harness;
   • stdio MCP probes;
   • a 4.1.x spot check.
3. Publish only on the release owner's go.

🤖 Generated with Claude Code

[github-actions]

Integration Tests (ubuntu-latest, Java 21)

78 tests   78 ✅  2m 1s ⏱️
14 suites   0 💤
 1 files     0 ❌

Results for commit a5d5ba5.

♻️ This comment has been updated with latest results.

[github-actions]

Unit Tests (ubuntu-latest, Java 21)

 65 files   65 suites   3m 49s ⏱️
783 tests 777 ✅ 6 💤 0 ❌
788 runs  782 ✅ 6 💤 0 ❌

Results for commit a5d5ba5.

♻️ This comment has been updated with latest results.

[bpamiri]

rev1-r3 review @ a5d5ba5: APPROVE

Release prep for 0.6.2.3. Three files, +12/-4, branch up to date with wheels.

• pom.xml 0.6.2.2 → 0.6.2.3, and the install-validation.yml default → 0.6.2.3. No other 0.6.2.x reference outside FORK.md history and CHANGELOG (unchanged by design, as for 0.6.2.2).
• FORK.md:
  • "Next queue" becomes "0.6.2.3 queue" (rows 8–15), base v0.6.2.2. That tag resolves to b3c01ce, as stated.
  • "(see Release)" resolves to the Release section.
  • A new empty "Next queue" follows.
• The row-8 compatibility note is accurate:
  • v4.1.2 pins LuCLI 0.6.2.1 (tools/lucli.json) and has no __lucliMcpCall handling under cli/lucli.
  • develop handles it (fix(cli): refuse generate type=app over MCP, using LuCLI's tools/call marker wheels#4031, closing #3980).
  • So 4.1.x stays at max 0.6.2.2 unless that fix is backported.

CI on this head, attempt 1: Build macOS/Ubuntu/Windows pass; Unit Tests macOS/Ubuntu/Windows pass (Ubuntu report: 777 pass, 6 skipped); Integration Tests macOS/Ubuntu pass (Ubuntu report: 78/78). APT Install Smoke skipped (not triggered for this change).

Nothing is published by this PR. Tagging still follows the Release runbook after the release owner's go.