aboutsummaryrefslogtreecommitdiff
path: root/lib/kernel/date_spec.mli
diff options
context:
space:
mode:
authorLukasz Kasprzak <lukas@labunix.xyz>2026-08-14 12:41:10 +0200
committerLukasz Kasprzak <lukas@labunix.xyz>2026-08-14 12:41:10 +0200
commitd0468f53820585e7b4e4bfeb9a4a18f672b821a5 (patch)
treee739546256e34e16d651c69b86d8a898b50b4191 /lib/kernel/date_spec.mli
parent112781d6e3b92310d9d657c53a7e0fc789aefdfb (diff)
downloadcolitur-d0468f53820585e7b4e4bfeb9a4a18f672b821a5.tar.gz
colitur-d0468f53820585e7b4e4bfeb9a4a18f672b821a5.zip
test,docs: tighten M21, and record what the bucket summary does not say
M21 accepted `subset diffs [Colour_f; Comm_identity_unresolved]`, so a row with no colour diff at all could be absorbed under a colour citation. The unresolved allowance existed only for the 22 February rows the previous commit reverted; with those gone the predicate tightens to exact equality on Colour_f, matching C18's shape, and stays green. Records two things the audit's bucket summary did not carry. The effective dataset is 329, not 328: base 327 plus three overlay Adds minus one Suppress, so commemoration-of-st-peter and major-litanies fall outside both buckets despite being in the stated scope, and a suppressed entry is counted as verified. And the summary says colour was "independently checked against RG 124" for every entry where much of it is inferred from the saint's category rather than read -- the per-entry basis column makes that distinction and the summary line erases it. Also records that "zero blast radius" holds only for the observed office: 49766 commemoration-colour changes on 8 slugs are real data changes, invisible because the CLI omits commemoration colour.
Diffstat (limited to 'lib/kernel/date_spec.mli')
0 files changed, 0 insertions, 0 deletions