Failure to generate cursor telemetry (`.cursor.json`) after DMG installation on macOS, impacting editor features.

## Bug Description

After installing Recordly v1.1.7 via the DMG on macOS 26.2 (Apple Silicon M3), cursor telemetry `.cursor.json` files are not being created alongside recordings. The editor shows "No cursor telemetry available — Record a screencast first to generate cursor-based suggestions."

## Environment

- **OS**: macOS 26.2 (Build 25C56) — Apple Silicon (M3 MacBook Pro)
- **Recordly version**: v1.1.7 (DMG install to `/Applications/Recordly.app`)
- **Permissions granted**: Screen Recording ✅, Accessibility ✅
- **Quarantine flags**: Cleared via `xattr -cr`

## Reproduction Steps

1. Install Recordly v1.1.7 via DMG
2. Grant Screen Recording and Accessibility permissions in System Settings
3. Record a screencast (any duration, tried multiple 30s+ recordings)
4. Open recording in editor
5. Click the zoom suggestions / wand button
6. See toast: "No cursor telemetry available"

## Evidence

Recordings made with `npm run dev` (dev build) **do** produce `.cursor.json` files. Recordings made with the DMG-installed app **do not**.

```
# Recordings WITH cursor.json (dev build, same machine, same day):
recording-1774718957877.mp4.cursor.json (1.5MB, ~10:35am)
recording-1774719579103.mp4.cursor.json (1.5MB, ~10:45am)
recording-1774743781164.mp4.cursor.json (77KB, ~5:23pm)

# Recordings WITHOUT cursor.json (DMG install, 7pm onward):
recording-1774749616308.mp4 ← no .cursor.json
recording-1774750149033.mp4 ← no .cursor.json
recording-1774750394518.mp4 ← no .cursor.json
record...