feat(preview): add a crashes panel to the tools sidebar

[gwdp]

Why

/crashes had no reader. You could curl it, but nothing in the preview told you the app had died.

How

• Crashes section at the bottom of the Tools panel, with a count so you see it while collapsed
• A row opens the report: exception, thread, version, the stack with system frames folded away, and the log tail the backend collected
• Repeats collapse into one row. Older and Newer step through the kept occurrences, each with its own time, pid and tail
• Download the raw .ips if you want to open it elsewhere
• When there is no tail it says why, rather than showing an empty box
• The panel reads a stream instead of polling, so a crash shows up on its own. The device log tail is only kept alive while the section is open, so having the Tools panel open costs nothing
• The report dialog can be resized by dragging its right edge or using the Left and Right Arrow keys, and it remembers the selected width

Test Plan

• CI
• Crashed an app on a booted Sim with the panel open: the row appeared on its own, opened to a ~40 line tail, and stepping the occurrences swapped the time, pid and tail
• Resized the real crash report by dragging and with the keyboard, then closed and reopened it to verify the saved width

crash-ui.mp4

---

[linear-code]

ENG-25676

[devin-ai-integration]

Devin Review found 1 new potential issue.

[devin-ai-integration]

🟡 Malformed crash bodies remain downloadable

When an incident report retains a valid header but has a malformed body, isSameReport accepts it. parseCrashReport only gates incidentless occurrences, so the detail endpoint returns corrupt raw data without reportError.

(Refers to this code)

Learn more

An IPS report has a JSON header followed by a JSON body. The header can remain valid while the body is truncated or otherwise invalid. For occurrences with an incident ID, isSameReport returns immediately after comparing that header, so it never verifies the body. The route then exposes the malformed file as a valid raw report and leaves reportError null.

Example: The stored occurrence has incident ID INC-1. Its file now contains a valid INC-1 header followed by { "pid":. parseIpsHeader succeeds, the incident IDs match, and the corrupt file is returned instead of the fallback summary error.

Recommended fix: Require parseCrashReport(raw) to succeed before either identity comparison. Then compare incident IDs when present, otherwise compare PID and capture time. Add a route test using a valid header and malformed body.

---

Was this helpful? React with 👍 or 👎 to provide feedback.