superlocalmemory 3.7.8 → 3.8.1

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

@@ -0,0 +1,148 @@
+---
+name: slm-profile
+description: Workspace isolation and runtime profile switching for SuperLocalMemory. Each profile is a fully independent memory namespace — separate facts, code graphs, and tool sets. Use switch_profile (MCP, requires code/full/power profile) to change the active workspace without restarting. Check the active profile with slm status. Required when working across multiple projects, clients, or tenants.
+when_to_use: |
+  - "Switch to my work profile"
+  - "Use the code profile for this session"
+  - "What profile am I currently in?"
+  - "I need mesh tools — switch to full profile"
+  - "Load the devops workspace"
+  - Multi-project workflows needing memory isolation
+  - Switching between personal and team workspaces
+  - Enabling additional MCP tools by activating a richer profile
+allowed-tools: switch_profile, Bash
+---
+
+# slm-profile — Workspace Isolation and Profile Switching
+
+A profile is a fully isolated memory workspace. Each profile has its own:
+- Memory facts (nothing bleeds across profiles by default)
+- Code graph index (separate per repo/project)
+- Active MCP tool set (determined by profile tier)
+- Retention policy and decay settings
+
+Profiles are the right tool when you have genuinely separate contexts: a personal
+project, a client engagement, a production vs staging environment.
+
+---
+
+## Available profiles and their tool sets
+
+| Profile | Tools | When to use |
+|---------|-------|-------------|
+| `core` | 14 tools — remember, recall, search, session, optimize | Minimal footprint, no code tools |
+| `code` | 24 tools — core + 6 code-graph tools + switch_profile + 3 bounded-loop tools | Default for IDE/coding agents |
+| `full` | 42 tools — code + all memory ops + mesh + bounded loops | Multi-session, team workflows |
+| `power` | 54 tools — full + governance + behavioral tools | Enterprise, admin, audit use cases |
+| `mesh` | 8 tools — mesh coordination only | Lightweight cross-session signalling |
+
+The profile is set at MCP server startup via `SLM_MCP_PROFILE` in the MCP config.
+`switch_profile` lets you change it at runtime without a restart.
+
+---
+
+## Checking the active profile
+
+```bash
+slm status --json
+```
+
+The `profile` field in the output is the currently active profile name.
+
+Or via MCP (works in any profile):
+
+```bash
+slm status
+```
+
+---
+
+## Switching profiles at runtime (v3.8.0+)
+
+`switch_profile` is available in `code`, `full`, and `power` profiles.
+
+```
+switch_profile(
+  profile: str,   # one of: "core", "code", "full", "power", "mesh"
+)
+```
+
+### Example: activate full profile to access mesh tools
+
+```
+# You started in code profile but need mesh coordination
+switch_profile(profile="full")
+
+# Now mesh_peers, mesh_send, mesh_inbox, etc. are available
+mesh_peers()
+```
+
+### Example: switch workspaces
+
+```
+# Switch from personal to work workspace
+switch_profile(profile="work-project")
+```
+
+Wait — profile names and workspace names are distinct concepts:
+- **Profile tier** (`core`, `code`, `full`, `power`, `mesh`) controls which MCP
+  tools are registered.
+- **Workspace / data directory** (`SLM_DATA_DIR`) controls which memory database
+  is used.
+
+`switch_profile` changes the **tool tier** within the current workspace. To
+switch to a completely different memory database (workspace), you need to change
+`SLM_DATA_DIR` — this requires restarting the MCP server or using a separately
+configured MCP server instance.
+
+---
+
+## Configuring the initial profile
+
+In your `.mcp.json` (Claude Code) or `.codex/config.toml` (Codex):
+
+```json
+"env": {
+  "SLM_MCP_PROFILE": "code",
+  "SLM_DATA_DIR": "~/.superlocalmemory"
+}
+```
+
+Profile aliases from older versions still resolve: `code20` → `code`,
+`full38` → `full`, `power50` → `power`. Stale configs get a startup warning
+but continue to work.
+
+---
+
+## Profile isolation guarantees
+
+- `recall` returns only memories in the active profile (plus opt-in shared/global
+  facts — see `slm-scope`).
+- `remember` writes to the active profile only unless `scope="shared"/"global"`.
+- Code graph tools (`build_code_graph`, `get_blast_radius`, etc.) index into the
+  active profile's graph store.
+- KV cache entries are namespaced per profile — switching profiles gives you a
+  clean cache.
+
+---
+
+## Multiple concurrent profiles
+
+You can run multiple SLM MCP server instances simultaneously, each pointed at a
+different `SLM_DATA_DIR`, to serve different workspaces in the same IDE session.
+Name them differently in your MCP config (e.g. `superlocalmemory-personal` and
+`superlocalmemory-work`) and route tool calls to the appropriate server.
+
+---
+
+## Related skills
+
+- `slm-scope` — opt-in fact sharing across profiles (personal/shared/global)
+- `slm-graph` — code-graph tools available in code/full/power profiles
+- `slm-mesh` — mesh tools available in full/power/mesh profiles
+- `slm-status` — check active profile name and tool inventory
+- `slm-governance` — enterprise role-based access to profiles
+
+---
+
+*SuperLocalMemory v3.8.1 · Qualixar · AGPL-3.0-or-later*

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

