...

Unfortunately we can't just use code-rev and ruleset alone, since corpora change over time (and don't have a handy ID number like code-revs do). So I'm just using the date when the mass-check started, as the ID number identifying the corpus version. (that also takes care of 'date and time of execution', too.)

Timezones And Edges

Since the daily tag occurs at 0850 UTC, the 'date' part of the daterev string wraps around at 0800 UTC, just before that tag event. So, for example, here's a table of time_t value, time+date as string in the UTC timezone, and the corresponding daterev:

...