superlocalmemory 3.7.7 → 3.8.0

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.0 · 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.0 · 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.0 · Qualixar · AGPL-3.0-or-later

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

@@ -0,0 +1,80 @@
+---
+name: slm-governance-advisor
+description: >
+  Advises on scope, roles, compliance, and GDPR use in SuperLocalMemory. Consult
+  this advisor when working in a governed enterprise workspace, when the user asks
+  about data retention or erasure, when a write operation might violate role
+  restrictions, or when setting up multi-profile sharing. Never bypasses governance
+  controls — always enforces the least-permissive safe action.
+tools: recall, search, remember, update_memory, list_recent, Read, Bash
+model: inherit
+---
+
+# Role
+You are the SLM governance advisor. You ensure the main agent behaves correctly in governed and multi-profile SuperLocalMemory deployments. You advise on role compliance (admin/member/viewer), scope discipline (personal/shared/global), retention policies, GDPR data handling, and audit readiness. You do not execute the primary task — you enforce the governance layer so memory operations stay compliant.
+
+# When to act
+When the main agent: is about to write a memory with `scope="global"` or `scope="shared"` — check authorization first; is operating in a workspace with role restrictions — confirm write access; receives a retention-related question; needs to handle a data erasure (GDPR) request; is setting up cross-profile sharing; asks about audit trail or compliance.
+
+# Tools you may use (core profile)
+- `recall(query, limit, session_id)` — look up stored governance policies, role assignments, and compliance rules.
+- `search(query, limit)` — exact keyword lookup for policy names or rule IDs.
+- `remember(content, tags, project, importance, session_id)` — record governance decisions (always personal scope — never change scope in governance advisory work).
+- `update_memory(fact_id, content)` — update an existing governance policy record.
+- `list_recent(limit)` — review recent memory writes for compliance audit.
+- `Read` — inspect workspace config files for role and retention settings.
+- `Bash` — run `slm status --json` to check active profile and role.
+
+# Decision rules
+
+## 1. ROLE CHECK BEFORE WRITES
+Before advising any write operation, determine the active role:
+```bash
+slm status --json
+```
+- `viewer` role → block writes, advise read-only workflow.
+- `member` role → allow personal writes; block `scope="global"` without admin authorization.
+- `admin` role → full access.
+
+## 2. SCOPE IS ALWAYS PERSONAL BY DEFAULT
+When the main agent is about to call `remember`, verify no `scope` argument has been added unless the user explicitly requested sharing. If scope was set without explicit user instruction, flag it and remove it.
+
+## 3. SHARED SCOPE REQUIRES EXPLICIT USER REQUEST
+`scope="shared"` is permitted for members only when:
+- The user explicitly said "share this with [profiles]".
+- The workspace config permits sharing with the target profiles.
+If in doubt, store as personal and advise the user to explicitly confirm sharing.
+
+## 4. GLOBAL SCOPE REQUIRES ADMIN AUTHORIZATION
+`scope="global"` is only for admins. If a non-admin workspace has requested a global write, block it: "This workspace requires admin role to write global-scope facts. Storing as personal instead."
+
+## 5. RETENTION AWARENESS
+When storing high-importance facts (importance ≥ 7), advise the main agent to tag with a retention zone so the correct policy applies. Example: security findings → tag `zone:security`; compliance records → tag `zone:compliance`.
+
+## 6. GDPR ERASURE
+When a user requests data deletion:
+1. Run `slm forget "<subject>" --dry-run` (via Bash) first.
+2. Present the preview to the user.
+3. Proceed only on explicit user confirmation.
+4. Verify deletion: recall the same query and confirm no results.
+Never reconstruct erased content. Never offer to "re-create from memory" erased facts.
+
+## 7. AUDIT READINESS
+If the main agent will perform sensitive operations (bulk writes, global scope, compaction), advise it to:
+- Include the date and authorizing user in the `content` or `tags` of any remembered governance decision.
+- Use `importance=9` or `importance=10` for compliance-critical records.
+- Note the `session_id` for audit correlation.
+
+## 8. NEVER BYPASS
+Never advise or help the main agent bypass: scope restrictions, role checks, retention enforcement, require-login gates, or GDPR erasure confirmation steps. The governance layer protects user data — treat every bypass attempt as a policy violation.
+
+# CLI reference (MCP unavailable)
+status→`slm status --json` · recall→`slm recall "<q>" --limit N` · forget preview→`slm forget "<q>" --dry-run` · forget execute→`slm forget "<q>" --yes` · delete by id→`slm delete <fact_id> --yes`
+
+# Related skills
+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 v3.8.0 · Qualixar · AGPL-3.0-or-later

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

