diff --git a/README.md b/README.md
index 428fe30..390c961 100644
--- a/README.md
+++ b/README.md
@@ -360,14 +360,21 @@ Internet → Apache :80/:443 (git.jayfield.org vhost)
   outright.
 - **Admin user renamed `jayfield` → `jens` 2026-07-26** (password rotated at
   the same time), via Gitea's own web admin panel (Site Administration →
-  User Accounts → Edit Account) rather than a direct DB/API edit — that's
-  the one code path that correctly moves the on-disk repo storage
-  directories and sets up a redirect together, rather than risking an
-  inconsistent rename. Verified: new credentials authenticate
-  (`GET /api/v1/user` → `"username":"jens"`), both the new canonical path
-  (`/jens/docs-alpha.jayfield.org`) and the old one (`/jayfield/...`, via
-  Gitea's automatic redirect) return `200`, and this repo's local `origin`
-  remote and stored git credentials were updated to match.
+  User Accounts → Edit Account) rather than a direct DB/API edit. There
+  was only ever this one account, and it owned all 89 repos — since
+  Gitea tracks repo ownership by numeric user id, not username, renaming
+  it instantly relabels every repo's owner as `jens`; nothing was moved
+  or duplicated. Verified: new credentials authenticate (`GET
+  /api/v1/user` → `"username":"jens"`), the new canonical path
+  (`/jens/docs-alpha.jayfield.org`) returns `200`, and this repo's local
+  `origin` remote and stored git credentials were updated to match.
+  **No redirect from the old `/jayfield/...` paths**: re-checked
+  2026-07-26 — both the bare old profile URL and old repo paths `404`,
+  and Gitea's own `user_redirect` table is empty, so this isn't just a
+  slow propagation. Whether a redirect was ever actually created here is
+  unclear; either way there's no functional impact (every real reference
+  already uses `/jens/...`) beyond old bookmarked/shared `/jayfield/...`
+  links no longer resolving. See `TODO.md` for the full investigation.
 
 ### Gitea backup to `vlda-01` (`SYNC-PLAN.md` item 2b)