v2.12.1
Bug fixes
Cross-app intents: malformed due/previous_due on rescheduled and updated events
Timed tasks (those with a start time) were emitting due and previous_due as
timezone-naive strings, e.g. 2026-05-27T09:00:00. The @glance-apps/intents
schema requires either a full ISO 8601 datetime with offset or a plain YYYY-MM-DD
date. On the encrypted notify path this caused a MalformedEnvelopeError in the
receiving app; the plaintext path swallowed the error silently before writing.
Fixed by appending the local UTC offset (e.g. +05:00), preserving wall-clock time
rather than converting to UTC.
Cross-app intents: bare-date completed_at on completed events
completedAt is stored internally as YYYY-MM-DD. Because a date string is truthy,
the ISO datetime fallback in the notify emitter never fired, so completed_at was
sent as a bare date where a full datetime with offset is required. Normalized to ISO
at the emit boundary; stored task data is unchanged.
Activity log: MalformedEnvelopeError downgraded to warning
Schema validation failures after successful decryption (protocol mismatches between
app versions) are now logged with an amber warning badge rather than red, consistent
with how receiving apps in the GLANCE ecosystem treat this condition.