#185 docs: add a full CLI reference page (docs/CLI.md)

[Anonymous]

Originally created by: fu351

What

Doberman's CLI (doberman, Typer-based) has 21 subcommands defined in src/doberman/cli/main.py, but there is no single reference page listing them. Add docs/CLI.md: one entry per subcommand with its name, a one-line purpose, and one example invocation. This is pure transcription from the existing @app.command() docstrings/help text — no code changes.

Difficulty: level-1

Docs-only, no code to write or run beyond reading doberman --help and the CLI source. Good first issue.

Starting files

• src/doberman/cli/main.py — grep for @app.command to find every subcommand (currently: serve, scan, review, mode, enforcement, prefs, status, doctor, revoke, log, tui, dash, demo, memory, policy-history, install-hooks, uninstall-hooks, setup, dashboard, version, plus the hook subgroup's pre/post). Each command's docstring is its help text.
• docs/SETUP.md — existing docs page; match its tone/format.
• New file: docs/CLI.md.

Acceptance criteria

• [ ] Every command shown by doberman --help has an entry in docs/CLI.md: name, one-line purpose, one example invocation.
• [ ] 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 --help
# manually confirm every listed command name appears as a heading/row in docs/CLI.md

Out of scope

• Do not change any CLI behavior or add new flags (see the --quiet-flag and --json-output issues for that).
• Do not document internal-only test/dev commands not exposed via doberman --help.

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