@mnci/cli 1.11.1 → 1.11.2

package/README.md

@@ -223,8 +223,11 @@ would make `npm run lint` and `npm run format:check` mutually unsatisfiable.
 Choosing Prettier means accepting its call there.
 
 `npm run lint` checks code quality; `npm run format` (write) and
-`npm run format:check` (CI-safe) handle formatting. The CI runs lint/test/build
-only — formatting is left as a local/pre-commit step.
+`npm run format:check` (CI-safe) handle formatting. **Both run in CI**, as
+separate steps: ESLint is configured for correctness only and deliberately
+reports nothing about formatting, so Prettier needs a gate of its own or the
+whole formatting opinion is advisory and a workspace drifts out of compliance
+with no signal anywhere.
 
 TypeScript is not a question — every workspace runs the **dual compiler** from
 [Nx's TS 7 guide](https://nx.dev/docs/technologies/typescript/guides/typescript-7):

package/dist/cli.js

@@ -1523,11 +1523,17 @@ steps:
   - script: npx nx sync:check
     displayName: Verify the workspace is synced (run 'npx nx sync' locally and commit if this fails)
 
-  # One verify for every run (PR and main). \`npm run lint\` abstracts the chosen
-  # linter (eslint via nx, or oxlint), so the pipeline needs no linter branch;
-  # Nx cache makes unchanged test/build projects instant.
+  # One verify for every run (PR and main). Nx cache makes unchanged test/build
+  # projects instant.
   - script: npm run lint
     displayName: Lint
+
+  # Prettier owns ALL formatting in this workspace, so it needs a gate of its
+  # own: ESLint is configured for correctness only and deliberately reports
+  # nothing about formatting. Without this step the entire formatting opinion is
+  # advisory, and a workspace drifts out of compliance with no signal anywhere.
+  - script: npm run format:check
+    displayName: Check formatting (run 'npm run format' locally to fix)
   # \`lint\` here also runs any Nx lint targets \`npm run lint\` does not cover \u2014
   # notably Python's ruff (every Python project owns a hand-authored \`lint\`
   # target). For the eslint stack the JS lint runs twice, but Nx caches the
@@ -1694,11 +1700,18 @@ jobs:
       - run: npx nx sync:check
         name: Verify the workspace is synced (run 'npx nx sync' locally and commit if this fails)
 
-      # One verify for every run (PR and main). \`npm run lint\` abstracts the chosen
-      # linter (eslint via nx, or oxlint), so the workflow needs no linter branch;
-      # Nx cache makes unchanged test/build projects instant.
+      # One verify for every run (PR and main). Nx cache makes unchanged
+      # test/build projects instant.
       - run: npm run lint
         name: Lint
+
+      # Prettier owns ALL formatting in this workspace, so it needs a gate of
+      # its own: ESLint is configured for correctness only and deliberately
+      # reports nothing about formatting. Without this step the entire
+      # formatting opinion is advisory, and a workspace drifts out of
+      # compliance with no signal anywhere.
+      - run: npm run format:check
+        name: Check formatting (run 'npm run format' locally to fix)
       # \`lint\` here also runs any Nx lint targets \`npm run lint\` does not cover \u2014
       # notably Python's ruff (every Python project owns a hand-authored \`lint\`
       # target). For the eslint stack the JS lint runs twice, but Nx caches the