Files
Nomarchy/agent/BACKLOG.md
Bernardo Magri 4cdc80c9bc
Some checks failed
Check / eval (push) Failing after 1m31s
docs(agent): close #76 — hibernate→resume V3 PASSED on TuringMachine
Bernardo ran the real power-cycle on the T14s (LUKS + btrfs @swap
swapfile): hibernate → power off → single LUKS unlock → session
restored. BACKLOG #76 deleted; HARDWARE-QUEUE resume entry pruned
(outcome recorded in the remaining no-swap-notify entry, JOURNAL, and
the ROADMAP ✓-entry); Decisions hibernation note marked shipped. The
no-swap Hibernate notify check remains the one open leftover.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-12 07:52:10 +01:00

187 lines
9.1 KiB
Markdown
Raw Blame History

This file contains invisible Unicode characters
This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Backlog — the prioritized task queue
**This is the only executable work list for agents.** Product themes and
v1.0 intent live in [`docs/VISION.md`](../docs/VISION.md); design history
in [`docs/ROADMAP.md`](../docs/ROADMAP.md); map in
[`docs/README.md`](../docs/README.md) and [`agent/README.md`](README.md).
**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 (and/or a note in VISION)
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 (include
`VISION § …` or `ROADMAP § …` when relevant); only Bernardo moves items
*out* of PROPOSED into the tiers.
---
## NOW
*(empty — NEXT's top item is the queue head)*
## NEXT
### 89. Tray icon parity — themed overrides for SNI apps (Bernardo 2026-07-11)
The bar is monochrome; third-party tray icons aren't. EasyEffects 8's Qt
SNI publishes IconName `com.github.wwmm.easyeffects` → Papirus full-color
blue (T14s V3, 2026-07-11); Signal / Telegram / ZapZap (all flatpaks on
the T14s) likely worse. Goal: every tray icon reads like part of the bar.
Slices:
1. **Inventory — DONE (T14s live session, 2026-07-11):**
| app | IconName | pixmap? | verdict |
|---|---|---|---|
| nm-applet | `nm-signal-*` (state-varying) | no | **name-based** — override the `nm-*` family |
| udiskie | `drive-removable-media-usb-panel` | no | **name-based** |
| Telegram | `org.telegram.desktop[-mute/-attention]-symbolic` | yes (fallback) | **name-based** — ship all state names |
| Signal | `Signal_status_icon_1` (generated, not a real theme name) | yes | **pixmap** — slice 3 |
| ZapZap | *(empty)* | yes | **pixmap** — slice 3; check its own tray-style setting first |
| EasyEffects 8 | `com.github.wwmm.easyeffects` (prior T14s finding) | — | **name-based**; NB `--gapplication-service` alone registers no SNI |
**Bernardo's visual verdict (T14s, 2026-07-11):** Telegram and ZapZap
already read fine on the bar — out of scope. The offenders are
**EasyEffects** (slice 2: name-based override) and **Signal**
(slice 3: pixmap; check for an app-side tray option, else document).
Related fix shipped same day: easyeffects.service now *waits for a
registered tray host* before starting (the old After=waybar.service
ordering was inert — waybar is supervisor-run, not a unit), so the
icon no longer vanishes on unlucky boot order.
2. **Override layer:** an HM-managed shadow icon dir that wins the XDG
lookup for the session icon theme (e.g. `xdg.dataFile
"icons/<theme-iconset>/…"` shadowing the store copy, or a
`Nomarchy-tray` theme inheriting the active set — pick whichever
survives theme whole-swaps; icons must follow the active theme per
THEME-DESIGN, not hardcode one palette). Ship monochrome SVGs for the
name-based offenders found in slice 1. Waybar restart re-resolves.
3. **Pixmap apps:** document (or wire, where a setting exists) per-app
monochrome/tray options; what can't be fixed goes in the item's
record, not silent scope creep.
V-path: V1 eval + icon file lands in the right lookup dir; V3 screenshot
of the tray on a real session (headless VM has no flatpak chat apps).
## 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.
- **MIPI/IPU software-ISP camera** support (no-UVC machines).
- **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).
## FUTURE (decided deferred — not the agent queue head)
Work we **intend** someday but explicitly **not** NEXT. Agents do not
pick these unless Bernardo promotes one into NEXT/NOW.
### 20. KVM runner → VM suite in CI `[human]`
**Status (2026-07-10):** keep **eval-only** CI on the current Gitea
stack (act_runner in docker-compose on the 4c/4GB IONOS VPS). Nested
KVM + RAM headroom on that host are a poor fit next to Gitea; full
`checks.*` VMs stay local / promotion-time until a **separate**
KVM-capable machine exists.
**When ready:** register a second runner (host-mode nix + `/dev/kvm`,
label `nix-kvm` — not the existing docker eval runner), then uncomment
the `vm-checks` job in `.gitea/workflows/check.yml` (`runs-on: nix-kvm`,
`nix flake check` + toplevel/HM builds). Do not enable the job until
that label is online (Gitea queues forever otherwise).
### Formatter — adopt later `[human]`
**Intent:** add a Nix formatter (likely `nixfmt-rfc-style`) in a dedicated
pass: reformat the tree once, document in CONVENTIONS, optional CI
check. **Not** the queue head — no drive-by reformats until that pass.
## 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.*
*Open work only. Shipped exam/AC items (#47#63, #14, #52 theme
high-ROI, etc.) live in the journal + ROADMAP — not here.*
### Product / day-2
- **NVIDIA first-class options** — **deferred past v1** (Bernardo
2026-07-10). Keep #59 commented install guidance; no
`nomarchy.hardware.nvidia.*` until a hybrid maintainer + queue.
- **Post-install hardware hints** (`VISION § B`) — After the general
“you're set” card (#81), optionally fire **one** additional
self-gated notify when the machine actually has the hardware:
(a) `fwupdmgr` on PATH → “System Firmware to check LVFS updates”;
(b) `fprintd-list` on PATH → “System Fingerprint to enroll”.
One-shot markers in `settings.*` (same in-checkout discipline as
`firstBootShown`); never a permanent MOTD nag. Cost: small — extend
`nomarchy-first-boot` or a sibling oneshot + `checks.first-boot`
fixture. Control-center / MOTD already mention these; the gap is the
silent first *graphical* session for people who never open those.
- **Fingerprint *or* password, in parallel** (2026-07-11, Bernardo) —
`fingerprint.pam` gives pam_fprintd's sequential UX: sudo waits on
the reader, password only after failure/timeout. Bernardo wants
either factor accepted at the same prompt (type the password *or*
touch the sensor, whichever comes first). Stock PAM can't express
this; needs a parallel-conversation module (e.g. `pam-any`, not in
nixpkgs — would be a new package + `fingerprint.pam = "any"` mode).
Cost: medium (package + PAM wiring + careful lockout testing on real
hardware). Security note: keep sudo fallback sane if fprintd hangs.
_(#80#83 + #85#88 shipped 2026-07-11. Theme A day-2 + neon-glass finish
shipped — VISION ✓. Dock/hibernate V3 → HARDWARE-QUEUE.)_
### v1.0 pointer
See **VISION**. Open PROPOSED: post-install hardware hints; NVIDIA
deferred past v1; IR portal (b)/(c) need T14s (HARDWARE-QUEUE § T14s).
Standing calls: browser = Chromium; power = PPD.
## Decisions `[human]`
Open calls only Bernardo can make; agents add options/evidence but never
decide. **Resolved** entries stay for history; agents treat them as closed.
### Resolved (2026-07-10)
- **Docs site vs Markdown-in-repo** — **markdown in-repo for now**
(`docs/`, README). A rendered docs site is FUTURE if wanted.
- **Default browser** — **ship Chromium** in
`templates/downstream/home.nix`; mime → `chromium-browser.desktop`.
Opt out: delete the line / override mime.
- **Default power backend** — **keep PPD** (`nomarchy.system.power.backend`
default). TLP remains the one-line opt-in. Rationale: stability + live
profile API for menu/Waybar; Omarchys TLP experiment reverted.
### Resolved (2026-07-10, more)
- **Formatter adoption** — **yes, but not now.** Tracked as FUTURE
(below). Nix-source style only (`nixfmt-rfc-style` or similar); one
bulk reformat + CI/check when promoted. Until then: hand-aligned
style per CONVENTIONS.
- **Hibernation** — **want by default** (product intent). Needs a
disk-backed swap (file or partition) sized for resume; not zram alone.
**Shipped as #76**; V3 power-cycle PASSED on TuringMachine 2026-07-12
(ROADMAP § Hibernation + zram by default).
### Resolved (2026-07-10, #76 design)
- **Swap sizing** — **exactly RAM** (installer default, unchanged). Hibernate
image ≤ RAM; zram takes day-to-day paging. **`swapSize=0`** stays no-swap.
- **Migration** — **docs runbook** (`docs/MIGRATION.md`), not a tool.
- **No-swap Hibernate** — keep the menu row; **notify on failure**.