scip-query 0.19.3 → 0.19.4

package/docs/architecture-coherence-vision.md

@@ -87,6 +87,35 @@ row for a boundary that may depend on nothing. `requireAcyclic` independently
 forbids multi-boundary strongly connected components. A project should enable
 both only after the observed graph has been classified and repaired.
 
+`requireResolvedBoundaries` closes the gap those two leave open. Same-boundary
+dependencies are always allowed, so every edge inside a boundary is discarded
+before `requireAcyclic` runs — which means a boundary coarse enough to contain
+both sides of a cycle passes the check while saying nothing about the code
+inside it. The rule quotients each boundary by its sub-directories and requires
+that quotient to be acyclic too, so "no cycles" keeps its meaning as boundaries
+grow. It reports the narrowest internal edge as the inspection point, because a
+hidden cycle is usually one import against a dominant direction rather than a
+tangle.
+
+Four narrower rules close the remaining holes. `requireMinimalPolicy` rejects a
+declared allowance no edge uses, because `requireCompletePolicy` checks only
+that a row exists and a stale row widens the policy silently.
+`maxBoundaryFanOut` and global `maxBoundaryFiles` bound growth, since coarseness
+was otherwise caught only when it hid a cycle. A boundary-specific `maxFiles`
+overrides the global file ceiling only for that reviewed responsibility.
+`testPaths` brings test files back
+under enforcement — they are excluded from the compiler project and so from the
+index, which put them outside every rule — judging each test against the
+boundary of the code it covers, while still allowing it to reach anything that
+subject transitively reaches or that reaches the subject. And a boundary may set
+`subUnits: "file"` when its members form layers inside one directory.
+
+The failure it prevents is specific: this repository's own configuration
+declared 14 boundaries with `requireAcyclic: true` and reported zero cycles,
+while six of those boundaries — holding 85% of all files — each contained an
+internal cycle. The clean result was an artifact of granularity, not a property
+of the code.
+
 ## What the Analyzer Should Report
 
 The report should preserve both policy truth and graph evidence:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "scip-query",
-  "version": "0.19.3",
+  "version": "0.19.4",
   "description": "Evidence and verification for AI coding agents: map code, reuse concepts, finish migrations, and gate diffs.",
   "type": "module",
   "main": "dist/index.js",
@@ -324,7 +324,7 @@
     "bench:native-symbol-leaf": "node scripts/bench-native-symbol-leaf.mjs",
     "calibrate": "node scripts/accuracy-calibration.mjs",
     "docs:commands": "vite-node scripts/render-command-reference.ts --write",
-    "prepublishOnly": "npm run publish:scip-windows && npm run build",
+    "prepublishOnly": "vite-node scripts/publish-scip-windows.ts && npm run build",
     "postinstall": "node dist/postinstall.js || true",
     "publish:scip-windows": "vite-node scripts/publish-scip-windows.ts"
   },