diff --git a/TODO.md b/TODO.md
index 155f500..8e4feb0 100644
--- a/TODO.md
+++ b/TODO.md
@@ -39,12 +39,23 @@ compute of its own yet.
       ceilings sum to 4.5GB. Revisit if arena's heaps come down — 8GB is
       headroom for a ceiling nothing has been observed to reach.
 - [ ] **The reports behaviour has no health check of its own.** `/reports/*`
-      is a second origin on the site's distribution, so the api host being
-      down is now a hole in lance.blue rather than only in api.lance.blue.
+      and `/unfurl/*` are the api host on the site's distribution, so the api
+      host being down is now a hole in lance.blue rather than only in
+      api.lance.blue.
       CloudFront serves its cached copies through it - a finished match never
       changes, so most reads are edge hits - but a cold URL 502s, and that
       502 is no longer cached. Whatever raises its hand for the api host
       should raise it for this too.
+- [ ] **Nothing checks that a player's link still previews.** The split is
+      made on the User-Agent in `index-rewrite.js`, so it is invisible in
+      both directions: a fetcher this list has never heard of quietly gets
+      the site's generic card, and a name added to the list by mistake sends
+      readers to the api host. `node --test
+      modules/static-site/index-rewrite.test.mjs` covers the function's own
+      logic; what nothing covers is the deployed distribution actually doing
+      it, which is one `curl -A` against each prefix and belongs wherever
+      `scripts/health.sh` ends up.
+
 - [ ] **Nothing says which index a deployed site expects.** The site pins a
       MegaMek version in its own source and fetches `/assets/helm/…`; nothing
       here fails when the pinned pair has no index published. The check