Format CLI errors and centralize output fallback

[Copilot]

CLI errors were surfacing raw stack traces; defaults weren’t consistently respecting output format resolution.

• Error formatting: Added handleCliError to render unexpected failures as boxen in TTY, JSON/plain otherwise; wired into CLI entry to catch parseAsync failures.
• Output resolution: Centralized resolveOutputFormat in output.ts with a safe fallback and warning when option parsing fails.
• Tests: Added/updated errors.test.ts to cover formatting paths and exit behavior.

Example:

// packages/use-agently/src/bin.ts
try {
  await cli.parseAsync();
  await Promise.all([checkAutoUpdate(), flushTelemetry()]);
} catch (err) {
  handleCliError(err, resolveOutputFormat(cli));
}

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 --network base (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)

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.