will
83bf55efdb
New ResolvedPart kinds (nocturn-psalmody, te-deum) and lesson fields (nocturn, source, isGospel, responsory) in hours/types.ts. Three new content-store modules: propers/bible-plan.ts (the user's own continuous scripture-reading plan, replacing the historical Nocturn-1 lectionary), propers/nocturn-readings.ts (general feast/temporal-day Nocturn 2-3 readings, extending propers/octave-readings.ts's combine-into-one-reading pattern via a newly-exported resolvePassages), and propers/matins-responsories.ts (a per-book responsory pool, matched loosely rather than by exact citation). Data: Sunday's fixed 12-psalm/3-canticle psalmody (live-verified against the reference engine), the invitatory antiphon, ferial hymn and capitulum, the Te Deum, a seeded Isaiah responsory, two live-transcribed scripture chapters, and the two bible-plan rows needed for this pass' proof content.
22 lines
1011 B
YAML
22 lines
1011 B
YAML
# The user's own continuous scripture-reading plan, row "14th Sunday
|
|
# after Trinity" -> "Tob 1-2, Sir 45" (temporalId post-pentecost-15 =
|
|
# "14th Sunday after Trinity" in this app's own Trinity-counted display
|
|
# label — Trinity Sunday itself is post-pentecost-01, so "Nth Sunday
|
|
# after Trinity" is always post-pentecost-(N+1); see calendar/
|
|
# day-label.ts and calendar/temporal-id.ts). No Gospel reading on this
|
|
# Sunday row — confirmed a deliberate editorial choice across the whole
|
|
# plan (the user's plan never puts a Gospel reading on a Sunday), not a
|
|
# gap. This Sunday's own Nocturn 1 (see hours/matins.ts) uses this data;
|
|
# Nocturns 2-3 use the day's own patristic/Gospel content instead (see
|
|
# src/propers/nocturn-readings.ts).
|
|
temporalId: post-pentecost-15
|
|
weekday: sunday
|
|
readings:
|
|
- passages:
|
|
- { book: tob, chapter: 1 }
|
|
- { book: tob, chapter: 2 }
|
|
status: { la: missing, en: missing }
|
|
- passages:
|
|
- { book: sir, chapter: 45 }
|
|
status: { la: missing, en: missing }
|