chore: add structured package data for `math/base/special/csignum`

[MeKaustubh07]

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: na task: lint_package_json status: passed task: lint_repl_help status: na task: lint_javascript_src status: na task: lint_javascript_cli status: na task: lint_javascript_examples status: na task: lint_javascript_tests status: na 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: na task: lint_license_headers status: passed

Resolves a part of #7924

Description

What is the purpose of this pull request?

This pull request has the following related issues:

adds structured package data for math/base/special/csignum

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

Resolves a part of [RFC]: add structured package data for unary functions in math/base/special (tracking issue) #7924

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.

• [x] 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]

Hello! Thank you for your contribution to stdlib.

We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:

1. Please read our contributing guidelines.

2. Update your pull request description to include this checked box:

   - [x] Read, understood, and followed the [contributing guidelines](https://github.com/stdlib-js/stdlib/blob/develop/CONTRIBUTING.md)

This acknowledgment confirms that you've read the guidelines, which include:

• The developer's certificate of origin
• Your agreement to license your contributions under the project's terms

We can't review or accept contributions without this acknowledgment.

Thank you for your understanding and cooperation. We look forward to reviewing your contribution!

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
math/base/special/csignum	$\color{green}229/229$ $color{green}+100.00%$	$\color{green}7/7$ $color{green}+100.00%$	$\color{green}2/2$ $color{green}+100.00%$	$\color{green}229/229$ $color{green}+100.00%$

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