feat: Add action summary to push view

[andypols]

Summary

It can be hard to understand why a push was rejected. This PR adds a view of each step involved in a push, making it easier to identify failures. It also fixes #1387 and prevents the UI from crashing when a push fails before a diff is generated.

We use "steps" instead of actions in the UI, since “actions” was confusing for users.

Solution

• Introduces a tabbed view for push data, including Commits, Diff, and Steps. This reduces scrolling and provides a foundation for future additions, such as an AI-generated change summary (future PR).

• Adds dedicated components for each tab.
• Extended CustomTabs to support an optional badge.
• Calculates the total error count across steps and displays it as a badge to make failures more visible.
• Sums the error count from the steps and displays an error count as a badge to highlight there are errors.
• Adds a StepsTimeline component featuring an accordion layout, status chips, and log output to better surface errors, blocked steps, and successful execution.

• Clicking on an accordion step the info about that action

• Prevents large step payloads from being rendered.

[netlify]

✅ Deploy Preview for endearing-brigadeiros-63f9d0 canceled.

Name	Link
🔨 Latest commit	17dc7f2
🔍 Latest deploy log	https://app.netlify.com/projects/endearing-brigadeiros-63f9d0/deploys/69b29607159ddd000885a8d4

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.71%. Comparing base (90df884) to head (17dc7f2).
⚠️ Report is 70 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1446      +/-   ##
==========================================
- Coverage   90.01%   89.71%   -0.31%     
==========================================
  Files          67       68       +1     
  Lines        4769     4880     +111     
  Branches      885      888       +3     
==========================================
+ Hits         4293     4378      +85     
- Misses        458      484      +26     
  Partials       18       18              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[re-vlad]

lets couple of non-blocking suggestions

[re-vlad]

Can we pass steps={push.steps ?? []} into StepsTimeline so the component never receives undefined

[fabiovincenzi]

Also noticed that StepsTimeline already has an expandStepId prop that auto-expands a specific accordion, but it's never passed from PushDetails. If we calculate the first failing step, we can auto-expand it when the user opens the Steps tab:
const firstErrorStep = (push.steps ?? []).find((step) => step.error);

tabContent: <StepsTimeline steps={push.steps ?? []} expandStepId={firstErrorStep?.id} />

This way errors are immediately visible without the user having to manually click the failing step.

[andypols]

@fabiovincenzi auto-opening the steps with errors is a nice idea, but feels strange passing firstErrorStep in when StepsTimeline has all the information to do itself?

[re-vlad]

Small non-blocking suggestion: if push.steps is ever undefined (e.g. old API shape or malformed response), this throws. As for me, optional is more appropriate, something like this: const errorCount = push.steps?.filter((step) => step.error).length ?? 0

[re-vlad]

When commitData is empty, the table renders only headers with no body rows. Can you add an explicit empty state (e.g. a single row with colSpan and "No commits" or a short message)