Fix npm install by reverting version bump and removing npm upgrade step

[jfrench9]

Summary

This PR addresses a broken npm install issue caused by the publish workflow and an incorrect version bump. Two targeted changes are made to restore proper build and publish behavior:

1. Reverted package.json version from 0.2.41 back to 0.2.40 — the version was prematurely or incorrectly bumped, likely causing conflicts or failed installs for consumers of the package.
2. Removed the npm upgrade step from the GitHub Actions publish workflow (.github/workflows/publish.yml) — this step was modifying dependency versions during CI, which can introduce non-deterministic builds and was likely the root cause of the install failures.

Root Cause

The publish workflow included an npm upgrade step that mutated dependency versions at publish time, potentially causing version mismatches, lockfile inconsistencies, or pulling in breaking transitive dependencies. Combined with the premature version bump to 0.2.41, this resulted in a broken install experience for downstream consumers.

Changes

File	Change
package.json	Version reverted: 0.2.41 → 0.2.40
.github/workflows/publish.yml	Removed 6 lines comprising the npm upgrade step

Key Improvements

• Restores reliable npm install for all consumers of the package
• Deterministic CI builds — dependencies are no longer silently upgraded during the publish pipeline
• Prevents future regressions by eliminating the unsafe upgrade step from the workflow

Breaking Changes

None. This is a corrective fix that restores the previously working state. The version is reverted to 0.2.40, so no new public version is introduced.

Testing Notes for Reviewers

• Verify that npm install completes successfully in a clean environment after these changes
• Confirm the GitHub Actions publish workflow runs end-to-end without errors (trigger a dry run or monitor the next publish)
• Validate that the published package at version 0.2.40 installs correctly: npm install <package-name>@0.2.40
• Check that no unintended dependency changes snuck into package-lock.json (it should remain unchanged by this PR)

Browser Compatibility Considerations

No impact — these changes are limited to CI/CD configuration and package metadata. No application code, runtime behavior, or front-end assets are modified.

---

🤖 Generated with Claude Code

Branch Info:

• Source: bugfix/fix-npm-install
• Target: main
• Type: bugfix

Co-Authored-By: Claude noreply@anthropic.com