feat: add tools/c-impl-status to track all C dependecy implementation status of a package

[DhruvArvindSingh]

Resolves None.

Description

What is the purpose of this pull request?

This pull request:

• This tool sees all the dependency of a package and sees weather its C implementation is present or not.

• If the dependency is of tool folder or any other util package then ignores weather the C implementation exist.

• If the package is not from any tools/utils folder then it shows that the package requires its C implementation first.

• Example 1:
  Input:

node lib/node_modules/@stdlib/_tools/pkgs/c-impl-status/bin/cli @stdlib/math/base/special/betainc

Output:

Package: @stdlib/math/base/special/betainc
Package C status: ✗ Needs src/ directory + C implementation

Dependencies summary:
  Total: 1
  Has C: 0
  Needs C: 1
  JS-only (tools/constants): 0
  External: 0

⚠️  NOT READY - 1 blocking package(s) need C implementation.

Dependencies:
  ✗ @stdlib/math/base/special/kernel-betainc (needs src/ + C)

Blocking packages (implement C for these first):
  ✗ @stdlib/math/base/special/kernel-betainc (needs src/ + C)

Legend:
  ✓  Has C implementation
  ✗  Needs C implementation (missing src/ or C files)
  -  JS-only by design (tools/constants)
  ?  External package (not in stdlib)

• Example 2:
  Input:

node lib/node_modules/@stdlib/_tools/pkgs/c-impl-status/bin/cli @stdlib/math/base/special/polygamma

Output:

Package: @stdlib/math/base/special/polygamma
Package C status: ✗ Needs src/ directory + C implementation

Dependencies summary:
  Total: 29
  Has C: 18
  Needs C: 0
  JS-only (tools/constants): 10
  External: 1

✅ READY for C implementation - all dependencies have C. Add src/ directory first.

Dependencies:
  - @stdlib/array/base/zeros (JS-only (tools/constants))
  - @stdlib/constants/float64/eps (JS-only (tools/constants))
  - @stdlib/constants/float64/ln-pi (JS-only (tools/constants))
  - @stdlib/constants/float64/ln-two (JS-only (tools/constants))
  - @stdlib/constants/float64/max (JS-only (tools/constants))
  - @stdlib/constants/float64/max-ln (JS-only (tools/constants))
  - @stdlib/constants/float64/ninf (JS-only (tools/constants))
  - @stdlib/constants/float64/pi (JS-only (tools/constants))
  - @stdlib/constants/float64/pinf (JS-only (tools/constants))
  ✓ @stdlib/math/base/assert/is-nonnegative-integer (2 C files)
  ✓ @stdlib/math/base/special/abs (2 C files)
  ✓ @stdlib/math/base/special/bernoulli (2 C files)
  ✓ @stdlib/math/base/special/cospi (2 C files)
  ✓ @stdlib/math/base/special/digamma (2 C files)
  ✓ @stdlib/math/base/special/exp (2 C files)
  ✓ @stdlib/math/base/special/factorial (2 C files)
  ✓ @stdlib/math/base/special/floor (2 C files)
  ✓ @stdlib/math/base/special/gammaln (2 C files)
  ✓ @stdlib/math/base/special/ldexp (2 C files)
  ✓ @stdlib/math/base/special/ln (2 C files)
  ✓ @stdlib/math/base/special/min (2 C files)
  ✓ @stdlib/math/base/special/pow (2 C files)
  ✓ @stdlib/math/base/special/riemann-zeta (2 C files)
  ✓ @stdlib/math/base/special/signum (2 C files)
  ✓ @stdlib/math/base/special/sinpi (2 C files)
  ✓ @stdlib/math/base/special/trigamma (2 C files)
  ✓ @stdlib/math/base/special/trunc (2 C files)
  - @stdlib/math/base/tools/evalpoly (JS-only (tools/constants))
  ? debug (external package)

Legend:
  ✓  Has C implementation
  ✗  Needs C implementation (missing src/ or C files)
  -  JS-only by design (tools/constants)
  ?  External package (not in stdlib)

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

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

{{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!

[DhruvArvindSingh]

@Planeshifter @kgryte ,The idea is that , we can create a different tool on top of this which can create a hierarchy tree representation of a package family so that we can identify and implement bottleneck packages first.