zara-timers: reject coercible numeric values in persisted state #63

New issue

Closed

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

nsaspy commented

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

Owner

Problem

TimerDomain._load() currently coerces persisted numeric fields with int() / float(). Corrupt or externally edited state can therefore turn booleans and numeric strings into trusted sequence/countdown data.

Required behavior

persisted sequence must be an exact non-negative integer, excluding booleans
persisted running/paused timer remaining must be an exact finite int/float, excluding booleans, within the normal timer duration bound
persisted reminder cadence must satisfy the same exact integer/range contract as newly-created reminders
malformed persisted numeric state fails closed as TimerError
deterministic restart regressions
full registry/install/Nix gate remains green

No Zara Core changes.

## Problem `TimerDomain._load()` currently coerces persisted numeric fields with `int()` / `float()`. Corrupt or externally edited state can therefore turn booleans and numeric strings into trusted sequence/countdown data. ## Required behavior - persisted `sequence` must be an exact non-negative integer, excluding booleans - persisted running/paused timer `remaining` must be an exact finite int/float, excluding booleans, within the normal timer duration bound - persisted reminder cadence must satisfy the same exact integer/range contract as newly-created reminders - malformed persisted numeric state fails closed as `TimerError` - deterministic restart regressions - full registry/install/Nix gate remains green No Zara Core changes.

nsaspy closed this issue

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

nsaspy referenced this issue

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

Add provider-neutral verified zara-calendar service #500