Use when submitting, pushing, or publishing a RayMol build to the **Mac App Store** — the sandboxed Apple-Distribution / App Store Connect flow (NOT the Sparkle notarized-DMG flow, which is `cut-macos-release`). Covers building the MAS archive (`archive_appstore.sh`, `RAYMOL_MAS_RESTRICTED` compiles out Sparkle + MCP), signing as Apple Distribution, uploading the build with `altool` + an ASC API key, and creating + submitting the App Store version in App Store Connect. Trigger whenever the user says "push to the App Store", "submit to the Mac App Store", "MAS release", "send it to App Review", "ship it on the App Store", "new App Store version", or asks to get a version onto the Mac App Store — even if they don't name a version or the steps. This is the Mac App Store channel; it does NOT mean the Sparkle/DMG release (use `cut-macos-release` for that) or the iOS App Store archive.
Use when cutting, preparing, or publishing a new macOS RayMol release — the Sparkle auto-update / notarized-DMG flow. Covers deciding the version bump from what's on master, building and notarizing the DMG, and publishing the appcast + GitHub release. Trigger whenever the user says "prepare a release", "cut a release", "new release", "release", "release it", "ship it" / "ship the app", "bump the version", or asks to review master for a possible release — even if they don't name a version number or list the steps. This means shipping a macOS build to users; it does NOT mean merging an unrelated PR or shipping other code. macOS/Sparkle only — the iOS/Mac App Store archive is a separate flow this skill does not cover.
Use when checking RayMol GitHub release download counts, DMG install stats, or auto-updater vs manual download breakdown across releases.
Develop and functionally test the native macOS RayMol app inside an isolated, disposable macOS VM AND drive it over its built-in MCP server from the host. Use when working on the macOS SwiftUI/Metal RayMol app and you want to build it, run it in a throwaway VM (not the host UI), and load/color/render/measure structures in it via MCP from this session. Builds on the mac-vm-test skill + mac-vm-pool MCP; adds the RayMol-specific dev flags and a direct-HTTP MCP driver so host↔VM control works.