refactor(web): move the Memory screens onto the memory contract API (P1.5)
- adapter: memory ids are strings; single-memory calls take only the id
(no ?mind= disambiguation). searchMemory takes the workspace as its own
parameter. New getMemoryCapabilities / setMemoryExtraction. Removed:
incrementFrameAccess, getMemoryOriginalSource, listSuppression,
allowReimport, getWeaverStatus, and the dead importPreview, importCommit
and getWikiWatermark. eraseMemory takes { id } or { sessionId }.
- memory-features reads GET /api/memory/capabilities for the knowledge
graph; history import, wiki, hooks, Room and the memory MCP stay hidden
(ADR-0002). useMemoryCapabilities re-renders the Memory screens.
- Settings > General has a Memory toggle for background fact extraction.
- Memory Center: the confidence filter, the erased-sources panel, the
original-source view and the Deprecated chip are gone; Erase forgets
every memory saved from the chat a memory came from and is offered only
for memories with a chat session. Memory kinds follow the contract.
- Trust views show short memory labels for the new string ids and drop the
per-row "not scored yet" badge (v1 stores no confidence).
- The Weaver maintenance view and the Cockpit weaver card are removed
(the weaver package and its routes are deleted).
- Timeline uses the contract kinds and maps important/temporary
importance.
Logs UF-033 (search scope sent as the workspace id), UF-034 (importance
mapping) and UF-035 (restore over open databases, open).
This commit is contained in:
@@ -63,6 +63,9 @@ Baseline: commit `b20b138` of `git.os-dev.tech/oleg.m/waggle-os`.
|
||||
| UF-032 | Team capability policies are always read from the team "default" | Open | Team mode, governance |
|
||||
| UF-033 | Command palette memory search uses whichever workspace the Memory app opened last | Fixed | Sidecar, command palette |
|
||||
| UF-034 | Artifact Center "related sessions" never finds a chat session | Fixed | Sidecar, Artifact Center |
|
||||
| UF-035 | Timeline search and the chat recall toast send the workspace id as the search scope | Fixed | Web UI, memory, privacy |
|
||||
| UF-036 | The web client reads "important" and "temporary" memories as normal importance | Fixed | Web UI, memory |
|
||||
| UF-037 | Restore overwrites database files the running sidecar holds open | Open | Sidecar, backup |
|
||||
|
||||
## Entries
|
||||
|
||||
@@ -344,3 +347,30 @@ Entries UF-010 to UF-019 come from the UI audit `anti-slop/audit-001-2026-10-14.
|
||||
- Cause: the route matches the query against the memory engine's session rows (`SessionStore.getActive()`, their `summary` and `gop_id`). Those rows are named write buckets such as 'harvest', 'agent-runs' or 'loop', not chat sessions; chat transcripts are JSONL files under `<dataDir>/workspaces/<id>/sessions/`.
|
||||
- What we did: the route runs `searchSessions()` over each workspace's chat session files, the same search as `GET /api/workspaces/:id/sessions/search`, and returns the session id, title, workspace and the first matching snippet.
|
||||
- Recommendation: do the same in the main project.
|
||||
|
||||
### UF-035. Timeline search and the chat recall toast send the workspace id as the search scope
|
||||
- Status: Fixed
|
||||
- Found: 2026-10-24
|
||||
- Where: at commit `b20b138`, `apps/web/src/hooks/useMemory.ts:25` (`searchMemory(filters.searchQuery, workspaceId)`), `apps/web/src/components/os/apps/ChatApp.tsx:670` (`scope = workspaceId ?? 'global'`), `packages/server/src/local/routes/memory.ts:259-278` (`/api/memory/search`)
|
||||
- Symptom: a search in Memory → Timeline, and the "I just remembered something relevant" toast in a workspace chat, do not search the open workspace. They return personal memories plus those of whichever workspace mind the sidecar attached last, which can belong to another workspace.
|
||||
- Cause: both callers pass the workspace id as `scope` and send no `workspace` parameter. The route treats an unknown scope as 'all' and, without a `workspace` parameter, searches `multiMind` with the workspace mind it still holds from an earlier request.
|
||||
- What we did: the client sends `scope=all&workspace=<id>`; the memory contract version of the route searches exactly the scopes it is asked for (personal memory plus the named workspace, personal only when none is named).
|
||||
- Recommendation: pass the workspace as its own parameter in both callers, and make the route resolve an unknown scope to personal memory only instead of reusing a previously attached workspace mind.
|
||||
|
||||
### UF-036. The web client reads "important" and "temporary" memories as normal importance
|
||||
- Status: Fixed
|
||||
- Found: 2026-10-24
|
||||
- Where: at commit `b20b138`, `apps/web/src/lib/adapter.ts:223` (`IMPORTANCE_MAP`) and `:252` (`normalizeFrame`)
|
||||
- Symptom: the Timeline shows important memories with the same importance dots as normal ones, its minimum-importance filter cannot separate them, and the login briefing, which ranks highlights by importance, ranks important memories like normal ones.
|
||||
- Cause: the sidecar returns the frame-store importance values (critical, important, normal, temporary), but the client maps only low, normal, high and critical, so 'important' and 'temporary' fall back to 2 (normal).
|
||||
- What we did: the map now covers temporary (1) and important (3), and keeps low and high for the Tauri command.
|
||||
- Recommendation: map the importance values the sidecar actually returns.
|
||||
|
||||
### UF-037. Restore overwrites database files the running sidecar holds open
|
||||
- Status: Open
|
||||
- Found: 2026-10-24
|
||||
- Where: at commit `b20b138`, `packages/server/src/local/routes/backup.ts:380-542` (`POST /api/restore`)
|
||||
- Symptom: restoring a backup while Waggle runs writes `personal.mind`, the workspace minds and the other SQLite files over the files the sidecar has open. The running process keeps its old view of the data and can write over the restored files, or leave a WAL file that no longer matches them.
|
||||
- Cause: the restore writes every file of the archive in place (only `marketplace.db` is skipped) without closing the open databases first.
|
||||
- What we did: nothing yet. In the community edition the same applies to `waggle.db` and the mem0 files in `<dataDir>/memory/`.
|
||||
- Recommendation: stage the restored files and apply them at the next start, before any database opens, as the data-erase marker does; or close the databases, restore, and restart the sidecar.
|
||||
|
||||
Reference in New Issue
Block a user