The clipboard bridge backend has been ext-data-control since the
wlr-data-control migration; three comments/log strings still named the
old protocol. Cosmetic-only, no behavior change.
nested-labwc.sh runs a command inside a nested labwc (wlroots-family host)
so the clipboard bridge exercises the data-control backend; stress-clipboard.sh
loops the clipboard smoke tests, snapshotting logs into /tmp/stress-fail/ on
any failure. Recovered verbatim after the history rewrite dropped scripts/.
Usage:
scripts/nested-labwc.sh scripts/stress-clipboard.sh [iterations]