indelible-mcp 5.8.5 → 5.8.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -774,6 +774,31 @@ protected; `indelible-mcp strongbox run` protects the current session now (it ne
774
774
  than one transcript matches, pass `--session <id>`). It is local-only and free — the chain save is the
775
775
  provable record, the strongbox is the raw material.
776
776
 
777
+ **Disk, and the duplicate-copy defect fixed in 5.8.5.** Every version up to and including 5.8.3 wrote a
778
+ fresh copy each time the host rotated the session id, so a machine that has been running a while can be
779
+ holding many duplicates of the same few conversations — gigabytes, accumulating in bursts, with nothing
780
+ surfacing it. 5.8.5 fixes the writer and reports the number on the next save. To clear what is already
781
+ there: `indelible-mcp strongbox clean` **only looks** and deletes nothing;
782
+ `indelible-mcp strongbox clean --write` acts.
783
+
784
+ **You have this as tools, not only as a shell command** (5.8.5), which is what makes it reachable from a
785
+ client with no terminal: `strongbox_status` is read-only and safe to call whenever disk comes up;
786
+ `strongbox_consent` records the customer's answer and must be called only after they have actually
787
+ answered; `strongbox_clean` acts, and refuses unless a consent was recorded by that separate, earlier
788
+ call. You cannot grant that permission yourself — recording it is a distinct step from acting on it, on
789
+ purpose, so that a yes cannot be manufactured in the same breath as the deletion.
790
+
791
+ ⚠️ **What makes the deletion safe is the containment proof, not the consent gate.** A copy is removed
792
+ only after being shown byte-for-byte to be an earlier, shorter version of a copy that is kept (transcripts
793
+ only ever grow, so an older snapshot is a literal prefix of a newer one). That check reads every byte;
794
+ there is no sampling. One complete verified copy of every conversation always survives, and if any file in
795
+ a group cannot be proven redundant the whole group is left alone rather than partly cleaned.
796
+
797
+ ⚠️ **A client reads the tool list once, when it starts.** After a customer upgrades, the server process
798
+ already running is still the old code, so the strongbox tools will not appear until their assistant is
799
+ restarted. If someone says they just updated and you cannot see `strongbox_status`, that is the reason:
800
+ tell them to quit and reopen their assistant. Do not tell them the feature is missing.
801
+
777
802
  Auto-save is your seatbelt. The daily MD is your actually-arriving-somewhere.
778
803
 
779
804
  ## 10.2 Bank at milestones, not at the end
package/CLI_HANDBOOK.md CHANGED
@@ -430,6 +430,11 @@ you say yes. (That works through three tools: `strongbox_status` looks, `strongb
430
430
  records your answer, and `strongbox_clean` acts. Your assistant cannot grant your permission for
431
431
  you — recording it is a separate step from doing it, on purpose.)
432
432
 
433
+ ⚠️ **Just upgraded? Restart your assistant before you ask.** It reads the list of available tools
434
+ once, when it starts. If you updated Indelible while it was running, it is still holding the old
435
+ list and will tell you the cleanup does not exist. Quit and reopen Claude Desktop, or restart
436
+ Claude Code, and ask again.
437
+
433
438
  **What "safe" means here, exactly, because it is a deletion.** A copy is removed only if it has
434
439
  been proven byte-for-byte to be an earlier, shorter version of a copy that is kept — transcripts
435
440
  only ever grow, so an older snapshot is a literal prefix of a newer one. That check reads every
package/README.md CHANGED
@@ -15,6 +15,10 @@ npm install -g indelible-mcp
15
15
  indelible-mcp
16
16
  ```
17
17
 
18
+ **Upgrading from an earlier version?** Same command — and then **restart your assistant**: quit and
19
+ reopen Claude Desktop, or restart Claude Code. It reads the list of available tools once, when it
20
+ starts, so anything new in the release stays invisible until you do.
21
+
18
22
  ## Setup
19
23
 
20
24
  ### 1. Install & Connect Your Wallet
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "indelible-mcp",
3
- "version": "5.8.5",
3
+ "version": "5.8.6",
4
4
  "description": "Blockchain-backed memory and code storage for Claude Code. Save AI conversations and source code permanently on BSV.",
5
5
  "type": "module",
6
6
  "main": "src/index.js",
package/src/index.js CHANGED
@@ -23454,7 +23454,7 @@ init_wall_stub();
23454
23454
  init_wall_stub();
23455
23455
  init_wall_stub();
23456
23456
  var PROJECT_ROOT_FOR_CLONE_CHECK = resolve5(dirname25(fileURLToPath2(import.meta.url)), "../..");
23457
- var INDELIBLE_VERSION = "5.8.5";
23457
+ var INDELIBLE_VERSION = "5.8.6";
23458
23458
  var VERSION_CACHE_MS = 24 * 60 * 60 * 1e3;
23459
23459
  var REGISTRY_URL = process.env.INDELIBLE_REGISTRY_URL || "https://registry.npmjs.org";
23460
23460
  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
26217
26217
  }
26218
26218
  function printHelp() {
26219
26219
  console.log(`
26220
- Indelible MCP \u2014 Blockchain memory for Claude Code (v5.8.5)
26220
+ Indelible MCP \u2014 Blockchain memory for Claude Code (v5.8.6)
26221
26221
 
26222
26222
  Setup:
26223
26223
  indelible-mcp Set up interactively (recommended \u2014 your key is never written to shell history)