[Planeshifter]

Restores example linting behavior lost during the flat-config migration.

Description

What is the purpose of this pull request?

This pull request:

• sets no-new-wrappers to warn for JavaScript examples.
• disables stdlib/jsdoc-doctest, stdlib/vars-order, and stdlib/no-unnecessary-nested-functions for examples.
• enables stdlib/doctest and stdlib/require-last-path-relative for examples.

This restores checks of inline expected values and the final relative import, while preserving the legacy example-specific relaxations. Example code continues to be evaluated by stdlib/doctest to validate inline expected values.

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• build: switch Makefiles and pre-commit to flat config (gh54 part VII) #10973: migration to flat configuration omitted these overrides.
• build: restore shared JSDoc settings in flat config #16378: related restoration of shared JSDoc settings.
• build: restore benchmark ESLint rule overrides #16393: related restoration of benchmark overrides.

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 changes restore the legacy example configuration at f6df0741b98 and the legacy editor example overrides at the same commit.

What carried over from the reference(s)?

• The original severities for all six restored rules, including the nested-function exemption from the editor overrides.

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

• Applied the settings in the existing flat-config example entry, making them available through both CLI linting and editor integration, including nested example paths.

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:

• Confirmed the baseline silently accepts an incorrect inline expected value.
• Verified all six severities for both example and nested example paths.
• Verified inline doctests reject incorrect expected values and accept correct values.
• Verified wrapper construction produces a warning and the final require must be relative.
• Verified the variable-order and nested-function relaxations apply to examples, with source-file settings unchanged.
• Linted eslint.config.js and representative examples from assert/is-function and array/fixed-endian-factory: zero errors; existing warnings on the config's path import and an unused disable directive in the is-function example.
• 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