superlocalmemory 4.0.6 → 4.0.8

package/CHANGELOG.md

@@ -5,6 +5,127 @@ All notable changes to SuperLocalMemory will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [4.0.8] — Where you were actually looking
+
+### Added
+- **Summaries reach agents and the dashboard.** 4.0.7 gave the summary layer a
+  command; an agent still had no way to ask for one, and neither did anyone
+  reading the dashboard. Adds the `get_memory_summary` tool and a **Summaries**
+  tab under Memories with Today, Yesterday, and a picker listing the projects
+  SuperLocalMemory has actually recorded activity in. Every result states how
+  many memories it was built from and how much it covered.
+- **Bounded Loops has its own page**, alongside the other integrations. It shows
+  whether Bounded Loops is installed, which agreement the two products
+  negotiated, and which finished runs have been imported — and states plainly
+  that imported evidence is read-only: SuperLocalMemory never learns from it, no
+  file paths leave your workspace, and the tamper-evidence it carries is not the
+  same thing as independent verification.
+- **Mesh shows its history**, not only who is connected this second. Sessions
+  leave the mesh when they end, so the page was empty between sessions even on a
+  machine with plenty of mesh activity.
+
+### Changed
+- **Recall Lab is the first thing you see under Memories**, with example
+  questions to start from. Summaries sits next to it. The three browsing views
+  follow.
+
+### Fixed
+- **Memory stopped learning from use.** Recall marks which memories it returned
+  so that later use can be credited back, but the mark never reached the
+  assistant, so nothing was ever credited. Every recall was scored as neither
+  good nor bad, which is why recall quality sat at its starting value and no
+  source ever showed a settled quality signal however much the memory was used.
+- **The behavioural half of consolidation had never run.** Nothing triggered it,
+  and when it did run, two of its four steps failed without reporting anything.
+  SuperLocalMemory now runs it on a schedule while idle — never while you are
+  storing or recalling — and at session end.
+- **"This project" summaries could not work.** The button sent no project, and
+  the answer was always an error. SuperLocalMemory installs once for your whole
+  machine, so a browser tab has no way to know which project you mean; it now
+  lists the ones it has seen.
+- **Locally written summaries began with an apology.** The local model was never
+  told what it was writing, so it replied as if in a chat. It now returns the
+  summary and nothing else.
+- **A summary built from nothing claimed to cover everything.** A project with
+  recorded activity but no saved facts is now reported as a partial view.
+- **Multi-Agent Memory showed access tokens instead of agent names**, and because
+  one agent uses many tokens over time, a single agent appeared as dozens.
+- **Optimize invented a chart.** The cache hit-rate graph drew a rising trend
+  generated from the current value rather than measured; no history is recorded,
+  so it is gone until there is something real to plot. "Tokens saved" was
+  labelled as a monthly figure with an upward arrow that nothing ever set — it is
+  a total since install, and now says so. The page also explains why its numbers
+  are zero while its switches are on.
+- **One kind of memory pattern was never produced.** The query that finds it
+  asked for columns that do not exist, so it failed on every run and was skipped
+  silently.
+- **Code links never appeared for anyone.** Two separate reasons. The pass that
+  creates them matched no facts at all on a real store — it looked for an empty
+  archive marker, while live facts carry `live`, so every fact was excluded. And
+  the panel that displayed them was the search-results view, not the memory
+  drawer people actually open. Both fixed; on a real store this produces 7,470
+  links across 3,603 memories.
+- **"Atomic facts" always read "No atomic facts recorded for this memory."** The
+  drawer looked up child facts using the row's own id, but a row in that pane is
+  itself an atomic fact and its parent is a separate field. Records stored
+  directly, which have no parent, now say so rather than reporting missing data.
+- **Summaries ignored your mode.** The command never passed the configuration, so
+  every summary took the no-model path — a Mode B user got Mode A output. Ollama
+  now writes them when configured, falling back if it is unavailable.
+- **Summary highlights were unreadable.** Truncation counted characters but
+  ignored newlines, so one fact containing headings and blank lines rendered as
+  six lines and the list stopped being a list.
+- **"Active entities" listed internal identifiers** instead of names. It now
+  reads `Fixed (127), Gateway (124)`.
+
+## [4.0.7] — Reachable
+
+Everything here was already built. None of it could be used.
+
+### Added
+- **`slm summary` — the readable layer over your memories.** Requested in #113
+  and shipped without a way to call it in 4.0.6.
+  - `slm summary day` — what you recorded today (also `yesterday`, or a date)
+  - `slm summary project` — what was worked on, for a directory
+  - `slm summary session <id>` — what one session covered
+
+  Every summary says how much of the underlying data it could actually see, and
+  `--json` lists the exact memories it was built from. Session data is sparse —
+  roughly 4% of facts carry a session id — so a session summary reports that
+  rather than presenting a fraction as the whole. No language model needed, so
+  these work in the fully offline mode.
+- **Memories now link to the code they mention.** A memory that names a
+  function, method or file is connected to it in the code graph, with a short
+  description of what it points at and a marker when the code has since changed.
+  Expanding a memory in the dashboard shows this; nothing appears if you have no
+  code graph. Runs during background maintenance, never when a memory is saved,
+  and requires no language model.
+- **`scripts/bump_version.py`** sets the release version in all fifteen places
+  that declare one, with `--check` for CI.
+
+### Fixed
+- **The code↔memory bridge never ran.** Four things were missing at once: setup
+  wrote a `bridge_enabled` flag no code read, the code-graph build discarded it,
+  the code-graph settings had no loader at all, and the method the bridge was
+  written against was an unimplemented placeholder. Enabling the code graph
+  during setup left the flag on disk and the feature inert, with nothing to
+  indicate it.
+- **Version numbers disagreed across the project.** 4.0.6 shipped with the pip
+  requirements pins, the npm lockfile, the editor plugin manifest, the citation
+  metadata and the lockfile all still reading 4.0.5, and the agent rule footers
+  reading 4.0.4. Installing from `requirements.txt` fetched the wrong release.
+- **Stale-memory checks reported "nothing is stale" when the feature was off.**
+  They answer entirely from code links, so with linking disabled they returned an
+  empty list — the most reassuring possible answer, from something that never
+  ran. They now say the feature is off, and the remediation message names a
+  setting that exists (it previously named one that did not).
+- **`slm help` did not mention `gdpr`**, which shipped in 4.0.6. The drift guard
+  that should have caught it only read one file, so a command registered
+  elsewhere was exempt from the check.
+- **Consolidation could create a database file named after a bad argument.**
+  Given something that was neither a database handle nor a path, it stringified
+  the object and let SQLite create that filename. It now refuses the argument.
+
 ## [4.0.6] — The Connected Brain
 
 ### Added
