llm-wiki-kit 0.1.8 → 0.1.9

package/README.md

@@ -94,7 +94,7 @@ Most users should not need these during daily Claude Code/Codex work. They exist
 
 `llm-wiki update --check [--to <version-or-tag>]` is the online update check. It compares the installed package version with the npm registry target without changing files, and reports an available update only when the target version is newer than the installed version.
 
-`llm-wiki update` upgrades the global npm package, reinstalls the hook entries, and reapplies safe managed template updates across known project roots. Use `--current-only` when you intentionally want to update only the supplied workspace. Existing wiki content is not overwritten.
+`llm-wiki update` upgrades the global npm package when npm has a newer target, reinstalls the hook entries, and reapplies safe managed template updates across known project roots. If the installed runtime already satisfies the registry target, it skips `npm install -g` and still runs post-update maintenance. Use `--current-only` when you intentionally want to update only the supplied workspace. Existing wiki content is not overwritten.
 
 `llm-wiki post-update --workspace <project>` reapplies the current runtime's hook entries and safe managed template updates without running `npm install -g`. Use `post-update --all --workspace <search-root>` to reapply templates across discovered project roots.
 

package/docs/operations.md

@@ -103,7 +103,8 @@ llm-wiki consolidate --workspace /path/to/project
 
 `update` applies changes explicitly only when the user runs it:
 
-- runs `npm install -g llm-wiki-kit@<target>`
+- runs `npm install -g llm-wiki-kit@<target>` only when the registry target is newer than the installed runtime
+- skips npm installation when the installed runtime already satisfies the target, then still runs post-update maintenance
 - restarts into the updated binary for `post-update`
 - reinstalls hook entries without duplicating them
 - patches only managed project files across known or discovered project roots

package/docs/troubleshooting.md

@@ -102,6 +102,8 @@ hash -r
 llm-wiki status --workspace /path/to/project
 ```
 
+After a manual `sudo npm install -g llm-wiki-kit@latest`, a normal-user `llm-wiki update --workspace <search-root>` can be used to reapply hooks and managed templates. When the installed runtime already matches the registry target, `update` skips the npm install step and runs only post-update maintenance.
+
 If `readlink -f "$(command -v llm-wiki)"` points at a repository checkout such as `/mnt/d/dev_proj/llm-wiki-kit/bin/llm-wiki.js`, `npm install -g` is not updating that checkout. Either switch the shim to the npm package as above, or update the checkout itself with `git pull` and run it intentionally as source.
 
 Running `llm-wiki post-update --workspace /path/to/project` or `llm-wiki install --workspace /path/to/project --profile standard` also reconnects hook entries to the current runtime. `install` uses an npm/nvm global command when it already resolves to the current runtime, removes an older kit-managed local shim when it shadows that command, and creates a local shim only when no `PATH` command points at the current runtime.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "llm-wiki-kit",
-  "version": "0.1.8",
+  "version": "0.1.9",
   "description": "Hook-first living LLM Wiki runtime for Codex and Claude Code.",
   "type": "module",
   "files": [

package/src/update.js

@@ -192,9 +192,16 @@ export async function update(options = {}) {
   }
 
   const target = options.to || 'latest';
-  const installResult = runCommand(npmCommand(), ['install', '-g', `${packageName()}@${target}`], {
-    timeout: options.timeout || 120000,
-  });
+  const shouldRunNpmInstall = check.updateAvailable;
+  const installResult = shouldRunNpmInstall
+    ? runCommand(npmCommand(), ['install', '-g', `${packageName()}@${target}`], {
+      timeout: options.timeout || 120000,
+    })
+    : {
+      status: 0,
+      stdout: `skipped; installed ${check.installedVersion} is already >= target ${check.latestVersion}`,
+      stderr: '',
+    };
   assertCommandOk(installResult, 'npm install -g');
 
   const postArgs = [binCommand(), 'post-update', '--workspace', workspace, '--json'];
@@ -216,6 +223,7 @@ export async function update(options = {}) {
     target,
     scope: shouldUpdateAllProjects(options) ? 'all' : 'current',
     npmInstall: {
+      skipped: !shouldRunNpmInstall,
       stdout: installResult.stdout.trim(),
       stderr: installResult.stderr.trim(),
     },