shadowjoin 0.3.1 → 0.3.2

package/README.md

@@ -17,11 +17,11 @@ npx shadowjoin scan \
   --right crm_export.csv  --right-key account_name
 ```
 
-[![shadowjoin measuring a country-name join: 205 of 249 matched exactly, which looks fine, while five real matches were being dropped including Vietnam, spelled Viet Nam by the UN](assets/brag.gif)](https://github.com/harsh-chandak/shadowjoin/blob/main/assets/brag.mp4)
+[![shadowjoin measuring a country-name join: 205 of 249 matched exactly, which looks fine, while five real matches were being dropped including Vietnam, spelled Viet Nam by the UN](assets/brag.gif)](https://github.com/harsh-chandak/shadowjoin/blob/main/assets/brag.gif)
 
 <sub>Fourteen seconds, no sound. Every figure in it is verbatim CLI output from
 the committed example below — [higher-resolution
-version](https://github.com/harsh-chandak/shadowjoin/blob/main/assets/brag.mp4).</sub>
+version](https://github.com/harsh-chandak/shadowjoin/blob/main/assets/brag.gif).</sub>
 
 The progress output above is real: shadowjoin shows what it is doing while it
 works. All of it is suppressed automatically when stdout is not a terminal, so

package/dist/mcp.js

@@ -41,7 +41,12 @@ async function loadSdk() {
         process.exit(1);
     }
 }
-const CONFIG_PATH = resolve(process.env.SHADOWJOIN_CONFIG ?? "shadowjoin.config.json");
+// `||`, not `??`: the Claude Code plugin maps this to a user setting, and an
+// unset setting arrives as an empty string rather than as undefined. `??`
+// let "" through, and resolve("") is the working DIRECTORY — so the default
+// install read a directory as its config and told the user to create a file
+// at a path that was already a folder.
+const CONFIG_PATH = resolve(process.env.SHADOWJOIN_CONFIG?.trim() || "shadowjoin.config.json");
 async function loadConfig() {
     try {
         const parsed = JSON.parse(await readFile(CONFIG_PATH, "utf8"));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "shadowjoin",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "description": "Measure the matches your exact join is silently dropping. Runs a shadow matcher alongside your real join key and reports a verified floor on lost matches, plus the normalization rule that would recover each one.",
   "keywords": [
     "entity-resolution",
@@ -45,7 +45,7 @@
   "scripts": {
     "build": "tsc",
     "test": "node --test test/*.test.js",
-    "prepublishOnly": "npm run build"
+    "prepublishOnly": "node scripts/prepublish-guard.mjs && npm run build && npm test"
   },
   "peerDependencies": {
     "@modelcontextprotocol/sdk": ">=1",