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/hours/prime.yml

@@ -0,0 +1,14 @@
+# PLACEHOLDER structure: proves the fixed-parts + weekday-variable-psalm
+# pipeline works. The hymn/chapter/prayer textRefs don't resolve to real
+# text yet (data/propers/ doesn't exist yet) — they render as "pending"
+# in the UI. Real content is a separate task from this scaffolding.
+id: prime
+parts:
+  - kind: hymn
+    textRef: { source: common, id: hymn-iam-lucis-orto-sidere }
+  - kind: variable
+    resolve: by-weekday
+  - kind: chapter
+    textRef: { source: common, id: prime-chapter-ferial }
+  - kind: prayer
+    textRef: { source: common, id: prime-collect }