lshed 0.7.0 → 0.7.4

package/CHANGELOG.md

@@ -1,5 +1,45 @@
 # Changelog
 
+## 0.7.4 — 2026-09-03
+
+The first CI run on real macOS and Windows machines found three bugs. All of them were path comparisons that only hold on Linux.
+
+- A stub whose symlink points into a package was not recognised as generated on **macOS or Windows**. The target of a broken link cannot be resolved, so it was compared unresolved: on macOS `/var/folders/...` never matches the package's real `/private/var/folders/...`. Paths are now resolved as far as they exist before being compared.
+- The warning for a settings value pointing inside a package never fired on **Windows**, because it matched the raw path against JSON text where backslashes are escaped. It now walks the values and compares them as paths.
+- Path comparison is one helper that strips the Windows `\\?\` prefix and ignores case there.
+- The test that runs a package's `install:` script is skipped on Windows; `./setup` is a shell script and `cmd.exe` cannot run it.
+
+## 0.7.3 — 2026-09-03
+
+You no longer need Node to run lshed.
+
+- **Standalone binaries** for Windows x64, macOS (arm64/x64) and Linux (x64/arm64), attached to every tagged release. They carry their own runtime (~60-85 MB) and need nothing installed. `npm run binaries` builds all five from one machine.
+- **The npm package is self-contained.** `commander`, `yaml` and `zod` are bundled into `dist/cli.js` (627 KB) instead of being installed alongside it; `zod` alone was 7.9 MB. `npm install -g lshed` now downloads one file.
+- The version is baked in at build time, so the binaries do not look for a `package.json` that is not there.
+- The smoke script accepts `LSHED_CLI=<path>` and is run against the compiled binary in CI, so the binaries are tested, not just built.
+
+The design assumed everyone using a coding agent already had Node, because Claude Code installs through npm. Claude Code also has a native installer, and that assumption cost a user their laptop.
+
+## 0.7.2 — 2026-09-03
+
+Joining a machine that already has a harness, found while preparing the Windows check.
+
+- `restore` warns before removing parts that a **different** shed had claimed. Running `init` against a scratch shed to look around marks that machine's own parts as managed, so a later restore from the real shed would remove them. They were always backed up, but nothing said why. `lshed scan` is the read-only way to look.
+- No longer crashes with an `EPIPE` stack trace when output is piped into something that exits early (`lshed status | head`).
+- The smoke script now models a machine that already runs the agent: a skill whose name collides with the shed, a skill only that machine has, and its own MCP and settings. It checks that a collision is backed up and replaced, that machine-only parts survive, that nothing is removed, and that `add` pushes them into the shed.
+- README: how to join a machine that already has a setup, and why not to `init` there.
+
+## 0.7.1 — 2026-09-03
+
+Groundwork for running on Windows and macOS. Not yet verified on a real machine.
+
+- Package `install:` commands run through the platform shell (`sh` or `cmd.exe`) instead of a hard-coded `sh -c`.
+- On Windows, `claude` and other wrappers installed as `.cmd` are found by spawning through the shell.
+- Home-directory paths with backslashes are also rewritten to `${HOME}`.
+- `sync` explains what to do when git has no user identity.
+- `npm run smoke` drives the built CLI through init, restore, add, diff, save, profile switch, list and sync in a temporary directory without touching the real `~/.claude`. Use it on a new OS before trusting a real restore.
+- GitHub Actions matrix: ubuntu, macOS, Windows × Node 20, 22. Tests use directory junctions on Windows so no elevated privileges are needed.
+
 ## 0.7.0 — 2026-09-03
 
 `settings.json` travels, without merging.

package/README.md

@@ -25,11 +25,23 @@ Currently supports **Claude Code** (`~/.claude`). Other agents plug in through a
 
 ## Install
 
+With Node 20 or newer:
+
 ```
-npm install -g lshed
+npm install -g lshed          # or run it once: npx lshed status
 ```
 
-Node 20 or newer. `git` on the PATH for packages and `sync`. `claude` on the PATH if your shed lists plugins.
+Without Node, download a standalone binary from the [latest release](https://github.com/LeeSongHeon-LSH/lshed/releases/latest) and put it on your PATH. It carries its own runtime, so it is ~80 MB.
+
+| Platform | File |
+|---|---|
+| Windows x64 | `lshed-windows-x64.exe` → rename to `lshed.exe` |
+| macOS Apple Silicon / Intel | `lshed-darwin-arm64` / `lshed-darwin-x64` |
+| Linux x64 / arm64 | `lshed-linux-x64` / `lshed-linux-arm64` |
+
+On macOS and Linux, `chmod +x` it first. The binaries are unsigned, so macOS warns on first run.
+
+Either way you also need `git` on the PATH for packages and `sync`, and `claude` if your shed lists plugins.
 
 ## Quick start
 
@@ -89,6 +101,31 @@ lshed sync            # commit the shed, pull, push
 
 `save` is the only path from `~/.claude` to the shed, and it only works for parts the shed owns (`file:` sources). `sync` warns if you have unsaved edits so you do not push a shed that is behind your machine.
 
+### A machine that already has a setup
+
+The common case is not an empty machine: it already runs the agent and has skills, settings and MCP servers of its own. `restore` is built for that. With no prior lshed state it **removes nothing** — it places what the profile lists, and anything it overwrites goes to `~/.claude/lshed/backups/<timestamp>/` first. Parts that exist only on that machine are untouched.
+
+```
+$ lshed restore default --shed ~/lshed --dry-run
+  + skills/mine
+  ~ skills/shared            # same name, different content → backed up, then replaced
+  + mcp:exa  (${EXA_API_KEY})
+  ~ settings:model
+(dry-run) 변경 없음. 배치 5, 제거 0, 백업 예정 3
+```
+
+Always run `--dry-run` first. `+` is new, `~` replaces with a backup, `-` removes with a backup. If the plan looks right, drop the flag.
+
+Then push that machine's own parts up into the shed and both machines have everything:
+
+```
+lshed add                    # lists what this machine has that the shed does not
+lshed add windows-only mcp/my-local-server
+lshed sync
+```
+
+Do not run `init` on such a machine just to look around. `init` claims what it finds as lshed-managed, so a later `restore` from your real shed would treat those parts as removable (backed up, but removed). Use `lshed scan`, which only prints. If you do it anyway, `restore` warns you before removing anything and `lshed add` is the way out.
+
 ### A new machine
 
 ```