feat(cli): improve diagnostic output

[roodboi]

What changed

• add a reusable, width-aware status-list renderer for diagnostic output
• collapse healthy hack doctor groups and hack setup sync scopes into compact rows
• expand only actionable warnings and errors with wrapped details and paths
• constrain panels to readable terminal widths and preserve list indentation while wrapping
• suppress raw Docker IDs and subprocess chatter during doctor repairs
• show macOS resolver setup only when resolver checks need attention

Why

Diagnostic commands were mixing raw log events, wide bordered prose, subprocess output, and healthy per-artifact lines. On real terminals this produced noisy walls of text and broken borders, making the actual repair path hard to find.

Compatibility

• hack doctor --json remains unchanged as the detailed automation contract
• setup/doctor exit-code behavior remains intact
• failing integration paths remain visible; healthy paths are summarized

Validation

• bun test
• bun run check
• bun run typecheck
• bun run build
• bun run docs:cli-reference
• live 72-column pseudo-terminal previews of hack doctor and hack setup sync --all-scopes --check

Release signal

Yes. This is a user-facing CLI improvement and uses a feat(cli) commit, so it should trigger the normal feature release signal.

[roodboi]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 🚀

Reviewed commit: d511bc5b18

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".