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/calendar/sanctoral-calendar.yml

@@ -0,0 +1,12 @@
+# Maps a calendar day (MM-DD — the sanctoral cycle repeats every civil year
+# regardless of weekday, unlike the temporal cycle) to the saint-id(s)
+# celebrated that day. This indirection is the whole point: to move a saint
+# to a different day, edit this mapping. The saint's own record
+# (data/calendar/saints/<id>.yml) never changes — it's the same record
+# whichever day points at it.
+#
+# PLACEHOLDER: "01-01" -> example-confessor is fake data proving the shape,
+# not a real calendar assignment. Real sanctoral content-authoring
+# (a pre-1910-leaning calendar, per the plan) is a separate task.
+days:
+  "01-01": [example-confessor]