supercov 4.24.0 → 4.24.1

package/docs/supported-suites.md

@@ -715,8 +715,11 @@ image, as `.:/workspace` in a compose file does: Supercov runs the command
 in the copy, so the mount is of the copy. It gets the run's settings with
 each path into the copy moved to where the container sees it, and the
 project's `node_modules`, which the copy's packages link to, mounted
-read-only at its own path. A mount of one directory of the project
-(`./src:/app/src`) is not the copy, and is left alone.
+read-only at its own path. The copy's `.supercov`, where the run's evidence
+is written, is mounted writable where the container sees it, so a copy
+mounted read-only (`.:/workspace:ro`) is measured as well. A mount of one
+directory of the project (`./src:/app/src`) is not the copy, and is left
+alone.
 
 The tests can run in such a container too. A command `docker exec` (or
 `docker compose exec`) starts in it, `npx playwright test` say, gets the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "supercov",
-  "version": "4.24.0",
+  "version": "4.24.1",
   "description": "Coverage, security and code quality for coding agents",
   "keywords": [
     "coverage",
@@ -122,14 +122,14 @@
     "test:windows-tls": "node scripts/windows-tls-test.mjs"
   },
   "optionalDependencies": {
-    "@supercov/cli-darwin-arm64": "4.24.0",
-    "@supercov/cli-darwin-x64": "4.24.0",
-    "@supercov/cli-linux-arm64-gnu": "4.24.0",
-    "@supercov/cli-linux-arm64-musl": "4.24.0",
-    "@supercov/cli-linux-x64-gnu": "4.24.0",
-    "@supercov/cli-linux-x64-musl": "4.24.0",
-    "@supercov/cli-win32-arm64": "4.24.0",
-    "@supercov/cli-win32-x64": "4.24.0"
+    "@supercov/cli-darwin-arm64": "4.24.1",
+    "@supercov/cli-darwin-x64": "4.24.1",
+    "@supercov/cli-linux-arm64-gnu": "4.24.1",
+    "@supercov/cli-linux-arm64-musl": "4.24.1",
+    "@supercov/cli-linux-x64-gnu": "4.24.1",
+    "@supercov/cli-linux-x64-musl": "4.24.1",
+    "@supercov/cli-win32-arm64": "4.24.1",
+    "@supercov/cli-win32-x64": "4.24.1"
   },
   "peerDependencies": {
     "@playwright/test": ">=1.55.0",

package/runtime/javascript/runtime.mjs

@@ -625,6 +625,7 @@ function flushBackgroundAppends(fs) {
 // all.
 function makeEvidenceDirectory(fs, directory) {
   const first = fs.mkdirSync(directory, { recursive: true });
+  markContainerWriting(fs);
   if (!first || typeof process === "undefined" || !process.env || process.env.SUPERCOV_CONTAINER !== "1")
     return;
   let current = first;
@@ -640,6 +641,20 @@ function makeEvidenceDirectory(fs, directory) {
     }
   }
 }
+// A container Supercov's relay measured says, once, that its evidence could
+// be written: one that never does -- a server stopped at its first probe, a
+// directory it may not write -- is named when the run ends.
+function markContainerWriting(fs) {
+  const mark = typeof process !== "undefined" && process.env ? process.env.SUPERCOV_CONTAINER_MARK : void 0;
+  if (!mark || state.containerMarked)
+    return;
+  state.containerMarked = true;
+  try {
+    fs.mkdirSync(mark.slice(0, mark.lastIndexOf("/")), { recursive: true });
+    fs.writeFileSync(mark, "");
+  } catch (e) {
+  }
+}
 function writeBackgroundLines(fs, runId, payload) {
   var _a8;
   const directory = backgroundEvidenceDirectory(runId);