fix: Improve timestamp alignment in build logs

[Kraci]

Problem

Each build-log row shows a relative elapsed time (e.g. 3.6s) followed by the absolute time (e.g. 04:50:49.96 PM). The elapsed time has a variable width, which caused two visible bugs:

1. Truncation — once elapsed time hit two digits (10.2s), the extra character pushed the row past the fixed-width column and the absolute time got clipped to ….
2. Misalignment — the variable-width elapsed time shifted the absolute time to a different horizontal position on every row, so timestamps didn't line up vertically and were hard to scan.

On top of that, the elapsed value itself jumped around: formatDurationCompact emitted unpadded fields (2m 8s vs 2m 27s), so the seconds column wandered between single- and double-digit widths.

Solution

Gave the timestamp a stable, fixed-width layout so the whole column lines up vertically and is easy to scan top-to-bottom. The elapsed time and the absolute time now each occupy a fixed column, durations are zero-padded so digits don't shift between rows, and the full timestamp always fits without truncation.

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have @Kraci on file. You can sign our CLA at https://e2b.dev/docs/cla . Once you've signed, post a comment here that says '@cla-bot check'

[linear-code]

EN-601

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
web	Ready	Preview, Comment	Jun 18, 2026 1:10pm

[Kraci]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.