vigiles 26.2.0 → 27.0.0

package/dist/test-coverage.js

@@ -189,7 +189,7 @@ function discoverSkills(basePath, ignore, layout) {
  * this source file from matching its own search — a precaution that was never
  * checked and is contradicted by the tree it lives in: the literal already appears
  * in five other files under `src/`, and the detector reads only files matching
- * `testGlobs` in the SCANNED repo, never vigiles' own sources.
+ * `include` in the SCANNED repo, never vigiles' own sources.
  */
 const LEGACY_COVERS = "vigiles:covers";
 function discoverAgents(basePath, ignore, layout) {
@@ -343,8 +343,8 @@ function coverageOf(surface, tests, globs) {
 /**
  * Split the discovered tests into the two tiers — `*.eval.<runnable-ext>` is the
  * paid real-model tier, everything else (`*.harness.*` and any user-supplied
- * `testGlobs`) is the free deterministic tier. Decided by NAME, not by glob set,
- * so a custom `testGlobs` (a promptfoo suite, a home-grown loop) still lands in a
+ * `include`) is the free deterministic tier. Decided by NAME, not by glob set,
+ * so a custom `include` (a promptfoo suite, a home-grown loop) still lands in a
  * tier instead of silently disappearing from the split. The rule itself is
  * `isEvalScript` — shared with the browser twin, and see its header for the two
  * opposite ways this has been wrong.
@@ -414,7 +414,7 @@ function findUntestedSurfaces(options = {}) {
     const basePath = options.basePath ?? process.cwd();
     const layout = options.layout ?? layout_js_2.claudeCodeLayout;
     const ignore = [...DEFAULT_IGNORE, ...(options.exclude ?? [])];
-    const globs = options.testGlobs ?? DEFAULT_TEST_GLOBS;
+    const globs = options.include ?? DEFAULT_TEST_GLOBS;
     const surfaces = [];
     if (options.skills !== false)
         surfaces.push(...discoverSkills(basePath, ignore, layout));
@@ -823,14 +823,14 @@ function formatUntestedReport(report) {
     lines.push(...coverageCaveats(report));
     // Already testing these another way (a promptfoo suite, a home-grown evals
     // file)? Two shapes are accepted, and the message names BOTH — it used to
-    // name only `testGlobs`, which does not by itself make a centralized suite
+    // name only `include`, which does not by itself make a centralized suite
     // count, so a reader who followed it exactly saw the number not move (#175.2).
     // See docs/rules/untested-skill.md.
     lines.push(`  Testing these another way (promptfoo / a home-grown eval loop)? Either ` +
         `put the file NEXT TO the surface and name it after it ` +
         `(\`<surface>/<surface>.eval.mjs\`), or — for a centralized layout — point ` +
-        `\`testGlobs\` at it USING THE \`{surface}\` placeholder, e.g. ` +
-        `\`"tests/{surface}/evals/promptfooconfig*.yaml"\`. A \`testGlobs\` entry ` +
+        `\`include\` at it USING THE \`{surface}\` placeholder, e.g. ` +
+        `\`"tests/{surface}/evals/promptfooconfig*.yaml"\`. An \`include\` entry ` +
         `WITHOUT \`{surface}\` widens what counts as a test file but never says ` +
         `which surface it covers, so it credits nothing on its own. ` +
         `See docs/rules/untested-skill.md.`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vigiles",
-  "version": "26.2.0",
+  "version": "27.0.0",
   "description": "Audit, test and measure the harness your AI agent runs on — grade your CLAUDE.md / AGENTS.md, skills, subagents and hooks, run them against a scripted model, and measure whether they actually fire.",
   "keywords": [
     "claude-code",