[deps] nvim-lspconfig and nvim-treesitter-textobjects — no update tracking #169

What

Two plugins in nvim-pack-lock.json are pinned to old commits with no dedicated tracking issue:

nvim-lspconfig

Where: lua/config/plugins.lua line 12, lua/config/plugin_config.lua lines 91–99

Why it matters: Issue #145 notes that lspconfig may be vestigial — pyright, clangd, ts_ls, gopls, and rust_analyzer are enabled via vim.lsp.enable() without an explicit vim.lsp.config() call, meaning Neovim silently falls back to lspconfig's bundled configs/ specs. Those bundled specs have changed across versions (root markers, filetypes, default settings). The pinned commit predates multiple lspconfig releases that updated these specs.

Recommended action: Run :checkhealth lspconfig, compare pinned commit changelog, and decide whether to update or drop the dependency in favour of explicit vim.lsp.config("name", {…}) calls for each server (which would make #145's "vestigial" concern moot).

nvim-treesitter-textobjects

Where: lua/config/plugins.lua line 18, lua/config/plugin_config.lua lines 241–273

Why it matters: After nvim-treesitter was archived (#151), textobjects was rewritten to work directly with Neovim's native treesitter API (no hard nvim-treesitter dependency). The pinned commit (851e865) predates this migration. Staying on it means:

1. Textobjects still requires nvim-treesitter to be installed and functional
2. Once [deps] nvim-treesitter archived (April 2026) — migrate to native Neovim 0.12 treesitter or pin #151's migration drops or unpins nvim-treesitter, textobjects will break

Recommended action: Update nvim-treesitter-textobjects pin to a post-migration commit that works with native treesitter, then test ]f/[f/]c/[c keymaps still function without nvim-treesitter.