lachtan/nanobot-runtime
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

dream: 2026-06-02 20:16, 2 change(s)

Browse Source 
[MEMORY] User wants important reports saved to `results/` directory with descriptive, date-prefixed filenames (e.g., `2026-06-02_remind-skill-analysis-and-improvements.md`)
[MEMORY] `/remind` skill critical issues: one-time `at` reminders fire repeatedly (60s tolerance window), non-atomic YAML writes, fragile manual YAML string construction, missing `list` subcommand, no tests for edit/send scripts, race condition between edit and send without file locking
[MEMORY] `/remind` fix priorities: P0 = atomic writes + deduplicate one-time reminders; P1 = `list` command + proper YAML serialization + validation; P2 = add tests; P3 = SQLite state tracking + edit command + cron step syntax
[MEMORY-REMOVE] "User is considering consolidating remind skill into a single script" — superseded by concrete analysis with assigned fix priorities
[MEMORY-REMOVE] "User is evaluating SQLite vs YAML for remind skill data storage" — superseded; P3 now explicitly includes SQLite state tracking
This commit is contained in:
nanobot
2026-06-02 20:21:00 +02:00
parent 0cca85f598
commit 5ef9e0dff3
2 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
memory/.dream_cursor
View File

@@ -1 +1 @@
293
294

7
memory/MEMORY.md
View File

@@ -8,6 +8,9 @@ This file stores important information that should persist across sessions.
## Preferences
### Report / result files
- Save important reports to `results/` directory with descriptive, date-prefixed filenames (e.g., `2026-06-02_remind-skill-analysis-and-improvements.md`)
### Script-writing convention
- Location: always save scripts in the `scripts/` directory.
- Language choice:
@@ -52,8 +55,8 @@ This file stores important information that should persist across sessions.
- Execution: `exec` via `/home/nanobot/.local/bin/uv run <script>`
- Empty output → silent exit (no notification sent)
- Each non-empty output line → forwarded as separate Telegram notification
- User is considering consolidating remind skill into a single script
- User is evaluating SQLite vs YAML for remind skill data storage
- `/remind` critical issues: one-time `at` reminders fire repeatedly (60s tolerance window), non-atomic YAML writes, fragile manual YAML string construction, missing `list` subcommand, no tests for edit/send scripts, race condition between edit and send without file locking
- `/remind` fix priorities: P0 = atomic writes + deduplicate one-time reminders; P1 = `list` command + proper YAML serialization + validation; P2 = add tests; P3 = SQLite state tracking + edit command + cron step syntax
## Pending Tasks