After switching to different worktree, newly opened buffer gets deleted.

[adiSuper94]

I use bnext/nprev to move between buffers.

1. I open nvim and open a file.
2. I switch worktrees using this plugin, the hook in the readme opens and the same file that I had open in the previous worktree.
3. I use bprev, and end up in the file from the previous worktree(this is fine).
4. But bnext doesn't take me to the file in the newly switched worktree, that buffer gets deleted as soon as i do the bprev

[polarmutex]

This was generated by AI during triage.

Agent Brief

Category: bug
Summary: Buffer opened by update_current_buffer_on_switch is deleted when navigating with bprev/bnext

Current behavior:

1. User opens a file in worktree A
2. User switches to worktree B — the builtin update_current_buffer_on_switch hook opens the equivalent file in worktree B
3. User presses bprev — jumps to the file from worktree A (expected)
4. User presses bnext — the worktree B buffer is gone; it was deleted when bprev was pressed

The buffer opened by the switch hook is not surviving navigation away from it.

Desired behavior:
After switching worktrees, the buffer opened by update_current_buffer_on_switch should persist in the buffer list. Pressing bprev then bnext should return to it, the same as any normally-opened buffer.

Key interfaces:

• The update_current_buffer_on_switch builtin hook — look at how it opens the new buffer (which vim.api or vim.cmd call it uses) and whether it opens as a listed, normal buffer or as an unlisted/scratch/temporary buffer
• The switch hook registration in Hooks — verify the hook fires after the working directory has been changed, not before

Acceptance criteria:

• After switching worktrees and navigating away with bprev, pressing bnext returns to the buffer opened by the switch hook
• The buffer opened by the switch hook appears in ls (i.e. it is a listed buffer)
• No regression: switching without navigating away still lands on the correct file in the new worktree

Out of scope:

• Changes to how bprev/bnext work in Neovim
• Custom hook implementations (only the builtin update_current_buffer_on_switch is in scope)