v8 Release Todos

＃ memory.wiki — release audit + asset production brief

One-shot reference for the late-May / early-June 2026 release cycle. Lists what shipped on every channel, what still needs human action, and the exact image + copy briefs to commission new marketing assets from a designer (or to produce yourself).

Status as of 2026-06-05. Document owner: Hyunsang. Update in place as each item ships; archive when the entire checklist clears.

TL;DR — what landed in the last two weeks

Nine channels touched (web, desktop DMG, chrome ext, vscode, cli, mcp, iOS, Android, Mac App Store). Two channels are fully live; the rest are blocked on either store submission, manual upload, or fresh screenshots.

Headline features of the cycle, in order of "users will notice":

1. Per-user AI usage tracking — every callAI / streamText writes a row to ai_usage with action, provider, model, tokens, cost. Admin Usage tab at /admin → Usage shows totals, daily trend, top users, per-feature breakdown, per-provider breakdown, plus the full action catalog. Pro pricing finally has billing data.
2. Per-site Intent Capture suggestions in the Chrome extension. Twenty-four sites covered; site chips carry a small AI sparkle icon and are dismissible.
3. QuickLook actually registers with macOS now (v2.7.2). Root cause turned out to be electron-builder's deep-sign overwriting the .appex's sandbox entitlement. Fixed with an afterSign hook that re-signs the .appex with the right entitlements then refreshes the parent sign chain.
4. Threads body capture fixed. Long posts no longer ship as [Image #N] — falls back to og:description on permalinks when the React DOM only yields a fragment.
5. X quote-tweet body leak fixed. Clicking Add on a quote-tweet captures the focal tweet, not the quoted one.
6. Sidebar drag-out UX overhaul in the web editor. Drop anywhere on the tree background to move to root. Post-drop bounce killed; replaced with a brief background-fill flash + auto-scroll-into-view.
7. Sidebar context menu fit-to-viewport — right-clicking the bottom-most row no longer clips the menu.

Smaller polish: admin Usage tab silent auto-refresh, AI provider config admin-tunable, chrome-ext chip rail chevrons wrap at the ends, chip dedupe.

Per-channel release notes

memory.wiki (web app)

Live. No version bump. Recent commits:

• 7d7c3fb0 AI usage tracking — ai_usage table + logUsage helper across 22 call sites + admin Usage tab
• 876b2cd1 admin Usage tab action catalog + sidebar drag-out UX + context menu fit-to-viewport
• 494c6050 sidebar post-drop flash + scroll-into-view
• ea5cbf06 kill the post-drop bounce
• ca89fc7e drop accent left bar on the flash (background fill only)
• 7b0b931e admin page periodic flicker fix
• f56eaecd Start tab Starred + Recent show 5 by default with See More
• d730ffd7 realtime audit pass — fix sidebar miss + leaks + a11y
• 695293ce kill the false "updated elsewhere" toast + show external updates as a fresh-pulse
• 95b9848b Auto-Format runs on lite model + input-sized output cap
• 7cc88318 sidebar Refresh button does a full server resync
• 3b3d905b b972db44 AI provider cascade unification

Migration 062_ai_usage.sql applied.

Desktop (Mac, DMG — v2.7.2)

DMG ready, GitHub Release published. Notarized + stapled. Signed with Developer ID Application (Team W7NL89YGSD).

Download: https://github.com/raymindai/memory-wiki/releases/tag/desktop-v2.7.2

v2.7.1 was broken (Active badge said on, Space-in-Finder did nothing). v2.7.2 fixes the real cause:

• electron-builder's deep-sign was overwriting the QL .appex's com.apple.security.app-sandbox entitlement with the host's hardened-runtime entitlements (no sandbox). macOS pkd then silently rejected the extension with "plug-ins must be sandboxed".
• Fix: new scripts/afterSign.js hook re-signs the .appex with the QL entitlements file (sandbox + network.client), then refreshes the QL host bundle's signature, then refreshes the outer host's signature (shallow so it doesn't re-trigger the deep-sign). Verifies app-sandbox is present after re-sign; aborts the build if not.
• installQuickLook() in main.js now strips quarantine xattr + unregisters stale paths from previous installs (Xcode derived-data dev builds, old install locations) before lsregister'ing the current bundle. The Repair CTA on the Home banner is still there for emergencies.

Desktop (Mac App Store — task #165 pending)

Not submitted. Same code base as DMG, different build target. apps/desktop/scripts/build-mas.sh is wired and produces a signed .pkg, but App Store Connect submission has never been done.

Differences from DMG:

• appId flips to wiki.memory.desktop (already configured)
• .appex is embedded inside the host's Contents/PlugIns/ (not Resources/), with bundle id rewritten to wiki.memory.desktop.qlextension per Apple's "extension must be a child of host" rule
• Signed with Apple Distribution + provisioning profile (file already at apps/desktop/build/embedded.provisionprofile)
• Wrapped as .pkg via productbuild

What's blocked on submission:

1. App Store Connect record — never created. Need a new app entry: bundle id wiki.memory.desktop, primary category Productivity, secondary Developer Tools.
2. Screenshots — App Store requires at least one screenshot per supported size (1280×800 and 1440×900 are the common Mac sizes). See "Image production brief / Mac App Store" below.
3. Privacy nutrition label — App Store Connect form. Data collected: account info (email), user content (markdown docs uploaded to memory.wiki cloud), diagnostics (none). Data NOT collected: location, contacts, browsing history, ads.
4. Export compliance — uses HTTPS + standard TLS. Encryption Yes / Exempt (1.2.3).
5. Demo account — demo@memory.wiki with a couple of test docs already exists. Add credentials to the App Review notes.

Chrome extension (v2.7.0)

Zip ready, GitHub Release published, Web Store upload pending.

Zip: apps/chrome-extension/memory-wiki-clipper-2.7.0.zip (515 KB, 36 files) GitHub Release: https://github.com/raymindai/memory-wiki/releases/tag/chrome-ext-v2.7.0

New (user-visible): Per-site Intent Capture suggestions (24+ sites). Chip rail chevrons wrap around.

Fixed: X quote-tweet body leak, Threads body extraction (og:description fallback), Add button covering icons (dynamic svg-based positioning with !important inline), chip dedupe.

VS Code extension (v1.7.0)

Already published on Marketplace (June 2). No new commits since v1.7.0. Skipping.

Optional: refresh the Marketplace gallery screenshots — current ones are from v1.4.x, before the v3.0 TipTap web-parity migration.

CLI / MCP

Both up to date on npm. No code changes this cycle.

iOS (v0.1.0 — not yet shipped)

Native SwiftUI app at apps/ios-native/. v8 W9 deliverable.

What's built

• Main app: timeline of your memory.wiki docs, browse + open
• Share Extension (wiki.memory.MemoryWiki.Share) — capture from Safari, X, Threads, Notes, anywhere with iOS Share Sheet
• Widget (wiki.memory.MemoryWiki.Widget) — Home / Lock screen, recent docs
• Spotlight indexing of saved docs
• Offline-first sync (local SQLite mirror, sync on launch + on background-fetch)
• WebView hybrid renderer (v3.0 Phase E) — same markdown-it / KaTeX / Mermaid pipeline as the web

Bundle ids: wiki.memory.MemoryWiki (host), .Share (extension), .Widget (widget)

Project structure: generated from project.yml via XcodeGen — repo never has to merge a hand-edited .pbxproj. Existing screenshots in apps/ios-native/screenshots/ at v011, v012, v013, v014.

What's needed for first App Store submission

1. App Store Connect record — new app: bundle id wiki.memory.MemoryWiki, primary category Productivity, secondary Reference. Pricing free.
2. Screenshots — required sizes: 6.9" (iPhone 17 Pro Max), 6.5" (iPhone 14 Plus), and at least one iPad size if marking iPad compatible. See "Image production brief / iOS" below.
3. App icon — 1024×1024 master already in the Assets catalog from project.yml.
4. App review notes — demo account demo@memory.wiki / [password], sample doc URL like memory.wiki/abc123, explanation of Share Extension flow ("After install, open Safari → tap Share → select memory.wiki to save the page as markdown").
5. Privacy nutrition label — same as Mac App Store entry above.
6. TestFlight beta (recommended) — 1 internal test cycle before public submission. Easy to do once App Store Connect record exists.

Android (v0.1.0 — not yet shipped)

Native Kotlin/Compose app at apps/android-native/. v8 W9/W10 deliverable.

What's built

• Main app: timeline + browse + open
• Share intent receiver — capture from any app via Android Share Sheet
• Widget (Home screen, configurable size)
• WebView hybrid renderer (v3.0 Phase F) — same pipeline as iOS
• Offline-first via Room + sync on launch
• Material 3 + design-token-driven theme (v8 Pure design language)

Application id: wiki.memory.MemoryWiki

Release scaffolding is done — apps/android-native/RELEASE.md documents the upload-keystore.jks layout, gradle signing config, AAB build target, and Play Console submission flow. Both files (release-keystore.properties + upload-keystore.jks) are gitignored; founder back up only.

What's needed for first Play Store submission

1. Play Console app entry — package wiki.memory.MemoryWiki, category Productivity. Pricing free.
2. Signed AAB build — ./gradlew :app:bundleRelease (signing config already wired) → produces apps/android-native/app/build/outputs/bundle/release/app-release.aab
3. Screenshots — at least 2 phone screenshots (recommended 8) at 1080×1920 or higher. See "Image production brief / Android" below.
4. Feature graphic — 1024×500 PNG, the Play Store hero image
5. Privacy policy URL — Play Store requires a public URL. Use https://memory.wiki/privacy.
6. Data Safety form — analog to Apple's nutrition label. Collected: email (for account), user-uploaded markdown content. Not collected: location, contacts, advertising IDs.
7. Internal testing track (recommended) — ship to internal testers first, then closed beta, then production.

Image production brief

Every visual asset the release needs. Each subsection lists, per channel, every image to produce with exact dimensions, content, copy overlay, source-page-to-capture, design tokens, and where the asset will be uploaded.

Global design tokens (memory.wiki Pure design language)

Typography

• Headline: Cal Sans (bundled), tracking -0.01em
• Body: system-ui / -apple-system
• Mono: JetBrains Mono (bundled)

Brand voice for image copy

Plain. Specific. Verbs over adjectives. No "transform your workflow", no "supercharge". Avoid em-dash and middle-dot as separators inside image copy; use spacing or a forward slash. Mention "memory.wiki" lowercase. Reference features by their actual UI name. Numbers ("24+ sites", "2.7.2", "3 seconds") are good.

Chrome Web Store (priority 1)

Five images. Specs unchanged from earlier draft below.

chrome / 01-hero.png

chrome / 02-site-suggestions.png

| Dimensions | 1280 × 800 | | Background | Light (#fafafa) | | Capture | 3 mock browser frames stacked: YouTube, arXiv, GitHub. Each shows its popup with matching site chips. Sparkle icon visible | | Headline | "It knows where you are." | | Sub | "On YouTube: 'Summarize from transcript'. On arXiv: 'Abstract + contributions'. On GitHub: 'README in 5 bullets'." |

chrome / 03-social-capture.png

| Dimensions | 1280 × 800 | | Background | Dark (#09090b) | | Capture | Split: left = X / Threads post with Add button NOT covering pencil/more, right = resulting memory.wiki URL preview with clean markdown | | Headline | "Save a post, get a URL." | | Sub | "Author + body + media. No screenshot. Any AI can read it." | | Use a real Korean Threads post (the one that motivated the bug fix) so the screenshot is its own QA evidence |

chrome / 04-ai-transform.png

| Dimensions | 1280 × 800 | | Background | Light (#fafafa) | | Capture | Popup with Intent textarea filled ("Action items as checklist") + result preview below | | Headline | "Type what you want. Get it." | | Sub | "Polish, summarize, extract code, action items as checklist — your prompt, your call." |

chrome / 05-promo-tile.png (small promo, 440×280)

Morph blob left + "memory.wiki Clipper" wordmark right, "Capture, with intent." sub, mono "v2.7.0" corner pill. Dark.

chrome / 06-marquee-1400x560.png (optional, for featured-tile placement)

Wide horizontal. Blob + 3 bullet features: per-site / cross-AI / X-Threads-pages.

memory.wiki landing (priority 2)

site / hero-2026-06.png

| Dimensions | 2400 × 1200 @2x, displayed at 1200 × 600 | | Layout | Headline left, card collage right (doc URL chip, chrome popup with site chips, desktop Recent list) | | Headline | "From thought to shared URL, faster than your AI typed it." | | Sub | "Capture anywhere — web pages, X, Threads, AI chats, files — to a memory.wiki URL that Claude, ChatGPT, Cursor, and Gemini can all read." |

site / feature-admin-usage.png

| Dimensions | 1600 × 1000 | | Capture | Real /admin → Usage screenshot: totals header, daily cost trend chart, ≥1 row of Top users, ≥3 rows of per-feature breakdown | | Headline | "Pro pricing, on real data." | | Use real (anonymized) admin view — Pro pricing legitimacy shot |

site / feature-cross-ai.png

| Dimensions | 1600 × 1000 | | Layout | Center: memory.wiki/abc123 URL chip. 4 arrows radiating to Claude / ChatGPT / Cursor / Gemini marks | | Headline | "One URL. Every AI reads it the same way." |

site / feature-quicklook.gif

| Dimensions | 1200 × 750, 8s loop, ≤ 4 MB | | Capture | Finder window, .md file, Space → preview opens with our QL renderer (heading + code + mermaid). Close, repeat once | | Caption | "QuickLook for .md files. Press Space. That's the install." |

Mac Desktop DMG hero / docs (priority 3)

desktop / 01-hero-2.7.2.png

| Dimensions | 1920 × 1200 | | Capture | Full app window on macOS Sonoma dark mode. Sidebar with Synced / Local / Cloud expanded, open .md doc showing TipTap WYSIWYG (heading + list + code + math + mermaid), ambient morph blob low-opacity background | | Caption | "memory.wiki Desktop 2.7.2 — local files + cloud sync, in one editor." |

desktop / 02-quicklook-repair.png

| Dimensions | 1600 × 900 | | Capture | Home tab's QuickLook banner. Side-by-side: "ACTIVE" state (after repair) and "Repair" state (icon dimmed). Arrow between captioned "One click registers with macOS" |

desktop / 03-sidebar-drag.png

| Dimensions | 1600 × 900 | | Capture | Mid-drag screenshot: tab being dragged out of folder, tree showing the subtle background tint, destination row about to flash | | Caption | "Drag anywhere out of a folder. It scrolls into view and flashes — so you see where it went." |

Mac App Store (NEW — priority 3.5, blocking MAS submission)

App Store requires its OWN screenshots (not the DMG marketing shots). Required sizes:

mas / 01-1280x800.png (primary)

| Dimensions | 1280 × 800 | | Capture | Same as desktop / 01-hero but resized exactly. No marketing overlay text inside the screenshot itself — App Store renders the caption beneath | | Caption (entered in App Store Connect) | "Sidebar to your memory.wiki cloud, side by side with local files." |

mas / 02-1280x800.png

| Capture | Editor view — WYSIWYG content with mermaid diagram + KaTeX math + syntax-highlighted code block, all rendered | | Caption | "Same renderer as memory.wiki. What you see is what visitors see." |

mas / 03-1280x800.png

| Capture | Home tab with the QuickLook banner showing ACTIVE state | | Caption | "QuickLook for .md files. Press Space on any markdown file in Finder." |

mas / 04-1280x800.png

| Capture | Cloud tab with bundles + hub view, showing the AI sidebar open for one selected doc | | Caption | "Sync with the cloud. Chat with your docs. Cross-AI by default." |

mas / 05-1440x900.png (large display)

| Dimensions | 1440 × 900 | | Capture | Same as mas/01 but at 1440×900 — App Store also accepts this as a primary size |

Marketing text fields (App Store Connect)

• App name: memory.wiki
• Subtitle (30 char max): Markdown to a shareable URL
• Promotional text (170 char, can be edited without re-review): Per-user AI usage tracking, QuickLook for .md files, full TipTap WYSIWYG. Same cloud as memory.wiki on web.
• Description: see Copy library below
• Keywords (100 char): markdown,memory,wiki,notes,publish,wysiwyg,quicklook,obsidian,bear,ulysses
• Support URL: https://memory.wiki/support
• Marketing URL (optional): https://memory.wiki

iOS App Store (NEW — priority 4)

Required screenshot sizes (Apple requires AT LEAST the 6.9" iPhone size; 6.5" recommended for older devices):

ios / 6.9-01.png (iPhone 17 Pro Max — primary)

| Dimensions | 1320 × 2868 (portrait) | | Capture | Timeline view: recent docs as cards with title + first line + tiny visibility chip (Public / Private / Shared) | | Caption | "Every memory.wiki doc, in your pocket." |

ios / 6.9-02.png

| Capture | Share Extension flow: Safari article + Share Sheet open with "memory.wiki" highlighted | | Caption | "Save anything from Safari, X, Threads — to a URL Claude / ChatGPT can read." |

ios / 6.9-03.png

| Capture | Open doc with rendered TipTap content (heading + list + code block + KaTeX math) | | Caption | "Renders Markdown the same way the web does." |

ios / 6.9-04.png

| Capture | Widget on a Home screen — recent docs as a tappable list | | Caption | "Widget on Home or Lock screen. Tap to open." |

ios / 6.9-05.png

| Capture | Spotlight search for a doc title — result appears with memory.wiki icon | | Caption | "Spotlight finds your docs by title or body." |

Repeat same set at 6.5" (1284 × 2778) if marking compatible with older devices. Existing apps/ios-native/screenshots/v014/ may already have prior screenshots — start from those.

App Preview video (optional, 15-30s) — record a Share Extension capture + open in app + scroll timeline. Mute audio.

Marketing text

• App name: memory.wiki
• Subtitle: Capture to a shareable URL
• Promotional text: Capture anywhere with the Share Extension. Widget on Home + Lock screen. Spotlight indexing. Offline-first.
• Keywords: markdown,notes,share,bookmark,obsidian,bear,scrapbook,wiki,memory,publish
• Description: see Copy library

Android Play Store (NEW — priority 4)

android / 01-phone-1080x1920.png

| Capture | Timeline of recent docs (same as iOS 6.9-01) | | Caption | "Every memory.wiki doc, in your pocket." |

android / 02-phone-1080x1920.png

| Capture | Share intent flow: Android Share Sheet showing memory.wiki as a target | | Caption | "Share to memory.wiki from any app." |

android / 03-phone-1080x1920.png

| Capture | Open doc with rendered Markdown | | Caption | "Same renderer as memory.wiki on web." |

android / 04-phone-1080x1920.png

| Capture | Home screen widget showing recent docs | | Caption | "Widget for one-tap access." |

android / 05-tablet-1920x1200.png (optional but recommended)

| Capture | Tablet view: 2-pane (timeline left, doc right) | | Caption | "Big-screen layout on tablets and foldables." |

android / feature-graphic-1024x500.png (REQUIRED)

| Dimensions | 1024 × 500 | | Layout | Wide horizontal hero. Phone mockup on the right showing the app + headline left | | Headline | "memory.wiki for Android" | | Sub | "Capture, sync, share." |

Existing prior screenshots: apps/android-native/screenshots/v014/ — start there.

Marketing text

• App name: memory.wiki
• Short description (80 char): Capture to a shareable URL. Share Sheet integration. Widget. Offline-first.
• Full description: see Copy library
• Category: Productivity

VS Code Marketplace (priority 5)

vscode / banner-1376x768.png

| Capture | VS Code with memory.wiki sidebar open, open .md, WYSIWYG preview right with mermaid | | Caption | "memory.wiki for VS Code / Sidebar / WYSIWYG preview / one-click publish" |

vscode / 02-sidebar.png

| Capture | Sidebar close-up: Starred top, Cloud docs grouped by state (Public, Shared, Private, View only), Local-only bottom | | Caption | "Every cloud doc, grouped by who can see it." |

vscode / 03-preview.png

| Capture | Editor split: markdown source left, full TipTap preview right (code + KaTeX + mermaid) | | Caption | "Same renderer as memory.wiki. What you see is what visitors see." |

Social launch set (priority 6)

social / twitter-1200x675.png

| Headline | "Capture from anywhere on the web. Tell it what you want. Get a URL Claude / ChatGPT / Cursor can all read." | | Footer | "memory.wiki Clipper 2.7.0 — out now for Chrome." |

social / linkedin-1200x627.png

Same headline + screenshot. Caption (post body, not on image):

Spent the week shipping the boring-but-load-bearing parts: per-user AI usage tracking across every surface, QuickLook on macOS that actually registers with the system, and a chrome popup that knows whether you're on YouTube vs. arXiv. Small features individually, but together they're the difference between "I tried this once" and "I use this every day."

social / threads-1080x1350.png

| Layout | Stacked: screenshot top, headline middle, 3-feature list bottom | | Headline | "It guesses what you want to do, before you type it." |

Copy library

Chrome Web Store

Name: memory.wiki Clipper

Short description (132 char max)

Save anything on the web to a memory.wiki URL any AI can read. Per-site Intent Capture. AI transforms on the fly.

Full description

memory.wiki Clipper turns any web page, AI chat, social post, image, or selection into a clean memory.wiki URL — the same URL Claude, ChatGPT, Cursor, and Gemini all read identically.

What's new in 2.7.0

Per-site Intent Capture. The popup looks at the current tab and surfaces the 3 most likely intents for that kind of page. On YouTube: summarize from transcript. On arXiv: abstract + contributions. On Stack Overflow: accepted answer + code. Click a chip, capture, done.

X / Threads / page capture, fixed properly. Quote-tweets, long Threads posts (the kind that used to come through as just an image), URL-only tweets with link cards — all now capture cleanly. The Add button positions itself dynamically so it never covers the pencil or more-menu.

Chip rail wraps at the ends. No more dead clicks.

Core

Capture anywhere: full pages, selections, images, AI chats (Claude / ChatGPT / Gemini / Perplexity), X / Threads / Reddit / Hacker News / Medium / Substack posts. AI transform on the fly: "Action items as checklist", "Cursor-ready reference", "TL;DR in 2 sentences", or type your own intent. Every capture becomes a memory.wiki URL anyone (or any AI) can open. No login required for anonymous captures. Sign in to attach captures to your account.

No tracking. No third-party data sharing. Source on GitHub at raymindai/memory-wiki.

Mac App Store description

memory.wiki Desktop is the native macOS companion to memory.wiki. Sidebar to every doc in your cloud, side by side with local .md files on disk. WYSIWYG editor matches the web exactly (GFM, KaTeX math, Mermaid diagrams, syntax-highlighted code). Two-way sync.

Highlights

• QuickLook for .md files. Press Space on any markdown file in Finder, get a rendered preview instantly.
• Sidebar groups docs by visibility (Public, Shared, Private, View-only) and source (Synced, Local, Cloud-only).
• Every doc you publish gets a memory.wiki URL that Claude, ChatGPT, Cursor, and Gemini all read the same way.
• Drag-and-drop import. Move files between folders. Right-click for full per-doc actions.
• Offline-first. Edit local files anytime; sync resumes when you're back online.

No tracking. No third-party data sharing.

iOS App Store description

memory.wiki for iOS. Capture from anywhere with the Share Extension. Recent docs on Home + Lock screen via the Widget. Spotlight finds your docs by title or body. Offline-first.

Highlights

• Share Extension: select "memory.wiki" from any iOS Share Sheet — Safari, X, Threads, Notes, Mail — to save the source as a clean markdown doc on memory.wiki.
• Widget: recent docs on Home or Lock screen. Tap to open.
• Spotlight indexing: find your docs alongside system search results.
• Renders Markdown the same way memory.wiki does on web (GFM + KaTeX + Mermaid).
• Offline-first: docs cached locally, sync on launch and in the background.

Same account as memory.wiki on web. No tracking. No third-party data sharing.

Android Play Store description (full)

memory.wiki for Android. Capture from any app via the Share Sheet. Home screen widget with recent docs. Offline-first.

Highlights

• Share intent receiver: send any text / URL / image from any app to memory.wiki via Android's Share Sheet.
• Widget: recent docs on your Home screen, configurable size.
• Same renderer as memory.wiki on web (GFM + KaTeX + Mermaid + syntax highlighting).
• Offline-first: docs cached via Room; sync on launch.
• Material 3 themed; light and dark modes follow the system.

Same account as memory.wiki on web. No tracking. No third-party data sharing.

VS Code Marketplace description (if refreshing)

memory.wiki for VS Code. Sidebar to your memory.wiki cloud right inside the IDE. Publish a Markdown file, get a permanent URL Claude, ChatGPT, Cursor, and Gemini all read the same way. WYSIWYG preview matches the web renderer exactly (GFM, KaTeX, Mermaid, code highlighting). Sidebar lists every cloud doc by visibility state. Two-way sync.

memory.wiki landing — feature copy

Per-user AI usage tracking

Every AI call across memory.wiki — chat, polish, format, transform, hub synthesis — writes a row to ai_usage with the action, provider, model, tokens, and cost. The admin Usage tab shows totals, daily trend, per-user spend, and a per-feature breakdown. Pricing is built on real data, not estimates.

Per-site Intent Capture (Chrome extension)

Open the popup on YouTube and the first chip you see is "Summarize from transcript". On arXiv: "Abstract + contributions". On GitHub: "README in 5 bullets". Twenty-four sites covered out of the box. Click a chip, capture, done.

Cross-AI delivery model

Every memory.wiki URL serves a clean markdown payload — no auth wall, no proprietary container, no rendering tricks. Claude, ChatGPT, Cursor, Gemini, Perplexity all fetch the same bytes. The cross-AI moat is the delivery model, not the retrieval.

Manual launch checklist (in order)

Tier 1 — already shipped or one-click away

1. ✅ Web auto-deployed
2. ✅ Desktop DMG v2.7.2 — GitHub Release published
3. ✅ Chrome ext v2.7.0 zip — GitHub Release published
4. ⬜ Chrome Web Store upload (you, ~10 min + 1-3 day review)
   • Go to https://chrome.google.com/webstore/devconsole
   • Package tab → Upload new package → apps/chrome-extension/memory-wiki-clipper-2.7.0.zip
   • Store listing tab → replace screenshots (see Chrome brief above) + paste copy
   • Submit for review
5. ⬜ memory.wiki landing refresh — update Mac download link to v2.7.2, swap in new feature shots

Tier 2 — new stores (multi-week effort)

6. ⬜ Mac App Store first submission (task #165)
   • Create App Store Connect record
   • Build .pkg via cd apps/desktop && ./scripts/build-mas.sh
   • Take 4-5 screenshots per "Mac App Store" brief above
   • Fill privacy nutrition label, export compliance, demo account
   • Submit
7. ⬜ iOS App Store first submission
   • Create App Store Connect record for wiki.memory.MemoryWiki
   • Archive in Xcode → upload via Transporter
   • Take 5+ screenshots at 6.9" per iOS brief above
   • Fill privacy nutrition label, demo account
   • TestFlight 1 internal cycle, then Submit
8. ⬜ Android Play Store first submission
   • Create Play Console app entry
   • Build AAB via ./gradlew :app:bundleRelease
   • Take 4+ phone + 1 tablet screenshot + feature graphic per Android brief above
   • Fill Data Safety form + privacy policy URL
   • Internal testing → closed beta → production

Tier 3 — polish

9. ⬜ VS Code Marketplace gallery refresh (optional)
10. ⬜ Social launch posts (after Chrome Web Store goes live)
11. ⬜ Verify QuickLook on a fresh v2.7.2 install yourself before announcing

What I did automatically before writing this doc

For paper trail:

• Built + notarized + stapled Desktop v2.7.2 DMG (memory.wiki-2.7.2-arm64.dmg)
• Created afterSign.js hook that re-signs the QL .appex with the right entitlements file then refreshes the parent sign chain
• Bumped Chrome extension manifest 2.6.0 → 2.7.0, packaged clean zip (515 KB, 36 files)
• Tagged desktop-v2.7.2, desktop-v2.7.1, chrome-ext-v2.7.0 on origin
• Created GitHub Releases for the desktop and chrome ext
• Pushed everything to main

What remains is human-only: store submissions, new screenshots, copy review.

Generated 2026-06-05. Update in place as items ship; archive when checklist clears.