SubMiner/backlog/archive/tasks/task-30.3 - Expose-resolver-operations-via-Electron-IPC-to-renderer.md

id, title, status, assignee, created_date, updated_date, labels, dependencies, parent_task_id, priority

id	title	status	assignee	created_date	updated_date	labels	dependencies	parent_task_id	priority
TASK-30.3	Expose resolver operations via Electron IPC to renderer	To Do		2026-02-13 18:32	2026-02-13 18:34		TASK-30.2	TASK-30	high

Description

Add a typed preload and main-IPC contract for streaming queries and playback resolution so the renderer can initiate search/list/resolve without embedding network/provider logic in UI code.

Acceptance Criteria

• #1 Define IPC handlers in main with input/output schema validation and timeouts.
• #2 Expose corresponding functions in preload window.electronAPI and ElectronAPI types.
• #3 Reuse existing mpv command channel for playback and add a dedicated request/response flow for resolver actions.
• #4 Implement safe serialization and error marshalling for resolver-specific failures.
• #5 Add runtime wiring and lifetime management in app startup/shutdown.
• #6 Document event/callback behavior for loading/error states.

Implementation Notes

Phase 3 — API surface: IPC/preload contract for resolver operations

Definition of Done

• #1 Renderer code can query providers without importing Node-only modules.
• #2 IPC paths have clear names and consistent response shapes across all calls.
• #3 Error paths return explicit machine-readable codes mapped to user-visible messages.