skalpel 4.0.39 → 4.0.40

package/eval-harness.mjs

@@ -25,6 +25,7 @@
 
 import fs from "node:fs";
 import path from "node:path";
+import { fileURLToPath } from "node:url";
 
 // ───────────────────────────── tunables (UNCALIBRATED defaults) ─────────────────────────────
 // These thresholds are NOT tuned against a human gold set unless one is supplied via --gold.
@@ -1117,9 +1118,22 @@ function main() {
   console.log("═".repeat(90));
 }
 
-const isMain =
-  process.argv[1] &&
-  path.resolve(process.argv[1]) === path.resolve(new URL(import.meta.url).pathname);
+// Robust main detection (mirrors verify-shadow.mjs / skalpel-setup.mjs): compare REAL paths via
+// realpathSync, not a hand-built path.resolve(url.pathname). On Windows, `new URL(import.meta.url)
+// .pathname` yields "/C:/Users/..." (a leading slash BEFORE the drive letter); path.resolve() on that
+// string produces "\C:\Users\..." — a different string than path.resolve(process.argv[1])'s
+// "C:\Users\...". isMain then silently evaluates false, so `node eval-harness.mjs <dir>` (the CLI's
+// entire purpose) does nothing at all on Windows: no usage, no report, no error, exit 0.
+const isMain = (() => {
+  try {
+    return (
+      Boolean(process.argv[1]) &&
+      fs.realpathSync(process.argv[1]) === fs.realpathSync(fileURLToPath(import.meta.url))
+    );
+  } catch {
+    return false;
+  }
+})();
 if (isMain) main();
 
 export { V1_onset, V2_cue, V3_repeat, FIRE_ALWAYS, FIRE_NEVER, calibrate };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "skalpel",
-  "version": "4.0.39",
+  "version": "4.0.40",
   "description": "Behavioral graph for AI-assisted coding — learns how you work and steers Claude Code + Codex in real time.",
   "type": "module",
   "bin": {

package/skalpel-statusline.mjs

@@ -139,10 +139,17 @@ function steerLabel() {
 // line (fresh + honest — the statusline never invents it, it only renders what the re-run recorded) or
 // null. Auto-clears when stale (past the TTL) so an old catch can't wallpaper the bar. GATED entirely on
 // SKALPEL_VERIFY_REVEAL: when off, this is never called and the bar is byte-identical to the baseline.
-function revealNote() {
+function revealNote(sessionId) {
   try {
     const r = JSON.parse(readFileSync(REVEAL_PATH, "utf8"));
     if (!r || typeof r.line !== "string" || !r.line.trim()) return null;
+    // SESSION SCOPING: verify-reveal.json is a single shared path across every concurrent Claude Code
+    // session (multiple tabs/worktrees). Without this check, this pane would show — and misattribute to
+    // "your agent" — a catch that actually came from a DIFFERENT session's transcript. Only skip when
+    // BOTH sides know their session and they disagree; an unknown session on either side stays permissive.
+    // NOT deleted here (unlike the stale-TTL branch below) — it may still be the right reveal for whichever
+    // session actually owns it.
+    if (r.session && sessionId && r.session !== sessionId) return null;
     const age = Date.now() - Date.parse(r.ts);
     if (!Number.isFinite(age) || age > REVEAL_TTL_MS) {
       try {
@@ -361,7 +368,7 @@ function main() {
   // SKALPEL_VERIFY_REVEAL — when off (the default) this branch never runs and the bar is byte-identical to
   // the always-on baseline below.
   if (revealEnabled(process.env)) {
-    const reveal = revealNote();
+    const reveal = revealNote(payload.session_id);
     if (reveal) {
       process.stdout.write(`${BOLD}${reveal}${RESET}`);
       return;

package/verify-shadow.mjs

@@ -877,9 +877,23 @@ function writeReveal(row) {
   }
 }
 
-// clearReveal() — retract a prior catch (the agent actually fixed it: a later proof re-run PASSED).
-function clearReveal() {
+// clearReveal(session) — retract a prior catch (the agent actually fixed it: a later proof re-run
+// PASSED). SESSION-SCOPED: verify-reveal.json is a single shared path under ~/.skalpel, read/written by
+// every concurrent Claude Code session (multiple tabs/worktrees is a normal prosumer workflow). Without
+// this guard, session B's PASSING proof would silently wipe out session A's still-unresolved GENUINE_FAIL
+// reveal — the user in session A would never see the catch they hadn't gotten to yet, and session B gets
+// credit for "fixing" something it never touched. Only refuse to clear when BOTH sides know their session
+// and they disagree; an unknown session on either side stays permissive (matches prior single-session
+// behavior, and a manual/CLI-driven re-run with no session context still self-heals as before).
+function clearReveal(session) {
   try {
+    let existing = null;
+    try {
+      existing = JSON.parse(readFileSync(REVEAL_PATH, "utf8"));
+    } catch {
+      /* no reveal file, or unreadable — nothing to protect; fall through to the (idempotent) remove */
+    }
+    if (existing && existing.session && session && existing.session !== session) return; // not ours
     rmSync(REVEAL_PATH, { force: true });
   } catch {
     /* stale reveal self-expires via the statusline's TTL anyway */
@@ -946,7 +960,7 @@ function maybeSurfaceReveal(row) {
         session: row.session || null,
       });
     } else if (isPass) {
-      clearReveal(); // resolved — don't wallpaper a catch the agent already fixed
+      clearReveal(row.session || null); // resolved — don't wallpaper a catch the agent already fixed
       // The green VERDICT stamp is #612's TEST-pass path only: its line ("re-ran `<proof>`, exit 0") is a
       // real test re-run receipt. A ship SHIP_OK (read-only probe came back positive) has no re-run and no
       // proof_command, so it must NOT borrow that wording — it only clears any prior catch (as #611 did).