eslint-plugin-traceability 1.1.1 → 1.1.3

package/.voder/progress-log-areas.csv

@@ -1,39 +0,0 @@
-overall,functionality,code_quality,testing,execution,documentation,dependencies,security,vcs
-12.5,,10,0,0,55,5,10,20
-46,,68,90,60,35,85,0,30
-47,,90,30,90,50,80,0,35
-60.5,,72,25,95,75,100,92,25
-64.13,,75,85,90,48,90,95,30
-70,,90,92,75,55,95,95,55
-68.5,,90,75,90,25,98,95,75
-72.25,,78,80,85,50,95,100,90
-71.25,,92,90,35,70,95,100,88
-75,,90,75,65,87,100,95,90
-78,,75,85,90,90,95,95,95
-80.4,,90,88,80,90,100,100,95
-81,,92,85,85,92,100,100,95
-80.25,,85,90,90,92,100,95,90
-75,,92,90,90,82,98,100,55
-85,,90,90,90,85,100,100,98
-93.14,,90,92,95,88,97,98,92
-80,,85,90,92,88,98,100,90
-76,,92,85,75,85,95,95,80
-89,,70,92,90,80,98,100,90
-77.25,,90,90,95,65,100,88,90
-73.12,,85,92,90,45,100,98,75
-89,50,90,92,92,90,100,100,95
-78.5,,92,88,88,90,100,100,70
-79.4,,80,90,90,90,95,95,95
-77.9,,70,96,95,70,100,100,92
-75,,75,95,90,92,90,100,90
-85,,90,90,90,95,100,90,85
-75.625,,80,95,88,92,100,100,50
-90.5,60,90,92,92,92,100,100,98
-77.5,,77,60,93,95,100,100,95
-76.875,,93,92,95,85,100,95,55
-89.6,,90,90,95,82,100,95,75
-91,,93,87,95,85,100,95,85
-78.25,,70,85,95,85,100,98,93
-89.6,,95,92,95,90,100,95,60
-72.5,,80,95,95,55,100,95,60
-75.25,,85,95,85,92,95,95,55

package/.voder/progress-log.csv

@@ -1,38 +0,0 @@
-12.5
-46
-47
-60.5
-64.13
-70
-68.5
-72.25
-71.25
-75
-78
-80.4
-81
-80.25
-75
-85
-93.14
-80
-76
-89
-77.25
-73.12
-89
-78.5
-79.4
-77.9
-75
-85
-75.625
-90.5
-77.5
-76.875
-89.6
-91
-78.25
-89.6
-72.5
-75.25

package/.voder/traceability/docs-stories-001.0-DEV-PLUGIN-SETUP.story.xml

@@ -1,17 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<traceability>
-  <specification>docs/stories/001.0-DEV-PLUGIN-SETUP.story.md</specification>
-  <status>PASSED</status>
-  <last_validated>2025-11-16T17:05:11.795Z</last_validated>
-  <last_modified>2025-11-16T00:07:54.385Z</last_modified>
-  <evidence>- src/index.ts exports plugin.rules and plugin.configs in standard ESLint plugin structure with TypeScript and traceability annotations (@story docs/stories/001.0-DEV-PLUGIN-SETUP.story.md, @req REQ-PLUGIN-STRUCTURE).
-- package.json defines main and types fields, scripts for build, lint, test, and peerDependencies, conforming to npm package conventions.
-- tsconfig.json and build script (`npm run build`) compile TypeScript source to CommonJS without errors.
-- tests/basic.test.ts verifies that plugin.rules and plugin.configs are defined and correctly exported (Basic plugin structure test for Story 001.0).
-- tests/integration/plugin-validation.test.ts invokes ESLint CLI with flat config (eslint.config.js) and confirms rule errors as expected, demonstrating ESLint v9 flat config integration.
-- README.md and docs/eslint-9-setup-guide.md include clear installation and configuration instructions for the plugin.
-- eslint.config.js handles plugin loading errors via try/catch, satisfying graceful error handling.
-- All Jest tests pass under CI (`npm test`), and CLI integration script (cli-integration.js) also confirms plugin registration behavior.
-</evidence>
-  <notes>The foundational ESLint plugin structure defined in 001.0-DEV-PLUGIN-SETUP has been implemented: the plugin registers rules and configs, compiles cleanly under TypeScript, integrates with ESLint v9 flat config, includes comprehensive tests for module exports and CLI behavior, and provides clear documentation and error handling. All acceptance criteria and technical requirements for this story are satisfied.</notes>
-</traceability>

