Release v1.4.2

Rollup of v1.4.1 and v1.4.2.

What's Changed

-V short form for --version (v1.4.1)
git-repokit-common integrated as a subtree at scripts/repokit-common/ — shared DazzleTools tooling: sync-versions.py version management, git hooks (pre-commit/post-commit/pre-push), gh_issue_full.py, and more. Update anytime with git subtree pull --prefix=scripts/repokit-common repokit-common main --squash (v1.4.2)
[tool.repokit-common] configuration in pyproject.toml wiring version-source to dazzlesum.py (v1.4.2)

--version printed a stale hook-stamped build string on machines without the git hooks installed (could show 1.3.6 while the package was 1.4.0); it now derives from the semantic version components. Consistency is enforced by a CI-level test rather than runtime fallback code (v1.4.1)

Removed setup.py: fully superseded by pyproject.toml's dynamic version — eliminates the last duplicate version parser and metadata block (v1.4.1)
Version stamping now flows through repokit-common's sync-versions.py; build strings carry branch, build count, current date, and parent hash (the previous hand-rolled hook reused stale date/hash fields) (v1.4.2)
Retired hand-rolled scripts/install-hooks.sh and scripts/hooks/ in favor of the subtree's hook system (v1.4.2)
Version-format test assertions updated for the new stamp shape

pip install dazzlesum

Or clone and pip install -e ., or copy dazzlesum.py standalone (single file, stdlib only).

Full Changelog: v1.4.0...v1.4.2