docs(memory): tighten long-term memory hygiene

memory/2026-03-11.md

@@ -0,0 +1,20 @@
+# 2026-03-11
+
+## Memory maintenance
+- Reviewed recent memory habits and did a cleanup pass.
+- Assessment:
+  - capture frequency: good
+  - long-term curation: decent but lagging behind capture
+  - organization: getting messy due to a mix of daily logs, one-off topical notes, references, plans, logs, and machine-readable state in `memory/`
+- Cleaned up `MEMORY.md` so it stores durable facts/lessons instead of mixed-in runtime/instruction text.
+- Added a clearer rule to `AGENTS.md`: use named memory files only for long-lived plans/references/investigations; otherwise prefer the daily note.
+
+## Durable lessons promoted to MEMORY.md
+- Check current state before suggesting setup/re-setup.
+- Treat Telegram DM and TUI/webchat as separate main-session contexts when `session.dmScope = "per-channel-peer"` is active.
+- Prefer local-first search routing and remember Brave free-plan rate limits.
+- Keep backup/transcription infrastructure notes in long-term memory when they affect future operations.
+
+## Follow-up intent
+- Be more disciplined about using the daily note as the default inbox and promoting only durable truths into `MEMORY.md`.
+- Avoid adding new one-off memory files unless the topic is truly long-lived.