Update memory developer instructions to document built-in tools

Author: LEON-gittech

codex-rs/core/templates/memories/read_path.md

@@ -3,9 +3,39 @@
 You have access to a memory folder with guidance from prior runs. It can save
 time and help you stay consistent. Use it whenever it is likely to help.
 
-You may read memory files freely. If the user asks you to remember something
-explicitly, tell them they can use `/memory add <topic>` or `/memory edit <topic>`
-to create or update a memory topic. You should NOT write memory files directly.
+### Built-in Memory Tools
+
+You have built-in tools for accessing memory. **Prefer these over reading
+memory files directly**, as they handle relevance scoring, truncation, and
+formatting automatically:
+
+- `memory_read` — Read the memory index, relevant topics, and notepad priority.
+  Use this when you need a broad overview or when starting a new task.
+- `memory_search` — Search topics by query with relevance scoring. Use this
+  when looking for specific information across many topics.
+- `memory_write` — Create or update a memory topic with frontmatter.
+- `memory_add_note` — Append a timestamped note to an existing topic (creates
+  the topic if it does not exist).
+- `notepad_read` — Read the notepad (all sections or a specific section:
+  `priority`, `working`, or `manual`).
+- `notepad_write_priority` — Set the current top-priority item (≤500 chars,
+  replaces the previous priority). This is automatically injected into your
+  context on the next turn.
+- `notepad_write_working` — Append a timestamped working note.
+- `notepad_prune` — Remove working-memory entries older than N days.
+
+### Slash Commands (TUI)
+
+Users can also manage memory via the TUI:
+
+- `/memories list` — List all memory topics.
+- `/memories add <topic>` — Create a new topic in an external editor.
+- `/memories edit <topic>` — Edit an existing topic in an external editor.
+- `/memories clear` — Delete all memory topics.
+
+If the user asks you to remember something explicitly, tell them they can use
+`/memories add <topic>` or `/memory edit <topic>` to create or update a memory
+topic, or you can use `memory_write` / `memory_add_note` directly.
 
 Decision boundary: should you use memory for a new user query?
 
@@ -22,26 +52,36 @@ Decision boundary: should you use memory for a new user query?
 
 Memory layout (general -> specific):
 
-- {{ base_path }}/memory_summary.md (already provided below; do NOT open again)
 - {{ base_path }}/MEMORY.md (searchable registry; primary file to query)
+- {{ base_path }}/topics/ (individual topic files with YAML frontmatter)
+  - Each topic has: name, description, type, keywords, source
+  - Topics are scored by relevance to the current query
+- {{ base_path }}/notepad.md (structured scratchpad)
+  - PRIORITY: current top-priority item (auto-injected into context)
+  - WORKING MEMORY: timestamped session notes (auto-prunable)
+  - MANUAL: permanent notes
+- {{ base_path }}/memory_summary.md (already provided below; do NOT open again)
 - {{ base_path }}/skills/<skill-name>/ (skill folder)
   - SKILL.md (entrypoint instructions)
   - scripts/ (optional helper scripts)
   - examples/ (optional example outputs)
   - templates/ (optional templates)
- - {{ base_path }}/rollout_summaries/ (per-rollout recaps + evidence snippets)
+- {{ base_path }}/rollout_summaries/ (per-rollout recaps + evidence snippets)
   - The paths of these entries can be found in {{ base_path }}/MEMORY.md or {{ base_path }}/rollout_summaries/ as `rollout_path`
   - These files are append-only `jsonl`: `session_meta.payload.id` identifies the session, `turn_context` marks turn boundaries, `event_msg` is the lightweight status stream, and `response_item` contains actual messages, tool calls, and tool outputs.
   - For efficient lookup, prefer matching the filename suffix or `session_meta.payload.id`; avoid broad full-content scans unless needed.
 
 Quick memory pass (when applicable):
 
-1. Skim the MEMORY_SUMMARY below and extract task-relevant keywords.
-2. Search {{ base_path }}/MEMORY.md using those keywords.
-3. Only if MEMORY.md directly points to rollout summaries/skills, open the 1-2
+1. If you need a broad overview, use `memory_read` to get the index, top
+   topics, and notepad priority in one call.
+2. If you need specific information, use `memory_search` with targeted keywords
+   to find relevant topics with relevance scoring.
+3. Only if the built-in tools are insufficient, search
+   {{ base_path }}/MEMORY.md directly using those keywords.
+4. Only if MEMORY.md directly points to rollout summaries/skills, open the 1-2
    most relevant files under {{ base_path }}/rollout_summaries/ or
    {{ base_path }}/skills/.
-4. If above are not clear and you need exact commands, error text, or precise evidence, search over `rollout_path` for more evidence.
 5. If there are no relevant hits, stop memory lookup and continue normally.
 
 Quick-pass budget: