feat(examples): ship two real local calendars, with their limits stated

Poland and the Benedictines, in the flat INI form, installed beside the
invented diocesan example.

poland.ini -- 17 entries from the Calendarium Perpetuum pro Dioecesium
Poloniae (1964), promulgated under Rubricarum instructum and applying to the
1962 Missal. Transcribed from a published Polish EF ordo that names that same
calendar, cross-checked against missalemeum's supplement page for the two
formularies 1964 added (13 and 15 July). Date, Latin name and class were read
from the source for every entry; three classes could not be recovered from
the PDF's column layout and are marked INFERRED where they appear, with the
reasoning. The header carries an edition warning that is a real trap here:
the Proprium Poloniae of 1921 and 1934 is still bound into many missals and
carries an outdated arrangement of dioceses and ranks. It is not this
calendar, and it is exactly the kind of plausible wrong-edition source that
has cost this project time before.

benedictine.ini -- two entries, and the comment explaining why is the point of
shipping it. Counted across the Norcia ordo: 86 "I cl.", 43 "II cl.", ZERO
"III cl." and ZERO "IV cl.", against 103 "Semidup." and ~96 "Dup.". The
monastic rite uses the Roman classes at the top and the older Duplex /
Semiduplex grades below, exactly where the Roman calendar has III and IV
class. colitur's rank vocabulary cannot express those, so most Benedictine
propers cannot be written here at all -- a mismatch of vocabularies between
related rites, not a gap in the data. Rather than invent a Duplex -> Class3
mapping the source never states, that file ships only what its ordo gives in
Roman terms and lists roughly two dozen excluded feasts BY NAME, so the
omission is visible instead of silent.

Both headers say plainly that they are examples and not authorities: they are
transcriptions from published ordines, none of the five test layers can vouch
for either, and both should be checked against the reader's own ordo. The
cram test asserts only what we control -- that they parse, convert and apply
-- and says so.

They also demonstrate the precedence engine on real data: the Benedictine
Transitus is I class and takes 21 March with the Lenten feria commemorated,
and Maurus is II class and takes 15 January with Paul the First Hermit
commemorated.

1 files changed, 30 insertions, 0 deletions

diff --git a/man/colitur-overlay.5 b/man/colitur-overlay.5
index f1360e2..7650dfc 100644
--- a/man/colitur-overlay.5
+++ b/man/colitur-overlay.5
@@ -228,6 +228,36 @@ Recolour a universal entry without otherwise touching it:
 A worked file exercising all four directives and all three date shapes is
 installed at
 .IR <prefix>/share/colitur/examples/diocesan\-example.sexp .
+Every celebration in it is invented, with
+.B example\-
+slugs, so that nothing in it can be mistaken for calendar data.
+.PP
+Two REAL local calendars ship beside it, in the flat INI form:
+.TP
+.I examples/poland.ini
+The proper calendar of the dioceses of Poland, from the
+.I Calendarium Perpetuum pro Dioecesium Poloniae
+(1964). Seventeen entries. Its header records which classes were read from
+the source and which are colitur's inference, and warns about the 1921 and
+1934
+.I Proprium Poloniae
+still bound into many missals \(em an outdated arrangement of dioceses and
+ranks that is easy to mistake for this calendar.
+.TP
+.I examples/benedictine.ini
+Two entries, and deliberately so. The monastic rite grades feasts
+.B Duplex
+and
+.B Semiduplex
+below II class, where the Roman calendar has III and IV class, so most
+Benedictine propers cannot be expressed in this format at all. Rather than
+invent a mapping the source does not state, that file ships only what its
+ordo gives in Roman terms and lists the rest by name as excluded. It is worth
+reading for that reason more than for its two feasts.
+.PP
+.B Both are examples, not authorities.
+They are transcriptions from published ordines, and none of this program's
+test layers can vouch for either \(em check them against your own ordo.
 .SH HOW AN OVERLAY IS APPLIED
 Worth understanding, because the commonest surprise \(em "my feast does not
 appear" \(em is almost never a loading failure.