@hublo/sentinel 1.5.1-alpha.2 → 1.6.0-alpha.0

package/docs/typescript-traces.md

@@ -1571,5 +1571,263 @@ sentinel: mixed: preset is ambiguous, detected "react" (from react), also found
 # exit: 0
 ```
 
+## 6. Env conformance: the whole repository, from its root
+
+A throwaway git repository shaped like serviceapp: not nx, no contract, Node 10 behind a `v`, committed variable files. Every value is a placeholder.
+
+**--run --env (default level: warning, reports and exits 0)**
+
+```console
+$ sentinel --run --env
+env (level warning: report, and annotate in GitHub Actions; never fails)
+  2 env file(s), 0 contract(s), 0 required and 0 optional variable(s) read, 1 Dockerfile(s), node 10.15.3
+  settings: sentinel defaults (no env.config.mjs)
+
+  ✗ [committed-env-file] rule 2, blocking, 2
+    a real env file is committed: remove it from git (only .example contracts belong there; values come from a secret store)
+      variables/dev.variables.env
+      variables/production.variables.env
+
+  ! [public-secret-to-review] rule 5, advisory, 2
+    a public-prefixed, secret-named variable carries a committed value: it ships to the browser by design, confirm it is genuinely public
+      variables/dev.variables.env:2  REACT_APP_SEGMENT_API_KEY_ADMINS
+      variables/production.variables.env:2  REACT_APP_SEGMENT_API_KEY_ADMINS
+
+  ✗ [secret-not-blanked] rule 6, blocking, 2
+    a secret-named variable carries a committed value: blank it (leave the value empty) and move the value to a secret store
+      variables/dev.variables.env:1  DPAE_PASSWORD
+      variables/production.variables.env:1  DPAE_PASSWORD
+
+  ✗ [copy-not-owned] rule 10, blocking, 1
+    this COPY into the runtime stage has no --chown, so it lands root-owned under a non-root USER: add --chown (node:node, or 1000:1000 with --link) or a RUN chown -R
+      Dockerfile:8  COPY --from=build /home/node/app .
+  note: no contract is committed (**/*.env*.example): rules 1, 3 and 4 had nothing to compare the code with
+  note: no required reader call found (getOrFail, requireEnv, requireEnvVariable): rule 1 had nothing to check; name the repository's own helper in readers.required
+  note: not an nx workspace (no nx.json): rule 8 skipped
+
+  5 blocking findings: reported, not failing
+  ✓ serviceapp (repository) env — level=warning blocking=5
+  1 repository [serviceapp] in <n>ms
+# exit: 0
+```
+
+**SENTINEL_ENV_LEVEL=error --run --env (fails on a blocking finding)**
+
+```console
+$ sentinel --run --env
+env (level error: fails on a blocking finding (rules 1, 2, 6, 7 to 10))
+  2 env file(s), 0 contract(s), 0 required and 0 optional variable(s) read, 1 Dockerfile(s), node 10.15.3
+  settings: sentinel defaults (no env.config.mjs)
+
+  ✗ [committed-env-file] rule 2, blocking, 2
+    a real env file is committed: remove it from git (only .example contracts belong there; values come from a secret store)
+      variables/dev.variables.env
+      variables/production.variables.env
+
+  ! [public-secret-to-review] rule 5, advisory, 2
+    a public-prefixed, secret-named variable carries a committed value: it ships to the browser by design, confirm it is genuinely public
+      variables/dev.variables.env:2  REACT_APP_SEGMENT_API_KEY_ADMINS
+      variables/production.variables.env:2  REACT_APP_SEGMENT_API_KEY_ADMINS
+
+  ✗ [secret-not-blanked] rule 6, blocking, 2
+    a secret-named variable carries a committed value: blank it (leave the value empty) and move the value to a secret store
+      variables/dev.variables.env:1  DPAE_PASSWORD
+      variables/production.variables.env:1  DPAE_PASSWORD
+
+  ✗ [copy-not-owned] rule 10, blocking, 1
+    this COPY into the runtime stage has no --chown, so it lands root-owned under a non-root USER: add --chown (node:node, or 1000:1000 with --link) or a RUN chown -R
+      Dockerfile:8  COPY --from=build /home/node/app .
+  note: no contract is committed (**/*.env*.example): rules 1, 3 and 4 had nothing to compare the code with
+  note: no required reader call found (getOrFail, requireEnv, requireEnvVariable): rule 1 had nothing to check; name the repository's own helper in readers.required
+  note: not an nx workspace (no nx.json): rule 8 skipped
+
+  5 blocking findings: failing
+  ✗ serviceapp (repository) env — level=error blocking=5
+  1 repository [serviceapp] in <n>ms
+# exit: 1
+```
+
+**GITHUB_ACTIONS=true --run --env (one annotation per finding)**
+
+```console
+$ sentinel --run --env
+env (level warning: report, and annotate in GitHub Actions; never fails)
+  2 env file(s), 0 contract(s), 0 required and 0 optional variable(s) read, 1 Dockerfile(s), node 10.15.3
+  settings: sentinel defaults (no env.config.mjs)
+
+  ✗ [committed-env-file] rule 2, blocking, 2
+    a real env file is committed: remove it from git (only .example contracts belong there; values come from a secret store)
+      variables/dev.variables.env
+      variables/production.variables.env
+
+  ! [public-secret-to-review] rule 5, advisory, 2
+    a public-prefixed, secret-named variable carries a committed value: it ships to the browser by design, confirm it is genuinely public
+      variables/dev.variables.env:2  REACT_APP_SEGMENT_API_KEY_ADMINS
+      variables/production.variables.env:2  REACT_APP_SEGMENT_API_KEY_ADMINS
+
+  ✗ [secret-not-blanked] rule 6, blocking, 2
+    a secret-named variable carries a committed value: blank it (leave the value empty) and move the value to a secret store
+      variables/dev.variables.env:1  DPAE_PASSWORD
+      variables/production.variables.env:1  DPAE_PASSWORD
+
+  ✗ [copy-not-owned] rule 10, blocking, 1
+    this COPY into the runtime stage has no --chown, so it lands root-owned under a non-root USER: add --chown (node:node, or 1000:1000 with --link) or a RUN chown -R
+      Dockerfile:8  COPY --from=build /home/node/app .
+  note: no contract is committed (**/*.env*.example): rules 1, 3 and 4 had nothing to compare the code with
+  note: no required reader call found (getOrFail, requireEnv, requireEnvVariable): rule 1 had nothing to check; name the repository's own helper in readers.required
+  note: not an nx workspace (no nx.json): rule 8 skipped
+
+  5 blocking findings: reported, not failing
+::warning file=variables/dev.variables.env,title=env rule 2%3A committed-env-file::variables/dev.variables.env: a real env file is committed: remove it from git (only .example contracts belong there; values come from a secret store)
+::warning file=variables/production.variables.env,title=env rule 2%3A committed-env-file::variables/production.variables.env: a real env file is committed: remove it from git (only .example contracts belong there; values come from a secret store)
+::warning file=variables/dev.variables.env,line=2,title=env rule 5%3A public-secret-to-review::REACT_APP_SEGMENT_API_KEY_ADMINS: a public-prefixed, secret-named variable carries a committed value: it ships to the browser by design, confirm it is genuinely public
+::warning file=variables/production.variables.env,line=2,title=env rule 5%3A public-secret-to-review::REACT_APP_SEGMENT_API_KEY_ADMINS: a public-prefixed, secret-named variable carries a committed value: it ships to the browser by design, confirm it is genuinely public
+::warning file=variables/dev.variables.env,line=1,title=env rule 6%3A secret-not-blanked::DPAE_PASSWORD: a secret-named variable carries a committed value: blank it (leave the value empty) and move the value to a secret store
+::warning file=variables/production.variables.env,line=1,title=env rule 6%3A secret-not-blanked::DPAE_PASSWORD: a secret-named variable carries a committed value: blank it (leave the value empty) and move the value to a secret store
+::warning file=Dockerfile,line=8,title=env rule 10%3A copy-not-owned::COPY --from=build /home/node/app .: this COPY into the runtime stage has no --chown, so it lands root-owned under a non-root USER: add --chown (node:node, or 1000:1000 with --link) or a RUN chown -R
+  ✓ serviceapp (repository) env — level=warning blocking=5
+  1 repository [serviceapp] in <n>ms
+# exit: 0
+```
+
+**--run --env --json** (stdout only, the JSON envelope)
+
+```json
+$ sentinel --run --env --json 2>/dev/null
+{
+  "schemaVersion": 2,
+  "executed": [
+    "env"
+  ],
+  "skipped": [],
+  "results": [
+    {
+      "project": "serviceapp",
+      "target": "env",
+      "flavour": "repository",
+      "ok": true,
+      "status": "ok",
+      "level": "warning",
+      "verdict": "5 blocking findings: reported, not failing",
+      "blocking": 5,
+      "config": null,
+      "scanned": [
+        "."
+      ],
+      "counts": {
+        "required": 0,
+        "optional": 0,
+        "contracts": 0,
+        "envFiles": 2,
+        "dockerfiles": 1
+      },
+      "nodeVersion": "10.15.3",
+      "notes": [
+        "no contract is committed (**/*.env*.example): rules 1, 3 and 4 had nothing to compare the code with",
+        "no required reader call found (getOrFail, requireEnv, requireEnvVariable): rule 1 had nothing to check; name the repository's own helper in readers.required",
+        "not an nx workspace (no nx.json): rule 8 skipped"
+      ],
+      "findings": [
+        {
+          "rule": "committed-env-file",
+          "number": 2,
+          "severity": "blocking",
+          "name": "variables/dev.variables.env",
+          "file": "variables/dev.variables.env"
+        },
+        {
+          "rule": "committed-env-file",
+          "number": 2,
+          "severity": "blocking",
+          "name": "variables/production.variables.env",
+          "file": "variables/production.variables.env"
+        },
+        {
+          "rule": "public-secret-to-review",
+          "number": 5,
+          "severity": "advisory",
+          "name": "REACT_APP_SEGMENT_API_KEY_ADMINS",
+          "file": "variables/dev.variables.env",
+          "line": 2
+        },
+        {
+          "rule": "public-secret-to-review",
+          "number": 5,
+          "severity": "advisory",
+          "name": "REACT_APP_SEGMENT_API_KEY_ADMINS",
+          "file": "variables/production.variables.env",
+          "line": 2
+        },
+        {
+          "rule": "secret-not-blanked",
+          "number": 6,
+          "severity": "blocking",
+          "name": "DPAE_PASSWORD",
+          "file": "variables/dev.variables.env",
+          "line": 1
+        },
+        {
+          "rule": "secret-not-blanked",
+          "number": 6,
+          "severity": "blocking",
+          "name": "DPAE_PASSWORD",
+          "file": "variables/production.variables.env",
+          "line": 1
+        },
+        {
+          "rule": "copy-not-owned",
+          "number": 10,
+          "severity": "blocking",
+          "name": "COPY --from=build /home/node/app .",
+          "file": "Dockerfile",
+          "line": 8
+        }
+      ],
+      "inventory": {
+        "required": [],
+        "optional": [],
+        "contracts": []
+      }
+    }
+  ]
+}
+```
+
+**SENTINEL_ENV_LEVEL=strict (unknown level, refused)**
+
+```console
+$ sentinel --run --env
+sentinel: unknown SENTINEL_ENV_LEVEL "strict". Supported: info, warning, error (warning when unset).
+(run "sentinel --help" for usage)
+# exit: 1
+```
+
+**from inside a module (refused, with the root to run from)**
+
+```console
+$ sentinel --run --env
+sentinel: --env checks the whole repository, so it runs from its root rather than from a directory inside it. Run it from <fixture>/serviceapp.
+(run "sentinel --help" for usage)
+# exit: 1
+```
+
+**outside any git repository (refused)**
+
+```console
+$ sentinel --run --env
+sentinel: --env reads the repository through git, and <fixture>/nogit is not inside a git repository (or git cannot run here).
+(run "sentinel --help" for usage)
+# exit: 1
+```
+
+**--inspect --env (it only runs)**
+
+```console
+$ sentinel --inspect --env
+sentinel: --env reads the repository and writes no config, so it only runs: `sentinel --run --env`. It has no --inspect.
+(run "sentinel --help" for usage)
+# exit: 1
+```
+
 ---
 _Generated. Regenerate with `pnpm build && bash scripts/gen-traces.sh`._

package/docs/using-sentinel.md

@@ -23,15 +23,16 @@ sentinel --run                             # no target        -> every wired tar
 Read it by target, since that is what you pick first. `--report` and `--status` are deprecated
 everywhere (`--run --json` and `--inspect` answer them), and `--migrate` is refused everywhere.
 
-| Target              | `--init` writes                                                                                           | `--run` does                                                   | `--inspect` shows                                                |
-| ------------------- | --------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- | ---------------------------------------------------------------- |
-| `--lint`            | stub + scripts + nx metadata, removes the ESLint config and the module's ESLint deps, then autofixes once | lints; `--fix` autofixes in the same pass                      | rule count, what is disabled or downgraded and **why**, drift    |
-| `--format`          | materializes the preset + scripts + nx metadata, removes the Prettier config and deps, then formats once  | **checks**; `--fix` writes                                     | effective options, every departure from the standard and why     |
-| `--typescript`      | writes/extends the tsconfig + `typecheck` script                                                          | typechecks                                                     | resolved options, what is deferred, drift                        |
-| `--build`           | points the module's Vite config at sentinel's toolchain + scripts + nx metadata                           | builds                                                         | runner, config file, whose Vite, how many overrides, adoption    |
-| `--dev`             | adopts the BUILD too: one plan writes both `build` and `serve`                                            | serves; long-running, so never swept by an unqualified `--run` | refuses, and sends you to `--inspect --build`: it is that config |
-| `--test`            | the Vitest config + scripts + nx metadata, and migrates every spec file                                   | runs Vitest                                                    | runner, which configs were found, adoption state, drift          |
-| `--static-analysis` | the config stub + three scripts + nx metadata, and ignores the report directory at the repository root    | measures and reports; never exits non-zero on a finding        | runner, config file, resolved settings, what this module moved   |
+| Target              | `--init` writes                                                                                           | `--run` does                                                                                                                                                                           | `--inspect` shows                                                |
+| ------------------- | --------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- |
+| `--lint`            | stub + scripts + nx metadata, removes the ESLint config and the module's ESLint deps, then autofixes once | lints; `--fix` autofixes in the same pass                                                                                                                                              | rule count, what is disabled or downgraded and **why**, drift    |
+| `--format`          | materializes the preset + scripts + nx metadata, removes the Prettier config and deps, then formats once  | **checks**; `--fix` writes                                                                                                                                                             | effective options, every departure from the standard and why     |
+| `--typescript`      | writes/extends the tsconfig + `typecheck` script                                                          | typechecks                                                                                                                                                                             | resolved options, what is deferred, drift                        |
+| `--build`           | points the module's Vite config at sentinel's toolchain + scripts + nx metadata                           | builds                                                                                                                                                                                 | runner, config file, whose Vite, how many overrides, adoption    |
+| `--dev`             | adopts the BUILD too: one plan writes both `build` and `serve`                                            | serves; long-running, so never swept by an unqualified `--run`                                                                                                                         | refuses, and sends you to `--inspect --build`: it is that config |
+| `--test`            | the Vitest config + scripts + nx metadata, and migrates every spec file                                   | runs Vitest                                                                                                                                                                            | runner, which configs were found, adoption state, drift          |
+| `--static-analysis` | the config stub + three scripts + nx metadata, and ignores the report directory at the repository root    | measures and reports; never exits non-zero on a finding                                                                                                                                | runner, config file, resolved settings, what this module moved   |
+| `--env`             | refuses: it writes no config (an optional `env.config.mjs` at the repository root declares exceptions)    | checks the whole REPOSITORY, from its git root only; exits 1 on a blocking finding at `SENTINEL_ENV_LEVEL=error`; an invalid level refuses the whole run, a bare root `--run` included | refuses: nothing to inspect                                      |
 
 `--json` works for every verb, and stdout carries **only** the envelope, so `| jq` always
 parses. `--dry-run` applies to `--init` and writes nothing. Besides the config diffs, it says
@@ -47,7 +48,7 @@ is refused, because a real `--init` runs the passes itself.
 `--output <shape>` is different, and only a role that WRITES a report reads it: `console` is the
 default and writes no file, `html` is the page you open and send, `json` is for CI and for a
 script, `markdown` is the six lines a workflow posts on a pull request. Today `--static-analysis`
-is the role that has them. ⚠️ `--output html` pays a graph layout the other three skip, which is
+is the role that has them, and `--env` writes `json` and `markdown` (see `env-adoption.md`). ⚠️ `--output html` pays a graph layout the other three skip, which is
 fine for a page somebody opens and wrong for a commit hook.
 
 **`--validate` is a verb of its own**, and the proof of a migration lives there rather than on

package/docs/validating-a-change.md

@@ -135,6 +135,109 @@ majority of the migration, and only a sweep over every real module found it.
 
 ---
 
+## The env role's validation matrix, 30 October 2026
+
+Every cell is a test in `tests/e2e/env.e2e.test.ts`, against the built CLI, on git fixtures: a
+serviceapp-shaped repository (not nx, committed `variables/*.env`), the same with a package below
+its root, an nx workspace with a module, and a directory in no repository. `SENTINEL_ENV_LEVEL` and
+`GITHUB_ACTIONS` are pinned on every call, and "unset" removes the variable from the child's
+environment, which is a different input from the empty string. 52 cells: the 31 of the first draft,
+one more refused verb, 19 new ones, and the rule 1 note.
+
+### verb, from the repository root
+
+| verb                                                         | result                                                                   |
+| ------------------------------------------------------------ | ------------------------------------------------------------------------ |
+| `--run --env`                                                | runs                                                                     |
+| `--report --env`                                             | runs, as the deprecated `--run --json`; exits 0 at `error` unless `--ci` |
+| `--inspect`, `--init`, `--status`, `--validate`, `--migrate` | refused: "so it only runs: `sentinel --run --env`"                       |
+| `--run --env --dry-run`                                      | refused: `--dry-run` only applies to `--init`                            |
+| `--init --env --dry-run`                                     | refused for env first, with the command that works                       |
+
+### level × config × GitHub Actions, `--run --env` at the root
+
+| level                     | no config: exit           | in GitHub Actions                        | exceptions declared: exit | in GitHub Actions              |
+| ------------------------- | ------------------------- | ---------------------------------------- | ------------------------- | ------------------------------ |
+| unset                     | 0, as `warning`           | `::warning` per finding                  |                           |                                |
+| empty                     | 0, as `warning`           |                                          |                           |                                |
+| `info`                    | 0                         | no annotation                            | 0                         |                                |
+| `warning`                 | 0                         | `::warning` per finding                  | 0                         |                                |
+| `error`, `ERROR`, `error` | 1                         | `::error` blocking, `::warning` the rest | 0                         | accepted secret is `::warning` |
+| `strict`, `loud`          | 1, refused before running | refused, nothing annotated               |                           |                                |
+
+`--json` in GitHub Actions: one document on stdout, the annotations on stderr, at `warning` and at
+`error`. The config cells already covered `defineEnv` installed, `defineEnv` not installed
+(explained), an unknown key (refused) and a plain object at `error`.
+
+### location
+
+| from                                | `--run --env`                                                            | bare `--run`                                                                               |
+| ----------------------------------- | ------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------ |
+| nx workspace root                   | runs                                                                     | includes env once, beside the modules                                                      |
+| nx module directory                 | refused, naming the root                                                 | no env                                                                                     |
+| root of a repository that is not nx | runs                                                                     | includes env once; an invalid level refuses the WHOLE sweep; `error` fails it on env alone |
+| a package below that root           | refused, naming the root, at unset, `error` and `loud`; level never read | no env, level never read                                                                   |
+| a directory in no git repository    | refused, before the level is read                                        | no env                                                                                     |
+
+### Negative controls
+
+Each behaviour reverted in the source, the CLI rebuilt, the 51 cells run. A family whose control
+fails nothing would be decoration; none is, and every new cell fails under at least one control.
+
+| reverted                                              | cells failing |
+| ----------------------------------------------------- | ------------: |
+| non-`--run` verbs refuse `--env`                      |             6 |
+| `--report` runs env                                   |             1 |
+| `--dry-run` refused outside `--init`                  |             1 |
+| default level `warning` (set to `info`)               |             7 |
+| an unknown level refused                              |             3 |
+| the level trimmed                                     |             1 |
+| `env.config.mjs` read                                 |             8 |
+| an advisory finding stays `::warning` at `error`      |             2 |
+| a named env refused away from the root or outside git |             4 |
+| a sweep includes env only at the root (made always)   |             3 |
+| a sweep includes env at the root (made never)         |             4 |
+| a sweep reads the level when it includes env          |             2 |
+| `--json` annotations on stderr                        |             2 |
+| the rule 1 note, never emitted (unit + e2e)           |             3 |
+| the rule 1 note, always emitted (unit + e2e)          |             2 |
+
+The `COPY` fix is unit (`env-checks-fixes`): reverted, its 3 tests fail and the 66 others pass.
+
+### Against real repositories, from the packed tarball
+
+`npm pack` of the branch, run through `npx --yes --package <tgz> sentinel --run --env` as a
+workflow step would, on six hublo repositories that are not the monorepo, at unset, `info`,
+`warning`, `error` and an invalid level, inside and outside GitHub Actions, console and `--json`:
+
+| repository        | blocking | findings by rule         | `error` exit | git status after |
+| ----------------- | -------: | ------------------------ | -----------: | ---------------- |
+| serviceapp        |       55 | 2: 9, 5: 9, 6: 45, 10: 1 |            1 | clean            |
+| serviceapi        |       11 | 1: 2, 4: 2, 6: 5, 10: 4  |            1 | clean            |
+| contract-front    |        4 | 4: 4, 5: 1, 9: 1, 10: 3  |            1 | clean            |
+| servicebackoffice |        3 | 2: 1, 10: 2              |            1 | clean            |
+| servicemission    |        3 | 4: 21, 9: 1, 10: 2       |            1 | clean            |
+| servicecontract   |        0 | 4: 21                    |            0 | clean            |
+
+Every other level exits 0, the invalid one 1. servicecontract shows the advisory rules never block:
+21 dead variables, exit 0 at `error`. It had 1 blocking finding before the `COPY` fix. No committed
+value of 6 characters or more appears in any output, other than four ordinary words sentinel prints
+itself (`default`, `require`, `production`, `staging`). Installed instead (`npm install` of the
+tarball in a copy of servicemission), `defineEnv` from `@hublo/sentinel/env` applies: 21 dead
+variables become 12 with two `knownExternalPatterns`, and an unknown key is refused.
+
+Rule 8 against a real nx ran on the monorepo only (nx installed in a throwaway worktree): 3 literal
+`nx run` references, no finding, no skip note.
+
+### What this matrix does NOT cover
+
+- GitHub's own cap on annotations: serviceapp emits 55 `::error`. GitHub's documentation says
+  "GitHub Actions are limited to 10 warning annotations and 10 error annotations per step"
+  (<https://docs.github.com/en/rest/checks/runs>), so a pull request would show 10 of them; that
+  is the documented figure, not a measured one.
+- `--output markdown` posted as a sticky comment: the file is tested, the posting is the
+  consumer's workflow.
+
 ## The `--init` matrix for 1.5.1, 29 October 2026
 
 Six fixes, then a seventh (below) found by the alpha.1 validation. Found by re-initializing the monorepo's 63 adopted modules with 1.5.1-alpha.0. Every

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hublo/sentinel",
-  "version": "1.5.1-alpha.2",
+  "version": "1.6.0-alpha.0",
   "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",
@@ -51,6 +51,10 @@
       "types": "./dist/roles/static-analysis/config.d.ts",
       "import": "./dist/roles/static-analysis/config.js"
     },
+    "./env": {
+      "types": "./dist/roles/env/config.d.ts",
+      "import": "./dist/roles/env/config.js"
+    },
     "./test/react": {
       "types": "./dist/roles/test/react/toolchain.d.ts",
       "import": "./dist/roles/test/react/toolchain.js"

package/dist/chunk-WBDBRGLV.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":["../src/shared/deep-merge.ts","../src/core/domain.ts","../src/roles/static-analysis/presets/shared.json","../src/roles/static-analysis/preset-data.ts","../src/roles/static-analysis/configs/define.ts"],"sourcesContent":["/**\n * Is this a plain JSON object?\n *\n * The file is named for a `deepMerge` that no longer exists. It was written when the engine\n * merged JSON in memory and wrote the result; that approach was replaced by editing the\n * document IN PLACE with jsonc-parser, so a project's comments, key order and formatting\n * survive a `merge-json` op. Nothing has called `deepMerge` since, except its own recursion,\n * so it went.\n *\n * What remains is the predicate the in-place merge still needs, to decide whether a value is\n * a branch to walk into or a leaf to set.\n */\n\n/** True for a mergeable plain object (not null, not an array). */\nexport function isPlainObject(value: unknown): value is Record<string, unknown> {\n  return typeof value === 'object' && value !== null && !Array.isArray(value)\n}\n","/**\n * The domain vocabulary: the fixed sets of verbs, targets, and presets, and the\n * types derived from them. This is the model, and the extension point: adding a\n * verb / target / preset is a one-line edit to a list here, and because the types\n * are DERIVED (`(typeof LIST)[number]`), the compiler forces every switch/handler\n * to cover the new member.\n *\n * Tunable behaviour (defaults, detection signals, marker filenames) lives in\n * `settings.ts`, not here.\n */\n\n/**\n * Verbs: what to do.\n *\n * The axis is not \"who runs it\" but **what survives the run**, which is the distinction that\n * outlives any sharing of the work:\n *\n * | verb | writes | what remains |\n * | --- | --- | --- |\n * | `init` | a module's config + the workspace prep it needs | the module's new state, that IS the deliverable |\n * | `migrate` | changes an already-initialized setup | same; reserved, not wired yet |\n * | `validate` | instrumentation, if it needs any | **nothing**, the project returns to what it was |\n * | `run` / `inspect` / `report` / `status` | nothing | they execute or introspect |\n *\n * `validate` is the one that judges. Héla, 2026-09-25: it does not carry the migration's\n * strictness, so it MAY write into the project under validation, a `data-testid` to make something\n * addressable for instance, provided it takes it back out. That freedom is what makes its\n * dependability the thing to design: idempotent, reversible on error, recoverable after a kill,\n * and never silent about instrumentation it failed to remove.\n */\nexport const VERBS = ['run', 'inspect', 'init', 'migrate', 'validate', 'report', 'status'] as const\nexport type Verb = (typeof VERBS)[number]\n\n/** Targets: the kind of check. The CLI `--<target>` flags map 1:1 to these. */\nexport const TARGETS = [\n  'lint',\n  'format',\n  'typescript',\n  'build',\n  'dev',\n  'test',\n  'static-analysis',\n  'runtime-analysis',\n  'arch',\n] as const\nexport type Target = (typeof TARGETS)[number]\n\n/**\n * Targets that do not TERMINATE, and are therefore never swept.\n *\n * Every other target is a check: it runs, it answers, it exits. `dev` starts a server and\n * stays up until someone stops it. That difference matters exactly once, and it matters a lot:\n * `sentinel --run` with no named target means \"every wired target\", so without this a sweep\n * would launch a dev server per module and never come back — on a 441-module workspace, from a\n * command whose whole purpose is to answer a question.\n *\n * So a long-running target is reachable only when NAMED. `sentinel --run --dev` starts the\n * server; `sentinel --run` never does.\n *\n * It is a target rather than a flag on `--build` because it is the app's second invocation of\n * the same toolchain: `build` stopped calling `vite build` directly, and `serve` still called\n * `vite` directly. Same migration, same tool, one script left behind.\n */\nexport const LONG_RUNNING_TARGETS: readonly Target[] = ['dev']\n\n/** The targets an unqualified `--run` / `--all` covers: everything that terminates. */\nexport const SWEEPABLE_TARGETS: readonly Target[] = TARGETS.filter(\n  (target) => !LONG_RUNNING_TARGETS.includes(target),\n)\n\n/** Presets: the stack preset a project resolves to (strict by default). */\nexport const PRESET_NAMES = ['react', 'nest', 'svelte', 'node', 'tools'] as const\nexport type PresetName = (typeof PRESET_NAMES)[number]\n\n/**\n * The shapes `--output` can ask a report-writing role for. `console` writes nothing to disk.\n *\n * ⛔ Here rather than in the role that happens to implement them today, for the same reason\n * `PRESET_NAMES` is here: `--output` is a GLOBAL flag, so the CLI has to validate it before any\n * role is chosen. It used to be validated inside the static-analysis adapter, which runs on\n * `--run` only, and the measured consequence was that `--inspect`, `--status` and `--init`\n * accepted `--output xml` silently and exited 0. A flag that is refused by one verb out of four\n * is worse than one that is never refused: it teaches you it was checked.\n */\nexport const OUTPUT_SHAPES = ['console', 'json', 'html', 'markdown'] as const\nexport type OutputShape = (typeof OUTPUT_SHAPES)[number]\n\n/**\n * The outcome of one module × target check. `unsupported` is a distinct third state\n * (a requested target has no adapter yet): it must never read as a pass, and an\n * explicitly-requested unsupported target is a usage error (non-zero exit), while an\n * unsupported target swept in by `--all` is just skipped and shown.\n */\nexport type ResultStatus = 'ok' | 'failed' | 'unsupported'\n\n/**\n * @deprecated Renamed to `PresetName`. Kept so an existing `import type { Flavour }` keeps\n * compiling: the CLI kept `--flavour` working for the same reason, and breaking the type\n * while sparing the flag would be an odd place to draw the line.\n */\nexport type Flavour = PresetName\n","{\n  \"entry\": [\n    \"**/*.integration-spec.ts\",\n    \"**/*.steps.ts\",\n    \"src/client.tsx\",\n    \"src/start.ts\",\n    \"src/router.tsx\",\n    \"src/RouterContext.tsx\"\n  ],\n  \"ignore\": [\n    \"**/node_modules/**\",\n    \"**/dist/**\",\n    \"**/build/**\",\n    \"**/coverage/**\",\n    \"**/.next/**\",\n    \"**/__mocks__/**\",\n    \"**/mocks/**\",\n    \"**/_mock_/**\",\n    \"**/**Mock**/**\",\n    \"**/__fixtures__/**\",\n    \"**/fixtures/**\",\n    \"**/public/**\",\n    \"**/.husky/**\",\n    \"**/.vscode/**\",\n    \"**/.idea/**\",\n    \"**/.github/**\",\n    \"**/*.d.ts\",\n    \"**/*.gen.ts\",\n    \"**/*.generated.ts\"\n  ],\n  \"languages\": [\"javascript\", \"typescript\", \"jsx\", \"tsx\", \"css\", \"scss\"],\n  \"journeys\": {},\n  \"duplication\": {\n    \"minTokens\": 50,\n    \"minLines\": 5,\n    \"kinds\": [\"exact\"],\n    \"tests\": [\n      \"*.{test,spec,steps,e2e-spec,integration-spec,stories}.{ts,tsx,js,jsx}\",\n      \"*.{msw,mock,test-data}.{ts,tsx,js,jsx}\",\n      \"{tests,__tests__,test,testing,stubs}/**/*.{ts,tsx,js,jsx}\"\n    ]\n  },\n  \"deadCode\": {\n    \"minConfidence\": 60,\n    \"categories\": [\"unused-file\", \"unused-export\", \"unused-symbol\", \"unused-import\"]\n  },\n  \"graph\": {\n    \"resolution\": 1\n  },\n  \"tools\": {\n    \"jscpd\": {}\n  }\n}\n","/**\n * The static analysis preset: the role's settings, as data.\n *\n * One shared layer and no per-stack preset yet, because nothing measured so far varies by stack:\n * duplication, dead code and complexity are the same questions in Nest and in React. The split\n * that is already foreseen is `LCOM4`, which is meaningless on a functional front end and real on\n * nest's 16 568 classes; when it arrives it becomes `nest.json` beside this layer, which is why\n * the values live here as JSON rather than inline in the code.\n *\n * ## Why these values are the role's and not the module's\n *\n * A team declares FACTS about its own domain (which journeys exist, which files are entry points);\n * it does not declare the values a number is judged by. Two files with the same measurement\n * getting different verdicts in two modules would make every figure incomparable, and the first\n * thing this role has to be able to say is that a number means the same thing everywhere.\n *\n * That is a default, not a wall: a module CAN move any of them (see `configs/define.ts`), and when\n * it does the report prints `(module)` next to the value. The seam exists from the first commit\n * because retrofitting one later means rewriting every module's file.\n *\n * ⛔ There are no thresholds here, and their absence is a decision rather than an omission.\n *\n * A threshold was written first, at 5% of duplicated lines, and then removed. Measured over all 228\n * nx projects: 5% flags 65 of the 201 measurable modules, a third of the repository, and moving the\n * figure until the count felt manageable is not calibration, it is fitting the instrument to the\n * answer. Calibration is legitimate when a bench is polluted and the noise is removed, or when the\n * reference frame changes; neither applies to a share of duplicated lines.\n *\n * And there is nothing to calibrate AGAINST: of the sources in `docs/static-analysis-study.md`\n * section 5, NDepend, Lattix, ArchUnit, CodeScene and Arcan, none publishes a threshold for\n * duplicated lines. One invented here would travel as if it were published.\n *\n * So the role reports the measurement. What makes a single figure readable is the distribution it\n * sits in, which only a workspace-wide run can know, so that belongs to the sweep and to the\n * migration page, not to a module's own report. The first defensible warning will not be an absolute\n * number either: a module that got WORSE than its own previous measurement is a signal that needs no\n * invented bar, which is what a baseline gives, and that was already deferred for its own reasons.\n *\n * ## Where each value comes from, so nobody has to guess later\n *\n *  - `entry` is the single most consequential line in the file. Measured on\n *    `apps/nest/microservices/network` with jscpd 5.4.0: with nothing declared the dead-code pass\n *    reports **33.4%** of lines dead (79 657 lines, 232 files, 13 entry points); with these two\n *    patterns declared it reports **1.0%** (2 462 lines, 207 entry points). The cause is a naming\n *    convention and not a bug: our integration tests are `foo.integration-spec.ts` with a HYPHEN,\n *    so they do not end in `.spec.ts` and the tool's own test-file detection never sees them, and\n *    the 115 `.steps.ts` BDD definitions are tests by no convention it knows. A module ADDS to\n *    this list rather than replacing it, precisely so no team can lose these two by declaring a\n *    third.\n *\n *    ⭐ The four `src/` files are the FRONT bootstrap, and they are the most consequential thing\n *    measured on this pass. The tool recognises around fifty frameworks and TanStack Start is not\n *    one of them, so nothing in the repository imports these files: the framework finds them by\n *    convention at build time. Measured without them declared, `apps/front/console` reports\n *    `src/client.tsx`, `src/router.tsx` and `src/start.ts` among its 5 dead files, which are its\n *    hydration entry, its router factory and its Start config. `host-admin` reports `client.tsx`\n *    too and `career` reports `router.tsx` and `RouterContext.tsx`. Three of console's five\n *    findings were its own bootstrap, and the first team to see that stops trusting the tool on\n *    the spot. They exist in 2 to 3 front apps each.\n *\n *    ⛔ `scripts/**` is deliberately NOT here, although 8 modules have one and\n *    `apps/nest/microservices/contract` reports two `scripts/e2e-*.ts` as dead. No `package.json`\n *    script invokes them, so whether they run at all is a fact only the team holds. Declaring them\n *    would hide a finding that may well be true, and that is the opposite of this role's job.\n *\n *  - `languages` is this role's name for what the tool calls `format`, a word that already names\n *    another sentinel role and means something else there. Stating it has a measured cost either\n *    way: on `apps/front/console`, naming `typescript` alone scans 300 of 523 files because `.tsx`\n *    is a SEPARATE language to the tool, naming all four scans 522 (the one left out being\n *    `styles.css`), and naming nothing scans every one of its 224 languages, json and markdown\n *    included. Stylesheets are in deliberately: measured on `libs/front` they duplicate at 9.64%\n *    against 3.50% for the code, a signal that only survives because the report is broken down per\n *    language.\n *\n *  - `duplication.minTokens` and `minLines` are the detection window, and the window decides what\n *    is INVISIBLE: a fragment shorter than it is not reported at all, so a reader comparing two\n *    runs has to know both values. They are the tool's own defaults, written out rather than\n *    inherited for that reason.\n *\n *  - `duplication.kinds` is `exact` alone, and that is a correctness constraint rather than\n *    caution. Measured: with a second kind enabled, `duplicatedLines` adds up overlapping clones.\n *    Two 9-line files reported 13 duplicated lines out of 18, 72%, because an `exact` clone of\n *    lines 1-4 and a `similar` clone of lines 1-9 containing it were both counted; the real extent\n *    is 9 of 18, 50%. The tool's own answer is to cap the display at 100%, which does not make a\n *    threshold meaningful. Opening another kind therefore requires computing the share ourselves\n *    from the UNION of the line ranges.\n *\n *  - `duplication.tests` is the glob that splits the pass in two, and the split is the finding that\n *    forced it. Measured across 8 modules of the three families, **71% of all duplicated lines are\n *    between two test files**: `libs/nest/auth` reports 35.77% and its product code is at 5.96%,\n *    `apps/front/host-admin` 7.91% against 3.59%. A single blended figure is therefore mostly a\n *    measure of spec duplication wearing the name of the module's duplication, and the number\n *    travels while that nuance does not. So the role reports the two side by side, the way it\n *    already refuses to blend languages, and neither is hidden: a module whose specs carry 93% of\n *    its clones is saying something about its specs that excluding them would erase.\n *\n *    ⚠️ The two passes PARTITION the files and therefore lose a clone that spans them: a fragment\n *    shared between a test and a product file has no partner in either scan. Measured on the same\n *    8 modules, that is 42 entries of 5117, 0.8%, 650 lines. Stated in the caveat rather than\n *    silently accepted, and it is the price of the split.\n *\n *    Two patterns and not one, because a suffix convention does not cover a DIRECTORY convention,\n *    and the directory one is not a quirk: 635 files across 26 modules live under `tests/` or\n *    `__tests__/` without a name this role's suffixes recognise, `apps/nest/microservices/recruitment`\n *    alone holding 160. They are step definitions, in-memory doubles and stubs, which is test-side\n *    code by any reading. A role default rather than 26 identical overrides.\n *\n *    ⚠️ The patterns are RELATIVE here, and the adapter prefixes and composes them, because the\n *    tool's `--pattern` takes exactly one glob. Verified on four modules that the two passes\n *    partition exactly: console 479 + 87 = 566, contract 399 + 151 = 550, backends-for-frontends/admin\n *    2062 + 773 = 2835, recruitment 936 + 621 = 1557.\n *\n *    ⚠️ And a trap that cost a wrong table before it was caught: these globs contain commas, so they\n *    survive the config FILE and are destroyed by the `-i` command-line flag, which splits on\n *    commas and cuts `{test,spec}` in half. The adapter writes a file, which is one more reason it\n *    does.\n *\n *  - `deadCode.minConfidence` is the tool's own default of 60. It scores every finding and names\n *    what lowered it (a file calling `eval`, an unrecognised decorator, a name appearing in a\n *    string literal, a file in the scan that did not parse). Measured on sentinel: 60 yields 20\n *    files, 10 exports and 22 symbols; 90 yields 18 files; 100 yields nothing.\n *\n *  - `deadCode.categories` leaves out `unused-member` deliberately: without type information\n *    `x.render()` could reach any `render` in the project, which the tool itself calls its least\n *    certain rule.\n *\n *  - `ignore` excludes generated, vendored and fixture code, which duplicates by nature and buries\n *    the clones a developer can act on. It is load-bearing rather than tidy: measured on this\n *    package, scanning the module root with no ignore list reports 18 186 files and 32 153 clones,\n *    **31 969** of them touching `node_modules`; with the list, 408 files and zero.\n *\n *  - `graph.resolution` is Louvain's, and it is 1 because that is the value the papers use and\n *    graphology's own default. It decides how large a community must be to survive, so it changes\n *    both the community count and `Q`, and graphology's documentation warns in its own words that\n *    it is finicky to tweak. `code-health-meter` ships 0.74, arrived at by trying values until the\n *    partition looked right; this role declines to do that, for the same reason it ships no\n *    duplication threshold. A module that has a reason can move it, and the report prints the\n *    value every figure was produced with.\n *\n *    ⚠️ What is NOT tunable is the random seed, and that is deliberate. Louvain is greedy, so its\n *    answer depends on the order it visits nodes, which graphology draws from `Math.random`.\n *    Measured over 20 runs per module: `console` produced 16 distinct values of `Q` and between 12\n *    and 14 communities, `recruitment` 19 distinct values spanning 0.0357. With the role's own\n *    generator all five modules produce one value. A figure that moves on its own between two runs\n *    is not a figure a team can act on, so this one is the role's and nobody's to change.\n *\n *  - `tools.jscpd` is passed to the tool verbatim, and it is **sentinel's own** escape hatch, not a\n *    module's: `defineStaticAnalysis` excludes it from what a module can override. Everything above\n *    uses OUR key names, translated on the way out, so that replacing the tool one day does not\n *    oblige a single module to edit its config file, and a module only ever knows the ROLE. This\n *    block is where that guarantee stops, which is why it stays on this side and why it is empty:\n *    the first thing to put in it would be an option a single preset needs, not a workaround.\n */\nimport { OUTPUT_SHAPES } from '../../core/domain.js'\n\nimport sharedData from './presets/shared.json'\n\n/**\n * Where the json and html reports are written, relative to the module.\n *\n * Named for the role rather than left on the tool's default `report/`, and added to `.gitignore`\n * by `--init`. Both halves matter: the format role once shipped a `lint/` directory that nothing\n * ignored, and every adopting module grew an untracked directory nobody could explain.\n */\nexport const REPORT_DIR = 'static-analysis-report'\n\n/** The target this role serves, which is also the npm script a module runs and the nx target. */\nexport const TARGET = 'static-analysis'\n\n/**\n * The output shapes `--run` can produce. `console` writes nothing to disk.\n *\n * Re-exported from `core/domain` rather than declared here: `--output` is a global CLI flag and\n * the CLI validates it before a role is chosen, so one list has to serve both. This spelling\n * stays because the role and its report read it everywhere.\n */\nexport const SHAPES = OUTPUT_SHAPES\n\n/**\n * The npm scripts a module gets: one per shape a developer runs, which is three of the four.\n *\n * Here rather than in the adapter because the REPORT needs them too, to tell a reader of the\n * console summary where the detail is, and two spellings of one script name is drift nobody\n * notices until a developer types the one that does not exist.\n */\nexport const SCRIPTS = {\n  console: TARGET,\n  json: `${TARGET}:json`,\n  html: `${TARGET}:html`,\n  // ⛔ No entry for the `markdown` shape, deliberately, and this is NOT a gap: these are the npm\n  // scripts a module gets, and markdown is the recap a workflow posts on a pull request, built\n  // from one file per affected module. A developer who wants it by hand gets the console shape,\n  // which says the same thing in less space and writes nothing. A fourth script here would be a\n  // command nobody runs, carried in 198 package.json files.\n} as const\n\n/**\n * What each language the role scans is called on disk.\n *\n * ⚠️ Two lists that MUST agree, and they were maintained separately: the role declares the\n * languages it asks the tool to scan, and the adapter declared the extensions it looks for when\n * deciding whether a module has anything to measure at all. A module that narrowed `languages`\n * would still be probed for the extensions it had removed, and a language added to the preset\n * would never reach the probe. Derived from one source now, with a test that every language maps.\n */\nconst EXTENSIONS_BY_LANGUAGE: Record<string, string[]> = {\n  javascript: ['.js', '.mjs', '.cjs'],\n  typescript: ['.ts'],\n  jsx: ['.jsx'],\n  tsx: ['.tsx'],\n  css: ['.css'],\n  scss: ['.scss'],\n}\n\n/** The file extensions of the languages given, for deciding whether a module has anything to read. */\nexport function extensionsOf(languages: readonly string[]): string[] {\n  return [...new Set(languages.flatMap((language) => EXTENSIONS_BY_LANGUAGE[language] ?? []))]\n}\n\n/** Every language the mapping knows, so a test can hold it against the preset. */\nexport const MAPPED_LANGUAGES = Object.keys(EXTENSIONS_BY_LANGUAGE)\n\nexport type StaticDefaults = {\n  entry: string[]\n  ignore: string[]\n  languages: string[]\n  journeys: Record<string, string[]>\n  duplication: { minTokens: number; minLines: number; kinds: string[]; tests: string[] }\n  deadCode: { minConfidence: number; categories: string[] }\n  graph: { resolution: number }\n  tools: { jscpd: Record<string, unknown> }\n}\n\n/** The role's settings. Read-only here; `defineStaticAnalysis` resolves a module against them. */\nexport const defaults: StaticDefaults = sharedData as StaticDefaults\n\n/**\n * Keys a module declares DIRECTLY rather than through `overrides`, and how each one combines.\n *\n * They are apart because the verb differs: these two are added to and merged, so a team cannot\n * lose what the role ships by declaring its own. Everything else replaces.\n */\nconst DECLARED: Record<string, string> = {\n  entry: 'added to the patterns the role ships, never replacing them',\n  journeys: \"merged by name with the role's\",\n}\n\n/**\n * ⛔ Not a module's to set, and the catalogue says so rather than leaving it absent: a key that is\n * simply missing from a list reads as an oversight, and someone will try it. Passing it is dropped\n * with a message, see `configs/define.ts`.\n */\nconst NOT_YOURS: Record<string, string> = {\n  tools: \"sentinel's own passthrough to the tool underneath; a module never names the vendor\",\n  // ⛔ Listed as movable until it was tried: the catalogue said \"what this module can move\" and\n  // moving it exits 1, because any kind beyond `exact` overlaps the first and the duplicated-line\n  // share then counts the same lines twice. A setting that is refused at run time belongs here,\n  // where the reason is readable, rather than in the list of things to turn.\n  'duplication.kinds': 'only `exact` is supported: any other kind overlaps it and double-counts',\n}\n\n/** A value as a reader compares it: short lists in full, long ones as a count. */\nfunction render(value: unknown): string {\n  if (Array.isArray(value)) {\n    const joined = value.join(', ')\n    return value.length <= 6 && joined.length <= 72 ? joined : `${value.length} patterns`\n  }\n  if (value && typeof value === 'object') return `${Object.keys(value).length} entries`\n  return String(value)\n}\n\n/** One documented key: its path, the role's value, and the note a reader needs. */\nexport interface OverridableSetting {\n  /** The dotted path a module writes, e.g. `duplication.minTokens`. */\n  key: string\n  /** The role's current value, rendered. */\n  value: string\n  /** How it combines, or why it is not available. */\n  note: string\n  /** Where it goes: directly in the config, inside `overrides`, or nowhere. */\n  where: 'declared' | 'overrides' | 'refused'\n}\n\n/**\n * Every setting a module can touch, DERIVED from the values rather than written beside them.\n *\n * Héla's ask, and the reason it is generated: a hand-written list is a second copy of the preset,\n * and the first setting somebody adds makes it a lie that nobody notices, because a stale comment\n * fails no test. Here a new key appears in the next module's config file on its own, with its real\n * value, and `tests/role-layout.test.ts` refuses a key that reaches none of the three groups.\n *\n * It is a snapshot: `--init` leaves an EXISTING config alone, by design, so a module that adopted\n * earlier keeps the catalogue of that day. The report is the live answer, since it prints the value\n * every figure was produced with.\n */\nexport function overridableSettings(from: StaticDefaults = defaults): OverridableSetting[] {\n  const rows: OverridableSetting[] = []\n\n  for (const [key, value] of Object.entries(from)) {\n    if (key in NOT_YOURS) {\n      rows.push({ key, value: render(value), note: NOT_YOURS[key] ?? '', where: 'refused' })\n      continue\n    }\n    if (key in DECLARED) {\n      rows.push({ key, value: render(value), note: DECLARED[key] ?? '', where: 'declared' })\n      continue\n    }\n    // A group is documented by its leaves, because `duplication` whole is not what anyone writes.\n    const leaves =\n      value && typeof value === 'object' && !Array.isArray(value)\n        ? Object.entries(value).map(([leaf, own]) => ({ key: `${key}.${leaf}`, own }))\n        : [{ key, own: value }]\n    for (const leaf of leaves) {\n      /*\n       * ⛔ A LEAF can be refused too, and this check was missing. `NOT_YOURS` holds the dotted key\n       * `duplication.kinds`, but the test above only ran on top-level keys: `duplication` is not\n       * in `NOT_YOURS`, so every one of its leaves fell through to here and the catalogue printed\n       * `duplication.kinds` under \"What this module can move\".\n       *\n       * ⚠️ A developer who followed it got exit 1 on the next run, with a message refusing the\n       * very setting the generated config had invited them to write. The test that was supposed\n       * to cover this passed because the key DID reach a group, just the wrong one.\n       */\n      if (leaf.key in NOT_YOURS) {\n        rows.push({\n          key: leaf.key,\n          value: render(leaf.own),\n          note: NOT_YOURS[leaf.key] ?? '',\n          where: 'refused',\n        })\n        continue\n      }\n      rows.push({ key: leaf.key, value: render(leaf.own), note: 'replaced', where: 'overrides' })\n    }\n  }\n\n  return rows\n}\n","/**\n * `defineStaticAnalysis`: what a module imports to declare its own static analysis settings.\n *\n * ```js\n * // static-analysis.config.mjs\n * import { defineStaticAnalysis } from '@hublo/sentinel/static-analysis'\n *\n * export default defineStaticAnalysis({\n *   root: import.meta.dirname,\n *   entry: ['**\\/*.steps.ts'],\n *   journeys: { planning: ['src/planning/**'] },\n * })\n * ```\n *\n * ## Why a function and not `{ ...baseConfig, ... }`\n *\n * A spread is SHALLOW, so a module writing `deadCode: { minConfidence: 80 }` would replace the\n * whole block and silently lose `categories`. And the flattening happens in the module's file,\n * before this package ever sees the object, so nothing here could tell \"set one key, keep the\n * rest\" from \"set one key, drop the rest\". A function receives the module's INTENT, the keys it\n * actually passed, and merges them here. Second reason: the defaults are never copied into a\n * module, so changing one reaches every module at the next release instead of leaving 108 stale\n * copies behind.\n *\n * Same shape as `reactTestConfig` in the test role, for the same reasons.\n *\n * ## Two semantics, one obvious and one deliberate\n *\n * `entry` and `journeys` are FACTS a team declares, and they ADD to what this role ships: no\n * module can lose `**\\/*.integration-spec.ts` by declaring a third pattern, which matters\n * because that one pattern is the difference between 33.4% and 1.0% of dead code on a real\n * service (see `defaults.ts`).\n *\n * `overrides` REPLACES, including those lists. It is the seam for the day a team has a real\n * reason, it is not documented anywhere a developer would meet it, and every path it sets is\n * recorded in `moved` so the report can print `(module)` next to the value. Without that trace\n * two modules stop being comparable and nobody knows. It reaches every setting EXCEPT the vendor\n * passthrough, for the reason stated on the field itself.\n */\nimport { isPlainObject } from '../../../shared/deep-merge.js'\nimport { defaults, type StaticDefaults } from '../preset-data.js'\n\ntype DeepPartial<T> = { [K in keyof T]?: T[K] extends object ? DeepPartial<T[K]> : T[K] }\n\n/** What a module's config file passes. Everything is optional, including the file itself. */\nexport interface StaticAnalysisInput {\n  /** The module's own directory, normally `import.meta.dirname`. */\n  root?: string\n  /** Files that run although nothing imports them. ADDED to the shipped patterns. */\n  entry?: string[]\n  /**\n   * Named journeys, as `{ name: [globs] }`. MERGED by name with any shipped ones.\n   *\n   * ⛔ **No pass reads this yet, and the generated config stub no longer asks for it.** It is the\n   * seam for the product axis, where a figure is reported per journey rather than per module, and\n   * that is V2 work tracked in issue #98. It stays accepted so a module that already declared one\n   * is not broken, and `--inspect` echoes it back, but nothing measures against it.\n   *\n   * It was in the stub for a while, under a comment telling every adopting team to fill it in. A\n   * team that did would have waited for a breakdown that never came and concluded their globs were\n   * wrong. Asking for something nothing consumes is worse than not offering it.\n   */\n  journeys?: Record<string, string[]>\n  /**\n   * The seam. Replaces whatever it names, and every path it sets lands in `moved`.\n   *\n   * ⛔ `tools` is excluded, and the reason is the whole point of translating the vocabulary: a\n   * module knows the ROLE, not the tool underneath it. A key named after the vendor would mean\n   * nothing to the person reading their own config file, and showing it would invite them to learn\n   * a name we are working to keep out of their world. The passthrough still exists, on sentinel's\n   * side, for a preset that needs a vendor option; a module that genuinely needs one gets a key in\n   * OUR vocabulary, which is the right friction because it goes through a review instead of\n   * spreading silently.\n   */\n  overrides?: DeepPartial<Omit<StaticDefaults, 'tools'>>\n}\n\nexport interface ResolvedStaticConfig extends StaticDefaults {\n  /** The module's directory, or null when its config file did not say. */\n  root: string | null\n  /**\n   * Dotted paths the module set through `overrides`, so the report can mark them. Sorted, so\n   * two runs on the same config produce the same report.\n   */\n  moved: string[]\n}\n\n/**\n * Merge `patch` into `base`, recursively, patch winning.\n *\n * Not the `deepMerge` this repo once had: that one existed for WRITING a module's json and was\n * replaced by an in-place jsonc edit, which is why only `isPlainObject` survived. This is the\n * read side, which has no file to preserve and only has to resolve two objects into one.\n *\n * Arrays are replaced, never concatenated. Additive behaviour is a decision about a specific\n * key, which `defineStaticAnalysis` makes explicitly for `entry`, rather than a property of the\n * merge: a merge that silently concatenates cannot express \"replace this list\", and a team\n * reaching for `overrides` is asking for exactly that.\n */\nfunction mergeInto<T>(base: T, patch: unknown): T {\n  if (!isPlainObject(patch)) return base\n  if (!isPlainObject(base)) return patch as T\n  const out: Record<string, unknown> = { ...base }\n  for (const [key, value] of Object.entries(patch)) {\n    out[key] = isPlainObject(value) ? mergeInto(out[key], value) : value\n  }\n  return out as T\n}\n\n/** Every leaf path in `patch`, dotted, so a reader can be told what the module decided. */\nfunction leafPaths(patch: unknown, prefix = ''): string[] {\n  if (!isPlainObject(patch)) return prefix ? [prefix] : []\n  return Object.entries(patch).flatMap(([key, value]) =>\n    leafPaths(value, prefix ? `${prefix}.${key}` : key),\n  )\n}\n\n/** The same list with duplicates dropped, keeping the first occurrence's order. */\nfunction unique(values: string[]): string[] {\n  return [...new Set(values)]\n}\n\n/**\n * Drop the vendor passthrough from what a module sent.\n *\n * ⚠️ Enforced here and not by the type, because the type cannot: a module's config file is `.mjs`,\n * so nothing type-checks it, and `Omit` on the input would be documentation that compiles away. A\n * `tools` key written there is dropped and NAMED on stderr rather than ignored, so a developer who\n * found the key somewhere learns why it did nothing instead of concluding the role is broken.\n */\nfunction withoutVendorKeys(overrides: unknown): unknown {\n  if (!isPlainObject(overrides) || !('tools' in overrides)) return overrides\n  const { tools: _vendor, ...rest } = overrides\n  process.stderr.write(\n    'sentinel static-analysis: ignoring `overrides.tools` from this module. The tool underneath ' +\n      \"the role is not part of a module's surface; if a setting is missing, it needs a key of \" +\n      'its own.\\n',\n  )\n  return rest\n}\n\n/** Resolve a module's declaration against this role's defaults. */\nexport function defineStaticAnalysis(input: StaticAnalysisInput = {}): ResolvedStaticConfig {\n  const declared: StaticDefaults = {\n    ...defaults,\n    entry: unique([...defaults.entry, ...(input.entry ?? [])]),\n    journeys: { ...defaults.journeys, ...(input.journeys ?? {}) },\n  }\n  const overrides = withoutVendorKeys(input.overrides)\n\n  return {\n    ...mergeInto(declared, overrides),\n    root: input.root ?? null,\n    moved: leafPaths(overrides).sort(),\n  }\n}\n"],"mappings":";AAcO,SAAS,cAAc,OAAkD;AAC9E,SAAO,OAAO,UAAU,YAAY,UAAU,QAAQ,CAAC,MAAM,QAAQ,KAAK;AAC5E;;;ACcO,IAAM,QAAQ,CAAC,OAAO,WAAW,QAAQ,WAAW,YAAY,UAAU,QAAQ;AAIlF,IAAM,UAAU;AAAA,EACrB;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AACF;AAmBO,IAAM,uBAA0C,CAAC,KAAK;AAGtD,IAAM,oBAAuC,QAAQ;AAAA,EAC1D,CAAC,WAAW,CAAC,qBAAqB,SAAS,MAAM;AACnD;AAGO,IAAM,eAAe,CAAC,SAAS,QAAQ,UAAU,QAAQ,OAAO;AAahE,IAAM,gBAAgB,CAAC,WAAW,QAAQ,QAAQ,UAAU;;;ACpFnE;AAAA,EACE,OAAS;AAAA,IACP;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,EACF;AAAA,EACA,QAAU;AAAA,IACR;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,EACF;AAAA,EACA,WAAa,CAAC,cAAc,cAAc,OAAO,OAAO,OAAO,MAAM;AAAA,EACrE,UAAY,CAAC;AAAA,EACb,aAAe;AAAA,IACb,WAAa;AAAA,IACb,UAAY;AAAA,IACZ,OAAS,CAAC,OAAO;AAAA,IACjB,OAAS;AAAA,MACP;AAAA,MACA;AAAA,MACA;AAAA,IACF;AAAA,EACF;AAAA,EACA,UAAY;AAAA,IACV,eAAiB;AAAA,IACjB,YAAc,CAAC,eAAe,iBAAiB,iBAAiB,eAAe;AAAA,EACjF;AAAA,EACA,OAAS;AAAA,IACP,YAAc;AAAA,EAChB;AAAA,EACA,OAAS;AAAA,IACP,OAAS,CAAC;AAAA,EACZ;AACF;;;ACgHO,IAAM,aAAa;AAGnB,IAAM,SAAS;AASf,IAAM,SAAS;AASf,IAAM,UAAU;AAAA,EACrB,SAAS;AAAA,EACT,MAAM,GAAG,MAAM;AAAA,EACf,MAAM,GAAG,MAAM;AAAA;AAAA;AAAA;AAAA;AAAA;AAMjB;AAWA,IAAM,yBAAmD;AAAA,EACvD,YAAY,CAAC,OAAO,QAAQ,MAAM;AAAA,EAClC,YAAY,CAAC,KAAK;AAAA,EAClB,KAAK,CAAC,MAAM;AAAA,EACZ,KAAK,CAAC,MAAM;AAAA,EACZ,KAAK,CAAC,MAAM;AAAA,EACZ,MAAM,CAAC,OAAO;AAChB;AAGO,SAAS,aAAa,WAAwC;AACnE,SAAO,CAAC,GAAG,IAAI,IAAI,UAAU,QAAQ,CAAC,aAAa,uBAAuB,QAAQ,KAAK,CAAC,CAAC,CAAC,CAAC;AAC7F;AAGO,IAAM,mBAAmB,OAAO,KAAK,sBAAsB;AAc3D,IAAM,WAA2B;AAQxC,IAAM,WAAmC;AAAA,EACvC,OAAO;AAAA,EACP,UAAU;AACZ;AAOA,IAAM,YAAoC;AAAA,EACxC,OAAO;AAAA;AAAA;AAAA;AAAA;AAAA,EAKP,qBAAqB;AACvB;AAGA,SAAS,OAAO,OAAwB;AACtC,MAAI,MAAM,QAAQ,KAAK,GAAG;AACxB,UAAM,SAAS,MAAM,KAAK,IAAI;AAC9B,WAAO,MAAM,UAAU,KAAK,OAAO,UAAU,KAAK,SAAS,GAAG,MAAM,MAAM;AAAA,EAC5E;AACA,MAAI,SAAS,OAAO,UAAU,SAAU,QAAO,GAAG,OAAO,KAAK,KAAK,EAAE,MAAM;AAC3E,SAAO,OAAO,KAAK;AACrB;AA0BO,SAAS,oBAAoB,OAAuB,UAAgC;AACzF,QAAM,OAA6B,CAAC;AAEpC,aAAW,CAAC,KAAK,KAAK,KAAK,OAAO,QAAQ,IAAI,GAAG;AAC/C,QAAI,OAAO,WAAW;AACpB,WAAK,KAAK,EAAE,KAAK,OAAO,OAAO,KAAK,GAAG,MAAM,UAAU,GAAG,KAAK,IAAI,OAAO,UAAU,CAAC;AACrF;AAAA,IACF;AACA,QAAI,OAAO,UAAU;AACnB,WAAK,KAAK,EAAE,KAAK,OAAO,OAAO,KAAK,GAAG,MAAM,SAAS,GAAG,KAAK,IAAI,OAAO,WAAW,CAAC;AACrF;AAAA,IACF;AAEA,UAAM,SACJ,SAAS,OAAO,UAAU,YAAY,CAAC,MAAM,QAAQ,KAAK,IACtD,OAAO,QAAQ,KAAK,EAAE,IAAI,CAAC,CAAC,MAAM,GAAG,OAAO,EAAE,KAAK,GAAG,GAAG,IAAI,IAAI,IAAI,IAAI,EAAE,IAC3E,CAAC,EAAE,KAAK,KAAK,MAAM,CAAC;AAC1B,eAAW,QAAQ,QAAQ;AAWzB,UAAI,KAAK,OAAO,WAAW;AACzB,aAAK,KAAK;AAAA,UACR,KAAK,KAAK;AAAA,UACV,OAAO,OAAO,KAAK,GAAG;AAAA,UACtB,MAAM,UAAU,KAAK,GAAG,KAAK;AAAA,UAC7B,OAAO;AAAA,QACT,CAAC;AACD;AAAA,MACF;AACA,WAAK,KAAK,EAAE,KAAK,KAAK,KAAK,OAAO,OAAO,KAAK,GAAG,GAAG,MAAM,YAAY,OAAO,YAAY,CAAC;AAAA,IAC5F;AAAA,EACF;AAEA,SAAO;AACT;;;AC9OA,SAAS,UAAa,MAAS,OAAmB;AAChD,MAAI,CAAC,cAAc,KAAK,EAAG,QAAO;AAClC,MAAI,CAAC,cAAc,IAAI,EAAG,QAAO;AACjC,QAAM,MAA+B,EAAE,GAAG,KAAK;AAC/C,aAAW,CAAC,KAAK,KAAK,KAAK,OAAO,QAAQ,KAAK,GAAG;AAChD,QAAI,GAAG,IAAI,cAAc,KAAK,IAAI,UAAU,IAAI,GAAG,GAAG,KAAK,IAAI;AAAA,EACjE;AACA,SAAO;AACT;AAGA,SAAS,UAAU,OAAgB,SAAS,IAAc;AACxD,MAAI,CAAC,cAAc,KAAK,EAAG,QAAO,SAAS,CAAC,MAAM,IAAI,CAAC;AACvD,SAAO,OAAO,QAAQ,KAAK,EAAE;AAAA,IAAQ,CAAC,CAAC,KAAK,KAAK,MAC/C,UAAU,OAAO,SAAS,GAAG,MAAM,IAAI,GAAG,KAAK,GAAG;AAAA,EACpD;AACF;AAGA,SAAS,OAAO,QAA4B;AAC1C,SAAO,CAAC,GAAG,IAAI,IAAI,MAAM,CAAC;AAC5B;AAUA,SAAS,kBAAkB,WAA6B;AACtD,MAAI,CAAC,cAAc,SAAS,KAAK,EAAE,WAAW,WAAY,QAAO;AACjE,QAAM,EAAE,OAAO,SAAS,GAAG,KAAK,IAAI;AACpC,UAAQ,OAAO;AAAA,IACb;AAAA,EAGF;AACA,SAAO;AACT;AAGO,SAAS,qBAAqB,QAA6B,CAAC,GAAyB;AAC1F,QAAM,WAA2B;AAAA,IAC/B,GAAG;AAAA,IACH,OAAO,OAAO,CAAC,GAAG,SAAS,OAAO,GAAI,MAAM,SAAS,CAAC,CAAE,CAAC;AAAA,IACzD,UAAU,EAAE,GAAG,SAAS,UAAU,GAAI,MAAM,YAAY,CAAC,EAAG;AAAA,EAC9D;AACA,QAAM,YAAY,kBAAkB,MAAM,SAAS;AAEnD,SAAO;AAAA,IACL,GAAG,UAAU,UAAU,SAAS;AAAA,IAChC,MAAM,MAAM,QAAQ;AAAA,IACpB,OAAO,UAAU,SAAS,EAAE,KAAK;AAAA,EACnC;AACF;","names":[]}