fix: set major_on_zero=false and allow_zero_version=true for consistency

Reviewer feedback: this should be set across the whole batch, not just
repos currently on 0.x, so no repo in this effort can ever auto-jump to
1.0.0 as an accidental side effect if it's reset to 0.x in the future.
Note this is a no-op for repos already past 1.0 -- major_on_zero only
governs the 0.x -> 1.0.0 transition, not 1.x -> 2.0.0 (there's no PSR
setting that suppresses major bumps once past 1.0; that's normal SemVer
behavior for a breaking-change commit at any version).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Author: 2 people

pyproject.toml

@@ -113,6 +113,11 @@ fallback_version = "0.0.0.dev0"
 # wouldn't recognize any prior release and would restart versioning from scratch.
 tag_format = "{version}"
 build_command = "pip install build && SETUPTOOLS_SCM_PRETEND_VERSION=$NEW_VERSION python -m build"
+# Already past 1.0 (1.8.x), so major_on_zero is a no-op today -- it only governs
+# the 0.x -> 1.0.0 transition, not 1.x -> 2.0.0. Set for consistency across the
+# batch and so this repo never auto-jumps to 1.0.0 if it's ever reset to 0.x.
+major_on_zero = false
+allow_zero_version = true
 
 [tool.uv]
 # Every `uv sync`/`uv run` invocation in this repo names an explicit --group.