#54 fix(cli): encode-safe CLI output on non-UTF-8 consoles (Windows onboarding crash)

[Anonymous]

Originally created by: fu351

What this PR does

Found while installing Doberman on a Windows laptop to dogfood it: doberman install-hooks / setup crash with UnicodeEncodeError on the default Windows cp1252 console — they print decorative Unicode (→, box-drawing rules, em-dashes) via typer.echo, and cp1252 can't encode them. This blocks onboarding for any such user.

Universal fix (two layers):

1. _ensure_encode_safe_stdio() at the CLI entry reconfigures stdout/stderr to UTF-8 with errors="replace" (no-op where reconfigure is unavailable) — so all CLI output, including dynamic content, can never crash on the console encoding.
2. Replaced the decorative Unicode in CLI/onboarding strings with ASCII (->, -, x) so output also renders cleanly on any console (not just UTF-8).

Tests added (run in CI)

tests/unit/test_cli_encode_safe.py: a strict-cp1252 stdout no longer raises after the safe-guard; install-hooks --dry-run and setup --yes output is ASCII and cp1252-encodable. Local: ruff/format clean; CLI/hook/setup suite (136) green.

Public-release safety

• [x] Test/CLI-output only; no behavior change to the decision path. Core still standalone.

Notes / follow-up

• Separate minor observation (not in this PR): an editable pip install -e . didn't generate the doberman.exe console script on this Windows setup (a normal pip install doberman-core does). Worth a quick check of the editable packaging for dev onboarding.

[Anonymous]

Ticket changed by: Bestpart-Irene

• status: open --> closed