git-history-recoverylisted
Install: claude install-skill TR4W/TR4W-D12
# The 2026-08-19 history rewrite, and how to recover from it
Moved out of `CLAUDE.md` on 2026-08-31 because it is a **one-time recipe**: needed
when a stale clone turns up, and never otherwise, so it does not earn a place in
every session's context. The *prohibitions* it implies stayed behind in
`CLAUDE.md` — "**NEVER force-push `main`**" and "**DO NOT RE-SIGN OR RE-STRIP
HISTORY**" — because a safety rule must not be one invocation away from being
missed.
## What actually happened, so nobody chases the wrong commits
**The rewrite was 2026-08-19 at 12:04, not 2026-08-29.** The 29th is when a stale
clone first *fetched* it — that clone's tip was `152118b2` from **2026-08-14**, so
it met a ten-day-old force-push and reported it as same-day. Every push on
2026-08-29 was an ordinary fast-forward.
It was **deliberate**: `git filter-branch` over `fpc` to strip `Claude-Session:`
trailers, which are links to private transcripts and do not belong in a public
repo. Whoever ran it took a backup first — `backup-pre-trailer-strip-2026-08-19`,
still present, tip `e815d7a3`. `.git/refs/original/` was also left behind, which
is `filter-branch`'s fingerprint.
Signature loss was collateral: `filter-branch` re-creates every commit and
`gpgsig` does not survive. Hence **741 unsigned commits dated 2026-08-19 or
earlier, and 335 signed after it**.
**Three things follow, and the third is the one that will tempt someone:**
1. The cleanup did not hold — **12 more commits carrying the trailer l