@@ -50,7 +50,7 @@ recall(
   query="authentication strategy decision",
   limit=20,            # default 20; reduce to 5 for quick pre-task checks
   session_id="<sid>",  # pass the session_id returned by session_init
-  fast=False,          # default False; True skips SpreadingActivation channel
+  fast=False,          # default False; True enables faster, reduced-channel retrieval
 )
 ```
 
@@ -101,8 +101,8 @@ correctly, but feedback is not attributed to the session.
 ### 3. Fast mode
 
 Use `fast=True` for pre-tool-call checks where sub-second response matters.
-This skips the SpreadingActivation channel. The remaining channels — semantic,
-lexical, temporal, and structural — still run.
+This enables a faster, reduced-channel mode. Core semantic and keyword channels
+always run; additional graph and contextual channels are skipped.
 
 ```
 recall(query="rate limiting approach", limit=5, session_id="<sid>", fast=True)
@@ -142,12 +142,12 @@ once you have the `fact_id` for full content.
 
 ## How multi-channel retrieval works
 
-`recall` runs five candidate producers in parallel — semantic vector similarity,
-lexical BM25, temporal recency, spreading activation, and Hopfield — then fuses
-them with Reciprocal Rank Fusion (RRF), applies a reranker, and layers an
-optional entity-graph post-fusion score enhancement. The `channel_weights` field in the
-response shows how each channel contributed for that query. Weights adapt over
-time based on engagement signals attributed via `session_id`.
+`recall` runs multiple candidate producers in parallel — semantic vector similarity,
+keyword matching, temporal recency weighting, and contextual graph channels — then
+fuses and reranks the combined results, with an optional entity-graph score
+enhancement. The `channel_weights` field in the response shows how each channel
+contributed for that query. Weights adapt over time based on engagement signals
+attributed via `session_id`.
 
 To inspect per-channel scores for a real query against your own data:
 
@@ -202,4 +202,40 @@ trusts that what you surface came from the store.
 
 ---
 
-*SuperLocalMemory v3.6.18 · Qualixar · AGPL-3.0-or-later*
+## Multi-scope retrieval (v3.6.15+, opt-in)
+
+By default `recall` returns only memories in the active profile (personal scope).
+To also surface memories shared from other profiles, pass the scope flags:
+
+```
+recall(
+  query="...",
+  include_global=True,   # include global-scope memories (visible to all profiles)
+  include_shared=True,   # include shared-scope memories (shared with this profile)
+  session_id="<sid>",
+)
+```
+
+Scope flags are **off by default**. Only enable them when the user explicitly asks
+to see shared or global facts. See `slm-scope` for the full sharing model.
+
+---
+
+## Profile-aware retrieval (v3.8.0+)
+
+`recall` always queries the currently active profile. To query a different
+workspace, use `switch_profile` (requires `code`, `full`, or `power` MCP profile)
+before recalling, then switch back. See `slm-profile` for workspace switching.
+
+---
+
+## Related skills
+
+- `slm-remember` — store the decisions and facts that recall surfaces later
+- `slm-session` — session lifecycle (must call before first recall)
+- `slm-scope` — multi-scope sharing model (personal / shared / global)
+- `slm-profile` — workspace isolation and profile switching
+
+---
+
+*SuperLocalMemory v3.8.1 · Qualixar · AGPL-3.0-or-later*

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

@@ -191,4 +191,51 @@ slm remember "<content>" --scope shared --shared-with alice,bob
 
 ---
 
