chore: clean-up

[Planeshifter]

Description

What is the purpose of this pull request?

This pull request contains follow-up fixes for commits merged to develop between 2026-07-07 14:20 PDT (b5b7b4c) and 2026-07-08 01:31 PDT (bb93e56). Findings were surfaced by an automated multi-agent review of the window's union diff, then filtered to keep only high-signal, unambiguous defects (typos, broken doc identifiers, style-guide violations, and a demonstrable declarations gap).

Fixes, grouped by package:

• Fix searchElement param docs mislabeled as "scalar constant"/"search Element" across blas/ext/base/dfill-equal (lib/dfill_equal.js, lib/dfill_equal.native.js, lib/ndarray.js, lib/ndarray.native.js, src/main.c, README.md), normalizing to "search element" to match docs/types/index.d.ts; copy-paste leftover from ad0783b.
• In ml/base/sgd-classification/loss-functions (3148fe6), the C API docs in README.md reference STDLIB_ML_SGD_CLASSIFICATION_LOSS_FUNCTIONS/STDLIB_ML_SGD_CLASSIFICATION_HINGE, but the header declares STDLIB_ML_BASE_SGD_CLASSIFICATION_LOSS_FUNCTIONS/STDLIB_ML_BASE_SGD_CLASSIFICATION_HINGE (missing _BASE_), so the documented usage example doesn't compile; fixed to match include/stdlib/ml/base/sgd-classification/loss_functions.h. Also fixed a stray filename typo (loss functions.h → loss_functions.h) in lib/enum.js and spacing (obj[ o[i] ] → obj[ o[ i ] ]) in test/test.js to match house style.
• Backfill cxmy, zxmy, and dfillEqual imports and interface members in lib/node_modules/@stdlib/blas/ext/base/docs/types/index.d.ts, mirroring the sibling cxpy/dfill/zxpy blocks; these three landed on the runtime namespace via 5402a8a but were never added to the declarations file, which 044b270 last touched for other packages.

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. The multi-agent review comprised: (1) two style-guide compliance passes (one over the new BLAS/ML packages, one over the docs / lint / refactor sweeps), each comparing every touched file against an established sibling of similar shape; (2) two independent bug hunts over the diff-only surface. Findings surviving cross-agent verification and diff re-check were kept; the rest were dropped as either subjective or out-of-scope.

Deliberately excluded from this PR:

• Adding .0 decimal suffixes to the y0 REPL output in blas/ext/base/{cxmy,zxmy}/docs/repl.txt — initially applied for consistency with sibling cxpy/zxpy docs, then reverted because the resulting line exceeds the 80-character REPL line-length lint rule (the larger absolute values in the cxmy/zxmy example don't fit once suffixed). The original integer formatting was a deliberate choice by the package authors to satisfy the same rule.
• An isnan-guard ordering inconsistency across the stats/base/dists refactor (b5b7b4c) — both orderings are functionally equivalent and the JS style guide does not prescribe one. Left to a follow-up if maintainers want to normalize.
• Extending the 09d16f18 "returns → e.g., returns" wording fix into regexp/basename/README.md — the README example is guarded by an explicit "Assuming a POSIX platform..." comment and the original lint sweep did not touch READMEs.

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

This PR was assembled by an automated Claude Code review routine. The routine enumerated commits merged to develop in the preceding 24 hours, fanned out to independent reviewer subagents (two for stdlib style-guide compliance, two for bug hunting), merged and filtered the findings to a high-signal set, applied the fixes grouped by package, and drafted this body. A maintainer should audit each commit before promoting from draft.

---

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
blas/ext/base/dfill-equal	$\\color{green}363/363$ $\\color{green}+0.00\\%$	$\\color{green}18/18$ $\\color{green}+0.00\\%$	$\\color{green}4/4$ $\\color{green}+0.00\\%$	$\\color{green}363/363$ $\\color{green}+0.00\\%$
ml/base/sgd-classification/loss-functions	$\\color{green}163/163$ $\\color{green}+0.00\\%$	$\\color{green}5/5$ $\\color{green}+0.00\\%$	$\\color{green}2/2$ $\\color{green}+0.00\\%$	$\\color{green}163/163$ $\\color{green}+0.00\\%$

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

[kgryte]

@Planeshifter These sorts of changes should not be considered "fixes". We have automated workflows for this. This sort of proposed change just adds noise. In short, tell your bot to stay in its lane.