docs: add QVAC provider setup guide

[simon-iribarren]

What does this PR do?

Adds a provider setup page for QVAC and registers it in the providers index.

QVAC is an open-source runtime for local-first, peer-to-peer AI. It can expose your local models through an OpenAI-compatible HTTP server (qvac serve openai), so it connects to Roo Code through the existing OpenAI Compatible provider — no new provider code is required.

The page mirrors the format of the other local-provider pages (Ollama, LM Studio) and covers:

• Installing the QVAC CLI (npm i -g @qvac/cli).
• Defining a model alias in qvac.config.json and starting the server (default port 11434).
• Configuring the OpenAI Compatible provider in Roo Code: Base URL http://127.0.0.1:11434/v1, any non-empty API key, and a model id equal to the serve alias.

It also documents the non-obvious settings needed for QVAC to work well as a coding agent:

• Set ctx_size explicitly — the default of 1024 is too small for agent prompts.
• Set "tools": true so the model emits native tool calls instead of plain text (Roo Code uses native tool calling exclusively).
• For reasoning-tuned models such as Qwen3, set "reasoning_budget": 0.
• Tool-calling quality is bounded by the model, so a larger agent-tuned model such as gpt-oss-20b is recommended for local use.

Files changed

• docs/providers/qvac.md — new provider page.
• docs/providers/index.json — registers QVAC so it appears in the sidebar and the provider comparison table.

How was it tested?

Validated index.json, and the new page follows the same structure and frontmatter as the existing local-provider pages. The page uses no images and only absolute, extensionless internal links per the repo's documentation rules.

[vercel]

@simon-iribarren is attempting to deploy a commit to the Roo Code Team on Vercel.

A member of the Team first needs to authorize it.

[simon-iribarren]

Friendly ping @mrubens. This docs PR is mergeable and the Docusaurus build passes. The remaining blocker appears to be the Vercel preview requiring authorization from a Roo Code team member.

Could you take a look or authorize/bypass the preview for this docs-only change?

[simon-iribarren]

@mrubens, could you authorize or bypass the Vercel preview and review this docs-only provider guide? The Docusaurus build passes and the branch is mergeable; deployment authorization is the remaining visible blocker.

[simon-iribarren]

@mrubens quick follow-up on this docs-only provider guide. Docusaurus build is passing; remaining blocker appears to be Vercel preview authorization. Could you authorize/bypass that check and review when possible?