-*SuperLocalMemory v3.6.18 · Qualixar · AGPL-3.0-or-later*
+## Multi-scope sharing (v3.6.15+, opt-in)
+
+Every `remember` call defaults to `personal` scope — private to the active profile.
+To share a fact with other profiles on the same machine, set the `scope` parameter:
+
+```
+# Share with every profile on this machine
+remember(
+  content="API rate limit is 100 req/min per tenant",
+  tags="api,limits,shared",
+  project="platform",
+  scope="global",      # visible to all profiles
+  session_id="<sid>",
+)
+
+# Share with specific profiles only
+remember(
+  content="Staging DB migration runs Fridays 22:00 UTC",
+  tags="db,ops",
+  scope="shared",
+  shared_with="work-profile,devops-profile",
+  session_id="<sid>",
+)
+```
+
+**Only set scope when the user explicitly asks to share.** The default
+`personal` scope is identical to single-profile SLM. See `slm-scope` for the
+complete sharing model and when to use each scope.
+
+---
+
+## Profile-aware storage (v3.8.0+)
+
+`remember` always stores in the active profile's namespace. To write to a
+different workspace, use `switch_profile` first. See `slm-profile`.
+
+---
+
+## Related skills
+
+- `slm-recall` — retrieve what was remembered
+- `slm-session` — session lifecycle; session_id is required for attribution
+- `slm-scope` — complete guide to personal / shared / global scopes
+- `slm-profile` — workspace isolation and profile switching
+
+---
+
+*SuperLocalMemory v3.8.1 · Qualixar · AGPL-3.0-or-later*

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

@@ -0,0 +1,176 @@
+---
+name: slm-scope
+description: Controls memory visibility across profiles — personal (private, default), shared (selected profiles), or global (all profiles on this machine). Default is always personal. Only change scope when the user explicitly asks to share a memory across workspaces. Works with both remember (write scope) and recall (read scope flags).
+when_to_use: |
+  - "Share this memory with the team profile"
+  - "Store this globally so all my agents can see it"
+  - "Recall anything shared from the work profile"
+  - "Can other agents on this machine see my memories?"
+  - User explicitly asks to cross-profile share a fact or see shared facts
+  - Enterprise setup where multiple profiles collaborate
+allowed-tools: remember, recall, search, list_recent, Bash
+---
+
+# slm-scope — Memory Scope and Sharing Model
+
+SuperLocalMemory is profile-isolated by default. Every profile is a fully
+independent memory namespace. The scope model adds controlled, opt-in sharing
+between profiles on the same machine — it is never active unless you explicitly
+set it.
+
+---
+
+## The Three Scopes
+
+| Scope | Visibility | When to use |
+|-------|-----------|-------------|
+| `personal` | Active profile only | Default — all facts. Never set explicitly. |
+| `shared` | Active profile + `shared_with` profiles | Team handoffs, shared project context |
+| `global` | Every profile on this machine | Machine-wide conventions, org-wide rules |
+
+**The default is always `personal`.** A fact stored without a `scope` argument
+is private to the profile that stored it. Recall without scope flags returns only
+personal facts. This is identical to single-profile SLM.
+
+---
+
+## Opt-in is mandatory
+
+Never set `scope="shared"` or `scope="global"` (or the recall equivalents
+`include_shared`, `include_global`) unless the user explicitly asks you to share
+or read across profiles. This is a hard rule — scope expansion is an action with
+team-wide or machine-wide impact, and it must always be user-initiated.
+
+---
+
+## Writing a shared or global fact
+
+### share with specific profiles
+
+```
+remember(
+  content="API gateway rate limit is 1000 req/min per client",
+  tags="api,limits,ops",
+  project="platform",
+  importance=8,
+  session_id="<sid>",
+  scope="shared",
+  shared_with="devops-profile,backend-profile",
+)
+```
+
+`shared_with` is a comma-separated list of profile IDs that should be able to
+recall this fact. Use `slm status` to see the current profile name — that is the
+`profile_id` to supply.
+
+### share with all profiles on the machine
+
+```
+remember(
+  content="All services must enforce TLS 1.3 minimum",
+  tags="security,tls,global",
+  project="infra",
+  importance=9,
+  session_id="<sid>",
+  scope="global",
+)
+```
+
+`scope="global"` makes the fact visible to every profile on this machine. Use
+this only for machine-wide conventions (security rules, org-wide constraints).
+
+---
+
+## Reading shared or global facts
+
+By default, `recall` returns only the active profile's personal facts. To surface
+shared and global facts, pass the opt-in flags:
+
+```
+recall(
+  query="rate limiting rules",
+  limit=20,
+  include_global=True,   # include global-scope facts
+  include_shared=True,   # include facts shared with this profile
+  session_id="<sid>",
+)
+```
+
+You can opt in to either or both flags independently. Only the active profile's
+permitted shared facts are returned — you cannot read another profile's personal
+facts.
+
+### CLI equivalents
+
+```bash
+# Recall with global facts included
+slm recall "rate limiting rules" --include-global
+
+# Recall with shared facts included
+slm recall "rate limiting rules" --include-shared
+
+# Both
+slm recall "rate limiting rules" --include-global --include-shared
+
+# Store a global fact
+slm remember "TLS 1.3 minimum" --scope global
+
+# Store a shared fact (shared-with is a comma-separated list of profile IDs)
+slm remember "API rate limit 1000/min" --scope shared --shared-with devops,backend
+```
+
+CLI flags verified in source: `--include-global` / `--no-global`, `--include-shared` / `--no-shared`,
+`--scope personal|shared|global`, `--shared-with <profile-ids>`.
+
+---
+
+## Configuring scope defaults
+
+Per-profile defaults live in `mode_a/b/c.json` configuration. To make a profile
+always include global facts without passing flags each time:
+
+```json
+{
+  "recall": {
+    "include_global": true,
+    "include_shared": false
+  }
+}
+```
+
+Changing the default requires editing the profile config directly — this is an
+admin-level operation.
+
+---
+
+## Enterprise governance
+
+In a governed workspace (admin/member/viewer roles), scope expansion may be
+restricted:
+- **Viewers** cannot write `scope="global"` facts — their writes are always `personal`.
+- **Members** can write `scope="shared"` with profiles in their access list.
+- **Admins** can write `scope="global"` unrestricted.
+
+See `slm-governance` for the full enterprise behavior model.
+
+---
+
+## Scope deletion and retention
+
+A `scope="global"` fact deleted by one profile is deleted for all profiles. A
+`scope="shared"` fact is deleted from all profiles that had access to it.
+Use `slm forget "<query>" --dry-run` before any deletion involving shared facts
+to review the impact. See `slm-remember` for the full deletion discipline.
+
+---
+
+## Related skills
+
+- `slm-remember` — full fact storage reference including scope parameters
+- `slm-recall` — full retrieval reference including include_global/include_shared
+- `slm-profile` — what a profile is and how to switch between them
+- `slm-governance` — enterprise role restrictions on scope
+
+---
+
+*SuperLocalMemory v3.8.1 · Qualixar · AGPL-3.0-or-later*

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

