[tony]

Stacked on #149, which adds the kill_session confirmation this extends. Merge #149 first.

Fixes #150, fixes #152, fixes #153.

Summary

• Add elicitation confirmation to kill_window, kill_pane and kill_server.
• Name the window, the pane's running command, or the session count in each question.
• Share one confirmation helper across all four kill tools.
• Fail a call_read_tools_batch row whose tool asks for user input.
• Pin the response limiter's pass-through of a confirmation question with a test.
• Name all four kill tools in the prompting guide's sample prompt.

Changes by area

Teardown confirmation

• src/libtmux_mcp/_utils.py: _confirm_teardown holds the two-era elicitation flow, and _ask_before_teardown adds the decline error and the identity recheck. _tmux_identity reads #{pid}:#{start_time}:<id> from any tmux object.
• src/libtmux_mcp/tools/window_tools.py, src/libtmux_mcp/tools/pane_tools/lifecycle.py, src/libtmux_mcp/tools/server_tools.py: kill_window, kill_pane and kill_server become async and ask through the helper.
• src/libtmux_mcp/tools/session_tools.py: kill_session uses the same helper.

Batch

• src/libtmux_mcp/tools/batch_tools.py: _ensure_tool_result raises a row error for fastmcp's InputRequiredToolResult and tells the agent to call the tool directly.

Docs

• docs/tools/window/kill-window.md, docs/tools/pane/kill-pane.md, docs/tools/server/kill-server.md: a Confirmation note on each page.
• docs/topics/prompting.md: the sample prompt names all four kill tools. A note says the confirm-first sentence can be dropped in clients that ask through elicitation.
• CHANGES: the kill-confirmation entry covers all four tools.

Design decisions

• No tool schema changes. FastMCP injects ctx and hides it from the schema, and the tool-surface snapshot is unchanged.
• kill_server has no object id to compare, so its identity is the server's #{pid}:#{start_time}. A server restarted on the same socket during the question gets a new pid and is left alone.
• The batch refuses a question instead of relaying it, since a row has no channel back to the user. call_read_tools_batch admits only inspect tools, none of which ask today, so the guard is for the next one that does.
• The response limiter stays as it is. fastmcp's ResponseLimitingMiddleware returns an InputRequiredToolResult untouched, and our subclass rebuilds only results it trimmed.

Test plan

• kill_window, kill_pane and kill_server accept, decline, and client-cannot-ask cases on 2025-11-25 and 2026-07-28 (test_kill_tools_ask_before_killing)
• A target recreated while the user is asked is not killed, through the shared helper (test_kill_session_confirmation)
• A batched tool that asks for input fails its row with the direct-call hint (test_batch_refuses_a_tool_that_asks_for_input)
• The response limiter passes a question through as input-required (test_response_limiter_passes_a_question_through)
• Tool-surface snapshot unchanged (test_tool_surface_matches_snapshot)
• Full suite, ruff format --check, ruff check, and mypy .
• just build-docs with no warnings
• Confirmation prompts in a live elicitation client
• Full suite across the CI tmux-version matrix

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.08%. Comparing base (c57314c) to head (2ee0683).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #154      +/-   ##
==========================================
+ Coverage   86.97%   87.08%   +0.10%     
==========================================
  Files          47       47              
  Lines        3947     3964      +17     
  Branches      596      601       +5     
==========================================
+ Hits         3433     3452      +19     
+ Misses        354      353       -1     
+ Partials      160      159       -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.