feat: add --quiet flag for scriptable, low-noise runs

[Arthur742Ramos]

Summary

Adds a --quiet / -q flag to the main bootcamp <repo-url> command for scripting and CI. It suppresses all decorative output — the ASCII banner, run header, detected-stack table, progress spinners, score summary, and the generated-files tree — and prints only the output directory path on stdout.

OUT=$(bootcamp https://github.com/owner/repo --quiet)
open "$OUT/BOOTCAMP.md"

Failures and warnings are still written to stderr, so problems remain visible even when the chrome is gone. --quiet and --verbose are mutually exclusive (passing both exits 1 with a clear message).

Why

The full run prints a lot of human-friendly chrome that's noise in a pipeline. Until now there was no way to get a clean, parseable result. --quiet makes the command composable: capture the path, gate on exit code, and keep logs tidy.

Implementation

• BootcampOptions.quiet plumbed from the CLI.
• ProgressTracker gains a quiet mode: the spinner is silenced via ora's isSilent, but fail/warn fall back to direct stderr writes so failures are never swallowed.
• main-command.ts gates every decorative console.log behind !quiet, and prints the output dir as the final stdout line.
• agent.ts ("Using model" / tools banner) and output-writer.ts (diagram render messages) honor quiet too, so stray lines don't leak.

Testing

• 4 unit tests on ProgressTracker quiet mode: spinner stays silent for normal phases; fail/warn still reach stderr; tool-call bookkeeping is preserved.
• 1 main-command behavior test: with quiet: true the banner/stack/success-box/next-step are absent and the output directory is printed.
• 2 E2E tests (real CLI via the test LLM harness): quiet stdout's last line is exactly the output dir and the docs are still written; --quiet --verbose exits 1 with "mutually exclusive".
• Full suite green: npm test → 1067 passing; typecheck + lint + build clean.

🤖 Generated with Claude Code