aboutsummaryrefslogtreecommitdiff
path: root/lib/kernel/calendar.ml
diff options
context:
space:
mode:
authorLukasz Kasprzak <lukas@labunix.xyz>2026-08-25 19:21:33 +0200
committerLukasz Kasprzak <lukas@labunix.xyz>2026-08-25 19:21:33 +0200
commit8885c9af2f69b81b9aefcf3ab6c4da641338b71d (patch)
treedc4a5a75fbb780c14c1075a38cdd33ba079d779b /lib/kernel/calendar.ml
parentc6faa32c85e350349181ab920b0b8b7defdd678c (diff)
downloadcolitur-8885c9af2f69b81b9aefcf3ab6c4da641338b71d.tar.gz
colitur-8885c9af2f69b81b9aefcf3ab6c4da641338b71d.zip
test(of): pin the Nativity Vigil at entry 3, not entry 9
Fix round 1 (coordinator review). The Nativity Vigil (24 December, Sollemnitas) bands at entry 3 (30) rather than entry 9 (90) as a direct consequence of this task's ruling, but nothing pinned it -- a future branch-reorder (e.g. inserting an entry between 3 and 9, or loosening entry 9's date guard) could silently revert it to 90 with the suite green. Adds one row to part2_cases with a comment recording: the Tabula's own entry 9 textually covers 24 December as a late-Advent feria, yet Phase 1 gives that civil day the of-nativity-vigil identity at Sollemnitas because the Vigil Mass is celebrated that evening -- the same civil-day-granularity shape Holy Thursday already settles (entry 2, not entry 1); Phase 2 classifies Phase 1's emitted identity rather than overriding it. Unobservable on the universal calendar today (no competing candidate on 24 December); live under a proper/diocesan overlay, where a proper solemnity (entry 4, band 40) loses to the Vigil at 30 but would beat it at the textually-arguable 90. No production code change -- test-only, per the coordinator's ruling to pin current behaviour rather than alter it.
Diffstat (limited to 'lib/kernel/calendar.ml')
0 files changed, 0 insertions, 0 deletions