Console improvements

[graeme]

PR: Make the console output selectable like a terminal

Summary

The console body was a List with one Text per line, so every line was its own selection scope: no drag across lines, nothing for Cmd-A to select, dead gaps between rows, and a pointer that flipped between an arrow and an I-beam. This makes it one text document, and tidies up the toolbar buttons above it.

Changes

Console output:

• ConsoleTextView replaces the list with an NSTextView, so drag selection, Cmd-A, Cmd-C, clicking between lines and the I-beam behave the way they do in Terminal.
• ConsoleTranscript (ViewModels) returns the minimal edit for each update rather than re-rendering the buffer, which would be quadratic over a run and would drop the user's selection every time a line arrived.
• ANSIConsoleText renders AppKit attributed text, with colours still named on the SwiftUI token palette so the design system stays the source.
• The view follows the tail only while the user is at the bottom, so scrolling up to read during a long install is no longer fought.
• ConsoleBody binds to one ConsoleBodyContent from the view model instead of reaching into the selected job.

Toolbar buttons:

• New shared BrewActionButton, used by the console toolbar and the command block header so both agree on icon-to-title spacing and highlighting. Hover fills the button; the press takes the app's selection tint.
• Copy and Clear confirm with a tick and "Copied" / "Cleared". Save does not, since its save panel is its own confirmation.

Testing

• scripts/test green (832 tests, plus 19 for BrewUILint). SwiftFormat, SwiftLint strict and BrewUILint clean; app and UI test targets build.
• Driven in the real app with an injected driver: drag selects four lines, selectAll: selects the whole document, the console opens pinned to the end, and a selection survives streamed output.
• Screenshotted the toolbar in its hover, pressed and confirming states.

PR checklist

• Have you followed this repository's contribution and workflow guidance?
• Have you explained what changed and why this should land now?
• Have you run relevant local checks for the changed scope?
• Are changes scoped and free of unrelated modifications?

---

• AI was used to generate or assist with generating this PR.
• If yes, describe exactly how AI was used and what manual verification was performed: Claude Code wrote the implementation and tests, then verified behaviour by driving and screenshotting the real app. Menu-routed Cmd-A could not be exercised that way, so it is worth one manual check.