@bglocation/tune-context 2.0.0 → 2.0.1

package/.claude-plugin/marketplace.json

@@ -1,6 +1,6 @@
 {
   "name": "bglocation",
-  "description": "Context-engineering tooling for Claude Code from bglocation — token-saving doctrine, configurators and semantic-search wiring.",
+  "description": "Context-engineering tooling for Claude Code from bglocation \u2014 token-saving doctrine, configurators and semantic-search wiring.",
   "owner": {
     "name": "Szymon Walczak",
     "url": "https://bglocation.dev"
@@ -10,7 +10,7 @@
       "name": "tune-context",
       "source": "./",
       "description": "Context-efficiency configurator for Claude Code: doctrine skills (token-efficiency, caveman, cdd, phase-workflow) plus a tune-context configurator that scaffolds a lean CLAUDE.md, subagents, settings and hooks.",
-      "version": "2.0.0",
+      "version": "2.0.1",
       "author": {
         "name": "Szymon Walczak",
         "url": "https://bglocation.dev"

package/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "tune-context",
   "displayName": "tune-context",
   "description": "Context-efficiency configurator for Claude Code: doctrine skills (token-efficiency, caveman, cdd, phase-workflow) plus a tune-context configurator that scaffolds a lean CLAUDE.md, subagents, settings and hooks.",
-  "version": "2.0.0",
+  "version": "2.0.1",
   "author": {
     "name": "Szymon Walczak",
     "url": "https://bglocation.dev"

package/CHANGELOG.md

@@ -5,6 +5,46 @@ All notable changes to `@bglocation/tune-context` are documented here.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.0.1] — 2026-07-26
+
+### Fixed
+
+- **The npm-installed CLI did nothing at all in 2.0.0.** `npm i -g` puts the
+  `bin` entry on PATH as a symlink named `tune-context`, with no extension, but
+  2.0.0's entry-point guard tested `process.argv[1].endsWith('tune-context.mjs')`.
+  That is false for the symlink, so `main()` never ran: every command —
+  `init`, `--version`, `--help` — exited 0 without printing a byte or touching a
+  file. Now compares resolved real paths, which holds for the npm symlink, a
+  direct `.mjs` invocation, the extensionless `bin/tune-context` wrapper (still
+  exactly one run, not two) and `import` from a test.
+- Only the npm channel was affected. Plugin installs call `bin/tune-context`,
+  which invokes `main()` itself, and the hooks are always registered by literal
+  path — both kept working.
+
+### Testing
+
+- The suite spawned `.../bin/tune-context.mjs` everywhere, which is the one shape
+  no user ever runs; that is why 119 green tests said nothing about a completely
+  dead CLI. Added a test that installs the binary the way npm does — through an
+  extensionless symlink — and asserts a silent exit 0 is a failure.
+
+### Upgrading from 2.0.0 (npm channel)
+
+Upgrading is not enough on its own. If you ran `tune-context init` under 2.0.0
+it exited 0 and looked like it worked, but **nothing was installed** — so
+`~/.claude/hooks/context-reminder.mjs` is missing and the `UserPromptSubmit`
+hook was never registered. Re-run it after upgrading:
+
+```bash
+npm i -g @bglocation/tune-context@2.0.1
+tune-context --version    # must print 2.0.1 — silence means the upgrade did not take
+tune-context init
+```
+
+The `init` is idempotent and additive: it never removes a hook or permission
+entry, and never touches content outside the managed blocks. Plugin-only
+installs were unaffected and need nothing.
+
 ## [2.0.0] — 2026-07-25
 
 Three hardening epics' worth of work plus the first new feature since 1.0: a

package/bin/tune-context.mjs

@@ -16,7 +16,7 @@
 // "No model in the loop" is the feature here, not a gap — but the gap has to be
 // stated, or a CLI user cannot know what they did not get. Run the skill
 // (/tune-context) for the full pass.
-import { readFileSync } from 'node:fs';
+import { readFileSync, realpathSync } from 'node:fs';
 import { dirname, join, resolve } from 'node:path';
 import { fileURLToPath } from 'node:url';
 import { claudeDirs, detectExistingConfig, detectMcpServers, detectRejectedMcpServers, detectStack } from '../cli/detect.mjs';
@@ -173,11 +173,37 @@ export function main() {
   }
 }
 
-// Guarded so importing this file for parseArgs/main (tests, or the
-// extensionless bin/tune-context wrapper) never runs the CLI as a side
-// effect of the import — only direct invocation of THIS file does. The
-// wrapper has a different argv[1] (its own path), so it calls main()
-// explicitly instead of relying on this check.
-if (process.argv[1] && process.argv[1].endsWith('tune-context.mjs')) {
+/**
+ * True only when THIS file is the process entry point, so importing it for
+ * parseArgs/main (tests, or the extensionless bin/tune-context wrapper) never
+ * runs the CLI as a side effect of the import.
+ *
+ * Deliberately NOT a filename-suffix test on argv[1]. npm installs the
+ * package.json `bin` entry as a symlink named `tune-context` — no extension —
+ * so `argv[1].endsWith('tune-context.mjs')` was false for every real npm-channel
+ * invocation: main() never ran and the CLI exited 0 in total silence. That
+ * shipped in 2.0.0 (see the symlink test in test/bin-tune-context.test.mjs);
+ * the whole suite missed it because tests and smoke:init both spawn the full
+ * `.../bin/tune-context.mjs` path, which is the one shape a user never uses.
+ *
+ * Comparing resolved real paths holds for all four shapes: direct `.mjs`
+ * invocation, the npm symlink (resolves THROUGH the link to this file), the
+ * extensionless wrapper (a different real path, so this stays false and the
+ * wrapper's own main() call is the single entry — no double run), and `import`
+ * from a test (argv[1] is the test runner). realpathSync on both sides also
+ * survives a symlinked package dir, as `npm link` and nvm both produce.
+ */
+function isEntryPoint() {
+  if (!process.argv[1]) return false;
+  try {
+    return realpathSync(process.argv[1]) === realpathSync(fileURLToPath(import.meta.url));
+  } catch {
+    // argv[1] can name something unresolvable (deleted, or a bare `-`); a CLI
+    // that cannot identify its own entry point must stay silent, not crash.
+    return false;
+  }
+}
+
+if (isEntryPoint()) {
   main();
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@bglocation/tune-context",
-  "version": "2.0.0",
-  "description": "Context-efficiency configurator for Claude Code — token-saving doctrine packaged as skills, plus a tune-context configurator that scaffolds a lean CLAUDE.md, doctrine skills, subagents, settings, hooks and MCP wiring.",
+  "version": "2.0.1",
+  "description": "Context-efficiency configurator for Claude Code \u2014 token-saving doctrine packaged as skills, plus a tune-context configurator that scaffolds a lean CLAUDE.md, doctrine skills, subagents, settings, hooks and MCP wiring.",
   "type": "module",
   "license": "MIT",
   "author": "Szymon Walczak",