package/.voder/traceability/docs-stories-002.0-DEV-ESLINT-CONFIG.story.xml

@@ -1,13 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<traceability>
-  <specification>docs/stories/002.0-DEV-ESLINT-CONFIG.story.md</specification>
-  <status>PASSED</status>
-  <last_validated>2025-11-16T17:05:16.869Z</last_validated>
-  <last_modified>2025-11-16T00:07:54.396Z</last_modified>
-  <evidence>- src/index.ts exports `configs.recommended` and `configs.strict` with the required rule presets (REQ-CONFIG-PRESETS)
-- eslint.config.js is written in ESLint v9 flat‐config format and includes sections for JS, TS, common CJS files, and ignores (REQ-FLAT-CONFIG)
-- valid-story-reference rule schema supports `storyDirectories`, `allowAbsolutePaths`, and `requireStoryExtension` options (REQ-CUSTOMIZABLE-PATHS, REQ-RULE-OPTIONS)
-- CI build and linting pass without errors, demonstrating seamless integration (EXECUTION reports 92%, CODE_QUALITY reports lint/test/type-check OK)
-- docs/config-presets.md and docs/eslint-9-setup-guide.md provide clear setup instructions, examples, and troubleshooting (Documentation acceptance)</evidence>
-  <notes>All acceptance criteria for story 002.0-DEV-ESLINT-CONFIG have been met: the plugin provides both recommended and strict presets, follows ESLint v9 flat config best practices, allows rule customization, integrates with JS/TS projects, and includes comprehensive documentation and configuration validation.</notes>
-</traceability>

package/.voder/traceability/docs-stories-003.0-DEV-FUNCTION-ANNOTATIONS.story.xml

@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<traceability>
-  <specification>docs/stories/003.0-DEV-FUNCTION-ANNOTATIONS.story.md</specification>
-  <status>FAILED</status>
-  <last_validated>2025-11-16T17:03:12.326Z</last_validated>
-  <last_modified>2025-11-16T00:07:54.405Z</last_modified>
-  <evidence>Inspection of src/rules/require-story-annotation.ts and src/rules/require-req-annotation.ts shows only FunctionDeclaration nodes are handled (no arrow functions, function expressions, or class methods), there is no support for TypeScript‐specific syntax or parser configuration in RuleTester (only default parser used), and neither rule exposes configuration to scope which functions are checked or to prioritize exported functions. Key requirements REQ-FUNCTION-DETECTION (expressions/arrow functions), REQ-CONFIGURABLE-SCOPE, REQ-EXPORT-PRIORITY, and REQ-TYPESCRIPT-SUPPORT are not implemented.</evidence>
-  <notes>While basic function‐level detection and error reporting exist for missing @story and @req, the implementation does not satisfy the full breadth of acceptance criteria and technical requirements outlined in the story. Additional work is needed to support all function patterns, configurability, and TypeScript integration.</notes>
-</traceability>

package/.voder/traceability/docs-stories-004.0-DEV-BRANCH-ANNOTATIONS.story.xml

@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<traceability>
-  <specification>docs/stories/004.0-DEV-BRANCH-ANNOTATIONS.story.md</specification>
-  <status>FAILED</status>
-  <last_validated>2025-11-16T17:03:22.383Z</last_validated>
-  <last_modified>2025-11-16T00:07:54.419Z</last_modified>
-  <evidence>In src/rules/require-branch-annotation.ts the rule.meta.schema is an empty array (schema: []), and the documentation (docs/rules/require-branch-annotation.md) explicitly states “This rule does not accept any options.” However, the story’s Requirements include REQ-CONFIGURABLE-SCOPE: “Allow configuration of which branch types require annotations.” There is no code to accept or handle any configuration options for branch scopes, nor any tests for that behavior.</evidence>
-  <notes>While the core detection, parsing, and error reporting for branch annotations are implemented and well-tested, the required ability to configure which branch types are enforced is missing. The story is therefore not fully satisfied.</notes>
-</traceability>

