23 Commits

Author	SHA1	Message	Date
will	bcae61568a	Add Paschaltide-variant fallback for minor-hour Commons ... Confirms and formalizes what TODO.md had flagged as an open question: the reference engine's own source has explicit Paschaltide variants (Commune/C1p.txt, C2p.txt, C3p.txt -- "tempore Paschali") for exactly 3 of its 12 Common categories -- Apostles, a Martyr-Bishop, Several Martyrs -- a real liturgical restriction of Alleluia/victory imagery to apostles and martyrs, not a coincidence. resolveMinorHourAntiphon/resolveMinorHourChapter now try a `${minorHoursCommon}-paschaltide` variant first whenever day.season is eastertide/ascensiontide/pentecost (the same three-season window as Compline's own Regina Caeli table, since "tempore paschali" runs through the Pentecost octave in both), falling back to the plain Common when no variant is authored. common-of-apostles-paschaltide (7 files) ported directly from the reference engine's own Commune/C1p.txt source files rather than live-queried, then cross-checked against st-mark's already-authored, live-queried content -- identical except one antiphon's asterisk, which the source places one word earlier; corrected to match. st-mark and st-john-before-the-latin-gate's duplicate per-saint files removed entirely; ss-philip-and-james's chapter files removed (its antiphons stay proper). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-12 16:03:06 -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	2658a2b94e	Fix splitNamedAntiphon silently upgrading draft text to verified ... Every antiphon that goes through the incipit/full split -- which is every antiphon across every hour -- lost its real status the moment it passed through here: splitNamedAntiphon hardcoded `verified` on its output via verifiedText(), regardless of what the source's actual status was. Concretely, this meant St. Scholastica's antiphon (I translated it myself, no English existed in the source), Matthias's and several other apostles' reworded English, and Gregory the Great's translated antiphon all silently rendered as if fully verified -- losing the "unverified draft text" UI marker (src/ui/styles.css's .text-draft, a dashed underline + tooltip) that's supposed to distinguish "copied straight from the source" from "Claude's own rendering." Fixed by having splitNamedAntiphon accept a real ResolvedText and carry its per-language status through unchanged to both outputs, instead of silently upgrading everything to verified. Callers whose antiphon never had a status field to begin with (plain weekday-default antiphons and Lauds psalmody overrides -- neither type tracks status at all, always implicitly verified by the source file's own live-checked convention) now wrap with verifiedText() explicitly at the call site, rather than that assumption being buried inside splitNamedAntiphon itself. resolveMinorHourAntiphon (Prime/Terce/Sext/None's override lookup) now returns a full ResolvedText for the same reason. Verified end-to-end with St. Scholastica's real draft-English antiphon, both via a direct unit test and visually in the browser (the dashed underline now shows correctly under her Benedictus antiphon). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-12 11:34:21 -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	5f4cf33776	Add per-feast overrides to Prime/Terce/Sext/None; fill Lauds' own Lawrence office bundle ... Prime/Terce/Sext/None had no per-feast override mechanism at all before this -- their psalm antiphon always fell back to the plain weekday default and their chapter was always a single fixed per-annum/per-weekday text, regardless of what was actually being celebrated, even on a saint's own actual feast day (not just during an octave). Confirmed live (Monastic Tridentinum 1617) that St. Lawrence has his own real antiphon and chapter at every one of these hours, both on his own day and throughout his octave. New shared mechanism in hours/resolve-common.ts: getMinorHourOverrideId (duplex-majus+ threshold, kept in sync with Lauds' own so it's one shared backlog), resolveMinorHourAntiphon, resolveMinorHourChapter -- all resolveOfficeWinner-aware, so an octave day gets the same override as the feast's own actual day. Prime additionally needed isSundayOrFeastOffice (its capitulum/Preces Sunday-vs-ferial choice) made octave-aware -- live-verified Prime's capitulum stays the Sunday/feast form throughout the octave too, so no new file was needed there, just reaching the existing one correctly. Also fills in Lauds' own still-missing Lawrence office bundle (capitulum/responsory/hymn/versicle) -- flagged in TODO.md as worth fixing "even before tackling the other 32" and still not done until now. Authored real content for St. Lawrence across all five hours from live queries. The same ~31-saint backlog (TODO.md) now applies uniformly across Lauds and the four hours fixed here. Also documents a real, found-not-fixed gap: when two octaves overlap with no temporal standing to yield to (St. Lawrence's and the Assumption's genuinely overlap every Aug 16-17), this app currently picks whichever started first, which happens to match the live engine on Aug 17 (Lawrence's own elevated final "Octave Day" outranks the Assumption's ordinary octave-day strength) but only by coincidence, not a real rank comparison -- proposed design written up in TODO.md pending a decision on scope. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-12 08:05:08 -04:00
will	143244203d	Fix octave-day office content: use the octave's own feast, not the plain ferial ... Real, multi-part bug found by looking closely at today's rendering (day 3 of St. Lawrence's octave, St. Clare commemorated): the psalmody antiphons, hymn, chapter/responsory/versicle, Benedictus antiphon, and day collect were all keyed off `day.winner` directly, which stays the plain temporal identity (post-pentecost-11) throughout an octave -- St. Lawrence's own already-authored psalmody override and collect never engaged on any day but his actual feast day. Live-verified (Tridentine 1910, 2026-08-12) that the whole office on an ordinary octave day actually comes from the octave's own feast ("{ex Commune aut Festo}" / "{ex Proprio Sanctorum}"), with a *weaker* commemorated saint (Clare) getting a separate Ant+V/R+collect block of her own alongside it. Fixed with a new resolveOfficeWinner(day) in hours/resolve-common.ts, used everywhere getDayCollect/getDayCollects/getBenedictusAntiphon/ getPsalmodyOverrideFor used to read day.winner directly. Deliberately gated on temporalCategory === 'ordinary-feria' (the day has no standing of its own) rather than "any active octave" -- the Christmas Octave's own stacked octaves are the live-verified counterexample where the *temporal* day keeps the office instead, each octave becoming its own separate commemoration block (not yet modeled, flagged in TODO.md). Also fixes the ferial Preces gate (added in the previous commit) to exclude active octaves the same way the suffrages already do -- live-verified "Preces Feriales{omittitur}" on the same date. getDayCollects now renders a sanctoral commemoration as a real Ant+V/R+collect bundle when authored (${propers}-commemoration.yml), not just a bare, unlabeled collect -- the old rendering was indeed the confusing "PRAYER / (translation pending)" block spotted today, which was St. Clare's placeholder with no indication whose it was or why. Authored her real commemoration bundle and standalone collect from the same live query rather than leaving it pending. One correction to a guess floated mid-session: the Benedictus antiphon does NOT go to the commemorated saint (Clare) -- live-verified it stays with the octave's own feast (Lawrence's "In cratícula"), same as everything else in the primary office; only the separate commemoration block is Clare's. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-12 07:44:39 -04:00
will	9c9811a9ed	Add Lauds' ferial Preces (Tridentine 1906/1910), shown on ferial/vigil days ... Monastic 1617 has no Preces feriales at Lauds at all -- content sourced from Tridentine 1906/1910 per direct instruction, same track as the Cross suffrage and St. Joseph's suffrage. New lauds-preces-feriales.yml (Kyrie, Pater noster, the full versicle litany, Psalm 129, closing versicles) transcribed from a live query against a clean Advent feria, matching what actually rendered rather than the underlying template's own conditional markup (the Pope/Bishop and benefactors' versicles are both dropped live despite being present in the template; the King/nation versicle pair is kept despite the template's own rubric note suggesting otherwise). New `lauds-preces` part kind (hours/types.ts) picks between this and the existing short Sunday/feast litany (lauds-short-litany.yml, unchanged content) on a ferial-or-vigil day. Deliberately not the shared `isSundayOrFeast` predicate, which treats a Vigil as a "feast" -- here a Vigil needs to land on the ferial side instead, per direct instruction. Also deliberately wider than the real 1906/1910 rubric itself, which restricts the fuller form to Advent/Lent/Ember days specifically -- shown on *every* ferial or vigil day instead, mirroring the identical explicit choice already made for Prime's own ferial Preces. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-12 07:12:27 -04:00
will	2f8f744cd1	Omit Lauds suffrages entirely during Advent/Christmastide/Passiontide and any active octave ... Checked directly against Monastic Tridentinum 1617 (not just the Tridentine 1906/1910 track the suffrage content itself comes from) -- this omission isn't a rubric-track-specific quirk, it holds under this app's own primary source too: - Advent, Christmastide, and Passiontide ferias: suffrages omitted entirely. Confirmed ordinary Lent (weeks 1-4, not Passiontide) is NOT excluded -- only the last two weeks are. - Any day within an active octave: suffrages omitted entirely, however low that octave's own rank is -- confirmed against day 2/3 of St. Lawrence's own Semiduplex octave, well below the existing Duplex+ threshold. Today (within Lawrence's octave) was showing all five suffrages before this fix; the real office has none but the Marian antiphon. Still not modeled, flagged in TODO.md: Paschaltide's own substitution (a single alleluia-form "Suffragium Paschale" replaces the whole set during Eastertide, rather than the ordinary set showing or being omitted) -- a separate, larger feature. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-12 06:59:17 -04:00
will	fb66f60770	Add St. Joseph's suffrage; fix Cross/BVM suffrage gating ... Three things prompted by today's date resolving wrong: 1. St. Joseph's own Lauds suffrage was never modeled at all. Added lauds-suffrage-joseph.yml, sourced from Tridentine 1906/1910 (the reference engine's "Tridentine - 1906" version) per direct instruction -- Monastic 1617's own suffrage set has no Joseph suffrage at Lauds, so this one genuinely comes from a different track than the other four. 2. The Cross suffrage's actual gating rule, live-verified against a plain ferial win, a plain Sunday win, a low-rank saint's own win (even bare Simplex), and Marian Saturday: it shows only when the bare temporal feria itself is what's being prayed -- the opposite of "Sunday or a feast of the Lord." Expressed as `!isSundayOrFeast(day)` (the same ferial/festive split Prime's capitulum already uses) plus one more exclusion for a named temporal identity like Marian Saturday, which isn't Sunday or a sanctoral win either but still isn't a bare ferial office. 3. The BVM suffrage is correctly dropped on Marian Saturday (unchanged behavior, just now understood and commented correctly): it's specific to a day whose own office is already Marian, confirmed via the same live source, not a guess. Also models St. Clare (Aug 12, Simplex under Monastic 1617) and surfaces active octaves in getDayLabel, since today's date was resolving as a plain ferial day instead of showing St. Lawrence's octave with St. Clare commemorated. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-12 06:51:22 -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	4548042b65	hours: split Saturday's Deuteronomy canticle back into its own two parts ... Per direct instruction: RB 13 says this canticle "in duas glorias" -- two pieces, each closing with its own Gloria Patri, framed by one shared antiphon (opening before the first, full only after the second) -- not joined into one continuous block the way this was first built. canticleText() now takes an optional verse slice so Saturday can ask for two. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-11 13:46:20 -04:00
will	5830e4cfd2	hours: build Lauds ... Opening versicle; Ps 66 (fixed, no antiphon at all); the weekday- variable psalm groups (Ps 50 plus 1-2 more, framed by their own antiphon each, wholesale-substituted by Sunday's Ps 50+117-share-one- antiphon shape); the weekday OT canticle; the Laudate psalms (148-150) under one more shared antiphon; the weekday chapter/responsory/hymn/ versicle bundle; the Benedictus (framed by a day-resolved antiphon, same incipit-or-full/full-repeat shape as Compline's Nunc Dimittis); the Kyrie/Pater-noster short litany; the day's collect(s) — winner plus one per commemoration, via the new getDayCollects; the four Tridentine suffrages (omitted on a Double-or-higher feast); the conclusio; the closing versicle (the silent Our Father that precedes it isn't re-rendered, its text having already appeared once at the short litany); and the closing Marian antiphon, reusing Compline's own mechanism exactly. Known, deliberate gap, not yet fixed: the psalmody doesn't model the Commune/feast override real practice applies on a Semiduplex-or-higher day (substituting an entirely different psalm+canticle set) — every day currently gets the plain ferial weekday distribution regardless of who wins. That's a separate, larger propers-authoring task (a full Common-of-Saints psalm set per Common). Also a simplification in getDayCollects: each collect in a multi- collect day renders as its own complete "Let us pray ... Amen." block, rather than the more compressed real form (one "Let us pray," only the last collect's doxology). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-11 11:45:25 -04:00
will	d06f9deb99	psalter: transcribe the 16 psalms and 7 OT canticles Lauds needs ... Ps 5, 35, 42, 50, 56, 62, 63, 64, 66, 75, 87, 89, 91, 117, 142, 148-150 weren't needed by any hour built so far. The 7 weekday OT canticles (Isaiah, Ezechias, Anna, Moses x2, Habacuc, the Three Young Men) get their own small store (src/hours/lauds-canticles.ts), separate from the Psalter, since they use their own liturgical verse-numbering per canticle rather than the Psalter's 1-150 numbering. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-11 11:44:53 -04:00
will	813d173f5c	hours: build Terce, Sext, and None ... Three separate resolver files (terce.ts/sext.ts/none.ts), not a shared little-hour module — they're structurally identical but kept independent by choice. Ordo verified against Divinum Officium (Monastic Tridentinum 1617): opening versicle, self-contained hymn, one antiphon framing three psalms (no closing repeat, unlike Prime), a capitulum with its own embedded short versicle/response, the day's own collect, and a closing identical across all three hours. Also fills in psalter-distribution.yml's previously-missing Sunday/ Monday/Tuesday psalm entries (Ps 118 sections for Sunday/Monday; Tuesday turns out to share Wednesday/Thursday's native gradual-psalm set, not a distinct one). Friday/Saturday's antiphons are derived from each day's first psalm rather than reusing the native gradual antiphons, since those two days already use a redistributed, non-native psalm set. hours/types.ts gains a 'day-collect' part kind — the first ordo to use the day's own Proper collect rather than a fixed text. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-10 13:51:08 -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	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	ec448bc35b	compline: build the full hour, sharing Prime's resolver helpers ... Ordo is Monastic 1617 as a base, with deliberate Tridentine 1906 additions: the "In manus tuas" short responsory, the Nunc Dimittis with its "Salva nos" antiphon, the fuller Preces (Monastic's own is shorter), and Lent's "Christe, qui lux es et dies" hymn replacement (English translation marked draft, pending a real historical one). Psalms 4, 90, 133 are fixed daily with real verified text, unlike Prime's weekday-rotated psalms. The closing Marian antiphon now picks Alma Redemptoris Mater / Ave Regina Caelorum / Regina Caeli / Salve Regina by real season, using the calendar work from the previous commit — except Ave Regina Caelorum's own window (Candlemas through the day before Maundy Thursday) doesn't align to any single season value, so that one case checks the real date directly instead of going through the by-season table. resolve-common.ts extracts the resolve/status/doxology/antiphon helpers Prime already had into something Compline can share; a few propers files lose their "prime-" prefix now that both hours use them.	2026-08-10 05:27:40 -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