v0.3.12

Deployed November 3, 2026 to the public and private dashboards and the Cloud Run jobs, from main at 4b8f02b.

Changes since v0.3.11

• Data freshness, shown separately from check freshness: each check records when the publisher last changed its data (ArcGIS lastEditDate, HTTP Last-Modified, or the newest MnGeo county acquisition date). Each source has an expected update interval: an owner-set expected_update_days, or one learned from history, or a 90-day default. The private overview gets a Data freshness card, and source pages show the age, the interval and where it came from. Stale data never becomes an active alert (#197).
• Weekly digest: the new watchtower weekly-digest command reads saved state and logs one structured digest line. It lists stale sources oldest first, sources with no publisher time, and overdue checks, and it makes no provider requests. An informational alert policy emails it on Monday mornings (#197).
• Digest policy for a dedicated job: render_alert_policies.py --digest-job renders the digest policy for a job that runs only weekly-digest, so its scheduler needs no permission to override job arguments (#199).

Known limitations

• Provider-terms follow-ups join the digest with the CRM-backed terms view (#185).
• Sources checked only by the local worker learn no update interval in the digest. They use their configured interval or the 90-day default.

v0.3.11

Deployed November 3, 2026 to the public and private dashboards and both Cloud Run jobs, from main at 21eecb7.

Changes since v0.3.10

• Hosted private dashboard from the repository: the new watchtower private-dashboard command replaces the out-of-repo hosted wrapper. It is the ordinary dashboard server, read-only (no refresh; POST returns 405), syncing the aggregate and the cloud worker's history from storage, and trusting Identity-Aware Proxy only inside Cloud Run. The separate dashboard image is retired (#194).
• Active alerts on the private overview: derived from source status and freshness instead of "Alert status unavailable"; "No active alerts" appears only when every source is healthy and current (#194).
• Run history: each run records checked_at, rate_limited and deferred per source (#194).

Known limitations

• Hosted source sparklines cover cloud-worker history only.
• The private dashboard relies on IAP enforced on Cloud Run; it does not verify the IAP assertion itself.

v0.3.10

Deployed November 3, 2026 to the public and private dashboards and both Cloud Run jobs, from main at 6be9f09.

Changes since v0.3.9

• Provider-run alerting: alerts now fire on Watchtower tool failures (exit 3) instead of every non-zero exit, plus a new "no provider run in 26 hours" alert driven by a watchdog in the public publisher, and a publisher-absence alert (#192).
• Provider safety: a provider 429 backoff is saved, and shared, the moment it is signaled (#158, #164); a declined county reply or a limited scope constrains dispatch (#157).
• Data correctness: truncated ArcGIS results and malformed state are not treated as complete (#161); future publication, check and report times are shown as unknown (#160).
• Publisher hardening: public output is validated before it replaces the last publication, and source/destination aliasing is refused (#159).
• Maintenance: alert-ledger records are pruned after 180 days (#165); pyasn1 updated to 0.6.5 for four advisories (#163); build-input, accessibility and release-discovery fixes (#162); public release records exclude deployment evidence (#166).
• Operations: the private dashboard runs under its own read-only identity.

Known limitations

• The first daily provider run on v0.3.10 is still to be confirmed. The signed-in private-dashboard check passed.
• Release record: docs/release-v0.3.10.md.

v0.2.2 — Review corrections and Watchtower favicon

Version 0.2.2 fixes public GAC diagnostic sanitization, ArcGIS refusal handling, malformed GAC statistics, repeated contact-file loading, and duplicate table scroll regions. It also adds the supplied Minnesota Watchtower favicon at 16px and 32px.

The public/private dashboards and provider/publisher job images are deployed. The obsolete local worker was retired without changing any source observations, and the existing security job is now required on main.

Validation: 368 strict unit tests, full CI/security checks, independent bounded CCE patch review, mobile keyboard verification, and live public dashboard/export checks. All 35 source observations remain intact. Existing Hennepin imagery warning remains; no extra GIS-provider cycle was run. Private anonymous sign-in protection was verified; authenticated private rendering was not exercised.

Full deployment, validation, and rollback record

Exact deployed source: aba3d23b28ccf93b0de56b4b1b50d2518e3ffd43.

v0.2.1 — Open-source About panel and version guard

Highlights

GIS Data Watchtower is an open-source ClearParcel project that helps people explore Minnesota public GIS data, source monitoring, county access research, and Minnesota GAC field-population insights.

• Replaced the lengthy public boundary panel with a concise About section, approved disclaimer, and direct GitHub link.
• Simplified public version labels to v0.2.1, without visible build or production tags.
• Added a fail-closed deployment version check that requires each new application release to have a newer version.
• Includes the previously merged public static-output, provider retry handling, and accessibility fixes from PR #69.

Validation

• Built from exact source 9dbf6597f76aacf64e2ecbe55ba62d5757185921.
• Google Cloud Build c4be7733-8784-4d3b-ba7e-b1c06097af6d passed all eight build/verification steps.
• 359/359 unit tests passed.
• Live public dashboard and isolated preview passed page and export checks (35 monitored sources, 87 county profiles, 350 parcel-source records, valid Excel output).
• Public health is HTTP 200. Private anonymous login redirect remains in place; authenticated private rendering was not independently tested.
• Provider monitoring and sanitized publication schedules were preserved.

See full deployment evidence and rollback guidance.

Live dashboard: https://gis-watchtower.clear-parcel.com/

v0.2.0 — County status and inline dashboard

Watchtower v0.2.0 is live at https://gis-watchtower.clear-parcel.com/.

• Selecting a county updates the adjacent pane with monitoring details, field-population graphics and dated direct-feed MN GAC schema evidence.
• Map and county panes retain equal heights, including mobile layouts. The simplified county chooser shows each name once.
• Map categories distinguish statewide standardized availability, differing direct schemas, fee-policy restrictions, unassessed open schemas and unresolved access. Unavailable percentage observations use N/A.
• Olmsted and 12 other direct counties also appear in MnGeo Open Parcels. Unique coverage remains derived at 70/87 counties.
• Stale selection responses are canceled; missing county/source pages return HTTP 404. County exports share schema findings.

Built from merged commit 308e3a720886db080b908d7a91719e6732b0d736 after passing CI and 340 offline tests. Preview and production page/export acceptance passed. Public revision 00014-jsr and private revision 00021-hr8 receive 100% traffic. Runtime settings, IAM, private authentication, schedules and provider observations were preserved.

Daily Google Cloud provider polling is already enabled at 5:00 AM America/Chicago. Latest activation results: 35/35 healthy sources. The five-day observation study remains incomplete; normal Codex Cloud development acceptance is separate. Signed-in private-session acceptance was not performed.

Deployment evidence, immutable images and rollback targets.

v0.1.2 — Dashboard and reporting fixes

Changes

• Repair corrupted punctuation in public display labels while preserving identifiers and valid Unicode.
• Use a packaged transparent ClearParcel footer logo.
• Correct version reporting when an editable installation contains stale metadata.
• Report unknown and unsupported source statuses as unknown health instead of healthy.
• Restrict Cloud Build uploads to public application inputs.

Validation

322 local tests passed. The merged commit passed all six Windows/Ubuntu and Python 3.12–3.14 CI lanes, dependency audit, CodeQL, container smoke test and vulnerability scan. Installed-wheel checks and five local dashboard routes passed. Fresh visual browser acceptance was unavailable.

Deployment status

Deployed on October 10, 2026 from a3899f6 (PR #60). The live public dashboard serves revision 00012-c5j; the private IAP-protected dashboard serves 00020-lqc; the isolated preview serves 00018-rkt. The existing sanitized publisher uses the new production image.

Preview and production page/export checks passed, including all 87 county CSV rows and unchanged facts for all 35 source observations. Runtime settings and access controls were verified unchanged. The private wrapper hash is unchanged and anonymous access still redirects to Google authentication. Public publication health returned 200.

Live dashboard: https://gis-watchtower.clear-parcel.com

Production image: sha256:003c60772fc5a5fa1f91ccabbd840c60a4ca52d14160078f7df65adf3205b8b7.
Private derivative: sha256:fada00d83d7c5da6462d453a54cc6822ba292201935a1d42061ed62d3cbc96a2.

Provider scheduling, private registries, credentials and worker retirement are unchanged. The multi-day cloud activation and Codex Cloud readiness gates remain separate and incomplete. See docs/release-v0.1.2.md for the review scope and remaining limits.

The first scheduled publisher execution on the new image, gis-data-watchtower-public-publisher-ndhgm, completed successfully at 2026-10-10T23:55:12Z. Its new public snapshot passed page/export and source-observation parity checks.