feat: wiki single-source-of-memory replaces FTS5 memory tools

[UmarFarooq75]

Summary

Switches daemora's memory model to a Karpathy-style wiki — persistent LLM-maintained markdown under data/wiki/ — replacing the separate FTS5 notebook the agent queried via memory_save / memory_recall. Single source of truth, accessed through the agent's existing filesystem tools.

Why

The agent had two parallel paths for "remember a fact" (memory_save) and "look up a fact" (memory_recall) on top of an FTS5 table that re-derived synthesis on every query. That setup encouraged the agent to hallucinate which path to use and rediscover context every recall. The wiki keeps the synthesis already built and lets the same filesystem tools the agent already has carry the load.

Architecture

• data/wiki/{projects,people,topics,decisions}/*.md — synthesis pages
• data/wiki/index.md — table of contents
• data/wiki/log.md — append-only event ledger (every memory save + gallery change writes one line)
• data/wiki/.sync-cursor — heartbeat sync watermark

Phase 1 — skeleton + write hooks

• New src/wiki/WikiLog.ts — idempotent skeleton + atomic append (POSIX O_APPEND).
• MemoryStore.save() and FileProjectStore mutations (create / updateMeta / delete / addFile / removeFile) each append one structured line to log.md so synthesis turns get reliable signal.

Phase 2 — idle maintenance turn

• Heartbeat gets a third mode (wikiSyncCheck) on a 10 min cadence (WIKI_SYNC_INTERVAL_MINUTES env override).
• Reads only the unsynced tail of log.md, drops trailing partial lines, hands the agent a 16KB-capped delta + the new cursor, and the same main agent folds events into pages with read_file / write_file / edit_file.
• Skips when the user has been active within the last 5 min (SessionStore.lastUserActivityAt() tracks user-role message timestamps).
• Best-effort: cursor only advances after the agent writes it back, so a failed turn just retries on the next tick.

Phase 3 — drop the duplicate path

• Remove memory_save and memory_recall from the tool registry.
• MemoryStore stays wired so existing rows remain queryable from internal code; the agent simply no longer sees a memory tool surface.

SOUL.md

• Replaced the rule-list ## Memory section with a principle-led ## Wiki — your single source of memory section: page health (50–200 lines, cap 350), conflict handling (in-place blockquotes), source provenance, idle-maintenance contract.
• Fixed stale searchMemory / writeMemory references in the teamTask section.

Test plan

• npm run typecheck clean (verified locally)
• First boot creates data/wiki/ skeleton with index.md, log.md, four subdirs
• Calling any memory-affecting path (memory save via internal code, gallery file add, project create) appends one event line to log.md
• Heartbeat tick logs wiki sync — enqueuing maintenance turn when log.md has unsynced content and the user has been quiet for >5 min
• Memory tools (memory_save / memory_recall) no longer surface to the agent
• No runtime crash with empty data/wiki/ (skeleton creation is idempotent)