will
7816450086
St. Zephyrinus (Aug 26, common-of-a-martyr-bishop, Simplex) claims First Vespers over St. Louis's Aug 25, but that evening was showing the plain ferial hymn instead of a real Common-of-a-Martyr hymn: no content had been authored yet for this Common category's Lauds/Vespers bundle, so resolveOfficeBundle's chapter lookup came back missing and the whole bundle fell through to the ferial default. Live-verified against Divinum Officium (Monastic Tridentinum 1617) votive=C2b: chapter Jac 1:12, Lauds hymn "Martyr Dei, qui unicum," Vespers hymn "Deus tuorum militum," shared versicle "Justus ut palma florebit." Used the votive-office view rather than a real saint's own day for the same structural reason as the earlier Confessor-Not-Bishop fix: every real Common-of-a-Martyr-Bishop saint either has proper content of his own (St. Lawrence, St. Stephen) or never reaches the rank needed to keep his own Vespers (St. Zephyrinus, St. Callistus). Cross-checked votive=C2/C2a/ C2b/C2-1 all render identical text, so the same 7 files were duplicated under the plain common-of-a-martyr id too (St. Hadrian, St. Hermes, St. Fidelis of Sigmaringen). Updates one existing Vespers test whose date (2026-03-03) turned out to also anticipate St. Lucius I's First Vespers, previously masked by this same content gap; adds two new proof tests and a TODO.md entry. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014axryJBrRswYh2niA7WCUc
vu
A static, offline-first PWA for praying the Divine Office — Matins, Lauds, Prime, Terce, Sext, None, Vespers, and Compline — in bilingual Latin/English, for any given date.
This isn't a reconstruction of any single historical breviary. It's a personal design that
draws on several historical sources without reproducing any one of them exactly: hour
structure chiefly from the Monastic Tridentinum (1617), precedence/rubrics from Divino
Afflatu, and a calendar merged from both the Tridentine 1906 and Divino Afflatu calendars,
with more generous handling of commemorations and octaves than any one historical rite used.
See CLAUDE.md (gitignored, not shipped in this repo) or the project's own notes for the full
rationale if you're extending it.
There's no backend and no database — everything is a pre-built static bundle, and the app is designed to keep working fully offline once it's been loaded once.
Development
Requires Node.js (developed against Node 20+).
npm install
npm run dev # start the Vite dev server
npm run build # type-check (tsc --noEmit) and produce a production build in dist/
npm run preview # serve the production build locally
npm test # run the test suite (vitest)
Run a single test file or a subset by name:
npx vitest run tests/hours/vespers.test.ts
npx vitest run -t "some test name"
Running in production
The app is entirely static once built, so "running it" just means serving dist/ — any static
file host works, as long as it falls back to index.html for unknown paths (the app does its
own client-side routing for URLs like /2026-08-09/prime).
Docker
A Dockerfile builds the static bundle with Node and serves it with Caddy:
docker build -t vu .
docker run -p 8080:80 vu
Or with Docker Compose (docker-compose.yml is included):
docker compose up -d --build
This serves the app on http://localhost:8080. Put a reverse proxy/TLS terminator in front of
it for a real deployment; the container itself just listens on port 80 internally and has no
configuration, secrets, or external dependencies.
Without Docker
Any static file server works — build the app, then serve dist/ with SPA-style fallback
routing. For example, with Caddy directly:
npm run build
caddy file-server --root dist --listen :8080
(For a real deployment you'll want a fallback rule so unknown paths resolve to index.html —
see the Caddyfile in this repo for the pattern.)