claude-nomad 0.63.2 → 0.64.0

package/CHANGELOG.md

@@ -1,5 +1,55 @@
 # Changelog
 
+## [0.64.0](https://github.com/funkadelic/claude-nomad/compare/v0.63.2...v0.64.0) (2026-08-05)
+
+### What's new
+
+- **Native Windows: deleting a shared config file now sticks.** On native Windows (PowerShell or
+  cmd), deleting a file inside a synced folder, say `~/.claude/commands/old.md`, used to leave it
+  sitting in the sync repo, and the next `nomad pull` put it straight back. The deletion is now
+  carried into the sync repo instead, so it survives the pull and reaches your other machines.
+  Nothing is removed unless this machine's own record shows it had the file, and every removed file
+  is copied to the backup directory first. The first pull after upgrading has no record yet, so
+  deletions start propagating from the pull after that. macOS, Linux, and WSL2 were never affected:
+  they symlink shared config, so deleting the file was always a deletion in the repo.
+- **Native Windows: a name clash during a pull now explains itself.** If a file you created inside a
+  synced folder has the same name as one an incoming update adds, the pull stops before changing
+  anything. You used to be left with git's own error, which pointed at a copy inside the sync repo
+  and told you to move it, and following that advice looped, because the next pull copied your file
+  back over it. You now get the file under `~/.claude/` to act on and the two ways to finish, keep
+  the incoming version or keep both and merge them, and nomad clears its own copy out of the way for
+  you. Your file is untouched either way.
+- **Native Windows shared-config changes show up in a preview first.** `nomad pull --dry-run` and
+  `nomad diff` now list both the edits being carried into the repo and the files being removed from
+  it, worked out before the pull so the preview and the real run agree.
+- **`nomad doctor` notices a native Windows shared file that has drifted.** When a synced copy under
+  `~/.claude/` no longer matches the one in the repo, doctor warns about it instead of reporting the
+  machine as healthy. On the symlink platforms there is only ever one file, so there is nothing to
+  drift.
+- **`nomad doctor` no longer recognizes `leftArrowOpensAgents`.** Claude Code dropped it from its
+  settings schema, so doctor will flag it as an unknown key if you still have it set. This one
+  applies everywhere, not just on Windows.
+
+
+### Added
+
+* **pull:** propagate Windows shared-config deletions into the sync repo ([#489](https://github.com/funkadelic/claude-nomad/issues/489)) ([3255fb7](https://github.com/funkadelic/claude-nomad/commit/3255fb7fc54e3c490627e0701d96226403020f7e))
+
+
+### Fixed
+
+* **pull:** explain a Windows mirror collision instead of forwarding git advice ([#491](https://github.com/funkadelic/claude-nomad/issues/491)) ([2f13a61](https://github.com/funkadelic/claude-nomad/commit/2f13a619ca066ea707cc7b7e7e0e738a136ebf9f))
+
+
+### Changed
+
+* **doctor:** sync settings schema keys ([#488](https://github.com/funkadelic/claude-nomad/issues/488)) ([78bcf7c](https://github.com/funkadelic/claude-nomad/commit/78bcf7c17b8557f6f26e33bd74405fb8cd7228a8))
+
+
+### Documentation
+
+* distinguish native Windows from WSL2 in the user docs ([#492](https://github.com/funkadelic/claude-nomad/issues/492)) ([f6b1e9e](https://github.com/funkadelic/claude-nomad/commit/f6b1e9ee1feba24150b03741a255793b4238f253))
+
 ## [0.63.2](https://github.com/funkadelic/claude-nomad/compare/v0.63.1...v0.63.2) (2026-08-04)
 
 ### What's new

package/README.md

@@ -58,13 +58,14 @@ survives different file paths and your secrets never ride along.
   project folder no longer exists on this machine, a multi-host repo where this machine's
   hostname-derived key matches no `hosts/<HOST>.json` or path-map entry (a sign `NOMAD_HOST` is
   unset here, so per-host settings and session sync will not line up with the other hosts), synced
-  skills with local edits that differ from the shared copy, 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.
-  By default the report is compact: it shows only checks that need action plus a one-line verdict.
-  Add `--verbose` (or `--all` / `-v`) to see the full per-check tree, including everything that
-  passed.
+  skills with local edits that differ from the shared copy, a native Windows shared-config copy that
+  has drifted from the repo's copy (a warning, not a failure), 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. By default the report is compact: it shows only checks that need action plus a one-line
+  verdict. Add `--verbose` (or `--all` / `-v`) to see the full per-check tree, including everything
+  that passed.
 - **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
@@ -130,9 +131,9 @@ That leaves two files to keep in step, and claude-nomad does it for you: `nomad
 overwritten. Enabling Developer Mode does not change this; copies are used on every native Windows
 host either way.
 
-Two things are genuinely Windows-only, both covered in the bullets below: a `.gitleaksignore` allow
-entry may not travel to a macOS or Linux host, and deep session paths can hit Windows's
-260-character path limit.
+Two things come from native Windows specifically, both covered in the bullets below: a
+`.gitleaksignore` allow entry may not travel to a macOS, Linux, or WSL2 host, and deep session paths
+can hit the native Windows 260-character path limit.
 
 The native Windows steps are the same as above with a couple of PowerShell-specific swaps:
 
@@ -154,7 +155,9 @@ The native Windows steps are the same as above with a couple of PowerShell-speci
 > nomad push
 ```
 
-A few Windows-specific things worth knowing:
+A few native Windows specifics worth knowing. WSL2 behaves like Linux, so the copy-sync and
+path-length items below do not apply to it; the `.gitleaksignore` one can still reach it, from the
+other side:
 
 - **Installing gh:** `winget install GitHub.cli` (or `scoop install gh`), then `gh auth login`.
   Needed before `nomad init` on the first host; later hosts only clone with it.
@@ -162,26 +165,37 @@ A few Windows-specific things worth knowing:
   use Scoop). `nomad doctor` prints the same hint whenever gitleaks is missing from PATH.
 - **Shared config is copied, not symlinked.** On macOS and Linux, files like `CLAUDE.md` and your
   skills live in the sync repo and are symlinked into `~/.claude/`, so there is one source of truth
-  on disk. Creating a symlink on Windows needs Developer Mode or admin rights, so on native Windows
-  these are real copies instead, whether or not you have Developer Mode enabled. WSL2 is unaffected
-  and behaves like Linux. What this means for you: nothing extra. On Windows both `nomad pull` and
-  `nomad sync` mirror your local copies into the repo before they fetch, so an unpublished edit is
-  captured rather than reverted. The one command that deliberately takes the repo's version is
-  `nomad pull --force-remote`, which is what that flag is for; the copy it replaces is snapshotted
-  to the backup dir first. This is the same behavior claude-nomad's `skills/` sync already has on
-  every platform.
+  on disk. Creating a symlink on native Windows needs Developer Mode or admin rights, so there these
+  are real copies instead, whether or not you have Developer Mode enabled. WSL2 is unaffected and
+  behaves like Linux. What this means for you: nothing extra. On native Windows both `nomad pull`
+  and `nomad sync` mirror your local copies into the repo before they fetch, so an unpublished edit
+  is captured rather than reverted. A file you delete from a shared directory is handled the same
+  way: it is removed from the sync repo by the next pull, exactly as deleting inside a symlinked
+  directory already removes it on macOS or Linux. The removal is left uncommitted, so it publishes
+  on your next push and passes the same secret scan as everything else, and the file is snapshotted
+  to the backup dir first. The safety rule behind this: nomad only removes a file it has a record of
+  having given this machine, so a repo file this machine has never synced is never touched. That
+  record is also why the first pull after you upgrade to this version is an exception: there is
+  nothing to compare against yet, so a deletion made before that pull comes back once, and deleting
+  it again sticks. If a file you created has the same name as one another machine just created, the
+  pull stops before it changes anything and tells you which file under `~/.claude/` to move or
+  rename, with the two ways to finish. Nothing is lost either way: your file stays exactly as you
+  left it and the update simply waits for the next pull. The one command that deliberately takes the
+  repo's version is `nomad pull --force-remote`, which is what that flag is for; the copy it
+  replaces is snapshotted to the backup dir first. This is the same behavior claude-nomad's
+  `skills/` sync already has on every platform.
 - **A `.gitleaksignore` allow entry may not travel across hosts.** gitleaks fingerprints each
-  finding using the file path exactly as it saw it: backslashes on Windows, forward slashes on
-  macOS/Linux. If you allow a finding with `nomad push --allow` (or `nomad allow`) on Windows, the
-  identical finding can reappear as "new" the first time it is scanned from a macOS/Linux host, and
-  the same happens in reverse. This is a known gitleaks limitation, not a claude-nomad bug; just
-  allow it again from the other host.
+  finding using the file path exactly as it saw it: backslashes on native Windows, forward slashes
+  on macOS/Linux/WSL2. If you allow a finding with `nomad push --allow` (or `nomad allow`) on native
+  Windows, the identical finding can reappear as "new" the first time it is scanned from a macOS,
+  Linux, or WSL2 host, and the same happens in reverse. This is a known gitleaks limitation, not a
+  claude-nomad bug; just allow it again from the other host.
 - **Line endings stay put.** A fresh `nomad init` writes a `.gitattributes` with `* -text`, so Git
   never converts line endings between hosts. If you are joining a sync repo created before this file
   existed, add that one line from any host (or watch for the `nomad doctor` warning that nudges
-  you), otherwise a Windows checkout with the common `core.autocrlf=true` Git default would rewrite
-  every text file's line endings, and every host would then see the whole tree as permanently
-  changed.
+  you), otherwise a native Windows checkout with the common `core.autocrlf=true` Git default would
+  rewrite every text file's line endings, and every host would then see the whole tree as
+  permanently changed.
 
 Everyday loop on any host:
 
@@ -307,8 +321,8 @@ independently from the CLI, but requires nomad `>= 0.35.0` because it calls rece
 - `gh` ([GitHub CLI](https://cli.github.com/)), required by `nomad init`
 
 Works on macOS, Linux (including WSL2), and native Windows (PowerShell or cmd). See
-[Windows](#windows) above for the Windows equivalents of the install and host-label steps, the
-copy-sync trade-off, and the `.gitleaksignore` cross-host caveat.
+[Windows](#windows) above for the native Windows equivalents of the install and host-label steps,
+the copy-sync trade-off, and the `.gitleaksignore` cross-host caveat.
 
 **Optional:** [curl](https://curl.se/) or [wget](https://www.gnu.org/software/wget/) for the
 version-staleness check and `nomad doctor --check-schema`. The CLI works without them. The opt-in