[Planeshifter]

Restores the JSDoc doctest exemption for ESLint rule-definition files.

Description

What is the purpose of this pull request?

This pull request:

• disables stdlib/jsdoc-doctest for etc/eslint/rules/*.js, restoring the legacy exemption introduced in commit fd16a2f49cc.

These files document lint rules using illustrative "Bad" and "Good" examples. Treating intentionally incorrect expected values in that documentation as executable doctests produces misleading lint failures. The override preserves the original path scope and leaves all other lint rules enabled.

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• build: migrate JSDoc linting off removed core rules #10965: introduced the original exemption.
• build: switch Makefiles and pre-commit to flat config (gh54 part VII) #10973: migration to flat configuration omitted the exemption.
• build: restore shared JSDoc settings in flat config #16378, build: restore benchmark ESLint rule overrides #16393, and build: restore example ESLint rule overrides #16394: related restorations of legacy lint configuration.

Reference Packages

Did the content of this pull request follow one or more existing packages? Answering is optional.

This pull request followed these packages:

• No package reference; the change restores etc/eslint/overrides/source.js at fd16a2f49cc.

What carried over from the reference(s)?

• The exact etc/eslint/rules/*.js file pattern and stdlib/jsdoc-doctest: 'off' override.

What differed, or what did you have to work out yourself?

• Added the override as an entry in eslint.config.js and verified that it changes only the intended rule and file scope.

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

Validation:

• Reproduced a doctest failure for an illustrative incorrect expected value under the rule-definition path before applying the override.
• Verified the same documentation is exempt afterward while ordinary source-file doctests still report the error.
• Compared effective rule configurations: only stdlib/jsdoc-doctest changes for rule-definition files.
• Confirmed nested directories outside the original file pattern retain doctest checking.
• Confirmed no-undef still detects undefined names in rule-definition files.
• Linted eslint.config.js and all 11 JavaScript files under etc/eslint/rules/: zero errors and nine warnings in existing code.
• git diff --check, normal pre-commit checks, and the pre-push dependency license check passed.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

This PR was written primarily by OpenAI Codex under human direction, including investigation, implementation, validation, and the PR description.

---

@stdlib-js/reviewers