feat: map sanctoral vigils and attach them to their feast (#27) #343
No reviewers
Labels
No labels
area: build
area: ci
area: compare
area: data
area: engine
area: model
area: provenance
area: rite
area: validation
backport
blocked
breaking
confirmed
dependencies
duplicate
epic
github_actions
invalid
needs-info
needs-triage
php
priority: high
priority: low
priority: medium
regression
type: bug
type: chore
type: correction
type: docs
type: enhancement
type: feature
type: fix
type: perf
type: refactor
type: security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Directorium/Core!343
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/27-sanctoral-vigils"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #27. Epic #23, issue 4/6.
What
Seeds the four sanctoral vigils that survive the 1960 reform, each kept on
the day before its feast, violet, and linked to it via
vigilOfId:feast (10 Aug, II, red) is seeded alongside its vigil.
data → never emitted.
SanctoralObservancenow carriesvigilOfIdthrough from the entry, so therealized office exposes its parent link for the resolver's vigil boundary (#29).
Correctness
Adversarially verified against the 1962 Missal (Divinum Officium source data):
the set is complete, ranks/colour confirmed (II/II/III/II, violet), and all
four Latin titles match — no corrections needed.
Verification
composer lint·composer analyse(PHPStan L6, no errors) ·composer test(387 tests, 16,541 assertions — +5). Commits signed + DCO.