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>

src/data/psalter-distribution.yml

@@ -0,0 +1,16 @@
+# PLACEHOLDER distribution: real Benedictine Prime actually distributes
+# multiple fixed psalms plus a rotating section of Ps 118 across the week,
+# and the user has modifications in mind on top of that — none of that is
+# designed yet. This file exists only to prove the (hourId, weekday) -> psalm
+# numbers lookup works end to end, using the one psalm we have sample data
+# for. Expect this file to be rewritten entirely once real content-authoring
+# starts (see plan: "psalter modifications are edits to this data, not
+# engine changes").
+prime:
+  sunday: [1]
+  monday: [1]
+  tuesday: [1]
+  wednesday: [1]
+  thursday: [1]
+  friday: [1]
+  saturday: [1]