v1.22: drop -O from right-click menu so the pane unfreezes on click-outside

The example tmux snippet bound `MouseDown3Pane` to `display-menu -O …`. The
`-O` flag tells tmux to hold the menu open until an item is picked or
Escape is pressed — releasing the mouse outside the menu does nothing.
Inside a TUI that grabs keystrokes (Claude Code's chat input is the
reported case), the running pane appears completely frozen after a
right-click: typing produces no output until the user remembers Escape.

Dropping `-O` switches to standard native-GUI behaviour: clicking
outside the menu, or releasing the mouse outside the menu, auto-
dismisses it and the pane is immediately responsive again. Escape
still closes the menu; item-selection still closes it; the visible
menu rows are unchanged.

Scope is the example snippet only — bin/, rs/, and systemd/ are not
touched. The `examples/kitty.conf.snippet` peer file has no analogous
binding so no symmetric edit is needed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: NagyVikt

CHANGELOG.md

@@ -25,6 +25,11 @@ Release-tag policy: every `vX.Y` commit on `main` must be tagged and have a matc
 - `assets/hero-flow-light.svg` light-mode variant
 - README badges, animated SVG hero, animated tier-comparison chart, Mermaid sequence diagram, AI-assistant TL;DR block, extended FAQ, alternatives comparison
 
+## [1.22] - 2026-05-19
+
+### Fixed
+- `examples/tmux.conf.snippet`: dropped the `-O` flag from the right-click menu binding so the menu auto-dismisses on click-outside / mouse-release-outside. With `-O` the menu held the pane in modal-grab until Escape, which read as the pane being "frozen" after a right-click — most visible in TUIs that grab keystrokes (Claude Code chat input).
+
 ## [1.19] - 2026-05-19
 
 ### Fixed

examples/tmux.conf.snippet

@@ -47,7 +47,13 @@ bind -n MouseDown2Pane run-shell -b "buf=$(sh -c '#{@paste}'); if [ -n \"$buf\"
 # invokes `flashpaste-trigger '#{pane_id}'` with the TMUX_PASTE_TRIGGER
 # env var so ~/.local/state/flashpaste-trigger.log can distinguish the
 # right-click path from the C-v path during debugging.
-bind -n MouseDown3Pane display-menu -O -x M -y M \
+#
+# No `-O` flag: the menu auto-dismisses on click-outside / mouse-release
+# outside the menu, matching native GUI menus. Escape still closes it,
+# and item-selection still works. With `-O` the menu stuck open until
+# Escape, which read as the pane being "frozen" after a right-click —
+# visible in TUIs like Claude Code that grab keystrokes (v1.22).
+bind -n MouseDown3Pane display-menu -x M -y M \
   -T "#[align=centre,fg=#FFFFFF,bold] pane #{pane_index} " \
   "#[fg=#34C759]↳ Paste" p \
     "run-shell -b \"TMUX_PASTE_TRIGGER=right-click-menu flashpaste-trigger '#{pane_id}' 2>/dev/null || TMUX_PASTE_TRIGGER=right-click-menu /home/$USER/.local/bin/tmux-paste-dispatch.sh '#{pane_id}'\""