Fix invalid platform restrictions in package-lock.json and make benchmark setup non-blocking

[Just-Bamford]

Description

Problem

package-lock.json contains incorrect os restrictions for three pure JavaScript dependencies:

• pretty-format@29.7.0 → ["aix"]
• resolve.exports@2.0.3 → ["linux"]
• semver@6.3.1 → ["linux"]

These restrictions cause npm install and npm ci to fail on unsupported platforms and also break the benchmark workflow when it checks out main and installs dependencies.

Additionally, .github/workflows/benchmarks.yml only provides a fallback for npm run bench, while a failed npm ci causes the benchmark job to fail before the fallback is reached.

Solution

Regenerate package-lock.json from the current package manifest to remove the incorrect platform metadata.

Update the benchmark workflow so failures while installing the main baseline are handled as non-blocking, consistent with the workflow's manual comparison purpose.

Acceptance Criteria

• package-lock.json no longer contains incorrect os restrictions.
• npm ci succeeds on Linux, macOS, and Windows.
• The benchmark workflow handles a failed baseline install without failing the PR job.
• Benchmark output clearly indicates when a baseline is unavailable.
• No package versions are changed unless required by lockfile regeneration.

Note for Contributors

Regenerate the lockfile using the repository's supported Node.js and npm versions. Do not manually edit integrity hashes or dependency metadata.

[comzzy-comzzy]

Hello Maintainer,

I'm a JavaScript developer with experience maintaining npm-based projects and GitHub Actions workflows.

I understand the issue is to regenerate the lockfile to remove the invalid platform metadata without introducing unnecessary dependency changes, and to make the benchmark workflow resilient when the baseline install fails. I'll regenerate "package-lock.json" using the project's supported Node.js/npm versions, update the workflow to treat baseline installation failures as non-blocking, and verify that benchmark output clearly reports when a baseline is unavailable.

[arandomogg]

I would love to resolve this issue please assign it to me.

[Alimzy]

Hi! I'd like to work on this issue.
I'm a software engineer with hands-on experience in testing, debugging, and building reliable features across the stack. I'm confident I can take this on and deliver a solid, well-tested solution that follows the project's existing conventions.
I'll make sure to cover the core functionality as well as relevant edge cases to keep things reliable and regression-resistant.
Let me know if I can get started, and I'll provide updates as I progress.

[grantfox-oss]

🦊 GrantFox — @arandomogg has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #46)
2. Your PR will be reviewed by the AnonVote maintainers

Good luck! Track your progress on GrantFox.