gedcom-fidelity-registry

To prevent GEDCOM data loss when modifying a database schema, enforce a round-trip fidelity registry that requires an explicit entry for every authored database field. This mechanically verifies lossless, lossy, or excluded outcomes through CI-backed coverage and automated tests.

GEDCOM round-trip fidelity ensures data integrity by verifying that exported GEDCOM 5.5.1 or 7.0 files re-import without silent data loss. It requires defining exporter and importer ownership to validate post-round-trip values against expected results.

Test GEDCOM import and export for TypeScript schema migrations by seeding values, exporting to GEDCOM, re-importing, and asserting post-round-trip values match registry expectations. CI enforcement blocks schema changes lacking these registry entries.

CI fails on missing GEDCOM fidelity registry entries because it enforces per-column coverage for schema changes. This mechanism blocks code changes that lack explicit lossless, lossless-via, lossy, or excluded declarations and fails when entries don't map to real columns.

Yes, the GEDCOM fidelity registry supports both 5.5.1 and 7.0 standards. It declares per table and column behavior for both formats, ensuring round-trip data integrity across different GEDCOM versions through automated testing.

Exclude a database field from GEDCOM export by marking it as excluded in the registry with a deliberate justification like audit or cache-only usage. The registry supports justified exclusions so reviewers can verify they are documented and intentional.