aboutsummaryrefslogtreecommitdiff
path: root/tools/export_lectio_patch.py
Commit message (Collapse)AuthorAgeFilesLines
* docs(tools): the lectio patch exporter cannot see temporal correctionsLukasz Kasprzak2026-08-181-0/+11
| | | | | | | | | | | | It compares colitur's sanctoral data against lectio's calendar ini, so a correction to a temporal day -- computed in code on both sides, present in neither file -- is structurally invisible to it. Not hypothetical. The Good Friday colour fix (RG 128(b) + RG 132, v0.4.0) was missed entirely by this tool when the eight-field patch was produced, and surfaced only by running clectio at the bottom of the chain and diffing its output against colitur date by date. The tool narrows the search; it does not close it.
* feat(tools): export the lectio EF correction patchLukasz Kasprzak2026-08-181-0/+91
colitur has been downstream of lectio since its data was bootstrapped from it. These are the fields where that relationship should now invert: eight changes, each annotated with the colitur allow-list entry carrying its rubric. Deliberately a PATCH and not a regeneration. colitur carries 205 of the 327 Polish names lectio ships, so regenerating lectio's ini from colitur would silently drop 122 of them; colitur also uses a different slug vocabulary for Passion/Holy week and different Paschaltide week numbering. What colitur is authoritative for is the adjudicated fields, and only those are emitted. Comparing the two datasets field by field also caught a counting error in colitur's own register that no assertion in this project was watching for: six sanctoral entries carry subject = Lord, not the four recorded, because the regex that counted them truncated on the two longest Polish names. The RG 112(b) reachability measurement was re-run against all six and is unchanged at 0/0; both docs are corrected.