bench: add missing function documentation and ensure consistency with other benchmarks

[Planeshifter]

Follow-up fixes for commits merged to develop between 2026-06-30 14:47 PDT (14c51b7f3) and 2026-07-01 01:30 CDT (aebd92a2a).

Description

Small style follow-ups against the eight commits merged to develop in the last 24 hours. Only stats/base/dists/anglit/quantile needed changes; the other three new distribution packages (poisson/entropy C addition, lognormal/logpdf C addition, log-logistic/pdf) and the four bot/namespace commits came in clean.

Fixes in this PR:

• Static helper functions in the anglit quantile benchmark lacked the /** ... */ doc comments every sibling benchmark.c uses. Added matching doc comments to print_version, print_summary, print_results, tic, random_uniform, benchmark, and main. (aebd92a2a, lib/node_modules/@stdlib/stats/base/dists/anglit/quantile/benchmark/c/benchmark.c)
• isnan( y ) in lib/node_modules/@stdlib/stats/base/dists/anglit/quantile/benchmark/c/benchmark.c broke with the tree's established y != y self-comparison idiom for NaN checks, dragging in an unneeded <math.h>. Switched both call sites to y != y and dropped the include. (aebd92a2a, lib/node_modules/@stdlib/stats/base/dists/anglit/quantile/benchmark/c/benchmark.c)

Related Issues

None.

Questions

No.

Other

Validation. Reviewed all eight commits merged to develop in the window with four parallel reviewers (two style, two bug-hunt). Checked for stdlib code style compliance, copy-paste artefacts, math/logic bugs, boundary handling, contract mismatches, wrong constants, and manifest/addon wiring. Findings that were not independently re-verifiable against a sibling reference package, or that would require touching code outside the window's diff, were deliberately excluded. The three sibling C benchmarks added in the same window (poisson/entropy, lognormal/logpdf, log-logistic/pdf) served as the reference for the anglit benchmark fix.

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 as part of a scheduled routine that audits recent commits to develop. The reviewer agents surfaced the two style deviations above; the fixes mirror the doc-comment scaffold and NaN-check idiom already used by the three sibling C benchmarks added in the same window.

---

@stdlib-js/reviewers

---

Generated by Claude Code

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
stats/base/dists/anglit/quantile	$\\color{green}297/297$ $\\color{green}+100.00\\%$	$\\color{green}27/27$ $\\color{green}+100.00\\%$	$\\color{green}4/4$ $\\color{green}+100.00\\%$	$\\color{green}297/297$ $\\color{green}+100.00\\%$

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