[ENHANCEMENT] Document a repeatable Windows VS Code bootstrap path for Roo tasks

[Mwright413]

Problem

Windows users do not currently have the same clean Roo CLI bootstrap path as macOS/Linux users. The CLI quick installer documents macOS Apple Silicon and Linux x64 support, while the VS Code extension can already run the needed workflow on Windows but does not have a documented repeatable launch pattern for workspace + mode + provider profile + prompt file.

Context

This affects Windows users who want to use Roo Code as a focused builder for app projects, especially after reboot or on a new machine. The VS Code extension works well for this, including provider profiles such as openai-codex, but the manual setup involves several clicks: open folder, select custom mode, choose provider/model/reasoning, load or paste a prompt, and start a task.

We validated a local helper approach on Windows with:

• Roo Code extension 3.53.0
• provider openai-codex
• model gpt-5.5
• reasoning effort xhigh
• workspace-local .roomodes
• prompt file handoff
• extension API calls to upsertProfile(...) and startNewTask(...)

Desired Behavior

Roo Code should have a documented Windows-friendly way to reopen a workspace and start a prepared Roo task from project-local configuration. Conceptually, users should be able to initialize or launch a workspace without remembering every UI step.

Constraints / Preferences

• Keep OAuth/sign-in owned by Roo Code. A bootstrapper should not automate or store OAuth secrets.
• Keep secrets out of launch config files.
• Treat this as a VS Code extension path, not a replacement for the Roo CLI.
• The product being built should remain standalone; VS Code/Roo is only the build cockpit.
• A docs-first contribution is probably safest. A later first-class command could absorb the helper-extension behavior.

Request Checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Acceptance Criteria

Given a Windows user with VS Code and Roo Code installed
When they want to use Roo as a repeatable builder for a workspace
Then the docs describe how to use workspace-local .roomodes, a prompt file, and a provider profile to start a task repeatably
And the docs clarify that openai-codex uses Roo/OpenAI Codex auth rather than OPENAI_API_KEY
But the docs do not claim the current CLI installer supports Windows.

Proposed Approach

Add a docs page under the CLI docs that explains the Windows VS Code bootstrap pattern and link it from the CLI README near the installer platform requirements.

Longer term, consider a first-class command such as:

Roo Code: Launch Task From Config

That command could read a workspace-local config, activate a profile, select a mode, and start a new task from a prompt file without requiring a local helper extension.

Trade-offs / Risks

• A documented helper pattern is less polished than a first-class Roo command, but it gives Windows users a useful path immediately.
• A project-local JSON config should be clearly described as a local handoff pattern, not a stable Roo API contract, unless Roo decides to formalize it.

[Mwright413]

Claiming

I have a small docs-only branch prepared locally that links the CLI README to a Windows VS Code bootstrap note. The change is scoped to documenting the pattern; it does not add helper-extension code or change runtime behavior.

[roomote-v0]

I looked into this issue but I see @Mwright413 has already claimed it and has a docs-only branch prepared. I will defer to their work on this one.

If help is needed or the issue becomes available again, I am happy to pick it up. In the meantime, here is a rough outline of what I think the docs contribution should cover, in case it is useful:

1. A new doc page (or section) under the CLI docs describing the Windows VS Code bootstrap pattern using workspace-local .roomodes, a prompt file, and a provider profile.
2. A note in the CLI README near the platform requirements clarifying that the CLI quick installer does not yet support Windows, but linking to the new Windows VS Code bootstrap doc.
3. Clarification that openai-codex uses Roo/OpenAI Codex auth rather than a user-supplied OPENAI_API_KEY.
4. An example workflow showing the steps: open workspace, select custom mode, choose provider/model/reasoning, load prompt file, and start task.

Please mention @roomote if you would like me to proceed with an implementation instead.