chore: propagate node/ -> n/ eslint plugin prefix update across README directives

[Planeshifter]

Propagating fixes merged to develop between 2026-04-27 15:46 PT and 2026-04-27 19:00 ET to sibling packages.

Description

What is the purpose of this pull request?

This pull request:

• Propagates the deprecated-eslint-plugin-prefix fix from 54c4bf0a ("chore: minor clean-up") to README HTML <!-- eslint-disable ... --> directives across 11 sibling packages.

54c4bf0a — node/ -> n/ plugin prefix in README directives

54c4bf0a renamed the ESLint plugin prefix from node/ to n/ in etc/eslint/plugin/index.js, but 11 README files still carry <!-- eslint-disable node/... --> directives that silently no-op against the renamed plugin. Updated each directive to the n/ prefix so the disable comments resolve to active rules again. Rules referenced are no-unpublished-require, no-path-concat, no-process-exit, no-unsupported-features/es-syntax, and no-unsupported-features/node-builtins — all present under the n/ prefix in etc/eslint/rules/nodejs.js.

• _tools/eslint/rules/first-unit-test
• _tools/test-cov/tape-istanbul
• array/to-json
• assert/is-arrow-function
• assert/is-class
• assert/is-generator-object
• math/base/tools/continued-fraction
• math/base/tools/sum-series
• net/http-server
• net/http2-secure-server
• os/num-cpus

Related Issues

Does this pull request have any related issues?

No.

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. Pattern search scoped to lib/**/*.{js,cjs,mjs,ts,md} and etc/**; only README.md HTML directives surfaced. Two independent validation agents confirmed every site against etc/eslint/rules/nodejs.js to verify each rule resolves under the n/ prefix; an adaptation agent produced verbatim mechanical patches; a style-consistency agent confirmed each patch preserves indentation, comma-space separators, rule ordering, and trailing whitespace (notably the double-space before --> on assert/is-class/README.md line 37). All 16 line-level edits across 11 files survived filtering.

Out of scope / deliberately excluded. No sites flagged needs-human. The 24-hour candidate window also surfaced patterns from bb1eae9b2 (single-file lint-restructure with no grep signature), 6a4d9614 (already fully propagated across stats/base/dists/*), 8b687a9f (already fully propagated across blas/base/ndarray/*), and the backtick-require subpattern of 54c4bf0a7 (already fully propagated). No remaining sites for those patterns.

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 generated by Claude Code as part of a fix-propagation routine: candidate commits from the last 24 hours of develop were filtered for generalizable patterns, sibling sites were enumerated by rg-based search agents, and each proposed patch was independently validated by two opus agents plus an opus adaptation agent and a sonnet style-consistency agent before being applied verbatim.

---

@stdlib-js/reviewers

---

Generated by Claude Code

[kgryte]

As the CI failure is not due to changes introduced in this PR, I'll go ahead and merge.