@vib795/agent-memory 0.7.4 → 0.7.5

package/README.md

@@ -440,7 +440,7 @@ equivalent and is not: npm links the global install to that folder rather than c
 it, which shows up as an arrow in `npm list -g`:
 
 ```
-`-- @vib795/agent-memory@0.7.4 -> .\..\..\..\agent-memory
+`-- @vib795/agent-memory@0.7.5 -> .\..\..\..\agent-memory
 ```
 
 Move or delete the clone afterwards and the global install points at nothing — the same

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vib795/agent-memory",
-  "version": "0.7.4",
+  "version": "0.7.5",
   "description": "Durable cross-repo knowledge graph for GitHub Copilot and Claude Code. Markdown source of truth, disposable SQLite index, zero runtime dependencies.",
   "keywords": [
     "github-copilot",

package/skills/handoff/SKILL.md

@@ -26,6 +26,22 @@ Every extra request costs the user credits, which is the reason this skill exist
 
 ---
 
+## Scope
+
+Bare `/handoff`: you decide what the working state is.
+
+`/handoff <focus>` — "just the auth work", "the migration, skip the CI detour" — names
+which thread of a braided conversation to carry forward. Treat it as a filter on Step 2
+and Step 3, not as a title. Work outside that focus stays out of Orientation, Decisions
+and Current task state even when it was the more recent work: a long conversation
+usually holds more than one thread, and carrying both is how a handoff becomes the
+transcript summary this skill exists to avoid.
+
+If the focus names a thread you cannot find in the conversation, say so in one line and
+hand off what you did find. Do not invent a thread to match the words.
+
+---
+
 ## Step 0 — Resolve the store path
 
 | Platform | Store |

package/skills/recall/SKILL.md

@@ -59,6 +59,10 @@ are the router. There is no keyword matching underneath this and there should no
 be: a title is a sentence, and matching sentences to a question is what you do well
 and what a regex does badly.
 
+When the user typed `/recall <topic>`, `<topic>` is the question. Route on it, and carry
+it into Step 5 — a cold `/recall deploy ordering` is someone asking what the store knows
+about deploy ordering, not asking for a tour of the store.
+
 - Pick 1 to 3 ids. More than 3 means the question is really several questions.
 - Always include a `constraint` that touches the subject, even when the user did not
   ask about limits. Constraints are what stop an approach that cannot ship.
@@ -115,7 +119,10 @@ Rules that separate a useful recall from a confident wrong one:
    right now, trust the repository, say which note is wrong, and suggest
    `/remember` to correct it. A store that quietly rots is worse than no store.
 4. **Never present an `inferred` note as established.** The note says which it is.
-5. Answer the question. Do not summarize the store.
+5. **Answer the question.** An explicit `/recall <topic>` is the target whenever one
+   was given, and it wins over a different question already in the conversation —
+   the user narrowed it on purpose. Fall back to the conversation's own question only
+   for a bare `/recall`. Either way, do not summarize the store.
 
 ---
 

package/skills/remember/SKILL.md

@@ -107,6 +107,13 @@ Skip this step only when the user named exactly what to write and it is plainly
 
 ## Step 1 — Select what is durable
 
+When the user typed `/remember <what>`, `<what>` is both a filter and a mandate: select
+only what bears on it, and select that even if you would otherwise have ranked something
+else higher. It does not suspend the durability test below. If the named thing is task
+state, write nothing and say so in one line — `that reads as task state, not durable;
+nothing written`. Writing nothing *silently* after an explicit request is the failure
+that matters here, because the user leaves believing it was captured.
+
 <!-- extraction-rules:start -->
 - A node is durable only if it will still be true next month. Task state is not
   durable and belongs in a handoff file, not in the graph.