xavierk/voidkontrol
1
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

Establish the native niri and Noctalia integration contracts #3

New Issue
Closed
opened 2026-09-21 04:57:53 +00:00 by xavierk · 1 comment
xavierk commented 2026-09-21 04:57:53 +00:00
Owner
Copy Link
Copy Source

Question

What maintained interfaces support first-class VoidKontrol integration with the current niri and Noctalia releases on Void Linux? Verify Wayland application launch/identity and lifecycle, niri startup/bindings/IPC, Noctalia plugin versus tray/IPC surfaces, theme and notification contracts, versioning, and operation without systemd. Inspect installed versions and relevant configuration read-only. Propose concrete minimal-v1 integration options and acceptance criteria; distinguish documented facts, observed state, and decisions still requiring the user. No host configuration changes.

Parent map: Find the way to VoidKontrol v1: complete verified Swarm75 control on Void Linux

## Question What maintained interfaces support first-class VoidKontrol integration with the current niri and Noctalia releases on Void Linux? Verify Wayland application launch/identity and lifecycle, niri startup/bindings/IPC, Noctalia plugin versus tray/IPC surfaces, theme and notification contracts, versioning, and operation without systemd. Inspect installed versions and relevant configuration read-only. Propose concrete minimal-v1 integration options and acceptance criteria; distinguish documented facts, observed state, and decisions still requiring the user. No host configuration changes. Parent map: [Find the way to VoidKontrol v1: complete verified Swarm75 control on Void Linux](https://git.bongbetic.com/xavierk/voidkontrol/issues/1)
xavierk added the wayfinder:researchwayfinder:child-of-1 labels 2026-09-21 04:57:53 +00:00
xavierk self-assigned this 2026-09-21 04:58:47 +00:00
xavierk commented 2026-09-21 05:10:23 +00:00
Author
Owner
Copy Link
Copy Source

Resolution

The supported current interfaces are established for niri 26.04 and Noctalia 5.1.0. Noctalia v5 is the native shell with Luau plugins; older Quickshell/QML instructions are not the correct baseline. A native bar widget, quick panel, control-center shortcut, and shared background status entry are available without systemd. Recommend plugin API 24 for shell-free argv execution, and a packaged path source with explicit enable/place steps.

A standard Wayland app identity/desktop entry and user-initiated niri launch/focus path can support the Carbon editor. Noctalia plugin controls must use the same authorized daemon transaction path as the GUI/CLI. No automatic setting writes may follow startup, polling, reconnect, resume, or theme changes. The app-facing theme preference and shell theme can differ; Carbon and the native shell controls should each preserve their own semantic theme system.

Native niri and Noctalia integration report records release-pinned primary sources, read-only local notification/portal evidence, proposed CLI contracts, error/lifecycle behavior and acceptance criteria, captured on research/desktop-integration.

This resolves the interface research. Plugin scope, app identity, runtime, packaging and schema remain architecture decisions; no plugin, GUI or hardware integration has yet been built or tested. No running desktop configuration was changed.

## Resolution The supported current interfaces are established for niri 26.04 and Noctalia 5.1.0. Noctalia v5 is the native shell with Luau plugins; older Quickshell/QML instructions are not the correct baseline. A native bar widget, quick panel, control-center shortcut, and shared background status entry are available without systemd. Recommend plugin API 24 for shell-free argv execution, and a packaged path source with explicit enable/place steps. A standard Wayland app identity/desktop entry and user-initiated niri launch/focus path can support the Carbon editor. Noctalia plugin controls must use the same authorized daemon transaction path as the GUI/CLI. No automatic setting writes may follow startup, polling, reconnect, resume, or theme changes. The app-facing theme preference and shell theme can differ; Carbon and the native shell controls should each preserve their own semantic theme system. [Native niri and Noctalia integration report](https://git.bongbetic.com/xavierk/voidkontrol/src/commit/73d7327ace37ce78532aa8576362934548787076/docs/research/desktop-integration.md) records release-pinned primary sources, read-only local notification/portal evidence, proposed CLI contracts, error/lifecycle behavior and acceptance criteria, captured on `research/desktop-integration`. This resolves the interface research. Plugin scope, app identity, runtime, packaging and schema remain architecture decisions; no plugin, GUI or hardware integration has yet been built or tested. No running desktop configuration was changed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
wayfinder:child-of-1
Child of the VoidKontrol v1 decision map
 wayfinder:grilling
Decision requiring a live exchange with the user
 wayfinder:map
Canonical wayfinding decision map
 wayfinder:prototype
Decision supported by a user-reviewed prototype
 wayfinder:research
Primary-source investigation for a decision
 wayfinder:task
Prerequisite work that unblocks a decision
No labels wayfinder:child-of-1 wayfinder:research
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
xavierk (Xavier Karma)
No Assignees xavierk
1 Participants
Notifications
Due Date
No due date set.
Blocks
#6 Choose the VoidKontrol service, UI, and desktop integration architecture
xavierk/voidkontrol
Reference: xavierk/voidkontrol#3