dream: 2026-06-21 14:18, 3 change(s)

[USER] Prefers single reminder with multiple fire times rather than separate reminders for each time
[MEMORY] Reminders DB schema has no "frequency" column; scheduling uses separate tables (schedule_at, schedule_cron, schedule_random, reminder_fires)
[MEMORY] Use `python3` not `python` on this system (latter not found)
[MEMORY-REMOVE] "Workspace safety guard workaround: write Python runner scripts to `tmp/` using `uv run --script` with inline dependency declarations (`# /// script` metadata); graph scripts (`wiki_graph_lint.py`, `wiki_graph_extract.py`) cannot be run directly — use wrapper script in `tmp/` that imports and calls them" — the general workaround ("write Python scripts to workspace and execute them") is now captured more concisely; the graph-script-specific detail is stale context from a past wiki compilation session and no longer needed as a permanent memory entry

USER.md

@@ -55,6 +55,7 @@
 - Osobní připomínky VŽDY přes /remind skill, NIKDY přes cron tool — i jednorázové
 - Prefer cron jobs with `message` to leverage agent skills and LLM capabilities over standalone shell scripts
 - Daily reminders at random times within a window (e.g., 8:00–21:00), not at fixed clock times
+- Prefers single reminder with multiple fire times rather than separate reminders for each time
 
 ## Automation testing
 - Při nastavování periodických jobů nejprve otestuje s krátkým intervalem, po potvrzení smaže testovací job a nastaví cílový interval