chore: normalize main field to ./lib in array/base and array/float16 package.json

[Planeshifter]

Description

What is the purpose of this pull request?

This pull request:

• Normalizes the main field in two @stdlib/array packages to the canonical "./lib" form used by 101 of the 103 packages in the namespace (98% conformance). Node's module resolution treats "./lib", "lib/index.js", and "./lib/index.js" identically — all three resolve to ./lib/index.js — so the change is purely metadata normalization with no behavioral impact.

@stdlib/array/base

main was "lib/index.js" (missing leading ./ and full path). Changed to "./lib". 98% namespace conformance.

@stdlib/array/float16

main was "./lib/index.js" (full path rather than directory). Changed to "./lib". 98% namespace conformance.

Related Issues

Does this pull request have any related issues?

This pull request has no related issues.

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.

Verified post-edit with require.resolve(): both packages still resolve to ./lib/index.js. No test, source file, or stdlib tooling compares the literal main value as a string — tools/.../create_namespace_types.js operates on the resolved absolute path from require.resolve(), which is unaffected.

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

This PR was produced by Claude Code running a namespace drift-detection routine: extract structural and semantic features from every package in a randomly selected @stdlib namespace, compute per-feature majority patterns at a 75% threshold, and propose corrections for outliers. Both deviations were independently verified by separate sonnet validation agents (structural-review and cross-reference) before any edits were made.

---

@stdlib-js/reviewers

---

Generated by Claude Code

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
array/base	$\color{red}39461/52356$ $\color{green}+75.37%$	$\color{red}588/592$ $\color{green}+99.32%$	$\color{red}2/533$ $\color{green}+0.38%$	$\color{red}39461/52356$ $\color{green}+75.37%$
array/float16	$\color{red}2660/2708$ $\color{green}+98.23%$	$\color{red}451/466$ $\color{green}+96.78%$	$\color{red}58/59$ $\color{green}+98.31%$	$\color{red}2660/2708$ $\color{green}+98.23%$

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