#187 cli: add a --quiet flag to doberman scan

[Anonymous]

Originally created by: fu351

What

doberman scan (src/doberman/cli/main.py, scan() at line 206) always prints a human-readable risk map. For CI use (e.g. gating a script on doberman scan without wanting its output in the log) it's useful to suppress stdout while keeping the same exit code.

Difficulty: level-2

One new Typer option and a conditional around the existing typer.echo(render_risk_map(...)) call. No new logic.

Starting files

• src/doberman/cli/main.py — scan() (line 206), the typer.Option pattern already used by --path/-p on the same command.

Acceptance criteria

• [ ] doberman scan --quiet prints nothing to stdout.
• [ ] doberman scan --quiet exits with the same code as a plain doberman scan for the same repo.
• [ ] Plain doberman scan output is unchanged.
• [ ] Existing behaviour unchanged (no test weakened, no output format broken)
• [ ] ruff check . && ruff format --check . and lint-imports pass
• [ ] pytest passes

How to validate

doberman scan --quiet; echo "exit=$?"
doberman scan | wc -l   # non-zero: proves --quiet actually differs from the default

Out of scope

• Do not add --quiet to any other command in this issue.
• Do not change scan's exit-code semantics.

Notes for contributors

New here? Start with CONTRIBUTING.md. Issues are labelled level-1 (docs only) through level-10 (new subsystem) — pick one at your level and climb. Comment to claim an issue before starting.

[Anonymous]

Ticket changed by: fu351

• status: open --> closed