feat: output, rendering and publishing

Gives colitur a publishable exit. Until now its only output was terminal
rows; it can now print an ordo booklet and a wall calendar, publish an
iCalendar feed people subscribe to, and serve a static JSON/XML API.

  lib/render   escaping (six flavours + RFC 5545 folding), a deliberately
               logic-less template engine, the view model, and five
               emitters (CSV, JSON, XML, iCalendar, S-expression)
  CLI          emit, table, render, publish -- all accepting --overlay
  templates    ordo booklet in six flavours, wall grid in three
  schema       day-v1.json and colitur-v1.xsd, the published contract
  man          colitur-templates.5, plus colitur.1 updates

The view model is why the engine can stay logic-less: a month grid needs
leading blank cells, week bucketing and an in-month test, and a
logic-less template can compute none of it. Shaping the data in OCaml
keeps the engine safe for untrusted templates and makes the grid
trivial.

Formats split by whether correctness is mechanical. Presentation goes
through templates; iCalendar and XML get dedicated emitters, because
folding, exclusive DTEND, stable UIDs and schema fidelity are rules a
template cannot enforce and each fails silently in a subscriber's
client rather than loudly at generation.

publish is deterministic and non-destructive: two runs produce a
byte-identical tree, and --prune removes only files a previous run
created, refusing any manifest entry that escapes the output directory.

No new dependencies. The kernel and rite modules are untouched, and
colitur day and colitur readings remain byte-identical.

1 files changed, 24 insertions, 0 deletions

diff --git a/lib/render/view.mli b/lib/render/view.mli
new file mode 100644
index 0000000..fb48590
--- /dev/null
+++ b/lib/render/view.mli
@@ -0,0 +1,24 @@
+(** Shapes a civil year of resolved days into the value a template renders
+    against (spec section 4).
+
+    This layer exists because a month grid needs leading blank cells, week
+    bucketing and an "is this cell in the current month" test, and a logic-less
+    template can compute none of it. Shaping the data here keeps the engine
+    logic-less AND makes the grid template trivial. The view model IS the design.
+
+    Both [weeks] and [days] are offered at every level: the booklet walks
+    [days], the grid walks [weeks]. One model, two artefacts, no second code
+    path that could drift.
+
+    Colours are exposed as six booleans rather than a hex string: hex would bake
+    a presentation policy into the engine, and LaTeX, groff and HTML each want a
+    different colour expression. Exactly one of the six is true on every day. *)
+
+val of_days :
+  vocab:('s, 'r) Colitur_kernel.Vocab.t ->
+  rite:string ->
+  year:int ->
+  ('s, 'r) Colitur_kernel.Liturgical_day.t list ->
+  Template.value
+(** [of_days ~vocab ~rite ~year days] where [days] is one civil year, 1 January
+    to 31 December, in order. Pure and total. *)