Git safety and recovery
Git recovery starts with preserving evidence and choosing a reversible operation, not resetting a working tree blindly.
On this page2

Steps
- Run git status, git diff, and a short git log to identify the exact state.
- Save important untracked or uncommitted files before attempting recovery.
- Prefer a new commit or git revert for shared history, and target individual paths when possible.
- Run the project checks and inspect status again after recovery.
Expected result
The repository returns to a known state without erasing unrelated user work.
Note: A Foxora checkpoint restores eligible workspace files but does not move Git HEAD. Avoid destructive reset or clean commands unless explicitly required and backed up.