@@ -204,4 +204,27 @@ slm doctor [--json]    # preflight check including daemon and embedding worker
 
 ---
 
-*SuperLocalMemory v3.6.18 · Qualixar · AGPL-3.0-or-later*
+## Profile context (v3.8.0+)
+
+`session_init` operates on the currently active profile. If you need to start
+a session on a different workspace, call `switch_profile` (requires `code`,
+`full`, or `power` MCP profile) before `session_init`, then call `session_init`
+for that workspace. See `slm-profile` for workspace switching.
+
+The returned `memories` array reflects facts stored in the active profile only.
+To also surface shared or global facts in the initial context, pass the query
+explicitly and call `recall` with `include_global`/`include_shared` after
+`session_init`. See `slm-scope` for the sharing model.
+
+---
+
+## Related skills
+
+- `slm-recall` — multi-channel retrieval during the session
+- `slm-remember` — store durable facts during the session
+- `slm-profile` — workspace isolation and profile switching
+- `slm-scope` — multi-scope sharing model
+
+---
+
+*SuperLocalMemory v3.8.1 · Qualixar · AGPL-3.0-or-later*

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

@@ -146,4 +146,21 @@ Note: the `slm optimize` subcommands have known pre-existing parse-test failures
 
 ---
 
-SuperLocalMemory v3.6.18 · Qualixar · AGPL-3.0-or-later
+## Profile-aware status (v3.8.0+)
+
+`slm status --json` reports the currently active profile name in the `profile`
+field. Use this to confirm which workspace is active before starting work on a
+multi-profile setup. To switch the active profile, see `slm-profile`.
+
+---
+
+## Related skills
+
+- `slm-session` — session lifecycle (session_init/close_session)
+- `slm-profile` — workspace isolation and profile switching
+- `slm-cache` — KV cache performance metrics
+- `slm-compress` — reversible context compression
+
+---
+
+SuperLocalMemory v3.8.1 · Qualixar · AGPL-3.0-or-later

package/plugin-src/rules/AGENTS.md

@@ -43,6 +43,16 @@ Apply automatically when context pressure builds:
 
 ---
 
