git stash pop without ref grabs another branch's stash

Trap: after making changes, running git stash then bare git stash pop is natural — but it pops the LATEST entry in the repository-wide stash list, which may belong to ANOTHER branch. In getsentry/craft this popped stash@{0} 'lore-churn-pre-rebase' from fix/dependabot-security-alerts onto a PR worktree, flooding it with 72 staged + 5 deleted unrelated files and 7 merge conflicts — looks like lore-daemon churn, but is a mis-targeted stash. Fix: never bare-pop; inspect git stash list first and use git stash pop stash@{N}. Recovery: git reset --hard <known-good-commit> clears the staged churn/conflicts; LEAVE the foreign stash in place (dropping it loses another branch's work) and don't commit its untracked leftovers.