eslint-plugin-traceability 1.6.1 → 1.6.3

package/lib/src/index.d.ts

@@ -12,6 +12,12 @@ import type { Rule } from "eslint";
 declare const RULE_NAMES: readonly ["require-story-annotation", "require-req-annotation", "require-branch-annotation", "valid-annotation-format", "valid-story-reference", "valid-req-reference"];
 type RuleName = (typeof RULE_NAMES)[number];
 declare const rules: Record<RuleName, Rule.RuleModule>;
+/**
+ * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
+ * @req REQ-ERROR-SEVERITY - Map rule types to appropriate ESLint severity levels (errors vs warnings)
+ * The recommended and strict configs treat missing annotations and missing references as errors,
+ * while formatting issues are reported as warnings, matching the story's severity conventions.
+ */
 declare const configs: {
     recommended: {
         plugins: {

package/lib/src/index.js

@@ -67,6 +67,12 @@ RULE_NAMES.forEach(
         };
     }
 });
+/**
+ * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
+ * @req REQ-ERROR-SEVERITY - Map rule types to appropriate ESLint severity levels (errors vs warnings)
+ * The recommended and strict configs treat missing annotations and missing references as errors,
+ * while formatting issues are reported as warnings, matching the story's severity conventions.
+ */
 const configs = {
     recommended: [
         {

package/lib/src/rules/helpers/require-story-helpers.d.ts

@@ -100,9 +100,11 @@ declare function shouldProcessNode(node: any, scope: string[], exportPriority?:
  * Report a missing @story annotation for a function-like node
  * Provides a suggestion to add the annotation.
  * @story docs/stories/003.0-DEV-FUNCTION-ANNOTATIONS.story.md
+ * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
  * @story docs/stories/008.0-DEV-AUTO-FIX.story.md
  * @req REQ-ANNOTATION-REQUIRED - Implement reporting for missing annotations with suggestion
  * @req REQ-AUTOFIX-MISSING - Provide autofix for missing annotations while preserving suggestions
+ * @req REQ-ERROR-SPECIFIC - Error reports must include both name and functionName in the data payload for specific function context
  * @param {Rule.RuleContext} context - ESLint rule context used to report
  * @param {any} sourceCode - ESLint sourceCode object
  * @param {any} node - AST node that is missing the annotation
@@ -112,10 +114,15 @@ declare function reportMissing(context: Rule.RuleContext, sourceCode: any, node:
 /**
  * Report a missing @story annotation for a method-like node
  * Provides a suggestion to update the method/interface with the annotation.
+ * The error data payload uses both name and functionName for consistent, specific error context.
  * @story docs/stories/003.0-DEV-FUNCTION-ANNOTATIONS.story.md
  * @story docs/stories/008.0-DEV-AUTO-FIX.story.md
+ * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
  * @req REQ-ANNOTATION-REQUIRED - Implement reporting for missing method/interface annotations with suggestion
  * @req REQ-AUTOFIX-MISSING - Provide autofix for missing method/interface annotations while preserving suggestions
+ * @req REQ-ERROR-SPECIFIC - Method error reports must include both name and functionName in the data payload for specific function context
+ * @req REQ-ERROR-LOCATION - Method error reports must use the method name node to anchor error location
+ * @req REQ-ERROR-CONTEXT - Method error reports must include functionName data for consistent error context
  * @param {Rule.RuleContext} context - ESLint rule context to report
  * @param {any} sourceCode - ESLint sourceCode object
  * @param {any} node - AST node that is missing the annotation

package/lib/src/rules/helpers/require-story-helpers.js

@@ -238,9 +238,11 @@ function shouldProcessNode(node, scope, exportPriority = "all") {
  * Report a missing @story annotation for a function-like node
  * Provides a suggestion to add the annotation.
  * @story docs/stories/003.0-DEV-FUNCTION-ANNOTATIONS.story.md
+ * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
  * @story docs/stories/008.0-DEV-AUTO-FIX.story.md
  * @req REQ-ANNOTATION-REQUIRED - Implement reporting for missing annotations with suggestion
  * @req REQ-AUTOFIX-MISSING - Provide autofix for missing annotations while preserving suggestions
+ * @req REQ-ERROR-SPECIFIC - Error reports must include both name and functionName in the data payload for specific function context
  * @param {Rule.RuleContext} context - ESLint rule context used to report
  * @param {any} sourceCode - ESLint sourceCode object
  * @param {any} node - AST node that is missing the annotation
@@ -260,7 +262,7 @@ function reportMissing(context, sourceCode, node, passedTarget) {
         context.report({
             node: nameNode,
             messageId: "missingStory",
-            data: { name },
+            data: { name, functionName: name },
             fix: (0, require_story_core_1.createAddStoryFix)(resolvedTarget),
             suggest: [
                 {
@@ -277,10 +279,15 @@ function reportMissing(context, sourceCode, node, passedTarget) {
 /**
  * Report a missing @story annotation for a method-like node
  * Provides a suggestion to update the method/interface with the annotation.
+ * The error data payload uses both name and functionName for consistent, specific error context.
  * @story docs/stories/003.0-DEV-FUNCTION-ANNOTATIONS.story.md
  * @story docs/stories/008.0-DEV-AUTO-FIX.story.md
+ * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
  * @req REQ-ANNOTATION-REQUIRED - Implement reporting for missing method/interface annotations with suggestion
  * @req REQ-AUTOFIX-MISSING - Provide autofix for missing method/interface annotations while preserving suggestions
+ * @req REQ-ERROR-SPECIFIC - Method error reports must include both name and functionName in the data payload for specific function context
+ * @req REQ-ERROR-LOCATION - Method error reports must use the method name node to anchor error location
+ * @req REQ-ERROR-CONTEXT - Method error reports must include functionName data for consistent error context
  * @param {Rule.RuleContext} context - ESLint rule context to report
  * @param {any} sourceCode - ESLint sourceCode object
  * @param {any} node - AST node that is missing the annotation
@@ -297,7 +304,7 @@ function reportMethod(context, sourceCode, node, passedTarget) {
         context.report({
             node: nameNode,
             messageId: "missingStory",
-            data: { name },
+            data: { name, functionName: name },
             fix: (0, require_story_core_1.createMethodFix)(resolvedTarget),
             suggest: [
                 {

package/lib/src/rules/require-branch-annotation.js

@@ -16,7 +16,11 @@ const rule = {
         },
         fixable: "code",
         messages: {
-            missingAnnotation: "Missing {{missing}} annotation on code branch",
+            /**
+             * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
+             * @req REQ-ERROR-CONSISTENCY - Use shared branch error message convention with {{missing}} placeholder
+             */
+            missingAnnotation: "Branch is missing required annotation: {{missing}}.",
         },
         schema: [
             {

package/lib/src/rules/require-req-annotation.js

@@ -11,7 +11,19 @@ const rule = {
             recommended: "error",
         },
         messages: {
-            missingReq: "Missing @req annotation for function '{{name}}' (REQ-ANNOTATION-REQUIRED)",
+            /**
+             * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
+             * @req REQ-ERROR-CONSISTENCY - Align missing @req function error with cross-rule conventions
+             * @req REQ-ERROR-SPECIFIC - Provide specific function name in error message
+             * @req REQ-ERROR-SUGGESTION - Suggest adding a @req annotation with an example identifier
+             * @req REQ-ERROR-CONTEXT - Include @req format guidance in the error text
+             * @req REQ-ERROR-LOCATION - Report the error at the function identifier location
+             * @req REQ-ERROR-SEVERITY - Use ESLint severity level "error" for missing @req annotations
+             *
+             * This rule uses ESLint's message data placeholders for the function name,
+             * specifically the {{name}} placeholder populated via context.report.
+             */
+            missingReq: "Function '{{functionName}}' is missing a required @req annotation. Add a JSDoc or line comment with @req (for example, '@req REQ-EXAMPLE') referencing the appropriate requirement from the story file.",
         },
         schema: [
             {

package/lib/src/rules/require-story-annotation.d.ts

@@ -16,9 +16,13 @@ import type { Rule } from "eslint";
  * ESLint rule to require @story annotations on functions/methods.
  *
  * @story docs/stories/003.0-DEV-FUNCTION-ANNOTATIONS.story.md
+ * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
  * @story docs/stories/008.0-DEV-AUTO-FIX.story.md
  * @req REQ-ANNOTATION-REQUIRED
  * @req REQ-AUTOFIX-MISSING - This rule participates in auto-fix for missing @story annotations.
+ * @req REQ-ERROR-MSG-CONTENT - Error message instructs adding an explicit @story annotation that points to the implementing story file.
+ * @req REQ-ERROR-MSG-PLACEHOLDER - Error message retains the {{name}} placeholder while also providing functionName in the data payload for cross-rule consistency.
+ * @req REQ-ERROR-MSG-ACTIONABLE - Error message text is concise, imperative, and describes the required remediation.
  */
 declare const rule: Rule.RuleModule;
 export default rule;

package/lib/src/rules/require-story-annotation.js

@@ -6,9 +6,13 @@ const require_story_helpers_1 = require("./helpers/require-story-helpers");
  * ESLint rule to require @story annotations on functions/methods.
  *
  * @story docs/stories/003.0-DEV-FUNCTION-ANNOTATIONS.story.md
+ * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
  * @story docs/stories/008.0-DEV-AUTO-FIX.story.md
  * @req REQ-ANNOTATION-REQUIRED
  * @req REQ-AUTOFIX-MISSING - This rule participates in auto-fix for missing @story annotations.
+ * @req REQ-ERROR-MSG-CONTENT - Error message instructs adding an explicit @story annotation that points to the implementing story file.
+ * @req REQ-ERROR-MSG-PLACEHOLDER - Error message retains the {{name}} placeholder while also providing functionName in the data payload for cross-rule consistency.
+ * @req REQ-ERROR-MSG-ACTIONABLE - Error message text is concise, imperative, and describes the required remediation.
  */
 const rule = {
     meta: {
@@ -29,7 +33,7 @@ const rule = {
          */
         fixable: "code",
         messages: {
-            missingStory: "Missing @story annotation for function '{{name}}' (REQ-ANNOTATION-REQUIRED)",
+            missingStory: "Function '{{name}}' must have an explicit @story annotation. Add a JSDoc or line comment with @story that points to the implementing story file (for example, docs/stories/003.0-DEV-FUNCTION-ANNOTATIONS.story.md).",
         },
         schema: [
             {

package/lib/src/rules/valid-annotation-format.js

@@ -324,8 +324,20 @@ exports.default = {
             recommended: "error",
         },
         messages: {
-            invalidStoryFormat: "{{details}}",
-            invalidReqFormat: "{{details}}",
+            /**
+             * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
+             * @req REQ-ERROR-SPECIFIC - Provide specific details about invalid @story annotation format
+             * @req REQ-ERROR-CONTEXT - Include human-readable details about the expected @story annotation format
+             * @req REQ-ERROR-CONSISTENCY - Use shared "Invalid annotation format: {{details}}." message pattern across rules
+             */
+            invalidStoryFormat: "Invalid annotation format: {{details}}.",
+            /**
+             * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
+             * @req REQ-ERROR-SPECIFIC - Provide specific details about invalid @req annotation format
+             * @req REQ-ERROR-CONTEXT - Include human-readable details about the expected @req annotation format
+             * @req REQ-ERROR-CONSISTENCY - Use shared "Invalid annotation format: {{details}}." message pattern across rules
+             */
+            invalidReqFormat: "Invalid annotation format: {{details}}.",
         },
         schema: [],
         /**

package/lib/src/rules/valid-req-reference.js

@@ -170,7 +170,21 @@ exports.default = {
             recommended: "error",
         },
         messages: {
+            /**
+             * @story docs/stories/010.0-DEV-DEEP-VALIDATION.story.md
+             * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
+             * @req REQ-ERROR-SPECIFIC - Provide specific diagnostics when a referenced requirement ID cannot be found in a story
+             * @req REQ-ERROR-CONTEXT - Include both the missing requirement ID and the story path in the message
+             * @req REQ-ERROR-CONSISTENCY - Use a consistent message template for requirement lookup failures
+             */
             reqMissing: "Requirement '{{reqId}}' not found in '{{storyPath}}'",
+            /**
+             * @story docs/stories/010.0-DEV-DEEP-VALIDATION.story.md
+             * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
+             * @req REQ-ERROR-SPECIFIC - Indicate that the story path associated with a @req annotation is invalid
+             * @req REQ-ERROR-CONTEXT - Include the problematic storyPath value so the developer can correct it
+             * @req REQ-ERROR-CONSISTENCY - Reuse the same storyPath placeholder convention used by other rules
+             */
             invalidPath: "Invalid story path '{{storyPath}}'",
         },
         schema: [],

package/lib/src/rules/valid-story-reference.js

@@ -36,18 +36,37 @@ function validateStoryPath(opts) {
     });
 }
 /**
- * Report any problems related to the existence or accessibility of the
- * referenced story file. Filesystem and I/O errors are surfaced with a
- * dedicated diagnostic that differentiates them from missing files.
+ * Analyze candidate paths against the project boundary, returning whether any
+ * are within the project and whether any are outside.
+ *
+ * @story docs/stories/006.0-DEV-FILE-VALIDATION.story.md
+ * @req REQ-PROJECT-BOUNDARY - Validate files are within project boundaries
+ * @req REQ-CONFIGURABLE-PATHS - Respect configured storyDirectories while enforcing project boundaries
+ */
+function analyzeCandidateBoundaries(candidates, cwd) {
+    let hasInProjectCandidate = false;
+    let hasOutOfProjectCandidate = false;
+    for (const candidate of candidates) {
+        const boundary = (0, storyReferenceUtils_1.enforceProjectBoundary)(candidate, cwd);
+        if (boundary.isWithinProject) {
+            hasInProjectCandidate = true;
+        }
+        else {
+            hasOutOfProjectCandidate = true;
+        }
+    }
+    return { hasInProjectCandidate, hasOutOfProjectCandidate };
+}
+/**
+ * Handle existence status and report appropriate diagnostics for missing
+ * or filesystem-error conditions, assuming project-boundary checks have
+ * already been applied.
  *
  * @story docs/stories/006.0-DEV-FILE-VALIDATION.story.md
  * @req REQ-FILE-EXISTENCE - Ensure referenced files exist
  * @req REQ-ERROR-HANDLING - Differentiate missing files from filesystem errors
  */
-function reportExistenceProblems(opts) {
-    const { storyPath, commentNode, context, cwd, storyDirs } = opts;
-    const result = (0, storyReferenceUtils_1.normalizeStoryPath)(storyPath, cwd, storyDirs);
-    const existenceResult = result.existence;
+function reportExistenceStatus(existenceResult, storyPath, commentNode, context) {
     if (!existenceResult || existenceResult.status === "exists") {
         return;
     }
@@ -81,6 +100,48 @@ function reportExistenceProblems(opts) {
         });
     }
 }
+/**
+ * Report any problems related to the existence or accessibility of the
+ * referenced story file. Filesystem and I/O errors are surfaced with a
+ * dedicated diagnostic that differentiates them from missing files.
+ *
+ * @story docs/stories/006.0-DEV-FILE-VALIDATION.story.md
+ * @req REQ-FILE-EXISTENCE - Ensure referenced files exist
+ * @req REQ-ERROR-HANDLING - Differentiate missing files from filesystem errors
+ * @req REQ-PROJECT-BOUNDARY - Ensure resolved candidate paths remain within the project root
+ * @req REQ-CONFIGURABLE-PATHS - Respect configured storyDirectories while enforcing project boundaries
+ */
+function reportExistenceProblems(opts) {
+    const { storyPath, commentNode, context, cwd, storyDirs } = opts;
+    const result = (0, storyReferenceUtils_1.normalizeStoryPath)(storyPath, cwd, storyDirs);
+    const existenceResult = result.existence;
+    const candidates = result.candidates || [];
+    if (candidates.length > 0) {
+        const { hasInProjectCandidate, hasOutOfProjectCandidate } = analyzeCandidateBoundaries(candidates, cwd);
+        if (hasOutOfProjectCandidate && !hasInProjectCandidate) {
+            context.report({
+                node: commentNode,
+                messageId: "invalidPath",
+                data: { path: storyPath },
+            });
+            return;
+        }
+    }
+    if (existenceResult &&
+        existenceResult.status === "exists" &&
+        existenceResult.matchedPath) {
+        const boundary = (0, storyReferenceUtils_1.enforceProjectBoundary)(existenceResult.matchedPath, cwd);
+        if (!boundary.isWithinProject) {
+            context.report({
+                node: commentNode,
+                messageId: "invalidPath",
+                data: { path: storyPath },
+            });
+            return;
+        }
+    }
+    reportExistenceStatus(existenceResult, storyPath, commentNode, context);
+}
 /**
  * Process and validate the story path for security, extension, and existence.
  * Filesystem and I/O errors are handled inside the underlying utilities
@@ -103,8 +164,10 @@ function processStoryPath(opts) {
                 messageId: "invalidPath",
                 data: { path: storyPath },
             });
+            return;
         }
-        return;
+        // When absolute paths are allowed, we still enforce extension and
+        // project-boundary checks below via the existence phase.
     }
     // Path traversal check
     if ((0, storyReferenceUtils_1.containsPathTraversal)(storyPath)) {
@@ -180,8 +243,29 @@ exports.default = {
             recommended: "error",
         },
         messages: {
+            /**
+             * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
+             * @story docs/stories/006.0-DEV-FILE-VALIDATION.story.md
+             * @req REQ-ERROR-SPECIFIC - Provide specific diagnostics when a referenced story file cannot be found
+             * @req REQ-ERROR-CONTEXT - Include the original story path in the error message for troubleshooting
+             * @req REQ-ERROR-CONSISTENCY - Use consistent file-related error wording and placeholders across rules
+             */
             fileMissing: "Story file '{{path}}' not found",
+            /**
+             * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
+             * @story docs/stories/006.0-DEV-FILE-VALIDATION.story.md
+             * @req REQ-ERROR-SPECIFIC - Indicate that the story file extension is invalid and what is expected
+             * @req REQ-ERROR-CONTEXT - Include the provided path so developers can see which reference is wrong
+             * @req REQ-ERROR-CONSISTENCY - Reuse the same pattern of "{{path}}" placeholder across file validation messages
+             */
             invalidExtension: "Invalid story file extension for '{{path}}', expected '.story.md'",
+            /**
+             * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
+             * @story docs/stories/006.0-DEV-FILE-VALIDATION.story.md
+             * @req REQ-ERROR-SPECIFIC - Explain that the story path is invalid due to absolute or unsafe traversal
+             * @req REQ-ERROR-CONTEXT - Surface the offending path to assist with correcting the reference
+             * @req REQ-ERROR-CONSISTENCY - Maintain a consistent template for invalid path diagnostics across rules
+             */
             invalidPath: "Invalid story path '{{path}}'",
             /**
              * @story docs/stories/006.0-DEV-FILE-VALIDATION.story.md
@@ -202,7 +286,7 @@ exports.default = {
         ],
     },
     create(context) {
-        const cwd = process.cwd();
+        const cwd = context.cwd ?? process.cwd();
         const opts = context.options[0];
         const storyDirs = opts?.storyDirectories || defaultStoryDirs;
         const allowAbsolute = opts?.allowAbsolutePaths || false;

package/lib/src/utils/annotation-checker.js

@@ -2,6 +2,7 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.checkReqAnnotation = checkReqAnnotation;
 const require_story_utils_1 = require("../rules/helpers/require-story-utils");
+const require_story_io_1 = require("../rules/helpers/require-story-io");
 /**
  * Helper to retrieve the JSDoc comment for a node.
  * @story docs/stories/003.0-DEV-FUNCTION-ANNOTATIONS.story.md
@@ -42,12 +43,94 @@ function combineComments(leading, before) {
 function commentContainsReq(c) {
     return c && typeof c.value === "string" && c.value.includes("@req");
 }
+/**
+ * Line-based helper adapted from linesBeforeHasStory to detect @req.
+ */
+function linesBeforeHasReq(sourceCode, node) {
+    const lines = sourceCode && sourceCode.lines;
+    const startLine = node && node.loc && typeof node.loc.start?.line === "number"
+        ? node.loc.start.line
+        : null;
+    if (!Array.isArray(lines) || typeof startLine !== "number") {
+        return false;
+    }
+    const from = Math.max(0, startLine - 1 - require_story_io_1.LOOKBACK_LINES);
+    const to = Math.max(0, startLine - 1);
+    for (let i = from; i < to; i++) {
+        const text = lines[i];
+        if (typeof text === "string" && text.includes("@req")) {
+            return true;
+        }
+    }
+    return false;
+}
+/**
+ * Parent-chain helper adapted from parentChainHasStory to detect @req.
+ */
+function parentChainHasReq(sourceCode, node) {
+    let p = node && node.parent;
+    while (p) {
+        const pComments = typeof sourceCode?.getCommentsBefore === "function"
+            ? sourceCode.getCommentsBefore(p) || []
+            : [];
+        if (Array.isArray(pComments) &&
+            pComments.some((c) => typeof c.value === "string" && c.value.includes("@req"))) {
+            return true;
+        }
+        const pLeading = p.leadingComments || [];
+        if (Array.isArray(pLeading) &&
+            pLeading.some((c) => typeof c.value === "string" && c.value.includes("@req"))) {
+            return true;
+        }
+        p = p.parent;
+    }
+    return false;
+}
+/**
+ * Fallback text window helper adapted from fallbackTextBeforeHasStory to detect @req.
+ */
+function fallbackTextBeforeHasReq(sourceCode, node) {
+    if (typeof sourceCode?.getText !== "function" ||
+        !Array.isArray((node && node.range) || [])) {
+        return false;
+    }
+    const range = node.range;
+    if (!Array.isArray(range) || typeof range[0] !== "number") {
+        return false;
+    }
+    try {
+        const start = Math.max(0, range[0] - require_story_io_1.FALLBACK_WINDOW);
+        const textBefore = sourceCode.getText().slice(start, range[0]);
+        if (typeof textBefore === "string" && textBefore.includes("@req")) {
+            return true;
+        }
+    }
+    catch {
+        /* noop */
+    }
+    return false;
+}
 /**
  * Helper to determine whether a JSDoc or any nearby comments contain a @req annotation.
  * @story docs/stories/003.0-DEV-FUNCTION-ANNOTATIONS.story.md
  * @req REQ-ANNOTATION-REQ-DETECTION - Determine presence of @req annotation
  */
-function hasReqAnnotation(jsdoc, comments) {
+function hasReqAnnotation(jsdoc, comments, context, node) {
+    try {
+        const sourceCode = context && typeof context.getSourceCode === "function"
+            ? context.getSourceCode()
+            : undefined;
+        if (sourceCode && node) {
+            if (linesBeforeHasReq(sourceCode, node) ||
+                parentChainHasReq(sourceCode, node) ||
+                fallbackTextBeforeHasReq(sourceCode, node)) {
+                return true;
+            }
+        }
+    }
+    catch {
+        // Swallow detection errors and fall through to simple checks.
+    }
     // BRANCH @req detection on JSDoc or comments
     // @story docs/stories/003.0-DEV-FUNCTION-ANNOTATIONS.story.md
     // @req REQ-ANNOTATION-REQ-DETECTION
@@ -103,14 +186,21 @@ function createMissingReqFix(node) {
  * @req REQ-ANNOTATION-REPORTING - Report missing @req annotation to context
  * @req REQ-ERROR-SPECIFIC - Provide specific error details including node name
  * @req REQ-ERROR-LOCATION - Include contextual location information in errors
+ * @req REQ-ERROR-SUGGESTION - Provide actionable suggestions or fixes where possible
+ * @req REQ-ERROR-CONTEXT - Include contextual hints to help understand the error
  */
 function reportMissing(context, node, enableFix = true) {
     const rawName = (0, require_story_utils_1.getNodeName)(node) ?? (node && (0, require_story_utils_1.getNodeName)(node.parent));
     const name = rawName ?? "(anonymous)";
+    const nameNode = (node && node.id && node.id.type === "Identifier"
+        ? node.id
+        : node && node.key && node.key.type === "Identifier"
+            ? node.key
+            : node) ?? node;
     const reportOptions = {
-        node,
+        node: nameNode,
         messageId: "missingReq",
-        data: { name },
+        data: { name, functionName: name },
     };
     if (enableFix) {
         reportOptions.fix = createMissingReqFix(node);
@@ -133,7 +223,7 @@ function checkReqAnnotation(context, node, options) {
     const leading = getLeadingComments(node);
     const comments = getCommentsBefore(sourceCode, node);
     const all = combineComments(leading, comments);
-    const hasReq = hasReqAnnotation(jsdoc, all);
+    const hasReq = hasReqAnnotation(jsdoc, all, context, node);
     // BRANCH when a @req annotation is missing and must be reported
     // @story docs/stories/003.0-DEV-FUNCTION-ANNOTATIONS.story.md
     // @req REQ-ANNOTATION-REQ-DETECTION

package/lib/src/utils/storyReferenceUtils.d.ts

@@ -31,6 +31,34 @@ export interface StoryExistenceResult {
     matchedPath?: string;
     error?: unknown;
 }
+/**
+ * Result of validating that a candidate path stays within the project boundary.
+ * @story docs/stories/006.0-DEV-FILE-VALIDATION.story.md
+ * @req REQ-PROJECT-BOUNDARY - Validate files are within project boundaries
+ */
+export interface ProjectBoundaryCheckResult {
+    candidate: string;
+    isWithinProject: boolean;
+}
+/**
+ * Validate that a candidate path stays within the project boundary.
+ * This compares the resolved candidate path against the normalized cwd
+ * prefix, ensuring that even when storyDirectories are misconfigured, we
+ * never treat files outside the project as valid story references.
+ *
+ * @story docs/stories/006.0-DEV-FILE-VALIDATION.story.md
+ * @req REQ-PROJECT-BOUNDARY - Validate files are within project boundaries
+ */
+export declare function enforceProjectBoundary(candidate: string, cwd: string): ProjectBoundaryCheckResult;
+/**
+ * Internal helper to reset the filesystem existence cache. This is primarily
+ * intended for tests that need to run multiple scenarios with different
+ * mocked filesystem behavior without carrying over cached results.
+ *
+ * @story docs/stories/006.0-DEV-FILE-VALIDATION.story.md
+ * @req REQ-PERFORMANCE-OPTIMIZATION - Allow safe cache reset in tests to avoid stale entries
+ */
+export declare function __resetStoryExistenceCacheForTests(): void;
 /**
  * Build candidate file paths for a given story path.
  * @story docs/stories/006.0-DEV-FILE-VALIDATION.story.md

package/lib/src/utils/storyReferenceUtils.js

@@ -3,6 +3,8 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
     return (mod && mod.__esModule) ? mod : { "default": mod };
 };
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.enforceProjectBoundary = enforceProjectBoundary;
+exports.__resetStoryExistenceCacheForTests = __resetStoryExistenceCacheForTests;
 exports.buildStoryCandidates = buildStoryCandidates;
 exports.getStoryExistence = getStoryExistence;
 exports.storyExists = storyExists;
@@ -22,6 +24,36 @@ exports.isUnsafeStoryPath = isUnsafeStoryPath;
  */
 const fs_1 = __importDefault(require("fs"));
 const path_1 = __importDefault(require("path"));
+/**
+ * Validate that a candidate path stays within the project boundary.
+ * This compares the resolved candidate path against the normalized cwd
+ * prefix, ensuring that even when storyDirectories are misconfigured, we
+ * never treat files outside the project as valid story references.
+ *
+ * @story docs/stories/006.0-DEV-FILE-VALIDATION.story.md
+ * @req REQ-PROJECT-BOUNDARY - Validate files are within project boundaries
+ */
+function enforceProjectBoundary(candidate, cwd) {
+    const normalizedCwd = path_1.default.resolve(cwd);
+    const normalizedCandidate = path_1.default.resolve(candidate);
+    const isWithinProject = normalizedCandidate === normalizedCwd ||
+        normalizedCandidate.startsWith(normalizedCwd + path_1.default.sep);
+    return {
+        candidate: normalizedCandidate,
+        isWithinProject,
+    };
+}
+/**
+ * Internal helper to reset the filesystem existence cache. This is primarily
+ * intended for tests that need to run multiple scenarios with different
+ * mocked filesystem behavior without carrying over cached results.
+ *
+ * @story docs/stories/006.0-DEV-FILE-VALIDATION.story.md
+ * @req REQ-PERFORMANCE-OPTIMIZATION - Allow safe cache reset in tests to avoid stale entries
+ */
+function __resetStoryExistenceCacheForTests() {
+    fileExistStatusCache.clear();
+}
 /**
  * Build candidate file paths for a given story path.
  * @story docs/stories/006.0-DEV-FILE-VALIDATION.story.md

package/lib/tests/cli-error-handling.test.js

@@ -39,6 +39,6 @@ describe("CLI Error Handling for Traceability Plugin (Story 001.0-DEV-PLUGIN-SET
         });
         // Expect non-zero exit and missing annotation message on stdout
         expect(result.status).not.toBe(0);
-        expect(result.stdout).toContain("Missing @story annotation");
+        expect(result.stdout).toContain("Function 'foo' must have an explicit @story annotation. Add a JSDoc or line comment with @story that points to the implementing story file (for example, docs/stories/003.0-DEV-FUNCTION-ANNOTATIONS.story.md)");
     });
 });

package/lib/tests/plugin-default-export-and-configs.test.js

@@ -36,7 +36,9 @@ Object.defineProperty(exports, "__esModule", { value: true });
 /**
  * Tests for: docs/stories/001.0-DEV-PLUGIN-SETUP.story.md
  * @story docs/stories/001.0-DEV-PLUGIN-SETUP.story.md
+ * @story docs/stories/007.0-DEV-ERROR-REPORTING.story.md
  * @req REQ-PLUGIN-STRUCTURE - Validate plugin default export and configs in src/index.ts
+ * @req REQ-ERROR-SEVERITY - Validate error severity configuration in plugin configs
  */
 const index_1 = __importStar(require("../src/index"));
 describe("Plugin Default Export and Configs (Story 001.0-DEV-PLUGIN-SETUP)", () => {
@@ -69,4 +71,18 @@ describe("Plugin Default Export and Configs (Story 001.0-DEV-PLUGIN-SETUP)", ()
         const strictRules = index_1.configs.strict[0].rules;
         expect(strictRules).toEqual(index_1.configs.recommended[0].rules);
     });
+    it("[REQ-ERROR-SEVERITY] configs.recommended maps valid-annotation-format to warn and others to error", () => {
+        const recommendedRules = index_1.configs.recommended[0].rules;
+        expect(recommendedRules).toHaveProperty("traceability/valid-annotation-format", "warn");
+        expect(recommendedRules).toHaveProperty("traceability/require-story-annotation", "error");
+        expect(recommendedRules).toHaveProperty("traceability/require-req-annotation", "error");
+        expect(recommendedRules).toHaveProperty("traceability/require-branch-annotation", "error");
+        expect(recommendedRules).toHaveProperty("traceability/valid-story-reference", "error");
+        expect(recommendedRules).toHaveProperty("traceability/valid-req-reference", "error");
+    });
+    it("[REQ-ERROR-SEVERITY] configs.strict uses same severity mapping as recommended", () => {
+        const strictRules = index_1.configs.strict[0].rules;
+        const recommendedRules = index_1.configs.recommended[0].rules;
+        expect(strictRules).toEqual(recommendedRules);
+    });
 });