The pattern write-back pushed a style note into its "saved" list even when
the memory store answered 'unchanged', so the chat route announced
"Auto-saved 1 memory" on every repeat of the same style signal. The legacy
code checked for the note before writing; the contract port lost that.
A style note that already exists is now neither written nor reported.
Other write-back saves keep reporting repeats, as before the port.
Not logged in upstream-fixes.md: the defect came with the P1.5 port and
does not exist in the commercial product.
- Orchestrator, memory tools, context loader and pattern write-back use a
MemoryStore and a workspace scope instead of MindDB layers; the knowledge
graph tools, cognify, memory linker and feedback handler are gone (graph
hidden in v1, ADR-0002).
- The server opens one mem0 store in <dataDir>/memory/, embedded by the
in-process model on first use, and extracts facts about the user in the
background with the model the user chose (memoryExtraction setting).
- Legacy .mind memories are copied into the store once, in the background;
the legacy files are only read.
- Weaver consolidation, harvest, wiki, memory import, memory lanes, vector
backfill and index reconciliation are removed; agent runs, loops, sub-agent
results, connector fetch and the failed-turn capture write through the
contract. Workspace sessions no longer hold a mind handle.
- FileIndexer and the install audit move to waggle.db; recall date helpers and
the reranker are copied into core.
- The CLI REPL opens the same memory store.