passport-bootstraplisted

# Passport Bootstrap Restore an encrypted memory passport from a configured backend so a fresh mnemo-mcp install picks up the user's full memory history. ## When to Use Trigger on explicit signals: - "set up mnemo on this machine" - "restore my passport" / "import my memory passport" - "bootstrap mnemo on this laptop / VM" - New-machine context: "I just installed mnemo on a new device" - Recovery context: "I lost my memories, can you restore from S3?" Do NOT trigger when the user is on an already-configured machine (check `config(action="status")` first - if `total_memories > 0`, ask before importing because import LWW-merges and may NOT overwrite local rows newer than the bundle). ## Workflow ### Step 1: Detect configured backend Call `config(action="status")` and inspect the response. The default backend is the first entry of `SYNC_BACKEND` env (defaults to `gdrive`). If both `s3` and `gdrive` are configured, ask the user which one to import from. If neither is configured, stop and tell the user they need to run the relay form first (`config(action="setup_start")` in HTTP mode, or set `SYNC_S3_BUCKET` + `GOOGLE_DRIVE_CLIENT_ID` env vars in stdio mode). ### Step 2: Confirm passphrase The bundle is AES-256-GCM-encrypted with an Argon2id-derived key from the user's passphrase. The MCP server needs the RAW passphrase to decrypt - the Argon2id hash stored in `config.enc` is verification- only. In stdio mode: instruct the user to set `SYNC_PASSPHRASE` env var before ru