[Hackathon] Width-aware progress ticker

[Andy00L]

Discord Username / User ID

interferon0

What does this improvement do?

The test run --wait / test wait progress ticker prints a single in-place line. On a narrow terminal or with a long run id the line soft-wraps to a second row, and the next \x1b[2K\r clears only one of the two rows, corrupting the redraw (ghost lines). This clips each frame to the current terminal width, re-read on every poll so it also follows a live resize. It stays completely silent on non-TTY (CI) and under --output json, so machine output is unchanged.

Details / implementation notes

Approach: width-aware truncation in src/lib/ticker.ts (read process.stderr.columns ?? 80, clip to width-1 to avoid last-cell auto-wrap, append a 1-column ellipsis). No new dependencies (ticker content is ASCII, so .length is an exact column count). Adds 10 unit tests (truncation, simulated resize, 80-col fallback, non-TTY silence). Full gate green: tsc, eslint, prettier, 1703 tests, coverage 98% on ticker.ts. PR to follow once assigned.

Confirmations

• I have searched existing issues and this is not a duplicate.
• I have provided my Discord identity above for reward coordination.

[Davidson3556]

can you assign this to me?

[zeshi-du]

To claim an issue, comment /assign (the literal slash command) — the triage bot only reacts to that exact form, not free-text requests.

[zeshi-du]

Triage: accepted (this one slipped through the 07-03 batch — sorry for the silence). Width-aware ticker rendering is a well-scoped, low-risk improvement to the stderr progress line. Constraints to honor: TTY-gated as today, no behavior change under --output json / non-TTY / CI, and degrade gracefully when columns is unavailable. Comment /assign if you want it.

[testsprite-hob]

Assigned to @zeshi-du. Thanks for taking this on. (0 more slots available.)

Your open assigned issues (3/3):

• MSW contract suite validates an obsolete LatestResult schema #255 — MSW contract suite validates an obsolete LatestResult schema
• Runtime Node guard accepts releases excluded by package engines #254 — Runtime Node guard accepts releases excluded by package engines

[zeshi-du]

Un-assigning myself. To be clear about why, since it looks odd in the history: the bot attached me as a side effect of my own triage comment — its matcher looks for a bare /assign token anywhere in a comment body and then assigns the comment author, so a maintainer writing "comment /assign if you want it" self-assigns. I unassigned myself once already on another issue and the explanatory comment re-triggered it 15 seconds later. That's being fixed (the command will have to be at the start of its own line, and mentions inside prose, code, or quotes won't count).

The verdict stands: accepted, and still unfixed. src/lib/ticker.ts is 116 lines with no terminal-width awareness at all — no columns read, no truncation, no ellipsis — so the ticker smears on narrow terminals.

This is open for anyone to pick up, and it's a good first change: read the terminal width, truncate to it, and keep the behaviour sane when stdout isn't a TTY.