#182 docs(contributing): clarify Windows venv activation

[Anonymous]

Originally created by: kushin25

Summary

• Clarifies that Unix/macOS, Windows PowerShell, and Windows Command Prompt use different virtual-environment activation commands.
• Fixes the contributor onboarding instruction described in [#173] without changing dependencies, packaging, or runtime behavior.

Test plan

• git diff --check — passed.
• Reviewed the rendered Markdown structure: the contributor setup block remains a balanced fenced bash block, and the commands match the named shells.
• Full Python lint/test suite was not run because this is a documentation-only change; no Python or dependency files changed.

Notes

• AI assistance was used to prepare this documentation-only change; it was reviewed before submission.

Public-release safety (doberman-core only)

• [x] Contains nothing from the "not allowed" list: no enterprise/hosted code, no proprietary detection, no customer data, no secrets, no commercial-license code.
• [x] Core build/test behavior is unchanged; no enterprise package is involved.

Security checklist

• [x] No secret, full file, or unredacted prompt logged or committed.
• [x] No guardrail, learning, or runtime behavior changed; fail-closed and raise-only invariants are unaffected.
• [x] No doberman_enterprise import was added.

Edge cases covered / Deviations from plan / Risks introduced

• The commands explicitly distinguish PowerShell's Activate.ps1 from Command Prompt's activate.bat.
• Validation on an actual Windows shell was not available in this Linux runner; the commands follow the issue's acceptance criteria and standard venv layout.

[Anonymous]

Originally posted by: fu351

Thank you for the contribution. Your fix is correct; PR [#181] submitted the same change earlier and had green CI, so I closed this one only as a duplicate. I appreciate you taking the time to improve the Windows onboarding docs. You’re also very welcome to join the Doberman Discord and stay involved.

[Anonymous]

Ticket changed by: fu351

• status: open --> closed

[Anonymous]

Originally posted by: fu351

@kushin25 This one was beaten to the punch rather than turned down; the instinct to smooth the Windows setup path was right. I'd love to see you take another issue.

Quick community roll-call: are you in the Doberman Discord? If yes, drop your handle here (or DM me there) so I can match the GitHub side of your work to your Discord name. If not, you're warmly invited: https://discord.gg/Sfy5XGNqty