superlocalmemory 4.0.10 → 4.1.2

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

@@ -103,8 +103,10 @@ remember(
   project: str = "",  # project scope, e.g. "superlocalmemory"
   importance: int = 5,# 1–10; see scale below
   session_id: str = "",# from session_init; attributes the write to this session
+  session_date: str = "",# when the memory is ABOUT, if not today
   scope: str = None,   # v3.6.15 multi-scope: "personal" (default) | "shared" | "global"
   shared_with: str = "",# comma-separated profile_ids for scope="shared"
+  idempotency_key: str = "",# replaying the same key will not store a second copy
 )
 ```
 
@@ -121,14 +123,44 @@ remember(
 
 Use 7–10 only for facts that would cause real damage if forgotten.
 
-### 4. One fact per call
+### 4. Date a memory to when it happened
+
+`session_date` says **when the memory is about**, as distinct from when you
+wrote it. Omit it and the memory is dated today.
+
+```
+remember(
+  content="The outage on the payments queue was caused by a stale DNS entry",
+  tags="incident,payments,postmortem",
+  project="platform",
+  session_date="2026-08-14",       # YYYY-MM-DD, or a full ISO 8601 timestamp
+  session_id="<sid>",
+)
+```
+
+Use it whenever you are writing something down after the fact — a postmortem, a
+decision taken in a meeting last week, a migration that ran on a known date.
+Time-filtered recall (`window="7d"`, `window="2026-07-01..2026-07-31"`) reads
+event time, so a mis-dated memory is one a time-scoped question cannot find.
+
+`session_date` does not change what **kind** of memory it is. A memory that
+describes something planned — "the migration is scheduled for Tuesday", "the
+certificate expires on 2026-09-01" — is stored as a **prospective** memory, and
+recall reports it as `"fact_type": "prospective"`. That is inferred from how the
+content reads, not from the date you pass. Stores written before 4.1.0 spelled
+this type `"temporal"`; that value still reads correctly and needs nothing from
+you.
+
+---
+
+### 5. One fact per call
 
 Store one atomic fact per `remember` call. Do not concatenate multiple unrelated
 points into a single content string — they will be hard to update individually
 and harder to retrieve cleanly. If you have three separate decisions, make three
 calls.
 
-### 5. Always set tags and project
+### 6. Always set tags and project
 
 Untagged, unscoped facts are harder to retrieve and harder to manage. Minimum:
 set `tags` to one or two relevant terms and `project` to the repo/product name.
@@ -238,4 +270,4 @@ different workspace, use `switch_profile` first. See `slm-profile`.
 
 ---
 
-*SuperLocalMemory v4.0.4 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.1.2 · Qualixar · AGPL-3.0-or-later*

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

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

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

@@ -121,7 +121,14 @@ remember(content="...", session_id=session_id, tags="auth,decision", project="my
 ```
 
 This attribution is what allows the ranker to learn which recalls led to useful
-outcomes for this project.
+outcomes for this project. It also gives the session a small working set, so
+successive recalls in one conversation build on what the earlier ones surfaced
+instead of each starting cold.
+
+**Do not synthesise a session id.** An id beginning `http:`, `mcp:`, `cli:` or
+`probe:` is read as a synthetic per-request label rather than a conversation and
+is deliberately excluded from that working set. Use the one `session_init`
+returned, unchanged, for the whole session.
 
 ---
 
@@ -177,6 +184,23 @@ never attributed to a project or agent. Over many sessions this compounds:
 projects where lifecycle is respected have measurably better retrieval quality
 than projects where session_init is skipped.
 
+Within a single session it compounds faster. The session's working set holds the
+memories its recalls have already surfaced, and later recalls rank those higher,
+so a long conversation converges on the material it is actually about.
+
+### Closing the loop explicitly
+
+Engagement signals say a memory was *shown*. `report_outcome` says it was
+*right*:
+
+```
+report_outcome(memory_ids="<ids you actually used>", outcome="success")
+```
+
+Send it when a recalled memory changed what you did, and send `failure` when a
+confidently-returned memory turned out to be wrong — that is the only signal
+that stops a stale memory from being promoted. See the `slm-recall` skill.
+
 ---
 
 ## CLI fallback (when MCP is unavailable)
@@ -198,7 +222,9 @@ slm doctor [--json]    # preflight check including daemon and embedding worker
 | Mistake | Consequence | Fix |
 |---------|-------------|-----|
 | Calling `session_init` twice in one session | Two session IDs; signals split across them | Call once; store the returned ID |
-| Omitting `session_id` from `recall` / `remember` | No learning attribution | Always pass the stored `session_id` |
+| Omitting `session_id` from `recall` / `remember` | No learning attribution, and every turn starts cold | Always pass the stored `session_id` |
+| Inventing a `session_id` such as `mcp:agent` or `http:1234` | Read as synthetic, excluded from the working set | Use the id `session_init` returned |
+| Never reporting an outcome | Ranking cannot tell a useful memory from a merely returned one | `report_outcome` after a recall that changed what you did |
 | Never calling `close_session` | Temporal summaries not written | Call at end of each meaningful work unit |
 | Calling `close_session` without a `session_id` when no prior writes exist | Returns error "No session_id found" | Pass the explicit `session_id` from `session_init` |
 
@@ -227,4 +253,4 @@ explicitly and call `recall` with `include_global`/`include_shared` after
 
 ---
 
-*SuperLocalMemory v4.0.4 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.1.2 · Qualixar · AGPL-3.0-or-later*

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

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

package/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "superlocalmemory"
-version = "4.0.10"
+version = "4.1.2"
 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.10"
+__version__ = "4.1.2"
 
 _REQUIRED_VERSIONS = {
     "sentence_transformers": "5.3.0",