docs: add Windows and WSL2 setup notes

[afurm]

Draftmora documents the common macOS/Linux-style local setup, but the README does not yet give Windows or WSL2-specific guidance.

Scope:

• Add tested Windows/WSL2 setup notes to README.md or CONTRIBUTING.md.
• Cover Node 22.14+, npm 11+, default ports, and where SQLite data is written.
• Include any path or browser-open differences that matter for npx draftmora and npm run dev.

Acceptance criteria:

• A contributor can follow the docs from a clean Windows 11 WSL2 environment.
• No private OpenAI tokens, .env, SQLite databases, or memory files are included.
• Run npm run typecheck, npm test, and npm run build after doc changes if source changes are involved.

[snakefood3232]

I see you're looking for Windows and WSL2 setup notes for Draftmora. I'd handle this by setting up a clean Windows 11 WSL2 environment to ensure everything works as expected with Node 22.14+ and npm 11+. I can cover default port settings and SQLite data paths, along with any necessary path/browser-open differences you need for npx draftmora and npm run dev. Can have a PR up within 2 days. I've built several cross-platform setups for TypeScript/Next.js projects, ensuring thorough documentation.

[afurm]

Thanks @snakefood3232, this sounds well aligned with the issue. Please go ahead.

A focused docs-only PR is ideal here. I would keep the scope to README.md and/or CONTRIBUTING.md unless you find a real setup bug while testing.

Useful details to include:

• Windows 11 + WSL2 distro tested
• Node and npm versions used
• npx draftmora flow and the default app URL
• local checkout flow with npm install and npm run dev
• default ports: packaged app/API on 127.0.0.1:4141, Vite dev UI on localhost:5173
• default SQLite path from the command working directory: ./data/board.db
• any browser-open or path differences specific to WSL2

Please avoid committing .env, API keys, OAuth tokens, SQLite databases, USER.md, MEMORY.md, or any local data. For a docs-only PR, a short tested-environment note is enough. If you need to touch source, please run npm run typecheck, npm test, and npm run build too.