v0.29.3

A commit no longer leaves a deleted-then-recreated path pending in the shared index.

Context

An archiving deletion tool stages the removal of a tracked file it takes away, so the next commit cannot resurrect it. When a new file was then written at that same path and committed, safegit recorded the new bytes and put the staged removal back into the shared index, because its reconciler reads "the pre-operation tip holds this path and the index has no slot for it" as another session's staged deletion worth preserving. It was the very path the commit had just answered, and the repository was left reporting it as deleted and untracked right after safegit reported it committed.

Preserving another session's staged work was stated over the whole index; it now holds over the paths the operation did not speak for. Only the DERIVED removal is suppressed for a path a commit or amend staged: where the index really holds a slot for such a path, two real blobs exist and choosing between them is still not the reconciler's to do.

Fixes

• The tool describes itself with one sentence everywhere, including --help. The --help header, README, docs site and package metadata now carry the same line.
• A file deleted-then-recreated at the same path no longer stays pending after being committed. When a deletion tool has staged the removal of a tracked file (git rm --cached) and a new file is written at that same path, safegit commit left the shared index still holding the deletion -- git status reported the path as both deleted and untracked right after safegit reported it committed, which was enough to block a release. Another session's staged work at a path the commit never named still outlives the commit unchanged.
• A file renamed with git mv and then edited no longer stays pending after being committed. safegit commit recorded the edited bytes at the new path and then put the rename's pre-edit blob back into the shared index, so git status reported MM on the file right after safegit reported it committed, and committing it again was refused as nothing to commit. The shared index now holds what the commit recorded on every path the commit staged; another session's staged work at a path the commit never named still outlives it unchanged.