@sarj/eslint-plugin 7.1.0 → 9.0.0

package/dist/index.d.cts

@@ -1,5 +1,19 @@
 import * as _typescript_eslint_utils_ts_eslint from '@typescript-eslint/utils/ts-eslint';
 
+/**
+ * @fileoverview _retired — a withdrawn rule name is burned, not recycled, because a consumer's `eslint-disable` comment or suppressions entry still names it.
+ *
+ * Evidence: https://github.com/sarj-ai/standards/blob/main/docs/rules/_retired.md
+ */
+/** Why a name was withdrawn, and in which release. */
+interface RetiredRule {
+    /** The plugin version whose release removed the rule. */
+    readonly removedIn: string;
+    /** One line a consumer can act on: why it went, and what (if anything) replaced it. */
+    readonly reason: string;
+}
+declare const retiredRules: Readonly<Record<string, RetiredRule>>;
+
 /**
  * @fileoverview _comment-wall — the shared judgement behind the comment-VOLUME rules: a run of member comments that mostly re-spell their members is a wall.
  *
@@ -62,7 +76,9 @@ interface RuleOptions {
 }
 
 /**
- * @fileoverview _renames — a renamed rule keeps its old name registered as a deprecated alias, because a name that simply vanishes reads as growth to a shrink-only baseline.
+ * @fileoverview _renames — every rule this plugin has renamed, old name to new; the old names no longer resolve, so this map is what says what to write instead.
+ *
+ * It feeds `scripts/sync-rule-ledger.py`, which turns each entry into a `renamed` row of the shipped `rule-ledger.json` that `sarj-lint-configs doctor` reads.
  *
  * Evidence: https://github.com/sarj-ai/standards/blob/main/docs/rules/_renames.md
  */
@@ -255,7 +271,6 @@ declare const rules: {
         name: string;
     };
 };
-type RuleModule = (typeof rules)[keyof typeof rules];
 declare const recommendedRules: {
     readonly "@sarj/enforce-file-structure": "warn";
     readonly "@sarj/no-async-callback-in-wait-for": "warn";
@@ -377,13 +392,9 @@ type FlatPreset = {
 declare const plugin: {
     meta: {
         readonly name: "@sarj/eslint-plugin";
-        readonly version: "7.1.0";
+        readonly version: "9.0.0";
     };
     rules: {
-        "jsdoc-restates-signature": RuleModule;
-        "no-async-callback-in-waitfor": RuleModule;
-        "strict-test-assertions": RuleModule;
-        "trailing-value-narration": RuleModule;
         "enforce-file-structure": _typescript_eslint_utils_ts_eslint.RuleModule<"importsFirst" | "useServerDirective", readonly [], unknown, _typescript_eslint_utils_ts_eslint.RuleListener> & {
             name: string;
         };
@@ -565,10 +576,11 @@ declare const plugin: {
             name: string;
         };
     };
+    retiredRules: Readonly<Record<string, RetiredRule>>;
     configs: {
         recommended: FlatPreset;
         strict: FlatPreset;
     };
 };
 
-export { plugin as default, recommendedRules, renamedRules, rules, strictRules };
+export { type RetiredRule, plugin as default, recommendedRules, renamedRules, retiredRules, rules, strictRules };

package/dist/index.d.ts

@@ -1,5 +1,19 @@
 import * as _typescript_eslint_utils_ts_eslint from '@typescript-eslint/utils/ts-eslint';
 
+/**
+ * @fileoverview _retired — a withdrawn rule name is burned, not recycled, because a consumer's `eslint-disable` comment or suppressions entry still names it.
+ *
+ * Evidence: https://github.com/sarj-ai/standards/blob/main/docs/rules/_retired.md
+ */
+/** Why a name was withdrawn, and in which release. */
+interface RetiredRule {
+    /** The plugin version whose release removed the rule. */
+    readonly removedIn: string;
+    /** One line a consumer can act on: why it went, and what (if anything) replaced it. */
+    readonly reason: string;
+}
+declare const retiredRules: Readonly<Record<string, RetiredRule>>;
+
 /**
  * @fileoverview _comment-wall — the shared judgement behind the comment-VOLUME rules: a run of member comments that mostly re-spell their members is a wall.
  *
@@ -62,7 +76,9 @@ interface RuleOptions {
 }
 
 /**
- * @fileoverview _renames — a renamed rule keeps its old name registered as a deprecated alias, because a name that simply vanishes reads as growth to a shrink-only baseline.
+ * @fileoverview _renames — every rule this plugin has renamed, old name to new; the old names no longer resolve, so this map is what says what to write instead.
+ *
+ * It feeds `scripts/sync-rule-ledger.py`, which turns each entry into a `renamed` row of the shipped `rule-ledger.json` that `sarj-lint-configs doctor` reads.
  *
  * Evidence: https://github.com/sarj-ai/standards/blob/main/docs/rules/_renames.md
  */
@@ -255,7 +271,6 @@ declare const rules: {
         name: string;
     };
 };
-type RuleModule = (typeof rules)[keyof typeof rules];
 declare const recommendedRules: {
     readonly "@sarj/enforce-file-structure": "warn";
     readonly "@sarj/no-async-callback-in-wait-for": "warn";
@@ -377,13 +392,9 @@ type FlatPreset = {
 declare const plugin: {
     meta: {
         readonly name: "@sarj/eslint-plugin";
-        readonly version: "7.1.0";
+        readonly version: "9.0.0";
     };
     rules: {
-        "jsdoc-restates-signature": RuleModule;
-        "no-async-callback-in-waitfor": RuleModule;
-        "strict-test-assertions": RuleModule;
-        "trailing-value-narration": RuleModule;
         "enforce-file-structure": _typescript_eslint_utils_ts_eslint.RuleModule<"importsFirst" | "useServerDirective", readonly [], unknown, _typescript_eslint_utils_ts_eslint.RuleListener> & {
             name: string;
         };
@@ -565,10 +576,11 @@ declare const plugin: {
             name: string;
         };
     };
+    retiredRules: Readonly<Record<string, RetiredRule>>;
     configs: {
         recommended: FlatPreset;
         strict: FlatPreset;
     };
 };
 
-export { plugin as default, recommendedRules, renamedRules, rules, strictRules };
+export { type RetiredRule, plugin as default, recommendedRules, renamedRules, retiredRules, rules, strictRules };