[Planeshifter]

Description

This pull request normalizes production REPL help files to exactly two trailing LF characters (\n\n), matching the existing scaffold templates and the dominant codebase convention for the empty See Also section.

• Add one trailing newline to 790 files.
• Remove one trailing newline from 10 files.
• Leave the remaining 4,883 production help files unchanged.

All bytes preceding the final newline run and all file modes are preserved. Test fixtures are excluded.

Related Issues

None. This is a repository-wide documentation formatting cleanup.

Reference Packages

This follows the seven REPL scaffold templates under lib/node_modules/@stdlib/_tools/scaffold and the guidance in docs/contributing/repl_text.md.

The EOF format carried over unchanged from those templates; no package behavior or REPL examples were edited.

Questions

No.

Other

Validation:

• Inspected all 5,683 production docs/repl.txt files on the base commit.
• Verified that every production help file ends with exactly two LF characters after this change.
• Verified byte-for-byte identity before the trailing newline run for every changed file and preservation of file modes.
• Parsed all 800 changed files before and after normalization and verified equivalent ASTs, excluding source line positions and trailing newline padding.
• Filename, EditorConfig, license-header, dependency-license, and commit-message checks passed.
• The normal commit hook fails REPL-help lint on 121 pre-existing errors in 57 files, plus 16 warnings. Before/after validation shows identical rule IDs, messages, severities, and counts; only one diagnostic end-line position shifts with the EOF padding. No new diagnostics were introduced. The maintainer approved skipping only REPL-help lint for this EOF-only commit; the remaining commit and push hooks remain enabled.

Git's generic whitespace check reports added blank lines at EOF; those lines are the intentional formatting change in this PR.

Checklist

• Read, understood, and followed the contributing guidelines.

AI Assistance

• Yes
• No

How AI assistance was used:

• Code generation (the temporary normalization and verification scripts)
• Test/benchmark generation
• Documentation (including this description)
• Research and understanding

Disclosure

Codex prepared the EOF-only normalization and validation scripts, checked the resulting diff, and drafted this description under maintainer direction.

---

[kgryte]

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