Updates

Even death stars have an exhaust vent.

Social sync memory cleanup now runs after failed provider scrapes

Run post-sync memory cleanup after Instagram placeholder-feed failures
Recover reclaimable WebKit memory tails after social scrapes before later providers stall
Report LinkedIn zero-event scrapes as IPC timeouts instead of successful empty feeds

Freed Desktop keeps locked installed sync soaks quiet and avoids waking WebKit while waiting for the workstation to unlock.

Destroy and rebuild the main WebView when idle WebKit memory is reclaimable but still resident.
Recover visible main-renderer WebKit resident tails once they cross the high-memory threshold.
Ignore stale age-matched WebKit process telemetry after a rebuild, which prevents repeated recovery loops and unnecessary background safe mode.
Record post-recovery memory verification so failed WebKit reclaim can be diagnosed from the health log.
Restart Freed Desktop when a renderer rebuild leaves the same main WebKit process above the high-memory line.
Keep post-scrape reclaimable WebKit resident-tail cleanup below the high-memory threshold from rebuilding the main renderer, so Instagram and LinkedIn retries do not trip recovery backoff while memory is still under budget.
Prevent the installed sync trigger helper from requeueing Instagram or LinkedIn during provider-safe cooldown windows.
Stop the native trigger watcher from replaying a request when the renderer rebuild happens after the provider run already finished.
Fail LinkedIn zero-post runs with local DOM diagnostics for candidate counts, activity URNs, login chrome, feed containers, and URL instead of treating them as successful empty syncs.
Slow locked-machine terminal sync trigger retries to 10 minutes, with an explicit long-soak timeout override for unattended testing.
Short-circuit locked-machine terminal sync triggers in native code before waking the main renderer, so locked soak retries do not inflate WebKit memory.

Improves social sync reliability after renderer recovery

Prevents dev sync trigger recovery from launching a duplicate Facebook, Instagram, or LinkedIn sync while the original provider job is still finishing.
Recovers hidden main renderers when WebKit resident memory grows past the idle cap, so stale WebKit memory does not block social sync preflight.
Recovers dev sync triggers that were left waiting after Freed Desktop rebuilt the renderer at the end of a social sync.
Reduces desktop sync renderer pressure after long social sync runs.

Freed now ships safer app recovery and steadier desktop validation.

Prevented the Linux social scraper window from crashing as it opens.
Cleaned up app recovery deferrals so Facebook, Instagram, and LinkedIn no longer show raw safe-mode timing noise in provider status.
Aligned LinkedIn feed sync with the shared social scrape queue so recovery pauses do not poison provider health or block later retries.
Reduced Friends graph interaction churn and stabilized desktop window compositing during recovery.
Pinned release-script Node routing, relaxed the scripted settings perf buffer that blocked the last dev build, and kept perf comparison comments from failing validation on read-only pull request tokens.

Hot WebKit recovery and unattended sync validation

Freed Desktop now recovers CPU-hot multi-GB WebKit renderer growth before the global high-memory ceiling
Facebook group refresh now reports group-list refresh state separately from Facebook post sync
Release notes now honor pinned same-day highlights so latest dev builds keep required carry-forward items
Release build and type-safety cleanup
Reader, feed, and header polish
Capture and scraper reliability fixes
Terminal Facebook, Instagram, and LinkedIn sync triggers now fail zero-post, deferred, paused, or unauthenticated runs instead of reporting false success
Sync trigger output now includes provider outcome details, post counts, added-item counts, and failure stage data so unattended runs can tell whether Facebook actually returned posts
The quiet startup contract now records the occlusion recovery policy in native tests and the desktop phase notes