1.0.11 — Packaging metadata + prerelease publish hardening

Main story

This release focuses on making publishing and dependency management more reliable and repeatable. It hardens prerelease publish validation, updates package/dependency metadata, and begins tracking the npm lockfile to keep installs deterministic.

Changes

Publish & release process reliability

• Hardened prerelease publish prechecks so prerelease validation and policy checks behave consistently.
• Added publishConfig.tag: dev in package.json to ensure prerelease publishes go to the expected npm dist-tag (helps avoid accidental publication to latest and aligns automation with prerelease workflows).
• Committed package-lock.json (large addition) to make installs reproducible across CI and developer machines and to support lockfile-based checks.

Note: the lockfile currently contains a 1.0.11-dev.0 version string internally, reflecting how it was generated during prerelease work. The release version for this build is 1.0.11 (as in package.json).

Dependency & metadata updates

• Updated package.json metadata and bumped dependency/devDependency versions (notably tooling like TypeScript, ESLint, Vite, Vitest, and Node types), aligning the project with newer toolchain releases.

Repo hygiene

• Minor .gitignore cleanup (1-line change).

Impact

For users (consumers of the package)

• No functional runtime behavior changes were introduced in this range; this release is primarily packaging and tooling related.
• Dependency updates may change your transitive dependency tree slightly (via updated resolutions), but the public API/behavior is not targeted here.

For developers (contributors/maintainers)

• More predictable installs due to the committed lockfile.
• More robust prerelease publishing and automation due to explicit npm tagging and stricter prechecks.

Breaking changes

• None identified from main to HEAD in this release.