eslint-plugin-traceability 1.0.3 → 1.0.5

package/docs/decisions/006-semantic-release-for-automated-publishing.accepted.md

@@ -0,0 +1,227 @@
+---
+status: "accepted"
+date: 2025-11-17
+decision-makers: [Development Team]
+consulted:
+  [
+    semantic-release Documentation,
+    Conventional Commits Specification,
+    GitHub Actions Best Practices,
+    npm Publishing Guidelines,
+  ]
+informed: [Project Stakeholders, CI/CD Pipeline Maintainers]
+---
+
+# Semantic Release for Automated Publishing
+
+## Context and Problem Statement
+
+The current automated version bumping strategy (ADR 004) has several limitations that impact maintainability and developer experience:
+
+1. **Single Increment Logic**: The CI/CD pipeline only increments the version once, requiring complex loop logic to handle cases where multiple increments are needed (e.g., when both 1.0.3 and 1.0.4 already exist on npm)
+
+2. **No Semantic Version Determination**: The system only performs patch increments and cannot automatically determine when minor or major version bumps are appropriate based on the nature of changes
+
+3. **Missing Release Management**: No automatic git tagging, release notes, or CHANGELOG.md generation, reducing traceability and release visibility
+
+4. **Workflow Complexity**: The custom version increment logic in GitHub Actions is becoming complex and error-prone, potentially violating workflow validation best practices established in ADR 005
+
+5. **Package.json/npm Version Drift**: The package.json version in the repository can lag behind the published npm version, creating confusion about the actual release state
+
+The current approach was designed as a temporary solution to prevent npm publish failures, but its limitations suggest that a more comprehensive release automation strategy is needed.
+
+## Decision Drivers
+
+- Need for proper semantic version determination based on change significance
+- Automatic generation of release notes and changelog maintenance
+- Git tag creation for release tracking and traceability
+- Elimination of complex custom version increment logic in CI/CD workflows
+- Integration with conventional commit standards for automated version type detection
+- Prevention of unnecessary publishing when no changes warrant a release
+- Alignment with npm ecosystem best practices for release management
+- Simplification of GitHub Actions workflow to improve maintainability and validation compliance
+
+## Considered Options
+
+- Enhance current in-memory version increment approach with loop logic
+- Implement semantic-release with conventional commits
+- Switch to git write-back approach with automated tagging
+- Implement manual release workflow with GitHub releases
+
+## Decision Outcome
+
+Chosen option: "semantic-release with conventional commits", because it provides comprehensive release automation, proper semantic versioning, automated changelog generation, and eliminates the need for complex custom version logic while following industry standards.
+
+### Implementation Strategy
+
+1. **Install and Configure semantic-release**:
+   - Add `semantic-release` and related plugins as development dependencies
+   - Configure semantic-release with conventional commits preset
+   - Set up plugins for npm publishing, git tagging, and changelog generation
+
+2. **Establish Conventional Commit Standards**:
+   - Adopt conventional commit message format for semantic version determination
+   - Configure semantic-release to analyze commit messages for version impact
+   - Document commit message guidelines for contributors
+
+3. **Update CI/CD Pipeline**:
+   - Replace custom version increment logic with semantic-release execution
+   - Configure semantic-release to run on main branch pushes
+   - Set up proper npm registry authentication and git permissions
+
+4. **Configure Release Automation**:
+   - Automatic CHANGELOG.md generation and maintenance
+   - Git tag creation for each release
+   - GitHub release creation with release notes
+   - Conditional publishing (only when changes warrant a release)
+
+### Consequences
+
+- Good, because eliminates complex custom version increment logic from CI/CD workflows
+- Good, because provides proper semantic version determination based on commit analysis
+- Good, because automatically generates and maintains CHANGELOG.md with release notes
+- Good, because creates proper git tags and GitHub releases for traceability
+- Good, because follows conventional commits standard adopted widely in open source
+- Good, because only publishes when changes actually warrant a new release
+- Good, because avoids package.json version drift by using git tags as source of truth
+- Good, because simplifies GitHub Actions workflow, improving validation compliance
+- Good, because provides comprehensive release management with minimal configuration
+- Good, because prevents infinite CI loops from version commits
+- Neutral, because requires team adoption of conventional commit message format
+- Neutral, because package.json version in repository may lag behind published version (git tags are source of truth)
+- Bad, because introduces dependency on semantic-release tool and its ecosystem
+- Bad, because may require learning curve for conventional commit message format
+
+### Confirmation
+
+Implementation compliance will be confirmed through:
+
+- semantic-release successfully analyzes commits and determines appropriate version increments
+- Automatic CHANGELOG.md generation and git tag creation on releases
+- CI/CD pipeline publishes to npm only when semantic-release determines a release is warranted
+- No npm publish failures due to version conflicts or unnecessary publishing attempts
+- Package.json version remains synchronized with published npm version
+- GitHub Actions workflow simplified and validates successfully with actionlint (ADR 005)
+- Conventional commit message format adopted and documented for contributors
+
+## Pros and Cons of the Options
+
+### semantic-release with conventional commits
+
+Comprehensive automated release management based on commit message analysis.
+
+- Good, because industry standard tool with extensive ecosystem
+- Good, because proper semantic version determination based on commit analysis
+- Good, because automatic CHANGELOG.md and release notes generation
+- Good, because creates git tags and GitHub releases automatically
+- Good, because only publishes when changes warrant a release
+- Good, because eliminates custom version increment logic complexity
+- Good, because maintains git history and package.json synchronization
+- Good, because follows conventional commits standard
+- Good, because comprehensive documentation and community support
+- Neutral, because requires conventional commit message discipline
+- Neutral, because adds dependency on semantic-release ecosystem
+- Bad, because requires git write permissions in CI/CD
+- Bad, because learning curve for commit message conventions
+
+### Enhanced in-memory version increment with loop logic
+
+Improve the current approach with better version conflict resolution.
+
+- Good, because builds on existing working foundation
+- Good, because no external dependencies or new tooling
+- Good, because maintains current simplicity of git read-only CI/CD
+- Neutral, because addresses immediate technical limitation
+- Bad, because still provides only patch-level version increments
+- Bad, because no semantic version determination capability
+- Bad, because no automatic changelog or git tag generation
+- Bad, because increases complexity of custom GitHub Actions logic
+- Bad, because doesn't address package.json/npm version synchronization
+- Bad, because potential for workflow validation issues with complex logic
+
+### Git write-back approach with automated tagging
+
+Custom solution with git operations for version commits and tagging.
+
+- Good, because provides git tag creation and version history
+- Good, because maintains package.json synchronization
+- Good, because can be customized for specific project needs
+- Neutral, because requires git write permissions
+- Bad, because requires complex infinite loop prevention logic
+- Bad, because no semantic version determination
+- Bad, because no automated changelog generation
+- Bad, because potential race conditions in CI/CD
+- Bad, because increased failure modes with git operations
+- Bad, because custom implementation maintenance burden
+
+### Manual release workflow with GitHub releases
+
+Manual release creation through GitHub interface with automated publishing.
+
+- Good, because provides full control over release timing and messaging
+- Good, because natural integration with GitHub releases interface
+- Good, because allows for manual changelog and release notes
+- Good, because no automated commit message requirements
+- Neutral, because requires manual intervention for releases
+- Bad, because breaks continuous delivery principle
+- Bad, because prone to human error and forgotten releases
+- Bad, because no automation of version determination
+- Bad, because workflow friction for regular development
+- Bad, because doesn't solve original npm publish failure problem
+
+## More Information
+
+This decision supersedes ADR 004 "Automated Version Bumping for CI/CD Publishing", which served as a temporary solution to prevent npm publish failures but has reached its limitations in terms of semantic versioning and release management.
+
+semantic-release configuration will include:
+
+```json
+{
+  "branches": ["main"],
+  "plugins": [
+    "@semantic-release/commit-analyzer",
+    "@semantic-release/release-notes-generator",
+    "@semantic-release/changelog",
+    "@semantic-release/npm",
+    "@semantic-release/github"
+  ]
+}
+```
+
+**Note**: The `@semantic-release/git` plugin is intentionally excluded. semantic-release will manage versions through git tags only, without committing version changes back to package.json. This approach:
+
+- Prevents infinite CI loops from version commits
+- Follows npm ecosystem best practices where tags are the source of truth
+- Keeps the repository history clean of automated version bump commits
+- Aligns with how other projects in the ecosystem use semantic-release
+
+The published npm package will have the correct version, but package.json in the repository may not reflect the latest published version. Git tags serve as the authoritative version record.
+
+Conventional commit format examples:
+
+- `feat: add new validation rule` → minor version increment
+- `fix: resolve annotation parsing issue` → patch version increment
+- `feat!: change API interface` → major version increment
+- `docs: update README` → no version increment
+
+GitHub Actions workflow simplification:
+
+- Remove custom version increment logic
+- Replace with single `npx semantic-release` command
+- Configure necessary permissions (contents:write, issues:write, pull-requests:write, id-token:write)
+- Set HUSKY=0 environment variable to disable git hooks during release
+- Maintain existing quality checks and security audits
+- Add smoke test for published package verification
+
+This decision should be re-evaluated if:
+
+- Conventional commit discipline becomes difficult to maintain
+- semantic-release ecosystem introduces breaking changes or maintenance issues
+- Project requirements change to need custom release logic not supported by semantic-release
+- Team prefers different commit message standards incompatible with conventional commits
+
+Related resources:
+
+- [semantic-release Documentation](https://semantic-release.gitbook.io/)
+- [Conventional Commits Specification](https://www.conventionalcommits.org/)
+- [GitHub Actions with semantic-release](https://github.com/semantic-release/semantic-release/blob/master/docs/recipes/github-actions.md)

package/eslint.config.js

@@ -73,9 +73,9 @@ module.exports = [
     rules: {
       complexity: "error",
       // Enforce maximum lines per function for maintainability
-      "max-lines-per-function": ["error", { max: 90, skipBlankLines: true, skipComments: true }],
+      "max-lines-per-function": ["error", { max: 80, skipBlankLines: true, skipComments: true }],
       // Enforce maximum lines per file for maintainability
-      "max-lines": ["error", { max: 400, skipBlankLines: true, skipComments: true }],
+      "max-lines": ["error", { max: 350, skipBlankLines: true, skipComments: true }],
     },
   },
   {
@@ -90,9 +90,9 @@ module.exports = [
     rules: {
       complexity: "error",
       // Enforce maximum lines per function for maintainability
-      "max-lines-per-function": ["error", { max: 90, skipBlankLines: true, skipComments: true }],
+      "max-lines-per-function": ["error", { max: 80, skipBlankLines: true, skipComments: true }],
       // Enforce maximum lines per file for maintainability
-      "max-lines": ["error", { max: 400, skipBlankLines: true, skipComments: true }],
+      "max-lines": ["error", { max: 350, skipBlankLines: true, skipComments: true }],
     },
   },
   {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eslint-plugin-traceability",
-  "version": "1.0.3",
+  "version": "1.0.5",
   "description": "",
   "main": "lib/index.js",
   "types": "lib/index.d.ts",
@@ -41,17 +41,22 @@
   "homepage": "https://github.com/voder-ai/eslint-plugin-traceability#readme",
   "devDependencies": {
     "@eslint/js": "^9.39.1",
+    "@semantic-release/changelog": "^6.0.3",
+    "@semantic-release/git": "^10.0.1",
+    "@semantic-release/github": "^12.0.2",
     "@types/eslint": "^9.6.1",
     "@types/jest": "^30.0.0",
     "@types/node": "^24.10.1",
     "@typescript-eslint/parser": "^8.46.4",
     "@typescript-eslint/utils": "^8.46.4",
+    "actionlint": "^2.0.6",
     "eslint": "^9.39.1",
     "husky": "^9.1.7",
     "jest": "^30.2.0",
     "jscpd": "^4.0.5",
     "lint-staged": "^16.2.6",
     "prettier": "^3.6.2",
+    "semantic-release": "^25.0.2",
     "ts-jest": "^29.4.5",
     "typescript": "^5.9.3"
   },
@@ -64,4 +69,4 @@
   "overrides": {
     "js-yaml": ">=4.1.1"
   }
-}
+}

package/tests/{basic.test.ts → plugin-setup.test.ts}

@@ -3,7 +3,7 @@
  * @story docs/stories/001.0-DEV-PLUGIN-SETUP.story.md
  * @req REQ-PLUGIN-STRUCTURE - plugin exports rules and configs
  */
-import plugin, { rules, configs } from "../lib/index";
+import plugin, { rules, configs } from "../src/index";
 
 describe("Traceability ESLint Plugin (Story 001.0-DEV-PLUGIN-SETUP)", () => {
   it("[REQ-PLUGIN-STRUCTURE] plugin exports rules and configs", () => {

package/user-docs/migration-guide.md

@@ -0,0 +1,71 @@
+# Migration Guide from v0.x to v1.x
+
+Created autonomously by [voder.ai](https://voder.ai)
+
+This guide helps you migrate from versions 0.x of `eslint-plugin-traceability` to 1.x.
+
+## 1. Update Dependency
+
+Update your development dependency to the latest 1.x release:
+
+```bash
+npm install --save-dev eslint-plugin-traceability@^1.0.0
+```
+
+Or with Yarn:
+
+```bash
+yarn add --dev eslint-plugin-traceability@^1.0.0
+```
+
+## 2. ESLint Configuration Changes
+
+- Version 1.x uses ESLint v9 flat config by default. If you currently use `.eslintrc.js`, you can continue using it, but consider migrating to the new flat config format for future upgrades.
+- Update your ESLint config to load the plugin’s recommended settings:
+
+```js
+// eslint.config.js (ESLint v9 flat config)
+import traceability from "eslint-plugin-traceability";
+
+export default [traceability.configs.recommended];
+```
+
+## 3. New and Updated Rules
+
+- `valid-story-reference` now enforces `.story.md` extensions strictly.
+- `valid-req-reference` rejects path traversal (`../`) and absolute paths (`/etc/passwd`).
+- `valid-annotation-format` enforces correct JSDoc traceability annotation syntax (`@story` and `@req` tags).
+
+Review and update your existing annotations accordingly:
+
+```diff
+- /** @story docs/stories/001.0-DEV-PLUGIN-SETUP.md */
++ /** @story docs/stories/001.0-DEV-PLUGIN-SETUP.story.md */
+```
+
+## 4. CLI Integration Script
+
+Version 1.x includes a new `cli-integration.js` script at the project root to run end-to-end CLI integration tests:
+
+```bash
+node ./cli-integration.js
+```
+
+## 5. Test and Validate
+
+Run your test suite and the new CLI integration script to confirm everything passes:
+
+```bash
+npm test
+npm run lint -- --max-warnings=0
+npm run format:check
+node ./cli-integration.js
+```
+
+## 6. Update Documentation
+
+If you have custom documentation or examples that reference old rule names or file paths, update them to match the new conventions introduced in v1.x.
+
+---
+
+If you encounter any issues during migration, please file an issue at https://github.com/voder-ai/eslint-plugin-traceability/issues.

package/lib/index.d.ts

@@ -1,26 +0,0 @@
-/**
- * ESLint Traceability Plugin
- * @story docs/stories/001.0-DEV-PLUGIN-SETUP.story.md
- * @req REQ-PLUGIN-STRUCTURE - Provide foundational plugin export and registration
- */
-export declare const rules: Record<string, unknown>;
-export declare const configs: {
-  recommended: {
-    rules: {};
-  }[];
-  strict: {
-    rules: {};
-  }[];
-};
-declare const _default: {
-  rules: Record<string, unknown>;
-  configs: {
-    recommended: {
-      rules: {};
-    }[];
-    strict: {
-      rules: {};
-    }[];
-  };
-};
-export default _default;

package/lib/index.js

@@ -1,11 +0,0 @@
-"use strict";
-/**
- * ESLint Traceability Plugin
- * @story docs/stories/001.0-DEV-PLUGIN-SETUP.story.md
- * @req REQ-PLUGIN-STRUCTURE - Provide foundational plugin export and registration
- */
-const plugin = require("./src/index.js");
-
-module.exports = plugin;
-module.exports.rules = plugin.rules;
-module.exports.configs = plugin.configs;

package/lib/src/index.d.ts

@@ -1,80 +0,0 @@
-/**
- * ESLint Traceability Plugin
- * @story docs/stories/001.0-DEV-PLUGIN-SETUP.story.md
- * @req REQ-PLUGIN-STRUCTURE - Provide foundational plugin export and registration
- */
-export declare const rules: {
-    "require-story-annotation": any;
-    "require-req-annotation": any;
-    "require-branch-annotation": any;
-    "valid-annotation-format": any;
-    "valid-story-reference": import("eslint").Rule.RuleModule;
-    "valid-req-reference": import("eslint").Rule.RuleModule;
-};
-export declare const configs: {
-    recommended: {
-        plugins: {
-            traceability: {};
-        };
-        rules: {
-            "traceability/require-story-annotation": string;
-            "traceability/require-req-annotation": string;
-            "traceability/require-branch-annotation": string;
-            "traceability/valid-annotation-format": string;
-            "traceability/valid-story-reference": string;
-            "traceability/valid-req-reference": string;
-        };
-    }[];
-    strict: {
-        plugins: {
-            traceability: {};
-        };
-        rules: {
-            "traceability/require-story-annotation": string;
-            "traceability/require-req-annotation": string;
-            "traceability/require-branch-annotation": string;
-            "traceability/valid-annotation-format": string;
-            "traceability/valid-story-reference": string;
-            "traceability/valid-req-reference": string;
-        };
-    }[];
-};
-declare const _default: {
-    rules: {
-        "require-story-annotation": any;
-        "require-req-annotation": any;
-        "require-branch-annotation": any;
-        "valid-annotation-format": any;
-        "valid-story-reference": import("eslint").Rule.RuleModule;
-        "valid-req-reference": import("eslint").Rule.RuleModule;
-    };
-    configs: {
-        recommended: {
-            plugins: {
-                traceability: {};
-            };
-            rules: {
-                "traceability/require-story-annotation": string;
-                "traceability/require-req-annotation": string;
-                "traceability/require-branch-annotation": string;
-                "traceability/valid-annotation-format": string;
-                "traceability/valid-story-reference": string;
-                "traceability/valid-req-reference": string;
-            };
-        }[];
-        strict: {
-            plugins: {
-                traceability: {};
-            };
-            rules: {
-                "traceability/require-story-annotation": string;
-                "traceability/require-req-annotation": string;
-                "traceability/require-branch-annotation": string;
-                "traceability/valid-annotation-format": string;
-                "traceability/valid-story-reference": string;
-                "traceability/valid-req-reference": string;
-            };
-        }[];
-    };
-};
-export default _default;

package/lib/src/index.js

@@ -1,58 +0,0 @@
-"use strict";
-/**
- * ESLint Traceability Plugin
- * @story docs/stories/001.0-DEV-PLUGIN-SETUP.story.md
- * @req REQ-PLUGIN-STRUCTURE - Provide foundational plugin export and registration
- */
-var __importDefault = (this && this.__importDefault) || function (mod) {
-    return (mod && mod.__esModule) ? mod : { "default": mod };
-};
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.configs = exports.rules = void 0;
-const require_story_annotation_1 = __importDefault(require("./rules/require-story-annotation"));
-const require_req_annotation_1 = __importDefault(require("./rules/require-req-annotation"));
-const require_branch_annotation_1 = __importDefault(require("./rules/require-branch-annotation"));
-const valid_annotation_format_1 = __importDefault(require("./rules/valid-annotation-format"));
-const valid_story_reference_1 = __importDefault(require("./rules/valid-story-reference"));
-const valid_req_reference_1 = __importDefault(require("./rules/valid-req-reference"));
-exports.rules = {
-    "require-story-annotation": require_story_annotation_1.default,
-    "require-req-annotation": require_req_annotation_1.default,
-    "require-branch-annotation": require_branch_annotation_1.default,
-    "valid-annotation-format": valid_annotation_format_1.default,
-    "valid-story-reference": valid_story_reference_1.default,
-    "valid-req-reference": valid_req_reference_1.default,
-};
-exports.configs = {
-    recommended: [
-        {
-            plugins: {
-                traceability: {},
-            },
-            rules: {
-                "traceability/require-story-annotation": "error",
-                "traceability/require-req-annotation": "error",
-                "traceability/require-branch-annotation": "error",
-                "traceability/valid-annotation-format": "error",
-                "traceability/valid-story-reference": "error",
-                "traceability/valid-req-reference": "error",
-            },
-        },
-    ],
-    strict: [
-        {
-            plugins: {
-                traceability: {},
-            },
-            rules: {
-                "traceability/require-story-annotation": "error",
-                "traceability/require-req-annotation": "error",
-                "traceability/require-branch-annotation": "error",
-                "traceability/valid-annotation-format": "error",
-                "traceability/valid-story-reference": "error",
-                "traceability/valid-req-reference": "error",
-            },
-        },
-    ],
-};
-exports.default = { rules: exports.rules, configs: exports.configs };

package/lib/src/maintenance/batch.d.ts

@@ -1,16 +0,0 @@
-/**
- * Batch update annotations and verify references
- * @story docs/stories/009.0-DEV-MAINTENANCE-TOOLS.story.md
- * @req REQ-MAINT-BATCH - Perform batch updates
- * @req REQ-MAINT-VERIFY - Verify annotation references
- */
-export declare function batchUpdateAnnotations(codebasePath: string, mappings: {
-    oldPath: string;
-    newPath: string;
-}[]): number;
-/**
- * Verify annotation references in codebase after maintenance operations
- * @story docs/stories/009.0-DEV-MAINTENANCE-TOOLS.story.md
- * @req REQ-MAINT-VERIFY - Verify annotation references
- */
-export declare function verifyAnnotations(codebasePath: string): boolean;

package/lib/src/maintenance/batch.js

@@ -1,28 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.batchUpdateAnnotations = batchUpdateAnnotations;
-exports.verifyAnnotations = verifyAnnotations;
-const update_1 = require("./update");
-const detect_1 = require("./detect");
-/**
- * Batch update annotations and verify references
- * @story docs/stories/009.0-DEV-MAINTENANCE-TOOLS.story.md
- * @req REQ-MAINT-BATCH - Perform batch updates
- * @req REQ-MAINT-VERIFY - Verify annotation references
- */
-function batchUpdateAnnotations(codebasePath, mappings) {
-    let totalUpdated = 0;
-    for (const { oldPath, newPath } of mappings) {
-        totalUpdated += (0, update_1.updateAnnotationReferences)(codebasePath, oldPath, newPath);
-    }
-    return totalUpdated;
-}
-/**
- * Verify annotation references in codebase after maintenance operations
- * @story docs/stories/009.0-DEV-MAINTENANCE-TOOLS.story.md
- * @req REQ-MAINT-VERIFY - Verify annotation references
- */
-function verifyAnnotations(codebasePath) {
-    const staleAnnotations = (0, detect_1.detectStaleAnnotations)(codebasePath);
-    return staleAnnotations.length === 0;
-}

package/lib/src/maintenance/detect.d.ts

@@ -1,6 +0,0 @@
-/**
- * Detect stale annotation references that point to moved or deleted story files
- * @story docs/stories/009.0-DEV-MAINTENANCE-TOOLS.story.md
- * @req REQ-MAINT-DETECT - Detect stale annotation references
- */
-export declare function detectStaleAnnotations(codebasePath: string): string[];

package/lib/src/maintenance/detect.js

@@ -1,69 +0,0 @@
-"use strict";
-var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
-    if (k2 === undefined) k2 = k;
-    var desc = Object.getOwnPropertyDescriptor(m, k);
-    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
-      desc = { enumerable: true, get: function() { return m[k]; } };
-    }
-    Object.defineProperty(o, k2, desc);
-}) : (function(o, m, k, k2) {
-    if (k2 === undefined) k2 = k;
-    o[k2] = m[k];
-}));
-var __setModuleDefault = (this && this.__setModuleDefault) || (Object.create ? (function(o, v) {
-    Object.defineProperty(o, "default", { enumerable: true, value: v });
-}) : function(o, v) {
-    o["default"] = v;
-});
-var __importStar = (this && this.__importStar) || (function () {
-    var ownKeys = function(o) {
-        ownKeys = Object.getOwnPropertyNames || function (o) {
-            var ar = [];
-            for (var k in o) if (Object.prototype.hasOwnProperty.call(o, k)) ar[ar.length] = k;
-            return ar;
-        };
-        return ownKeys(o);
-    };
-    return function (mod) {
-        if (mod && mod.__esModule) return mod;
-        var result = {};
-        if (mod != null) for (var k = ownKeys(mod), i = 0; i < k.length; i++) if (k[i] !== "default") __createBinding(result, mod, k[i]);
-        __setModuleDefault(result, mod);
-        return result;
-    };
-})();
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.detectStaleAnnotations = detectStaleAnnotations;
-const fs = __importStar(require("fs"));
-const path = __importStar(require("path"));
-const utils_1 = require("./utils");
-/**
- * Detect stale annotation references that point to moved or deleted story files
- * @story docs/stories/009.0-DEV-MAINTENANCE-TOOLS.story.md
- * @req REQ-MAINT-DETECT - Detect stale annotation references
- */
-function detectStaleAnnotations(codebasePath) {
-    if (!fs.existsSync(codebasePath) ||
-        !fs.statSync(codebasePath).isDirectory()) {
-        return [];
-    }
-    const cwd = process.cwd();
-    const baseDir = path.resolve(cwd, codebasePath);
-    const stale = new Set();
-    const files = (0, utils_1.getAllFiles)(codebasePath);
-    for (const file of files) {
-        const content = fs.readFileSync(file, "utf8");
-        const regex = /@story\s+([^\s]+)/g;
-        let match;
-        while ((match = regex.exec(content)) !== null) {
-            const storyPath = match[1];
-            const storyProjectPath = path.resolve(cwd, storyPath);
-            const storyCodebasePath = path.resolve(baseDir, storyPath);
-            if (!fs.existsSync(storyProjectPath) &&
-                !fs.existsSync(storyCodebasePath)) {
-                stale.add(storyPath);
-            }
-        }
-    }
-    return Array.from(stale);
-}