860c70466f
All checks were successful
Check / eval (push) Successful in 3m46s
Adds an "Auto theme (on/off)" row to Look & Feel and an `autotheme` submenu: toggle the feature, pick the day/night themes (from `nomarchy-theme-sync list`), and set the sunrise/sunset times (HH:MM, validated). This is the menu surface over settings.autoTheme, completing the auto time-of-day theme feature (slices: CLI / timer / menu). Enabling writes the flag and defaults the summer-day/summer-night pair --no-switch, then runs `auto --force`, so a single rebuild both installs the timer and applies the correct theme for now. Disabling is instant (--no-switch): the flag flips and `auto` self-gates, so the lingering timer no-ops until the next rebuild. Day/night/time writes are live --no-switch (read by `auto` at tick time). Verification: V1 — HM generation builds (bash -n on nomarchy-menu at build) + bash -n on the built menu. Logic test with stubbed rofi/theme-sync/notify: selecting the toggle from off runs exactly `set day/night/enable ... --no-switch` then `auto --force` — the intended one-rebuild path. V0 flake check green. All three #79 slices shipped; the live timer switch across sunset is a real-session (V3) check on a Nomarchy machine. Co-Authored-By: Claude Opus 4.8 <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 |
| 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 |
|---|---|
| ../agent/README.md | Executable agent loop state: BACKLOG, LOOP, MEMORY, … |
| ../CLAUDE.md | Agent entry point (any harness that reads it) |
| ../.claude/ | Claude Code 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 § ….