chore: release 2.0.0

[David Chicaiza (david0723)]

Version bump to 2.0.0.

Includes #65: validateForman / validateFormanWithDomains gain an opt-in fillDefaults option ('requiredOnly' | 'always') that fills declared defaults for omitted fields during validation, mirroring BlueprintValidator's useDefaults modes, and return the filled values as normalizedValues plus an audit trail in appliedDefaults.

Why a major. Nothing was removed or renamed and the return type only narrows, so valid/errors readers are unaffected. But both result fields are now present on every result, with or without the option, so anyone deep-comparing the whole result object or forwarding it into a fixed-shape response will see two new keys. With the option off, validation outcomes (valid, errors, warnings) are byte-identical to 1.19.0. The README carries the release note and the migration line.

Once merged, creating the v2.0.0 GitHub release triggers the npm + JSR publish workflows.

[Copilot]

Pull request overview

Bumps the library’s published version to 2.0.0 in preparation for the release that includes the fillDefaults validation feature and the always-present normalizedValues/appliedDefaults result fields.

Changes:

• Update package.json version from 1.19.0 to 2.0.0.
• Update package-lock.json root/package entry versions to 2.0.0.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File	Description
package.json	Bumps package version to 2.0.0.
package-lock.json	Syncs lockfile’s recorded package versions to 2.0.0.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Jakub Stok (jakubstokcelonis)]

Version bump only (package.json + package-lock.json), CI green on build and test 18/20/22.

Checked the 2.0.0 call against what it releases (#65): the fill is gated behind context.fillDefaults != null in validateFormanValue, so with the option off valid/errors/warnings are unchanged. The break is purely shape — normalizedValues and appliedDefaults are now unconditional on the result, which this repo's own suite had to widen assertions for and the MCP Server consumer needed a response guard for. Major is the right call.

Release plumbing also checks out: both deploy workflows fire on release: created, and build:version derives jsr.json from package.json, so the placeholder 0.0.0 resolves to 2.0.0 on publish.