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/hours/matins.ts

@@ -0,0 +1,8 @@
+import type { ResolvedOrdo } from './types';
+
+// Milestone 5, most complex. Needs its own resolution path (reading-candidate
+// pool + rank/season-driven slotting), not the static parts-array pattern the
+// other hours use — see the plan's "Matins schema seam" note. Not built yet.
+export function resolveOrdo(date: string): ResolvedOrdo {
+  return { hourId: 'matins', date, parts: [], notImplemented: true };
+}