feat: add read-only interactions and fix calendar lifecycle

[thedhanawada]

Summary

Two separate commits preserve the distinction between fixes and the new capability:

• Lifecycle/declaration fix: destroy the owned Core Calendar, make the public API safe before initialization and after destroy, and correct generated public types
• Read-only feature: reflected readOnly property / readonly boolean attribute disables built-in user mutations while preserving navigation, selection and host data APIs

Dynamic toggles close forms and cancel gestures. Drag controllers and trailing-click guards now clean up across rerenders and isolated calendar instances. Read-only is explicitly a UI feature, not an authorization boundary.

Validation

• npm test: strict generated consumer declarations and 182 tests across 15 suites pass
• Vite build, ESLint, Prettier and diff checks pass (12 existing lint warnings)
• Independent code review complete
• Tested against the actual published @forcecalendar/core 2.5.4, with the development dependency/lockfile updated
• All-four packed integration passes strict Bundler and NodeNext checking; real React/Vue snapshots, CRUD, navigation, SSR and teardown checks pass
• Salesforce local LWC integration verified against the read-only bundle; real-org validation is still pending authentication

The new public capability intentionally requires a minor release. The existing master workflow will select the version; no package version has been manually bumped.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
force-calendar-interface	Ready	Preview	Oct 2, 2026 6:21am UTC

[thedhanawada]

Added a separate compatible lockfile-only cleanup for baseline-browser-mapping, browserslist and brace-expansion advisories. A clean install, strict declaration checks, all 182 tests, production build, lint and formatting pass; npm audit now reports zero vulnerabilities. No direct dependency ranges or runtime code changed in this cleanup.