Bernardo Magri
bbdc329ed6
All checks were successful
Check / eval (push) Successful in 3m39s
After the #81 "you're set" card, at most one additional "Hardware tips" toast: a Firmware line when fwupdmgr is on PATH, a Fingerprint line when fprintd-list is (VISION § B). One-shot marker settings.hardwareHintsShown, in-checkout like firstBootShown. When no tooling matches, the marker is deliberately left unset — the re-check costs a command -v per session, and a later-enabled fwupd or newly-added reader still gets its hint once. Never a permanent nag; live-ISO gate covers the new stage too. Lives inside nomarchy-first-boot: the card's semantics are unchanged (retry loop, exit 1 so a failed notify retries next login, marker only after success); hints run only once the card has landed. Docs: README option row, HARDWARE.md hint paragraphs, VISION § B checked off. Verification: V2 — shellcheck clean, nix flake check --no-build green, nix build .#checks.x86_64-linux.first-boot green (bare node silent → fwupdmgr appears → fires once → silent again → live-ISO still skips). Real toast rendering is the same session surface as the proven #81 card. Implementation by a Sonnet subagent; design and review on Fable. 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 § ….