claude-nomad 0.50.3 → 0.51.1

package/CHANGELOG.md

@@ -1,5 +1,24 @@
 # Changelog
 
+## [0.51.1](https://github.com/funkadelic/claude-nomad/compare/v0.51.0...v0.51.1) (2026-06-18)
+
+
+### Fixed
+
+* **doctor:** handle diverged settings keys honestly instead of advising blind pull ([#315](https://github.com/funkadelic/claude-nomad/issues/315)) ([39f8148](https://github.com/funkadelic/claude-nomad/commit/39f81480285693e08575f5ab4ecbb8b182eeb233))
+
+## [0.51.0](https://github.com/funkadelic/claude-nomad/compare/v0.50.3...v0.51.0) (2026-06-18)
+
+
+### Added
+
+* **capture-settings:** direction-aware settings drift detection and capture command ([#314](https://github.com/funkadelic/claude-nomad/issues/314)) ([512c1a2](https://github.com/funkadelic/claude-nomad/commit/512c1a27a3a573b3c2684bae21e577a50a58a098))
+
+
+### Changed
+
+* **deps:** regenerate package-lock.json ([#312](https://github.com/funkadelic/claude-nomad/issues/312)) ([a80a974](https://github.com/funkadelic/claude-nomad/commit/a80a9740be72a1cad6e7865697548274ff0fbe51))
+
 ## [0.50.3](https://github.com/funkadelic/claude-nomad/compare/v0.50.2...v0.50.3) (2026-06-17)
 
 

package/README.md

@@ -40,9 +40,11 @@ survives different file paths and your secrets never ride along.
   `--dry-run` on pull and push prints the plan without writing anything.
 - **One command tells you what is wrong.** `nomad doctor` is a read-only health check: wedged sync
   repo, broken hook references, hooks that would crash on session start because of a missing
-  `--preserve-symlinks-main` flag, version drift, oversized backup cache, and settings drift (warns
-  when `~/.claude/settings.json` no longer matches the base+host merge nomad would write, the
-  silent-clobber case, with `nomad pull` as the fix), each with a fix hint.
+  `--preserve-symlinks-main` flag, version drift, oversized backup cache, and settings drift in both
+  directions: keys present in the repo merge but absent from your live `settings.json` (behind; the
+  next `nomad pull` will restore them, fix: `nomad pull`) and keys present locally but not yet in
+  the repo (ahead; local-only additions, fix: `nomad capture-settings`). Each issue includes a fix
+  hint.
 - **Self-healing sync.** Every overwrite is backed up first, and `nomad pull --force-remote`
   recovers two kinds of stuck sync repo: a repo stuck mid-rebase or mid-merge (aborts the operation,
   parks stranded work on a branch, refuses if shared config is at risk), and a repo where the rebase
@@ -123,6 +125,15 @@ surfaces any orphaned autostash entry, then re-pulls). Run `nomad doctor` first
 which state you are in; the Repository section names the specific problem and points at the right
 fix.
 
+If an external tool (such as Claude Code or GSD) wrote new keys into your `~/.claude/settings.json`
+that are not yet in your shared repo, run `nomad capture-settings` to promote them before the next
+`nomad pull` overwrites them. With `--host`, the keys land in `hosts/<NOMAD_HOST>.json` instead of
+`shared/settings.base.json` (useful for machine-specific values such as absolute paths). `--dry-run`
+shows what would be written without touching anything. Before it writes, `capture-settings` shows
+the destination and the keys and asks you to confirm; pass `--yes` (or `-y`) to skip the prompt,
+which is required when running without an interactive terminal. `nomad push` also warns when it
+detects ahead-drift so you have a prompt to act before the push completes.
+
 ## Claude Code plugin
 
 An optional companion plugin puts nomad one slash away inside Claude Code and warns you at session