DOC: Add Windows troubleshooting & clarify User vs Developer setup

[skyforge-glitch]

What's wrong with the existing documentation

Problem

Several contributors on Windows (including me) ran into confusion while setting up PictoPy locally:

• The Windows .exe build works, but
• The Tauri dev flow often fails (backend startup / logging recursion / server readiness)
• Backend runs fine when started standalone (fastapi dev)
• Frontend/Tauri assumes backend auto-start, which is not always true on Windows

This makes it unclear:

• how users vs contributors are expected to run PictoPy
• whether Windows is fully supported for development or only for packaged builds

Proposal

Add a Windows-specific section to CONTRIBUTING.md (or a new doc) that clearly explains:

1. User workflow (recommended for Windows users)

   • Download .exe
   • First run may fail → grant firewall permission → reopen
   • App works after that

2. Developer workflow on Windows

   • Backend: run via fastapi dev
   • Frontend: run independently
   • Tauri dev flow may require extra setup or is unstable
   • Known Windows-specific caveats (logging, server startup)

3. Troubleshooting section

   • Backend starts but UI hangs
   • Server ports (8000 / 8001)
   • Firewall/network permissions
   • When to prefer EXE over dev mode

Benefit

• Reduces onboarding friction
• Prevents duplicate issues
• Helps contributors understand the intended workflow
• Clarifies Windows support expectations

If this sounds reasonable, I’m happy to open a docs PR.

Record

• I agree to follow this project's Code of Conduct
• I want to work on this issue

[github-actions]

👋 Thanks for opening this issue! The maintainers will review it shortly. Till then, do not open any PR. This is a strict rule we like to follow around here :)

[PrithvijitBose]

hey @skyforge-glitch i would like to work on this. i did the setup today and many things were unclear in the docs. It needs improvement.

[Ranganath-007]

hi, @skyforge-glitch I have gone through it and i would like on it

[rahulharpal1603]

hi, @skyforge-glitch I have gone through it and i would like on it

Do you not see the comment made by the GitHub Actions bot? Why are you in a hurry to start the work.

[udaykiran243]

Hey @rahulharpal1603 i would like to take this issue and it would be great if you assign me with this issue.

[rahulharpal1603]

@Ranganath-007 Why did you open a PR again?

[rahul-vyas-dev]

Hey @Ranganath-007 , have you not read the contribution rules before starting?
You should not open any PR until @rahulharpal1603 sir has reviewed the issue.
Please wait for their response, read the rules carefully, and then start contributing.
Do not violate the rules.