topology: exclusive was echoed back by the API and dropped on Hyprland and sway
#304
Merged
enricobuehler
merged 1 commits from 2026-08-18 15:54:15 +00:00
worktree-vdisplay-topology-wlroots-hyprland into main
1
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
 enricobuehler
|
4b5a37dae2 |
feat(vdisplay): topology: exclusive was echoed back by the API and dropped on Hyprland and sway
ci / bun-nix (pull_request) Successful in 36s
ci / web (pull_request) Successful in 1m18s
ci / docs-site (pull_request) Successful in 1m43s
ci / rust-arm64 (pull_request) Successful in 2m8s
android / android (pull_request) Successful in 7m40s
ci / rust (pull_request) Successful in 8m5s
Both wlr-family backends accepted the topology axis, the management API reported it as the session's effective topology, and the backend logged a warning and did nothing (sweep 13.18 shipped the warning, never the behaviour). Because `resolve_topology` sends `auto` — the default — to `Exclusive` on any host without a `PUNKTFUNK_COMPOSITOR` pin, and both compositors are auto-detected, the default policy on every such box was an Exclusive that behaved as Extend. Closes #284. `exclusive` now disables the operator's heads for the session and restores them when the display GROUP's last member is torn down, via the same `take_topology_restore` hand-off KWin uses — so the registry runs the restore before the last output is reclaimed and the compositor never sees zero enabled outputs, and a sibling session never has the desk re-enabled under it. The disable filter is group-aware (design §6.1): enabled, not ours, and not managed. On Hyprland `managed` is `PF-<pid>-<n>`, which covers a second host's outputs too; on sway it is the `HEADLESS-` prefix, which also spares a headless sway's own bootstrap output — the harmless failure, versus blacking out a live sibling. `primary` stays treated as extend, which is the honest answer rather than a gap: Wayland has no primary-output concept and these compositors have only a focused output, which the streamed head already holds since #283. It now says so distinctly instead of sharing a warning with `exclusive`. 🛑 The Hyprland restore is `hyprctl reload`, and that is measured, not chosen. Re-applying the head's own mode/position/scale — what design §5.2 and the issue both assume — does NOT undo a disable: it answers `ok` and leaves `disabled: true`. Probed 2026-08-18 against 0.56.2 (hyprlang) and 0.55.4 (Lua); every targeted form was accepted and changed nothing, including `,enable` (answers `invalid resolution`), `preferred,auto,1`, `monitorv2 disabled=false`, `keyword unset monitor`, the Lua `disabled = false`, `dispatch dpms on` and `forcerendererreload`. A runtime monitor rule is additive and the `disable` keeps winning; only re-reading the config clears it. The headless output survives the reload, so the issue's worry about losing it does not hold. Side effects are documented at the call site and in the docs: other runtime `keyword` overrides are dropped, and a hyprlang config re-runs its `exec =` lines. It runs only when a session actually disabled something. Disable is spelled per config era and confirmed by read-back, mirroring `set_monitor_rule`: `keyword monitor <n>,disable` under hyprlang, `hl.monitor{ output = "<n>", disabled = true }` under Lua. Both eras reject the other's form at exit 0, so the read-back — not the exit status, not the `ok` — is what decides. Also fixes a marker gap that made one of those rejections read as success: `hyprctl keyword` under the Lua config manager answers "keyword can't work with non-legacy parsers. Use eval.", and `hyprctl_dispatch` matched "couldn't" but not "can't". `set_monitor_rule` was covered by its own mode verification; nothing else was. ⚠ The sway half is NOT exercised on a live sway — no box in the fleet runs one, the same gap #283's `focus output` shipped with. The argv is sway's documented surface, both shapes are pinned by tests (this file uses `output <name> <verb>` AND `focus output <name>`, so getting one backwards is the live risk), and the read-back turns a wrong guess into a warning naming the outputs rather than a screen that silently stays dark. Six new unit tests cover the group-aware filter on both backends, the headless no-op case, both disable spellings and the marker set. 246 pass on Linux. |