38 lines
1.6 KiB
Markdown
38 lines
1.6 KiB
Markdown
# Linux Notification Environment Preparation
|
|
|
|
Last verified: 2026-06-02
|
|
|
|
Read this when you need to provide Linux runner and desktop notification
|
|
environment choices so an agent can finish Linux notification implementation and
|
|
smoke verification. You do not need to run the test from this document.
|
|
|
|
## Provide
|
|
|
|
| Needed | What to prepare |
|
|
|---|---|
|
|
| Linux runner | Local machine, VM, remote desktop, headless-only runner, or deferral. |
|
|
| Distribution | Distribution and version, such as Ubuntu, Debian, or Fedora. |
|
|
| Desktop session | GNOME/KDE/XFCE/other and X11/Wayland/headless. |
|
|
| Notification path | D-Bus notifications, XDG Desktop Portal, libnotify, or debug injection only. |
|
|
| Dependencies | Whether the agent may install required system packages. |
|
|
| Operator path | Who handles UI prompts/clicks if the runner is remote. |
|
|
| Evidence path | Choose where sanitized logs/screenshots/run notes should be stored. |
|
|
|
|
## Do Not Put In Tracked Files
|
|
|
|
- Private host names, user names, private endpoints, auth tokens, channel names,
|
|
server URLs, machine-identifying session details, private package repository
|
|
credentials, device tokens, or signing keys.
|
|
|
|
## Agent Can Then
|
|
|
|
- add Linux platform registration and host scaffold if selected;
|
|
- implement the native notification/action bridge;
|
|
- configure the selected desktop notification path;
|
|
- run routing checks and, if allowed, visible notification smoke;
|
|
- record sanitized evidence in the task or private run note.
|
|
|
|
## Current Repo Note
|
|
|
|
Linux is not registered yet and has no plugin or test-host scaffold. Smoke work
|
|
first needs platform scaffold plus the environment choices above.
|