+## Bounded loops
+
+When a task has a checkable acceptance condition (tests, schema, lint, reconciliation), run it as a **bounded loop**: iterate until an INDEPENDENT gate passes — never stop because the agent believes it is done. The agent's own "done" claim is advisory only; the gate is the authority.
+
+- Try it: `slm loop demo` (keyless convergence demo, records every lap to SLM).
+- Inspect: `slm loop history` / `slm loop show <run_id>` — each lap is persisted as queryable SLM memory (tag `loop:<name>`), so runs are auditable and resumable.
+- Terminal statuses: `DONE` (gate passed + approved), `HALT` (bound tripped: iterations/no-progress/budget), `PAUSE` (approval pending), `KILLED`, `ERROR`. Report the exact status — never turn HALT/PAUSE/ERROR into success. See slm-loop.
+
+---
+
 ## Session end
 
 Call `close_session(session_id)` when the work in the session is meaningfully complete. This finalises session metadata and allows the next session to find this one via `session_init`.
@@ -71,21 +81,50 @@ When the SLM MCP server is unavailable, use these CLI equivalents:
 
 ## Tool reference (core profile — 14 tools)
 
-| Tool               | Signature (key params)                                                         | Notes                              |
-|--------------------|--------------------------------------------------------------------------------|------------------------------------|
-| `remember`         | `content, tags="", project="", importance=5, session_id="", scope="personal", shared_with=""` | Store atomic fact. `scope` opt-in (personal default) |
-| `recall`           | `query, limit=10, agent_id, session_id="", fast=False, include_global, include_shared`         | Multi-channel retrieval. Scope flags off by default |
-| `search`           | `query, limit=10, profile_id=""`                                               | FTS5 BM25 keyword search           |
-| `fetch`            | `url, ...`                                                                     | Fetch remote content               |
-| `list_recent`      | `limit=20, profile_id=""`                                                      | Newest memories first              |
-| `update_memory`    | `fact_id, content, agent_id`                                                   | Correct an existing memory by id   |
-| `forget`           | `profile_id="", dry_run=True`                                                  | Decay cycle; always dry_run first  |
-| `session_init`     | `project_path="", query="", max_results=10, max_age_days=30`                   | Once per session; loads context    |
-| `close_session`    | `session_id=""`                                                                | Finalise session                   |
-| `slm_compress`     | `content, mode="auto", reversible=True, ttl_seconds=86400`                     | Returns compressed, lossy, ccr_id  |
-| `slm_retrieve`     | `ccr_id`                                                                       | Retrieve original from ccr_id      |
-| `slm_cache_set`    | `key, value, ttl_seconds=86400`                                                | KV cache set                       |
-| `slm_cache_get`    | `key`                                                                          | KV cache get; returns hit, value   |
-| `slm_optimize_stats` | `()`                                                                         | Returns compress_runs, tokens_saved_compress, cache_kv_hits |
-
-SuperLocalMemory v3.6.18 · Qualixar · AGPL-3.0-or-later
+> The MCP config ships `SLM_MCP_PROFILE=code` (24 tools): the 14 core memory tools below
+> **plus** 6 code-graph tools (`build_code_graph`, `get_blast_radius`, `query_graph`,
+> `semantic_search_code`, `get_review_context`, `detect_changes`) and `switch_profile`.
+> Use `full` (42 tools) to add mesh coordination. Use `power` (54 tools) for governance
+> and audit tools. See slm-profile for profile switching.
+
+| Tool               | Signature (key params)                                                                       | Notes                                  |
+|--------------------|----------------------------------------------------------------------------------------------|----------------------------------------|
+| `remember`         | `content, tags="", project="", importance=5, session_id="", scope="personal", shared_with=""` | Store atomic fact. `scope` opt-in (personal default). See slm-scope. |
+| `recall`           | `query, limit=10, agent_id, session_id="", fast=False, include_global, include_shared`       | Multi-channel retrieval. Scope flags off by default. See slm-scope. |
+| `search`           | `query, limit=10, profile_id=""`                                                             | FTS5 BM25 keyword search               |
+| `fetch`            | `url, ...`                                                                                   | Fetch remote content                   |
+| `list_recent`      | `limit=20, profile_id=""`                                                                    | Newest memories first                  |
+| `update_memory`    | `fact_id, content, agent_id`                                                                 | Correct an existing memory by id       |
+| `forget`           | `profile_id="", dry_run=True`                                                                | Decay cycle; always dry_run first      |
+| `session_init`     | `project_path="", query="", max_results=10, max_age_days=30`                                 | Once per session; loads context        |
+| `close_session`    | `session_id=""`                                                                              | Finalise session                       |
+| `slm_compress`     | `content, mode="auto", reversible=True, ttl_seconds=86400`                                   | Returns compressed, lossy, ccr_id      |
+| `slm_retrieve`     | `ccr_id`                                                                                     | Retrieve original from ccr_id          |
+| `slm_cache_set`    | `key, value, ttl_seconds=86400`                                                              | KV cache set                           |
+| `slm_cache_get`    | `key`                                                                                        | KV cache get; returns hit, value       |
+| `slm_optimize_stats` | `()`                                                                                       | Returns compress_runs, tokens_saved_compress, cache_kv_hits |
+
+## Skills
+
+| Skill | Purpose |
+|-------|---------|
+| slm-recall | Multi-channel memory retrieval |
+| slm-remember | Store durable facts and decisions |
+| slm-session | Session lifecycle (init + close) |
+| slm-status | Health check, optimize stats |
+| slm-cache | KV cache for repeated reads |
+| slm-compress | Reversible context compression |
+| slm-graph | Code graph: blast radius, callers, search (code profile) |
+| slm-loop | Bounded, gate-verified agent loops with an SLM-backed ledger |
+| slm-scope | Personal / shared / global memory scoping |
+| slm-profile | Workspace isolation and profile switching |
+| slm-governance | Enterprise roles, retention, audit, GDPR |
+| slm-mesh | Cross-session peer coordination (full/mesh profile) |
+
+## Subagents
+
+- **slm-memory-advisor** — memory decisions, session hygiene, scope and profile guidance
+- **slm-optimize-advisor** — context compression and KV cache
+- **slm-governance-advisor** — scope/role compliance, retention policies, GDPR
+
+SuperLocalMemory v3.8.1 · Qualixar · AGPL-3.0-or-later

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

