chore(deps): bump libtmux floor to 0.55.1

libtmux 0.55.1 ships the pytest-plugin socket-reaper fix
(tmux-python/libtmux#661) so the `server` / `TestServer` fixtures now
kill the tmux daemon AND unlink the socket file under
`/tmp/tmux-<uid>/` on teardown. This bumps the runtime floor and
refreshes uv.lock so CI and fresh installs pick up the fix.

Verified locally: after the bump, `uv run pytest` leaves a single
residual socket per run (down from thousands accumulating across
runs pre-fix). The remaining straggler originates outside the
standard fixture teardown path and is a separate, minor issue —
not a regression.

Supersedes the local conftest reaper proposed in
#23; that PR can now be closed without merge.

Author: tony

CHANGES

@@ -6,6 +6,16 @@
 _Notes on upcoming releases will be added here_
 <!-- END PLACEHOLDER - ADD NEW CHANGELOG ENTRIES BELOW THIS LINE -->
 
+### Dependencies
+
+- Minimum `libtmux>=0.55.1` (was `>=0.55.0`). 0.55.1 ships the
+  pytest-plugin socket-reaper fix
+  ([tmux-python/libtmux#661](https://github.com/tmux-python/libtmux/pull/661))
+  so `libtmux_test*` daemons and socket files no longer leak under
+  `/tmp/tmux-<uid>/` during test runs. Downstream effect: no local
+  conftest reaper is needed in libtmux-mcp — the upstream fixtures
+  self-clean.
+
 ## libtmux-mcp 0.1.0a2 (2026-04-19)
 
 _FastMCP alignment: new tools, prompts, and middleware (#15)_

pyproject.toml

@@ -40,7 +40,7 @@ include = [
 ]
 
 dependencies = [
-  "libtmux>=0.55.0,<1.0",
+  "libtmux>=0.55.1,<1.0",
   "fastmcp>=3.2.4,<4.0.0",
 ]