3 Commits

Include renames

Author	SHA1	Message	Date
sandrodachandClaude Opus 5.5	d1982816c1	fix(alarms): give up after three runs without delivery (FLAW-12) ... New column alarm_failures counts ticker runs in which no channel delivered; at three the alarm is marked as done and a warning is logged instead of retrying every minute forever. Success, a new due date or reopening the task starts over with three attempts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-29 12:22:13 +01:00
sandrodachandClaude Opus 5.5	344f5e4ab2	feat(tasks): due dates with optional time; alarms at the right moment ... Due dates can carry a time (YYYY-MM-DDTHH:MM). Alarms fire at that time, or 09:00 for all-day tasks, minus the user's lead time, in TZ (default Europe/Berlin, tzdata embedded). A new due date or reopening a task re-arms the alarm. Recurrence keeps the time; Markdown export/import carry it. The UI shows relative labels ("Heute, 14:30"), marks overdue tasks to the minute and groups by local day instead of the UTC date. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-29 07:48:37 +01:00
sandrodachandClaude Opus 5.5	588c679c6a	feat(tasks): repeating tasks (daily, weekly, monthly, yearly) ... - recurrence on tasks, set in the detail dialog; 🔁 on rows and Kanban cards - Completing a repeating task (detail, list, Kanban drag to done, note checkbox) creates the next one: title, tags, priority, notes, list, assignees and rule copied, subtasks reset, first open column, due date one interval later (month end clamped); pushed live as TASK_CREATED - Each task spawns at most once (re-open + complete makes no duplicate) - Export/import keep the rule (Obsidian Tasks "🔁 every week", JSON field) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-29 07:23:09 +01:00