feat: add constants/float16/sqrt-three

[Amansingh0807]

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: na
• task: lint_python status: na
• task: lint_r status: na
• task: lint_c_src status: na
• task: lint_c_examples status: na
• task: lint_c_benchmarks status: na
• 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 ---

Resolves none

Description

What is the purpose of this pull request?

This pull request:

• add constants/float64/sqrt-three

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• Resolves None

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.".

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
constants/float16/sqrt-three	$\color{green}51/51$ $\color{green}+0.00%$	$\color{green}1/1$ $\color{green}+0.00%$	$\color{green}0/0$ $\color{green}+0.00%$	$\color{green}51/51$ $\color{green}+0.00%$

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

[Amansingh0807]

Thanks for the review, @Neerajpathak07!
I have implemented both suggestions - removed the auto-populated content from the related section and the related-links area. Changes pushed!

Appreciate the clarification! 🙏

[Neerajpathak07]

Just a small advice do try and avoid force pushing commits reason being when contributors pull from your work it causes merge conflicts which are pretty tedious to resolve.
If an unwanted commit was added it is viable to close the pr and create a new one.

[Amansingh0807]

Thank you for the advice, @Neerajpathak07!
I completely understand - I will avoid force pushing to prevent merge conflicts. Will use revert or create a new PR if needed to undo commits.
Really appreciate you taking the time to guide me on best practices. I will keep this in mind going forward. 😊

[kgryte]

LGTM