diff --git a/README.md b/README.md index 3507ee2..815caec 100644 --- a/README.md +++ b/README.md @@ -194,7 +194,10 @@ nomarchy-what-changed # plain-language last rebuild (system + desktop; --summar `~/.nomarchy` is **your machine flake** (`system.nix` / `home.nix`). Newer Nomarchy code arrives when `flake.lock` updates the `nomarchy` input (`nomarchy-pull`), not by `git pull` of that directory (many installs have -no remote there — only local commits from auto-commit). +no remote there — only local commits from auto-commit). With auto-commit +on (menu: **System › Auto-commit**), all three commands above also sweep +any pending hand edits into a commit before they switch, so +`git -C ~/.nomarchy log` mirrors your generations. | When | Run | |---|---| diff --git a/agent/JOURNAL.md b/agent/JOURNAL.md index 66840df..22f2be1 100644 --- a/agent/JOURNAL.md +++ b/agent/JOURNAL.md @@ -19,6 +19,28 @@ Template: --- +## 2026-07-12 — auto-commit sweep before pull/rebuild/home (interactive) +- **Task:** Bernardo's request (no BACKLOG item): with autoCommit on, + hand edits to `~/.nomarchy` (his had 4) stayed forever-dirty — + theme-sync's commit is pathspec-limited to theme-state.json by design. +- **Did:** New internal `nomarchy-autocommit` in nomarchy-lifecycle: + live-reads `settings.autoCommit`, commits *everything* dirty with + message `nomarchy: auto-commit before