docs: propagate recent fixes across stats/base/dists and lapack/base

[Planeshifter]

Description

Propagating fixes merged to develop between 2026-05-07 18:37 UTC and 2026-05-08 11:47 UTC to sibling packages.

docs: correct C API heading function name

Fixes a copy-paste error in the C API section heading of @stdlib/stats/base/dists/gumbel/logpdf, propagating the same correction made in ff7716f. The level-4 heading incorrectly named stdlib_base_dists_gumbel_logcdf rather than stdlib_base_dists_gumbel_logpdf; the surrounding #include, example call, and C signature were already correct. The defect originated from reuse of sibling-package documentation without updating the function name in the heading.

Source: ff7716f (docs: correct C API heading function name in stats/base/dists/exponential/logcdf)

Target packages:

• @stdlib/stats/base/dists/gumbel/logpdf

docs: improve doctests for complex number typed arrays

Propagates the pattern from ee5eced, which replaced per-element real/imag unwrap idioms on Complex typed array views with a direct > view print rendering the full array, to @stdlib/lapack/base/zlacpy. Both the {{alias}} and {{alias}}.ndarray doctests in docs/repl.txt were updated accordingly.

Source: ee5eced (docs: improve doctests for complex number typed arrays in blas/base/wasm)

Target packages:

• @stdlib/lapack/base/zlacpy

Related Issues

None.

Questions

No.

Other

Validation

Pattern search scope:

• Pattern A (C API heading): all lib/node_modules/@stdlib/stats/base/dists/*/*/README.md (423 files scanned).
• Pattern B (verbose Complex array doctest): all **/docs/repl.txt under lib/node_modules/@stdlib/, plus the alias-call sweep across complex/real/imag references.

Each candidate site passed two independent validation agents (defect confirmation by reading the full file), an adaptation pass (computing the exact <Complex128Array>[ ... ] rendering from the doctest setup), and a style-consistency pass (checked against an already-fixed sibling, blas/base/wasm/zcopy/docs/repl.txt).

Deliberately excluded:

• Sites where the view.get(i) / real / imag triplet documents per-element accessor behavior itself (e.g., array/complex64/docs/repl.txt, array/complex128/docs/repl.txt) — the unwrap is the feature being demonstrated.
• Scalar Complex64 / Complex128 return-value unwraps in complex/float{32,64}/base/{add,sub,mul,div,...}/docs/repl.txt — no array view, so the source pattern does not apply.
• Sites needing cross-package edits or new test fixtures; none surfaced in this run.

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 prepared by Claude Code as part of an automated fix-propagation routine. The agent enumerated candidate sites for each source-commit pattern, ran independent validation passes, and applied the validated patches; commits and the PR body were authored by the agent. A maintainer should review before promoting from draft.

---

@stdlib-js/reviewers

---

Generated by Claude Code

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
lapack/base/zlacpy	$\color{green}854/854$ $\color{green}+0.00%$	$\color{green}40/40$ $\color{green}+0.00%$	$\color{green}6/6$ $\color{green}+0.00%$	$\color{green}854/854$ $\color{green}+0.00%$
stats/base/dists/gumbel/logpdf	$\color{green}298/298$ $\color{green}+0.00%$	$\color{green}23/23$ $\color{green}+0.00%$	$\color{green}4/4$ $\color{green}+0.00%$	$\color{green}298/298$ $\color{green}+0.00%$

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

[kgryte]

LGTM after resolving the lint failure