indelible-mcp 5.8.5 → 5.8.7

package/AI_OPERATORS_HANDBOOK.md

@@ -774,6 +774,35 @@ protected; `indelible-mcp strongbox run` protects the current session now (it ne
 than one transcript matches, pass `--session <id>`). It is local-only and free — the chain save is the
 provable record, the strongbox is the raw material.
 
+**Disk, and the duplicate-copy defect fixed in 5.8.5.** Every version up to and including 5.8.3 wrote a
+fresh copy each time the host rotated the session id, so a machine that has been running a while can be
+holding many duplicates of the same few conversations — anywhere from tens of megabytes up to gigabytes
+on a heavily-used machine, accumulating in bursts rather than steadily, with nothing surfacing it.
+⚠️ **We do not have a typical-customer number, so do not quote a magnitude as if it were theirs** —
+the two measured piles were 2 GB and 276 GB and both were builder machines. Report what
+`strongbox_status` says about THEIR machine and nothing more.
+5.8.5 fixes the writer and reports the number on the next save. To clear what is already
+there: `indelible-mcp strongbox clean` **only looks** and deletes nothing;
+`indelible-mcp strongbox clean --write` acts.
+
+**You have this as tools, not only as a shell command** (5.8.5), which is what makes it reachable from a
+client with no terminal: `strongbox_status` is read-only and safe to call whenever disk comes up;
+`strongbox_consent` records the customer's answer and must be called only after they have actually
+answered; `strongbox_clean` acts, and refuses unless a consent was recorded by that separate, earlier
+call. You cannot grant that permission yourself — recording it is a distinct step from acting on it, on
+purpose, so that a yes cannot be manufactured in the same breath as the deletion.
+
+⚠️ **What makes the deletion safe is the containment proof, not the consent gate.** A copy is removed
+only after being shown byte-for-byte to be an earlier, shorter version of a copy that is kept (transcripts
+only ever grow, so an older snapshot is a literal prefix of a newer one). That check reads every byte;
+there is no sampling. One complete verified copy of every conversation always survives, and if any file in
+a group cannot be proven redundant the whole group is left alone rather than partly cleaned.
+
+⚠️ **A client reads the tool list once, when it starts.** After a customer upgrades, the server process
+already running is still the old code, so the strongbox tools will not appear until their assistant is
+restarted. If someone says they just updated and you cannot see `strongbox_status`, that is the reason:
+tell them to quit and reopen their assistant. Do not tell them the feature is missing.
+
 Auto-save is your seatbelt. The daily MD is your actually-arriving-somewhere.
 
 ## 10.2 Bank at milestones, not at the end

package/CLI_HANDBOOK.md

