#173 docs: correct Windows virtual environment activation commands

[Anonymous]

Originally created by: fu351

Context

CONTRIBUTING.md currently shows one generic Windows virtual-environment activation command. PowerShell and Command Prompt use different activation scripts, so first-time contributors can hit an avoidable setup error.

Suggested starting point

• CONTRIBUTING.md (github.com)

Acceptance criteria

• [ ] Show the PowerShell command as .venv\Scripts\Activate.ps1.
• [ ] Show the Command Prompt command as .venv\Scripts\activate.bat.
• [ ] Clearly identify which shell each command belongs to.
• [ ] Preserve the existing Unix/macOS activation guidance.
• [ ] Keep the surrounding setup sequence accurate and easy to copy.
• [ ] Verify the rendered Markdown has no broken code blocks or headings.

Suggested validation

• Preview the edited Markdown on GitHub or with a local Markdown previewer.
• Follow the instructions in a clean PowerShell session and, if available, Command Prompt.

Out of scope

• Changing Doberman's dependencies or packaging.
• Rewriting the complete contributor guide.
• Automatically changing a contributor's PowerShell execution policy.

Security and compatibility

Do not recommend bypassing execution-policy protections or running downloaded scripts with elevated privileges. This documentation change must not alter Unix/macOS instructions.

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

[Anonymous]

Ticket changed by: fu351

• status: open --> closed