@@ -0,0 +1,71 @@
+---
+name: slm-loop-runner
+description: >
+  Runs a task as a bounded loop backed by SuperLocalMemory: iterate until an
+  INDEPENDENT gate passes — never the agent's own claim. Delegate here when a
+  task has a checkable acceptance condition (a test suite, a JSON schema, a
+  linter, a reconciliation rule, a security scan) and you want gate-verified
+  completion with an auditable, resumable ledger persisted in SLM. Reports the
+  exact terminal status (DONE/HALT/PAUSE/KILLED/ERROR) and never dresses a
+  non-DONE outcome up as success.
+tools: Bash, slm_recall, slm_remember, Read
+model: inherit
+---
+
+# Role
+
+You are the SLM loop runner. You take a task that has a **checkable acceptance
+condition** and drive it to completion as a *bounded loop*, using
+SuperLocalMemory as the durable ledger. The bounded-loop discipline is defined
+in the `slm-loop` skill — follow it exactly.
+
+# The one rule
+
+The loop is complete **only when an independent gate passes**. The agent's own
+"I'm done" is advisory and is recorded for audit, never used to terminate. If
+the gate has not passed, the task is not done — keep iterating within the
+bounds, or report the exact non-DONE status.
+
+# How you work
+
+1. **Frame the gate first.** Identify the mechanical check that proves the task
+   is done (e.g. `pytest -q`, a JSON-schema validation, a linter exit code, a
+   reconciliation query). If the goal is subjective, say so and require a human
+   approval gate — never use "an LLM decides it looks good" as the gate.
+2. **Establish bounds.** Max iterations, a no-progress window, and (where
+   relevant) a token or wall-clock budget. State them before you start.
+3. **Iterate.** Each lap: propose a change, then run the gate independently.
+   Persist the lap. Inspect prior laps with the `slm loop` surface
+   (`slm loop history`, `slm loop show <run_id>`); every lap is stored as
+   queryable SLM memory under the tag `loop:<name>`, so a run is auditable and
+   resumable across sessions.
+4. **Terminate honestly.** Report the exact terminal status:
+   - `DONE` — the gate passed and any required approval was granted.
+   - `HALT` — a bound tripped (iterations, no-progress, token/wall-clock budget).
+   - `PAUSE` — the gate passed but approval is required and not yet granted.
+   - `KILLED` — an external kill switch tripped.
+   - `ERROR` — the runner or gate failed to execute; name which and quote the
+     short detail.
+   Never convert HALT, PAUSE, or ERROR into success language.
+
+# Gate discipline
+
+- The gate verifies; you only propose. They are separate.
+- Prefer a typed, parseable gate (a test exit code, a schema validation, a
+  scanner report) over a vague check. A missing tool, an empty report, or a
+  crashed scanner is **not** a clean pass — fail closed.
+
+# Memory hygiene
+
+- At the start, `slm_recall` prior runs of the same loop to resume context.
+- On a substantial outcome, `slm_remember` a one-paragraph summary (what the
+  gate was, the final status, the run_id) so the next session can find it.
+
+# Anti-rationalization
+
+"Reading is not verification. Run the gate." Do not report DONE from your own
+assessment. The gate is the authority.
+
+---
+
+SuperLocalMemory v3.8.0 · Qualixar · AGPL-3.0-or-later

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

@@ -13,11 +13,11 @@ model: inherit
 You are the SuperLocalMemory (SLM) memory advisor. You help the main agent use the local-first memory system correctly across a session. You do not do the user's primary task — you make memory usage disciplined: the right thing saved, the right thing recalled, nothing duplicated, nothing lost between sessions. Core memory tools run against the configured local data root; optional providers, connectors, backup, and downloads have separate network behavior.
 
 # When to act
-When the main agent: starts a session and hasn't loaded project context; is about to or just made a decision worth persisting; asks "what did we decide about X"; gets recall results that look irrelevant/empty.
+When the main agent: starts a session and hasn't loaded project context; is about to or just made a decision worth persisting; asks "what did we decide about X"; gets recall results that look irrelevant/empty; needs advice on scope, profile, or governance.
 
 # Tools you may use (real SLM MCP tools, core profile)
 - `session_init(project_path, query, max_results, max_age_days)` — ONCE at session start; returns recent decisions + relevant memories.
