UK ICO breach notifications

https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/

Information Commissioner's Office breach announcements. WebFetch returns HTTP 403 (ICO filters the routine UA; re-confirmed 2026-05-08). REQUIRED FETCH METHOD: `python3 tools/fetch_source.py url https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/`. For specific enforcement action listings use `python3 tools/fetch_source.py url https://ico.org.uk/action-weve-taken/enforcement/`. | 2026-06-20 full audit (v2.62): live=Y, drill=Y. FETCH → api: python3 tools/fetch_source.py ico-uk enforcement N (returns enforcement URLs from sitemap; then `url <enforcement_url>` for body). News index via `url https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/`.. AVOID: WebFetch 403s the routine UA, skip it, use the bridge. Article body text sits inside <main id='main-content'>; the page leads with a large cookie-banner JSON island so naive byte-range reads miss the body.. | 2026-07-05 admiralty audit: A, first-party government regulator publishing its own enforcement/breach decisions; primary authority for its jurisdiction. HIGH->A, stays active. | 2026-07-28: bridge returned the JS-rendered page shell with no dated listing. No demotion, transport/anti-bot block, not content death. | 2026-07-30: fetch_method bridge -> jina. S2 reached https://ico.org.uk/action-weve-taken/enforcement/ with HTTP 200 but the enforcement-action list sits behind a JS-hydrated block grid and no dated /enforcement/action/<slug> hrefs surface in the raw body. Switching fetch_method to jina to hydrate the listing. Transport block, not source death, no demotion (HTTP 200 throughout). | 2026-08-02: flagged needs-demote by the sweep, diagnosed as the reader-credential outage, NOT a recipe break. All four pooled jina keys report HTTP 402 (exhausted, negative balance) this run, and this record is pinned fetch_method: jina precisely because the listing is JS-hydrated. Direct alternatives probed this run: https://ico.org.uk/action-weve-taken/enforcement/ and the news-and-blogs listing both return HTTP 200 with a browser UA but expose no dated enforcement hrefs in the raw body (the hydration problem the 2026-07-30 note already recorded), and /rss paths under both return 404. No demotion; HTTP 200 throughout and the recipe is intact; the source returns as soon as reader credit is restored. | 2026-08-15: health-probe failure this run is an artifact of the exhausted reader key pool, not a recipe defect; fetch_method is pinned to the reader. Not demoted; re-probe once the pool is topped up. | 2026-08-16: source_health flagged needs-demote; a serial re-probe this run returned 50 KB through the generic `url` bridge. Same parallel-contention artifact as ncsc-ch-incidents. NOT demoted. | 2026-08-16 weekly (RECIPE FIX): fetch_method jina -> bridge. The record was pinned to the reader, which is why source_health kept flagging it needs-demote while the reader pool sat at HTTP 402, the generic `url` bridge reaches this host directly and returned 50 KB for /action-weve-taken/enforcement/ and 40 KB for the media-centre listing on a serial probe this run. Pinning to the reader was the defect; this is a fix, not a workaround. Cite the per-action /action-weve-taken/enforcement/<year>/<month>/<slug> or media-centre URL. | 2026-08-18: RECIPE FIX CANDIDATE: /media-centre/news-and-blogs/ returned 404 on the direct transport this run, while current ICO news items resolve under /about-the-ico/media-centre/news-and-blogs/YYYY/MM/. The enforcement listing remains a client-side-filtered application with no server-rendered result links on any transport.