documentation update

docs/services/memory-service.md

@@ -58,7 +58,7 @@ Six core tables:
 - **entities** — named things the system learns about (people, places, concepts)
 - **relationships** — directional labeled links between entities
 - **summaries** — condensed episode groups for efficient context retrieval
-- **projects** — named groupings of sessions with `name`, `description`, `colour`, `icon`, `isolated`
+- **projects** — named groupings of sessions with `name`, `description`, `colour`, `icon`, `isolated`, `notes`
 
 ### Migrations
 
@@ -70,6 +70,7 @@ try { db.exec(`ALTER TABLE sessions ADD COLUMN name TEXT`); } catch {}
 try { db.exec(`ALTER TABLE sessions ADD COLUMN project_id INTEGER REFERENCES projects(id)`); } catch {}
 try { db.exec(`CREATE INDEX IF NOT EXISTS idx_sessions_project ON sessions(project_id)`); } catch {}
 try { db.exec(`ALTER TABLE projects ADD COLUMN isolated INTEGER NOT NULL DEFAULT 0`); } catch {}
+try { db.exec(`ALTER TABLE projects ADD COLUMN notes TEXT`); } catch {}
 ```
 
 New migrations are always appended here — never modify the schema file for
@@ -87,22 +88,34 @@ keep the FTS index automatically in sync with the episodes table.
 - `foreign_keys = ON` — enforces referential integrity and cascade deletes
 - PRAGMAs set via `db.pragma()`, not `db.exec()`
 
-### Dynamic Session Updates
+### Dynamic Updates
 
-`updateSession` builds its `SET` clause dynamically from only the fields
-passed — prevents partial updates from overwriting fields that weren't
-touched:
+Both `updateSession` and `updateProject` build their `SET` clause dynamically
+from only the fields passed — prevents partial updates from overwriting fields
+that weren't touched:
 
 ```js
-function updateSession(id, { name, projectId } = {}) {
+// updateProject example
+function updateProject(id, fields = {}) {
+  const allowed = ['name', 'description', 'colour', 'icon', 'isolated', 'notes'];
   const updates = [];
   const values = [];
-  if (name !== undefined)      { updates.push('name = ?');       values.push(name ?? null); }
-  if (projectId !== undefined) { updates.push('project_id = ?'); values.push(projectId ?? null); }
-  // ...
+  for (const key of allowed) {
+    if (fields[key] !== undefined) {
+      updates.push(`${key} = ?`);
+      values.push(fields[key] ?? null);
+    }
+  }
+  if (updates.length === 0) return getProject(id);
+  values.push(id);
+  db.prepare(`UPDATE projects SET ${updates.join(', ')} WHERE id = ?`).run(...values);
+  return getProject(id);
 }
 ```
 
+This means saving just `{ notes: "..." }` won't touch `name`, `colour`, or
+any other field.
+
 ## Qdrant / Semantic Layer
 
 Three Qdrant collections are initialized on service startup: