# Virsaitis Usage Guide

## Quick Start

1. **Install the extension**: Sideload the `.vsix` file via Extensions → "..." → "Install from VSIX..."
2. **Open your project**: The extension activates on startup
3. **First run**: The Setup Wizard will guide you through initial configuration

## Daily Workflow

### Protected Files
Files in `.github/` are protected by governance rules. To edit them:
1. Open the Command Palette → "Virsaitis: Request Override"
2. Select the file, reason, and provide justification (min 20 chars)
3. The file becomes temporarily editable

### Secret Scanning
The extension automatically scans saved files for secrets and credentials.
If a secret is detected, the save is reverted and you'll see an error with line numbers.

### Status Bar
The shield icon in the status bar shows governance status:
- 🟢 **Active** — MCP server connected, enforcement active
- 🟡 **Reconnecting** — MCP server restarting
- 🔴 **Error** — MCP server failed (click for options)
- ⚪ **Disabled** — Governance enforcement turned off

### Commands
| Command | Description |
|---------|-------------|
| Install Governance Framework | Set up governance files in workspace |
| Validate Framework | Check installation completeness |
| Update Governance Framework | Update to latest bundled version |
| Configure MCP Server | Generate `.vscode/mcp.json` |
| Request Override | Temporarily unlock a protected file |
| Check Prerequisites | Verify Node.js ≥18 is installed |
| Run Setup Wizard | Re-run the initial setup flow |
| Restart MCP Server | Restart the governance validation server |

## Troubleshooting

### MCP Server won't start
1. Run "Virsaitis: Check Prerequisites" to verify Node.js ≥18
2. Check the Virsaitis output channel (View → Output → Virsaitis)
3. Try "Virsaitis: Restart MCP Server"

### Files are read-only unexpectedly
Protected governance files are intentionally read-only. Use "Request Override" to edit them.

### Extension not activating
Ensure `virsaitis.enabled` is `true` in your VS Code settings.