zara-calendar: reject provider events with invalid temporal order #61

New issue

Closed

opened 2026-09-08 02:02:53 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-08 02:02:53 +00:00

Owner

Problem

CalendarDomain._event() verifies that provider event start/end timestamps are timezone-aware but does not verify end > start. A malformed backend event can therefore be returned by search/get and used as trusted calendar state even when its interval is zero or backwards.

Required behavior

provider event start/end must be timezone-aware and end > start
zero-length and backwards provider events fail structurally as CalendarError
valid event normalization remains unchanged
deterministic regressions and full registry/install/Nix gate

No Zara Core changes.

## Problem `CalendarDomain._event()` verifies that provider event start/end timestamps are timezone-aware but does not verify `end > start`. A malformed backend event can therefore be returned by search/get and used as trusted calendar state even when its interval is zero or backwards. ## Required behavior - provider event start/end must be timezone-aware and `end > start` - zero-length and backwards provider events fail structurally as `CalendarError` - valid event normalization remains unchanged - deterministic regressions and full registry/install/Nix gate No Zara Core changes.

nsaspy closed this issue

2026-09-08 02:02:53 +00:00

nsaspy referenced this issue

2026-09-08 02:20:14 +00:00

Add typed diagnostic zara-sysadmin service #502