v0.1.3: Reference data auto-merges, and schedule windows fire once per turn

The Count keeps his appointments: a window time is due on the first run after it, however often he is woken. Reference data such as CA root bundles is now fast-tracked, and the server no longer sweeps when it starts.

Added

• Reference data is fast-tracked (#8, @sweepies). CA root bundles, time zone data and the public suffix list now carry a reference-data kind on top of their own. A built-in first rule gives those updates no release-age wait, no schedule window, their own PR, and auto-merge once checks and required reviews pass. Covered packages include certifi, tzdata, pytz, publicsuffixlist, webpki-roots, webpki-root-certs, chrono-tz, psl, golang.org/x/crypto/x509roots/fallback, tldts, tzinfo-data, public_suffix and composer/ca-bundle. Open-PR and per-hour limits still apply to these PRs.

  To keep a reference data update on manual review, add a rule after the built-in one:

  rules {
    new Rule {
      select { kinds { "reference-data" } }
      apply { merge = false; waitHours = 24 }
    }
  }

  Assigning your own rules Listing replaces the whole list, including the built-in rule.

Breaking Changes

Schedule windows are due on the first run after each time (#9, @sweepies). A window's cron times are no longer matched only against the current minute. Each time an expression names is due on the first run after it, so "0 3 * * *" means once a day, after 03:00, whether the Count runs hourly, daily, from a webhook or from CI. Expressions that cover a range, such as every minute of a morning, still allow every run in that range. The Count records each repository's last successful run in its cache; dry runs and failed runs do not count.

Check these when you upgrade:

• The first run for a repository, before a run has been recorded, proposes only if the current minute matches a window time. This includes the first run after upgrading.
• Lockfile maintenance uses the same rule. Its default Monday 00:00 to 04:00 UTC window is now a real window.
• Weekdays use standard numbering: 0 or 7 is Sunday, 1 is Monday. The old parser counted 1 as Sunday, so "* 0-6 * * 1" ran on Sundays. The same numbering applies to the server's sweepCron.

The server does no sweep at startup (617c6cc). The first sweep is the next time the sweepCron schedule names. Queued work survives restarts, and the readiness probe still checks installations straight away. If you relied on a restart to trigger a sweep, wait for the schedule or use a webhook. The Railway guide now says to leave Serverless off, because the server's 30-second App probe keeps it awake anyway.

Fixed

• Auto-merge no longer waits for a window. The fallback merge checked windows, which the configuration guide never said it did, so a PR could wait a day after its checks passed. Windows decide when updates are proposed; release age still gates merging (#9, @sweepies).

Full Changelog: v0.1.2...v0.1.3