@activate-core/test-forge 0.17.0 → 0.18.1

package/dist/core/lint.js

@@ -16,11 +16,18 @@
  * repository, not to impose a preference.
  */
 import { spawnSync } from 'node:child_process';
+import { resolve } from 'node:path';
 import { existsSync } from 'node:fs';
 import { join, dirname } from 'node:path';
 /** Walk up from a file to the nearest package that has ESLint installed. */
 function eslintFor(file) {
-    let dir = dirname(file);
+    // Absolute throughout. The binary is spawned WITH cwd set to the package that
+    // owns it, so a relative bin path is re-resolved from there:
+    // "packages/api/node_modules/.bin/eslint" becomes
+    // "packages/api/packages/api/node_modules/.bin/eslint", the spawn fails with
+    // ENOENT, stdout is empty, and the empty JSON parses as zero problems. The
+    // gate then reported every generated file clean without ever running.
+    let dir = dirname(resolve(file));
     for (let i = 0; i < 8; i++) {
         const bin = join(dir, 'node_modules', '.bin', 'eslint');
         if (existsSync(bin))
@@ -48,7 +55,13 @@ export function lintGenerated(files) {
         if (!found)
             continue;
         const g = groups.get(found.cwd) || { bin: found.bin, files: [] };
-        g.files.push(f);
+        // ABSOLUTE, always. ESLint runs with cwd set to the package that owns it,
+        // so a path relative to the repo root ("packages/api/helpers/x.js")
+        // resolved there becomes "packages/api/packages/api/helpers/x.js" — a file
+        // that does not exist. With --no-error-on-unmatched-pattern that is not an
+        // error, it is silence: the gate reported zero problems on files it had
+        // never opened, and the lint errors it exists to stop reached CI anyway.
+        g.files.push(resolve(f));
         groups.set(found.cwd, g);
     }
     if (!groups.size) {

package/dist/core/validate.js

@@ -114,6 +114,29 @@ export function checkTestGates(content, _ext, ctx) {
             }
         }
     }
+    // F12 — "same host" is not a reason to abandon a dependency. A skip that
+    // blames the dependency for sharing a hostname with the app, without saying
+    // what else was tried, is the generator giving up on a stub it could have
+    // scoped. A service on another PORT is a different origin; one under its own
+    // PATH prefix is separable too; failing both, a predicate on the request
+    // itself usually is. Left unchecked this costs whole areas: sixty-four checks
+    // in one journey skipped on this wording alone, against a dependency sitting
+    // on a plainly different port.
+    //
+    // The rule still allows the genuine case — a dependency that truly cannot be
+    // told apart — but the reason has to show the work: name the port, the path,
+    // or the request property you checked.
+    {
+        const sameHost = /\b(?:skip|fixme)\s*\([^)]{0,400}?same\s+host(?:name)?[^)]{0,400}?\)/is;
+        const showedWork = /\b(?:port|origin|path\s*prefix|prefix|resource\s*type|header|predicate)\b/i;
+        const m = content.match(sameHost);
+        if (m && !showedWork.test(m[0])) {
+            return ('a test is skipped because the dependency "shares a host" with the app, ' +
+                'without saying what else was checked — a different port is a different ' +
+                'origin, and a path prefix or a request predicate usually separates them ' +
+                'too; scope the stub to one of those, or name the ones you ruled out');
+        }
+    }
     // F10 — selector grounding: a RUNNABLE (non-skipped) UI test must not lean
     // on a guessed selector. Unchecked, the generator invents plausible
     // data-testids that time out at runtime — the journey is never really

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@activate-core/test-forge",
-  "version": "0.17.0",
+  "version": "0.18.1",
   "description": "AI-powered QA automation. Scans a project, drafts journey docs, and generates seeded Jest/Playwright tests. Works in any project, with any AI CLI.",
   "type": "module",
   "bin": {