Read Raycast 2.x (RAYCFG3) backups

[tiliakoos]

What changed

Adds support for the .rayconfig format Raycast 2.x writes. src/main/raycast-v2-backup.ts decrypts the new container and maps the payload back onto the 1.x shape, so every existing importer, preview and count keeps working untouched.

Why

A Raycast 2.x export fails today, and the failure is reported as Password was not valid no matter what the user types. Raycast changed both halves of the export:

Container. 2.x writes RAYCFG3\n + UInt32LE header length + gzipped header JSON + AES-256-GCM ciphertext + a 16-byte auth tag. The key is scrypt over the password and the header's salt (N=16384, r=8, p=1, dkLen=32). decryptRaycastBuffer feeds the whole file to OpenSSL as salt-less AES-256-CBC, which cannot decrypt it, and the resulting failure falls into the wrong-password branch.

Payload. The decrypted JSON is category-keyed (settings, quicklinks, notes, nodeExtensions, ai, ...) rather than the 1.x builtin_package_* keys. Even a successful decrypt would find nothing to import.

Closes #652.

How it works

Detection is by container signature, checked before the plain-JSON probe. A RAYCFG3 file takes the new path; 1.x encrypted backups and unencrypted JSON exports take exactly the path they took before.

Mapped: global hotkey, window mode, pop-to-root timeout, navigation bindings, quicklinks, notes, snippets, store extensions with their per-command enabled state and preference values, command hotkeys, command aliases, and AI chats. Clipboard history and MCP servers are carried as counts only, so the preview keeps listing them as unsupported.

Three details worth review:

• Command ids. 2.x ids are opaque (c:n:<extension-uuid>::-::<command>). The converter emits root-search records only for the kinds SuperCmd can resolve: store extension commands by extension name, applications by path, and built-ins through an explicit id map. Quicklink, Apple Shortcut and AI-tool entries are skipped rather than approximated, since SuperCmd mints its own ids for those and a near-miss would bind a hotkey to the wrong command.
• Aliases. 2.x records an explicit alias field, so it is used verbatim (trimmed and lowercased). The existing heuristic that guesses an alias out of 1.x searchTerms discards anything under three characters, which would throw away real two-character aliases. The heuristic still runs for 1.x backups.
• Secrets. settings.nodeExtensions[].oauthTokens and settings.internalExtensions[].meta (which holds BYOK API keys) are never read. A test asserts nothing from those fields reaches the converted backup.

Compatibility impact

None for existing backups. The 1.x decrypt path, the plain-JSON path, and every downstream importer are unchanged. The only edits outside the new module are additive: an optional alias field on the root-search record type, an alias resolver that prefers an explicit alias over the guess, emacs accepted as a navigation-bindings value, and the 2.x built-in id map merged into the existing one.

How it was tested

• scripts/test-raycast-v2-import.mjs — 11 cases over a synthetic RAYCFG3 fixture built with a known password: container recognition, decrypt round-trip, wrong password producing the exact string the retry prompt matches, malformed and truncated containers reporting as malformed rather than as a bad password, unsupported container version, hotkey encoding, the category mapping, extension preference joining, secret exclusion, root-search emission rules, and AI chat message rejoining with tool turns dropped. No real .rayconfig is committed; the harness builds its own.
• npm test — 95 pass, 0 fail.
• npm run build — clean.
• Verified end to end against a real Raycast 2.3.0.0 export on macOS 26.6: 4 quicklinks, 4 notes, 13 extensions, 3 with preference values, 68 disabled extension commands, 33 AI chats, and 19 resolvable command records carrying 7 hotkeys and 16 aliases.

Verified after the fix by importing that same export into a local build: 4 quicklinks, 4 notes, 13 extensions, 33 AI chats, 7 command hotkeys and 16 aliases all landed.