wordpress-tools PR #57 deleted 108 source files and added nothing — but scores as a completed migration
Surfaced while closing #246 and #280. Both of those steps are legitimately closeable — the files are gone — but how they went differs sharply between repos, and one case wants a look.
The commit
2966736 / PR #57, "complete RSR language purge", 2026-08-23:
|
|
| files changed |
411 |
| insertions |
2,208 |
| deletions |
21,656 |
.ts removed |
43 |
.res removed |
41 |
.js removed |
24 |
.affine in the repo today |
0 |
The only things added were 14 git hook .sample files and a directory named git_corrupted/.
Why this matters beyond one repo
Every other repo in the same campaign genuinely ported, and the history proves it — .ts deleted and .affine added in the same commit:
| repo |
files |
evidence |
thunderbird-template-reloaded |
7 |
9ae8103 — delete + add together |
double-track-browser |
6 |
5e24561 — same |
polyglot-i18n |
2 |
ee73cad — same |
universal-chat-extractor |
7 |
e29ad92 → 11 .idr present |
zotero-tools |
41 .res |
25b66b9 → 51 .affine |
wordpress-tools |
108 |
deleted; nothing added |
So the campaign's own metric — "0 banned-language files remain" — is satisfied identically by a real port and by a deletion. This is the estate's documented absence-scored-as-completion pattern, and it is the one case in this campaign where it appears to have fired.
What this issue is actually asking
- Was the deletion intended? If
wordpress-tools was being retired or its functionality moved elsewhere, this is fine and wants recording as such.
- If not, is the content recoverable? It is in git history at
2966736^, so nothing is lost — but nobody will look unless it is written down.
- What is
git_corrupted/? A directory by that name added in a purge commit is worth explaining.
Not a request to revert
The files are gone from main and both campaign steps are closed on that basis. This exists so the distinction survives — otherwise the only record is a green checkbox on a campaign that treated a deletion and a port as the same outcome.
Related: #246, #280, #239.
wordpress-toolsPR #57 deleted 108 source files and added nothing — but scores as a completed migrationSurfaced while closing #246 and #280. Both of those steps are legitimately closeable — the files are gone — but how they went differs sharply between repos, and one case wants a look.
The commit
2966736/ PR #57, "complete RSR language purge", 2026-08-23:.tsremoved.resremoved.jsremoved.affinein the repo todayThe only things added were 14 git hook
.samplefiles and a directory namedgit_corrupted/.Why this matters beyond one repo
Every other repo in the same campaign genuinely ported, and the history proves it —
.tsdeleted and.affineadded in the same commit:thunderbird-template-reloaded9ae8103— delete + add togetherdouble-track-browser5e24561— samepolyglot-i18nee73cad— sameuniversal-chat-extractore29ad92→ 11.idrpresentzotero-tools.res25b66b9→ 51.affinewordpress-toolsSo the campaign's own metric — "0 banned-language files remain" — is satisfied identically by a real port and by a deletion. This is the estate's documented absence-scored-as-completion pattern, and it is the one case in this campaign where it appears to have fired.
What this issue is actually asking
wordpress-toolswas being retired or its functionality moved elsewhere, this is fine and wants recording as such.2966736^, so nothing is lost — but nobody will look unless it is written down.git_corrupted/? A directory by that name added in a purge commit is worth explaining.Not a request to revert
The files are gone from
mainand both campaign steps are closed on that basis. This exists so the distinction survives — otherwise the only record is a green checkbox on a campaign that treated a deletion and a port as the same outcome.Related: #246, #280, #239.