Repository README carried dated and undated counts of the same set, fix mandates timestamps

A software repository's README file contained three references to the same set of filed submissions, but only one of those references included a dated epoch while the other two did not. As new submissions were filed, the undated counts became stale, revealing a consistency gap rather than mere carelessness — the dating mechanism already existed in the file for the same object. The maintainer closed the issue at commit R286 on 2026-09-15, establishing that any count is a measurement and must be dated at the time it is taken. A related issue three days earlier, at commit R242 on 2026-09-12, found that a review had incorrectly asserted a withdrawn annotation was present in a committed file without reproducing the artefact. The repository responded by adding a review rule requiring that claims about artefact contents be verified by producing the artefact both ways and comparing results, not by reading source code alone.