Fix fraction dropping leading zeros

[DavidMStraub]

No description provided.

[Copilot]

Pull request overview

This PR fixes incorrect handling of fractional seconds where leading zeros were being dropped (e.g., interpreting .05 as .5) by preserving the fraction digits verbatim as a string throughout parsing and conversions.

Changes:

• Change types.Time.fraction from int | None to str | None and document why the digits are preserved verbatim.
• Update _cast_time to keep the captured fraction substring instead of casting it to int.
• Update and extend tests to ensure fraction width/leading zeros are preserved and remain semantically significant.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
gedcom7/types.py	Updates Time.fraction type to `str
gedcom7/cast.py	Preserves the fraction group as a string when casting time values.
test/test_util.py	Updates fraction inputs to strings and adds a test asserting leading-zero significance.
test/test_cast.py	Updates time-casting expectations and adds a test for preserving fraction text width.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.