@@ -14,10 +135,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   a starting value as a measured result. Source quality no longer lists internal
   identifiers; when nothing has been measured yet it says so and explains what
   would change that.
-- **Session, daily and project summaries.** A readable layer over your memories:
-  what a session covered, what a day's main topics were, and what was worked on
-  per project. Each one links back to the memories it came from, and each states
-  how much of the underlying data it could actually cover. Requested in #113.
+- **Session, daily and project summaries — generators only, not yet reachable.**
+  A readable layer over your memories: what a session covered, what a day's main
+  topics were, and what was worked on per project. Each links back to the
+  memories it came from and states how much of the underlying data it could
+  actually cover. Corrected after release: 4.0.6 ships the generators but no
+  command, tool or endpoint that calls them, so there is no way to use this yet.
+  The surface lands in 4.0.7. Requested in #113.
 - **Entity-level memory consolidation now runs.** Repeated facts about the same
   entity are merged during maintenance, and the originals are archived rather
   than deleted.

package/README.md

@@ -5,7 +5,7 @@
   </picture>
 </p>
 
-<h1 align="center">SuperLocalMemory V4.0.6</h1>
+<h1 align="center">SuperLocalMemory V4.0.8</h1>
 
 <h2 align="center">Rent the LLM. Own the memory.</h2>
 
@@ -27,12 +27,12 @@ guarantee here is stated as a falsifiable invariant, tested under an adversarial
 negative control, and shipped with the harness that regenerates the evidence:
 <code>python benchmark/run_all.py --trials 200 --output-dir results/</code>. What each experiment
 does <em>not</em> exercise is stated too.</p>