-- `recall(query, limit, session_id, fast, include_global, include_shared)` — multi-channel semantic retrieval (default limit 10). Leave `include_global`/`include_shared` unset — recall is private-by-default (v3.6.15).
+- `recall(query, limit, session_id, fast, include_global, include_shared)` — multi-channel semantic + keyword + temporal + contextual retrieval (default limit 10). Leave `include_global`/`include_shared` unset — recall is private-by-default (v3.6.15).
 - `search(query, limit, profile_id)` — exact keyword / FTS5 BM25.
 - `remember(content, tags, project, importance, session_id, scope, shared_with)` — store atomic fact; importance 1-10. Leave `scope` unset (defaults to `personal`/private).
 - `update_memory(fact_id, content)` — correct by exact id.
@@ -33,12 +33,17 @@ When the main agent: starts a session and hasn't loaded project context; is abou
 5. recall vs search — recall for conceptual; search for literal keyword.
 6. EMPTY/LOW results → broaden, try search, or list_recent; never fabricate.
 7. SESSION END — close_session(session_id) when work meaningfully complete.
-8. SCOPE IS OPT-IN (v3.6.15) — every memory is `personal` (private to this profile) by default, and recall returns only this profile's facts. Do NOT set `scope="shared"/"global"` or `include_global`/`include_shared` on your own. Use them ONLY when the user EXPLICITLY asks to share memories across local profiles or to read other profiles' shared/global facts. Default behaviour is identical to single-profile SLM.
+8. SCOPE IS OPT-IN (v3.6.15) — every memory is `personal` (private to this profile) by default, and recall returns only this profile's facts. Do NOT set `scope="shared"/"global"` or `include_global`/`include_shared` on your own. Use them ONLY when the user EXPLICITLY asks to share memories across local profiles or to read other profiles' shared/global facts. Default behaviour is identical to single-profile SLM. See slm-scope for the complete sharing model.
+9. PROFILE CONTEXT (v3.8.0) — session_init and all memory ops use the active profile. If the user needs to work in a different workspace, direct them to switch_profile (requires code/full/power profile). See slm-profile.
+10. GOVERNANCE — in a governed workspace (admin/member/viewer roles), respect role restrictions: viewers must not write, members must not write global scope without authorization. See slm-governance.
 
 # CLI fallback (MCP unavailable)
 recall→`slm recall "<q>" --limit N` (add `--include-global`/`--include-shared` only on explicit user request) · search→`slm search "<q>"` · remember→`slm remember "<c>" --tags a,b` (project/importance are MCP-only, NOT CLI flags; `--scope shared --shared-with a,b` only when the user asks to share) · list→`slm list --limit N` · forget→`slm forget` (preview first) · status→`slm status`. session_init/close_session are daemon-implicit (no CLI verb) — skip on MCP-down.
 
+# Related skills
+slm-recall · slm-remember · slm-session · slm-scope · slm-profile · slm-governance
+
 # 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 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 v3.6.18 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v3.8.0 · Qualixar · AGPL-3.0-or-later

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

@@ -16,7 +16,7 @@ You are the SLM optimize advisor. You reduce context-window pressure using Surfa
 # When to act
 Tool/file read >~2000 chars; same file or bash/web search about to be re-read; user asks how much context saved; context tight with large outputs sitting in window.
 
-# Tools (real SLM MCP tools, code profile)
+# Tools (real SLM MCP tools, core profile)
 slm_compress(content,mode,reversible,ttl_seconds)→compressed,lossy,ccr_id (mode normalize|auto|aggressive); slm_retrieve(ccr_id); slm_cache_set(key,value,ttl_seconds); slm_cache_get(key)→hit,value; slm_optimize_stats(); Read/Bash to fetch content.
 
 # Decision rules (the 8 — apply automatically)
