diff options
| author | Lukasz Kasprzak <lukas@labunix.xyz> | 2026-08-12 17:49:46 +0200 |
|---|---|---|
| committer | Lukasz Kasprzak <lukas@labunix.xyz> | 2026-08-12 17:49:46 +0200 |
| commit | 8240dbe8221792510aba2405652b59c22f865957 (patch) | |
| tree | 9d496d01e553a35d1ac885b345ffc7e26e09dcc4 /data/ef | |
| parent | 4ab0e8aeb83dfc41d03ee8e4dabea018b74a22bd (diff) | |
| download | colitur-8240dbe8221792510aba2405652b59c22f865957.tar.gz colitur-8240dbe8221792510aba2405652b59c22f865957.zip | |
test(golden): pin the six days RG91 entry24>28 now resolves correctly
2008-04-02/04/05 and 2038-03-06/08/09 are the six dates the re-bootstrap's
own brief named as producing a wrong observed office under the old data
(a III-class feast wrongly demoted to Commemoration_only, unable to win
against an ordinary class-4 feria it should trivially outrank). Verified
against the Missal before pinning, per this file's own rule: RG 91 entry 24
("Festa III classis, in calendario Ecclesiae universae inscripta")
outranks entry 28 ("feriae IV classis"), a plain, unqualified table
reading, and the calendarium text for all six was already primary-verified
in the register before this task ran -- only the data was wrong.
Each pin proves the mechanism, not merely the answer: an omitted_has check
(one per season family, Paschaltide and Septuagesima) confirms the
displaced class-4 feria actually reached disposition and was actively
excluded under RG26, not merely absent because nothing was ever offered.
test_easter_extreme_2038_late_modern's own header previously recorded these
three March dates as a DELIBERATE EXCLUSION because they were known wrong;
corrected in place to point at the now-existing pin instead of continuing
to justify an exclusion whose reason no longer holds.
Diffstat (limited to 'data/ef')
0 files changed, 0 insertions, 0 deletions
