chore: rename little_endian_array.js example to plural in four blas/base/wasm packages

[Planeshifter]

Description

Renames examples/little_endian_array.js to examples/little_endian_arrays.js in four blas/base/wasm packages — dcopy, dswap, scopy, sswap — to align with the universal convention in the namespace. No content changes; rename only.

Namespace summary

• Target: @stdlib/blas/base/wasm
• Members: 33 (none autogenerated; all included in the vote).
• Features extracted: full file tree, directory layout, package.json shape (top-level keys, scripts, stdlib, keywords, engines, main, types, browser), manifest.json shape, README.md ##/### section list and order, file naming under test/, benchmark/, examples/, docs/, scripts/, src/, lib/, plus a fast cross-package scan for error-construction patterns in lib/.
• Features with a clear majority (≥75%): every feature except the one fixed here. manifest.json shape is identical across all 33 packages (confs, fields, options). All 33 packages have identical README structure (## Usage / ### Module / ## Notes / ## Examples). All 33 use format() from @stdlib/string/format for the single throw new TypeError(...) site in lib/module.js. All 33 share identical package.json top-level key sets and identical engines keys. The lone outlier is the examples/little_endian_arrays.js filename — present in 29/33 (88%) packages.
• Features without a clear majority (excluded): none material. The package.json keywords array necessarily contains a per-routine token (e.g., "dcopy"); that is the package identifier, not drift.

blas/base/wasm/dcopy, dswap, scopy, sswap

These four packages alone ship examples/little_endian_array.js (singular) where every other sibling — including all 13 single-vector routines (dasum, dnrm2, idamax, sasum, snrm2, isamax, dscal, sscal, cscal, zscal, dznrm2, scasum, scnrm2) — ships examples/little_endian_arrays.js (plural). The convention is arity-independent; the singular name is an early-package legacy. The file content in all four outliers creates two Float64ArrayLE views (x and y), so the plural form is also the semantically accurate name. Each file is renamed in place with no content edits.

Validation

Checked:

• Structural feature extraction across all 33 members; no autogenerated packages to exclude.
• Cross-package error-construction scan: every lib/ directory contains exactly one throw new TypeError( format( ... ) ) site (in module.js) and no template-literal, concatenation, or plain-string throws — so error normalization had nothing to flag.
• Three-agent drift validation on the surviving candidate (opus semantic-review, opus cross-reference, sonnet structural-review). All three returned confirmed-drift for all four outliers.
• Cross-reference sweep across lib/node_modules/@stdlib/ for any reference to the singular filename little_endian_array.js: zero hits. No test/, docs/repl.txt, docs/types/*, package.json, README.md, or examples/index.js references the renamed file.
• Pre-validation open-PR collision check via GitHub MCP: no open PRs touch blas/base/wasm/{dcopy,dswap,scopy,sswap}. The 10 open blas/*/wasm PRs all add new packages under blas/ext/base/wasm/.
• Cross-run dedup against PRs merged in the last 14 days: feat: add TypeScript declarations for blas/base/igamax #12420 (drift on blas/base, not wasm), docs: fix TSDoc errors in blas declarations #12529 (TSDoc fixes in blas declarations — does not touch examples/), chore: propagate blas/* JSDoc and cscal header fixes to siblings #12318 (JSDoc descriptor propagation — does not touch examples/). No collision.

Deliberately excluded:

• keywords per-package tokens — every package legitimately has its own routine name in keywords; this is identity, not drift.
• Semantic-feature extraction via per-package agents — the structural pre-pass already showed (a) identical README structure across all 33, (b) identical lib/ file layout (binary.js, binary.browser.js, index.js, main.js, module.js, routine.js), and (c) 100% format()-conformance, so the per-package agent sweep would yield no signal at the cost of 33 model calls.

Related Issues

None.

Questions

No.

Other

Generated by an automated cross-package drift-detection run (random-pick namespace selection; full per-feature distribution lives in a local report). The diff is mechanical: four file renames, zero content changes, no observable behavior change.

Checklist

• 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 authored by Claude Code as part of an automated cross-package drift-detection routine over a random-pick stdlib namespace. The drift was identified by structural feature extraction across @stdlib/blas/base/wasm/; the proposed rename was validated by three parallel review subagents (opus semantic-review, opus cross-reference, sonnet structural-review), all of which returned confirmed-drift for all four outlier packages.

---

@stdlib-js/reviewers

---

Generated by Claude Code

[stdlib-bot]

Coverage Report

No coverage information available.