v0.1.11 everywhere: version badge, pin examples, landing page, release request

[navbytes]

v0.1.10 shipped at 01:48 UTC today, before any of this session's work
landed, so everything below is unreleased. Touching
.github/release-request dispatches Release, which builds four targets,
creates the v0.1.11 tag from Cargo.toml itself, and publishes with
SHA256SUMS.txt.

Two silent data-loss bugs.

• Alt+w on the last pane — whose own prompt calls it "quit roost" —
  removed the pane and then quit, so shutdown saved a tab whose
  layout named a pane its map no longer had. The repair minted a blank
  shell spec on next launch, and the session id, cwd, title and note
  of the pane you quit on were gone. Alt+q on the same pane kept all
  of them. (workspace: quitting with Alt+w threw away the pane it quit on #147)
• A recycled pane id inherited the dead pane's session-detection clock.
  last_shell_seen and pending_detect were the only two
  PaneId-keyed maps close_pane_id did not prune, so a pane taking
  that id could scan hours back and resume a stranger's conversation,
  permanently. (panes: a recycled pane id inherited the dead pane's session-detection clock #141)

Idle cost down ~13x. 2.75% CPU and 888 B/s of terminal traffic, to
0.2–0.4% and ~62 B/s, flat in the pane count at every step because it
was all fixed per-frame chrome: a String allocated per cell per frame
(#140); the quick-launch picker's $PATH probe running ~1,500 stat(2)
a second with no dialog on screen, plus the whole help table, every
frame (#144); an unconditional 30 fps repaint (#146); and 12 fps even
with nothing animating (#149).

Desktop notifications changed channel, and this one is user-visible.
They used to fork osascript, which macOS attributes to Script
Editor — there is no flag for that; a CLI cannot post under its own
name. roost now asks the terminal instead, with a bell and an OSC 9,
which is the mechanism SPEC-parity P2 already named. Ghostty, iTerm2,
WezTerm and kitty raise a real notification from it, attributed to
themselves, and it survives ssh. A host that ignores OSC 9 (Apple
Terminal, Alacritty) now gets only the bell. (#152)

And a pane's notification no longer arrives twice: there were two
emitters, invisible as a duplicate only while one of them was the
osascript fork. The named one won, so one banner, saying which pane,
and silence for the pane you are already looking at. (#153)

Three new fuzzers over input surfaces nothing reached before — the
mouse router, the key router, and paste — each walking a layout being
reshaped underneath it, drawing a real frame and re-checking the layout
fuzzer's own invariants after every step. The mouse one found #147 on
seed 15. (#147, #148)

rustfmt and clippy, enforced in CI (#150), tuned to the style the
tree already had rather than imposed: the config was picked by measuring
churn (556 hunks vs 1,632 for the naive setting). The lint set is in
Cargo.toml's [lints] tables so it binds locally too, and three
candidate lints were measured and rejected. It found ten unsafe blocks
missing the SAFETY: comment every other one in the tree has.

Plus: the reformat kept out of git blame (#151), and three test gates
that blamed roost for the machine being out of ptys (#154).

Verified before cutting: 1,048 tests, clippy clean at -D warnings,
fmt --check clean. Both agent adapters checked end to end against live
binaries (pi --session …, claude --resume …), the session-resolution
table across all five adapters, the 45s status decays timed against the
clock, and two 15-minute soaks (~78k random keystrokes each, ~1,800
panes) with no orphan, no leak and no unreadable workspace.

Note for after the merge: HOMEBREW_TAP_TOKEN is still unset, so
release.yml will skip the tap sync again (it did for v0.1.10). The
formula needs the usual hand-sync.