[codex] Preserve desktop update state causes

[juliusmarminge]

Summary

• retain the structured DesktopUpdateStateReadError in terminal retry logs
• preserve its exact IPC cause and stack alongside the existing attempt metadata
• keep update retries, listener behavior, and the null fallback unchanged

Root cause

The recovery boundary copied the error tag and attempt count into log attributes but retained only the wrapper stack. The original IPC cause was therefore unavailable after the read failure was swallowed.

Validation

• vp test apps/web/src/state/desktopUpdate.test.ts
• vp check
• vp run typecheck

---

Note

Low Risk
Observability-only change to error log payload; no change to retry, subscription, or state fallback behavior.

Overview
When the initial getUpdateState read fails after retries, terminal Effect.logError now attaches the full DesktopUpdateStateReadError (via an error field) instead of only copying error.stack.

That keeps the original IPC failure on error.cause in log context for debugging, while retry count, listener behavior, and the null fallback stay the same. Tests now assert the logged error is the tagged instance and that cause matches the rejected IPC error.

^{Reviewed by Cursor Bugbot for commit 37fe94b. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Preserve error cause in desktop update state read failure logging

In createDesktopUpdateStateAtom, the Effect.catchTags handler for DesktopUpdateStateReadError now includes the full error object in the log context instead of a separate stack field. This makes the original cause accessible when inspecting error logs.

^{Macroscope summarized 37fe94b.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 1bc8ebd9-1d01-4955-b56f-26d0e0db9ec4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/preserve-desktop-update-state-cause

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

Simple logging improvement that preserves full error context (including cause chain) instead of just the stack trace. No runtime behavior changes - only affects debugging information.

^{You can customize Macroscope's approvability policy. Learn more.}