git-history-cutoverlisted

# Git History Cutover — LFS Storage Reclamation **Goal**: Take `.git` from bloated-with-old-LFS-history to reclaimed, with every affected worktree/clone back on the new history and nothing silently lost. Scripts live in `scripts/git-history-cutover/` (`01-analyze.sh` through `05-local-resync.sh`) — full runbook and rationale in that directory's `README.md`. This skill is the guided, decision-aware driver on top of them: it tells you which script to run when, tracks the per-worktree replay work, and holds the line on the safety gates none of the scripts skip on their own. --- ## Read this first: rewriting history does NOT immediately free the quota GitHub's own docs are explicit: LFS objects removed from history stay in remote storage and keep counting against the quota until they're truly unreferenced by any ref — then GitHub garbage-collects them automatically, but only after roughly a 30-day grace period. There is no supported self-service "delete now" button; the only way to force it sooner is a support ticket, or deleting and recreating the repo (not viable here — this is a live, actively-developed repo with two remotes, issues, and PR history). **Implication**: this operation stops the bleeding and reclaims space over the following weeks. It does not unblock CI today. If CI needs to be unblocked immediately, that's a separate, smaller fix (e.g. skip the LFS checkout step for jobs that don't actually need `docs/demos/*.gif` — check with the user before doing this, s