chore: prepare 2.0.1 canary base version

[bntvllnt]

Summary

• Set only the package base version to 2.0.1 and document canary preparation under Unreleased.
• No dependency, preset, lockfile, or workflow changes. Existing ^2.0.0 documentation remains compatible.
• After a separately authorized merge, the existing push workflow publishes 2.0.1-canary. to canary. This PR does not merge, publish, tag, or create a stable release. Stable requires a separate manual workflow dispatch and a matching versioned changelog heading, which this PR does not add.

Verification

• Fresh root node_modules install: pnpm install --frozen-lockfile --config.minimumReleaseAgeStrict=true (passed; lockfile and workspace config unchanged, no exclusions).
• pnpm check: passed, 11 tests and 100% coverage; React/Vite and Next.js production builds passed.
• pnpm pack --dry-run and git diff --check passed.
• An initial fresh copy nested inside .git hit React TS2883 path inference failures; fresh install at the real repository root passed without code/config changes.

Known issue / scope

• Existing development-only handlebars 4.7.8 via @boundaries/elements 1.2.0 has a reported Dependabot security_update_not_possible result (run 34965679429); dependencies are unchanged and not in the published tarball.
• Newly published canary consumer installs remain subject to registry/package-manager minimum release age. No bypasses are introduced.
• Prep only: do not merge or publish without separate authorization.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.