package/.voder/traceability/docs-stories-005.0-DEV-ANNOTATION-VALIDATION.story.xml

@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<traceability>
-  <specification>docs/stories/005.0-DEV-ANNOTATION-VALIDATION.story.md</specification>
-  <status>PASSED</status>
-  <last_validated>2025-11-16T17:03:32.682Z</last_validated>
-  <last_modified>2025-11-16T00:07:54.431Z</last_modified>
-  <evidence>The `valid-annotation-format` rule is present in src/rules/valid-annotation-format.ts with appropriate meta, messages, and schema. Tests in tests/rules/valid-annotation-format.test.ts cover valid and invalid @story and @req formats, including block comments and single-line comments, and all tests pass (100% statements, 100% lines, 92.85% branches). Documentation exists at docs/rules/valid-annotation-format.md with examples matching implementation. The rule is exported in src/index.ts and included in both 'recommended' and 'strict' configs. ESLint linting, Jest testing, type checking, and coverage checks all pass.</evidence>
-  <notes>The annotation format validation rule fully meets the story’s acceptance criteria: it validates @story and @req syntax, follows ESLint best practices, integrates with other rules, provides clear error messages, handles edge cases (multiline/block comments), and is documented with examples. Tests ensure REQ-FORMAT-SPECIFICATION, REQ-SYNTAX-VALIDATION, REQ-PATH-FORMAT, REQ-REQ-FORMAT, REQ-MULTILINE-SUPPORT, REQ-FLEXIBLE-PARSING, and REQ-ERROR-SPECIFICITY are satisfied.</notes>
-</traceability>

package/.voder/traceability/docs-stories-006.0-DEV-FILE-VALIDATION.story.xml

@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<traceability>
-  <specification>docs/stories/006.0-DEV-FILE-VALIDATION.story.md</specification>
-  <status>PASSED</status>
-  <last_validated>2025-11-16T17:03:17.855Z</last_validated>
-  <last_modified>2025-11-16T00:07:54.445Z</last_modified>
-  <evidence>Found src/rules/valid-story-reference.ts with full implementation of REQ-FILE-EXISTENCE, REQ-PATH-RESOLUTION, REQ-SECURITY-VALIDATION, REQ-PERFORMANCE-OPTIMIZATION (caching), REQ-PROJECT-BOUNDARY, and REQ-CONFIGURABLE-PATHS, all annotated with @story docs/stories/006.0-DEV-FILE-VALIDATION.story.md. Corresponding tests in tests/rules/valid-story-reference.test.ts cover valid and invalid scenarios (file exists, extension check, path traversal, absolute paths) and reference the story and requirement IDs. package.json scripts include Jest run, and CI reports 100% passing tests and high coverage.</evidence>
-  <notes>The valid-story-reference rule meets all acceptance criteria: core functionality, ESLint best practices, integration with format validation, clear error messages, and documented examples. Tests confirm correct behavior across file system scenarios.</notes>
-</traceability>

package/.voder/traceability/docs-stories-007.0-DEV-ERROR-REPORTING.story.xml

@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<traceability>
-  <specification>docs/stories/007.0-DEV-ERROR-REPORTING.story.md</specification>
-  <status>FAILED</status>
-  <last_validated>2025-11-16T17:04:41.461Z</last_validated>
-  <last_modified>2025-11-16T00:07:54.454Z</last_modified>
-  <evidence>A review of the rule implementations shows that none of the context.report() calls supply “suggest” fixes or instruction text: for example, require-story-annotation only reports messageId “missingStory” with text “Missing @story annotation” and no suggestion on how to add one. None of the rules use ESLint’s suggest API or include actionable guidance (e.g. “Add @story docs/stories/...”) or dynamic context beyond basic identifiers. The docs/rules markdown do not document full error messages or suggestions, and existing unit and CLI tests only assert that errors fire, not that they carry specific, actionable message text or locations beyond the default. </evidence>
-  <notes>The 007.0-DEV-ERROR-REPORTING story calls for clear, actionable error messages including suggested fixes, context and consistent formatting. While basic error reporting exists, there is no implementation of suggestion API, no contextual guidance, and no documentation of full message format. Therefore the story is not satisfied.</notes>
-</traceability>

package/.voder/traceability/docs-stories-008.0-DEV-AUTO-FIX.story.xml

