fix(cask): zap real @memry userData and updater caches

[h4yfans]

Summary

brew uninstall --zap only trashed aspirational MemryNote paths and left all real app state behind: userData is keyed by package.json name (@memry/desktop) because electron-builder never writes productName into the asar package.json.

Makes the cask zap trash list the full union across all three naming eras (existing entries kept — harmless):

Today's real dirs (verified on disk):

• ~/Library/Application Support/@memry — real userData parent (Chromium profile, crdt-store, models, config, secure-secrets)
• ~/Library/Caches/@memrydesktop-updater — electron-updater download cache (app.name with / sanitized)
• ~/Library/Caches/com.memrynote.memry.ShipIt — Squirrel.Mac update staging
• ~/Library/HTTPStorages/com.memrynote.memry
• ~/Library/Logs/@memry — where prod logs actually live today

Post-identity-rename dirs (PR #897 moves userData/logs/updater cache to memrynote):

• ~/Library/Application Support/memrynote
• ~/Library/Caches/memrynote-updater
• ~/Library/Logs/memrynote

Also adds five selfcheck regression asserts pinning the @memry, updater-cache, and memrynote entries.

Deliberate decisions, for review:

• Vault content is NOT zapped. Notes and both SQLite DBs live inside the vault (<vault>/.memry/data.db|index.db, default ~/Documents/Memry) — casks don't touch Documents. Zap removes app state only, which is the zap convention (--zap is an explicit opt-in; plain brew uninstall still preserves everything).
• The existing Caches/com.memrynote.memry entry was already correct: macOS-level Caches/HTTPStorages/Preferences/ShipIt are keyed by bundle id (rename-independent), while Chromium's session cache lives inside userData (sessionData defaults to it). There is no ~/Library/Caches/@memry.
• This list is a superset of PR feat(app): rename the runtime identity to memrynote (logs, userData, Safe Storage) with legacy migration #897's cask edit — when the two branches conflict in the zap array, resolve by taking this block. @memry* entries stay for not-yet-migrated installs; feat(app): rename the runtime identity to memrynote (logs, userData, Safe Storage) with legacy migration #897's log migration deletes the emptied @memry Logs parent anyway.
• Keychain items can't be trashed by path and remain after zap (standard cask leftover).
• No tap-repo change needed: memrynote/homebrew-tap is fully generator-owned (publish-release overwrites Casks/memry.rb each release), so this propagates on the next release.

Release note

Homebrew: brew uninstall --zap now fully removes app data (settings, caches, logs, local sync state). Notes in your vault folder are never touched.

Test plan

• node scripts/generate-homebrew-cask.mjs --selfcheck — green, including the five new asserts
• Rendered the full cask and eyeballed the zap stanza
• Verified every current-era path exists under ~/Library on a machine running prod builds; confirmed Application Support/MemryNote does not exist; memrynote entries match PR feat(app): rename the runtime identity to memrynote (logs, userData, Safe Storage) with legacy migration #897's rename targets (app-identity.ts)
• Confirmed the setPath('userData') override is --device dev-profile-only (apps/desktop/src/main/index.ts:163) — prod path is stable
• pnpm docs:impact --base origin/main --strict — no docs-relevant changes

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.