feat(cli): nomarchy-pull / nomarchy-rebuild / nomarchy-home

Split lifecycle into three clear commands (user pick):
  nomarchy-pull     git pull (if checkout) + flake.lock update
  nomarchy-rebuild  system switch on current lock (snap + nvd)
  nomarchy-home     Home Manager switch

Full upgrade: pull && rebuild && home. Legacy sys-update / sys-rebuild /
home-update remain as wrappers. nixos-rebuild-snap uses NOMARCHY_PATH.

V0: flake check --no-build green.

docs/RECOVERY.md

@@ -27,11 +27,11 @@ recent desktop generations — pick one and it activates.
 Or simply apply a theme you know is good: `nomarchy-theme-sync apply
 boreal` (or any preset). If a switch failed halfway, the state file is written
 *before* the rebuild — fix the cause and re-run
-`home-manager switch --flake ~/.nomarchy` (or `home-update`).
+`home-manager switch --flake ~/.nomarchy` (or `nomarchy-home`).
 
 Your flake checkout is a git repo, and with auto-commit enabled every
 apply is a commit: `git -C ~/.nomarchy log` to see what changed,
-`git revert` the culprit, then `home-update`.
+`git revert` the culprit, then `nomarchy-home`.
 
 ## 2. The desktop won't start at all
 
@@ -59,7 +59,7 @@ last 10 generations are kept). That boots yesterday's system unchanged.
 Booting an old generation is temporary — the default entry is still the
 broken one. Make the fix stick from the working boot: revert the change
 in `~/.nomarchy` (`git -C ~/.nomarchy revert …` or edit `system.nix`
-back), then `sys-rebuild`.
+back), then `nomarchy-rebuild`.
 
 ## 4. Files went missing or wrong — snapshots (BTRFS installs)
 

docs/ROADMAP.md

@@ -264,9 +264,9 @@ Design/decision records and a running log of shipped work (items marked
   `gl`/`glg`, `gp`/`gpl`, `gf`), and a nix block (`ns`, `nr`, `nfu`, `nfc`,
   `nsearch`, `ngc`), plus `path` and `reload`. Scope decision: short where it
   helps but **never shadow a real binary** (same rule as rg/fd — the git block
-  deliberately avoids `gs`/ghostscript); system/home rebuilds keep their full
-  `sys-update`/`home-update` names rather than getting cryptic aliases. The set
-  is documented in README §5 (Day-to-day), and `alias` lists them in-shell.
+  deliberately avoids `gs`/ghostscript); lifecycle is `nomarchy-pull` /
+  `nomarchy-rebuild` / `nomarchy-home` (full names on PATH, not aliases). The
+  set is documented in README §5 (Day-to-day), and `alias` lists shell shortcuts.
 - **Theme-switch feedback:** ✓ the "rebuilding…" notification is now
   persistent (timeout 0) and replaced in place by "applied ✓" / failure
   via a synchronous tag, so a multi-minute switch never reads as a failed