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/index.ts

@@ -0,0 +1,23 @@
+import type { LiturgicalDay } from './types';
+import { weekdayOf } from './weekday';
+
+/**
+ * Resolves everything about a given day *except* hour content — weekday,
+ * season, and any occurring feasts. Season and occurring feasts are stubs
+ * until calendar/easter.ts and calendar/feasts.ts land at milestone 4;
+ * hours that only need weekday (Prime, Compline, Terce, Sext, None) can
+ * already rely on this fully.
+ */
+export function resolveDay(isoDate: string): LiturgicalDay {
+  return {
+    date: isoDate,
+    weekday: weekdayOf(isoDate),
+    // Placeholder string, not a real resolution — real season/temporal-id
+    // lookup (data/calendar/easter-offsets.yml + fixed-date-calendar.yml)
+    // lands at milestone 4.
+    season: 'trinitytide',
+    occurring: [],
+  };
+}
+
+export type { LiturgicalDay, OccurringFeast, Season, Weekday, FeastRank } from './types';