@@ -137,4 +137,12 @@ These subcommands control daemon-level cache settings. They do not read or write
 
 ---
 
-SuperLocalMemory v3.6.18 · Qualixar · AGPL-3.0-or-later
+## Related skills
+
+- `slm-compress` — for large content reduction; cache and compress work together
+- `slm-status` — view `cache_kv_hits`/`cache_kv_misses` counters from `slm_optimize_stats`
+- `slm-profile` — cache entries are namespaced per profile; switching profiles gives a fresh cache namespace
+
+---
+
+SuperLocalMemory v3.8.1 · Qualixar · AGPL-3.0-or-later

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

@@ -140,4 +140,11 @@ Content over 1 MB (1 000 000 bytes UTF-8) is processed but `reversible` is force
 
 ---
 
-SuperLocalMemory v3.6.18 · Qualixar · AGPL-3.0-or-later
+## Related skills
+
+- `slm-cache` — for repeated reads; use cache-aside before compressing a frequently re-read result
+- `slm-status` — check `tokens_saved_compress` and `compress_runs` from `slm_optimize_stats`
+
+---
+
+SuperLocalMemory v3.8.1 · Qualixar · AGPL-3.0-or-later

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

@@ -285,7 +285,8 @@ If `build_code_graph` returns `files_parsed: 0`, no supported source files were
 
 ## Profile Requirement
 
-This skill uses graph tools that are only active under the `code` MCP profile. Your plugin `.mcp.json` must include:
+This skill uses graph tools that are only active under the `code` MCP profile
+(or `full` / `power`). Your plugin `.mcp.json` must include:
 
 ```json
 "env": {
@@ -293,8 +294,21 @@ This skill uses graph tools that are only active under the `code` MCP profile. Y
 }
 ```
 
-Without this, the six graph tools are not registered and will appear as unknown tools. Run `slm status` to confirm the active profile.
+Without this, the six graph tools are not registered and will appear as unknown
+tools. Run `slm status` to confirm the active profile.
+
+**Switching profiles at runtime (v3.8.0+):** Use `switch_profile("code")` via
+MCP to activate the code profile in a session that started with a different
+profile. See `slm-profile` for the full profile switching workflow.
+
+---
+
+## Related skills
+
+- `slm-profile` — workspace isolation and profile switching (required for code tools)
+- `slm-recall` — retrieve architectural decisions before graph queries
+- `slm-status` — confirm the active profile and graph index health
 
 ---
 
-SuperLocalMemory v3.6.18 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v3.8.1 · Qualixar · AGPL-3.0-or-later