@videlic/connect 0.1.2 → 0.1.7

package/install.mjs

@@ -71,6 +71,12 @@ ok("Key valid");
 const here = dirname(fileURLToPath(import.meta.url));
 const hookDest = join(claudeDir, "videlic-hook.mjs");
 copyFileSync(join(here, "hook.mjs"), hookDest);
+// The hook imports this one at the moment it collects evidence, by a RELATIVE
+// path, so the two must land in the same directory or the import throws — in a
+// detached process, where the only sign would be a line in the log. Copied
+// second and unconditionally: a machine left with a new hook beside an old
+// collector is the one shape neither file can detect.
+copyFileSync(join(here, "evidence.mjs"), join(claudeDir, "evidence.mjs"));
 
 const configPath = join(claudeDir, "videlic.json");
 writeFileSync(

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@videlic/connect",
-  "version": "0.1.2",
-  "description": "Connect your coding agent to Videlic \u2014 installs a Stop hook that sends each finished session for review. Works on macOS, Windows, and Linux.",
+  "version": "0.1.7",
+  "description": "Connect your coding agent to Videlic — installs a Stop hook that sends each finished session for review. Works on macOS, Windows, and Linux.",
   "type": "module",
   "bin": {
     "connect": "install.mjs"
@@ -9,8 +9,13 @@
   "files": [
     "install.mjs",
     "hook.mjs",
+    "evidence.mjs",
+    "evidence.d.mts",
     "README.md"
   ],
+  "scripts": {
+    "test": "vitest"
+  },
   "engines": {
     "node": ">=18"
   },
@@ -18,5 +23,8 @@
   "homepage": "https://videlic.dev",
   "publishConfig": {
     "access": "public"
+  },
+  "devDependencies": {
+    "vitest": "^3.2.4"
   }
 }