#174 docs: add troubleshooting for PATH-shadowed Doberman installations

[Anonymous]

Originally created by: fu351

Context

A stale global, pipx, or virtual-environment installation can cause a different doberman executable to run than the one a contributor just installed. The setup guide should explain how to diagnose this without destructively rewriting PATH.

Suggested starting point

• docs/SETUP.md (github.com)

Acceptance criteria

• [ ] Add a focused “wrong or stale Doberman on PATH” troubleshooting section.
• [ ] Show how to list the resolved executable(s) in PowerShell (Get-Command -All doberman), Command Prompt (where.exe doberman), and Unix-like shells (command -v doberman or which -a doberman).
• [ ] Explain how to compare the resolved executable with the active virtual environment.
• [ ] Include safe inspection steps for common pip, pipx, and virtual-environment installs.
• [ ] Offer non-destructive remediation choices, such as activating the intended environment or invoking its executable explicitly.
• [ ] Keep commands clearly separated by shell so contributors can copy the right one.

Suggested validation

• Check every documented command against its named shell.
• Preview the Markdown and verify headings and code fences render correctly.

Out of scope

• Automatically editing a user's PATH.
• Deleting environments or uninstalling packages on the contributor's behalf.
• Rewriting Doberman's installer or packaging configuration.

Security and compatibility

Troubleshooting commands must not print secrets or dump the contributor's full environment. Do not recommend elevated shells, recursive deletion, or disabling shell security controls.

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

[Anonymous]

Ticket changed by: fu351

• status: open --> closed