mpvault-archivelisted

# Build an MPVault Knowledge Vault Create a local archive with explicit evidence for exported, deleted, unavailable, and failed records. Treat `manifest.json` and `verification.json` as completion evidence; never infer success merely from a command exiting. ## Preflight 1. Obtain the target original ID (`gh_...`), optional display name, and output directory from the request or existing context. 2. Resolve MPVault from an installed `mpvault` command, `MPVAULT_ROOT`, or a local checkout whose `package.json` name is `mpvault`. If none exists, ask the user to install or provide the official MPVault checkout; never guess a repository or machine-specific path. 3. Confirm Node.js 22 or newer with `node --version`. When using a checkout, run `npm install` in its repository root. 4. Use the installed `mpvault` command, or run every `npm exec mpvault` command with the resolved checkout as working directory. Do not require global npm installation or sudo. 5. Keep `.wechat-session/`, exports, QR codes, cookies, tokens, account identifiers, article content, and absolute local paths out of GitHub issues, commits, and external messages. ## Authenticate Run: ```bash npm exec mpvault -- login ``` Keep the process active while it polls. When it prints `QR_READY <absolute-path>`, show that local image to the user in commentary and ask them to scan it. Tell them to select a public account or service account, not a mini program. Wait for `LOGIN_OK`. Reuse a valid local session. If it expi