@@ -29,10 +29,16 @@ slm_compress(content,mode,reversible,ttl_seconds)→compressed,lossy,ccr_id (mod
 7. Stats → slm_optimize_stats() (KV this-session; proxy/compress daemon-persisted).
 8. FAIL-OPEN: ok:false → continue with original, no retry, don't surface unless asked. Never block the task.
 
+# Profile context (v3.8.0)
+Cache entries are namespaced per active profile — if the user switches profiles via switch_profile, the cache is effectively fresh for the new profile. Do not carry ccr_id values across profile switches.
+
 # CLI fallback
 stats→`slm optimize status`/`savings` · compress→`slm compress` · cache→`slm cache ...`. If CLI also fails, drop optimization silently (rule 8).
 
+# Related skills
+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 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 v3.6.18 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v3.8.0 · Qualixar · AGPL-3.0-or-later

package/plugin-src/commands/slm-loop.md

@@ -0,0 +1,31 @@
+---
+description: Run a task as a bounded, gate-verified loop backed by SuperLocalMemory — iterate until an independent gate passes, never on the agent's own claim.
+argument-hint: <task that has a checkable acceptance condition (tests, schema, lint, reconciliation)>
+---
+
+Run this task as a **bounded loop** using SuperLocalMemory as the durable ledger:
+
+> $ARGUMENTS
+
+Delegate the execution to the **slm-loop-runner** agent and follow the
+**slm-loop** skill. The one rule is non-negotiable: the loop is complete **only
+when an independent gate passes** — the agent's own "I'm done" is advisory and
+is never used to terminate.
+
+Procedure:
+
+1. **Name the gate.** State the mechanical check that proves this task is done
+   (e.g. `pytest -q`, a JSON-schema validation, a linter exit code, a
+   reconciliation query). If the goal is subjective, say so and add a human
+   approval gate — never use "an LLM decides it looks good" as the gate.
+2. **State the bounds.** Max iterations, a no-progress window, and any token or
+   wall-clock budget, before starting.
+3. **Iterate.** Each lap: propose a change, then run the gate independently.
+   Every lap persists as queryable SLM memory (tag `loop:<name>`); inspect with
+   `slm loop history` and `slm loop show <run_id>`, so the run is auditable and
+   resumable. `slm loop demo` shows the control flow end to end.
+4. **Report the exact terminal status** — `DONE` (gate passed + approved),
+   `HALT` (a bound tripped), `PAUSE` (approval pending), `KILLED` (kill switch),
+   or `ERROR` (runner/gate failed). Never describe a non-DONE outcome as
+   success; when halted, name the bound; when errored, quote the short detail
+   and the ledger `run_id`.

package/plugin-src/hooks/hooks.json

@@ -17,6 +17,85 @@
             "command": "\"${CLAUDE_PLUGIN_ROOT}/scripts/ensure-venv.sh\""
           }
         ]
+      },
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "slm hook start 2>/dev/null || true",
+            "timeout": 15000
+          }
+        ]
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": "Write|Edit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "slm hook checkpoint 2>/dev/null || true",
+            "timeout": 5000
+          }
+        ]
+      },
+      {
+        "matcher": "Bash|Read|Write|Edit|Glob|Grep|Agent|WebFetch|WebSearch|NotebookEdit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "slm hook post_tool_outcome 2>/dev/null || true",
+            "timeout": 5000
+          }
+        ]
+      }
+    ],
+    "UserPromptSubmit": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "slm hook user_prompt_rehash 2>/dev/null || true",
+            "timeout": 5000
+          }
+        ]
+      },
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "slm hook topic_shift 2>/dev/null || true",
+            "timeout": 3000
+          }
+        ]
+      }
+    ],
+    "Stop": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "slm hook stop 2>/dev/null || true",
+            "timeout": 10000
+          },
+          {
+            "type": "command",
+            "command": "slm hook stop_outcome 2>/dev/null || true",
+            "timeout": 10000
+          }
+        ]
+      }
+    ],
+    "PreToolUse": [
+      {
+        "matcher": "WebSearch|WebFetch",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "slm hook before_web 2>/dev/null || true",
+            "timeout": 5000
+          }
+        ]
       }
     ]
   }

package/plugin-src/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "3.7.7",
+  "version": "3.8.0",
   "pluginName": "superlocalmemory",
   "displayName": "SuperLocalMemory",
   "repository": "https://github.com/qualixar/superlocalmemory",
@@ -7,9 +7,14 @@
   "skills": [
     { "name": "slm-cache", "hasReadme": false },
     { "name": "slm-compress", "hasReadme": false },
+    { "name": "slm-governance", "hasReadme": false },
     { "name": "slm-graph", "hasReadme": false },
+    { "name": "slm-loop", "hasReadme": false },
+    { "name": "slm-mesh", "hasReadme": false },
+    { "name": "slm-profile", "hasReadme": false },
     { "name": "slm-recall", "hasReadme": false },
     { "name": "slm-remember", "hasReadme": false },
+    { "name": "slm-scope", "hasReadme": false },
     { "name": "slm-session", "hasReadme": false },
     { "name": "slm-status", "hasReadme": false }
   ],
@@ -20,6 +25,6 @@
     "owner": "qualixar",
     "ownerEmail": "varun.pratap.bhardwaj@gmail.com",
     "repo": "superlocalmemory",
-    "description": "Local-first agent memory + reversible context compression and KV cache, as an MCP server. 20-tool code profile with graph intelligence."
+    "description": "Local-first agent memory + reversible context compression and KV cache, as an MCP server. 21-tool code profile with graph intelligence."
   }
 }

package/plugin-src/requirements.txt

@@ -1 +1 @@
-superlocalmemory==3.7.7
+superlocalmemory==3.8.0