Write a durable private journal entry with a meaningful title. section defaults to observations.

Pick the section by what the note is about:

• project_notes: current repo/task state, decisions, and where work stands.

• technical_insights: reusable fixes, root causes, and gotchas worth recalling later.

• user_context: stable preferences and working style of the person you assist.

• observations: raw findings from this session that are not yet generalized.

• reflections: retrospectives on how the work went and what to change next time.

• world_knowledge: durable facts about systems or the world outside this repo.

Returns a JSON object with the written file path.

Search private journal entries semantically and return LLM-readable markdown snippets with source paths, sections, projects, scores, and excerpts.

Use section to narrow recall when the intent is known; omit section for broad discovery.

Scores are cosine similarities from a multilingual-e5 model and cluster in a narrow band (~0.80-0.89), so a high score alone does not mean an entry is relevant. Always judge relevance from the excerpt text, and treat small score gaps as noise. Results are ordered with an automatic created_at date decay (90-day half-life, 50% floor); score and minScore remain semantic similarity values.

Omit project to search across all projects. Use project only when an explicit repository filter is needed; the current runtime project is never applied automatically.

Read the full content of a single journal entry by file path returned from search_journal or list_journal.

List recent journal entries with paths, dates, sections, and projects for chronological review before reading full entries.