@sarj/eslint-plugin 9.10.0 → 9.12.1

package/README.md

@@ -1,5 +1,12 @@
 # @sarj/eslint-plugin
 
+## New in 9.11.0 — disabled test assertions
+
+`no-comment-cruft` now recognizes commented-out `expect(...)` chains and
+`assert(...)` calls. A disabled assertion leaves a collected test passing while
+verifying nothing. JSDoc and assertion examples introduced by prose remain
+exempt, as do active assertions.
+
 ## New in 9.9.0 — static Next.js matchers
 
 `require-static-next-matcher` rejects runtime expressions in exported
@@ -123,9 +130,17 @@ platform too.
 |---|---|---|
 | `no-hand-rolled-spinner` | Intrinsic elements styled as Tailwind border-ring loading spinners outside the design system. | error / error |
 | `prefer-input-group-search` | Search icons and shared Input controls composed without the shared InputGroup primitive. | error / error |
+| `prefer-shadcn-primitives` | Deterministically visible raw JSX controls used instead of shared shadcn primitives. Unknown and hidden input types are excluded. | application profile: warn |
 | `require-static-next-matcher` | Dynamic values in exported Next.js middleware and proxy matcher configuration. | error / error |
 | `no-hand-rolled-sleep` | `new Promise((r) => setTimeout(r, ms))` in any spelling, and an uncleared `Promise.race`/`Promise.any` timeout arm. Options: `checkClientModules` (default `false`), `allowIn`. | warn / error |
 
+`prefer-shadcn-primitives` is application-only because generic plugin consumers
+may use another design system or intentionally expose native controls. It starts
+at warning with 53 measured adoption findings across four application-profile
+consumers; two additional consumers are clean. Promote it only after those
+findings are removed, and keep it disabled inside `components/ui` and
+`components/design-system`, where shared primitives must wrap native elements.
+
 ## New in 2.14.0 — `no-tautological-expect`
 
 The TS half of SARJ057. An `expect(...)` whose operands are all literals has