P1 — implement Android timer, alarm and dual-calendar capability adapters #200

New issue

Open

opened 2026-08-24 06:24:53 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-08-24 06:24:53 +00:00

(Migrated from github.com)

Parent: #194
Depends on: #159, #174, #198
Integrates with: #150, #152, #177

Goal

Provide typed public-API integrations for compatible Android clocks and both device/Zara calendars.

Required capabilities

set timer with optional label and show timers where supported;
set alarm and show alarms where supported;
device calendar query/create/edit/delete/show through supported Calendar APIs/intents;
principal-scoped Zara server calendar query/create/edit/delete/show;
semantic selection or clarification among device calendar, Zara calendar and configured default.

Prefer Android AlarmClock contracts and normal calendar providers so compatible Samsung/user-selected applications handle requests. Do not depend on undocumented Samsung Clock APIs.

Security and lifecycle

Define confirmation, permission, cancellation, idempotency/replay, provider mutation races and principal/device binding for side effects. Calendar data and labels follow private-text logging policy.

Tests

TDD supported/unsupported handlers, permission denial/revocation, malformed times/ranges, DST/timezone boundaries, ambiguous provider, duplicate/replayed actions, process restart and server disconnect.

Acceptance

Clock actions resolve through public handlers, standard device calendars interoperate, and Zara calendar remains server/principal owned without an Android-only authoritative database.

Parent: #194 Depends on: #159, #174, #198 Integrates with: #150, #152, #177 ## Goal Provide typed public-API integrations for compatible Android clocks and both device/Zara calendars. ## Required capabilities - set timer with optional label and show timers where supported; - set alarm and show alarms where supported; - device calendar query/create/edit/delete/show through supported Calendar APIs/intents; - principal-scoped Zara server calendar query/create/edit/delete/show; - semantic selection or clarification among device calendar, Zara calendar and configured default. Prefer Android AlarmClock contracts and normal calendar providers so compatible Samsung/user-selected applications handle requests. Do not depend on undocumented Samsung Clock APIs. ## Security and lifecycle Define confirmation, permission, cancellation, idempotency/replay, provider mutation races and principal/device binding for side effects. Calendar data and labels follow private-text logging policy. ## Tests TDD supported/unsupported handlers, permission denial/revocation, malformed times/ranges, DST/timezone boundaries, ambiguous provider, duplicate/replayed actions, process restart and server disconnect. ## Acceptance Clock actions resolve through public handlers, standard device calendars interoperate, and Zara calendar remains server/principal owned without an Android-only authoritative database.