Improve CLI error formatting

[Copilot]

• CLI now formats top-level errors instead of dumping stack traces, providing boxen-styled TUI output on TTY and JSON when stdout is non-TTY.
• Added reusable handleCliError/resolveOutputFormat utilities and wrapped the CLI entrypoint to ensure consistent formatting.
• Expanded coverage with TUI/JSON/default output tests and deterministic stderr TTY mocking.

Example:

try {
  await cli.parseAsync();
  await checkAutoUpdate();
} catch (err) {
  handleCliError(err, { output: resolveOutputFormat(cli.optsWithGlobals().output) });
}

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• mainnet.base.org
  • Triggering command: /usr/local/bin/node node dist/cli.js dev --anvil-port 8545 --anvil-host 0.0.0.0 --port 4022 --rpc-url REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.