c44616aeb0
All checks were successful
Check / eval (push) Successful in 3m53s
modules/home/autotheme.nix installs a user service + timer (nomarchy-auto-theme) that periodically runs `nomarchy-theme-sync auto`, so the day/night theme is applied on the current schedule through the same one engine. Install gates on settings.autoTheme.enable (read from state, the way updates.nix gates on its enable), so a machine not using the feature carries no timer. Timer: OnStartupSec=1min (settle after login) + OnCalendar=*:0/15 + Persistent (catch a transition missed while off). Periodic rather than exact sunrise/sunset timers — robust to suspend/DST, and `auto` is idempotent (no rebuild unless the theme must change) so ticks are cheap. Verification: V1 — real-config eval (state temporarily enabled, then restored) confirms the units land when enabled (OnCalendar *:0/15, ExecStart `... nomarchy-theme-sync auto`) and are absent when disabled; systemd-analyze validates the schedule. V0 flake check green. The live timer -> home-manager switch on a real Nomarchy session is pending a Nomarchy machine (same blocker as #76). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Agent loop state
Git-tracked state for autonomous and assisted work on Nomarchy. Protocol: LOOP.md. Entry for most harnesses: repo-root CLAUDE.md.
Files
| File | Who writes | Role |
|---|---|---|
| LOOP.md | Human | One-iteration protocol (orient → pick → work → verify → commit → record) |
| GOALS.md | Human (agents propose) | Pillars, quality bars, non-goals |
| CONVENTIONS.md | Human (agents propose) | How to write code/menu/state while shipping |
| BACKLOG.md | Both | Prioritized queue — only executable work list |
| JOURNAL.md | Agents | Append-only iteration log (read last 3–5 entries) |
| MEMORY.md | Agents | Curated durable gotchas |
| HARDWARE-QUEUE.md | Agents append, human checks | On-hardware V3 tests only Bernardo can run |
Product / design docs (not a queue)
| File | Role |
|---|---|
| ../docs/VISION.md | v1.0 product themes — agents slice into BACKLOG PROPOSED |
| ../docs/ROADMAP.md | Design history + shipped log |
| ../docs/README.md | Full docs map |
Claude Code only
| Path | Role |
|---|---|
| ../.claude/settings.json | Tool permissions |
| ../.claude/agents/ | nomarchy-scout / nomarchy-runner subagent defs |
Do not put backlog items or vision text under .claude/ — it is not
shared with other agent runners.
Rules of thumb
- Execute from BACKLOG only (NOW → NEXT; never PROPOSED without human triage).
- Orient with GOALS + CONVENTIONS + MEMORY + last journal + BACKLOG; when the task is product-shaped, also read the relevant VISION §.
- Record lasting design in ROADMAP ✓ when something ships that future humans should know; delete the BACKLOG line.
- v1 branch is human-only — never advance from an agent session.