indelible-mcp 5.6.0 → 5.7.0

package/CLI_HANDBOOK.md

@@ -214,6 +214,13 @@ hook post-compact            Auto-restore after compaction (called by hook)
 
 The CLI and MCP server are the **same codebase**. They import the same tool functions (`saveSession`, `loadContext`, `saveFile`, `diaryChat`, etc.) and use the same wallet at `~/.indelible/config.json`.
 
+> ⚠️ **The same wallet on two machines: read from both, write from one.** The coin-reservation that
+> stops two saves colliding is kept **on the machine it runs on** — it cannot see a sibling box. So
+> two machines sharing a wallet can pick the same coin, both broadcast, and Bitcoin keeps one; each
+> box sees only its own attempt, so both can report success while one save is lost. Recall, verify
+> and read freely from anywhere. Do your **saving from one machine at a time**, and treat a save that
+> times out or says *pending* as not yet durable until it confirms.
+
 | | CLI | MCP Server |
 |---|---|---|
 | **Location** | `C:/Indelible-main/indelible-cli/src/` | `C:/bsv-claude-wrapper/mcp-server/` |

package/CUSTOMER_AGENT_HANDBOOK.md

@@ -263,6 +263,16 @@ They are not assigned to you. Nothing is issued. Each one is computed from your
 
 **Check it yourself.** Press "Verify crew" and the browser re-derives all sixteen from your wallet and compares them to what is stored. Close the browser, open it on another machine, unlock, and you get the same sixteen addresses. Nothing is fetched from us to make that happen.
 
+> ⚠️ **One machine writing at a time.** Deriving your crew on a second machine is safe — that is a
+> read, and it is the paragraph above. **Saving to the chain from two machines on the same wallet at
+> the same time is not.** Both boxes can pick the same coin, both broadcast, and Bitcoin keeps one of
+> them. Each box only sees its own attempt, so both can report success while one save is lost.
+>
+> Until coordinated writing ships, keep **one active writer**: use the second machine to read, verify
+> and recall, and do your saving from one. And treat a save that times out or reports *pending* as
+> **not yet saved** — it may still land, but until it is confirmed it is not durable, and the honest
+> move is to check `indelible-mcp status` rather than assume.
+
 Your crew is also **signed by your wallet**, and the signature is public. Anyone can fetch `/api/sanctuary/crew/<your-address>` with no account and check it offline: every agent is signed, and a separate crew signature commits to the exact set, so nobody can quietly serve someone a shortened version.
 
 **What that does and does not prove.** It proves we did not invent your crew and cannot alter it. It does not prove the agents were derived from your wallet, and nothing ever can: derivation runs on a shared secret, so only someone holding the private key can reproduce it. That is a recovery property, not a proof to strangers. It also does not stop us withholding the record entirely, which is what the on-chain anchor in section 8 is for. Until that lands the app marks every agent unattested, and means it.

package/LICENSE

@@ -11,7 +11,7 @@ Additional Use Grant: You may make use of the Licensed Work for personal,
                       commercial blockchain storage, session saving, or
                       encrypted vault service without written permission
                       from the Licensor.
-Change Date:          August 8, 2030
+Change Date:          August 13, 2030
 Change License:       MIT License
 
 Terms

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "indelible-mcp",
-  "version": "5.6.0",
+  "version": "5.7.0",
   "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",