Cherry-picked upstream PRs (not yet merged)

This vendored copy is based on the tag in .vendored-from (cua-driver-rs-v0.6.8), plus a small set of upstream trycua/cua pull requests that were still open when we needed their fixes (all four are still open as of the 0.6.8 sync — confirmed by the sync applying with no collision on their lines). They are applied as ordinary commits on top of the base snapshot.

Upstream PR	Fix	Touches
trycua/cua#2035	start_session revives an idle-reaped session instead of erroring	cua-driver-core (session)
trycua/cua#2036	retry daemon socket writes on EAGAIN/EWOULDBLOCK instead of failing fatally	cua-driver-core (socket_io)
trycua/cua#2025	stop reporting a bare "Clicked" for X11 synthetic (XSendEvent) clicks that toolkits ignore	platform-linux
trycua/cua#2021	list_windows includes empty-/null-title top-level windows	platform-windows

When you sync to a newer upstream ref

scripts/sync-from-upstream.sh diffs .vendored-from→<new-ref>. If <new-ref> is at or past the commit where one of these PRs merged, that PR's changes are already in the upstream delta, so:

1. The hunks will collide with the cherry-picked commit (expect .rej on the files above), and
2. Once reconciled, remove the row from this table — it's no longer a local patch, it's part of the base.

If <new-ref> is still before a PR merges, that row stays; the cherry-pick keeps carrying the fix.