chore: clean-up

[Planeshifter]

Follow-up fixes for commits merged to develop between 2026-09-26 02:09 UTC and 2026-09-26 10:55 UTC (947861b67..05ed6e856, 45 first-parent commits, 279 files).

Description

What is the purpose of this pull request?

This pull request:

_tools/repl-txt/wrap-text

• In 81c7584d9, docs/usage.txt advertised -i for --indent and -w for --max-width, but neither alias is registered in etc/cli_opts.json, so minimist parsed them as flags.i/flags.w while bin/cli reads flags.indent/flags['max-width'] — both short forms silently no-op'd and the defaults (4, 80) applied. The aliases are intentionally absent (i and w carry other conventional meanings), so ecf705995 removes the short forms from the usage text rather than registering them, rendering both as long-only options the way _tools/github/get and net/disposable-http-server do.

blas/ext/fill-range

• Fix 71a87cf23: blas/ext/fill-range complex128 @example in lib/node_modules/@stdlib/blas/ext/fill-range/docs/types/index.d.ts (line 241) shows <Complex128>[ 00.0, 0.0 ]; drop the stray leading zero to 0.0.

Two intermediate commits net out to nothing and can be skipped when reading the diff:

• ea85e5080 registered the -i/-w aliases in etc/cli_opts.json. That was the wrong side of the inconsistency; reverted in ecf705995 per review.
• dc7a4a233 added whitespace after the commas in the kernel2d–kernel10d signatures in ndarray/base/kernels/generic/ternary-strided1d/blocked/docs/repl.txt; reverted in 164116892. REPL help is capped at 80 characters by @stdlib/_tools/repl-txt/rules/line-length, and the ternary signature runs to 83–84 characters when fully spaced. The compact spacing in 25aa58ae7 is how the signature was made to fit. The binary and unary siblings have one fewer argument per group and stay under the cap, which is why theirs are spaced.

Net diff is 2 files, 3 lines.

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

Checked across the window:

• Style guide compliance — every new package was diffed against an established reference sibling of comparable complexity (fast/acoshf ↔ fast/acosh, exp10f ↔ exp10, cfill/zfill ↔ gfill, gfill-by ↔ gfill, fill-range ↔ copy-within, last-index-of-truthy ↔ last-index-of-falsy, ternary-strided1d/blocked ↔ binary-strided1d/blocked, fftpack/ndarray/{float32,float64}/rfftf ↔ fftpack/ndarray/generic/rfftf, repl-txt/wrap-text ↔ repl-txt/wrap-desc), against docs/style-guides.
• Bug scan — JS lib/main.js vs. C src/main.c agreement for the three new float32 math kernels (polynomial coefficients, special-case ordering, NaN/±Inf/domain thresholds); stride/offset/block-size arithmetic in all nine ternary-strided1d/blocked dimensionality kernels; dtype→kernel dispatch tables and argument-arity overloads in the new blas/ext packages; examples/index.js executed for every new package.
• ULP test migrations — the seven stats/** migrations to isAlmostSameValue were re-derived empirically against their Julia fixtures; every migrated ULP argument reproduces the measured distance exactly.

Deliberately excluded (recorded but not acted on):

• Namespace docs/types/index.d.ts gaps — rfftf is registered in fft/base/fftpack/ndarray/{float32,float64}/lib/index.js and cfill/zfill/gfillBy in blas/ext/base/ndarray/lib/index.js, but none are declared in the corresponding namespace .d.ts. stdlib-bot backfills these automatically — 116141557 did exactly that for ndarray/generic within this same window — so hand-editing them here would only conflict with the next bot run.
• The rffti placeholder docstring (TODO) in fft/base/fftpack/ndarray/float32/docs/types/index.d.ts, same bot-maintained file.
• // returns <ndarray>[ 2 ] for a zero-dimensional output in the blas/ext/last-index-of-truthy assign examples — resolving this requires a judgment call on ndarray print formatting.
• The unused "integer" key in wrap-text's etc/cli_opts.json (not a minimist option, no effect) — dead config, out of scope for a targeted fix.

Anything requiring interpretation, subjective preference, or changes outside the window's diff to validate was dropped rather than guessed at.

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 entirely by Claude Code as part of an automated daily review of commits merged to develop. Candidate issues were produced by independent reviewer agents, then re-verified by re-reading the diff and the referenced files before any edit was made; findings that could not be reproduced that way were dropped. Two that survived that filter were still wrong and have been reverted, as described above.

---

🤖 Generated with Claude Code

https://claude.ai/code/session_01LeUVqypEsPk1bBjJY3615J

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
blas/ext/fill-range	$\\color{green}484/484$ $\\color{green}+0.00\\%$	$\\color{green}55/55$ $\\color{green}+0.00\\%$	$\\color{green}2/2$ $\\color{green}+0.00\\%$	$\\color{green}484/484$ $\\color{green}+0.00\\%$

The above coverage report was generated for the changes in this PR.

[kgryte]

Why was this re-added? The point is that we don't want these aliases, as they are not commonly used for these purposes and we should avoid confusing users accustomed to other meanings for i and w.

[Planeshifter]

Understood — reverted in ecf705995; etc/cli_opts.json is back to its state on develop.

What prompted it: docs/usage.txt advertised -i and -w, so minimist parsed them as flags.i/flags.w and bin/cli (reading flags.indent/flags['max-width']) ignored them silently. I fixed the wrong side. ecf705995 drops the two short forms from the usage text instead, rendering them as long-only the way _tools/github/get and net/disposable-http-server do.

---

Generated by Claude Code

[kgryte]

Left initial comment.