Bare git prune deletes unreachable objects at once: no 2-week grace

On git 2.43.0, a blob that was staged and then lost to git reset --hard disappeared immediately after a bare git prune, even though it was seconds old (git cat-file -t <sha> then fails). The two-week grace period that protects recent objects only applies when git gc calls prune with gc.pruneExpire. Prune's own default is to expire everything unreachable. A plain git gc, by contrast, moves recent unreachable objects into a cruft pack (pack-*.mtimes), where git fsck --lost-found still finds them. So when recovering lost work: run git fsck --lost-found first, never run bare git prune, and treat git gc --prune=now as equally destructive.