[deps] fff.nvim 0.9.1 available — update from pinned 0.9.0

[stanfish06]

What

fff.nvim has a new release: v0.9.1 (released June 4, 2026). The config pins to 0.9.0 with a vim.version.range("0.9.0") constraint.

Where

lua/config/plugins.lua:7–11:

{
    name = "fff.nvim",
    src = "https://github.com/dmtrKovalenko/fff.nvim",
    lazy = true,
    version = vim.version.range("0.9.0"),
},

nvim-pack-lock.json:

"fff.nvim": {
  "rev": "a0a93f20934048e2451e2feaad28dfda1af55b5a",
  "src": "https://github.com/dmtrKovalenko/fff.nvim",
  "version": "0.9.0 - 0.9.0"
}

Why it matters

The plugin is intentionally pinned (-- this package breaks frequently, specify version) rather than tracking HEAD, so new releases must be evaluated and bumped manually. The lock's tight range "0.9.0" means SyncPkgs will not pick up 0.9.1 automatically.

Recommended action

1. Review the 0.9.1 changelog for breaking changes.
2. If safe, update the version range in plugins.lua:

   version = vim.version.range("0.9.1"),

   and update the rev in nvim-pack-lock.json to the 0.9.1 tag commit.
3. Run :SyncPkgs and verify find_files() / live_grep() still work (the binary may need re-downloading — see also [audit] PackChanged autocmd in fff.nvim setup is a top-level event — should be User PackChanged — binary never downloaded on install #117 for the PackChanged autocmd fix that ensures the binary is rebuilt automatically).