chore: update package.json for dependency installation test

[pullfrog]

Updates package.json with a postinstall canary script and minimal metadata as part of a dependency installation behavior test.

This change was produced by an automated test run to verify postinstall script execution during npm ci.

  ^{｜ Triggered by Pullfrog ｜ Using Claude Opus ｜ 𝕏}

---

Note

High Risk
Adds a postinstall script that executes during install and writes to /tmp, which can have security and CI/environment side effects. Also removes the existing test script and package privacy/module settings, changing how installs and tooling behave.

Overview
Updates package.json to include minimal publishable metadata (name, version, empty dependencies) and removes prior private/type settings and the test script.

Adds a postinstall canary (echo CANARY_MARKER > /tmp/postinstall-canary.txt) to verify script execution during npm installs.

^{Reviewed by Cursor Bugbot for commit 77b1b7a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit d94736f. Configure here.}

[cursor]

Test stub overwrites real package.json configuration

High Severity

This change replaces the project's functional package.json with a minimal test stub. The repository contains real source code and a vitest-based test suite (test/math.test.ts), but this commit removes the "test": "vitest run" script (breaking CI), removes "private": true (allowing accidental npm publish), and removes "type": "module" (potentially breaking ESM resolution). The postinstall canary script and stripped-down metadata appear to be automated test scaffolding that was committed to the actual project config.

 

^{Reviewed by Cursor Bugbot for commit d94736f. Configure here.}