@theglitchking/babel-fish 2.4.1 → 2.4.3

package/.claude/project-map/test_generate.py

@@ -30,7 +30,12 @@ def load_generate(project_root: Path):
         spec.loader.exec_module(mod)
     finally:
         sys.argv = argv
-    mod.PROJECT_ROOT = project_root
+    # configure_paths(), not `mod.PROJECT_ROOT = ...`: generate.py binds MAP_DIR,
+    # SECTIONS_DIR, CHECKSUMS, LEARNED_VOC and GLOSSARY at import time from
+    # __file__, and rebinds them only here. Setting PROJECT_ROOT alone left every
+    # output path aimed at the real repo, so the suite overwrote its own
+    # glossary.json with fixture data and still passed (#18).
+    mod.configure_paths(project_root)
     return mod
 
 
@@ -232,7 +237,11 @@ def test_glossary_survives_foreign_project_root(g):
     PROJECT_ROOT when --project-root points elsewhere. That combination raised
     ValueError from relative_to()."""
     import json
-    g.write_glossary([], g.load_stack())  # PROJECT_ROOT is the temp fixture here
+    # Recreate the mismatch explicitly. It used to arrive for free because the
+    # loader left SECTIONS_DIR pointing at the script dir — the same leak that
+    # let this test write into the real repo (#18).
+    g.SECTIONS_DIR = HERE / "sections"
+    g.write_glossary([], g.load_stack())
     data = json.loads(g.GLOSSARY.read_text())
     assert data["source"].endswith("01-vocabulary.md"), data["source"]
 

package/.claude/project-map/test_mine_sessions.py

@@ -28,7 +28,10 @@ def load_miner(project_root: Path, cursor_dir: Path):
         spec.loader.exec_module(mod)
     finally:
         sys.argv = argv
-    mod.PROJECT_ROOT = project_root
+    # configure_paths(), not `mod.PROJECT_ROOT = ...` — see the same note in
+    # test_generate.py (#18). LEARNED_VOC is bound at import time from __file__,
+    # so assigning PROJECT_ROOT alone leaves it aimed at the real repo.
+    mod.configure_paths(project_root)
     mod.MINE_CURSOR = cursor_dir / ".mine-cursor.json"
     return mod
 

package/.claude-plugin/marketplace.json

@@ -6,13 +6,13 @@
   },
   "metadata": {
     "description": "Official marketplace for babel-fish - Codebase introspection and vocabulary translation for AI coding assistants",
-    "version": "2.4.1"
+    "version": "2.4.3"
   },
   "plugins": [
     {
       "name": "babel-fish",
       "description": "Auto-generates a project map, vocabulary translation layer, and developer skill for any codebase. Introspects routes, models, services, features, infrastructure, and session history to give Claude instant full-stack context. Self-updates via pre-commit hook.",
-      "version": "2.4.1",
+      "version": "2.4.3",
       "author": {
         "name": "TheGlitchKing"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "babel-fish",
   "description": "Auto-generates a project map, vocabulary translation layer, and developer skill for any codebase. Introspects routes, models, services, features, infrastructure, and session history to give Claude instant full-stack context. Self-updates via pre-commit hook.",
-  "version": "2.4.1",
+  "version": "2.4.3",
   "author": {
     "name": "TheGlitchKing",
     "email": "theglitchking@users.noreply.github.com"

package/CHANGELOG.md

@@ -2,6 +2,62 @@
 
 All notable changes to this project will be documented in this file.
 
+## [2.4.3] - 2026-09-05
+
+### Fixed
+
+- **`npm test` overwrote the map it was testing, and still reported every test
+  passing** ([#18](https://github.com/TheGlitchKing/babel-fish/issues/18)). A run
+  rewrote the working tree's `.claude/project-map/glossary.json` with fixture
+  data — 10 entries down to 1 — and printed a clean pass. Caught only by
+  diffing before a commit during the 2.4.2 release.
+
+  `generate.py` and `mine-sessions.py` bind `MAP_DIR`, `SECTIONS_DIR`,
+  `CHECKSUMS`, `LEARNED_VOC` and `GLOSSARY` at import time from `__file__`, and
+  rebind them only inside `configure_paths()`. Both test loaders assigned
+  `mod.PROJECT_ROOT` and stopped there, so every output path stayed aimed at the
+  real repo while the tests believed they were in a temp fixture; whichever test
+  called `write_glossary()` last won. This is the [#15](https://github.com/TheGlitchKing/babel-fish/issues/15)
+  defect class — writes escaping to the script's own directory — surviving in
+  the harness after being fixed in the scripts themselves.
+
+  Both loaders now call `configure_paths(fixture_root)`.
+  `test_glossary_survives_foreign_project_root` depended on the leak (it needs
+  `SECTIONS_DIR` outside `PROJECT_ROOT`, which used to arrive for free) and now
+  recreates that mismatch explicitly, so it still covers the `ValueError` from
+  `relative_to()` without writing outside its fixture — verified by mutation:
+  deleting the `try`/`except` in `_relative_source()` fails that test and only
+  that one. `test_grader.py` is deliberately untouched; its loader assigns a map
+  dir rather than a project root.
+
+  38 tests pass across the three suites, and a full run now leaves the tree
+  clean.
+
+## [2.4.2] - 2026-09-05
+
+### Fixed
+
+- **`update` exited 0 without updating anything**
+  ([#17](https://github.com/TheGlitchKing/babel-fish/issues/17)). The defect was
+  in `@theglitchking/claude-plugin-runtime`, which resolved installation state
+  only from `<cwd>/node_modules` and `CLAUDE_PLUGIN_ROOT`. A marketplace-plugin
+  install — the documented, supported way to install babel-fish — matched
+  neither, so `babel-fish update` printed `Current: (not installed)` and
+  `Now: (not installed)`, ran an `npm update` that touched nothing, and reported
+  success. A stale plugin stayed stale and nobody found out.
+
+  `status` shared the blind spot, and contradicted itself in the process:
+  `installed: (not installed)` against a CLI whose `--version` printed 2.4.1,
+  and `hook: not in .claude/settings.json` while the SessionStart hook was
+  demonstrably firing — a marketplace plugin registers its hook through its own
+  `hooks/hooks.json` and needs nothing in project settings.
+
+  Fixed upstream in runtime 0.1.1, which this release requires (`^0.1.1`, raised
+  from `^0.1.0` so the range itself forces re-resolution past a lock pinned to
+  0.1.0). `update` now exits non-zero and names every path it checked; when the
+  copy is plugin-installed it says npm cannot update that and points at
+  `/plugin`. Nothing in babel-fish's own source changed.
+
 ## [2.4.1] - 2026-09-04
 
 ### Fixed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theglitchking/babel-fish",
-  "version": "2.4.1",
+  "version": "2.4.3",
   "description": "Gives your AI coding assistant instant, accurate knowledge of every route, model, service, feature, and infrastructure element in your codebase.",
   "type": "module",
   "bin": {
@@ -59,7 +59,7 @@
     "node": ">=20.0.0"
   },
   "dependencies": {
-    "@theglitchking/claude-plugin-runtime": "^0.1.0",
+    "@theglitchking/claude-plugin-runtime": "^0.1.1",
     "commander": "^14.0.0"
   }
 }