-<p align="center"><code>v4.0.6</code> — one control plane: <strong>SLM-Mesh</strong> peer coordination · multi-scope memory (personal / shared / global) · profiles · Cache · Compress · 7-layer retrieval · code graph · Entity Explorer · skill evolution · Modes A/B/C · GDPR retention &amp; audit chain · bounded loops — across CLI, MCP, dashboard, the <strong>Claude plugin</strong>, the <strong>Codex add-on</strong>, and documented IDE integrations.<br/>
+<p align="center"><code>v4.0.8</code> — one control plane: <strong>SLM-Mesh</strong> peer coordination · multi-scope memory (personal / shared / global) · profiles · Cache · Compress · 7-layer retrieval · code graph · Entity Explorer · skill evolution · Modes A/B/C · GDPR retention &amp; audit chain · bounded loops — across CLI, MCP, dashboard, the <strong>Claude plugin</strong>, the <strong>Codex add-on</strong>, and documented IDE integrations.<br/>
 Proxy: <code>slm wrap claude</code> &nbsp;·&nbsp; MCP: add <code>slm_compress</code> to your config &nbsp;·&nbsp; Skill: zero-config</p>
 <p align="center"><strong>Four public arXiv preprints</strong> · V4: <a href="https://arxiv.org/abs/2608.08253">arXiv:2608.08253</a> · companion archive: <a href="https://zenodo.org/records/21853302">Zenodo 21853302</a> (<a href="https://doi.org/10.5281/zenodo.21853302">DOI 10.5281/zenodo.21853302</a>) · prior preprints: <a href="https://arxiv.org/abs/2603.02240">2603.02240</a> · <a href="https://arxiv.org/abs/2603.14588">2603.14588</a> · <a href="https://arxiv.org/abs/2604.04514">2604.04514</a>.</p>
 
 <p align="center">
-  <a href="CHANGELOG.md"><img src="https://img.shields.io/badge/v4.0.6-Current_Release-2ea44f?style=for-the-badge&logo=checkmarx&logoColor=white" alt="v4.0.6 — Current Release"/></a>
+  <a href="CHANGELOG.md"><img src="https://img.shields.io/badge/v4.0.8-Current_Release-2ea44f?style=for-the-badge&logo=checkmarx&logoColor=white" alt="v4.0.8 — Current Release"/></a>
   <a href="https://arxiv.org/abs/2608.08253"><img src="https://img.shields.io/badge/arXiv-2608.08253-b31b1b?style=for-the-badge&logo=arxiv&logoColor=white" alt="SuperLocalMemory 4.0 paper on arXiv:2608.08253"/></a>
   <a href="https://zenodo.org/records/21853302"><img src="https://img.shields.io/badge/Zenodo-10.5281%2Fzenodo.21853302-1682D4?style=for-the-badge&logo=zenodo&logoColor=white" alt="V4 paper on Zenodo: 10.5281/zenodo.21853302"/></a>
   <a href="https://arxiv.org/abs/2603.14588"><img src="https://img.shields.io/badge/arXiv-2603.14588-b31b1b?style=for-the-badge&logo=arxiv&logoColor=white" alt="arXiv Paper"/></a>
@@ -62,16 +62,11 @@ SuperLocalMemory V4 combines conventional dense and lexical retrieval with graph
 
 **Memory with a sense of time.** SLM does not only store *what* an agent learned — it records *when*. Every fact carries ingestion timing and provenance; recall runs a dedicated temporal candidate channel alongside semantic, lexical, and associative retrieval; scenes and entity timelines reconstruct sequence; and the lifecycle lets neglected memory decay and self-archive instead of growing without bound. Time is a first-class ranking and lifecycle signal rather than a timestamp column an agent never reads — which is what lets a long-lived agent reason about how its context changed, not only what it currently holds.
 
-**What V4.0.6 ships.** The Living Brain is written for the person who owns the memory, not for the person who built the ranker. It leads with how many questions your memory has actually answered instead of a raw event count, names its ranking phase in words, and refuses to present an untrained starting value as a measured result — where nothing has been measured yet, it says so and says what would change that. Alongside it, a readable consolidation layer: session, daily, and project summaries, each linked back to the memories it was derived from and each explicit about how much of the underlying data it could cover. Entity-level consolidation now actually runs during maintenance, merging repeated facts about the same entity and archiving the originals rather than deleting them. Codex and Bounded Loops are detected and shown among connected clients, labelled by the evidence that supports them — configuration proves setup, not traffic, and the dashboard says which one it has. Presence now distinguishes "no agents are active" from "presence has stopped being recorded", because those looked identical before and only one of them is fine. See [reviewed corrections](docs/reviewed-corrections.md) for the correction lifecycle and [MCP tools](docs/mcp-tools.md) for host-facing commands.
+**What V4.0.7 ships.** Three things that existed but could not be used. `slm summary` gives you a readable layer over your own memories — `day` for what you recorded today, `project` for a directory, `session` for one session — each stating how much of the underlying data it could actually see, with `--json` listing the exact memories it came from. Memories that mention a function, method or file are now linked to that code, with a short description of what they point at and a marker once the code has changed; expanding a memory in the dashboard shows it. Both need no language model, so they work in the fully local mode. The code↔memory bridge behind the second one had never run at all: the setup flag was written and never read, the build discarded it, its settings had no loader, and the method it was written against was an unimplemented placeholder. Linking runs during background maintenance, never when a memory is saved. See [reviewed corrections](docs/reviewed-corrections.md) for the correction lifecycle and [MCP tools](docs/mcp-tools.md) for host-facing commands.
 
