@safekb/mcp 0.6.0 → 0.7.0

package/README.md

@@ -108,7 +108,7 @@ every tool that keeps a key this way; see [Where secrets are kept](#where-secret
 | `--move-key <ref>` | | Move a seal root's current key to `--store system\|file`. |
 | `--delete-key <ref>` | | Remove a seal root's keys from this machine, after a typed confirmation. |
 | `--export <file>` | | Write what this token reaches to a new passphrase-protected file. Takes `--space`, `--doc`, `--compress`, `--skip-locked`. See [Export and import](#export-and-import). |
-| `--import <file>` | | Create what such a file holds in this token's account, as new things. Takes `--into-space`, `--store`. |
+| `--import <file>` | | Create what such a file holds in this token's account, as new things. Takes `--into-space`, `--store`, `--keys`. |
 | | `SAFEKB_SEALED_IDLE_TTL` | Seconds an unlocked seal root may stay idle. Default 900. `unlock_sealed` can set it per root with `idle_ttl_seconds` (60 to 3600). |
 | | `SAFEKB_HOSTED_TIMEOUT` | Seconds a hosted tool call may take. Default 300. |
 | | `SAFEKB_MCP_NO_BROWSER` | Set to anything: never start a browser, only show the authorize link. |
@@ -319,6 +319,7 @@ npx -y @safekb/mcp --export all.safekb --compress        # everything this token
 npx -y @safekb/mcp --export work.safekb --space <space id> --doc <document id>
 npx -y @safekb/mcp --import all.safekb                   # into the account of this token
 npx -y @safekb/mcp --import work.safekb --into-space <space id>
+npx -y @safekb/mcp --import all.safekb --keys pc-a.keys --keys pc-b.keys   # keys of locked roots
 ```
 
 Both need a terminal: the passphrase of the file is typed there (twice for an export) and is never an
@@ -334,10 +335,12 @@ What an export holds:
 - Databases with columns, indexes, views, rows, row pages and the rows' files.
 - Credentials with every secret field. Each secret of a server-encrypted credential is one audited
   reveal on the server.
-- Sealed folders, documents, attachments and credentials, decrypted on this machine. Every seal root
-  in the selection must open with a secret this machine keeps or its sidecar holds
-  (`safekb-mcp --sidecar`, then `add <name or id>` for a passphrase root); otherwise the export
-  stops before it writes anything. `--skip-locked` exports without those roots and says so.
+- Sealed folders, documents, attachments and credentials of every seal root that opens with a secret
+  this machine keeps or its sidecar holds (`safekb-mcp --sidecar`, then `add <name or id>` for a
+  passphrase root), decrypted on this machine.
+- Every other seal root as the server stores it, still sealed: the machine that makes the backup needs
+  none of their keys. The export names these roots before it writes. Pending deposits in them are left
+  out. `--skip-locked` leaves such roots out entirely instead.
 - Projects, tasks, decisions, and the links between exported things.
 
 What is selected:
@@ -356,6 +359,12 @@ What an import does:
 - Every exported space becomes a new space, also where one of that name exists. `--into-space` puts
   everything into one existing space instead. A token limited to some spaces is given the spaces it
   creates (this needs a SafeKB server of October 2026 or newer).
+- A seal root the file holds still sealed is opened with its key: from a key export given with
+  `--keys <file>` (repeatable; made with `--export-keys` on any machine that keeps the key; its
+  passphrase is asked and its keys are used for this import only), or from a store of this machine.
+  A key of another account, or one replaced since by a key or passphrase change, does not open it.
+  Without a key everything in that root is left out, and the root is named with the reason; import
+  the file again with its key to restore it (that creates everything else again too).
 - Every seal root becomes a new seal root with a newly generated key, kept in the default key store
   or the one named by `--store`; a passphrase root therefore becomes a key root. A seal root whose
   name is taken on this machine gets ` (imported)` appended. **Back the new keys up**
@@ -365,6 +374,8 @@ What an import does:
 - When a step fails the import stops, says at which record, and leaves what it had created; nothing
   is rolled back.
 
+A file written by 0.7.0 or newer is not read by 0.6.0; 0.7.0 reads files of 0.6.0.
+
 Not in an export: version history, creation and change times and authors, shares, public links, space
 members, and the account's settings. A vault document (encrypted in the browser to its owner's vault)
 is exported as ciphertext and can only go back into the account it came from, while its id is free
@@ -377,7 +388,8 @@ there. Merged tasks are left out.
 - A program running as your user can read a key file, ask the system keyring or the sidecar for a
   secret, and read the memory of this client while a root is unlocked.
 - A session that has unlocked a root can be tricked by content it reads into copying it elsewhere.
-- An export file: it holds sealed content under the passphrase of the file, not under its seal roots.
+- An export file: it holds the sealed content of every root that opened under the passphrase of the
+  file, not under its seal roots.
 - A compromised local machine, or a malicious server serving stale data.
 - Metadata: existence, sizes, timestamps, tree position.