@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<traceability>
-  <specification>docs/stories/008.0-DEV-AUTO-FIX.story.md</specification>
-  <status>FAILED</status>
-  <last_validated>2025-11-16T17:04:59.379Z</last_validated>
-  <last_modified>2025-11-16T00:07:54.465Z</last_modified>
-  <evidence>Assessment error: 400 This model's maximum context length is 200000 tokens. However, your messages resulted in 206091 tokens (204696 in the messages, 1395 in the functions). Please reduce the length of the messages or functions.</evidence>
-  <notes>Technical error during assessment</notes>
-</traceability>

package/.voder/traceability/docs-stories-009.0-DEV-MAINTENANCE-TOOLS.story.xml

@@ -1,16 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<traceability>
-  <specification>docs/stories/009.0-DEV-MAINTENANCE-TOOLS.story.md</specification>
-  <status>PASSED</status>
-  <last_validated>2025-11-16T17:05:08.140Z</last_validated>
-  <last_modified>2025-11-16T00:07:54.476Z</last_modified>
-  <evidence>- src/maintenance/detect.ts, update.ts, batch.ts, report.ts, utils.ts implement all six REQ-MAINT-* requirements with JSDoc @story and @req annotations.  
-- tests/maintenance/detect.test.ts & detect-isolated.test.ts cover REQ-MAINT-DETECT (detectStaleAnnotations).  
-- tests/maintenance/update.test.ts & update-isolated.test.ts cover REQ-MAINT-UPDATE (updateAnnotationReferences).  
-- tests/maintenance/batch.test.ts cover REQ-MAINT-BATCH and REQ-MAINT-VERIFY (batchUpdateAnnotations, verifyAnnotations).  
-- tests/maintenance/report.test.ts covers REQ-MAINT-REPORT (generateMaintenanceReport) and implicitly REQ-MAINT-SAFE.  
-- npm test (Jest) runs all tests with 100% passing, maintaining >96% coverage in maintenance code.  
-- Code preserves formatting, handles missing directories, nested structures, permission errors, and writes updates safely.  
-</evidence>
-  <notes>All acceptance criteria for story 009.0-DEV-MAINTENANCE-TOOLS are satisfied: core functionality, quality standards, integration, UX feedback, error handling, and documentation via JSDoc and test coverage. Maintenance tools are fully implemented and validated by tests.</notes>
-</traceability>

package/.voder/traceability/docs-stories-010.0-DEV-DEEP-VALIDATION.story.xml

@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<traceability>
-  <specification>docs/stories/010.0-DEV-DEEP-VALIDATION.story.md</specification>
-  <status>PASSED</status>
-  <last_validated>2025-11-16T17:03:50.351Z</last_validated>
-  <last_modified>2025-11-16T00:07:54.487Z</last_modified>
-  <evidence>- src/rules/valid-req-reference.ts implements deep validation logic with AST comment parsing, path resolution, caching, regex-based requirement extraction, and reports both invalidPath and reqMissing messages.
-- Tests in tests/rules/valid-req-reference.test.ts cover valid references (including bullet-list fixture), missing requirements, path traversal, and absolute paths, all passing under Jest: exit code 0, coverage report included.
-- Documentation in docs/rules/valid-req-reference.md and docs/stories/010.0-DEV-DEEP-VALIDATION.story.md align, and the plugin builds, lints, type-checks, and tests successfully (npm test shows 96%+ statements, 84%+ branches overall).</evidence>
-  <notes>The implementation provides the required core functionality for deep requirement content validation: it parses story files, matches @req IDs, handles path errors, caches content, reports clear errors, and is fully tested. All acceptance criteria are satisfied.</notes>
-</traceability>

package/CHANGELOG.md