@@ -430,6 +430,11 @@ you say yes. (That works through three tools: `strongbox_status` looks, `strongb
 records your answer, and `strongbox_clean` acts. Your assistant cannot grant your permission for
 you — recording it is a separate step from doing it, on purpose.)
 
+⚠️ **Just upgraded? Restart your assistant before you ask.** Every MCP client reads the list of
+available tools once, when it starts. If you updated Indelible while it was running, it is still
+holding the old list and will tell you the cleanup does not exist. Quit and reopen whatever app you
+run Indelible in — Claude Desktop, Claude Code, Cursor, or any other MCP client — and ask again.
+
 **What "safe" means here, exactly, because it is a deletion.** A copy is removed only if it has
 been proven byte-for-byte to be an earlier, shorter version of a copy that is kept — transcripts
 only ever grow, so an older snapshot is a literal prefix of a newer one. That check reads every

package/CUSTOMER_AGENT_HANDBOOK.md

@@ -63,6 +63,14 @@ removed.) This is what each one does and why it is there.
 
 **PreCompact (strongbox)** and **SessionEnd (strongbox)** keep a verified, byte-exact local copy of your raw transcript in `~/.indelible/transcript-vault/` before your host's own cleanup (~30 days by default) can delete it. That is the strongbox: your transcript's local vault, separate from the chain save — free, local, no wallet needed. `indelible-mcp strongbox` shows what it holds; `indelible-mcp strongbox run` protects the current session on demand.
 
+**A bug that was filling your drive, and how to clear it.** Every version up to and including 5.8.3 saved a fresh copy of a conversation each time your session id rotated, which happens more often than you would think. It builds up in bursts rather than steadily, so a machine that has been running a while can be holding a great many copies of the same few conversations — anything from tens of megabytes to several gigabytes, with nothing telling you. That is fixed now, and after you update, the next time you save, Indelible tells you what your own machine is holding.
+
+**To clear what is already there, just ask.** Say to your assistant: "clean up my Strongbox." It will show you exactly what is safe to remove first, and nothing is deleted until you say yes. You do not need a terminal for this. (It works through three tools: one looks, one records your answer, one acts — and the one that acts refuses unless your answer was recorded by the separate earlier step. Your assistant cannot give your permission on your behalf, on purpose.) If you would rather do it yourself, `indelible-mcp strongbox clean` only looks and deletes nothing, and `indelible-mcp strongbox clean --write` acts.
+
+**What "safe to remove" means, because this is a deletion.** A copy is removed only after being proven, byte for byte, to be an earlier and shorter version of a copy that is kept. Transcripts only ever grow, so an older snapshot is a literal prefix of a newer one. That check reads every byte; there is no sampling. One complete verified copy of every conversation always survives, and if any file in a group cannot be proven to be a duplicate, that whole group is left alone rather than partly cleaned.
+
+⚠️ **Just updated? Restart your assistant before you ask.** Quit and reopen whatever app you run Indelible in — Claude Desktop, Claude Code, Cursor, or any other MCP client. It reads the list of things it can do once, when it starts, so if you updated while it was running it is still holding the old list and will tell you the cleanup does not exist. Restart, then ask again.
+
 Free tier and the hooks: every hook runs for everyone. Restore, the time card, style loading, and Guardrails are fully free. The pre-compaction **save** is the one piece that needs Pro. On a free wallet the hook still fires, but instead of saving it prints the plain notice that saving is a Pro feature. That is not an error. Your reads, diary, and recall keep working.
 
 Hook installation is idempotent. If you ever suspect the hooks are missing, run:

package/README.md

@@ -15,6 +15,11 @@ npm install -g indelible-mcp
 indelible-mcp
 ```
 
+**Upgrading from an earlier version?** Same command — and then **restart your assistant**: quit and
+reopen whatever app you run Indelible in (Claude Desktop, Claude Code, Cursor, or any other MCP
+client). Every one of them reads the list of available tools once, when it starts, so anything new in
+the release stays invisible until you restart.
+
 ## Setup
 
 ### 1. Install & Connect Your Wallet

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "indelible-mcp",
-  "version": "5.8.5",
+  "version": "5.8.7",
   "description": "Blockchain-backed memory and code storage for Claude Code. Save AI conversations and source code permanently on BSV.",
   "type": "module",
   "main": "src/index.js",

package/src/index.js

@@ -23454,7 +23454,7 @@ init_wall_stub();
 init_wall_stub();
 init_wall_stub();
 var PROJECT_ROOT_FOR_CLONE_CHECK = resolve5(dirname25(fileURLToPath2(import.meta.url)), "../..");
-var INDELIBLE_VERSION = "5.8.5";
+var INDELIBLE_VERSION = "5.8.7";
 var VERSION_CACHE_MS = 24 * 60 * 60 * 1e3;
 var REGISTRY_URL = process.env.INDELIBLE_REGISTRY_URL || "https://registry.npmjs.org";
 var versionCachePath = () => join52(homedir36(), ".indelible", "version-check.json");
@@ -26217,7 +26217,7 @@ Answer THAT message and nothing else \u2014 the wire also carries unrelated conv
 }
 function printHelp() {
   console.log(`
-Indelible MCP \u2014 Blockchain memory for Claude Code (v5.8.5)
+Indelible MCP \u2014 Blockchain memory for Claude Code (v5.8.7)
 
 Setup:
   indelible-mcp                              Set up interactively (recommended \u2014 your key is never written to shell history)