docs: restore the real account names, which belong only on this branch

main's history was redacted on 2026-08-20: every archived account name was
replaced throughout all 65 commits, because main is published to GitHub and
the list of accounts identifies the archive as surely as a hostname does. The
viewer's test fixtures now use synthetic names chosen to preserve exactly what
each case tests — a leading digit, an underscore, a dotted username, a
bracketed or dotted highlight title, and the trailing U+2800 that case 12
exists for.

The redaction swept these three docs too, since they were in the same history.
This puts the real names back, on the branch that is not published. The
scripts needed nothing: they are generic and never named an account.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UXfdJu7QhSJLr47K7koTDF

docs/jdownloader.md

@@ -1,8 +1,9 @@
 # JDownloader2 — archive fetching
 
 > **This file lives only on the `tooling` branch.** `main` is published to
-> GitHub and deliberately carries none of this. Keep host details, IPs and
-> account names here.
+> GitHub and deliberately carries none of this — not the host details, not the
+> IPs, and not the account names. `main`'s history was redacted on 2026-08-20;
+> real names exist only here.
 >
 > There is no `npm run jd2` script — `package.json` and `CLAUDE.md` are kept
 > byte-identical to `main` so that merging `main` into `tooling` never
@@ -26,7 +27,7 @@ There are two surfaces, and they're treated very differently:
 JDownloader does nearly all its work on the CDN. Instaloader's value — the rich
 `.json.xz` metadata — comes from asking `instagram.com` a question *per post*.
 
-Concretely, from this archive: `ivyofficial` has 188 post-metadata files, so
+Concretely, from this archive: `rivvsofficial` has 188 post-metadata files, so
 backfilling it cost 188 API requests for one 605-file profile. That's the ban
 vector. Downloading the 238 photos was never the problem.
 
@@ -164,10 +165,10 @@ Everything downloads into `<archives>/`, one directory per source:
 
 ```
 archives/
-  4utumn07/                                 posts
-  4utumn07 - reels/                         reels
-  story - 4utumn07/                         stories
-  story highlights - 4utumn07 - Sunstory/   a highlight
+  0ct0ber19/                                 posts
+  0ct0ber19 - reels/                         reels
+  story - 0ct0ber19/                         stories
+  story highlights - 0ct0ber19 - Heestory/   a highlight
 ```
 
 Non-archive directories (tool output, exports from elsewhere) live *outside*