indelible-mcp 4.9.9 — reliable when the world isn't perfect

This release hardens the client for the moments a dependency is slow, unreachable, or on a different shell. The product's happy path was already solid (a thousand-save soak passed clean); 4.9.9 fixes what happened around that.

Five things:

1. Auto-save and the security guard now fire on every install. The setup step was writing its hooks to a settings file Claude Code doesn't load at the user level, so on some installs the auto-save-before-compaction and the key-leak guard were installed but never ran. 4.9.9 writes them to the file Claude Code actually reads, and migrates any older install in place. If you ever want to confirm yours are live, run indelible-mcp install-hooks and it will report them.

2. A website or billing hiccup no longer blocks your saves. Saving verifies your plan against indelible.one. Before, if that check couldn't reach the server, the save was refused even with the chain, the bridges, and your wallet all healthy. Now a previously-verified Pro keeps saving straight through the outage, and the check resumes normally once the server is reachable again.

3. Saves are faster and more consistent. The client used to try bridges one at a time and could wait on a slow one. It now races them in parallel and takes whichever answers first, so a single slow bridge no longer stalls a save.

4. The save receipt tells the truth about recall. If a save lands on chain but the search-index post fails, the receipt now says so ("on chain, not yet findable") instead of a clean "committed." Your data was always safe on chain; now the receipt is honest about whether recall can see it yet.

5. The key-leak guard now covers PowerShell. On Windows, a command like Get-Content could read a config file past the guard. It's covered now.

Update with your usual npm command. No action needed on existing saves.