[lloydsmart]

Summary

• bump the embedded CHDTOOL_VERSION from 0.2.4 to 0.3.0
• prepare the next minor release after the validation, regression, CLI, logging, packaging, and documentation improvements merged since v0.2.5

Release process

This is the release-preparation PR into develop. After it merges and all checks pass, develop must be promoted to main. Tag v0.3.0 only on the resulting merged main commit; pushing that tag will trigger the existing Release workflow to test, package, checksum, publish, and generate the changelog PR.

Preflight validation

• make test
• ShellCheck across chdtool.sh, packaging scripts, tests, and stubs
• make package VERSION=0.3.0 using an isolated distribution directory
• sha256sum --check SHA256SUMS
• exact .tar.gz and .zip manifest inspection
• chdtool.sh --version reports 0.3.0
• git diff --check

[lloydsmart]

Closing this draft because the documented gitflow target was incorrect. After #47 merges, the v0.3.0 release branch will be rebased onto updated develop, renamed to release/v0.3.0, and proposed directly into main.