Bernardo Magri
3abeccf071
All checks were successful
Check / eval (push) Successful in 4m26s
The bare `button, button label` selectors in the #98 safety net load into every GTK3 process, including Waybar, and a rule matching the label node outranks the color waybar.css inherits onto `#workspaces button` — so workspace digits always rendered the gtk.css text color captured at bar start, never the theme's @muted dots / @base-on-accent active pill (the pair check-theme-contrast.py gates). With the bar never restarting on switch (previous commit) the pin also went stale: all three 2026-07-18 screenshots carried kiln-clay's @text #39302A across three dark themes. Scoped the enabled+disabled pins to the dialog selectors #98 actually targeted; forcing adw-gtk3-dark remains the primary #98 fix, and the sheet's own bare `label` rule sets only caret-color, so inheritance carries the bar colors again. Verified live on Newton (V3-grade): under the scoped gtk.css, boreal renders the designed digits — @base #21272F on the @accent pill, @muted #5E6A78 inactives — pixel-sampled from a bar spawned on a headless output. V1: HM generation builds; bare selectors absent from the built gtk.css, dialog-scoped ones present. Journal, hardware-queue (deploy round-trip) and ROADMAP follow-up ride along. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Docs map
Where human and agent documentation lives. Do not invent a third tree for the same facts.
| Path | Audience | Role |
|---|---|---|
| ../README.md | Everyone | What Nomarchy is, install, options tables |
| REQUIREMENTS.md | Users + agents | Minimum system requirements (GPU/OpenGL, RAM, disk, UEFI) |
| VISION.md | Maintainers + agents | Product north star toward v1.0 and beyond — themes, not a task queue |
| ROADMAP.md | Maintainers + agents | Design/decision records + shipped log (historical ✓) |
| HARDWARE.md | Users + agents | Firmware, profiles, drivers, unsupported machines |
| TESTING.md | Maintainers + agents | Verification ladder, honesty rule, ISO/VM recipes |
| RECOVERY.md | Users | Broken theme/desktop/boot → undo |
| OVERRIDES.md | Users | Downstream Nix overrides |
| MIGRATION.md | Users | Existing NixOS → Nomarchy without reinstall |
| OMARCHY.md | Users | Coming from Omarchy — bindings/theme/install/config map |
Related (not under docs/)
| Path | Role |
|---|---|
| ../AGENTS.md | Agent entry point, any vendor/harness (CLAUDE.md symlinks to it) |
| ../agent/README.md | Agent instructions + executable loop state: BACKLOG, LOOP, VERIFICATION, … |
| ../.claude/ | Claude Code adapter only: permissions + subagent defs |
How work flows
VISION (what we want the product to feel like)
│
▼ human triages slices into…
BACKLOG (what's next, ordered — agents execute only this)
│
▼ lasting design notes after ship →
ROADMAP ✓ entries
Agents do not implement directly from VISION or ROADMAP. They take
the top actionable item in agent/BACKLOG.md (see agent/LOOP.md).
They may append PROPOSED pitches that reference VISION § … or
ROADMAP § ….