docs: rewrite user docs, fix modal scroll, webhook URL, and sccache

Rewrite all public documentation to be user-facing only:
- Remove deployment, configuration, and self-hosting sections
- Add guide pages for SBOM, issues, webhooks & PR reviews
- Add reference pages for glossary and tools/scanners
- Add 12 screenshots from live dashboard
- Explain MCP, LLM triage, false positives, human-in-the-loop

Fix edit repository modal not scrollable (max-height + overflow-y).
Show full webhook URL using window.location.origin instead of path.
Unset RUSTC_WRAPPER in agent cargo commands to avoid sccache errors.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

docs/guide/getting-started.md

@@ -1,55 +1,49 @@
 # Getting Started
 
-Compliance Scanner is a security compliance platform that scans your Git repositories for vulnerabilities, builds software bills of materials, performs dynamic application testing, and provides AI-powered code intelligence.
+Certifai is an AI-powered security compliance platform that scans your Git repositories for vulnerabilities, builds software bills of materials, performs dynamic application testing, and provides code intelligence through an interactive knowledge graph and AI chat.
 
-## Architecture
+## What You Get
 
-The platform consists of three main components:
+When you connect a repository, Certifai runs a comprehensive scan pipeline that covers:
 
-- **Agent** — Background service that clones repositories, runs scans, builds graphs, and exposes a REST API
-- **Dashboard** — Web UI built with Dioxus (Rust full-stack framework) for viewing results and managing repositories
-- **MongoDB** — Database for storing all scan results, findings, SBOM data, and graph structures
+- **Static Analysis (SAST)** -- finds code-level vulnerabilities like injection flaws, insecure crypto, and misconfigurations
+- **Software Bill of Materials (SBOM)** -- inventories every dependency, its version, and its license
+- **CVE Monitoring** -- cross-references your dependencies against known vulnerabilities
+- **Code Knowledge Graph** -- maps the structure of your codebase for impact analysis
+- **AI Triage** -- every finding is reviewed by an LLM that provides severity assessment, confidence scores, and remediation guidance
+- **Issue Tracking** -- automatically creates issues in your tracker for new findings
 
-## Quick Start with Docker Compose
+## Dashboard Overview
 
-The fastest way to get running:
+After logging in, you land on the Overview page, which gives you a snapshot of your security posture across all repositories.
 
-```bash
-# Clone the repository
-git clone <repo-url> compliance-scanner
-cd compliance-scanner
+![Dashboard overview showing stats cards, severity distribution, and recent scan activity](/screenshots/dashboard-overview.png)
 
-# Copy and configure environment variables
-cp .env.example .env
-# Edit .env with your settings (see Configuration)
+The overview shows key metrics at a glance: total repositories, findings broken down by severity, dependency counts, CVE alerts, and tracker issues. A severity distribution chart visualizes your risk profile, and recent scan runs let you monitor scanning activity.
 
-# Start all services
-docker-compose up -d
-```
+## Quick Walkthrough
 
-This starts:
-- MongoDB on port `27017`
-- Agent API on port `3001`
-- Dashboard on port `8080`
-- Chromium (for DAST crawling) on port `3003`
+Here is the fastest path from zero to your first scan results:
 
-Open the dashboard at [http://localhost:8080](http://localhost:8080).
+### 1. Add a repository
 
-## What Happens During a Scan
+Navigate to **Repositories** in the sidebar and click **Add Repository**. Enter a name, the Git clone URL, and the default branch to scan.
 
-When you add a repository and trigger a scan, the agent runs through these phases:
+![Add repository dialog](/screenshots/add-repository.png)
 
-1. **Clone** — Clones or pulls the latest code from the Git remote
-2. **SAST** — Runs static analysis using Semgrep with rules for OWASP, GDPR, OAuth, and general security
-3. **SBOM** — Extracts all dependencies using Syft, identifying packages, versions, licenses, and known vulnerabilities
-4. **CVE Check** — Cross-references dependencies against the NVD database for known CVEs
-5. **Graph Build** — Parses the codebase to construct a code knowledge graph of functions, classes, and their relationships
-6. **Issue Sync** — Creates or updates issues in connected trackers (GitHub, GitLab, Jira) for new findings
+### 2. Trigger a scan
 
-Each phase produces results visible in the dashboard immediately.
+Click the **Scan** button on your repository row. The scan runs in the background through all phases: cloning, static analysis, SBOM extraction, CVE checking, graph building, and issue sync.
+
+### 3. View findings
+
+Once the scan completes, navigate to **Findings** to see everything that was discovered. Each finding includes a severity level, description, code evidence, and AI-generated remediation guidance.
+
+![Findings list with filters](/screenshots/findings-list.png)
 
 ## Next Steps
 
-- [Add your first repository](/guide/repositories)
-- [Understand scan results](/guide/findings)
-- [Configure integrations](/guide/configuration)
+- [Add and configure repositories](/guide/repositories) -- including private repos and issue tracker setup
+- [Understand how scans work](/guide/scanning) -- phases, triggers, and deduplication
+- [Work with findings](/guide/findings) -- triage, false positives, and developer feedback
+- [Explore your SBOM](/guide/sbom) -- dependencies, licenses, and exports