Run the paid canary weekly instead of daily

.github/workflows/canary.yml

@@ -1,6 +1,6 @@
 name: canary
 
-# One real run daily against a known-good search URL, >=3 pages, so
+# One real run weekly (Mondays; every run bills the proxy) against a known-good search URL, >=3 pages, so
 # pagination is exercised and not only page 1. Artefacts are uploaded on
 # every run, so a red canary can be diagnosed from the run alone.
 #
@@ -14,7 +14,7 @@ name: canary
 
 on:
   schedule:
-    - cron: "17 6 * * *"  # daily, off the hour to avoid the top-of-hour GitHub Actions crush
+    - cron: "17 6 * * 1"  # Mondays (weekly: every run bills the proxy), off the hour to avoid the top-of-hour GitHub Actions crush
   workflow_dispatch: {}
   # Also run when THIS file changes. A canary is the one workflow that
   # can sit broken for a full day before anyone finds out.

CHANGELOG.md

@@ -9,6 +9,12 @@ here rather than treated as a violation of the format.
 
 ## [Unreleased]
 
+### Changed
+
+- CI only: the canary bills the `ZIMMO_PROXY` exit, so its schedule is now
+  weekly (Mondays 06:17 UTC) instead of daily; a manual dispatch, and a push that
+  changes the canary file, still run it.
+
 ## [2.0.0] — 2026-10-15
 
 > **Major version for a schema break.** 2.0.0 is the same code as 1.3.0,

README.md

@@ -285,7 +285,7 @@ Scraping Browser API session), or supply a display yourself and pass
 `--headful`.
 
 A separate `canary` workflow runs live against a real filtered category
-once a day: 3 pages, headful under xvfb, with assertions on the share of
+once a week (Mondays): 3 pages, headful under xvfb, with assertions on the share of
 rows carrying a price, living area, bedrooms, energy grade and property
 type. It needs a residential exit — measured 2026-09-23 and 2026-10-13,
 GitHub's runner is refused like any datacentre address, and a US