@@ -1,58 +0,0 @@
-## [1.1.1](https://github.com/voder-ai/eslint-plugin-traceability/compare/v1.1.0...v1.1.1) (2025-11-17)
-
-
-### Bug Fixes
-
-* build project before semantic-release and improve smoke test to use npm pack ([e9621d3](https://github.com/voder-ai/eslint-plugin-traceability/commit/e9621d365bf8ebd36e507052c88ead787703cb17))
-* remove tarballDir option from semantic-release npm plugin ([e3703e5](https://github.com/voder-ai/eslint-plugin-traceability/commit/e3703e5a79e6b0784b98f8f4996083a6040a5fb4))
-
-# Changelog
-
-All notable changes to this project will be documented in this file.
-
-## [1.0.3] - 2025-11-17
-
-### Added
-- CLI integration script (`cli-integration.js`) for end-to-end ESLint CLI tests.
-- Migration guide in `user-docs/migration-guide.md`.
-
-## [1.0.2] - 2025-11-17
-
-### Changed
-- Updated README and docs to reference `cli-integration.js` script.
-- Removed stale references to migration guide in CHANGELOG gradients.
-
-## [1.0.1] - 2025-11-17
-
-### Added
-- Detailed API documentation in `user-docs/api-reference.md`
-- New usage examples in `user-docs/examples.md`
-
-### Changed
-- Updated `README.md` with advanced usage instructions and migration guide
-- Consolidated CI workflows into a unified GitHub Actions pipeline
-
-## [1.0.0] - 2025-11-16
-
-### Changed
-- Bumped version to 1.0.0 in package.json.
-- Aligned CHANGELOG with package.json version.
-
-## [0.1.0] - 2025-11-16
-
-### Added
-- Initial release of `eslint-plugin-traceability`:
-  - `require-story-annotation`
-  - `require-req-annotation`
-  - `require-branch-annotation`
-  - `valid-annotation-format`
-  - `valid-story-reference`
-  - `valid-req-reference`
-- Documentation for all rules under `docs/rules`.
-- Configuration presets in `docs/config-presets.md`.
-- Example usage in `README.md`.
-- Pre-commit and pre-push hooks with formatting, linting, and tests.
-- Comprehensive tests covering core validation rules.
-
-### Fixed
-- N/A

package/CONTRIBUTING.md

@@ -1,99 +0,0 @@
-# Contributing to eslint-plugin-traceability
-
-Thank you for your interest in contributing to `eslint-plugin-traceability`! We welcome bug reports, feature requests, and pull requests. To ensure a smooth process, please follow the guidelines below.
-
-## Reporting Issues
-
-If you encounter a bug or have a feature request:
-
-1. Search existing issues to see if the problem or suggestion has already been reported.
-2. If not, open a new issue on GitHub: [Issue Tracker](https://github.com/voder-ai/eslint-plugin-traceability/issues).
-3. Provide a clear and descriptive title, steps to reproduce, expected behavior, and any relevant screenshots or logs.
-4. Specify your environment:
-   - `node` version: `node -v`
-   - `eslint` version: `npx eslint -v`
-   - Operating system and shell.
-
-## Pull Request Process
-
-When submitting a pull request (PR):
-
-1. Fork the repository and create a branch for your changes.
-2. Commit your changes in small, logical increments. Use descriptive commit messages.
-3. Ensure all tests pass and the project builds successfully.
-4. Push your branch to GitHub and open a PR against the `main` branch.
-5. Reference any related issues in your PR description.
-6. A maintainer will review your changes and may request updates or approve the PR.
-
-## Commit Message Conventions
-
-We follow [Conventional Commits](https://www.conventionalcommits.org/) format to enable automated semantic versioning and changelog generation.
-
-For detailed guidelines and examples, see [docs/conventional-commits-guide.md](docs/conventional-commits-guide.md).
-
-Commit messages should be structured as:
-
-```
-type[optional scope]: description
-
-[optional body]
-
-[optional footer(s)]
-```
-
-Examples:
-
-- `feat: add new validation rule` → minor version increment
-- `fix: resolve parsing issue` → patch version increment
-- `feat!: change API interface` → major version increment
-- `docs: update README` → no version change
-
-Common types: `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore`, `ci`
-
-## Coding Style and Quality Checks
-
-We enforce code style and quality using ESLint, Prettier, TypeScript, and other tools. Please run the following commands before submitting your PR:
-
-```bash
-# Build the project and generate types
-npm run build
-
-# Run TypeScript type checks
-npm run type-check
-
-# Lint code
-npm run lint
-
-# Run tests
-npm test
-
-# Check formatting (no changes)
-npm run format:check
-
-# Check duplication threshold
-npm run duplication
-```
-
-Ensure there are no errors or warnings in the output.
-
-## Developing Locally
-
-1. Clone your fork and install dependencies:
-
-   ```bash
-   git clone https://github.com/<your-username>/eslint-plugin-traceability.git
-   cd eslint-plugin-traceability
-   npm install
-   ```
-
-````
-
-2. Run the tests in watch mode:
-
-   ```bash
-npm test
-````
-
-3. Make your changes, and verify that tests and linting continue to pass.
-
-Thank you for helping improve `eslint-plugin-traceability`!

package/cli-integration.js

@@ -1,103 +0,0 @@
-#!/usr/bin/env node
-/**
- * CLI integration tests script for ESLint Traceability Plugin
- * @story docs/stories/001.0-DEV-PLUGIN-SETUP.story.md
- * @req REQ-PLUGIN-STRUCTURE - Validate plugin registers via CLI
- */
-const { spawnSync } = require("child_process");
-const path = require("path");
-
-// Resolve the ESLint CLI binary and configuration path
-const eslintPkgDir = path.dirname(require.resolve("eslint/package.json"));
-const eslintCliPath = path.join(eslintPkgDir, "bin", "eslint.js");
-const configPath = path.resolve(__dirname, "eslint.config.js");
-
-// Define CLI integration test scenarios
-const tests = [
-  {
-    name: "reports error when @story annotation is missing",
-    code: "function foo() {}",
-    rule: "traceability/require-story-annotation:error",
-    expectedStatus: 1,
-  },
-  {
-    name: "does not report error when @story annotation is present",
-    code: `/**
- * @story docs/stories/003.0-DEV-FUNCTION-ANNOTATIONS.story.md
- */
-function foo() {}`,
-    rule: "traceability/require-story-annotation:error",
-    expectedStatus: 0,
-  },
-  {
-    name: "reports error when @req annotation is missing",
-    code: "function bar() {}",
-    rule: "traceability/require-req-annotation:error",
-    expectedStatus: 1,
-  },
-  {
-    name: "reports error when @story annotation uses path traversal and @req annotation uses path traversal",
-    code: `/**
- * @story ../docs/stories/invalid.story.md
- * @req ../docs/requirements/REQ-INVALID.md
- */
-function bar() {}`,
-    rule: "traceability/valid-req-reference:error",
-    expectedStatus: 1,
-  },
-  {
-    name: "reports error when @story annotation uses absolute path and @req annotation uses absolute path",
-    code: `/**
- * @story /absolute/path/to/story.story.md
- * @req /etc/passwd
- */
-function baz() {}`,
-    rule: "traceability/valid-req-reference:error",
-    expectedStatus: 1,
-  },
-];
-
-/**
- * Run ESLint CLI with given code and rule override
- * @param {string} code Source code to lint via stdin
- * @param {string} rule ESLint rule override e.g. "traceability/require-story-annotation:error"
- * @returns {object} Result of spawnSync call
- */
-function runEslint(code, rule) {
-  const args = [
-    "--no-config-lookup",
-    "--config",
-    configPath,
-    "--stdin",
-    "--stdin-filename",
-    "foo.js",
-    "--rule",
-    "no-unused-vars:off",
-    "--rule",
-    rule,
-  ];
-  return spawnSync(process.execPath, [eslintCliPath, ...args], {
-    encoding: "utf-8",
-    input: code,
-  });
-}
-
-// Execute tests and report results
-let failures = 0;
-tests.forEach((test) => {
-  const result = runEslint(test.code, test.rule);
-  const passed = result.status === test.expectedStatus;
-  if (passed) {
-    console.log(`✓ ${test.name}`);
-  } else {
-    console.error(`✗ ${test.name}`);
-    console.error(
-      `  Expected exit code ${test.expectedStatus}, got ${result.status}`,
-    );
-    if (result.stdout) console.error(`  stdout: ${result.stdout}`);
-    if (result.stderr) console.error(`  stderr: ${result.stderr}`);
-    failures++;
-  }
-});
-
-process.exit(failures > 0 ? 1 : 0);

package/docs/cli-integration.md

@@ -1,105 +0,0 @@
-# CLI Integration Script Documentation
-
-This document provides detailed information about the `cli-integration.js` script, which runs end-to-end CLI integration tests for the `eslint-plugin-traceability` plugin.
-
-Story: docs/stories/001.0-DEV-PLUGIN-SETUP.story.md  
-Requirement: REQ-PLUGIN-STRUCTURE - Validate plugin registers via CLI
-
-## Overview
-
-The `cli-integration.js` script automates tests that invoke the ESLint CLI with the plugin configured, verifying that rule errors are reported (or not) as expected when code is passed via `stdin`.
-
-It uses Node.js `child_process.spawnSync` to:
-
-- Disable default ESLint config resolution
-- Load the plugin via `eslint.config.js` flat config
-- Pass code and rule settings via `--stdin` and `--rule` flags
-
-## Tests Implemented
-
-The script defines an array of test scenarios, each with:
-
-- **name**: A descriptive test name
-- **code**: A string containing JavaScript code to lint
-- **rule**: An ESLint rule override specifying severity
-- **expectedStatus**: The expected exit code (0 or 1)
-
-Current test scenarios:
-
-1. `reports error when @story annotation is missing`
-   - Code: `function foo() {}`
-   - Rule: `traceability/require-story-annotation:error`
-   - Expected exit code: 1 (error reported)
-
-2. `does not report error when @story annotation is present`
-
-   ```js
-   /**
-    * @story docs/stories/003.0-DEV-FUNCTION-ANNOTATIONS.story.md
-    */
-   function foo() {}
-   ```
-
-   - Rule: `traceability/require-story-annotation:error`
-   - Expected exit code: 0 (no error)
-
-3. `reports error when @req annotation is missing`
-   - Code: `function bar() {}`
-   - Rule: `traceability/valid-req-reference:error`
-   - Expected exit code: 1 (error reported)
-
-4. `reports error when @req annotation uses path traversal`
-
-   ```js
-   /**
-    * @req ../docs/requirements/REQ-INVALID.md
-    */
-   function bar() {}
-   ```
-
-   - Rule: `traceability/valid-req-reference:error`
-   - Expected exit code: 1 (error reported)
-
-5. `reports error when @req annotation uses absolute path`
-
-   ```js
-   /**
-    * @req /etc/passwd
-    */
-   function baz() {}
-   ```
-
-   - Rule: `traceability/valid-req-reference:error`
-   - Expected exit code: 1 (error reported)
-
-## Usage
-
-Note: The script lives at the project root.
-
-```bash
-# Run CLI integration tests
-node ./cli-integration.js
-```
-
-## Integration into CI
-
-The CI workflow (`.github/workflows/ci.yml`) includes a separate `integration-tests` job that runs:
-
-```yaml
-jobs:
-  integration-tests:
-    needs: quality-checks
-    run: node cli-integration.js
-```
-
-This ensures that CLI-level behavior is verified on all supported Node.js versions.
-
-## Extending Tests
-
-To add new CLI integration scenarios:
-
-1. Open `cli-integration.js`.
-2. Append a new object to the `tests` array with the desired `name`, `code`, `rule`, and `expectedStatus`.
-3. Run `node cli-integration.js` locally to verify.
-
-Ensure that any new scenarios have clear test names and cover distinct rule behaviors.

package/docs/config-presets.md

@@ -1,38 +0,0 @@
-# Configuration Presets
-
-This document describes the built-in configuration presets provided by the `eslint-plugin-traceability` plugin.
-
-## Recommended Preset
-
-Use the **recommended** preset to enable the core traceability rule set with default settings.
-
-```javascript
-// eslint.config.js
-import js from "@eslint/js";
-import traceability from "eslint-plugin-traceability";
-
-export default [js.configs.recommended, traceability.configs.recommended];
-```
-
-This preset enables the following rules at the `error` level:
-
-- `traceability/require-story-annotation`
-- `traceability/require-req-annotation`
-- `traceability/require-branch-annotation`
-- `traceability/valid-annotation-format`
-- `traceability/valid-story-reference`
-- `traceability/valid-req-reference`
-
-## Strict Preset
-
-Use the **strict** preset to enforce the same core rules, with potential future enhancements for stricter policies.
-
-```javascript
-// eslint.config.js
-import js from "@eslint/js";
-import traceability from "eslint-plugin-traceability";
-
-export default [js.configs.recommended, traceability.configs.strict];
-```
-
-The **strict** preset currently mirrors the **recommended** rules, but may include additional constraints in future plugin versions.