Wayland compositor support + GDM session install (rebase/re-land from stale PR #15)

[jaylfc]

Tracking issue for landing the Wayland compositor feature, currently stranded in PR #15 (branch convoy/tuiui-wayland-compositor-gdm-session-cap/0b238ad9/head).

Why it's not just merged

PR #15 is large (~3963 lines, almost all a new feature-gated src/wayland/* module) and branched off a Jun-12 main. Against current main it conflicts on .github/workflows/release.yml — the file that now drives the auto-release-on-version-bump pipeline — so a naive merge risks reverting the release automation. It's also unreviewed compositor code that needs the wayland toolchain to build/verify. Folding it into an unrelated session would be reckless.

What the feature adds (from PR #15)

• A wayland-compositor Cargo feature + new src/wayland/ module (backend, compositor, input, protocols).
• A tuiui-compositor binary entry point (src/compositor_main.rs) and a --compositor flag on the main binary.
• BeginFocusCycle action for Alt+Tab window switching.
• install.sh gains --compositor/--tui modes, Wayland session-file install, DRM uaccess rule install, and GDM auto-detection.
• Assets: drm-uaccess.rules, tuiui-compositor.service, tuiui.desktop.
• tests/wayland_compositor_tests.rs.

Plan to land it

1. Rebase the #15 branch onto current main (or cherry-pick the wayland module fresh), preserving the new release.yml auto-release workflow.
2. Build with --features wayland-compositor (default builds stay unaffected — it's feature-gated).
3. Review the compositor code properly; run the wayland tests.
4. Decide on a feature-flag/release story (does it ship in the prebuilt binaries or stay opt-in source-build?).

Related

• PR Add Wayland compositor support and GDM session installation #15 — the original implementation (keep open as the source branch, or close in favour of a fresh PR once rebased).
• PR install.sh: scan all /dev/dri/* + PATH-resolved desktop Exec #17 — install.sh DRM-scan follow-ups stacked on the same convoy line; its tip is already an ancestor of main, so it's moot on its own (see issue triage).