fix: publish built-in nodes package

[Aymericr]

Summary

• add nodes as an explicit release target
• include @pascal-app/nodes in coordinated releases and dependency version syncing
• publish and tag the package alongside the other public editor packages

Why

The built-in measurement tools merged in #505 depend on @pascal-app/nodes, but the package was absent from the release workflow, including the all path. Without this, npm consumers cannot receive the measurement implementation.

Validation

• release workflow parses as YAML
• package manifests parse as JSON
• git diff --check
• npm pack --dry-run --json --ignore-scripts for @pascal-app/nodes@0.1.0 (1,726 files, 1.08 MB)

---

Note

Low Risk
CI/release configuration only; no runtime app logic, with publish behavior mirroring existing packages.

Overview
Wires @pascal-app/nodes into the manual release pipeline so npm consumers can get the built-in node package (e.g. measurement tools from #505).

The release.yml workflow now treats nodes like the other public packages: it appears as a package choice, joins version bump / peer & dev dependency sync loops, gets a Build & publish nodes step (bun run build + npm publish, with dry-run support), and is included in release commit messages and git tags via NODES_VERSION.

Root package.json adds release:nodes to trigger gh workflow run release.yml -f package=nodes -f bump=patch.

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