chore: update keywords

[Planeshifter]

Description

What is the purpose of this pull request?

Follow-up fixes for commits merged to develop between 2026-09-30 12:12:44 -0700 (77280218a) and 2026-10-01 03:45:10 -0700 (9eeec88f9).

This pull request:

• blas/ext/base/ndarray/scusome: In c03fb16, lib/node_modules/@stdlib/blas/ext/base/ndarray/scusome/package.json omits the package name and dtype keywords, unlike sibling dcusome. Add "scusome", "float32", "single-precision", and "float32array" in the positions matching dcusome's "dcusome", "float64", "double-precision", and "float64array".

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

• Window: 65 first-parent commits on develop (77280218a..9eeec88f9), 549 files changed. Main themes: the new blas/ext/base/ndarray weighted-op wrappers (*wax, *wapx, *wxpy, *wxsy, gwxmy, gwxdy, gwaxpb, cxdy, {d,s}cusome); strided zwxpy, cwxmy, and cxdy; the ndarray/zwxsa C implementation; blas/ext/cusome; gindex-of-greater-than-equal-sorted; powm1f; truncsdf; fftpack/generic/hc2c; ULP test migrations; and namespace wiring.
• Checked:
  • Two independent passes for style-guide compliance. Each new package was diffed against a reference package that already existed before the window.
  • Two independent bug scans: one on the diff only, and one on the introduced logic. These ran the new and changed JS tests, executed the README/JSDoc/repl examples, and checked the CI workflow change for injection.
• Excluded:
  • Anything requiring interpretation.
  • stdlib-bot generated files.
  • Intentional duplication across the type-prefixed wrapper families.
• Considered but dropped:
  • fft/base/fftpack/generic/hc2c/test/test.js L150-151 (a9f2296): the odd-length "no Nyquist component" assertion checks out.length, which can never change, so it can never fail. Dropped because the right fix (delete it, or add a trailing sentinel element) is a judgment call.

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 Claude Code as part of an automated daily review of commits merged to develop. A maintainer will audit it before promoting it from draft.

---

🤖 Generated with Claude Code

https://claude.ai/code/session_01BUtVm74AvDtgfCzdhVJX5f

---

Generated by Claude Code

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
blas/ext/base/ndarray/scusome	$\\color{green}129/129$ $\\color{green}+100.00\\%$	$\\color{green}3/3$ $\\color{green}+100.00\\%$	$\\color{green}1/1$ $\\color{green}+100.00\\%$	$\\color{green}129/129$ $\\color{green}+100.00\\%$

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