v1.7.1

pollen v1.7.1

v1.7.0's Settings overlay was bound only to Ctrl+,,
mirroring VS Code and IntelliJ. That works fine in
graphical editors that intercept keyboard events at the OS
level, but inside a terminal it doesn't survive. The comma
key has no traditional ASCII control code — Ctrl+letter
maps to 0x01–0x1A, and Ctrl+[, ], ^, _ map to 0x1B–0x1F
because of historical Unix conventions, but Ctrl+, just
sends a plain comma (0x2C). bubbletea v1 doesn't enable
the kitty / CSI-u keyboard protocol that some modern
terminals (kitty, WezTerm, recent Alacritty) use to encode
the distinct sequence, so on xterm, GNOME Terminal,
macOS Terminal.app, Windows Terminal, and WSL — the
overwhelming majority of pollen's homes — Ctrl+, did
absolutely nothing.

The fix adds Ctrl+P (ASCII 0x10, recognised by every
terminal) as the primary binding. Ctrl+, is kept as an
alias so users on CSI-u-capable terminals still get the
VS Code muscle memory. The Help overlay's Global section
now reads "Ctrl+P / Ctrl+, : Open settings overlay",
reflecting both options.

The Settings overlay implementation itself is unchanged —
only the keybinding that opens it is fixed.

Fixed:

• Settings overlay primary keybinding switched to Ctrl+P
  for universal terminal compatibility; Ctrl+, retained
  as an alias for kitty / CSI-u-capable terminals.
  Pre-v1.7.1 the binding was effectively dead on every
  standard terminal.

Notes:

• v1.x SemVer-frozen surface unchanged: additive only.
  Ctrl+P is new, Ctrl+, remains documented.
• The same kind of binding issue does not affect any other
  pollen shortcut: every existing Ctrl+letter mapping uses
  a key with a valid ASCII control code, and Ctrl+/ has the
  Ctrl+_ alias precisely because both transmit the same
  0x1F byte.

See CHANGELOG.md for the full list.