fix: add prepublishOnly guard to run tests before npm publish - #3

Problem

Currently bump and patch scripts execute npm publish directly without any pre-publish validation:

"bump": "npm version prerelease --preid=beta --workspaces=false && npm publish --tag beta",
"patch": "npm version patch --workspaces=false && npm publish --tag latest"

If tests happen to be failing at the time of publish, a broken package can still be released to npm. This is easy to miss especially when iterating quickly during beta.

Solution

Add a prepublishOnly lifecycle hook that runs bun test before every npm publish:

"prepublishOnly": "bun test"

prepublishOnly is an npm lifecycle script that runs automatically before npm publish and before npm pack. If tests fail, the publish is aborted — no manual step needed.

What changes

• packages/ol/package.json: Added "prepublishOnly": "bun test" to scripts

How it works

npm publish
  └─ prepublishOnly (bun test)
       ├─ tests pass → publish proceeds ✅
       └─ tests fail → publish aborted ❌

Both bump and patch scripts will now be guarded automatically since they both call npm publish internally.

Testing

Verified locally:

• npm publish --dry-run triggers prepublishOnly and runs bun test as expected
• If a test is intentionally broken, publish is correctly aborted

Summary by cubic

Add prepublishOnly to run bun test before every npm publish, so publishes abort if tests fail. This guards both bump and patch flows in packages/ol to prevent broken releases.

^{Written for commit c2bda75. Summary will update on new commits.}