feat(kernel): movable Date_spec variants, and Rogation Wednesday

Date_spec carried one variant, Fixed(month, day), and its own header said
Sunday- and Easter-relative forms would arrive with the OF sanctoral. They
arrive early because two things needed them at once: a user-supplied
overlay carrying a local movable feast had no way to express "the first
Sunday of October", and Rogation Wednesday's commemoration has been
recorded as architecturally blocked since 2026-08-13.

That blockage turns out to have been a premise, not a fact. The register
concluded the Rogation "is not Commemoration_only sanctoral data by
nature... it needs a genuinely THIRD kind of thing this architecture has
no name for" -- but the reasoning rested on there being "no civil (month,
day) pair to anchor a Fixed entry to". That is a statement about
Date_spec's expressiveness. With Easter_offset the entity is ordinary
sanctoral data, the identical shape Add major-litanies already ships,
differing only in how the date is written. No third channel was needed.
The register is corrected rather than left contradicting the code.

Two variants: Easter_offset of int, and Nth_weekday of {month; nth;
weekday} with negative nth counting from the end. Fixed's sexp
representation is untouched, so all 327 sanctoral entries and the whole
overlay parse unchanged. Both are re-validated in t_of_sexp through their
smart constructors, extending the idiom Fixed already used -- the failure
that guards against is invisible, a spec deserialising into something
that silently never resolves and a celebration vanishing with no
diagnostic.

Easter is supplied by the rite, not computed in the kernel. Computus
ships Gregorian and Julian both, and picking one here would hard-code a
Roman assumption into rite-agnostic code and be silently wrong for a
Julian-reckoning rite. Rite.t gains an easter field; Rite_ef supplies the
Gregorian one.

Layer keeps a split index. Fixed entries stay in the year-independent
(month, day) table, which preserves the fast path and the "30 November
counted twice in a 371-day span" behaviour validate.mli documents for St
Andrew. Movable entries have no year-independent key by construction --
the same spec lands on a different (month, day) each year -- so they
resolve per civil year into a rata-die table. index_by_date is removed
rather than kept as an alias: two ways to index a layer, one of which
silently ignores movable entries, is the trap this change exists to
avoid.

Two domain-edge defects, both found by the suite rather than reasoning. A
liturgical year is Advent-anchored, so resolving civil year y names y +/-
1, and at the edges those are 1582 and 10000, which Computus correctly
refuses by raising. The ceiling surfaced through the domain-ceiling test,
the floor through `colitur day 1583` failing outright. Fixed once, in
Layer.index, the single point that calls the rite's easter -- a clamp
repeated per caller would have been two places to get wrong a third time.

Rogation Wednesday: RG 87 assigns the Litaniae minores to the Monday,
Tuesday AND Wednesday before Ascension (scan1:691); colitur built the
first two from the start and never the third. RG 88 keeps it out of the
Office, so the Ascension Vigil remains observed. RG 89 routes it through
the Major Litanies' rules, but RG 109's closed list names only maiores,
so by RG 107 it is an ORDINARY commemoration -- confirmed in the output,
not assumed. Name from the Missal's own "feria IV" (scan1:20495-20497),
violet to match the Monday and Tuesday offices.

Blast radius, full 1583-9999 sweep against the pre-change binary: 2257
days, every one the same shape, zero unclassified, line counts equal both
sides. The complement is the informative half -- in the other 6160 years
the Rogation does not appear at all, because RG 111 admits one
commemoration on a II-class day and an impeded feast takes it under RG
113, a Commemoration_only candidate having no row in RG 91's table. Both
shapes are pinned.

Allow-lists unmoved: layer 3 compares no commemorations and is blind by
construction, and layer 4's 2026-2027 window has a competing feast on
both Wednesdays, so the Rogation is capped out in exactly the years the
oracle can see. C8 is unchanged, asserted by its own count pin.

Not built: Sunday-relative specs, which nothing needs yet, and the
--overlay plumbing that would let a user actually supply a local movable
feast. Nth_weekday therefore ships with synthetic and property coverage
only; inventing a shipped entry to exercise it would be fabricating
calendar data.

Register: section 6.10.

1 files changed, 17 insertions, 3 deletions

diff --git a/CLAUDE.md b/CLAUDE.md
index 39ca55a..f09c555 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -61,6 +61,18 @@ tool, not part of lectio.
 Rite-agnostic **kernel** + **rite modules** (plug in via a signature) + **data
 overlays**.
 
+- **`Date_spec` carries MOVABLE dates** (2026-08-17): `Fixed(month,day)` as
+  before, plus `Easter_offset of int` and `Nth_weekday of {month; nth;
+  weekday}` (negative `nth` counts from the end). `Fixed`'s sexp form is
+  unchanged, so all 327 sanctoral entries parse untouched. Easter comes from
+  the RITE (`Rite.t`'s `easter` field) — the kernel ships both Gregorian and
+  Julian and must not pick. `Layer` keeps a **split index**: fixed entries in
+  the year-independent `(month,day)` table, movable ones resolved per civil
+  year into a rata-die table, with the domain filter in `Layer.index` itself
+  (both edges, 1582 and 10000, bit during development). This unblocked
+  **Rogation Wednesday** (RG 87/88/89, register §6.10) and is what a
+  user-supplied overlay needs for a local movable feast. The `--overlay` CLI
+  plumbing is **not yet built**.
 - **Kernel** (`lib/kernel`, pure, total, bounded 1583–9999): `Computus` (Gregorian
   + Julian Easter + anchors), `Date` (proleptic Gregorian arithmetic), `Overlay`
   (ordered layer-merge algebra: field-level add/suppress/replace/edit, last-writer-
@@ -242,8 +254,8 @@ against missalemeum; layer 5 pins ~30 dates.
 **Plans 1 + 2 are on `main` (35 commits). Plan 3 and its follow-on fix/feature
 tasks (RG 16(a), Holy Family/RG 112(a), Holy Name/RG 110, the Sacred Triduum,
 the BVM Saturday Office, the Major Litanies) have landed on a chain of feature
-branches since — test count keeps climbing task by task (374 tests green, 375
-with the exhaustive sweep, as of `ef-oracle-2038`; this line is not kept in
+branches since — test count keeps climbing task by task (388 tests green, 389
+with the exhaustive sweep, as of the movable-date-specs task; this line is not kept in
 lockstep with every task, `git log`/`dune test` are the actual source of
 truth).** The kernel, the **complete EF
 temporal cycle**, the **resolution engine**, the **sanctoral data**, and **all five
@@ -291,7 +303,9 @@ M20 added by the `ef-major-litanies` task, M18 394 not 395 accordingly).
 Fixtures live in `test/fixtures/` with asserted SHA-256s.
 
 **CLI**: `colitur easter <year>`, `temporal <year>`, `day <year>`,
-`readings <year>`, `-h`/`--help`. Man page in `man/colitur.1`.
+`readings <year>`, `-h`/`--help`, `-V`/`--version`. Man page in
+`man/colitur.1`; `Makefile` installs binary + data + man page into `~/.local`
+by default. Tagged **v0.1.0**.
 
 `--help` prints to **stdout** and exits **0**; a usage error prints one line
 to **stderr** and exits **2**. The distinction is asserted in `test/cli.t`,