feat: add _tools/repl-txt/rules/no-premature-wrap

[headlessNode]

Resolves stdlib-js/metr-issue-tracker#1375.

Description

What is the purpose of this pull request?

This pull request:

• add _tools/repl-txt/rules/no-premature-wrap

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• Resolves [RFC]: add _tools/repl-txt/rules/no-premature-wrap metr-issue-tracker#1375.

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.

No.

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.".

Primarily written by Claude Code.

---

@stdlib-js/reviewers

[headlessNode]

Found a bug in wrap-text where it wraps the content of backticks like below:

Beep boop `-1`

to

Beep boop `-
1`

PR for the fix: #15588

[headlessNode]

@kgryte One thing I noticed while working on this: there's no convention for tables in repl.txt files, AFAIK. That's a problem for this rule, since wrap-text treats table rows by checking whether a line starts with | — anything else is wrapped normally.

For example, math/base/special/signum writes its table without leading/trailing pipes:

Value | Sign
----- | -----
x > 0 |    +1
x < 0 |    -1

while plot/sparklines/unicode/up-down:

| Value | Glyph |
|:-----:|:-----:|
|   1   |   ↑   |
|   -1  |   ↓   |

wrap-text would correctly skip the second table but not the first.

[kgryte]

Hmm...neither is incorrect. The one issue with the latter table markup is that it includes unnecessary/non-applicable Markdown markup to REPL text files where it is not useful.

Regardless, it is not clear why you need to explicitly distinguish handle "table" text any different from normal text.

[headlessNode]

@kgryte We need to know what a table looks like with variation in format we have to take account of a lot of cases. From first example in above, the wrap-text treats it like normal text since the table doesn't start with a Pipe. And it wraps the table like below, because it passes the line length:

Value | Sign ----- | ----- x > 0 |    +1 x < 0 |    -1

[kgryte]

@headlessNode Then it would seem that we need to adopt Markdown-like markup and normalize that across the codebase.

[headlessNode]

@kgryte Should that be done before this PR gets merged?