@hublo/sentinel 1.4.0-alpha.31 → 1.4.0-alpha.32

package/README.md

@@ -24,6 +24,7 @@ A large monorepo accumulates:
 - **One source of truth for config** — every project just `extends @hublo/sentinel/...`; the actual rules live in one versioned place. Change a rule once, everyone gets it on the next version bump.
 - **One source of truth for tooling dependencies** — a project depends on `@hublo/sentinel`, not on a scattered pile of eslint / vitest / plugin devDeps. Bump one version and the whole toolchain moves, atomically, tested in isolation first.
 - **`--init` sets a module up** — the one command generates the stubs the first time (**adopt**), regenerates them after a change like a runner swap (**refresh**), and applies the workspace prep the module needs. Run it module by module to roll out gradually. (`--migrate`, for changing an already-initialized setup, is a reserved future verb.)
+- **`--validate` proves the move did not change anything** — a verb of its own, because what separates it from `--init` is what SURVIVES the run: `--init` and `--migrate` write state that REMAINS, `--validate` may instrument the module it is proving provided nothing it writes stays. Run before a migration it records what the module does today; run after, it compares and refuses a run that lost a test or invented one. It composes with every type, and answers "not available yet" for the ones without a proof rather than calling a valid command wrong.
 - **Move one module at a time** — installed per module, so you adopt at your pace; a module can adopt sentinel while its neighbour keeps the old setup. No big-bang.
 - **Swap tools without touching projects** — change eslint → biome (or benchmark them) in one place; `--init` regenerates the stubs.
 - **No silent drift** — the guard keeps every project's config converged on the source of truth.

package/dist/bin/sentinel.js

@@ -15,10 +15,10 @@ import {
   palette,
   registerAdapters,
   resolve
-} from "../chunk-QYIF3HXC.js";
+} from "../chunk-SPW4KIQX.js";
 import {
   resolveContext
-} from "../chunk-XM65P73B.js";
+} from "../chunk-ORESQJAU.js";
 import "../chunk-O7REVMOC.js";
 import {
   ensureWorkspacePrep,
@@ -144,7 +144,7 @@ async function runValidate(ctx) {
     );
   }
   if (!ctx.targets.includes("test")) return 1;
-  const { validateModuleTests } = await import("../validate-YRLGMILJ.js");
+  const { validateModuleTests } = await import("../validate-5GABSOYH.js");
   const outcomes = modules.flatMap(
     (module) => validateModuleTests(module.name, module.root)
   );

package/dist/{chunk-XM65P73B.js → chunk-ORESQJAU.js}

@@ -1295,6 +1295,20 @@ function assertedMockedClass(source, node) {
   if (object === void 0) return false;
   return /\bMockedClass\b/.test(source.slice(object.start, object.end));
 }
