25 Commits

Author	SHA1	Message	Date
will	a7901b3c61	Implement the resumed-post-Epiphany-Sunday temporal-id algorithm ... Post-Pentecost overflow years (early Easter, fewer than 6 Sundays after Epiphany fit before Septuagesima) previously clamped every excess Sunday to post-pentecost-24 instead of resuming the skipped post-Epiphany Sundays' own content, per the traditional rubric. Ported directly from the reference engine's own DivinumOfficium/Date.pm getweek(). Also adds the Epiphany VI Saturday-before-Septuagesima commemoration (only when Epiphany V was the last Sunday to actually occur), and fixes day-label.ts's on-screen display to track the same resumed-Sunday content instead of a raw elapsed-week count — including a correction so the fixed final Sunday of the year always reads "23rd Sunday after Trinity", not a per-year-varying number. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-16 20:07:04 -04:00
will	979bbe6aa4	Model cross-day Vespers commemorations, fix First Vespers threshold ... Whichever of today/tomorrow doesn't govern a given evening's Vespers can still be commemorated there, unless it's Simplex (or a bare temporal winner with no standing of its own) — live-verified in both directions against the real Monastic 1617 engine: Ss. Cyriacus/Largus/ Smaragdus (Semiduplex) commemorated when Sunday claims First Vespers over them; St. Anne commemorated even though St. James (Duplex II. classis) keeps his own Second Vespers outright; St. Donatus (Simplex) gets nothing ("nihil de præcedenti") in the same situation Cyriacus/ etc. did get a commemoration. The isMajorFixedFeastOfTheLord override (Christmas/Epiphany/Candlemas/Easter/Ascension/Corpus Christi/Sacred Heart) deliberately doesn't inherit this yet — no live data on whether those suppress it the way privileged-sunday/privileged-feria-major do during the day. Also fixes hasFirstVespers's threshold, found wrong while gathering the above evidence: it required duplex-majus+, but Ss. Cyriacus/etc. (plain Semiduplex) actually claims First Vespers over St. Donatus in the live engine. Lowered to semiduplex, matching the sibling privileged-feria-minor threshold already used just below it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-13 18:59:16 -04:00
will	ffaa797940	Author Benedictus antiphon + P/T/S/N Commons for 66 propers:null saints ... Continues the 94-saint batch this collects pass unblocked. Raw Commune/*.txt fields don't reliably match what the engine actually renders per hour -- same lesson as the collects pass, confirmed again: no CommuneM/*.txt file defines explicit per-hour antiphon fields for any category this batch needed, and the already-authored common-of-a-confessor-bishop content (from the original 29-saint pass) doesn't match Commune/C4.txt's own raw [Ant 1] either, since it was live-query-sourced rather than read from the file directly. Fixed by querying web/cgi-bin/horas/officium.pl directly (local Perl, not a network fetch) for one representative saint per Common category, with every representative's title verified against an accent-insensitive name-stem match before its content is trusted -- caught a stale-date bug this way: St. Emerentiana's stored clean-year comment actually rendered St. Hilary of Poitiers's office that year. Cross-querying multiple saints per nominal SaintRecord.common category found the real liturgical groupings are coarser (Martyr-Bishop and Martyr; Abbot, Confessor-not-Bishop, and Confessor; Virgin-Martyr, Virgin, and Holy Woman all render identical minor-hour text) but not uniformly so (Pope-Martyrs render distinct allelúja-toned text from plain Several-Martyrs; the Dedication of the Basilicas of Ss. Peter and Paul draws from the Dedication Common, not its nominal common-of-an-apostle at all). Net: 7 new shared Common categories plus the pre-existing common-of-a-confessor-bishop (which also needed a new Benedictus-antiphon file of its own) cover 66 of the 94 saints. New mechanism: SaintRecord.benedictusCommon, with getBenedictusAntiphon falling back to it the same way getDayCollect already falls back to collectCommon -- no name-substitution needed here, since every Common category in current use renders name-free Benedictus-antiphon text. Also fixes a real bug this surfaced: getMinorHourOverrideId gated all Prime/Terce/Sext/None lookup behind the same duplex-majus+ threshold Lauds' own psalmody override uses, on the assumption that only a strong feast carries its own minor-hour content -- live-querying proved that wrong (a winning Semiduplex saint still renders its own antiphons, not the ferial default). Lauds' psalmody override itself stays majus+-gated correctly, since it's a much bigger per-saint commitment this batch doesn't add a Common fallback for. Ss. Ursula and Companions deliberately left without a minor-hour Common: her collect template has no other calendar member to verify a shared text against, and she can never be queried directly (a genuinely unwinnable stub) -- left honestly unauthored rather than guessed. The other 26 of the 94 (own proper collect, from the collects batch) still need their own individually-authored Benedictus antiphon, same shape as the original 109-saint pass -- not done in this pass. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-13 08:58:13 -04:00
will	6bb4c6a80f	Author day collects for all 94 propers:null saints via Kalendaria tables ... Blind per-date source-file reading (Sancti/SanctiM MM-DD.txt) turned out unreliable for collect authorship: those files are era-merged, carrying centuries of accumulated saints behind rubric-conditional gating, so a naive read often returned a saint canonized long after 1617 instead of the Monastic-Tridentine-era one actually on this calendar (St. Didacus instead of All Saints of the Benedictine Order, St. Rose of Lima instead of Ss. Felix and Adauctus, etc). Fixed by pulling from web/www/Tabulae/Kalendaria/'s own era-specific calendar tables (1570.txt Tridentine base + M1617.txt's Monastic diffs) instead, cross-validated against the pre-1955/Divino Afflatu chain (1888->1906->1939->1954) as a corroborating signal. Cross-referencing all 205 existing saint records against this table confirmed 204/205 were already correctly placed -- the earlier live-query verification work was sound, only blind file-reading was flawed -- so no sanctoral-calendar.yml corrections were needed, just the collect content itself. Two collect shapes came out of the 94: 34 proper collects (own YAML file, Latin verified against source, English translated+draft where the source lacked it) and 60 resolved via a new Common-collect templating mechanism -- SaintRecord.collectCommon/collectName plus substituteName() in resolve-common.ts, filling a template's {N} placeholders positionally from the saint's own declined name, across 21 new common/collect-c*.yml templates named after the source's own C-numbering. St. Michael's Sep 29 propers resolved via its whole-file @Sancti/05-08 inheritance (Apparition of St. Michael, May 8). St. Martha's plural- template default was overridden to the singular collect-c6a since she's one person, not a pair. Also fixes a latent bug this surfaced: getDayCollect looked up `${collectCommon}-collect`, but collect-c*.yml files are id'd as `collect-c2` etc with no such suffix -- caught by a smoke test where every one of the 93 non-Michael saints resolved as missing. 4 pre-existing tests updated: they asserted specific saints (St. Benedict, St. Romanus Abbot, St. Anthony Abbot) had no authored collect, which is no longer true; resolve-common.test.ts's generic "missing" case now uses a synthetic day/winner since no real unauthored saint remains as an example. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-13 08:19:28 -04:00
will	735f677815	Extract shared Commons for Prime/Terce/Sext/None minor-hour content ... A systematic diff across all 29 duplex-majus+ saints' P/T/S/N files found real shared-Common groups beyond the pairs noticed in passing while authoring them. Extracted into shared data/propers/common/{hour}-antiphon- common-of-*.yml / {hour}-capitulum-common-of-*.yml files and wired via a new SaintRecord.minorHoursCommon field, with resolveMinorHourAntiphon/ resolveMinorHourChapter falling back to it when a saint has no proper file of their own. Deliberately a separate field from the existing (previously unused) `common` field: the minor hours don't always draw from the same Common category as the saint's overall classification -- both Chair of St. Peter feasts are `common: common-of-an-apostle` by rank, but their P/T/S/N content is Common of a Confessor Bishop (Peter considered as bishop of that see). Four groups extracted (87 duplicate files collapsed to 21 shared ones), each confirmed byte-identical via diff first: common-of-apostles (8 saints, all 4 hours), common-of-a-confessor-bishop (Chair of Peter pair share antiphons+chapters, Martin of Tours shares only chapters), common- of-the-bvm (Nativity BVM + Immaculate Conception's Sext/None/Terce chapters -- the Assumption's own stay proper, different reading + proper versicles), and common-of-st-peter (St. Peter ad Vincula + Ss. Peter and Paul, not a real Common category, just genuinely identical Petrine content). Deliberately left un-extracted: St. Mark, St. John Before the Latin Gate, and Ss. Philip and James share identical text that live-checking shows is Paschaltide-seasonal (all three landed within the Easter octave weeks on their queried dates, despite disagreeing `common` classifications) rather than a fixed per-saint-category Common -- folding it into the same mechanism would misrepresent season-contingent content as timeless. Left as individually-authored files; flagged in TODO.md as needing a real Paschaltide-awareness mechanism this app doesn't have yet for any hour. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-12 15:47:13 -04:00
will	ea29e5ee45	Add Dec 26-30's own Sunday rule -- a deliberate remix, not a live-verified fix ... Per direct instruction, and explicitly framed as this project's own departure from Monastic 1617 itself: within Dec 26-30 inclusive (exactly one real Sunday falls somewhere in that window every year), whichever date is the actual Sunday always wins as Nat1-0 outright, with no rank check at all -- even Stephen/John/Holy Innocents (Duplex II. classis) get fully displaced, not just commemorated. The displaced saint isn't commemorated in place either; he reappears in full as Dec 30's own winner instead (the block's one date with no fixed saint of its own). Rank never matters for this rule -- confirmed with Becket (Semiduplex) transferring the same way as the Duplex-II-classis saints. This deliberately diverges both from what Monastic 1617 itself does on Dec 26-29 (live-verified two commits ago: the saint wins there, Sunday merely commemorated) and from the general privileged-sunday transfer rule elsewhere (which only transfers ranks below duplex-majus and commemorates everything else in place) -- this window transfers every rank and commemorates nothing in place, a genuinely new, third behavior specific to this 5-day block. Implemented as calendar/index.ts's applyChristmasOctaveSunday, a narrowly-scoped layer in the same spirit as applyMarianSaturday/ applyChristTheKing, rather than by changing the shared decideOccurrence/transfer machinery every other Sunday relies on. Dec 31 and everything outside Dec 26-30 is untouched -- St. Silvester still beats the Sunday there via the plain, unchanged ordinary-sunday rule. Verified against all five possible Sunday positions within the window (Dec 26/27/28/29/30) plus the "nothing displaces anything" control case, each with its own dedicated test in the new tests/calendar/christmas-octave-sunday.test.ts. Updates two existing tests whose assertions were correct under the old rule and are now superseded specifically within this window (Stephen/Innocents no longer win their own Sunday-collision dates there) while confirming the underlying ordinary-sunday rule is still live and real outside it (Dec 31/St. Silvester). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-12 10:59:34 -04:00
will	397f31f4fc	Implement octave-vs-octave precedence, and fix a real day-label bug it surfaced ... When more than one octave is active on a day with no temporal standing of its own (St. Lawrence's and the Assumption's genuinely overlap every Aug 16-17), which one governs the day's content/label is now decided by rank comparison instead of "whichever started first" (an accident of insertion order). Per direct instruction: - Highest effective rank wins outright; every other active octave still gets commemorated, same as a single octave already outranking a weak rival saint. - A rank tie goes to whichever octave started more recently -- day 1 of a new octave needs to be fully present, the whole point of it starting. No real tied-rank case exists yet to verify this empirically, unlike everything else here -- documented in TODO.md as a stated decision, not a live finding. New OctaveConfig.closingDayRank (default duplex): an octave's own final day ("in Octava") is elevated above its ordinary in-between rank -- live-verified as a real, general pattern (both St. Lawrence's Aug 17 and the Assumption's Aug 22 show as Duplex, above their otherwise-Semiduplex ordinary days), not a one-off. This elevation is *why* Lawrence's octave beats the Assumption's on their one real overlap day despite the Assumption being the far higher-ranked feast overall. Feeds both the existing rival-saint threshold and the new octave-vs-octave comparison. calendar/octaves.ts gains resolveActiveOctave (+ pickWinningOctave, the comparison itself factored out for direct unit testing against synthetic data, since no real tied-rank overlap exists to test against yet). hours/resolve-common.ts's resolveOfficeWinner and calendar/day-label.ts both now call it instead of each keeping their own "activeOctavesFor(...) [0]" logic. That consolidation surfaced a real, independent bug: getDayLabel never checked temporalCategory at all before choosing an octave name, unlike resolveOfficeWinner -- found while testing the real Aug 16 overlap (a Sunday that year, where the temporal Sunday has standing and should win outright). Live-verified counterexample: the Christmas Octave's own stack (Dec 30) was wrongly labeled "3rd Day within the Octave of The Holy Innocents" instead of the correct plain temporal label -- the real title never names any of the four stacked octaves there. Fixed by sharing the exact same ordinary-feria gate resolveOfficeWinner already had, so the two can no longer disagree. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-12 09:38:06 -04:00
will	5f32a3751c	Model St. Clare and surface active octaves in the day label ... Today (Aug 12, within St. Lawrence's octave) was resolving as a plain ferial day: St. Clare wasn't modeled in the calendar at all, and even once an octave commemoration exists, getDayLabel only ever looked for a sanctoral commemoration, never an octave one, so the label fell all the way through to the generic ordinal week label. Adds St. Clare (Simplex under Monastic 1617, correctly losing to Lawrence's octave and only commemorated -- live-verified against three clean years). Extends getDayLabel to show the active octave itself as the day's primary identity when nothing else has won outright (e.g. "3rd Day within the Octave of St. Lawrence, Martyr -- St. Clare, Virgin"), matching what the live reference engine actually titles these days, rather than falling back to an anonymous ordinal week label. Also fixes a regression this surfaced: Trinity Sunday is technically also day 8 of Pentecost's own octave, and the naive octave-first check was shadowing its own anchor-day name ("8th Day within the Octave of Pentecost" instead of "Trinity Sunday"). A season's own named anchor day now always outranks an active octave label. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-12 06:39:48 -04:00
will	2247e8c27f	calendar: exempt Vigils from Our Lady's Saturday's demotion ... Refined per direct correction: Our Lady's Saturday is really only a Simplex-strength standing, not a privileged-feria-minor-shaped one -- a Vigil keeps forcing its own primacy on a Saturday the same way it already does any other day (see calendar/commemorations.ts's own transferDirectionOf special-casing for Vigils elsewhere). Only a Simplex saint alone now loses to it; a Vigil, along with anything Semiduplex-or-higher, wins outright and Marian Saturday doesn't apply. Un-does the two test-date moves this same regression prompted last time (Vigil of St. Lawrence, Vigil of St. John Baptist) -- both dates' original years work again now that the fix is right. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-11 14:20:13 -04:00
will	0404642614	calendar: add Christ the King, last Sunday of October ... A 1925 addition, so nowhere in the Monastic Tridentinum 1617 base this project otherwise targets -- content sourced from "Monastic Divino 1930" instead, the Monastic-lineage version of the era that actually carries it. Always wins outright (Duplex I. classis, confirmed live), commemorating whichever Sunday after Pentecost it displaces -- same additive-layering shape as applyOctaves/applyMarianSaturday, run last so nested commemorations (e.g. a Simplex saint already commemorated under that Sunday) survive underneath it. Extended the Lauds psalmody-override mechanism (both the psalm groups and, newly, the chapter/responsory/hymn/versicle bundle) to recognize named temporal winners as unconditionally override-eligible, not just duplex-majus+ sanctoral ones -- generalizing what had been a Marian- Saturday-only special case. Suffrages needed their own explicit check too: isDoubleOrHigher only ever looks at a sanctoral rank, and a named temporal winner has no FeastClass to check at all. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-11 14:13:22 -04:00
will	747a078580	calendar: model Our Lady's Saturday as a real occurrence outcome ... On a free Saturday (nothing privileged already claims it, no active octave), the day's own identity is now "Our Lady's Saturday" rather than an anonymous ordinary-feria -- mirrors privileged-feria-minor exactly, per direct instruction: Semiduplex-or-higher still wins outright (Marian Saturday doesn't apply at all); below that (Simplex, and Vigil, both under semiduplex on the FeastClass scale) loses and is commemorated instead. Layered additively after decideOccurrence, same shape as applyOctaves -- never touches decideOccurrence's own rules. Needed a real winner identity (not just the plain temporal feria id) so day-label/antiphon/collect sourcing can recognize it -- added a temporal-feasts record purely for that, and taught getDayLabel to check it for any named temporal winner (a small, free improvement for Christmas/Pentecost's own labels too, previously unhandled). hours: build the duplex-majus+ Lauds psalmody override (per-feast) lauds-psalmody no longer unconditionally uses the plain weekday default: a duplex-majus-or-higher sanctoral winner, or Our Lady's Saturday (unconditional, no rank threshold -- it isn't competing with the weekday default the way a saint is), now substitutes its own proper psalm groups/antiphons/canticle. Per-feast, not per-Common, per direct instruction, even though most duplex-majus+ saints across the year don't have one authored yet and fall back to the plain weekday default until they do. Content for the worked example (St. Lawrence's own day) surfaced a real bug while sourcing it: st-lawrence-antiphon.yml had been read from the Roman/secular rite's own [Ant 1], not Monastic 1617's actual Benedictus antiphon for that day -- corrected from a fresh live query. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-11 14:02:55 -04:00
will	e35183bfac	propers: add octave Matins readings, starting with St. Lawrence's ... Adds propers/octave-readings.ts: a day-indexed lookup (getOctaveReading(octaveId, dayNumber), id convention "${octaveId}-octave-day-${dayNumber}") since readings genuinely vary day to day within a single octave (confirmed: the Assumption's own octave gives different patristic excerpts on day 2 vs. day 5) -- the singular OctaveConfig.readingId field from the previous commit didn't fit that reality and is removed. Sourced via a different query command (prayMatutinum, not prayTertia) than every other proper this pull has pulled -- the raw per-date Sancti/MM-DD.txt files for octave-continuation days are occupied by unrelated later-calendar saints (same trap as everywhere else), but the real content lives in MM-DDoct.txt/MM-DDbmv.txt-style variant files the live engine resolves correctly. Per project convention (2026-08 discussion): the historical 3 (or 9-12, on a day's own higher-rank office) Lectios are collapsed into one continuous reading rather than kept broken up, and only the first responsory is kept (which one to use when several collapse into one is still an open question). A caught bug along the way: several readings have no English translation in the source at all -- its own English page silently falls back to showing the Latin text under the "Reading" header, which an early pass mistakenly stored as a duplicate before the mismatch was caught; now left honestly missing instead. St. Lawrence's octave: real readings for days 2-5 and 8 (day 8, "In Octava S. Laurentii," is a fuller distinct office); days 6-7 (Aug 15-16) belong entirely to the Assumption's feast and octave instead -- day 7's query, redirected, became assumption-octave-day-2's reading. The other five octaves (Assumption's remaining days, Nativity BVM, Immaculate Conception, All Saints, the Christmas trio, Pentecost) are follow-up work, not done in this pass. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-11 08:46:58 -04:00
will	da3b6e893e	calendar: model octaves as a generic, data-driven mechanism ... Adds calendar/octaves.ts: a lookback over the past week collecting every octave (sanctoral or temporal) still active on a date, stacking multiple at once (Christmas + St. Stephen + St. John + Holy Innocents all commemorated together within the Christmas Octave). Declared via an optional `octave` field on a saint's own record or a new small TemporalFeastRecord (calendar/temporal-feasts.ts) for temporal ids like Christmas/Pentecost that didn't have a metadata record before -- data- driven per user design discussion, with `{ enabled: true }` alone using sensible defaults (8 days, semiduplex threshold) so a minimal declaration works without authored content. Wired into resolveDay as a post-processing layer: doesn't change how a single day's own precedence contest is decided, just adds commemorations for active octaves and occasionally overrides the winner when the occurring saint doesn't clear the strictest active octave's threshold. Populated so far: St. Lawrence's own octave (the one that repeatedly cost real saints their spot in August), the three Comites Christi octaves (Stephen/John/Innocents -- Thomas of Canterbury deliberately excluded, per discussion), and Pentecost's (duplex threshold, user-specified). Pentecost's octave offsets are also removed from temporal-categories.yml's privileged-feria-major classification, letting a real candidate reach the new octave layer instead of being transferred away first -- with the side effect that Pentecost's own Ember Saturday no longer forces a transfer (a sub-threshold saint is now commemorated in place instead, see tests/calendar/transfer.test.ts's updated case). Assumption, Nativity BVM, Immaculate Conception, and All Saints' own octaves are not yet populated with octave data -- deliberately deferred to a follow-up pass. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-11 07:23:43 -04:00
will	08f94823f7	calendar: give Advent's ordinary ferias their own precedence tier ... Found while starting the December sanctoral pull: Advent's plain (non-Ember) weekday ferias have real standing in the live Monastic 1617 engine that the existing ordinary-feria category couldn't represent -- a Simplex saint (St. Bibiana, Dec 2) is merely commemorated there rather than winning outright, while a Semiduplex+ saint (St. Nicholas, Dec 6) wins with the feria itself commemorated back. Adds a third, weaker privileged-feria-minor tier (Semiduplex+ threshold, vs. privileged- feria's Duplex+) rather than reusing either existing tier, mirroring how privileged-feria/privileged-feria-major were split in March. Lent's own ordinary ferias likely share this property but are left as-is, unverified this session. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-11 06:23:35 -04:00
will	f0e32ae0c1	calendar: fix transferred candidates blindly winning outright ... Found via real data (the May sanctoral pull): a transfer landing on a day whose own native winner was temporal blindly took over as winner, regardless of that day's own precedence category — so a transferred-in Simplex saint (St. Felix I, impeded by Pentecost's Ember Saturday) was overwriting Trinity Sunday itself instead of being merely commemorated, the way a native Simplex candidate on an ordinary Sunday already correctly is. Fixes applyIncomingTransfer to run the arriving candidate through decideOccurrence using the receiving day's own temporalCategory, the same rules a native occurrence there would use, instead of assuming an empty temporal slot means automatic victory. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-10 17:25:27 -04:00
will	effe2b1333	calendar: split privileged-feria into two real precedence tiers ... A plain Duplex saint was losing to any privileged feria (Ember days included) since the occurrence engine only let duplex-1-classis+ get even a commemoration there. Verified this was wrong: St. Gregory the Great, plain Duplex, outright wins against a Lenten Ember Saturday in the real Monastic 1617 engine. Splits TemporalCategory's single privileged-feria into privileged-feria (the lesser tier — Lent's Ember days, verified — now behaves like an ordinary Sunday: Duplex+ wins outright) and privileged-feria-major (Ash Wednesday, Holy Week, the Easter Octave, verified via St. Mark only ever being commemorated there, never winning — behaves like privileged- Sunday). Everywhere else the old single category was ambiguous (Pentecost's own Ember days/Vigil/Octave, the Vigil of Christmas) defaults to the stricter major tier pending verification. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-10 15:51:09 -04:00
will	81440de832	hours: add the day's-collect resolver ... Terce/Sext/None's Oratio is the day's own Proper-of-season/-saints collect, not a fixed text — getDayCollect() resolves it from the LiturgicalDay's winner (temporal id or sanctoral saint's propers), falling through to an honest "missing" status for saints that don't have authored propers yet. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-10 13:50:24 -04:00
will	37ac31c3f2	calendar: occurrence engine v2 — real rank thresholds, transfers, collisions ... Corrects and completes the occurrence rules, based on a design discussion plus one concrete data point: St. Anthony Abbot (plain Duplex) was found outright winning against an ordinary Sunday in the real Monastic 1617 engine, which the old duplex-1-classis-only threshold got wrong. - FeastClass gains `vigil`, inserted between `simplex` and `semiduplex` — one ordering that correctly serves both "does this win against a Sunday" (vigil behaves like simplex there) and "which of two saints wins a landing-day collision" (vigil beats simplex, loses to semiduplex). - LiturgicalDay.occurring (a flat OccurringFeast[] that could only ever express a losing *sanctoral* candidate) is replaced by `winner: DayWinner` + `commemorations: Commemoration[]` — a discriminated list that can hold the temporal day itself, one or more sanctoral entries, or (not built yet, but the shape already accommodates it) a future octave kind. - commemorations.ts: ordinary Sundays let Duplex+ win outright (Sunday commemorated in return), Semiduplex/Vigil transfer elsewhere (too substantial a feast to cheapen with a bare commemoration), Simplex stays and is commemorated. Privileged Sundays never displace; Duplex-majus+ commemorated, everything else transfers. - collision.ts (new): resolves two sanctoral candidates wanting the same day (a transfer landing on an already-occupied day, or two native saints sharing a date) — duplex > semiduplex > vigil > simplex, loser always commemorated, ties favor the native occupant. - temporal-id.ts (new): maps any date to one of the 52 real Sunday-collect ids from the previous commit, so a temporal winner/commemoration can actually be looked up, not just labeled "temporal" in the abstract. - index.ts's resolveDay orchestrates all of it, including the actual Monday/Saturday transfer mechanism. Landing on a privileged feria (the concrete case: Holy Week, right after Palm Sunday) is explicitly deferred rather than guessed at — it needs its own Easter-keyed lookup table, the same way the reference engine handles it. Added the Vigil of St. Lawrence (Aug 9) as real content specifically to exercise the backward-transfer rule end-to-end: Aug 9, 2026 is a Sunday, so the vigil transfers cleanly back to Saturday, verified by a new integration test alongside the unit-level rule and collision tests.	2026-08-10 12:00:01 -04:00
will	ad87d8dd18	calendar: move Sunday-governance arithmetic from day-label.ts into temporal.ts ... sundayOnOrBefore and firstSundayStrictlyAfter are calendar facts ("which Sunday does this feria belong to"), not presentation logic — day-label.ts was the only consumer so far, but a future temporal-propers content resolver (PropersRef's still-unused source: 'temporal' branch) will need the exact same arithmetic, just keyed for content ids instead of display strings. Moving it now, while the shape is still small and well understood, rather than duplicating it later. day-label.ts keeps the actual display config (which anchor, "Trinity" vs "Pentecost" wording) — that part stays presentation-only on purpose, since it's also where a future counting-convention setting would hook in. No behavior change: 88/88 tests still pass.	2026-08-10 07:30:21 -04:00
will	226fff2ce6	ui: show the "day being celebrated" label ... Adds a real label under each hour's heading — "Monday in the 10th week after Trinity", "The 1st Sunday of Advent" — computed from whichever LiturgicalDay the hour actually resolved against, which can differ from the nav date for Compline's evening anticipation. calendar/day-label.ts combines two things: an ordinal week-within-season label (pure date arithmetic on the season anchors from calendar/temporal.ts and calendar/easter.ts — Trinity-counted, not Divinum Officium's own Pentecost-counted convention; meant to become configurable later via the same day->id indirection already used for the sanctoral calendar, not hardcoded forever), and a feast name from calendar/commemorations.ts's occurrence decision — shown alone if the feast displaces the day outright, prefixed onto the temporal label if merely commemorated, or omitted entirely if nothing's occurring.	2026-08-10 07:07:10 -04:00
will	eaaca05ad8	calendar: First/Second Vespers anticipation for Compline ... Compline (and eventually Vespers) now resolves off whichever day's identity actually governs tonight's office, not always today's — real practice anticipates a higher-ranking tomorrow (Alma Redemptoris Mater starting the Saturday evening before Advent I, Ave Regina Caelorum starting the eve of Candlemas, Regina Caeli starting at the Easter Vigil), which the previous date-only resolution missed entirely. calendar/vespers.ts's resolveEveningDay compares today's and tomorrow's precedence (reusing commemorations.ts's FeastClass machinery) to decide. One deliberate absolute exception, caught by a failing test: a short, explicit list of supreme fixed/movable feasts (Easter, Christmas, Epiphany, Candlemas, Ascension, Corpus Christi, Sacred Heart) always wins tomorrow's Vespers before checking whether today would otherwise keep its own — without it, Holy Saturday's privileged-feria status incorrectly blocked Easter's anticipation, the textbook case this whole thing exists to get right. hours/compline.ts now resolves its whole ordo through resolveEveningDay instead of resolveDay.	2026-08-10 07:05:41 -04:00
will	2ea21f2c89	calendar: real occurrence/precedence resolution (feast ranks, sanctoral content) ... Replaces the FeastRank placeholder with a real ordered FeastClass (the old pre-1955 six-level scale) and a new TemporalCategory (privileged/ordinary Sunday/feria). calendar/commemorations.ts's decideOccurrence encodes the actual precedence rules as explicit, commented branches per category rather than the reference engine's own opaque numeric weights — this app targets one ruleset, so the readability trade-off is worth it. Category membership (data/calendar/temporal-categories.yml) is a best-effort reconstruction of the pre-1955 tradition, not sourced from a primary text; expect corrections. calendar/feasts.ts resolves real sanctoral candidates, and resolveDay() wires it all together — occurring/temporalCategory are no longer stubs. isDoubleOrHigher (hours/antiphon.ts) is now a real comparison instead of a hardcoded false. Seeded 7 real saints/feasts, each verified directly against Divinum Officium's own rank data (not reconstructed from memory) as a small, growable start: St. Lawrence, the Assumption, St. Augustine, the Nativity of the BVM, St. Michael, All Saints, the Immaculate Conception.	2026-08-10 07:03:28 -04:00
will	67037469fc	calendar: compute real Easter dates and temporal-cycle seasons ... resolveDay() no longer hardcodes season: 'trinitytide'. Easter is computed via the Anonymous Gregorian algorithm (verified against 16 known reference dates spanning 1583-2100); Advent/Christmastide/ Epiphanytide follow the Christmas-anchored rules (including Advent's "Sunday nearest Nov 30"); Septuagesima through Trinitytide come from easter-offsets.yml, reshaped from single named anchor points into real ranges plus single-day overrides for Corpus Christi and Sacred Heart. occurring feasts (calendar/feasts.ts) are still a stub — the sanctoral calendar and Double-vs-not ranking are a separate, larger project.	2026-08-10 05:27:12 -04:00
will	58958aa847	Prime: real content (psalms, Martyrology, Regula) and ordo corrections ... Pulls in verified content from Divinum Officium rather than placeholders: 17 psalms (2, 6, 7-19, 118, 129), 365 days of the Martyrology, and the full 121-reading Regula cycle, plus the Athanasian Creed. Ordo corrections driven by review against the real engine output: - Capitulum and Preces now pick a Sunday/feast vs. ferial form (calendar/isSundayOrFeast); ferial Preces said every ferial day by choice. - Chapter responsory, hymn doxology, and the opening versicle's Alleluia/Laus tibi all vary by season via a shared resolver (hours/seasonal-propers.ts). - Real Roman Kalends/Nones/Ides Latin dating (calendar/roman-date.ts, verified against 363/365 real Martyrology headings) plus the historical "bis sextus" Feb 29 handling, and the Martyrology's Luna (moon-day) heading (a ported Golden-Number calculation). - Fixed responsory structure (was missing its initial full repeat), weekday psalm antiphons (opening as incipit-or-full by rank, full repeat after the psalms/Creed as its own part, "*" chant mark kept), scripture citations on the capitulum/lectio brevis, and V./R. markers switched from Unicode symbols to plain text for reliable font rendering. - Dropped Pretiosa and the dead-commemoration psalm (129) for time; trimmed section headings down to the ones that are actually named things (Preces, Chapter Office, etc. no longer relabel connective text). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-09 20:03:53 -04:00
will	a5dc6502d7	Milestone 0/1: shell, calendar/psalter/hours scaffold, Prime ... Client-side-first PWA (Vite/TS, no backend) per the approved plan: day- navigable shell listing all 8 hours, Prime fully resolves via the calendar -> psalter -> ordo pipeline, the other 7 hours are registered but flagged not-implemented. Sanctoral/temporal calendar data uses a day -> id indirection layer (saints, easter-offsets, fixed-date-calendar) so reassigning a feast to a different day is a data edit, not a code change. Docker (Caddy-serving-static) + Gitea CI workflow scaffolded to match the eec/drip/bookshop operational pattern. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-09 15:20:06 -04:00