-**Fixed in V4.0.6.** The knowledge graph no longer opens blank. It framed itself against a canvas that had no size yet, spent its whole frame budget drawing off-screen, and stopped — so the graph appeared only after you moved the node slider. Returning to the pane cleared the canvas without redrawing it, which failed the same way for a different reason. Both are fixed, the default node count is 50, and on narrower screens the details and chat panel is reachable instead of stranded a screen-height below the fold. Recall no longer raises when the reranker reports success but returns no scores; it falls back to its existing ranking. Corrections attempted without the daemon now refuse with the reason and the remedy, rather than reporting a transient error that could never clear.
+**Fixed in V4.0.7.** Version numbers disagreed across the project — the pip requirement pins, npm lockfile, editor plugin manifest, citation metadata and lockfile all still named the previous release, so installing from `requirements.txt` fetched the wrong version; one script now sets all fifteen. Stale-memory checks reported "nothing is stale" when code linking was simply switched off, and pointed at a setting that did not exist. `slm gdpr` was missing from `slm help`. Consolidation, handed something that was neither a database handle nor a path, created a file named after the object instead of refusing it.
 
-**Carried forward from V4.0.5.** A correction is a review-gated lifecycle, not an in-place edit: SLM creates an immutable successor, keeps it out of current recall until an authenticated reviewer applies it, and preserves the predecessor for time-aware history. Every candidate path, including cached context, pins, bridge expansion, and scene expansion, uses hard current-truth admission and abstains if that truth cannot be read. `slm brain`, MCP, HTTP, and the Living Brain share one observation-only BrainTruth snapshot; feedback, external Bounded Loops evidence, and receipt claims are shown honestly but do not silently alter recall, ranking, or model routing. The optional Bounded Loops bridge remains capability-negotiated and independent.
-
-**Adaptive-ranking migration.** V4.0.6 leaves the optional adaptive ranker off
-unless an operator sets `SLM_RANKING` (`v1`, `v2`, or `v2-ensemble`). This does
-not disable the normal retrieval channels; it prevents feedback and
-observation data from changing ranking without an explicit operator decision.
+**Carried forward from V4.0.5 and V4.0.6.** A correction is a review-gated lifecycle, not an in-place edit: SLM creates an immutable successor, keeps it out of current recall until an authenticated reviewer applies it, and preserves the predecessor for time-aware history. Every candidate path — cached context, pins, bridge and scene expansion — uses hard current-truth admission and abstains if that truth cannot be read. `slm brain`, MCP, HTTP and the Living Brain share one observation-only BrainTruth snapshot; feedback, external Bounded Loops evidence and receipt claims are shown honestly but never silently alter recall, ranking or model routing. The Living Brain leads with how many questions your memory has answered rather than a raw event count, and says so plainly where nothing has been measured yet. The knowledge graph opens reliably, with a default of 50 nodes and its details panel reachable on narrow screens. The optional adaptive ranker stays off unless an operator sets `SLM_RANKING` (`v1`, `v2`, or `v2-ensemble`) — that gate prevents feedback and observation data from changing ranking without an explicit decision, and does not disable the normal retrieval channels.
 
 - **[SLM-Mesh](#slm-mesh-cross-session--cross-machine-coordination)** — authenticated cross-session and cross-machine peer coordination (messages, locks, shared state, inbox/outbox, optional discovery). Coordination only — not automatic replicated memory.
 - **Multi-scope memory & profiles** — workspaces (profiles) plus `personal` / `shared` / `global` scopes; cross-profile recall is default-deny.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "superlocalmemory",
-  "version": "4.0.6",
+  "version": "4.0.8",
   "description": "Local-first agent memory with MCP and an agent-native CLI. Documented clients include Claude Code, Cursor, and Windsurf.",
   "keywords": [
     "ai-memory",

package/plugin/.claude-plugin/plugin.json

@@ -15,5 +15,5 @@
   "mcpServers": "./.mcp.json",
   "name": "superlocalmemory",
   "repository": "https://github.com/qualixar/superlocalmemory",
-  "version": "4.0.5"
+  "version": "4.0.8"
 }

package/plugin/CLAUDE.md

@@ -1,4 +1,4 @@
-<!-- BEGIN SuperLocalMemory v4.0.5 -->
+<!-- BEGIN SuperLocalMemory v4.0.8 -->
 
 ## SuperLocalMemory (SLM) — Agent Rules
 
@@ -39,6 +39,6 @@ slm-recall · slm-remember · slm-session · slm-status · slm-cache · slm-comp
 ### Subagents
 slm-memory-advisor (memory decisions, session hygiene, scope/profile guidance) · slm-optimize-advisor (context compression + KV cache) · slm-governance-advisor (scope/roles/compliance/GDPR)
 
-<!-- END SuperLocalMemory v4.0.5 -->
+<!-- END SuperLocalMemory v4.0.8 -->
 
-SuperLocalMemory v4.0.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later

package/plugin/agents/slm-governance-advisor.md

@@ -77,4 +77,4 @@ slm-scope · slm-governance · slm-profile · slm-remember · slm-recall
 # What NOT to do
 Never session_init twice; never forget without dry-run preview; never store secrets; never bypass role checks; never claim an erasure succeeded without verifying via recall.
 
-SuperLocalMemory v4.0.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later

package/plugin/agents/slm-loop-runner.md

@@ -68,4 +68,4 @@ assessment. The gate is the authority.
 
 ---
 
-SuperLocalMemory v4.0.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later

package/plugin/agents/slm-memory-advisor.md

@@ -46,4 +46,4 @@ slm-recall · slm-remember · slm-session · slm-scope · slm-profile · slm-gov
 # What NOT to do
 Never session_init twice; never forget dry_run=False without reporting preview; never dump a whole file into remember; never invent a memory; never claim "saved" without success:true / clean CLI exit; never bypass scope or governance restrictions.
 
-SuperLocalMemory v4.0.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later

package/plugin/agents/slm-optimize-advisor.md

@@ -41,4 +41,4 @@ slm-compress · slm-cache · slm-status · slm-profile
 # What NOT to do
 Never compress code-for-edit/JSON-to-parse/<500 chars; never store secrets/ccr_ids; never let optimize failure block/alter the task; never claim a specific savings %; never carry ccr_ids across profile switches.
 
-SuperLocalMemory v4.0.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later

package/plugin/requirements.txt

@@ -1 +1 @@
-superlocalmemory==4.0.5
+superlocalmemory==4.0.8

package/plugin/skills/slm-cache/SKILL.md

@@ -145,4 +145,4 @@ These subcommands control daemon-level cache settings. They do not read or write
 
 ---
 
-SuperLocalMemory v4.0.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later

package/plugin/skills/slm-compress/SKILL.md

@@ -147,4 +147,4 @@ Content over 1 MB (1 000 000 bytes UTF-8) is processed but `reversible` is force
 
 ---
 
-SuperLocalMemory v4.0.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later

package/plugin/skills/slm-governance/SKILL.md

@@ -245,4 +245,4 @@ Before running any destructive operation (`forget`, `compact_memories`):
 
 ---
 
-*SuperLocalMemory v4.0.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later*

package/plugin/skills/slm-graph/SKILL.md

@@ -312,4 +312,4 @@ profile. See `slm-profile` for the full profile switching workflow.
 
 ---
 
-SuperLocalMemory v4.0.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later

package/plugin/skills/slm-loop/SKILL.md

@@ -96,4 +96,4 @@ paused, name the approval needed; when errored, quote the short detail.
 
 ---
 
-SuperLocalMemory v4.0.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later

package/plugin/skills/slm-mesh/SKILL.md

@@ -279,4 +279,4 @@ mesh availability.
 
 ---
 
-*SuperLocalMemory v4.0.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later*

package/plugin/skills/slm-profile/SKILL.md

@@ -146,4 +146,4 @@ Name them differently in your MCP config (e.g. `superlocalmemory-personal` and
 
 ---
 
-*SuperLocalMemory v4.0.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later*

package/plugin/skills/slm-recall/SKILL.md

@@ -236,4 +236,4 @@ before recalling, then switch back. See `slm-profile` for workspace switching.
 
 ---
 
-*SuperLocalMemory v4.0.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later*

package/plugin/skills/slm-remember/SKILL.md

@@ -238,4 +238,4 @@ different workspace, use `switch_profile` first. See `slm-profile`.
 
 ---
 
-*SuperLocalMemory v4.0.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later*

package/plugin/skills/slm-scope/SKILL.md

@@ -173,4 +173,4 @@ to review the impact. See `slm-remember` for the full deletion discipline.
 
 ---
 
-*SuperLocalMemory v4.0.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later*

package/plugin/skills/slm-session/SKILL.md

@@ -227,4 +227,4 @@ explicitly and call `recall` with `include_global`/`include_shared` after
 
 ---
 
-*SuperLocalMemory v4.0.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later*

package/plugin/skills/slm-status/SKILL.md

@@ -163,4 +163,4 @@ multi-profile setup. To switch the active profile, see `slm-profile`.
 
 ---
 
-SuperLocalMemory v4.0.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later

package/plugin-src/rules/AGENTS.md

@@ -129,4 +129,4 @@ When the SLM MCP server is unavailable, use these CLI equivalents:
 - **slm-optimize-advisor** — context compression and KV cache
 - **slm-governance-advisor** — scope/role compliance, retention policies, GDPR
 
-SuperLocalMemory v4.0.4 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.0.8 · Qualixar · AGPL-3.0-or-later

package/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "superlocalmemory"
-version = "4.0.6"
+version = "4.0.8"
 description = "Local-first agent memory with auditable hybrid retrieval"
 readme = "README.md"
 license = "AGPL-3.0-or-later"

package/src/superlocalmemory/__init__.py

@@ -32,7 +32,7 @@ if "OMP_NUM_THREADS" not in os.environ:
     os.environ["OMP_NUM_THREADS"] = "2"
 # ---------------------------------------------------------------------------
 
-__version__ = "4.0.6"
+__version__ = "4.0.8"
 
 _REQUIRED_VERSIONS = {
     "sentence_transformers": "5.3.0",

package/src/superlocalmemory/cli/commands.py

@@ -282,6 +282,12 @@ def _cmd_gdpr_dispatch(args: Namespace) -> None:
     cmd_gdpr(args)
 
 
+def _cmd_summary_dispatch(args: Namespace) -> None:
+    """V4.0.7: readable session/day/project summaries (issue #113)."""
+    from superlocalmemory.cli.summary_cmd import cmd_summary
+    cmd_summary(args)
+
+
 # ---- end SLM v3.6 Optimize dispatch functions ----
 
 
@@ -414,6 +420,7 @@ def dispatch(args: Namespace) -> None:
         "ops": _cmd_ops,
         # V4.0.6: GDPR subject-rights CLI (Art.15/17/20)
         "gdpr": _cmd_gdpr_dispatch,
+        "summary": _cmd_summary_dispatch,
     }
     handler = handlers.get(args.command)
     if handler:
@@ -2215,6 +2222,13 @@ _COMMAND_GROUPS: list[tuple[str, list[tuple[str, str]]]] = [
         ("forget", "Run the decay cycle (preview first)"),
         ("trace", "Recall with a per-channel score breakdown"),
         ("ingest", "Ingest external observations / documents"),
+        ("summary", "Readable summaries: session, day, or project"),
+    ]),
+    ("Privacy & compliance", [
+        # gdpr shipped in 4.0.6 but was never listed here, so `slm help` did not
+        # mention it at all. The drift test caught it; the omission is the thing
+        # that test exists to prevent.
+        ("gdpr", "Subject rights: status, export, erase, verify"),
     ]),
     ("Run SLM (daemon & dashboard)", [
         ("serve", "Start/stop the background daemon"),

package/src/superlocalmemory/cli/main.py

@@ -90,6 +90,9 @@ _NO_DAEMON_COMMANDS = {
     "serve", "restart",
     # V4.0.6: GDPR CLI accesses the DB directly; no daemon required.
     "gdpr",
+    # V4.0.7: summaries read memory.db directly and are extractive by default,
+    # so they need neither the daemon nor a language model.
+    "summary",
 }
 
 
@@ -968,6 +971,12 @@ def main() -> None:
         _sp.add_argument("--json", action="store_true",
                          help="Output structured JSON (agent-native)")
 
+    # V4.0.7: the readable summary layer from issue #113. The generators shipped
+    # in 4.0.6 with no caller; this is the surface that makes them reachable.
+    from superlocalmemory.cli.summary_cmd import register_summary_parser
+
+    register_summary_parser(sub)
+
     # Wave-3 / V4.0.6: GDPR subject-rights CLI (Art.15/17/20)
     gdpr_p = sub.add_parser(
         "gdpr",