+function classValuedProperties(factories) {
+  const found = [];
+  for (const factory of factories) {
+    walk(factory, (node) => {
+      if (node.type !== "Property" && node.type !== "ObjectProperty") return;
+      const key = node.key;
+      const name = key?.type === "Identifier" ? key.name : key?.type === "StringLiteral" || key?.type === "Literal" ? String(key.value) : void 0;
+      if (name === void 0 || !/^[A-Z]/.test(name)) return;
+      const value = node.value;
+      if (value !== void 0) found.push(value);
+    });
+  }
+  return found;
+}
 function readsThis(node) {
   let found = false;
   walk(node, (inner) => {
@@ -1307,7 +1321,7 @@ function rewriteConstructibleMocks(source, program, factories) {
   const refusals = [];
   let rewritten = 0;
   const seen = /* @__PURE__ */ new Set();
-  const subtrees = [...factories];
+  const subtrees = [...classValuedProperties(factories)];
   walk(program, (node) => {
     if (assertedMockedClass(source, node)) subtrees.push(node);
   });

package/dist/{chunk-QYIF3HXC.js → chunk-SPW4KIQX.js}

@@ -27,7 +27,7 @@ import {
   selfCommand,
   splitToolArgs,
   walk
-} from "./chunk-XM65P73B.js";
+} from "./chunk-ORESQJAU.js";
 import {
   DEFAULT_MAX_DIAGNOSTICS,
   findWorkspaceRoot,

package/dist/index.js

@@ -6,10 +6,10 @@ import {
   registerAdapters,
   resolve,
   setDefaultRunner
-} from "./chunk-QYIF3HXC.js";
+} from "./chunk-SPW4KIQX.js";
 import {
   BaseAdapter
-} from "./chunk-XM65P73B.js";
+} from "./chunk-ORESQJAU.js";
 import "./chunk-O7REVMOC.js";
 import "./chunk-NW6UHNYX.js";
 export {

package/dist/{validate-YRLGMILJ.js → validate-5GABSOYH.js}

@@ -7,7 +7,7 @@ import {
   readTestAdoption,
   resolveVitest,
   suiteOf
-} from "./chunk-XM65P73B.js";
+} from "./chunk-ORESQJAU.js";
 import "./chunk-O7REVMOC.js";
 import "./chunk-NW6UHNYX.js";
 

package/docs/test-adoption.md

@@ -10,6 +10,7 @@ that decided a design choice say which choice.
 - [The one line that makes a per-module migration possible](#the-one-line-that-makes-a-per-module-migration-possible)
 - [What `--init --test` rewrites, and what it refuses](#what---init---test-rewrites-and-what-it-refuses)
 - [Nest services](#nest-services)
+- [The two DOM matchers, which a react module gets without asking](#the-two-dom-matchers-which-a-react-module-gets-without-asking)
 - [The check that decides whether you are done](#the-check-that-decides-whether-you-are-done)
 
 ## What the ground actually looks like
@@ -292,16 +293,36 @@ member NAMES, which `any` gave up too. Applied only when the SAME file mocks tha
 ## The check that decides whether you are done
 
 Not "the suite is green". **The suite runs the same tests as before**. You do not have to arrange
-that comparison; the two commands do it between them:
+that comparison; `--validate` does it, on either side of the migration:
 
 ```console
-$ sentinel --init --test    # runs jest ONCE first, records every test name, then migrates
-$ pnpm install              # the module's dependencies changed
-$ sentinel --run --test     # runs vitest, compares against that recording, then spends it
+$ sentinel --validate --test   # on the JEST state: records every passing test name
+$ sentinel --init --test       # migrates
+$ pnpm install                 # the module's dependencies changed
+$ sentinel --validate --test   # runs vitest, compares against that recording, then spends it
 ```
 
 A codemod touching thousands of files cannot be reviewed by hand. This comparison is the review.
 
+⚠️ **The first command comes first, and the tool enforces it.** Start with `--init` and the jest
+config is already gone, so there is nothing left to record and nothing to compare against:
+
+```console
+✗ recruitment — already migrated, and no reference was recorded before it was, so there is
+  nothing to compare against. A proof has to be started BEFORE the migration:
+  `sentinel --validate --test` on the jest state, then `--init --test`, then this again.
+```
+
+### Why the proof is its own verb
+
+Because of what SURVIVES a run. `--init` and `--migrate` write state that stays, which is their
+whole purpose and why they are strict about what they touch. `--validate` may instrument the module
+it is proving, provided nothing it writes remains. Those are different contracts, so they are
+different verbs, and the proof can grow without touching a migration that is already proven.
+
+It answers every type, too: `sentinel --validate --lint` is a well-formed command, so it says "not
+available yet" rather than calling your sentence wrong.
+
 ### Why it cannot be one command
 
 The reference only exists BEFORE the migration, and the thing that produces it, the jest config, is
@@ -321,7 +342,7 @@ shorter.
 So the gate refuses a run that lost a name or invented one, and says which:
 
 ```console
-$ sentinel --run --test
+$ sentinel --validate --test
   1 test(s) no longer exist: useHublerNetworkProfilesQuery builds the URL with employment
   statuses only. (reference: jest.config.ts, 2026-09-23T21:10:00.000Z) The reference is KEPT
   until a run passes it, so this does not go green by running again. Fix the suite and re-run,
@@ -356,6 +377,7 @@ have read that improvement as a regression.
 ```console
 $ nx run <module>:typecheck            # BEFORE, and write that down too
 $ sentinel --init --test
+$ pnpm install
 $ nx run <module>:typecheck            # after
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hublo/sentinel",
-  "version": "1.4.0-alpha.31",
+  "version": "1.4.0-alpha.32",
   "description": "One CLI that guards code health across Hublo repos: shared lint/typescript/build/test presets, static & dynamic analysis, and architecture checks.",
   "type": "module",
   "license": "MIT",