docs: propagate fixes from develop across stats, blas, and plot siblings

[Planeshifter]

Description

Propagating fixes merged to develop between f8a43f95 (2026-05-24 01:23 -0700) and 40dad68e (2026-05-24 02:54 -0700) to sibling packages with the same underlying defect.

Pattern: propagate parameter-name fixes to umbrella namespace declarations

Commit 47f803ef corrected a stale scale parameter reference (s → c) in the entropy JSDoc and per-function TypeScript declaration for @stdlib/stats/base/dists/levy/entropy. The umbrella namespace docs/types/index.d.ts carries a duplicate of that description and requires the same correction at line 73.

• 47f803ef (docs: fix scale parameter reference in @stdlib/stats/base/dists/levy/entropy)
  • @stdlib/stats/base/dists/levy (umbrella docs/types/index.d.ts)

Pattern: propagate missing-verb fix in BLAS rank-1 update test descriptions

Test description strings in gger and sger read 'the function the rank 1 operation ...', omitting performs — the same defect fixed in dger. Corrects 16 sites across 6 test files.

• 7800c9a7 (test: fix grammar of test descriptions in blas/base/dger)
  • @stdlib/blas/base/gger
  • @stdlib/blas/base/sger

Pattern: replace new Array allocations with zeros in SVG plot component onRender re-emit callbacks

Nine sibling SVG plot components share the same onRender re-emit pattern as plot/components/svg/defs, each allocating an argument array via new Array( arguments.length+1 ). Replace each allocation with zeros( arguments.length+1, 'generic' ) and add the corresponding @stdlib/array/zeros require.

• 40dad68e (chore: fix JavaScript lint errors)
  • @stdlib/plot/components/svg/annotations
  • @stdlib/plot/components/svg/axis
  • @stdlib/plot/components/svg/background
  • @stdlib/plot/components/svg/canvas
  • @stdlib/plot/components/svg/graph
  • @stdlib/plot/components/svg/path
  • @stdlib/plot/components/svg/rug
  • @stdlib/plot/components/svg/symbols
  • @stdlib/plot/components/svg/title

Related Issues

None.

Questions

No.

Other

Validation

Reviewed all 12 commits merged to develop in the 24-hour window. Three source patterns advanced to the patch stage; per-pattern search scope and validation procedure:

• Search scope: scoped to the source commit's namespace first (stats/base/dists/levy/* for the scale parameter fix; blas/base/* for the test-description grammar fix; plot/components/svg/* for the new Array allocation pattern). Originating packages already fixed by the source commits were excluded.
• Independent validation: two opus validation agents independently reviewed every candidate site by reading each file in full; both returned confirmed for all 26 sites.
• An adaptation pass confirmed each @stdlib/array/zeros require insertion point for the nine SVG plot components (placement determined per-file: between inherit and instanceOf where present, otherwise after the last @stdlib/utils/* or @stdlib/assert/* require and before the first local require, mirroring the source commit's placement convention).
• A sonnet style-consistency pass confirmed JSDoc indentation, single-quoted string form, and require-block ordering match the source-commit canonical form.

Deliberately excluded:

• 91a6a85e (multi-offset README wording): the source commit was comprehensive — no remaining multi-offset README sites carry the old singular phrasing.
• f345dd63 (incorrect logEach argument in cgemv example): the defect (logging x where y is the output vector) has no grep-able textual signature distinguishing wrong from correct call sites; would require per-site semantic interpretation.
• c17ecc0d (separate @example tags in time/day-of-quarter): no remaining time/* packages exhibit the malformed-@example continuation pattern.
• a2fcfdb2 (ndarray-instance doctest improvement): single-package documentation improvement without a generalizable propagation signature.
• ac45b111 (refactor: main require alias in stats/base/dists/frechet): refactor commit, not a defect fix; out of scope for this routine.

Checklist

• Read, understood, and followed the contributing guidelines.

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 on behalf of @Planeshifter as an automated propagation of fixes merged to develop over the prior 24 hours. Candidate source commits were filtered for generalizable patterns, sibling sites located via grep-able pattern signatures, and each proposed patch independently validated by parallel reviewer agents (two opus validation passes plus a sonnet style-consistency pass) before commits were applied in the primary worktree. A human will audit and promote the PR out of draft.

---

@stdlib-js/reviewers

---

Generated by Claude Code

[kgryte]

As the CI failure is not due to changes introduced in this PR, I'll go ahead and merge.