chore: update package.json for canary test

[pullfrog]

This PR captures the package.json change made during a dependency installation canary test. The file was modified as part of testing postinstall script behavior.

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

---

Note

Medium Risk
Adds a postinstall script that executes on install and writes to the filesystem, which can affect CI/dev environments despite the small diff.

Overview
Updates package.json by renaming the package, adding a version, and removing private/type metadata.

Replaces the test script with a postinstall canary that writes CANARY_MARKER to /tmp/postinstall-canary.txt, and adds an empty dependencies section.

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

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

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

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

[cursor]

Test artifact postinstall script committed to repository

High Severity

A postinstall script that writes CANARY_MARKER to /tmp/postinstall-canary.txt is being committed. This will execute on every npm install for all contributors, writing to the filesystem as a side effect. This is a canary-test artifact that doesn't belong in the committed package.json. It also replaces the "test": "vitest run" script, so npm test no longer works despite test files (test/math.test.ts using vitest) still existing in the repo.

 

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

[cursor]

Removal of private: true risks accidental publication

Medium Severity

The "private": true field was removed as part of the canary test changes. This fixture/test repository (per the README) is not intended for npm publication, and without private: true, an accidental npm publish would succeed. The "type": "module" field was also removed, which could affect module resolution for the existing TypeScript source files that use ES module syntax.

 

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