diff --git a/TODO.md b/TODO.md
index a4f82ef..27333f7 100644
--- a/TODO.md
+++ b/TODO.md
@@ -20,6 +20,23 @@
     built-ins should keep answering the same setting.
   - Code: `src/client/components/Controls.tsx` (*What you see*), `src/client/state/usePrefs.ts`,
     `src/shared/routines.ts` (`activeRoutines`, `routineToAsk`), `src/client/components/Dailies.tsx`.
+- [ ] hololive Dreams has not refreshed in three weeks — find out why, or find it a new source.
+  The footer says (2026-10-13): *"Of the games you have switched on, this one has not refreshed in
+  over two days, so some end dates may have moved: hololive Dreams (21d 7h ago)."*
+  - What the repo shows: `snapshots/holodori-holodoriwiki-events.meta.json` was last confirmed
+    2026-09-22T17:28Z (content last changed 2026-09-22T05:28Z, one event parsed), and no
+    snapshot commit has touched it since. A `304` would still have stamped a confirmation, so every
+    cycle since then has either failed or skipped this host. The committed `.state.json` is older
+    (2026-09-12) because CI keeps live state in the Actions cache, not the repo.
+  - First: read the step summary and annotations of a recent `refresh.yml` run on Gitea for
+    `holodori-holodoriwiki-events` — its `lastStatus` and whether it was `skipped_robots`, failing
+    (and `broken` after three cycles), or parsing to zero. If needed, one manual dispatch with
+    `only: holodori-holodoriwiki-events` and dry-run off answers it (`--dry-run` makes no requests).
+  - Then, by cause: robots or an access block from the runner → AGENTS.md § Scraping conduct (no
+    workarounds; a manual refresh or another source). The wiki changed shape → repair
+    `src/ingest/parsers/holodori.ts` against a new fixture, keeping the old one. The wiki stopped
+    being maintained (`holodori.wiki` is a Miraheze wiki) → find another source; assess it in
+    `docs/SOURCES.md` as the others are.
 - [ ] Give *Add an event* and *Add a task* easy-to-use templates, and give both forms a UI/UX pass.
   - Templates: one tap fills the common shapes so the reader only adjusts the details — for
     example a weekly points task, a monthly shop reset, a login event, a banner with a known end.