fix(desktop): resolve campaign enrollment, sequence execution, metrics, and operations center crashes

[kjxcodez]

Overview

This PR resolves multiple critical runtime crashes, database schema omissions, and SMTP credentials issues that blocked outreach campaign enrollment, automation sequence execution, operations center rendering, and observability metrics.

---

Key Changes

1. Preload Script Whitelisting (IPC)

• Whitelisted and registered missing IPC channels for campaigns (campaigns:list, campaigns:create, etc.) and scheduler in the preload script to support the main process and renderer bindings.

2. Campaigns Screen UI Redundant Parsing Check

• Checked the type of sequence.steps before attempting to call JSON.parse when running online, preventing JSON parse exceptions on the Campaigns screen.

3. Observability Metrics RangeError

• Bound the type parameter when executing the getAvgDuration prepared query inside observability-ipc.ts, eliminating the RangeError: Too few parameter values were provided exception.

4. Operations Center List Renderer Crash

• Included both j.id and j.id as jobId in the scheduler:queue:list SQL select statement to satisfy the renderer's expectation of job.id for list identification and the queue monitor component.

5. SQLite Database Schema Migration (tags column in contacts)

• Added migration 025_add_contacts_tags to alter the contacts table and create the tags column in the SQLite schema, which prevented the automation worker execution from starting at step 0 (no such column: tags).

6. SMTP Credentials & Account Resolution

• Updated the automation worker's email sender step to load the campaign's specific sending email account, select all SMTP columns, and decrypt the stored SMTP password using Electron's decryptSecret tool.
• Provided fallback logic to use SMTP credentials from the connected email account when global workspace settings are not defined.
• Safely fetched the campaign ID from the SQLite execution log to avoid type check errors in the build.

---

Verification

• Validated that the application builds successfully for production (pnpm build).
• Confirmed that migrations execute sequentially on workspace runtime boot.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
leadforge-os-api	Skipped		Aug 5, 2026 1:37pm
leadforge-os-marketing	Skipped		Aug 5, 2026 1:37pm