[deps] nvim-treesitter-textobjects pinned to frozen `master` branch — migrate to `main`

[stanfish06]

What

nvim-treesitter-textobjects is pinned to commit 851e865 which lives on the master branch. That branch is now frozen — only kept for backward compatibility. All new development happens on main.

Where

nvim-pack-lock.json:

"nvim-treesitter-textobjects": {
  "rev": "851e865342e5a4cb1ae23d31caf6e991e1c99f1e",
  "src": "https://github.com/nvim-treesitter/nvim-treesitter-textobjects.git"
}

The plugin source in lua/config/plugins.lua:11 has no branch pin, so vim.pack / the old clone path will pull from the default branch (which may now be main on GitHub, but the lockfile still points to a frozen master commit).

Why it matters

The main branch is a major rewrite. It supports:

• A new attach/detach API replacing nvim-treesitter.configs setup integration
• Standalone setup via require("nvim-treesitter-textobjects").setup({})
• Bug fixes and support for new tree-sitter query syntax

Staying on master means receiving zero future fixes. The move functions used in lua/config/plugin_config.lua:174-197 may quietly break as treesitter query files evolve.

Recommended action

1. In lua/config/plugins.lua, optionally pin to main explicitly once vim.pack supports branch selection.
2. Run :SyncPkgs / update the lockfile SHA to point to the latest main HEAD after verifying the move keymaps still work.
3. Review tso.setup({ move = { set_jumps = true } }) — on main the setup interface may require enable = true alongside set_jumps; see also issue [audit] nvim-treesitter-textobjects: tso.setup({ move }) set_jumps may be silently ignored #72.

Reference: nvim-treesitter-textobjects master README freeze notice