Implement full CHANGE_DATE structure support

[AdamIsrael]

Summary

Implements complete GEDCOM 5.5.1 CHANGE_DATE structure support across all record types, including DATE, TIME, and NOTE fields.

Motivation

Previously, CHANGE_DATE implementation was inconsistent:

• Some record types only captured the DATE value, discarding TIME and NOTE
• SourceRecord and NoteRecord skipped CHANGE_DATE parsing entirely

This PR brings full GEDCOM 5.5.1 compliance for change tracking metadata.

Changes

New Type

• Created ChangeDate struct with date, time, and notes fields
• Comprehensive parser with 11 unit tests covering all scenarios

Updated Record Types

All 7 GEDCOM record types now use Option<ChangeDate>:

• ✅ Individual records
• ✅ Family records
• ✅ Submitter records
• ✅ Repository records
• ✅ Multimedia records
• ✅ Source records (previously skipping CHAN entirely)
• ✅ Note records (previously skipping CHAN entirely)

Testing

• Added comprehensive tests for TIME and NOTE field parsing
• Updated all existing tests to work with new ChangeDate struct
• All 266 tests passing (212 unit + 8 main + 25 edge + 21 integration)

Documentation

• Updated ROADMAP.md to reflect full CHANGE_DATE support
• Changed status from "basic parsing" to "full support: DATE, TIME, NOTE"

Breaking Changes

⚠️ Breaking API Change: The change_date field type changed from Option<String> to Option<ChangeDate> across all record types.

This is acceptable as confirmed with the maintainer - there are no users yet.

Verification

• ✅ All 266 tests pass
• ✅ No clippy warnings (cargo clippy -- -D warnings)
• ✅ Code properly formatted (cargo fmt)
• ✅ Successfully builds

Example

Before:

pub change_date: Option<String>  // Only DATE value

After:

pub change_date: Option<ChangeDate>  // Full structure

CHANGE_DATE Structure Now Captures:

n CHAN
  +1 DATE <value>      ✅ Captured
    +2 TIME <value>    ✅ Captured (was discarded)
  +1 NOTE <value>      ✅ Captured (was discarded)

[Copilot]

Pull request overview

This PR implements complete GEDCOM 5.5.1 CHANGE_DATE structure support across all record types by introducing a dedicated ChangeDate struct that captures DATE, TIME, and NOTE fields. Previously, some records only stored the DATE value as a string, while SourceRecord and NoteRecord skipped CHANGE_DATE parsing entirely.

Key Changes:

• Created new ChangeDate struct with comprehensive parsing logic and 11 unit tests
• Updated all 7 GEDCOM record types to use Option<ChangeDate> instead of Option<String>
• Enhanced documentation to reflect full CHANGE_DATE support

Reviewed changes

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

Show a summary per file

File	Description
src/types/change_date.rs	New file implementing ChangeDate struct with parser supporting DATE, TIME, and NOTE fields
src/types/mod.rs	Added ChangeDate module and export
src/types/submitter.rs	Replaced manual CHAN parsing with ChangeDate::parse call and updated tests
src/types/source_record.rs	Replaced CHAN skip logic with ChangeDate::parse and updated field type
src/types/repository_record.rs	Replaced basic DATE extraction with full ChangeDate::parse
src/types/note_record.rs	Replaced CHAN skip logic with ChangeDate::parse
src/types/multimedia_record.rs	Replaced basic DATE extraction with full ChangeDate::parse
src/types/individual/individual.rs	Replaced manual CHAN parsing with ChangeDate::parse and added test for NOTE field
src/types/family.rs	Replaced basic DATE extraction with full ChangeDate::parse and added test for NOTE field
src/main.rs	Updated integration tests to work with new ChangeDate struct
docs/ROADMAP.md	Updated CHANGE_DATE status from "basic parsing" to "full support" across all record types

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.