Shared types and IPC contract for meetcap (meeting detection + recording in Electron)

Renderer-process half of meetcap: detector client + mic & system (loopback) audio capture, mix, record to webm, save. Framework-agnostic + React/Vue hooks. Electron.

Main-process half of meetcap: detect native meeting clients (Zoom / Teams / Tencent / Lark) + set up loopback recording, save & media-access IPC. Electron.

Shared recording engine for meetcap — the backend-agnostic capture state machine (events, pause accounting, crash-safe chunk ordering) that meetcap-renderer (Electron) and meetcap-web (browser) plug their capture/persistence/permission backends into.

Browser-native recording for meetcap — capture the mic, camera, a shared tab/screen (getDisplayMedia) or caller-provided streams (e.g. WebRTC remote audio), mix, record to webm, and persist crash-safe to IndexedDB. No Electron required; pairs with meetcap

Runtime negotiation for hybrid web/Electron codebases — one install that records via meetcap-renderer when the Electron preload bridge is present (loopback system audio, disk persistence, meeting detection) and falls back to meetcap-web (browser capture +