Greptile Summary

This PR adds a LiveSpeedGraph boolean setting that lets users toggle between raw speed and EMA-smoothed speed in the speed graph. It also ships a collection of related UI quality improvements: truncateString is rewritten to use lipgloss.Width/MaxWidth for correct Unicode terminal-width handling, the label-offset in the focused details panel is corrected from -8 to -12 (matching StatsLabelStyle.Width(12)), description lines in the download list are now truncated, and d.ID receives truncation it was previously missing.

Confidence Score: 5/5

Safe to merge — the feature logic is correct and the accompanying UI fixes are improvements over the previous behavior.

All findings are P2 style suggestions. The core LiveSpeedGraph toggle is implemented correctly, the EMA fallback path is preserved, and the truncation refactor fixes real Unicode-width and overflow bugs.

No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[processProgressMsg] --> B{GraphUpdateInterval elapsed?}
    B -- No --> Z[Skip graph update]
    B -- Yes --> C[calcTotalSpeed]
    C --> D{Settings != nil &&\nLiveSpeedGraph?}
    D -- Yes --> E[smoothed = totalSpeed\n raw speed]
    D -- No --> F{len SpeedHistory > 0?}
    F -- Yes --> G[EMA: α·speed + 1-α·prev\nα = 0.3]
    F -- No --> H[smoothed = totalSpeed\n first-point fallback]
    E --> I[Append to SpeedHistory]
    G --> I
    H --> I

This is a comment left during a code review.
Path: internal/tui/components/box.go
Line: 95-96

Comment:
**"What" comment instead of "why"**

`// Style for truncation` restates what `truncStyle` is without explaining the intent. Per the project's comment guidelines, comments should explain *why* — in this case, why the style is hoisted outside the loop (to avoid allocating a new `lipgloss.Style` on every iteration).

```suggestion
	// Reused across iterations to avoid per-line style allocations
	truncStyle := lipgloss.NewStyle().MaxWidth(innerWidth)
```

**Rule Used:** What: Comments must explain *why* code exists, not... ([source](https://app.greptile.com/review/custom-context?memory=4e45ef13-32c2-4753-8060-a44ef767144d))

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (2): Last reviewed commit: "refactor: optimize box content truncatio..." | Re-trigger Greptile}