feat: add implementation of stats/base/dists/dweibull/mode

[shubham220420]

---

type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes. report:

• task: lint_filenames status: passed
• task: lint_editorconfig status: passed
• task: lint_markdown status: passed
• task: lint_package_json status: passed
• task: lint_repl_help status: passed
• task: lint_javascript_src status: passed
• task: lint_javascript_cli status: na
• task: lint_javascript_examples status: passed
• task: lint_javascript_tests status: passed
• task: lint_javascript_benchmarks status: passed
• task: lint_python status: passed
• task: lint_r status: na
• task: lint_c_src status: missing_dependencies
• task: lint_c_examples status: missing_dependencies
• task: lint_c_benchmarks status: missing_dependencies
• task: lint_c_tests_fixtures status: na
• task: lint_shell status: na
• task: lint_typescript_declarations status: passed
• task: lint_typescript_tests status: passed
• task: lint_license_headers status: passed ---

Ref: #173.

Description

What is the purpose of this pull request?

This pull request:

• This PR adds the implementation of stats/base/dists/dweibull/mode

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• RFC: add the double Weibull distribution #173

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.

No.

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

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

{{TODO: add disclosure if applicable}}

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
stats/base/dists/dweibull/mode	$\color{green}178/178$ $\color{green}+100.00%$	$\color{green}8/8$ $\color{green}+100.00%$	$\color{green}2/2$ $\color{green}+100.00%$	$\color{green}178/178$ $\color{green}+100.00%$

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

[rautelaKamal]

Hi @shubham220420
Looking at your PR - a couple of things that maintainers have flagged on similar C-port PRs that will likely come up in review:

1. Test fixtures: use a single data.json
Instead of separate fixture files for different parameter ranges, the convention is to consolidate all test cases into one test/fixtures/data.json file. You can see a reference implementation here:
https://github.com/stdlib-js/stdlib/blob/develop/lib/node_modules/%40stdlib/stats/base/dists/wald/pdf/test/test.pdf.js#L197

2. test.native.js: use isAlmostSameValue
Instead of manual delta/tol comparisons like:

delta = abs( y - expected[ i ] );
tol = 180.0 * EPS * abs( expected[ i ] );
t.ok( delta <= tol, ... );

Use the isAlmostSameValue utility which handles this cleanly. Same reference link above shows the pattern.

[kgryte]

@rautelaKamal Please do not create automated review comments on PRs. I have noticed that you have posted a few of these comments to other PRs, and several of them contain inaccurate guidance.

Re: (1) using a single data.json. This is incorrect. Different value ranges should have separate fixtures files. There are numerous examples of this throughout the codebase.