@hublo/sentinel 1.5.0-alpha.33 → 1.5.0-alpha.34

package/dist/bin/sentinel.js

@@ -15,7 +15,7 @@ import {
   palette,
   registerAdapters,
   resolve
-} from "../chunk-XQRL555B.js";
+} from "../chunk-LCQZGHYL.js";
 import {
   resolveContext
 } from "../chunk-ZFNBW6S3.js";

package/dist/{chunk-XQRL555B.js → chunk-LCQZGHYL.js}

@@ -4824,7 +4824,17 @@ function findBuildOutput(cwd) {
   const builds = typeof pkg.scripts?.["build"] === "string" || pkg.nx?.targets?.["build"] !== void 0;
   const declaresOutputs = Array.isArray(pkg.nx?.targets?.["build"]?.["outputs"]);
   return {
-    reason: builds ? `this module declares a build and wrote no entry manifest, so ${declaresOutputs ? "build it before measuring" : "declare that build's outputs on its nx target the way apps/front/career does"}. A build target with no declared \`outputs\` is still cached, and on a cache hit nx reports the task successful, restores no file and leaves the directory empty, so every job that reads the build sees nothing. Measured on this monorepo: 5 of the 48 projects with a build target are in that state.` : "this module declares no build, so it writes no entry manifest and there is nothing to measure here. A component library and a back-end service are in that case by construction, and no action follows.",
+    reason: builds ? (declaresOutputs ? "nothing is built here, so build this module before measuring" : "the build wrote no files here, so declare `outputs` on its nx build target as `apps/front/career` does") + /*
+     * ⛔ Problem, then solution, in ONE sentence and under 120 characters. The sentence that
+     * stood here ran 230 characters of nested clauses and a reader said what was wrong with
+     * it: *"un developpeur a bcp de taches en parallele donc son cerveau est concis, precis,
+     * probleme / solution tout court"*. One sentence because the recap prints only the first:
+     * split in two, the comment would carry the problem and lose the fix.
+     *
+     * ⚠️ The mechanism belongs AFTER, where the page and the json carry it and the comment
+     * does not. It is the explanation, and nobody acts on an explanation.
+     */
+    ". A build target with no declared `outputs` is still cached, and on a cache hit nx reports the task successful, restores no file and leaves the directory empty, so every job that reads the build sees nothing. Measured on this monorepo: 5 of the 48 projects with a build target are in that state, so the six bundle figures cannot be produced for any of them until they declare where their build writes." : "this module declares no build, so there is nothing to measure here. A component library and a back-end service are in that case by construction, and no action follows.",
     lookedIn
   };
 }
@@ -6085,29 +6095,21 @@ function renderMarkdown(report) {
     "",
     ...families,
     /*
-     * ⛔ The reserve says only what a reader of THIS comment can use, and the rest was cut.
+     * ⛔ ONE line, and it used to be five.
      *
-     * It used to spend 470 characters explaining `ok`, `near` and `exceeds` and defending the
-     * absence of a verdict as "a decision and not a gap". Measured on a five-module pull request:
-     * **not one of the 150 figures carried a verdict**, so three quarters of the reserve explained
-     * a notation that appeared nowhere in the comment, and argued with an objection a developer
-     * had not made. The legend now appears only when a verdict does.
+     * The reserve explained `ok`, `near` and `exceeds`, defended the absence of a verdict as "a
+     * decision and not a gap", and restated a counting rule. Measured on a five-module pull
+     * request: not one of the 150 figures carried a verdict, so most of it explained a notation
+     * that appeared nowhere and argued with an objection the reader had not made. A reader's
+     * verdict on it: *"on doit supprimer, laissons le message efficace le plus possible"*.
      *
-     * ⚠️ The non-comparison stays, and it is the one sentence here that prevents a wrong reading
-     * rather than answering a reviewer: a figure in a pull-request comment is read as a delta by
-     * default, so a module already at 6.81% looks identical to one this branch pushed there.
+     * ⚠️ What survives is the one clause that prevents a WRONG READING rather than defending a
+     * choice: a figure in a pull-request comment is read as a delta by default, so a module
+     * already at 6.81% would look like one this branch pushed there. Plus where the detail is,
+     * and the version, because two recaps from two versions are not comparable and nothing else
+     * on the comment would say so.
      */
-    "> Measured on this branch, **not compared with `main`**: every figure is a value, not a",
-    "> change. Nothing here blocks the merge. The code behind every place, and the import graph,",
-    "> are in the `static-analysis.html` the run keeps as an artifact.",
-    ...report.rows.some((row) => row.status !== void 0) ? [
-      "> **ok**, **near** and **exceeds** place a figure against a published reference. A figure",
-      "> without one carries no verdict."
-    ] : [],
-    // ⭐ The version that produced these numbers, because the thresholds a module cannot override
-    // live in the tool: nine gauge limits, the complexity bands, the bundle budgets. Two recaps
-    // from two versions are not comparable, and without this nothing on the comment would say so.
-    ...version === void 0 ? [] : [`> Measured by sentinel ${version}.`],
+    `<sub>Values on this branch, not a diff with \`main\`. Nothing here blocks the merge. The code behind every place, and the import graph, are in the \`static-analysis.html\` this run keeps as an artifact.${version === void 0 ? "" : ` Measured by sentinel ${version}.`}</sub>`,
     ""
   ].join("\n");
 }

package/dist/index.js

@@ -6,7 +6,7 @@ import {
   registerAdapters,
   resolve,
   setDefaultRunner
-} from "./chunk-XQRL555B.js";
+} from "./chunk-LCQZGHYL.js";
 import {
   BaseAdapter
 } from "./chunk-ZFNBW6S3.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hublo/sentinel",
-  "version": "1.5.0-alpha.33",
+  "version": "1.5.0-alpha.34",
   "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",