#176 tests: smoke-test --help for every Typer command and group

[Anonymous]

Originally created by: fu351

Context

A CLI command can accidentally break at import or option-registration time even when its runtime tests pass. Doberman-Core has a startup test, but it does not exercise --help across every public Typer command and command group.

Suggested starting points

• src/doberman/cli/main.py
• tests/unit/test_cli_startup.py
• Existing CliRunner tests under tests/unit/

Acceptance criteria

• [ ] Build a clear parametrized matrix containing every public command and command group exposed by the Typer app.
• [ ] Invoke each target with --help.
• [ ] Assert every invocation exits with code 0 and contains no traceback.
• [ ] Include the root application help.
• [ ] Keep the test deterministic and independent of the network, user prompts, real home-directory state, and optional enterprise packages.
• [ ] Make omissions easy to notice when a future command is added (for example, document where the matrix must be updated or derive it safely from registered commands).
• [ ] Preserve the existing startup test that guards against importing heavy optional scientific dependencies.

Suggested validation

Run the new focused test file or test group, then run the existing CLI unit-test suite.

Out of scope

• Rewriting command help text.
• Changing command behavior or option names.
• Installing or importing enterprise-only packages.
• Exercising the functional happy path of every command.

Security and compatibility

A help smoke test must not initialize persistent Doberman state, read private policy content, perform network calls, or invoke protected tools. Core must continue to work with no enterprise package installed.

See CONTRIBUTING.md (github.com) before opening a pull request.

[Anonymous]

Ticket changed by: fu351

• status: open --> closed