feat(templates): ordo booklet in six flavours, pinned by goldens

LaTeX and groff are the print paths; HTML carries a print stylesheet;
AsciiDoc, Markdown and plain text are the plain-consumer paths.

AsciiDoc and Markdown use flavour none, and say so in a comment: their
metacharacters are context-dependent and escaping them aggressively
produces worse output than not escaping. The consequence is real and
documented -- a feast name containing * renders as emphasis.

Golden tests pin all six byte-for-byte for 2027. They prove the
templates RENDER, not that they TYPESET; compiling needs TeX and groff,
which is Task 13's opt-in make check-templates.

1 files changed, 23 insertions, 0 deletions

diff --git a/templates/ef/ordo.md b/templates/ef/ordo.md
new file mode 100644
index 0000000..606ea01
--- /dev/null
+++ b/templates/ef/ordo.md
@@ -0,0 +1,23 @@
+<!-- colitur ordo booklet -- Markdown. flavour: none -->
+<!-- Markdown's own metacharacters (*, _, `, [, ...) are context-dependent,
+     so this template's flavour deliberately does NOT escape interpolated
+     values. A feast name containing `*` or `_` will render as emphasis.
+     That is a documented limitation, not a bug to fix. -->
+<!-- Day label falls back to the slug when the day carries no Latin name
+     (most temporal days, and most sanctoral entries, which are Latin-less
+     in the shipped data) -- see ordo.tex's own comment for why the fallback
+     is written as a name-section wrapping a plain var and its inverse,
+     rather than a single dotted lookup and its inverse. -->
+# Ordo {{year}} · {{rite}}
+
+{{#months}}
+## {{name.la}}
+
+{{#days}}
+**{{dom}}** {{#name}}{{la}}{{^la}}{{slug}}{{/la}}{{/name}}
+`{{rank}}` · {{colour}}{{#first}} · Ep. {{first}}{{/first}}{{#gospel}} · Ev. {{gospel}}{{/gospel}}
+{{#comms}}
+- Com. {{slug}}
+{{/comms}}
+
+{{/days}}{{/months}}