feat: add VS Code config generator for GitHub Copilot

[manuliner]

Add new VSCodeConfigGenerator to support GitHub Copilot in VS Code with MCP server integration. Extends the --generate-config CLI command with 'vscode' option.

Changes:

• Add VSCodeConfigGenerator class to config-generator.ts
  • Generates .vscode/mcp.json with MCP server configuration
  • Generates .github/copilot-instructions.md with workflow guidance
  • Follows same factory pattern as existing generators
• Fix async/await handling in CLI (parseCliArgs and runCli)
• Update documentation:
  • README.md: Add vscode to supported agents
  • packages/docs/README.md: Add vscode to quick start
  • packages/docs/user/agent-setup.md: Add VS Code setup instructions
• Update help text to include vscode in supported agents list

Usage:
npx responsible-vibe-mcp --generate-config vscode

This creates a complete VS Code + GitHub Copilot setup with:

• MCP server configured in workspace (.vscode/mcp.json)
• Copilot instructions for workflow guidance (.github/copilot-instructions.md)

Closes: N/A

[mrsimpson]

@manuliner Thanks for the PR!

Since copilot and vscode are actually two independent pieces of software, I'd propose to use a combined enum value (like we have it for amazonq-cli too).

Also, I hope that we don't need those verbose instructions. Q and others work nicely with the compact system prompt.

[mrsimpson]

@manuliner tests fail

[mrsimpson]

Testing it, I found that CoPilot now also supports agent configurations.

.github/agents/vibe.agent.md

---
description: 'Describe what this custom agent does and when to use it.'
tools: ['responsible-vibe-mcp/*']
---
Define what this custom agent accomplishes for the user, when to use it, and the edges it won't cross. Specify its ideal inputs/outputs, the tools it may call, and how it reports progress or asks for help.

I'd prefer to put the system prompt there. WDYT?

[manuliner]

Testing it, I found that CoPilot now also supports agent configurations.

.github/agents/vibe.agent.md

---
description: 'Describe what this custom agent does and when to use it.'
tools: ['responsible-vibe-mcp/*']
---
Define what this custom agent accomplishes for the user, when to use it, and the edges it won't cross. Specify its ideal inputs/outputs, the tools it may call, and how it reports progress or asks for help.

I'd prefer to put the system prompt there. WDYT?

thats an nice idea. Let me try how the agent behaves.

[manuliner]

agent works good

[mrsimpson]

Nice. Does it also find the project docs on its own (manipulating architecture.md etc)?

[mrsimpson]

looks good, except it didn't catch the docs.

Did you see for yourself that it actually creates the plan and works nicely in Coplitot?

lgtm

[mrsimpson]

tests fail.

Other than that, I noticed that in VSCode, the cwd is not set properly. This results in plan files being maintained in the user's home directory, with no proper assignment to a project. We should fix this, maybe even prior to generating the VSCode config

[manuliner]

i am not sure what you experience. I do use RV a few days with the agents file now and it sets up dev plans in the vibe folder. Yes the issue with the docs is correct. As long as i say where the docs are it works. My biggest problem is that even with the Agent.md file i always need to tell the model "use responsible mcp" to start an workflow.

[mrsimpson]

After the renovate-merge-conflict hell, it's finally merged. There are some remaining issues with hard coded cli instructions, but we can fix this separately

[mrsimpson]

Thanks for the contribution, @manuliner !