fb78c814cc
All checks were successful
Check / eval (push) Successful in 3m4s
The bar colored the battery at 25/10% but nothing notified. New shellcheck-gated watcher (pkgs/nomarchy-battery-notify, overlay) polls the same sysfs the bar reads — type=Battery, scope!=Device — and fires one toast per downward crossing (normal at 25%, critical at 10%; swaync keeps critical up until dismissed), re-armed by charging. Self-gates on battery presence (the powerprofile pattern), so desktops get a silent no-op. HM user unit behind nomarchy.batteryNotify.enable (default on) with libnotify on the unit PATH; notify-send resolves from PATH so the VM check can shim it. poweralertd rejected: its UPower thresholds (20/5) wouldn't match the bar, and it toasts every plug/unplug. Verified: V0 (flake check, bash -n); V1 (template-home builds, unit in the generation); V2 GREEN (new checks.battery-notify, test_power fake battery: self-gate, silence at 80%, one toast per crossing, critical urgency, charging re-arms). Remains: V3 — real swaync toast on a draining laptop (HARDWARE-QUEUE). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
164 lines
8.2 KiB
Markdown
164 lines
8.2 KiB
Markdown
# Backlog — the prioritized task queue
|
||
|
||
The forward-looking half of the old docs/ROADMAP.md, reworked as a queue
|
||
agents can execute. Detailed design notes and decision records stay in
|
||
`docs/ROADMAP.md` (referenced as "ROADMAP § <item>"); this file is *what's
|
||
next, in what order*.
|
||
|
||
**Rules:**
|
||
- Agents take the topmost actionable item (see LOOP.md). Finished items
|
||
are **deleted** here — the journal + git log are the record; durable
|
||
design notes get a ✓-entry in docs/ROADMAP.md if worth keeping.
|
||
- Item numbers are **stable IDs** — never renumbered or reused. A gap in
|
||
the sequence means shipped (or dropped) work; new items take the next
|
||
free number regardless of tier.
|
||
- Tags: `[blocked:hw]` needs real hardware (see HARDWARE-QUEUE.md) ·
|
||
`[human]` needs Bernardo · `[stuck]` two failed attempts, needs help ·
|
||
`[big]` must be split before starting.
|
||
- Agents may append to **PROPOSED** and **Decisions** freely; only
|
||
Bernardo moves items *out* of PROPOSED into the tiers.
|
||
|
||
---
|
||
|
||
## NOW
|
||
|
||
*(empty — NEXT's top item is the queue head)*
|
||
|
||
## NEXT
|
||
|
||
### 13. Small niceties batch (one slice per iteration)
|
||
Each is a small, self-contained polish item in the existing patterns
|
||
(shipped: idle-inhibit/caffeine 2026-07-04; low-battery notifications
|
||
2026-07-05 — sysfs watcher + checks.battery-notify):
|
||
- **Color picker:** `hyprpicker` → clipboard as a Tools › entry +
|
||
`SUPER+CTRL` bind; pairs naturally with theme work.
|
||
|
||
### 14. Automated upstream lock bumps (maintainer CI, slices b+c) `[big]`
|
||
ROADMAP § Automated upstream lock bumps — the scheduled half (the
|
||
checks-on-push workflow shipped; see item 20 for the runner status):
|
||
weekly job runs `nix flake update` (within pinned release branches) →
|
||
full check suite → lands on `main` on green; `v1` promotion stays
|
||
human. Plus the fast-lane note for security bumps. Note the current
|
||
runner is eval-only (no KVM) — a green bump run guards eval, not the VM
|
||
suite, until item 20's stretch runner exists.
|
||
|
||
### 20. KVM runner → VM suite in CI `[human]`
|
||
The remaining stretch of the CI item — checks-on-push is live and
|
||
**green** (run #58; runner = gitea/act_runner docker, eval tier).
|
||
Register a second runner on a host with `/dev/kvm` + nix (host-mode
|
||
label `nix-kvm`), then an agent uncomments the workflow's `vm-checks`
|
||
job: the `checks.*` VM suite + real toplevel/HM builds on every push
|
||
(also upgrades item 14's bump gate from eval-only to the full suite).
|
||
|
||
### 15. Display profiles — docked/undocked switching
|
||
ROADMAP § Display / monitor management, remaining: true profile
|
||
switching of the *same* outputs (multi-layout toggles, beyond
|
||
per-output hotplug rules), optionally workspace-to-monitor binding.
|
||
Design first (state-file shape, menu surface) — write the plan into
|
||
this entry before coding.
|
||
|
||
### 16. Greeter theming from the JSON
|
||
ROADMAP § Greeter. tuigreet themed from theme-state.json at system
|
||
rebuild (same model as Plymouth's tint). Scope: tuigreet only (no SDDM).
|
||
|
||
### 17. Launch-or-focus UX scripts
|
||
ROADMAP § launch-or-focus. Hyprland dispatch scripts: a bind launches an
|
||
app or focuses its existing window. Curate which apps get binds;
|
||
cheatsheet entries via keybinds.nix.
|
||
|
||
### 18. "nomarchy" control center + first-boot welcome `[big]`
|
||
ROADMAP § control center. A single front-end over the common toggles on
|
||
the same `nomarchy-theme-sync` surface, + a first-boot guided
|
||
"pick your theme / essentials" flow. Needs a design pass (TUI vs GUI)
|
||
→ write options into Decisions before implementing. Note: items 9–11
|
||
(rollback menu, doctor, validation) are natural panels of it — design
|
||
them as composable commands, not dead ends.
|
||
|
||
### 19. Look & Feel menu category
|
||
ROADMAP § Menu system, remaining: group Theme + night-light (+ wallpaper
|
||
cycle, future appearance toggles) under a Look & Feel submenu once it
|
||
earns ≥3 entries — keep the root at six.
|
||
|
||
## LATER
|
||
|
||
- **Wallpapers artifact split** (ROADMAP § Faster switches — decided,
|
||
deferred): pinned `Nomarchy-wallpapers` input so a state write stops
|
||
re-copying 86 MB. Follow-on: pre-built theme variants if switches are
|
||
still slow after.
|
||
- **Installer round 2** (ROADMAP § Installer): multi-disk BTRFS RAID,
|
||
impermanence, BIOS/legacy boot.
|
||
- **Boot-from-snapshot**: a systemd-boot equivalent of grub-btrfs.
|
||
- **Night-light geo mode**: lat/long auto sunset/sunrise (means wlsunset).
|
||
- **Per-theme icon overrides** / more icon packs (ROADMAP § Icon themes).
|
||
- **MIPI/IPU software-ISP camera** support (no-UVC machines).
|
||
- **OCR screenshot-to-text**: a Capture › entry (grim region → tesseract
|
||
→ clipboard) — recording (#12, shipped 2026-07-04) already reshaped
|
||
the submenu, so this is now a two-row addition.
|
||
- **Doctor Waybar warning**: a self-gating bar indicator fed by
|
||
`nomarchy-doctor` (shipped 2026-07-04) — appears only when the sheet
|
||
has a ✖; click opens the sheet.
|
||
- **Auto-timezone Waybar tooltip** showing the detected zone (optional).
|
||
- **VPN exit-node richer display** (country/city) (optional).
|
||
- **NixOS release bump → v2** `[human]`: deliberate, hand-edited, never
|
||
automated; the previous attempt was discarded (2026-06-22) over a
|
||
Hyprland OOM blocker — see MEMORY.md before retrying (NOW#3 should
|
||
also soften that blocker class).
|
||
|
||
## PROPOSED (agent suggestions — await human triage)
|
||
|
||
*Agents: append here with a one-paragraph pitch (what/why/cost). Do not
|
||
implement. Bernardo moves accepted items into a tier.*
|
||
|
||
- **Menu parity for downstream-flake options** (raised by Bernardo,
|
||
2026-07-04, from the hardware sweep): anything the docs or the
|
||
hardware queue ask a user to *hand-edit into the downstream flake*
|
||
(`keyboard.layout` multi-layout, `power.batteryChargeLimit`,
|
||
`updates.enable`, `services.printing`, …) should have a menu toggle
|
||
instead — the in-flake-state philosophy already gives the menu a
|
||
write-into-the-flake path, and night-light / auto-timezone /
|
||
auto-commit prove the pattern (incl. rebuild-on-first-enable).
|
||
Pitch: (a) an audit listing every user-facing `nomarchy.*` option vs
|
||
its menu surface; (b) menu writers for the gaps, respecting the
|
||
toggle-vs-package discipline (bare template packages stay hand-edits)
|
||
and menu-placement convention (right submenu, root stays short).
|
||
Values beyond booleans (layout lists, charge thresholds) need a small
|
||
input UI per option. Cost: audit is one iteration; the writers a few
|
||
more, sliceable per option.
|
||
|
||
- **Portal/Flatpak camera picker still lists the internal IR sensor**
|
||
(ROADMAP § Webcam follow-up). The shipped IR-hide is a *WirePlumber
|
||
v4l2* rule, but Flatpak/portal apps consume cameras via the
|
||
**libcamera** path, where both sensors remain visible — a Flatpak
|
||
Zoom user can still pick the black IR "camera". Options, roughly
|
||
ascending cost: (a) do nothing — document it (portal camera support
|
||
is still rare in practice); (b) a WirePlumber *libcamera* monitor
|
||
rule disabling GREY-only nodes — needs verifying that libcamera
|
||
monitor rules can match early enough (the v4l2 investigation found
|
||
only `device.api` binds pre-rule, which is why surgical scoping
|
||
failed before — same wall likely applies); (c) a libcamera
|
||
configuration/udev quirk hiding the IR sensor at the libcamera layer
|
||
itself. Cost: (b)/(c) need a T14s-style RGB+IR machine to verify →
|
||
pairs with a hardware-queue session. Recommend (a) now, (b)
|
||
investigated when the T14s is next available.
|
||
|
||
## Decisions `[human]`
|
||
|
||
Open calls only Bernardo can make; agents add options/evidence but never
|
||
decide.
|
||
|
||
- **Formatter adoption:** repo deliberately has none; `nixfmt-rfc-style`
|
||
would flatten the aligned hand-formatting of ~33 files. Adopt or
|
||
declare never?
|
||
- **Docs site vs Markdown-in-repo** (from the docs-review item).
|
||
- **Control center form factor:** TUI (gum/ratatui-style) vs GUI vs
|
||
"the rofi menu *is* the control center, just add a first-boot flow".
|
||
- **zram swap:** faster under pressure and pairs with NOW#3, but it
|
||
interacts with the hibernation-swapfile story (resume device/priority
|
||
ordering) — adopt, adopt-with-hibernation-guard, or skip?
|
||
- **Default browser:** the template comments Firefox out. The shipped
|
||
mime defaults (item 8, done) point `text/html`/http(s) at
|
||
`firefox.desktop` as *inert* entries — they activate the moment
|
||
Firefox is installed and are skipped otherwise, so the remaining call
|
||
is only: ship a browser active in the suite, or stay
|
||
browserless-by-default?
|