@memfork/cli 0.1.34 → 0.1.35

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@memfork/cli",
-  "version": "0.1.34",
+  "version": "0.1.35",
   "description": "MemForks CLI — init, commit, recall, merge, install plugins",
   "repository": {
     "type": "git",

package/plugins/codex/skills/memforks-status/SKILL.md

@@ -22,8 +22,9 @@ memfork ui                        # open the DAG visualizer
 
 ## Commit a decision on-chain
 
-Use this after significant architectural decisions — not for routine facts.
-(Routine facts go through `memwal_remember` via MCP.)
+`memfork commit --facts` calls MemWal internally — **one command indexes the facts
+for semantic recall AND anchors them on-chain.** Prefer this over calling
+`memwal_remember` separately.
 
 ```bash
 memfork commit \
@@ -33,6 +34,9 @@ memfork commit \
 
 The CLI auto-detects the current Git branch; pass `--branch <name>` only to target a different one.
 
+Only use `memwal_remember` directly for a lightweight mid-task note that does not
+warrant an on-chain entry.
+
 ## Merge branches
 
 When two branches need to reconcile their memory:

package/plugins/cursor/rules/memforks.mdc

@@ -29,28 +29,10 @@ memwal_recall(query="auth system design decisions", namespace="branch/<current-b
 
 Results with high relevance scores are verified context from prior sessions.
 
-## Remember — use the MCP tool
+## Remember — prefer the CLI commit
 
-When you learn a durable fact (not ephemeral task state), save it:
-
-```
-memwal_remember(text="<the complete fact>", namespace="branch/<current-branch>")
-```
-
-Only save facts that will be useful in future sessions:
-- Architecture decisions
-- Project conventions and preferences
-- Resolved problems and their solutions
-- Key constraints or non-obvious requirements
-
-Do **not** save: current task state, in-progress work, temporary findings.
-
----
-
-## On-chain commit — use the CLI
-
-After a significant turn where you've committed an architectural decision or resolved
-a non-trivial problem, also anchor it on-chain for immutable versioning:
+`memfork commit --facts` calls MemWal internally, so **one command does both**:
+indexes the facts for semantic recall AND anchors them on-chain.
 
 ```bash
 memfork commit \
@@ -58,20 +40,16 @@ memfork commit \
   --facts "<fact 1>" "<fact 2>"
 ```
 
-The CLI auto-detects the current Git branch, so you do not pass `--branch`
-unless you want to target a different branch.
+The CLI auto-detects the current Git branch — omit `--branch` unless targeting
+a different branch.
 
-This creates a cryptographically verifiable commit on Sui — not just a blob.
-Use it for decisions that matter for audit trail, not routine facts.
+Use this after any significant turn: architectural decisions, resolved problems,
+project conventions, key constraints.
 
----
+Only use `memwal_remember` directly for a quick lightweight note that does **not**
+warrant an on-chain entry (e.g. a transient preference noted mid-task).
 
-## Branch awareness
-
-- The `memfork` CLI auto-detects the current Git branch; pass `--branch` only to override it.
-- The `memwal_*` MCP tools have no Git context, so pass `namespace="branch/<current-branch>"` explicitly.
-- When the user switches branches, recall from the new branch namespace.
-- Use `memfork status` to see the current branch, on-chain tree state, and open merge proposals.
+Do **not** save: current task state, in-progress work, temporary findings.
 
 ---
 
@@ -111,6 +89,15 @@ human governance act.
 
 ---
 
+## Branch awareness
+
+- The `memfork` CLI auto-detects the current Git branch; pass `--branch` only to override it.
+- The `memwal_*` MCP tools have no Git context, so pass `namespace="branch/<current-branch>"` explicitly.
+- When the user switches branches, recall from the new branch namespace.
+- Use `memfork status` to see the current branch, on-chain tree state, and open merge proposals.
+
+---
+
 ## Suggesting a merge — proactive but not autonomous
 
 You may **suggest** a merge when you notice the current branch has accumulated