Release v0.1.0a2 (2026-04-19)

why: The `2026-04-follow-ups` branch (FastMCP alignment: new tools,
prompts, and middleware, #15) has merged and the accumulated
unreleased entries — new tools, prompts, full middleware stack,
bounded outputs, plus the search_panes / fastmcp minimum-version
breaking changes — constitute a shippable alpha point release. The
previous published version was 0.1.0a1 on 2026-04-13; everything
between v0.1.0a1 and main now belongs under a finalized release
block.

what:
- pyproject.toml: version 0.1.0a1 -> 0.1.0a2
- src/libtmux_mcp/__about__.py: __version__ 0.1.0a1 -> 0.1.0a2
- uv.lock: regenerated via `uv sync` (libtmux-mcp entry updated)
- CHANGES: introduce a `## libtmux-mcp 0.1.0a2 (2026-04-19)`
  heading between the rolling `0.1.x (unreleased)` placeholder and
  the existing `_FastMCP alignment..._` tagline. The placeholder
  block stays at the top for the next iteration; the Breaking
  changes, What's new, Fixes, and Documentation entries that had
  accumulated under "unreleased" are now the content of the
  0.1.0a2 release block. No bullet text changed.

Author: tony

CHANGES

@@ -6,6 +6,8 @@
 _Notes on upcoming releases will be added here_
 <!-- END PLACEHOLDER - ADD NEW CHANGELOG ENTRIES BELOW THIS LINE -->
 
+## libtmux-mcp 0.1.0a2 (2026-04-19)
+
 _FastMCP alignment: new tools, prompts, and middleware (#15)_
 
 ### Breaking changes

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "libtmux-mcp"
-version = "0.1.0a1"
+version = "0.1.0a2"
 description = "MCP server for tmux, powered by libtmux"
 requires-python = ">=3.10,<4.0"
 authors = [

src/libtmux_mcp/__about__.py

@@ -4,7 +4,7 @@
 
 __title__ = "libtmux-mcp"
 __package_name__ = "libtmux_mcp"
-__version__ = "0.1.0a1"
+__version__ = "0.1.0a2"
 __description__ = "MCP server for tmux, powered by libtmux"
 __author__ = "Tony Narlock"
 __email__ = "tony@git-pull.com"