@domorium/validator 2.0.0 → 2.0.1

package/CHANGELOG.md

@@ -2,6 +2,32 @@
 
 All notable changes to `@domorium/validator` are documented here.
 
+## 2.0.1
+
+- **A 5.5.1 date names its calendar where the specification puts it.** 5.5.1
+  writes the escape inside `<DATE>`, and `<DATE>` comes after the modifier:
+  `ABT <DATE>`, `BET <DATE> AND <DATE>`, `FROM <DATE> TO <DATE>`. The escape was
+  read only at the front of the whole payload, so `ABT @#DHEBREW@ TSH 5760` and
+  a Julian `FROM`/`TO` range were reported as invalid dates, while
+  `@#DJULIAN@ FROM 1 JAN 1700 TO 1 JAN 1710`, which the grammar does not admit,
+  passed. Each `<DATE>` now carries its own calendar and is read in
+  that calendar's months, so a range may cross calendars and neither half is
+  read in the other's vocabulary.
+- **An exact date is Gregorian, and says so.** `DATE_EXACT` is
+  `<DAY> <MONTH> <YEAR_GREG>` with no slot for a calendar, but the escape was
+  stripped before the grammar ran, so `1 CHAN` / `2 DATE @#DHEBREW@ 1 TSH 5760`
+  validated clean — where the GEDCOM 7 rule for the same payload rejects it. The
+  two dialects agreed on every other date rule and disagreed on this one.
+- **A day is measured against the calendar its own date names.** A calendar binds
+  to the date that follows it, which is what `FROM JULIAN 1670 TO 1800` says: two
+  dates, two calendars. The day-length check set the calendar once and carried it
+  to the end of the payload, so `FROM JULIAN 1 JAN 1700 TO 29 FEB 1900` reported
+  nothing — the second date is Gregorian, 1900 is not a Gregorian leap year, and
+  it was measured by the Julian rule, which has no exception for a century. The
+  same leading calendar suppressed the check for every later date in a range.
+  Each word that ends one date and begins the next now returns the calendar to
+  Gregorian, so a date names its own or is read as Gregorian.
+
 ## 2.0.0 - 2026-08-20
 
 Removes three members of `GedcomDocument` that no consumer read, which is what