eslint-plugin-traceability 1.21.0 → 1.22.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eslint-plugin-traceability",
-  "version": "1.21.0",
+  "version": "1.22.0",
   "description": "A customizable ESLint plugin that enforces traceability annotations in your code, ensuring each implementation is linked to its requirement or test case.",
   "main": "lib/src/index.js",
   "types": "lib/src/index.d.ts",
@@ -28,6 +28,8 @@
     "lint:require-built-plugin": "npm run lint-plugin-guard",
     "lint": "eslint --config eslint.config.js \"src/**/*.{js,ts}\" \"tests/**/*.{js,ts}\" --max-warnings=0",
     "test": "jest --ci --bail",
+    "test:unit": "jest --ci --bail --testPathPatterns='tests/(rules|maintenance|utils|unit)' --testPathIgnorePatterns='integration'",
+    "test:integration": "jest --ci --bail --testPathPatterns='tests/integration'",
     "ci-verify": "npm run type-check && npm run lint && npm run format:check && npm run duplication && npm run check:traceability && npm test && npm run audit:ci && npm run safety:deps",
     "ci-verify:full": "npm run check:traceability && npm run safety:deps && npm run audit:ci && npm run build && npm run type-check && npm run lint-plugin-check && npm run lint -- --max-warnings=0 && npm run duplication && npm run test -- --coverage && npm run format:check && npm audit --omit=dev --audit-level=high && npm run audit:dev-high && npm run check:ci-artifacts",
     "ci-verify:fast": "npm run type-check && npm run check:traceability && npm run duplication && jest --ci --bail --passWithNoTests --testPathPatterns 'tests/(rules|maintenance)'",
@@ -43,11 +45,14 @@
     "check:ci-artifacts": "node scripts/check-no-tracked-ci-artifacts.js",
     "security:secrets": "secretlint \"**/*\"",
     "smoke-test": "./scripts/smoke-test.sh",
+    "smoke:runtime": "./scripts/runtime-smoke.sh",
+    "run:cli": "node lib/src/maintenance/cli.js",
     "debug:cli": "node scripts/cli-debug.js",
     "debug:require-story": "node scripts/debug-require-story.js",
     "debug:repro": "node scripts/debug-repro.js",
     "report:eslint-suppressions": "node scripts/report-eslint-suppressions.js",
-    "check:scripts": "node scripts/validate-scripts-nonempty.js"
+    "check:scripts": "node scripts/validate-scripts-nonempty.js",
+    "voder": "voder --help"
   },
   "lint-staged": {
     "src/**/*.{js,jsx,ts,tsx,json,md}": [
@@ -71,29 +76,32 @@
   },
   "homepage": "https://github.com/voder-ai/eslint-plugin-traceability#readme",
   "devDependencies": {
-    "@eslint/js": "^9.39.1",
+    "@eslint/js": "^9.39.2",
+    "@secretlint/secretlint-rule-preset-recommend": "11.2.5",
     "@semantic-release/changelog": "^6.0.3",
     "@semantic-release/git": "^10.0.1",
     "@semantic-release/github": "12.0.2",
-    "@semantic-release/npm": "13.1.2",
+    "@semantic-release/npm": "^13.1.3",
     "@types/eslint": "^9.6.1",
     "@types/jest": "^30.0.0",
-    "@types/node": "^24.10.1",
+    "@types/node": "^25.0.3",
     "@typescript-eslint/parser": "^8.46.4",
     "@typescript-eslint/utils": "^8.46.4",
     "actionlint": "^2.0.6",
-    "dry-aged-deps": "^2.3.1",
-    "eslint": "^9.39.1",
+    "dry-aged-deps": "^2.5.1",
+    "eslint": "^9.39.2",
     "husky": "^9.1.7",
     "jest": "^30.2.0",
     "jscpd": "^4.0.5",
     "lint-staged": "^16.2.7",
     "prettier": "^3.7.4",
+    "secretlint": "11.2.5",
     "semantic-release": "25.0.2",
     "ts-jest": "^29.4.6",
-    "typescript": "^5.9.3",
-    "secretlint": "11.2.5",
-    "@secretlint/secretlint-rule-preset-recommend": "11.2.5"
+    "typescript": "^5.9.3"
+  },
+  "optionalDependencies": {
+    "@voder-ai/voder-ai": "^5.6.1"
   },
   "peerDependencies": {
     "eslint": "^9.0.0"

package/user-docs/api-reference.md

@@ -108,7 +108,7 @@ Behavior notes:
   - Valid locations for `@story` / `@req` annotations include:
     - Line or block comments immediately before the `else if` line.
     - Comment-only lines between the `else if (condition)` and the opening `{` of the consequent block (for styles where the condition and block are on separate lines).
-    - The first comment-only lines inside the consequent block body, which is where formatters like Prettier often move comments when they wrap long `else if` conditions. For a concrete before/after example of this formatter-aware behavior, see [user-docs/examples.md](examples.md) (section **6. Branch annotations with if/else/else-if and Prettier**).
+    - The first comment-only lines inside the consequent block body, which is where formatters like Prettier often move comments when they wrap long `else if` conditions. For a concrete before/after example of this formatter-aware behavior, see [Examples](examples.md) (section **6. Branch annotations with if/else/else-if and Prettier**).
   - When annotations appear in more than one of these locations, the rule prefers the comments immediately before the `else if` line, then comments between the condition and the block, and finally comments inside the block body. This precedence is designed to closely mirror real-world formatter behavior and matches the formatter-aware scenarios described in stories 025.0 and 026.0.
   - When auto-fixing missing annotations on an `else if` branch, the rule inserts placeholder comments as the first comment-only line inside the consequent block body (just after the opening `{`), which is a stable location under Prettier and similar formatters. As with catch clauses, a single `@supports` annotation placed in any of these accepted locations is treated as equivalent to having both `@story` and `@req` comments for that branch, with deep format and existence checks delegated to the other validation rules.
 
@@ -117,7 +117,7 @@ Placement modes:
 - `"before"` mode preserves the existing semantics described above, including the dual-position behavior for `catch` and `else if` branches where comments immediately before the branch and the first comment-only lines inside the block are both acceptable and validated according to their existing precedence rules.
 - `"inside"` mode standardizes on the first comment-only lines inside supported branch blocks (`if`/`else if`, loops, `catch`, and `try`) for validation and auto-fix insertion. This placement is designed to work well with Prettier and other formatters, while the current implementation still treats many before-branch annotations as needing migration and may, in corner cases where it cannot confidently rewrite placement, insert new placeholder comments above the branch rather than moving existing ones. Story `028.0-DEV-ANNOTATION-PLACEMENT-STANDARDIZATION` standardizes inside-brace placement for supported branch constructs; function-level rules continue to use before-function annotations until a future story extends the same standard to functions.
 
-For a concrete illustration of how these rules interact with Prettier, see the formatter-aware if/else/else-if example in [user-docs/examples.md](examples.md) (section **6. Branch annotations with if/else/else-if and Prettier**), which shows both the hand-written and formatted code that the rule considers valid.
+For a concrete illustration of how these rules interact with Prettier, see the formatter-aware if/else/else-if example in [examples.md](examples.md) (section **6. Branch annotations with if/else/else-if and Prettier**), which shows both the hand-written and formatted code that the rule considers valid.
 
 These behaviors are intentionally limited to `catch` clauses and `else if` branches; other branch types (plain `if`, `else`, loops, and `switch` cases) continue to use the simpler "comments immediately before the branch" association model for both validation and auto-fix placement.