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/calendar/temporal.ts

@@ -0,0 +1,8 @@
+// Temporal-cycle occurrence resolution: given a date, which temporal-id
+// applies (season, proper Sunday/feria), by combining two offset systems —
+// data/calendar/easter-offsets.yml (Septuagesima through Trinitytide) and
+// data/calendar/fixed-date-calendar.yml (Christmas, Epiphany). Also where
+// the Advent-start and Epiphanytide-length wrinkles noted in
+// fixed-date-calendar.yml get arbitrated. Depends on calendar/easter.ts for
+// the Easter date itself. Unused until milestone 4.
+export {};