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/saints/example-confessor.yml

@@ -0,0 +1,9 @@
+# PLACEHOLDER — demonstrates the saint-record shape only. Not a real saint,
+# not a real rank, not a real day assignment (see sanctoral-calendar.yml for
+# where this id gets pointed at a day). Which day(s) point here can change
+# freely without ever touching this file.
+id: example-confessor
+name: "Example Confessor (placeholder)"
+rank: placeholder # real rank scheme is a milestone 4 decision, not made yet
+common: common-of-a-confessor-not-bishop
+propers: null # set to a propers id once/if this saint has a full proper