Skip to content

Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.

feat(website): old docs links land on the matching docs.repowise.dev page (#4238)

Raghav Chamadiyae9879a5c9dd1
diff --git a/.github/doc-drift-baseline.json b/.github/doc-drift-baseline.json
index e2c39eb0e..b65e97ece 100644
--- a/.github/doc-drift-baseline.json
+++ b/.github/doc-drift-baseline.json
@@ -13,6 +13,12 @@
"file_path": "docs/architecture/language-support.md",
"kind": "path",
"target": "packages/core/src/repowise/core/ingestion/languages/specs/mylang.py"
+ },
+ {
+ "fingerprint": "957b0dfa42bee090f7155c9593927766",
+ "file_path": "docs/reference/COMPUTED_GLOSSARY.md",
+ "kind": "path",
+ "target": "docs/index.md"
}
]
}
diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml
index a497b2431..ec57000c4 100644
--- a/.github/workflows/docs.yml
+++ b/.github/workflows/docs.yml
@@ -24,27 +24,13 @@ jobs:
- name: Checkout
uses: actions/checkout@v4
- - name: Setup Ruby
- uses: ruby/setup-ruby@v1
- with:
- ruby-version: "3.3"
- bundler-cache: true
- working-directory: website
-
- name: Setup Pages
- id: pages
uses: actions/configure-pages@v5
- - name: Build with Jekyll
- working-directory: website
- run: bundle exec jekyll build --baseurl "${{ steps.pages.outputs.base_path }}"
- env:
- JEKYLL_ENV: production
-
- name: Upload artifact
uses: actions/upload-pages-artifact@v3
with:
- path: website/_site
+ path: website
deploy:
environment:
diff --git a/packages/core/src/repowise/core/analysis/doc_drift/renderer.py b/packages/core/src/repowise/core/analysis/doc_drift/renderer.py
index a2b2c3a9f..d328ef01c 100644
--- a/packages/core/src/repowise/core/analysis/doc_drift/renderer.py
+++ b/packages/core/src/repowise/core/analysis/doc_drift/renderer.py
@@ -11,13 +11,12 @@ So the class is gated. If a document is published through a renderer whose slug
algorithm this module does not implement, the anchor class stands down for that
document and reports ``uncheckable`` rather than guessing.
-The gate is **per subtree, not per repository.** This repository is why: it
-ships a Jekyll site at ``website/_config.yml`` that publishes the fifteen
-documents under ``website/`` and nothing else. The ``docs/`` tree and
-``.github/CONTRIBUTING.md`` beside it are read on GitHub. A repo-global gate
-reads one marker file and stands the whole class down, losing every real
-finding outside the site directory --- which is exactly what happened the first
-time this ran. A marker governs the directory that contains it, and documents
+The gate is **per subtree, not per repository.** A repo can ship a Jekyll site
+at ``website/_config.yml`` that publishes the documents under ``website/`` and
+nothing else, while the ``docs/`` tree and ``.github/CONTRIBUTING.md`` beside
+it are read on GitHub. A repo-global gate reads one marker file and stands the
+whole class down, losing every real finding outside the site directory. A
+marker governs the directory that contains it, and documents
outside every marked subtree are rendered by the forge.
Adding MkDocs or Docusaurus support later means implementing its slug function
diff --git a/tests/unit/cli/test_agent_matrix.py b/tests/unit/cli/test_agent_matrix.py
index ea696d2a7..c9678b0ad 100644
--- a/tests/unit/cli/test_agent_matrix.py
+++ b/tests/unit/cli/test_agent_matrix.py
@@ -251,8 +251,6 @@ COUNT_CLAIMS: tuple[tuple[str, str, str], ...] = (
),
("docs/start/USER_GUIDE.md", "single_repo", "**{W} tools, task-shaped.**"),
("docs/architecture/pluggable-storage.md", "single_repo", "{w} MCP tools still expose"),
- ("website/mcp-server.md", "total", "It registers {n} tools:"),
- ("website/mcp-server.md", "single_repo", "a curated {n}-tool default surface"),
("packages/server/README.md", "total", "registers {n} MCP tools"),
("packages/server/README.md", "single_repo", "advertises **{n} by default**"),
(".claude-plugin/marketplace.json", "single_repo", "{w} task-shaped MCP tools"),
diff --git a/website/.nojekyll b/website/.nojekyll
new file mode 100644
index 000000000..e69de29bb
diff --git a/website/404.html b/website/404.html
new file mode 100644
index 000000000..68c4540ca
--- /dev/null
+++ b/website/404.html
@@ -0,0 +1,14 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>Repowise docs moved to docs.repowise.dev</title>
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<meta http-equiv="refresh" content="1; url=https://docs.repowise.dev/">
+<link rel="canonical" href="https://docs.repowise.dev/">
+</head>
+<body>
+<h1>Repowise docs moved to docs.repowise.dev</h1>
+<p>This page is now at <a href="https://docs.repowise.dev/">https://docs.repowise.dev/</a>.</p>
+</body>
+</html>
diff --git a/website/Gemfile b/website/Gemfile
deleted file mode 100644
index e6bffb6fc..000000000
--- a/website/Gemfile
+++ /dev/null
@@ -1,6 +0,0 @@
-source "https://rubygems.org"
-
-gem "jekyll", "~> 4.3"
-gem "just-the-docs", "~> 0.10"
-gem "jekyll-seo-tag"
-gem "jekyll-github-metadata"
diff --git a/website/_config.yml b/website/_config.yml
deleted file mode 100644
index 8ad9c8510..000000000
--- a/website/_config.yml
+++ /dev/null
@@ -1,79 +0,0 @@
-title: repowise
-description: Codebase intelligence for developers and AI.
-baseurl: ""
-url: "https://repowise-dev.github.io"
-
-theme: just-the-docs
-
-logo: "/assets/images/logo.png"
-
-# Aux links for the upper right navigation
-aux_links:
- "GitHub":
- - "https://github.com/repowise-dev/repowise"
- "PyPI":
- - "https://pypi.org/project/repowise/"
-
-aux_links_new_tab: true
-
-# Footer content
-footer_content: "Copyright &copy; 2025 repowise. Distributed under the <a href=\"https://github.com/repowise-dev/repowise/blob/main/LICENSE\">AGPL-3.0 License</a>."
-
-# Color scheme
-color_scheme: dark
-
-# Enable search
-search_enabled: true
-search:
- heading_level: 2
- previews: 2
- preview_words_before: 3
- preview_words_after: 3
- tokenizer_separator: /[\s/]+/
- rel_url: true
- button: false
-
-# Navigation
-nav_sort: order
-
-# Callouts
-callouts_level: quiet
-callouts:
- highlight:
- color: yellow
- important:
- title: Important
- color: blue
- new:
- title: New
- color: green
- note:
- title: Note
- color: purple
- warning:
- title: Warning
- color: red
-
-# Back to top button
-back_to_top: true
-back_to_top_text: "Back to top"
-
-# Last edit timestamp
-last_edit_timestamp: true
-last_edit_time_format: "%b %e %Y at %I:%M %p"
-
-# Heading anchors
-heading_anchors: true
-
-# Plugins
-plugins:
- - jekyll-seo-tag
- - jekyll-github-metadata
-
-# Exclude from processing
-exclude:
- - "*.gemspec"
- - "Gemfile"
- - "Gemfile.lock"
- - "node_modules"
- - "vendor"
diff --git a/website/claude-cli.html b/website/claude-cli.html
new file mode 100644
index 000000000..c80f09e4c
--- /dev/null
+++ b/website/claude-cli.html
@@ -0,0 +1,14 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>Repowise docs moved to docs.repowise.dev</title>
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<meta http-equiv="refresh" content="1; url=https://docs.repowise.dev/getting-started/plugins#the-claude_cli-provider">
+<link rel="canonical" href="https://docs.repowise.dev/getting-started/plugins#the-claude_cli-provider">
+</head>
+<body>
+<h1>Repowise docs moved to docs.repowise.dev</h1>
+<p>This page is now at <a href="https://docs.repowise.dev/getting-started/plugins#the-claude_cli-provider">https://docs.repowise.dev/getting-started/plugins#the-claude_cli-provider</a>.</p>
+</body>
+</html>
diff --git a/website/claude-cli.md b/website/claude-cli.md
deleted file mode 100644
index 08754286e..000000000
--- a/website/claude-cli.md
+++ /dev/null
@@ -1,135 +0,0 @@
----
-layout: default
-title: Claude Code Provider
-nav_order: 5.7
----
-
-# Claude Code Provider
-{: .no_toc }
-
-Use Repowise with your Claude subscription via the `claude_cli` LLM provider. No API key — the Claude Code CLI holds the auth.
-{: .fs-6 .fw-300 }
-
----
-
-## Table of contents
-{: .no_toc .text-delta }
-
-1. TOC
-{:toc}
-
----
-
-## Quick setup
-
-```bash
-# 1. Install Claude Code, then authenticate once
-claude auth login
-
-# 2. Point Repowise at it
-repowise init --provider claude_cli --yes
-```
-
-Any plan that can run `claude -p` works — Pro, Max, Team or Enterprise.
-
-To use it on an index you already have:
-
-```bash
-REPOWISE_PROVIDER=claude_cli repowise generate --unwritten
-```
-
-Or persist it in `.repowise/config.yaml`:
-
-```yaml
-provider: claude_cli
-model: claude_cli/claude-haiku-5-5
-```
-
-## Two directions, one name
-
-This page is about Repowise **calling** Claude Code to write your wiki. The
-opposite direction — Claude Code calling Repowise's MCP tools to answer questions
-about your codebase — is the `claude-code` agent target, set up with
-`repowise agents add --target=claude-code`. They are independent; enabling one
-does not enable the other.
-
-## Choosing a model
-
-`claude_cli/claude-haiku-5-5` is the default, matching the `anthropic` provider.
-
-```bash
-repowise init --provider claude_cli --model claude_cli/claude-sonnet-4-6
-```
-
-The `claude_cli/` prefix is optional on input:
-
-```bash
-repowise init --provider claude_cli --model claude-opus-4-6
-```
-
-| Model | Notes |
-|---|---|
-| `claude-haiku-5-5` | Fastest, and ample for doc pages. Default. |
-| `claude-sonnet-4-6` | Better prose, slower. |
-| `claude-opus-4-6` | Highest quality, heaviest on subscription limits. |
-
-## Cost
-
-`claude_cli/*` is priced at **$0.00** in cost estimates and the cost history,
-because a subscription is not per-token API spend. The CLI's own reported cost is
-kept under `usage.reported_cost_usd` for auditing.
-
-The token volume is real and reported: Claude Code splits a prompt across
-`input_tokens` (the uncached remainder), `cache_creation_input_tokens` (a cache
-write) and `cache_read_input_tokens` (a cache read), and only the first is
-usually more than a couple of tokens for a page prompt. Repowise records the sum
-as the run's input tokens, so `repowise status` and `repowise costs` show the
-prompt the model actually read rather than a figure near zero.
-
-What it does consume is your **subscription rate limits**, the same ones your
-interactive Claude Code sessions use. Budget roughly 9k output tokens and a few
-minutes per page. A full wiki on a large repo is a real chunk of usage, so scope
-runs with `--path` rather than reaching for `--all`:
-
-```bash
-repowise generate --path src/api
-```
-
-Concurrency defaults to 4 processes. The variable below overrides it in either
-direction -- lower it if you are hitting limits, and note that raising it past 4
-is allowed but is the quickest way to hit them:
-
-```bash
-REPOWISE_CLAUDE_CLI_CONCURRENCY=2 repowise generate --unwritten
-```
-
-## Reasoning
-
-Claude Code's `--effort` flag maps directly to Repowise's `low`, `medium`,
-`high`, `xhigh`, and `max` reasoning modes. `auto` leaves the flag unset and
-uses the CLI default. The unsupported `off`, `none`, and `minimal` modes log a
-warning and proceed with the default rather than failing the run.
-
-## Embeddings are separate
-
-Anthropic has no embeddings API, so `claude_cli` cannot serve as an embedder. If
-you want semantic search rather than keyword-only, pick an embedder separately:
-
-```bash
-repowise init --provider claude_cli --embedder ollama # local, no key
-```
-
-Otherwise the index keeps `embedder: mock` and search stays lexical.
-
-## Troubleshooting
-
-**`Claude Code CLI not found`** — `claude` is not on `PATH`. Install it from
-[claude.com/claude-code](https://claude.com/claude-code).
-
-**Authentication errors on the first page** — run `claude auth login`, then
-check with `claude auth status`, which exits 0 when you are signed in. That is
-the check `repowise init` uses to show the provider as ready.
-
-**Rate-limit failures partway through a run** — lower
-`REPOWISE_CLAUDE_CLI_CONCURRENCY`, or scope the run with `--path`. Completed
-pages are kept, so re-running picks up where it stopped with `--unwritten`.
diff --git a/website/claude-code-plugin.html b/website/claude-code-plugin.html
new file mode 100644
index 000000000..c0f848429
--- /dev/null
+++ b/website/claude-code-plugin.html
@@ -0,0 +1,14 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>Repowise docs moved to docs.repowise.dev</title>
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<meta http-equiv="refresh" content="1; url=https://docs.repowise.dev/getting-started/plugins#claude-code-plugin">
+<link rel="canonical" href="https://docs.repowise.dev/getting-started/plugins#claude-code-plugin">
+</head>
+<body>
+<h1>Repowise docs moved to docs.repowise.dev</h1>
+<p>This page is now at <a href="https://docs.repowise.dev/getting-started/plugins#claude-code-plugin">https://docs.repowise.dev/getting-started/plugins#claude-code-plugin</a>.</p>
+</body>
+</html>
diff --git a/website/claude-code-plugin.md b/website/claude-code-plugin.md
deleted file mode 100644
index a7f6b2847..000000000
--- a/website/claude-code-plugin.md
+++ /dev/null
@@ -1,269 +0,0 @@
----
-layout: default
-title: Claude Code Plugin
-nav_order: 8
----
-
-# Claude Code Plugin
-{: .no_toc }
-
-The fastest way to get repowise — Claude handles everything.
-{: .fs-6 .fw-300 }
-
----
-
-## Table of contents
-{: .no_toc .text-delta }
-
-1. TOC
-{:toc}
-
----
-
-## Overview
-
-The Claude Code plugin integrates repowise directly into Claude Code. It handles installation, API key setup, MCP server registration, and teaches Claude to use repowise tools proactively — without manual configuration.
-
----
-
-## Installation
-
-Open Claude Code and run:
-
-```
-/plugin marketplace add repowise-dev/repowise
-/plugin install repowise@repowise
-```
-
-That's the entire installation. The plugin:
-
-- Installs `repowise` via pip if not already installed
-- Registers the MCP server with Claude Code
-- Loads the slash commands
-- Configures Claude to use repowise tools automatically
-
----
-
-## Slash commands
-
-### `/repowise:init`
-
-Interactive setup and indexing for the current repository.
-
-Claude will guide you through:
-
-1. **Mode selection** — choose between:
- - **Full** — complete wiki generation with LLM docs (requires API key)
- - **Index-only** — graph + git + dead code + code health, no LLM (free)
- - **Advanced** — manual control over provider, concurrency, exclude patterns
-
-2. **Provider selection** — Anthropic, OpenAI, Gemini, Codex CLI, OpenCode, or local Ollama
-
-3. **API key entry** — saved to `.repowise/.env` (gitignored) when a hosted provider needs one
-
-4. **Indexing** — runs in the background with live progress updates
-
-When done, Claude confirms the MCP server is active and the codebase is queryable.
-
----
-
-### `/repowise:status`
-
-Show the current state of the repowise index.
-
-Output includes:
-- Last sync commit and timestamp
-- Total pages, symbols, decisions indexed
-- Provider and model in use
-- Pages marked stale (need regeneration)
-- MCP server connection status
-
----
-
-### `/repowise:update`
-
-Incrementally sync the wiki after code changes.
-
-Claude detects which files have changed since the last indexed commit, regenerates only the affected pages, updates CLAUDE.md, and confirms when done.
-
----
-
-### `/repowise:search`
-
-Search the indexed wiki from within Claude Code.
-
-Claude will ask for your query and search mode (fulltext, semantic, or symbol), then display results inline with links to relevant pages.
-
----
-
-### `/repowise:ask`
-
-Ask a codebase question and get a cited, synthesised answer (`repowise ask`).
-This is the CLI adapter over the `get_answer` MCP tool — hybrid retrieval plus
-an LLM answer — so it costs a model call where `/repowise:search` does not.
-
-Use it when you want an answer with confidence and citations, not a hit list.
-`--scope` restricts retrieval to a path prefix; `--format json` / `--full`
-match the other tool-adapter commands.
-
----
-
-### `/repowise:context`
-
-Triage card for files, modules, or symbols (`repowise context`). CLI adapter
-over `get_context`: architectural layer, hotspot / fix history, doc freshness,
-and optional relationship blocks (`--include callers`, `skeleton`, …). Batch
-targets in one call. No source bytes by default — use `/repowise:symbol` for
-exact bodies.
-
----
-
-### `/repowise:symbol`
-
-Read one symbol body with live-verified line bounds (`repowise symbol`). CLI
-adapter over `get_symbol`. Accepts `path/to/file.py::Name`, a live range
-(`path:start-end`), or a `repowise#<hex>` distill omission ref.
-`--context-lines` adds surrounding lines; a truncated body returns a
-`continuation` you can pass straight back.
-
----
-
-### `/repowise:reindex`
-
-Rebuild the vector search index without making LLM calls.
-
-Use this after switching embedding providers, or if semantic search results seem off.
-
----
-
-### `/repowise:health`
-
-Code-health KPIs, lowest-scoring files, refactoring targets, or trends
-(`repowise health`).
-
----
-
-### `/repowise:risk`
-
-Repo-relative review percentile/classification with a supporting diff-shape score (`repowise risk`).
-
----
-
-### `/repowise:security`
-
-Full-history secret scan (`repowise security scan --history`). Working-tree
-scanning already runs during init/update; without `--history` the CLI only
-prints a hint. Default history mode is secrets-only; `--all-patterns` also
-reports code-smell patterns.
-
----
-
-### `/repowise:coverage`
-
-Ingest or inspect coverage reports (`repowise coverage add` / `status`).
-Lights up untested-hotspot markers and builds the per-test map when contexts
-are present.
-
----
-
-### `/repowise:impacted-tests`
-
-Tests whose coverage intersects a change (`repowise impacted-tests`).
-
----
-
-### `/repowise:dead-code`
-
-Unreachable files, unused exports, and zombie packages by confidence.
-
----
-
-### `/repowise:export`
-
-Export wiki pages or the architecture model (`repowise export`). Formats:
-`markdown` (default), `html`, `json`, and `structurizr`. JSON `--full` keeps
-tombstones and adds decisions / dead code / hotspots. Structurizr can emit a
-model fragment or a `--standalone` workspace (`--components`,
-`--no-externals`, `--force`).
-
----
-
-### `/repowise:decision`
-
-List, inspect, add, or confirm architectural decisions.
-
----
-
-### `/repowise:why`
-
-Why the code is shaped this way (`repowise why`). CLI adapter over `get_why`:
-decision search by question, governing decisions + origin story for a path,
-target-anchored search (`--target`), or the decision-health dashboard with no
-args. Falls back to git archaeology when no decision is recorded.
-`/repowise:decision` manages records; this command queries them.
-
----
-
-### `/repowise:doctor`
-
-Diagnose (and optionally repair) setup, keys, and index drift.
-
----
-
-## Automatic behaviors
-
-Beyond the slash commands, the plugin teaches Claude skills it uses automatically — without being asked.
-
-### Codebase exploration
-
-Before reading raw source files, Claude calls:
-
-- `get_overview()` at the start of new tasks to orient itself
-- `get_answer(question)` for direct how/where/why questions
-- `search_codebase(query)` to locate code instead of using grep
-- `get_context(targets)` to get docs and ownership before opening files
-
-### Pre-modification checks
-
-Before editing any file, Claude calls `get_risk(targets)` to assess:
-
-- Bug-fix history (`defect_profile` / `bug_magnet`) when present
-- Whether the file is a hotspot (high churn)
-- How many other files depend on it
-- Whether there are co-change patterns to be aware of
-
-If the risk is high, Claude surfaces this before making changes.
-
-### Change review
-
-For a PR / branch / working-tree diff, Claude combines `get_change_risk` (whole-change score) with `get_risk`'s per-file `directive` block.
-
-### Code health
-
-Quality / complexity / "what to refactor" questions go through `get_health`.
-
-### Architectural decision queries
-
-When facing "why is this structured this way" questions, Claude calls `get_why(query)` to check decision records and git archaeology before suggesting changes that might conflict with existing decisions.
-
-### Dead code awareness
-
-During refactoring or cleanup tasks, Claude calls `get_dead_code()` to find confirmed unused code rather than guessing.
-
----
-
-## How skills work
-
-Skills in Claude Code are prompt instructions that modify Claude's behavior. The repowise plugin registers six skills that Claude loads when working in an indexed repo.
-
-You don't need to trigger them manually. When Claude detects it's working in a repo with a connected repowise MCP server, the skills activate automatically.
-
-The CLAUDE.md generator reinforces these skills by writing the mandatory MCP tool workflow directly into your project's context file — so even without the plugin, any Claude session that reads your CLAUDE.md will follow the same workflow.
-
----
-
-## Requirements
-
-- Claude Code (desktop app, CLI, or IDE extension)
-- Python 3.11+
-- An LLM API key (for full mode — not needed for index-only)
diff --git a/website/claude-md-generator.html b/website/claude-md-generator.html
new file mode 100644
index 000000000..184caf817
--- /dev/null
+++ b/website/claude-md-generator.html
@@ -0,0 +1,14 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>Repowise docs moved to docs.repowise.dev</title>
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<meta http-equiv="refresh" content="1; url=https://docs.repowise.dev/cli/other#repowise-generate-claude-md">
+<link rel="canonical" href="https://docs.repowise.dev/cli/other#repowise-generate-claude-md">
+</head>
+<body>
+<h1>Repowise docs moved to docs.repowise.dev</h1>
+<p>This page is now at <a href="https://docs.repowise.dev/cli/other#repowise-generate-claude-md">https://docs.repowise.dev/cli/other#repowise-generate-claude-md</a>.</p>
+</body>
+</html>
diff --git a/website/claude-md-generator.md b/website/claude-md-generator.md
deleted file mode 100644
index 00ea61db3..000000000
--- a/website/claude-md-generator.md
+++ /dev/null
@@ -1,149 +0,0 @@
----
-layout: default
-title: CLAUDE.md Generator
-nav_order: 7
----
-
-# CLAUDE.md Generator
-{: .no_toc }
-
-How repowise keeps Claude Code informed about your codebase automatically.
-{: .fs-6 .fw-300 }
-
----
-
-## Table of contents
-{: .no_toc .text-delta }
-
-1. TOC
-{:toc}
-
----
-
-## What it is
-
-Claude Code reads `.claude/CLAUDE.md` at startup to understand the project it's working in. repowise generates this file from your indexed codebase — filling it with architecture summaries, hotspot warnings, module maps, MCP tool instructions, and codebase conventions.
-
-The result is a Claude that understands your repo's structure, knows which files are risky to edit, and uses the right tools before making changes.
-
----
-
-## How it's generated
-
-The generator runs at the end of `repowise init` and `repowise update`, or on demand:
-
-```bash
-repowise generate-claude-md
-```
-
-It queries the already-indexed database — **no LLM calls are made**. All content comes from data collected during ingestion and analysis.
-
-What goes into the generated content:
-
-| Section | Source |
-|---------|--------|
-| Architecture summary | Repository-level wiki page (4 sentences max) |
-| Key modules | Top modules by PageRank with purpose and owner |
-| Entry points | Detected `main.py`, `__main__`, CLI entry files |
-| Tech stack | Languages, frameworks, databases, infra |
-| Hotspots | Top 5 high-churn files with percentile rank |
-| MCP tool instructions | Mandatory usage table for the default MCP tool surface |
-| Codebase conventions | Active architectural decisions + build commands |
-
----
-
-## Two-section design
-
-The file is split into two sections with clear markers:
-
-```markdown
-# CLAUDE.md
-
-<!-- Add your custom instructions here. repowise will never
- modify anything outside the markers below. -->
-<!-- Examples: coding style, test commands, constraints -->
-
-Your custom content goes here and is never touched.
-
-<!-- REPOWISE:START — Do not edit below this line. Auto-generated by repowise. -->
-
-## IMPORTANT: Codebase Intelligence Instructions for my-repo
-
-> **CRITICAL**: This repository is indexed by repowise.
-> You MUST use the repowise MCP tools below instead of reading raw source files.
-
-... auto-generated content ...
-
-<!-- REPOWISE:END -->
-```
-
-**Your section (above the markers):** Add anything you want — coding style rules, test commands, workflow preferences, constraints. repowise never touches this.
-
-**repowise section (between markers):** Fully auto-generated. Updated on every `repowise update` run. Never edit this manually — changes will be overwritten.
-
----
-
-## Merge behavior
-
-The generator handles three cases:
-
-| Scenario | Behavior |
-|---------|----------|
-| No existing file | Creates file with empty user section + repowise section |
-| File without markers | Appends repowise section at the bottom, preserves all existing content |
-| File with markers | Replaces only the content between markers, preserves everything outside |
-
-Updates are written atomically via a temp file — if something goes wrong mid-write, the original file is not corrupted.
-
----
-
-## What Claude does with it
-
-When Claude Code opens your project, it reads CLAUDE.md and sees:
-
-1. **The MCP tool instructions** — a mandatory workflow table telling Claude to call `get_overview()` first, `get_context()` before reading files, `get_risk()` before edits, etc.
-
-2. **The hotspot warning** — a table of high-churn files with their percentile ranks and owners, so Claude knows which files need extra care.
-
-3. **The architecture summary** — enough context to understand the repo without reading every file.
-
-4. **Codebase conventions** — active architectural decisions that should be respected.
-
-This is why Claude Code performs better on indexed repos — it has the same mental model a senior engineer would have after a few weeks on the project.
-
----
-
-## Auto-sync on commits
-
-If you're using `repowise watch`, CLAUDE.md is updated automatically whenever indexed files change.
-
-For manual sync after coding sessions:
-
-```bash
-repowise update # Updates wiki + regenerates CLAUDE.md
-repowise generate-claude-md # Regenerates CLAUDE.md only (faster)
-```
-
-In Claude Code, run `/repowise:update` to trigger an update from within your editor.
-
----
-
-## Opting out
-
-To skip CLAUDE.md generation entirely during `init`:
-
-```bash
-repowise init --no-claude-md
-```
-
-To generate the content without writing a file (for inspection):
-
-```bash
-repowise generate-claude-md --stdout
-```
-
-To write to a custom path:
-
-```bash
-repowise generate-claude-md --output ./my-custom-context.md
-```
diff --git a/website/cli-reference.html b/website/cli-reference.html
new file mode 100644
index 000000000..be12c3108
--- /dev/null
+++ b/website/cli-reference.html
@@ -0,0 +1,14 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>Repowise docs moved to docs.repowise.dev</title>
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<meta http-equiv="refresh" content="1; url=https://docs.repowise.dev/cli/overview">
+<link rel="canonical" href="https://docs.repowise.dev/cli/overview">
+</head>
+<body>
+<h1>Repowise docs moved to docs.repowise.dev</h1>
+<p>This page is now at <a href="https://docs.repowise.dev/cli/overview">https://docs.repowise.dev/cli/overview</a>.</p>
+</body>
+</html>
diff --git a/website/cli-reference.md b/website/cli-reference.md
deleted file mode 100644
index b3509169b..000000000
--- a/website/cli-reference.md
+++ /dev/null
@@ -1,859 +0,0 @@
----
-layout: default
-title: CLI Reference
-nav_order: 4
----
-
-# CLI Reference
-{: .no_toc }
-
-Every command, flag, and option.
-{: .fs-6 .fw-300 }
-
----
-
-## Table of contents
-{: .no_toc .text-delta }
-
-1. TOC
-{:toc}
-
----
-
-## Global
-
-```bash
-repowise --version # Print version
-repowise --help # Show help
-repowise COMMAND --help # Help for a specific command
-```
-
-Most commands accept an optional `PATH` argument — the root of the repository to operate on. If omitted, the current directory is used.
-
----
-
-## `init`
-
-Generate the full wiki for a codebase. Runs all four layers: ingestion, analysis, generation, persistence.
-
-```bash
-repowise init [PATH] [OPTIONS]
-```
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--provider` | string | auto | LLM provider: `anthropic`, `openai`, `openrouter`, `gemini`, `deepseek`, `kimi`, `ollama`, `litellm`, `codex_cli`, `opencode`, `edenai`, `mock` |
-| `--model` | string | — | Model override (e.g., `claude-sonnet-4-6`, `gpt-4.1`) |
-| `--embedder` | choice | auto | Embedding provider: `gemini`, `openai`, `mock` |
-| `--prose` / `--no-prose` | flag | prose if a key | Write the subsystem (concept) pages as model prose (`--prose`, needs a key), or render the whole wiki from structure with no model and no spend (`--no-prose`). Every other page is structural either way. |
-| `--index-only` / `--docs` | — | — | Deprecated hidden aliases. `--index-only` == `--no-prose`; `--docs llm` == `--prose`, `--docs deterministic` == `--no-prose`. |
-| `--dry-run` | flag | false | Show generation plan and token estimate without running |
-| `--test-run` | flag | false | Limit to top 10 files by PageRank (for validation) |
-| `--skip-tests` | flag | false | Exclude test files |
-| `--skip-infra` | flag | false | Exclude Dockerfiles, Makefiles, Terraform, shell scripts |
-| `--exclude` / `-x` | string | — | Gitignore-style exclude pattern (repeatable: `-x vendor/ -x "*.gen.*"`) |
-| `--include-submodules` | flag | false | Include git submodule directories (excluded by default) |
-| `--concurrency` | int | 5 | Max concurrent LLM calls |
-| `--reasoning` | choice | auto | Reasoning mode for supported providers: `auto`, `off`/`none`, `minimal`, `low`, `medium`, `high`, `xhigh`, or `max` |
-| `--resume` | flag | false | Resume from last checkpoint after an interruption |
-| `--force` | flag | false | Regenerate all pages even if up to date |
-| `--commit-limit` | int | 5000 | Max commits per file for git analysis (max 10000, saved to config) |
-| `--follow-renames` | flag | false | Track file renames in git history (saved to config) |
-| `--no-claude-md` | flag | false | Skip generating `.claude/CLAUDE.md` |
-| `--agents` / `--no-agents` | flag | config | Generate or skip managed `AGENTS.md` for Codex |
-| `--codex` / `--no-codex` | flag | prompt/skip | Generate or skip project-local Codex MCP config and hooks |
-| `--distill-hook` / `--no-distill-hook` | flag | prompt/skip | Install or skip the Claude Code command-rewrite hook that routes noisy commands through `repowise distill` |
-| `--hook` / `--no-hook` | flag | on | Install or skip the post-commit hook that runs `repowise update` after each commit. Interactive runs ask; `--yes` and non-interactive runs install it and print how to undo it |
-| `--editor-setup` / `--no-editor-setup` | flag | true | Register the MCP server and hooks in your global Claude Code / Claude Desktop config. `--no-editor-setup` indexes the repo and leaves everything outside it untouched |
-| `--yes` / `-y` | flag | false | Skip the cost confirmation prompt |
-
-### Examples
-
-```bash
-# Interactive setup (recommended for first run)
-repowise init
-
-# Non-interactive, specific provider
-repowise init --provider anthropic --yes
-
-# Use the authenticated local Codex CLI
-repowise init --provider codex_cli --codex --yes
-repowise init --provider opencode --yes
-
-# OpenAI-compatible Qwen3 endpoint with thinking disabled
-repowise init --provider openai --model qwen3 --reasoning off
-
-# OpenRouter with minimal reasoning effort
-repowise init --provider openrouter --model openai/gpt-5 --reasoning minimal
-
-# Analysis plus a structural wiki, free, no API key needed
-repowise init --no-prose
-
-# Skip tests and infra, limit concurrency
-repowise init --skip-tests --skip-infra --concurrency 3
-
-# Exclude generated files and vendor directories
-repowise init -x "*.generated.ts" -x vendor/ -x proto/
-
-# Repo with git submodules — include them in indexing
-repowise init --include-submodules
-
-# Dry run to estimate cost before committing
-repowise init --dry-run
-
-# Resume an interrupted run
-repowise init --resume
-```
-
-### What it does
-
-1. **Ingestion** — parses all files with tree-sitter, builds dependency graph
-2. **Analysis** — git churn/ownership, dead code detection, decision mining
-3. **Generation** — every page is rendered from parsed structure; with a model (the default when a key is available) the subsystem (concept) pages are written as prose instead of stubs. `--no-prose` keeps them structural.
-4. **Persistence** — writes to SQLite, builds vector index, generates managed editor instruction files
-
-### Provider auto-detection
-
-If `--provider` is not specified, repowise checks in order:
-1. `REPOWISE_PROVIDER` environment variable
-2. `.repowise/config.yaml` from a previous run
-3. API key environment variables: `ANTHROPIC_API_KEY` → `OPENAI_API_KEY` → `OPENROUTER_API_KEY` → `OLLAMA_BASE_URL` → `GEMINI_API_KEY` → `DEEPSEEK_API_KEY` → `KIMI_API_KEY` → `EDENAI_API_KEY`
-
----
-
-## `update`
-
-Incrementally sync the wiki after code changes. Diffs against the last indexed commit, regenerates only affected pages.
-
-```bash
-repowise update [PATH] [OPTIONS]
-```
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--provider` | string | — | Override LLM provider |
-| `--model` | string | — | Override model |
-| `--since` | string | — | Git ref to diff from (overrides saved `state.json`) |
-| `--reasoning` | choice | auto | Reasoning mode for supported providers: `auto`, `off`/`none`, `minimal`, `low`, `medium`, `high`, `xhigh`, or `max` |
-| `--cascade-budget` | int | auto | Max pages to regenerate from cascading changes |
-| `--dry-run` | flag | false | Show affected pages without regenerating |
-| `--agents` / `--no-agents` | flag | config | Generate or skip managed `AGENTS.md` after update |
-
-### Examples
-
-```bash
-repowise update # Sync since last indexed commit
-repowise update --since HEAD~10 # Re-sync last 10 commits
-repowise update --reasoning off # One-off supported-provider thinking-off run
-repowise update --dry-run # Preview what would change
-repowise update --cascade-budget 20 # Limit cascade regeneration
-```
-
----
-
-## `watch`
-
-Auto-update wiki on file saves. Watches for filesystem changes and debounces rapid saves.
-
-```bash
-repowise watch [PATH] [OPTIONS]
-```
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--provider` | string | — | Override LLM provider |
-| `--model` | string | — | Override model |
-| `--debounce` | int | 2000 | Debounce delay in milliseconds |
-
-### Example
-
-```bash
-repowise watch --debounce 3000 # Wait 3 seconds after last save before updating
-```
-
----
-
-## `mcp`
-
-Start the MCP server for AI editor integration.
-
-```bash
-repowise mcp [PATH] [OPTIONS]
-```
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--transport` | choice | stdio | `stdio` (for editors), `streamable-http` (for HTTP clients), or `sse` (legacy) |
-| `--port` | int | 7338 | Port for HTTP/SSE transports |
-
-### Examples
-
-```bash
-repowise mcp # stdio (Claude Code, Cursor, Cline)
-repowise mcp --transport streamable-http # HTTP on port 7338
-repowise mcp --transport sse --port 7338 # legacy SSE
-```
-
-See [MCP Server →](mcp-server) for editor-specific configuration.
-
----
-
-## `serve`
-
-Start the API server and web dashboard.
-
-```bash
-repowise serve [PATH] [OPTIONS]
-```
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--port` | int | 7337 | API server port |
-| `--host` | string | 127.0.0.1 | Host to bind |
-| `--workers` | int | 1 | Number of uvicorn workers |
-| `--ui-port` | int | 3000 | Web UI port |
-| `--no-ui` | flag | false | Start API only, skip web UI |
-
-### Examples
-
-```bash
-repowise serve # API on :7337, UI on :3000
-repowise serve --no-ui # API only
-repowise serve --host 0.0.0.0 # Expose on network
-repowise serve --port 8080 --ui-port 4000 # Custom ports
-```
-
-See [Web Dashboard →](web-dashboard) for what you can do from the UI.
-
----
-
-## `search`
-
-Full-text, semantic, or symbol search across the indexed wiki.
-
-```bash
-repowise search <QUERY> [PATH] [OPTIONS]
-```
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--mode` | choice | fulltext | `fulltext`, `semantic`, or `symbol` |
-| `--limit` | int | 10 | Max results |
-
-### Examples
-
-```bash
-repowise search "authentication flow"
-repowise search "rate limiting" --mode semantic
-repowise search "AuthService" --mode symbol
-repowise search "database connection" --limit 20
-```
-
-For a synthesised answer rather than a keyword lookup, use [`ask`](#ask).
-
----
-
-## `ask`
-
-Answer a question about the codebase, with citations. The same synthesis the
-`get_answer` MCP tool performs: hybrid retrieval followed by an LLM answer over
-what it found, so this command costs an LLM call where the other query commands
-do not.
-
-```bash
-repowise ask <QUESTION> [OPTIONS]
-```
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--scope` | string | — | Restrict retrieval to a path prefix (e.g. `packages/cli/`) |
-| `--path` | string | cwd | Repo (or workspace) root |
-| `--repo` | string | — | Workspace repo alias to query |
-| `--no-workspace` | flag | false | Force single-repo mode even inside a workspace |
-| `--format` | choice | table | `table` or `json` |
-| `--full` | flag | false | Emit the raw MCP tool payload |
-
-### Examples
-
-```bash
-repowise ask "how does the retry backoff work?"
-repowise ask "where is the session cookie set?" --format json
-repowise ask "how is width resolved?" --scope packages/cli/
-repowise ask "why is auth split across two modules?" --full
-```
-
-`confidence: high` is content-grounded, so it can be cited directly. A
-low-confidence answer returns `best_guesses` instead of going silent.
-
-Also available as the Claude Code slash command `/repowise:ask`.
-
----
-
-## `context`
-
-Triage card for files, modules or symbols: title, summary, architectural layer,
-hotspot and bug-fix history, doc freshness, and the shape of the verified
-skeleton. Relationships and risk signals, not source bytes. Batch targets in one
-call.
-
-```bash
-repowise context <TARGETS...> [OPTIONS]
-```
-
-TARGETS are file paths, module paths, or `path/to/file.py::Symbol` ids.
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--include` | choice | — | Opt-in block, repeatable: `full_doc`, `ownership`, `last_change`, `callers`, `callees`, `metrics`, `community`, `decisions`, `health`, `skeleton`, `doc_drift` |
-| `--no-compact` | flag | false | Add structure, imports and docstrings to each card |
-| `--path` | string | cwd | Repo (or workspace) root |
-| `--repo` | string | — | Workspace repo alias to query |
-| `--no-workspace` | flag | false | Force single-repo mode even inside a workspace |
-| `--format` | choice | table | `table` or `json` |
-| `--full` | flag | false | Emit the raw MCP tool payload |
-
-### Examples
-
-```bash
-repowise context src/api/routes.py src/api/auth.py
-repowise context src/api/routes.py::login --include callers --include metrics
-repowise context src/api/routes.py --include skeleton # + the file's source shape
-```
-
-Pass `--include skeleton` for the whole file body-elided and line-verified, or
-use [`symbol`](#symbol) for one function body. Also available as `/repowise:context`.
-
----
-
-## `symbol`
-
-Read one function, class or constant with live-verified line bounds. `source`
-arrives in the same line-numbered format a file read produces; `verified: true`
-means the bounds were checked against the live file.
-
-```bash
-repowise symbol <SYMBOL_ID> [OPTIONS]
-```
-
-`SYMBOL_ID` is `path/to/file.py::Name` (as `repowise context` reports it),
-`path/to/file.py:140-180` for a live range read, or a `repowise#<hex>`
-omission ref from a distilled command.
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--context-lines` | int | 0 | Extra lines before and after the body (0–50) |
-| `--query` | string | — | Omission refs only: regex or substring filter on restored lines |
-| `--path` | string | cwd | Repo (or workspace) root |
-| `--repo` | string | — | Workspace repo alias to query |
-| `--no-workspace` | flag | false | Force single-repo mode even inside a workspace |
-| `--format` | choice | table | `table` or `json` |
-| `--full` | flag | false | Emit the raw MCP tool payload |
-
-### Examples
-
-```bash
-repowise symbol "src/api/routes.py::login"
-repowise symbol "src/api/routes.py:140-180" # live range read
-repowise symbol "repowise#a1b2c3d4e5f6" # a distill omission ref
-```
-
-An ambiguous id returns every matching body rather than silently picking one.
-A truncated body carries a `continuation` you can pass straight back.
-Also available as `/repowise:symbol`.
-
----
-
-## `why`
-
-Why the code is shaped this way: decision records, rationale and git
-archaeology. Worth running before a refactor or a deliberate divergence from a
-pattern.
-
-```bash
-repowise why [QUERY] [OPTIONS]
-```
-
-QUERY is a question (`why is auth using JWT?`), a file path (its governing
-decisions, origin story and alignment score), or omitted for the
-decision-health dashboard.
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--target` | string | — | File path to anchor the search to (repeatable) |
-| `--path` | string | cwd | Repo (or workspace) root |
-| `--repo` | string | — | Workspace repo alias to query |
-| `--no-workspace` | flag | false | Force single-repo mode even inside a workspace |
-| `--format` | choice | table | `table` or `json` |
-| `--full` | flag | false | Emit the raw MCP tool payload |
-
-### Examples
-
-```bash
-repowise why "why is auth using JWT?" # question
-repowise why src/api/auth.py # governing decisions + origin story
-repowise why "why the retry cap?" --target src/api/client.py
-repowise why # decision health dashboard
-```
-
-Falls back to git archaeology when a path has no decisions, so it is never
-empty. Also available as `/repowise:why`. Use `repowise decision` /
-`/repowise:decision` to manage the records themselves.
-
----
-
-## `reindex`
-
-Rebuild the vector search index from existing wiki pages. Does not make LLM calls.
-
-```bash
-repowise reindex [PATH] [OPTIONS]
-```
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--embedder` | choice | auto | `gemini`, `openai`, or `auto` |
-| `--batch-size` | int | 20 | Pages per embedding batch |
-
-Use this after switching embedding providers, or if the LanceDB index is corrupted.
-
----
-
-## `status`
-
-Show the current sync state, page counts, and provider info.
-
-```bash
-repowise status [PATH]
-```
-
-Output includes:
-- Last indexed commit and timestamp
-- Total pages, symbols, and decisions
-- Provider and model in use
-- Total tokens consumed
-- Index freshness (pages marked stale)
-
----
-
-## `doctor`
-
-Run health checks on the wiki setup.
-
-```bash
-repowise doctor [PATH]
-```
-
-Checks:
-- Database connectivity and schema version
-- Vector store consistency (pages without embeddings)
-- Stale pages that need regeneration
-- Missing or broken `.mcp.json` config
-- API key availability for configured provider
-
----
-
-## `dead-code`
-
-Detect and report unused code in the indexed codebase.
-
-```bash
-repowise dead-code [PATH] [OPTIONS]
-```
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--min-confidence` | float | 0.5 | Minimum confidence threshold (0.0–1.0) |
-| `--safe-only` | flag | false | Only show findings marked `safe_to_delete` |
-| `--kind` | choice | — | Filter by type: `unreachable_file`, `unused_export`, `unused_internal`, `zombie_package` |
-| `--format` | choice | table | Output format: `table`, `json`, or `md` |
-
-### Examples
-
-```bash
-repowise dead-code # All findings, table format
-repowise dead-code --safe-only # Only confirmed safe to delete
-repowise dead-code --kind unused_export # Only unused exports
-repowise dead-code --format json # Machine-readable output
-repowise dead-code --min-confidence 0.8 # High confidence only
-```
-
----
-
-## `health`
-
-Compute per-file code-health scores from deterministic markers. No LLM by
-default.
-
-```bash
-repowise health [PATH] [OPTIONS]
-```
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--file` | string | — | Deep-dive a single file (relative path) |
-| `--module` | string | — | Restrict to files whose path starts with this prefix |
-| `--scope` | choice | all | `all` or `production`. Tests score higher than production code, so narrowing lowers every figure without a defect being found |
-| `--counts` | choice | everything | `everything` or `code_shape`. `code_shape` removes the git-derived half of the score, which rises as a file is worked on |
-| `--refactoring-targets` | flag | false | Ranked refactoring candidates by impact/effort |
-| `--trend` | flag | false | Last health snapshots + declining alerts |
-| `--badge` | flag | false | Ready-to-paste health badge Markdown |
-| `--format` | choice | table | `table`, `json`, or `md` |
-| `--generate-code` | string | — | Opt-in LLM refactoring patch for one target (needs a provider) |
-
-### Examples
-
-```bash
-repowise health
-repowise health --refactoring-targets
-repowise health --file packages/server/app.py
-repowise health --trend
-```
-
----
-
-## `risk`
-
-Rank a *change* (commit or `base..head` range) by size and spread among the
-repo's recent commits, then report the bug-fix record of the files it touches.
-The percentile ranks diff size, not danger; the supporting 0-10 score measures
-diff size and spread and is not a probability. No LLM.
-
-```bash
-repowise risk [REVSPEC] [OPTIONS]
-```
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--path` | path | cwd | Git repository path |
-| `--ext` | string | all | Comma-separated suffixes to count (e.g. `.py,.ts`) |
-| `-x, --exclude` | pattern | — | Gitignore-style exclude (repeatable) |
-| `--format` | choice | table | `table` or `json` |
-
-### Examples
-
-```bash
-repowise risk # score uncommitted work, else HEAD
-repowise risk HEAD # score the last commit
-repowise risk main..HEAD # score a branch / PR range
-repowise risk --ext .ts,.tsx
-```
-
-With a readable index the command also prints whether the diff is one change or
-several: the changed files grouped by the links the index holds plus, for a
-`base..head` range, the files each commit touched. Only indexed, non-test source
-files a resolver can link are grouped; docs, config, data and tests are always
-printed under `Left out of the grouping:`. Each group names its files and the
-files that alone hold it together, and a closing `Basis:` line says what was
-checked. Silent when the diff is one change, and it carries no score.
-
----
-
-## `overlap`
-
-Which other open branches edit the files this change edits. Git answers it, so it
-works with no index; an index orders the shared files and adds the files history
-pairs with them. Every row states its basis in words, `same file` or
-`co-change pair, N of M commits`. No score. Branches stacked on the current one
-are skipped, as are noise paths and dependency manifests.
-
-```bash
-repowise overlap [OPTIONS]
-```
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--base` | ref | trunk | Base ref both sides are diffed against (`origin/HEAD`, else `main` or `master`) |
-| `--branch` | ref | HEAD | The change to compare |
-| `--path` | path | cwd | Git repository path |
-| `--limit` | int | 50 | How many branches to diff, newest committer date first |
-| `--format` | choice | table | `table` or `json` |
-
-### Examples
-
-```bash
-repowise overlap # who else is editing what you are editing
-repowise overlap --base main --limit 100 # a wider scan against an explicit base
-```
-
-When nothing overlaps, the command prints one line saying so with the scan counts.
-
----
-
-## `security`
-
-Security signal scanning. Working-tree scanning already runs during `init` /
-`update`. Use this group to walk **full git history** for leaked secrets.
-
-```bash
-repowise security scan --history [OPTIONS]
-```
-
-Without `--history`, the command prints a hint and exits (it does not re-run
-the working-tree scan).
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--history` | flag | false | Required for a real scan: walk full git history |
-| `--since` | rev | all | Lower bound (exclusive) |
-| `--to` | rev | HEAD | Upper bound (inclusive) |
-| `--path` | string | cwd | Repo path |
-| `--all-patterns` | flag | false | Also report code-smell patterns (default: secrets only) |
-| `--output` | choice | table | `table` or `json` |
-
-### Examples
-
-```bash
-repowise security scan --history
-repowise security scan --history --since v1.0.0 --output json
-```
-
----
-
-## `coverage`
-
-Ingest and inspect test-coverage reports (LCOV, Cobertura/Clover, coverage.py).
-
-```bash
-repowise coverage SUBCOMMAND [OPTIONS]
-```
-
-### Subcommands
-
-| Subcommand | Description |
-|-----------|-------------|
-| `add [PATHS...]` | Ingest reports (auto-discovers when none given); builds per-test map when contexts are present |
-| `status` | Show ingested coverage + test-to-code map counts |
-
-### Examples
-
-```bash
-repowise coverage add
-repowise coverage add coverage.lcov
-repowise coverage add .coverage
-repowise coverage status
-```
-
----
-
-## `impacted-tests`
-
-Print the tests whose coverage intersects a change's changed lines. Requires a
-per-test map from `coverage add`.
-
-```bash
-repowise impacted-tests [REVSPEC] [OPTIONS]
-```
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--path` | string | cwd | Repo path |
-| `--staged` | flag | when no revspec | Diff staged changes |
-| `--format` | choice | table | `table`, `json`, or `list` (pipeable test ids) |
-
-### Examples
-
-```bash
-repowise impacted-tests
-repowise impacted-tests main..HEAD
-repowise impacted-tests main..HEAD --format list | xargs pytest
-```
-
----
-
-## `workspace`
-
-Manage multi-repo workspaces.
-
-```bash
-repowise workspace SUBCOMMAND [OPTIONS]
-```
-
-### Subcommands
-
-| Subcommand | Description |
-|-----------|-------------|
-| `add` | Add a repo and (by default) index it |
-| `list` | Show workspace repos and status |
-| `remove` | Remove a repo from the workspace |
-| `scan` | Find new repos under the workspace root |
-| `set-default` | Change the primary repo |
-| `check` | Architecture lint (dependency rules / cycles) |
-| `metrics` | Architecture metrics |
-| `diagnostics` | Explain cross-repo contract link counts |
-
----
-
-## `distill`
-
-Run a command and print a compact, reversible rendering of its output.
-
-```bash
-repowise distill <command>...
-```
-
-### Examples
-
-```bash
-repowise distill pytest -x
-repowise distill git status
-repowise distill npm run build
-```
-
----
-
-## `decision`
-
-Manage architectural decision records (ADRs).
-
-```bash
-repowise decision SUBCOMMAND [OPTIONS]
-```
-
-### Subcommands
-
-| Subcommand | Description |
-|-----------|-------------|
-| `add` | Interactively add a new decision |
-| `list [PATH]` | List all decisions |
-| `show <ID>` | Display full decision details |
-| `confirm <ID>` | Mark a proposed decision as active |
-| `dismiss <ID>` | Delete a proposed decision |
-| `deprecate <ID>` | Mark a decision as deprecated |
-| `health [PATH]` | Show decision health metrics |
-
-### `list` options
-
-| Flag | Type | Description |
-|------|------|-------------|
-| `--status` | choice | Filter by status: `proposed`, `active`, `deprecated`, `superseded`, `all` |
-| `--source` | choice | Filter by origin: `adr`, `cli`, `comment`, `commit`, `conventions`, `git_archaeology`, `inline_marker`, `llm_inferred`, `pr`, `session`, `all` |
-| `--proposed` | flag | Show only proposed decisions |
-| `--stale-only` | flag | Show only decisions with staleness score ≥ 0.5 |
-
-### Examples
-
-```bash
-repowise decision list
-repowise decision list --status proposed
-repowise decision show d-42
-repowise decision confirm d-42
-repowise decision deprecate d-17 --superseded-by d-42
-```
-
----
-
-## `generate-claude-md`
-
-Generate or update the `.claude/CLAUDE.md` file for Claude Code context.
-
-```bash
-repowise generate-claude-md [PATH] [OPTIONS]
-```
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--output` | string | `.claude/CLAUDE.md` | Custom output path |
-| `--stdout` | flag | false | Print to stdout instead of writing a file |
-
-### Example
-
-```bash
-repowise generate-claude-md # Update .claude/CLAUDE.md in place
-repowise generate-claude-md --stdout # Preview without writing
-```
-
-See [CLAUDE.md Generator →](claude-md-generator) for how the file is structured.
-
----
-
-## `export`
-
-Export wiki pages to files, or emit a Structurizr DSL architecture model.
-
-```bash
-repowise export [PATH] [OPTIONS]
-```
-
-### Options
-
-| Flag | Type | Default | Description |
-|------|------|---------|-------------|
-| `--format` | choice | markdown | `markdown`, `html`, `json`, or `structurizr` |
-| `--output` / `-o` | string | `.repowise/export` | Output directory (for structurizr, a path ending in `.dsl` names the file) |
-| `--full` | flag | false | JSON: include tombstones plus decisions, dead code, and hotspot metadata |
-| `--standalone` | flag | false | Structurizr: emit a complete workspace with default views |
-| `--components` | flag | false | Structurizr: include the component level (one box per directory) |
-| `--force` | flag | false | Structurizr: overwrite the output file even if Repowise did not write it |
-| `--no-externals` | flag | false | Structurizr: leave third-party dependencies out of the model |
-
-### Examples
-
-```bash
-repowise export # Export all pages as markdown
-repowise export --format html -o ./site # HTML export to ./site
-repowise export --format json # Machine-readable JSON dump
-repowise export --format json --full # Archival JSON with decisions / dead code
-repowise export --format structurizr --standalone --components
-repowise export --format structurizr -o architecture.dsl
-```
-
-Also available as the Claude Code slash command `/repowise:export`.
-
----
-
-## Configuration
-
-Settings are saved to `.repowise/config.yaml` after the first `init`. You can edit this file directly or pass flags to override settings per run.
-
-```yaml
-provider: anthropic
-model: claude-sonnet-4-6
-embedder: gemini
-max_tokens: 16384
-exclude_patterns:
- - vendor/
- - "*.generated.*"
-commit_limit: 5000
-follow_renames: false
-```
-
-`max_tokens` is the persistent per-page documentation output limit used by all
-CLI and server generation paths.
-
-See [Configuration →](configuration) for the full reference.
diff --git a/website/codex.html b/website/codex.html
new file mode 100644
index 000000000..66d193813
--- /dev/null
+++ b/website/codex.html
@@ -0,0 +1,14 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>Repowise docs moved to docs.repowise.dev</title>
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<meta http-equiv="refresh" content="1; url=https://docs.repowise.dev/getting-started/plugins#codex-plugin">
+<link rel="canonical" href="https://docs.repowise.dev/getting-started/plugins#codex-plugin">
+</head>
+<body>
+<h1>Repowise docs moved to docs.repowise.dev</h1>
+<p>This page is now at <a href="https://docs.repowise.dev/getting-started/plugins#codex-plugin">https://docs.repowise.dev/getting-started/plugins#codex-plugin</a>.</p>
+</body>
+</html>
diff --git a/website/codex.md b/website/codex.md
deleted file mode 100644
index 26741ca5e..000000000
--- a/website/codex.md
+++ /dev/null
@@ -1,125 +0,0 @@
----
-layout: default
-title: Codex Integration
-nav_order: 5.5
----
-
-# Codex Integration
-{: .no_toc }
-
-Use Repowise with Codex MCP, lifecycle hooks, `AGENTS.md`, the `codex_cli` provider, and a local plugin.
-{: .fs-6 .fw-300 }
-
----
-
-## Table of contents
-{: .no_toc .text-delta }
-
-1. TOC
-{:toc}
-
----
-
-## Quick setup
-
-```bash
-npm install -g @openai/codex
-codex login
-codex login status
-
-cd /path/to/your-repo
-repowise init --codex --provider codex_cli --yes
-```
-
-`--codex` generates project-local `.codex/config.toml` and `.codex/hooks.json`. It does not write to global `~/.codex/config.toml`.
-
-## MCP
-
-Repowise writes:
-
-```toml
-[mcp_servers.repowise]
-command = "repowise"
-args = ["mcp"]
-cwd = "/path/to/your-repo"
-startup_timeout_sec = 20
-
-[features]
-hooks = true
-```
-
-`repowise mcp` can run without a path because it resolves upward to the nearest `.repowise` repository.
-
-Smoke check:
-
-```bash
-codex mcp list
-```
-
-## Hooks
-
-Codex hooks are written to `.codex/hooks.json`:
-
-| Event | Purpose |
-|-------|---------|
-| `SessionStart` | Add Repowise MCP workflow guidance and the session's standing decisions |
-| `PostToolUse` `Bash\|shell_command` | Detect git operations and stale wiki state |
-| `PostToolUse` `apply_patch\|Edit\|Write` | Remind after edits that context may need refresh |
-
-Repowise keeps Codex hooks focused on lifecycle guidance and freshness checks rather than trying to reuse Claude-specific search enrichment.
-
-## Provider
-
-`codex_cli` uses your local Codex CLI auth/subscription:
-
-```bash
-repowise init --provider codex_cli --yes
-```
-
-It runs:
-
-```bash
-codex exec --ephemeral --sandbox read-only --json --cd <repo> -
-```
-
-Repowise records token usage from Codex JSONL and treats `codex_cli/*` cost as `$0.00`. `--model` is passed to Codex only when explicitly configured.
-
-Concurrency defaults to 4 processes. The variable below overrides it in either direction -- lower it if you are hitting limits, and note that raising it past 4 is allowed but is the quickest way to hit them:
-
-```bash
-REPOWISE_CODEX_CLI_CONCURRENCY=2 repowise generate --unwritten
-```
-
-## Plugin and skills
-
-The Repowise repository includes a local Codex plugin at `plugins/codex` and a marketplace entry at `.agents/plugins/marketplace.json`.
-
-```bash
-cd /path/to/repowise
-codex plugin marketplace add .
-codex
-/plugins
-```
-
-Install Repowise from the plugin browser. The plugin bundles MCP config, lifecycle hooks, and Codex-neutral skills. It does not add Claude-style slash commands. Plugin-bundled hooks are opt-in in current Codex releases; enable `[features] plugin_hooks = true` if you want hooks loaded from an installed plugin.
-
-## AGENTS.md
-
-`repowise init --codex` generates managed `AGENTS.md` by default. `repowise update` refreshes it when `editor_files.agents_md` is enabled, or when `--agents` is passed. Use:
-
-```bash
-repowise init --no-agents
-repowise update --agents
-```
-
-User content outside the Repowise managed markers is preserved.
-
-## Official docs
-
-- [Codex hooks](https://developers.openai.com/codex/hooks)
-- [Codex MCP](https://developers.openai.com/codex/mcp)
-- [Codex non-interactive mode](https://developers.openai.com/codex/noninteractive)
-- [Codex plugins](https://developers.openai.com/codex/plugins)
-- [Build plugins](https://developers.openai.com/codex/plugins/build)
-- [Codex skills](https://developers.openai.com/codex/skills)
-- [AGENTS.md](https://developers.openai.com/codex/guides/agents-md)
diff --git a/website/concepts.html b/website/concepts.html
new file mode 100644
index 000000000..da5f7acf3
--- /dev/null
+++ b/website/concepts.html
@@ -0,0 +1,14 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>Repowise docs moved to docs.repowise.dev</title>
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<meta http-equiv="refresh" content="1; url=https://docs.repowise.dev/getting-started/how-it-works">
+<link rel="canonical" href="https://docs.repowise.dev/getting-started/how-it-works">
+</head>
+<body>
+<h1>Repowise docs moved to docs.repowise.dev</h1>
+<p>This page is now at <a href="https://docs.repowise.dev/getting-started/how-it-works">https://docs.repowise.dev/getting-started/how-it-works</a>.</p>
+</body>
+</html>
diff --git a/website/concepts.md b/website/concepts.md
deleted file mode 100644
index d82a58b35..000000000
--- a/website/concepts.md
+++ /dev/null
@@ -1,186 +0,0 @@
----
-layout: default
-title: Core Concepts
-nav_order: 3
----
-
-# Core Concepts
-{: .no_toc }
-
-The four layers that make up repowise, and why each one exists.
-{: .fs-6 .fw-300 }
-
----
-
-## Table of contents
-{: .no_toc .text-delta }
-
-1. TOC
-{:toc}
-
----
-
-## Overview
-
-Every time you run `repowise init`, it runs through four layers in sequence. Each layer builds on the previous one. Understanding what each layer captures helps you interpret what you're getting — and what to do when something looks wrong.
-
-```
-Source code
- │
- ▼
-┌─────────────┐
-│ Ingestion │ Parse, extract, build graph
-└──────┬──────┘
- │
- ▼
-┌─────────────┐
-│ Analysis │ Git signals, dead code, decisions
-└──────┬──────┘
- │
- ▼
-┌─────────────┐
-│ Generation │ LLM-written wiki pages
-└──────┬──────┘
- │
- ▼
-┌─────────────┐
-│ Persistence │ SQLite, vector index, REST, MCP
-└─────────────┘
-```
-
----
-
-## Layer 1: Ingestion
-
-**What it captures:** The static structure of your code.
-
-Ingestion parses every source file using [tree-sitter](https://tree-sitter.github.io/), a fast incremental parser that understands the syntax of each language. For each file, it extracts:
-
-- **Symbols** — functions, classes, methods, interfaces, types
-- **Imports and exports** — what each file depends on and exposes
-- **Call sites** — which functions call which
-- **File metadata** — size, language, path
-
-From this, repowise builds a **dependency graph** using NetworkX. Nodes are files and modules. Edges are imports and call relationships. This graph is used by every subsequent layer.
-
-**Why it matters for you:** The dependency graph powers risk analysis, cascade detection, and architecture diagrams. When you ask "what does this module affect?", the answer comes from this layer.
-
-**Supported languages:** Python, TypeScript, JavaScript, Go, Rust, Java, C, C++, Kotlin, Ruby, C#, Swift, Scala, PHP, Dart, Shell. **16 languages** parsed to a full AST (11 at the Full tier with code-health markers). See [Language Support](https://github.com/repowise-dev/repowise/blob/main/docs/layers/LANGUAGE_SUPPORT.md).
-
----
-
-## Layer 2: Analysis
-
-**What it captures:** Everything your code history knows that the source doesn't.
-
-Analysis runs after ingestion and enriches each file with three types of signals:
-
-### Git intelligence
-
-For each file, repowise runs `git log` to extract:
-
-- **Churn score** — how often this file changes relative to others (percentile rank)
-- **Ownership** — which contributors have touched this file and by how much
-- **Bus factor** — whether a file depends on knowledge held by too few people
-- **Recency** — how recently it was last changed
-- **Co-change partners** — which other files tend to change at the same time
-
-High-churn files appear in the hotspots view and receive a warning in the MCP `get_risk` tool. Files with bus factor 1 are flagged as single points of failure.
-
-### Dead code detection
-
-repowise compares what your dependency graph says is reachable against what is exported or imported. Files and symbols with no inbound edges from reachable code are flagged as potentially dead.
-
-Dead code findings are tiered by confidence:
-
-| Tier | Meaning |
-|------|---------|
-| **High** | Confirmed unreachable — no imports from anywhere |
-| **Medium** | No external imports, but exported (may be a public API) |
-| **Low** | Referenced only in tests or dead code itself |
-
-### Decision mining
-
-repowise scans your git history, README files, and inline comments for patterns that indicate architectural decisions: `"we chose X because"`, `"ADR:"`, `"decision:"`, and similar markers. These are surfaced in the decision tracker and made queryable via `get_why`.
-
-**Why it matters for you:** When an AI assistant edits a hotspot file without knowing it's high-churn, the change is risky. When it deletes an unused export without knowing it's a public API, that's a bug. The analysis layer gives AI tools the context to avoid these mistakes.
-
----
-
-## Layer 3: Generation
-
-**What it captures:** Human-readable documentation at every level of the hierarchy.
-
-Generation is the only layer that requires an LLM provider. repowise sends structured prompts to your chosen provider (Anthropic, OpenAI, Gemini, Ollama, LiteLLM, or the local Codex CLI provider) and generates wiki pages at three levels:
-
-| Level | What it contains |
-|-------|-----------------|
-| **Repository** | High-level architecture overview, module map, tech stack |
-| **Module** | Purpose, responsibilities, key dependencies, design patterns |
-| **File** | What this file does, how it fits in the module, key symbols |
-
-Each page is stored in the database and linked to the file it describes. Pages have a freshness score — if the underlying file changes, the page is marked stale and queued for regeneration.
-
-**Skipping the prose:** Run `repowise init --no-prose` and every page is still rendered from structure, with no key and no spend. You get the full dependency graph, git intelligence, dead code, and decision data, and a complete wiki whose subsystem (concept) pages are structural stubs rather than model prose. Fill that prose in later with `repowise generate` (or `repowise init --prose`) on the existing index.
-
-**Cost:** For a 200-file codebase, generation typically uses 150,000–300,000 tokens. The `--dry-run` flag shows you the estimated cost before committing.
-
----
-
-## Layer 4: Persistence
-
-**What it captures:** Everything, queryable in three complementary ways.
-
-All data from the previous three layers is stored across three stores:
-
-### SQL (SQLite or PostgreSQL)
-
-The primary store. Contains:
-- All wiki pages with full text and metadata
-- Symbol index (every function, class, method)
-- Dependency graph (nodes and edges)
-- Git metadata (churn, ownership, recency per file)
-- Architectural decisions
-- Dead code findings
-
-Default: SQLite at `.repowise/wiki.db`. Switch to PostgreSQL by setting `REPOWISE_DB_URL`.
-
-### Vector store (LanceDB)
-
-An embedding index on top of the wiki pages. Powers semantic search — when you run `repowise search "authentication flow"` or ask Claude `search_codebase("how is auth handled")`, this is what responds.
-
-Stored at `.repowise/lancedb/`. You can rebuild it at any time with `repowise reindex`.
-
-### In-memory graph (NetworkX)
-
-The dependency graph is loaded into memory at server startup for fast traversal. Used by `get_dependency_path`, `get_context` graph enrichment, and cascade analysis during `update`.
-
-**Why it matters for you:** Three stores means three access patterns. Simple lookups hit SQL. Natural language queries hit the vector store. Graph traversal hits NetworkX. The MCP server abstracts all of this — you ask one question, it queries the right store.
-
----
-
-## The MCP server
-
-The MCP server sits on top of the persistence layer and exposes everything to AI coding assistants through 18 registered tools: 11 by default in a single repository, 13 by default in workspace mode, and five opt-in tools. It's the primary interface between repowise and Claude Code, Codex, Cursor, Cline, or any other MCP-compatible editor.
-
-When you run `repowise mcp`, the server starts in stdio mode and your editor can begin calling tools. The tools are designed to answer the questions an AI needs to make good decisions about your code — not just "what is this file" but "should I edit it", "why is it structured this way", and "what will break if I change it".
-
-See [MCP Server →](mcp-server) for the full tool reference.
-
----
-
-## The `.repowise/` directory
-
-Everything repowise knows about your repo lives in `.repowise/`:
-
-```
-.repowise/
-├── wiki.db # SQLite database
-├── lancedb/ # Vector search index
-├── config.yaml # Provider, model, embedder settings
-├── state.json # Last sync commit, page counts
-├── mcp.json # MCP server config
-└── .env # API keys (gitignored)
-```
-
-This directory is created on first `init`. It should be added to `.gitignore` — repowise does this automatically.
diff --git a/website/configuration.html b/website/configuration.html
new file mode 100644
index 000000000..9d2ca6048
--- /dev/null
+++ b/website/configuration.html
@@ -0,0 +1,14 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>Repowise docs moved to docs.repowise.dev</title>
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<meta http-equiv="refresh" content="1; url=https://docs.repowise.dev/installation/configuration">
+<link rel="canonical" href="https://docs.repowise.dev/installation/configuration">
+</head>
+<body>
+<h1>Repowise docs moved to docs.repowise.dev</h1>
+<p>This page is now at <a href="https://docs.repowise.dev/installation/configuration">https://docs.repowise.dev/installation/configuration</a>.</p>
+</body>
+</html>
diff --git a/website/configuration.md b/website/configuration.md
deleted file mode 100644
index 8e5e601f1..000000000
--- a/website/configuration.md
+++ /dev/null
@@ -1,402 +0,0 @@
----
-layout: default
-title: Configuration
-nav_order: 9
----
-
-# Configuration
-{: .no_toc }
-
-The `.repowise/` directory, provider setup, API keys, and what's customizable.
-{: .fs-6 .fw-300 }
-
----
-
-## Table of contents
-{: .no_toc .text-delta }
-
-1. TOC
-{:toc}
-
----
-
-## The `.repowise/` directory
-
-Everything repowise knows about your repository lives here. It's created at the repo root on first `init`.
-
-```
-.repowise/
-├── wiki.db # SQLite database — all pages, symbols, graph, git metadata, decisions
-├── lancedb/ # Vector search index (LanceDB)
-├── config.yaml # Provider, model, embedder, exclude patterns
-├── state.json # Last sync commit, page counts, token usage
-├── mcp.json # MCP server configuration
-└── .env # API keys (gitignored automatically)
-```
-
-repowise adds `.repowise/` to your `.gitignore` automatically. The directory should not be committed — it's a local cache, not source of truth.
-
----
-
-## `config.yaml`
-
-The main configuration file. Created after first `init`, updated when you pass `--commit-limit` or `--follow-renames` flags.
-
-```yaml
-provider: anthropic # LLM provider
-model: claude-sonnet-4-6 # Model identifier
-embedder: gemini # Embedding provider
-reasoning: auto # auto | off/none | minimal | low | medium | high | xhigh | max
-max_tokens: 16384 # Max output tokens per generated documentation page
-exclude_patterns: # Gitignore-style patterns
- - vendor/
- - "*.generated.*"
- - proto/
-commit_limit: 5000 # Max commits per file for git analysis
-follow_renames: false # Track file renames in git history
-editor_files:
- claude_md: true
- agents_md: true
-```
-
-You can edit this file directly. Changes take effect on the next `init`, `update`, or `serve` run.
-
-`reasoning` controls documentation-generation calls for reasoning-capable chat
-models. `auto` preserves provider defaults. `off`/`none` disables Qwen3-style thinking
-for OpenAI-compatible vLLM/SGLang endpoints by sending
-`extra_body.chat_template_kwargs.enable_thinking=false`, and maps to
-OpenRouter's `reasoning.effort=none` for effort-capable OpenRouter model
-families. `minimal` requests OpenAI's lowest supported reasoning effort for
-supported OpenAI reasoning models and maps to OpenRouter's
-`reasoning.effort=minimal` for effort-capable OpenRouter model families.
-`low`, `medium`, `high`, `xhigh`, and `max` request native effort levels for
-providers and model families that expose them. Providers or models that cannot
-translate an explicit mode fail before making an API call. The interactive
-`serve` chat streaming path is separate and does not currently consume this
-setting.
-
-`max_tokens` bounds each model-written documentation response. It is a
-persistent repository setting used by `init`, `update`, `generate`, `restyle`,
-workspace generation, and server-triggered generation. If generation reaches a
-token limit before the page is complete, repowise rejects the partial page
-instead of saving it.
-
----
-
-## LLM providers
-
-### Anthropic (Claude)
-
-```bash
-export ANTHROPIC_API_KEY="sk-ant-..."
-```
-
-| Model | Notes |
-|-------|-------|
-| `claude-sonnet-4-6` | Best balance of quality and cost |
-| `claude-opus-4-6` | Highest quality, higher cost |
-| `claude-haiku-5-5` | Default, fastest, lowest cost |
-
-```bash
-repowise init --provider anthropic --model claude-haiku-5-5
-```
-
----
-
-### OpenAI (GPT)
-
-```bash
-export OPENAI_API_KEY="sk-..."
-```
-
-| Model | Notes |
-|-------|-------|
-| `gpt-4.1` | Default |
-| `gpt-4o` | Alternative |
-
-```bash
-repowise init --provider openai --model gpt-4.1
-```
-
-For an OpenAI-compatible Qwen3 endpoint served by vLLM or SGLang:
-
-```bash
-export OPENAI_BASE_URL="http://localhost:8000/v1"
-repowise init --provider openai --model qwen3 --reasoning off
-```
-
-For OpenRouter:
-
-```bash
-repowise init --provider openrouter --model openai/gpt-5 --reasoning minimal
-repowise init --provider openrouter --model x-ai/grok-4 --reasoning off
-```
-
----
-
-### Gemini (Google)
-
-```bash
-export GEMINI_API_KEY="AI..."
-# or:
-export GOOGLE_API_KEY="AI..."
-```
-
-| Model | Notes |
-|-------|-------|
-| `gemini-3.1-flash-lite-preview` | Default — very fast and cheap |
-| `gemini-2.5-pro` | Higher quality |
-
-```bash
-repowise init --provider gemini
-```
-
-Gemini is also the default embedding provider when `GEMINI_API_KEY` is set.
-
----
-
-### Kimi
-
-```bash
-export KIMI_API_KEY="..."
-repowise init --provider kimi --model kimi-for-coding
-```
-
-The default Kimi Code endpoint supports `kimi-for-coding` and
-`kimi-for-coding-highspeed`. Repowise automatically uses their required
-sampling parameters.
-
-K2.x models use the separate Kimi Open Platform. Supply a key from that
-platform together with its OpenAI-compatible endpoint:
-
-```bash
-export KIMI_API_KEY="..."
-export KIMI_BASE_URL="https://api.moonshot.ai/v1"
-repowise init --provider kimi --model kimi-k2.6
-```
-
-For K2.x models, Repowise selects the required sampling parameters for
-thinking or instant mode.
-
----
-
-### Ollama (local)
-
-Run models locally without any API key.
-
-```bash
-export OLLAMA_BASE_URL="http://localhost:11434" # default if Ollama is running locally
-```
-
-```bash
-repowise init --provider ollama --model llama3.2
-```
-
-Any model available in your local Ollama installation can be used.
-
----
-
-### LiteLLM (100+ providers)
-
-LiteLLM acts as a proxy supporting OpenAI, Azure, Cohere, Mistral, and dozens more.
-
-```bash
-export LITELLM_API_KEY="..."
-repowise init --provider litellm --model azure/gpt-4
-```
-
----
-
-### Codex CLI
-
-Use your authenticated local Codex CLI subscription instead of an API key:
-
-```bash
-npm install -g @openai/codex
-codex login
-codex login status
-repowise init --provider codex_cli --codex --yes
-```
-
-`codex_cli/default` uses the Codex CLI's configured model. `codex_cli/gpt-5.5` passes `--model gpt-5.5` to `codex exec`. Repowise records token usage from Codex JSONL output and treats `codex_cli/*` cost as `$0.00` because billing is handled by Codex CLI auth/subscription.
-
-Project-local Codex setup is controlled by:
-
-```yaml
-editor_files:
- agents_md: true
-```
-
-Use `repowise init --codex` to write `.codex/config.toml` and `.codex/hooks.json`.
-
----
-
-### OpenCode CLI
-
-Use your local OpenCode CLI instead of an API key:
-
-```bash
-curl -fsSL https://opencode.ai/install | bash
-opencode # first-run setup
-repowise init --provider opencode --yes
-```
-
-`opencode/default` uses the OpenCode CLI's configured default model. `opencode/deepseek-v4-pro` passes `--model deepseek-v4-pro` to `opencode run`. Repowise records token usage from OpenCode JSONL output and treats `opencode/*` cost as `$0.00` because billing is handled by OpenCode's own auth/subscription.
-
-OpenCode is detected automatically when installed — no auth setup needed from repowise. Use `opencode providers` to manage authentication and `opencode models` to list available models.
-
----
-
-### Provider auto-detection
-
-If you don't pass `--provider`, repowise detects your provider by checking:
-
-1. `REPOWISE_PROVIDER` environment variable
-2. `provider` in `.repowise/config.yaml`
-3. API key environment variables, in order: `ANTHROPIC_API_KEY` → `OPENAI_API_KEY` → `OPENROUTER_API_KEY` → `OLLAMA_BASE_URL` → `GEMINI_API_KEY` → `DEEPSEEK_API_KEY` → `KIMI_API_KEY` → `EDENAI_API_KEY`
-
-Codex CLI is intentionally explicit: pass `--provider codex_cli` or set `REPOWISE_PROVIDER=codex_cli`. Similarly, OpenCode is detected automatically when on `PATH` but can be explicitly selected with `--provider opencode` or `REPOWISE_PROVIDER=opencode`.
-
----
-
-## Embeddings (for semantic search)
-
-Embeddings power semantic search via the vector index. The embedder is separate from the LLM provider.
-
-| Embedder | Env var | Notes |
-|----------|---------|-------|
-| `gemini` | `GEMINI_API_KEY` | Default when key is present |
-| `openai` | `OPENAI_API_KEY` | OpenAI text-embedding-3-small |
-| `mock` | — | Dummy embeddings, no semantic search |
-
-```bash
-repowise init --embedder openai
-repowise reindex --embedder gemini # Switch embedder and rebuild index
-```
-
----
-
-## BYOK (Bring Your Own Key)
-
-API keys can be provided in three ways, checked in this order:
-
-1. **Environment variable** — set before running repowise
-2. **`.repowise/.env`** — persisted from interactive setup, loaded automatically
-3. **Interactive prompt** — repowise asks during `init` if no key is found, then saves to `.repowise/.env`
-
-The `.repowise/.env` file is gitignored automatically. Example:
-
-```env
-ANTHROPIC_API_KEY=sk-ant-...
-GEMINI_API_KEY=AI...
-```
-
----
-
-## `state.json`
-
-Tracks the current indexing state. Do not edit manually.
-
-```json
-{
- "last_sync_commit": "59ca5c8a1b2c3d4e5f6a7b8c",
- "total_pages": 247,
- "provider": "anthropic",
- "model": "claude-sonnet-4-6",
- "total_tokens_used": 180432
-}
-```
-
-`last_sync_commit` is used by `repowise update` to determine which files have changed since the last run.
-
----
-
-## `mcp.json`
-
-MCP server configuration for this repository.
-
-```json
-{
- "mcpServers": {
- "repowise": {
- "command": "repowise",
- "args": ["mcp", "/path/to/repo", "--transport", "stdio"],
- "description": "repowise: codebase intelligence for my-repo"
- }
- },
- "settings": {
- "port": 7338
- }
-}
-```
-
-repowise also writes a `.mcp.json` at the repository root for Claude Code auto-discovery. This file can be committed.
-
----
-
-## Environment variables
-
-| Variable | Description |
-|----------|-------------|
-| `ANTHROPIC_API_KEY` | Anthropic API key |
-| `OPENAI_API_KEY` | OpenAI API key |
-| `GEMINI_API_KEY` / `GOOGLE_API_KEY` | Google Gemini API key |
-| `KIMI_API_KEY` | Kimi API key |
-| `KIMI_BASE_URL` | Override the Kimi API base URL |
-| `OLLAMA_BASE_URL` | Ollama server URL (default: `http://localhost:11434`) |
-| `LITELLM_API_KEY` | LiteLLM proxy key |
-| `REPOWISE_PROVIDER` | Override provider (skips auto-detection) |
-| `REPOWISE_DB_URL` | Use PostgreSQL instead of SQLite (e.g., `postgresql+asyncpg://...`) |
-| `REPOWISE_HOST` | API server host (default: `127.0.0.1`) |
-| `REPOWISE_PORT` | API server port (default: `7337`) |
-| `REPOWISE_MCP_PORT` | MCP SSE server port (default: `7338`) |
-
----
-
-## Exclude patterns
-
-repowise respects your `.gitignore` automatically. All patterns in your root `.gitignore` are honored during file traversal using the same `gitwildmatch` format that git uses.
-
-On top of `.gitignore`, you can add extra patterns via `--exclude` / `-x`:
-
-```bash
-repowise init -x vendor/ -x "*.generated.ts" -x proto/ -x "**/*.pb.go"
-```
-
-Patterns are saved to `config.yaml` and applied on subsequent `update` runs. In interactive advanced mode, you can enter exclude patterns one per line instead of comma-separated.
-
-You can also create a `.repowiseIgnore` file (same gitignore syntax) at the repo root or in any subdirectory for more granular control.
-
-Built-in exclusions (always applied):
-- `.git/`, `.repowise/`, `node_modules/`
-- `__pycache__/`, `*.pyc`, `.venv/`
-- Binary files, lockfiles, and minified assets
-
-Use `--skip-tests` to exclude test files and `--skip-infra` to exclude Dockerfiles, Makefiles, and shell scripts.
-
-After traversal, repowise prints a filtering summary showing how many files were included and excluded by each rule (`.gitignore`, extensions, binary, oversized, etc.), along with a language breakdown.
-
----
-
-## Submodules
-
-Git submodule directories are excluded by default. If your repo uses submodules and you want to include them in the index, pass `--include-submodules`:
-
-```bash
-repowise init --include-submodules
-```
-
-repowise reads `.gitmodules` to detect submodule paths. When excluded, submodule directories are skipped entirely during traversal.
-
----
-
-## PostgreSQL
-
-For team deployments or larger repos, use PostgreSQL instead of SQLite:
-
-```bash
-export REPOWISE_DB_URL="postgresql+asyncpg://user:pass@localhost:5432/repowise"
-repowise init
-```
-
-The schema is managed with Alembic migrations. See [Self-hosting →](self-hosting) for Docker setup with PostgreSQL.
diff --git a/website/contributing.html b/website/contributing.html
new file mode 100644
index 000000000..a8440b4ae
--- /dev/null
+++ b/website/contributing.html
@@ -0,0 +1,14 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>Repowise docs moved to docs.repowise.dev</title>
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<meta http-equiv="refresh" content="1; url=https://docs.repowise.dev/contributing">
+<link rel="canonical" href="https://docs.repowise.dev/contributing">
+</head>
+<body>
+<h1>Repowise docs moved to docs.repowise.dev</h1>
+<p>This page is now at <a href="https://docs.repowise.dev/contributing">https://docs.repowise.dev/contributing</a>.</p>
+</body>
+</html>
diff --git a/website/contributing.md b/website/contributing.md
deleted file mode 100644
index 4142ddcf5..000000000
--- a/website/contributing.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-layout: default
-title: Contributing
-nav_order: 11
----
-
-# Contributing
-
-Contributions are welcome. The full guide is maintained in the repository and is the
-single source of truth for setup, the development workflow and how to claim an issue.
-
-**[Read CONTRIBUTING.md on GitHub →](https://github.com/repowise-dev/repowise/blob/main/.github/CONTRIBUTING.md)**
-
-Setup commands are deliberately not repeated on this page. They changed often enough
-that the copy here drifted from the real ones, and a wrong command costs more than a
-second click.
-
-## Quick links
-
-- [Open an issue](https://github.com/repowise-dev/repowise/issues) — bugs, feature requests, questions
-- [Open a pull request](https://github.com/repowise-dev/repowise/pulls)
-- [Good first issues](https://github.com/repowise-dev/repowise/labels/good%20first%20issue) — reserved for first-time contributors
-- [Help wanted](https://github.com/repowise-dev/repowise/labels/help%20wanted) — scoped work for people who know the codebase
-- [Architecture guide](https://github.com/repowise-dev/repowise/blob/main/docs/architecture/README.md)
-
-## Security issues
-
-For security vulnerabilities, see
-[SECURITY.md](https://github.com/repowise-dev/repowise/blob/main/.github/SECURITY.md).
-Please do not open a public issue.
diff --git a/website/getting-started.html b/website/getting-started.html
new file mode 100644
index 000000000..7cca9226c
--- /dev/null
+++ b/website/getting-started.html
@@ -0,0 +1,14 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>Repowise docs moved to docs.repowise.dev</title>
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<meta http-equiv="refresh" content="1; url=https://docs.repowise.dev/getting-started/quickstart">
+<link rel="canonical" href="https://docs.repowise.dev/getting-started/quickstart">
+</head>
+<body>
+<h1>Repowise docs moved to docs.repowise.dev</h1>
+<p>This page is now at <a href="https://docs.repowise.dev/getting-started/quickstart">https://docs.repowise.dev/getting-started/quickstart</a>.</p>
+</body>
+</html>
diff --git a/website/getting-started.md b/website/getting-started.md
deleted file mode 100644
index 9d1b1cde5..000000000
--- a/website/getting-started.md
+++ /dev/null
@@ -1,314 +0,0 @@
----
-layout: default
-title: Getting Started
-nav_order: 2
----
-
-# Getting Started
-{: .no_toc }
-
-The 60-second path to codebase intelligence.
-{: .fs-6 .fw-300 }
-
----
-
-## Table of contents
-{: .no_toc .text-delta }
-
-1. TOC
-{:toc}
-
----
-
-## Quick start (under 5 minutes, no API key)
-
-*Index once, and give your agent the dependency graph + git history + code-health — not 40 greps.*
-
-**1. Install**
-
-```bash
-pip install repowise # Windows: python -m pip install repowise
-repowise --version # -> repowise, version 0.27.x
-```
-
-**2. Index your repo**
-
-```bash
-cd /path/to/your/repo
-repowise init
-```
-
-Bare `init` scans the repo and asks how to index it: everything (the wiki written by a model), no prose (the same wiki rendered from your code's structure, no key and no spend), or advanced for every knob. Nothing is spent before you see an estimate and confirm it.
-
-Scripting it instead? Name the mode and skip the questions: `repowise init --no-prose -y` for the free path, `repowise init --prose -y` for model-written subsystem pages. Either way you get the dependency graph, git history, code-health score and dead-code findings in seconds, plus every wiki page.
-
-**3. Connect your agent** — the MCP server is `repowise mcp`, served from the repo dir.
-
-<details markdown="block"><summary><b>Claude Code</b></summary>
-
-```bash
-# Plugin (MCP tools + slash commands + skills):
-/plugin marketplace add repowise-dev/repowise
-/plugin install repowise@repowise
-
-# …or wire the MCP server directly:
-claude mcp add repowise -- repowise mcp
-```
-Or commit a project `.mcp.json`:
-```json
-{ "mcpServers": { "repowise": { "command": "repowise", "args": ["mcp"] } } }
-```
-</details>
-
-<details markdown="block"><summary><b>Codex CLI</b></summary>
-
-Add to `~/.codex/config.toml`:
-```toml
-[mcp_servers.repowise]
-command = "repowise"
-args = ["mcp"]
-```
-Or: `codex mcp add repowise -- repowise mcp`
-</details>
-
-**4. First real call.** Ask your agent: *"Use repowise `get_overview` to summarize this repo,"* or *"`get_context` for `src/auth.py`."* You get graph-grounded architecture and per-file triage instead of a flurry of greps. ✅
-
-> `get_overview` and `get_context` work in index-only mode with no key, synthesized from the graph, git and health layers. `search_codebase` and `get_answer` read the wiki, which index-only mode does build, but they answer from pages rendered from structure rather than model-written prose, and `search_codebase` is full-text only until you configure an embedder.
-
-Ready for the full picture? Run `repowise init --provider …` for the generated wiki + semantic search, or skip key management entirely with the [hosted tier](https://www.repowise.dev). The detailed setup paths below walk through each editor and mode.
-
----
-
-## Choose your path
-
-There are three ways to set up repowise. Pick the one that fits how you work.
-
-| Path | Best for | Time |
-|------|----------|------|
-| [Claude Code Plugin](#path-1-claude-code-plugin) | Claude Code users | ~30 seconds |
-| [pip + Claude Code](#path-2-pip--claude-code) | Manual control + Claude Code | ~2 minutes |
-| [pip + Codex](#path-3-pip--codex) | Codex CLI users | ~2 minutes |
-| [Standalone CLI](#path-4-standalone-cli) | No AI editor, or CI use | ~2 minutes |
-
----
-
-## Path 1: Claude Code Plugin
-
-**The recommended path.** Claude handles everything — installation, API key setup, indexing, and MCP registration.
-
-### Step 1: Install the plugin
-
-Open Claude Code and run:
-
-```
-/plugin marketplace add repowise-dev/repowise-plugin
-/plugin install repowise@repowise
-```
-
-### Step 2: Index your repo
-
-Navigate to your project directory and run:
-
-```
-/repowise:init
-```
-
-Or just ask Claude naturally:
-
-```
-set up repowise for this repo
-```
-
-### What happens
-
-Claude walks you through:
-
-1. **Mode selection** — full documentation, index-only (free, no LLM), or advanced
-2. **Provider setup** — choose Anthropic, OpenAI, Gemini, or local Ollama
-3. **API key** — entered once, saved to `.repowise/.env` (gitignored automatically)
-4. **Indexing** — parses your code, runs git analysis, generates docs
-
-When it finishes, the MCP server is registered and Claude can query your codebase directly. You'll see a progress bar as each phase completes.
-
-### What you see
-
-```
- repowise
-─────────────────────────────────────────────
- Indexing your codebase...
-
- Phase 1 of 4 — Ingestion
- Scanning & filtering files... [████████████████████]
- Scanned 1,247 files, 247 included
- Excluded: 820 by .gitignore, 45 by extension, 12 binary, 123 unknown type
- Languages: python 892, typescript 245, go 80, yaml 18, json 12
- Parsing files... [████████████████████] 247/247
- Building dependency graph... done
-
- Phase 2 of 4 — Analysis
- Indexing file history... done
- Detecting dead code... done
- Extracting decisions... done
-
- Phase 3 of 4 — Generation
- Languages: python 58%, typescript 28%, go 10%, yaml 2%, json 1%
- Generating wiki pages... [████████████████░░░░] 82%
- Estimated tokens: ~180k
-
- Phase 4 of 4 — Persistence
- Writing to database... done
- Building vector index... done
- Generating CLAUDE.md... done
-
- Done. 247 pages generated.
-─────────────────────────────────────────────
-```
-
----
-
-## Path 2: pip + Claude Code
-
-Install manually, then connect Claude Code to the MCP server.
-
-### Step 1: Install repowise
-
-```bash
-pip install repowise
-```
-
-### Step 2: Set your API key
-
-```bash
-export ANTHROPIC_API_KEY="sk-ant-..."
-# or: export OPENAI_API_KEY="sk-..."
-# or: export GEMINI_API_KEY="AI..."
-```
-
-### Step 3: Index your repo
-
-```bash
-cd /path/to/your-repo
-repowise init
-```
-
-repowise detects your API key automatically and starts the interactive setup. Follow the prompts — it takes about 2 minutes for a medium-sized codebase.
-
-### Step 4: Connect Claude Code
-
-After `init` completes, repowise writes a `.mcp.json` file at your repo root. Claude Code picks this up automatically next time you open the project.
-
-To verify the MCP server is connected:
-
-```
-/repowise:status
-```
-
----
-
-## Path 3: pip + Codex
-
-Use the local Codex CLI auth/subscription flow and project-local MCP/hooks config.
-
-### Step 1: Install repowise and Codex
-
-```bash
-pip install repowise
-npm install -g @openai/codex
-codex login
-codex login status
-```
-
-### Step 2: Index your repo
-
-```bash
-cd /path/to/your-repo
-repowise init --codex --provider codex_cli --yes
-```
-
-This writes `.codex/config.toml`, `.codex/hooks.json`, and managed `AGENTS.md` in the repository. It does not edit global `~/.codex/config.toml`.
-
-### Step 3: Start Codex
-
-```bash
-codex
-```
-
-Codex reads `AGENTS.md`, starts the Repowise MCP server from project config, and receives lightweight lifecycle/freshness hooks. See [Codex Integration](codex).
-
----
-
-## Path 4: Standalone CLI
-
-Use repowise without Claude Code — with the web dashboard, REST API, or any MCP-compatible editor.
-
-### Step 1: Install and set up
-
-```bash
-pip install repowise
-export ANTHROPIC_API_KEY="sk-ant-..."
-```
-
-### Step 2: Index your repo
-
-```bash
-cd /path/to/your-repo
-repowise init
-```
-
-### Step 3: Start the web dashboard
-
-```bash
-repowise serve
-```
-
-Open [http://localhost:3000](http://localhost:3000) in your browser. You'll see the full wiki, dependency graph, search, and more.
-
-### Step 4: Start the MCP server (optional)
-
-To connect any MCP-compatible editor (Codex, Cursor, Cline, Windsurf):
-
-```bash
-repowise mcp
-```
-
-Then add the MCP server to your editor's configuration. See [MCP Server →](mcp-server) for editor-specific setup.
-
----
-
-## The keyless path (the default)
-
-You don't need an LLM API key at all. A bare `repowise init` with no key configured succeeds and produces a wiki, rendered from the parsed structure of your code:
-
-```bash
-repowise init
-```
-
-`repowise init --no-prose` is the explicit spelling of the same thing, and guarantees no spend. Either way you get the full ingestion and analysis pipeline (parsing, graph, git, dead code) plus a complete wiki. It's free, takes under a minute for most repos, and still gives you:
-
-- Dependency graph
-- Hotspot detection
-- Dead code findings
-- Ownership data
-
-You can always run `repowise init --prose` (or `repowise generate`) later to write the subsystem pages as model prose on top of an existing index.
-
----
-
-## Keeping docs in sync
-
-After the initial index, keep your wiki current with:
-
-```bash
-repowise update # Sync changed files since last commit
-repowise watch # Auto-update on file saves
-```
-
-Or in Claude Code, run `/repowise:update` — Claude detects changed files and regenerates only the affected pages.
-
----
-
-## Next steps
-
-- [Core concepts →](concepts) — understand the four layers
-- [CLI reference →](cli-reference) — all commands and flags
-- [MCP server →](mcp-server) — connecting to Claude Code, Cursor, Cline
diff --git a/website/index.html b/website/index.html
new file mode 100644
index 000000000..68c4540ca
--- /dev/null
+++ b/website/index.html
@@ -0,0 +1,14 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>Repowise docs moved to docs.repowise.dev</title>
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<meta http-equiv="refresh" content="1; url=https://docs.repowise.dev/">
+<link rel="canonical" href="https://docs.repowise.dev/">
+</head>
+<body>
+<h1>Repowise docs moved to docs.repowise.dev</h1>
+<p>This page is now at <a href="https://docs.repowise.dev/">https://docs.repowise.dev/</a>.</p>
+</body>
+</html>
diff --git a/website/index.md b/website/index.md
deleted file mode 100644
index 91c1e65d2..000000000
--- a/website/index.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-layout: home
-title: Home
-nav_order: 1
----
-
-# repowise
-
-**Codebase intelligence for developers and AI.**
-
-repowise generates and maintains a structured wiki for any codebase. It tracks changes, exposes everything through an MCP server, and keeps your AI coding assistant deeply informed about your code — automatically.
-
-[![PyPI version](https://img.shields.io/pypi/v/repowise.svg)](https://pypi.org/project/repowise/)
-[![Python 3.11+](https://img.shields.io/badge/python-3.11%2B-blue.svg)](https://pypi.org/project/repowise/)
-[![License: AGPL-3.0](https://img.shields.io/badge/license-AGPL--3.0-purple.svg)](https://github.com/repowise-dev/repowise/blob/main/LICENSE)
-
----
-
-## What repowise does
-
-| Capability | Description |
-|-----------|-------------|
-| **Auto-documentation** | Module, file, and symbol-level docs generated from source code |
-| **Git intelligence** | Churn hotspots, ownership, bus factor, change patterns |
-| **Dead code detection** | Finds confirmed unused exports, functions, and types |
-| **Decision intelligence** | Captures *why* code is structured the way it is |
-| **MCP server** | 11 default tools (10 flagship + `list_repos`) for AI assistants; 18 registered |
-| **Web dashboard** | Browse wiki, search, and explore architecture diagrams |
-| **Multi-language** | 16 AST languages (11 Full tier): Python, TypeScript, JavaScript, Go, Rust, Java, C/C++, Kotlin, Ruby, C#, Swift, Scala, PHP, Dart, Shell |
-
----
-
-## Install in one line
-
-```bash
-pip install repowise
-```
-
----
-
-## Get started
-
-| | |
-|---|---|
-| [**60-second quickstart →**](getting-started) | The fastest path to a working setup. |
-| [**Core concepts →**](concepts) | Understand the four layers before diving in. |
-| [**CLI reference →**](cli-reference) | Every command, flag, and option. |
-| [**Codex integration →**](codex) | Codex MCP, hooks, AGENTS.md, and local CLI provider setup. |
diff --git a/website/mcp-server.html b/website/mcp-server.html
new file mode 100644
index 000000000..aa4d9a07e
--- /dev/null
+++ b/website/mcp-server.html
@@ -0,0 +1,14 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>Repowise docs moved to docs.repowise.dev</title>
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<meta http-equiv="refresh" content="1; url=https://docs.repowise.dev/mcp/overview">
+<link rel="canonical" href="https://docs.repowise.dev/mcp/overview">
+</head>
+<body>
+<h1>Repowise docs moved to docs.repowise.dev</h1>
+<p>This page is now at <a href="https://docs.repowise.dev/mcp/overview">https://docs.repowise.dev/mcp/overview</a>.</p>
+</body>
+</html>
diff --git a/website/mcp-server.md b/website/mcp-server.md
deleted file mode 100644
index fde7055bc..000000000
--- a/website/mcp-server.md
+++ /dev/null
@@ -1,486 +0,0 @@
----
-layout: default
-title: MCP Server
-nav_order: 5
----
-
-# MCP Server
-{: .no_toc }
-
-Connect repowise to Claude Code, Codex, Cursor, Cline, or any MCP-compatible editor.
-{: .fs-6 .fw-300 }
-
----
-
-## Table of contents
-{: .no_toc .text-delta }
-
-1. TOC
-{:toc}
-
----
-
-## Overview
-
-The MCP (Model Context Protocol) server is how repowise talks to AI coding assistants. It registers 18 tools: a curated 10-tool default surface in a single repository, `list_repos` added by default in workspace mode, and seven opt-in specialists subject to mode eligibility. Once connected, your editor's AI can query your codebase wiki for synthesized answers, symbols, docs, ownership, file and change-risk signals, code health, and architectural decisions.
-
-Start the server with:
-
-```bash
-repowise mcp [PATH]
-```
-
----
-
-## Connecting to editors
-
-### Claude Code
-
-**Via plugin (recommended):** The repowise Claude Code plugin registers the MCP server automatically. See [Claude Code Plugin →](claude-code-plugin).
-
-**Manual setup:** Add this to `.mcp.json` at your repo root:
-
-```json
-{
- "mcpServers": {
- "repowise": {
- "command": "repowise",
- "args": ["mcp", "/path/to/your-repo"],
- "description": "repowise codebase intelligence"
- }
- }
-}
-```
-
-If you're running repowise for the current directory, you can omit the path:
-
-```json
-{
- "mcpServers": {
- "repowise": {
- "command": "repowise",
- "args": ["mcp"]
- }
- }
-}
-```
-
-### Codex
-
-Run the Codex setup command from your repository:
-
-```bash
-repowise init --codex
-```
-
-This writes project-local `.codex/config.toml` with a Repowise MCP server entry:
-
-```toml
-[mcp_servers.repowise]
-command = "repowise"
-args = ["mcp"]
-cwd = "/path/to/your-repo"
-startup_timeout_sec = 20
-```
-
-It also writes `.codex/hooks.json` and managed `AGENTS.md`. See [Codex Integration](codex).
-
-### Cursor
-
-Add to `.cursor/mcp.json` in your repo or `~/.cursor/mcp.json` globally:
-
-```json
-{
- "mcpServers": {
- "repowise": {
- "command": "repowise",
- "args": ["mcp", "/path/to/your-repo"]
- }
- }
-}
-```
-
-### Cline
-
-Add to Cline's MCP settings file (`cline_mcp_settings.json`):
-
-```json
-{
- "mcpServers": {
- "repowise": {
- "command": "repowise",
- "args": ["mcp", "/path/to/your-repo"],
- "disabled": false,
- "autoApprove": ["get_overview", "get_context", "search_codebase"]
- }
- }
-}
-```
-
-### Windsurf
-
-Add to Windsurf's MCP configuration:
-
-```json
-{
- "mcpServers": {
- "repowise": {
- "command": "repowise",
- "args": ["mcp", "/path/to/your-repo"]
- }
- }
-}
-```
-
----
-
-## Transport protocols
-
-### stdio (default)
-
-The default transport. The MCP server runs as a subprocess of your editor, communicating over stdin/stdout. This is the correct option for Claude Code, Codex, Cursor, Cline, and Windsurf.
-
-```bash
-repowise mcp # stdio, current directory
-repowise mcp /path/to/repo # stdio, specific repo
-repowise mcp --transport stdio # explicit
-```
-
-### Streamable HTTP
-
-For HTTP-based MCP clients or headless setups where a persistent local server is preferable.
-
-```bash
-repowise mcp --transport streamable-http # HTTP on port 7338
-repowise mcp --transport streamable-http --port 8080 # Custom port
-```
-
-Clients connect to `http://localhost:7338/mcp`.
-
-### SSE (Server-Sent Events, legacy)
-
-For clients that still require the older SSE transport.
-
-```bash
-repowise mcp --transport sse # SSE on port 7338
-repowise mcp --transport sse --port 8080 # Custom port
-```
-
-Clients connect to `http://localhost:7338/sse` and receive server-sent events.
-
----
-
-## The default single-repo tools
-
-The ten flagship tools below, plus `list_repos`, are on by default in a
-single-repo server. Full reference: [MCP_TOOLS.md](https://github.com/repowise-dev/repowise/blob/main/docs/agent/MCP_TOOLS.md).
-
-### `get_answer(question, scope?)`
-
-One-call RAG over the wiki layer. Runs retrieval, gates on confidence, and synthesizes a 2–5 sentence answer with concrete file/symbol citations. Responses are cached per repository by question hash, so repeated questions cost nothing on the second call.
-
-**Parameters:**
-- `question` (string) — natural-language developer question
-- `scope` (optional, string) — path prefix to restrict retrieval (e.g. `"src/auth/"`)
-
-**Returns:**
-- `answer` (string) — synthesized 2–5 sentence answer
-- `citations` (list of strings) — file paths backing the answer
-- `confidence` (string) — `"high"`, `"medium"`, or `"low"`. High-confidence answers can be cited directly without verification reads; lower confidence indicates the agent should fall back to `search_codebase` or `Read`.
-- `fallback_targets` (list of strings) — top retrieval hits the agent should `Read` if it does not trust the synthesized answer
-- `candidate_files` (list of strings): ranked file paths retrieval resolved that the citations do not already name: up to 3 on a high-confidence answer, 5 otherwise
-- `retrieval` (list) — raw top-N hits with snippets
-
-**When to use:** First call on any code question. Collapses the typical "search → read → reason" loop into a single round-trip.
-
-**Example:**
-```
-get_answer(question="how does the request context get pushed and popped per request")
-
-→ answer: "Flask pushes a RequestContext onto _request_ctx_stack at the start
- of every request via Flask.wsgi_app, and pops it in the corresponding
- finally clause. The push happens in src/flask/app.py::Flask.wsgi_app."
- citations: ["src/flask/app.py", "src/flask/ctx.py"]
- confidence: "high"
-```
-
----
-
-### `get_symbol(symbol_id)`
-
-Resolves a fully-qualified symbol identifier to its definition. Returns the source body, signature, file location, line range, and any associated docstring without the agent having to grep then read.
-
-**Parameters:**
-- `symbol_id` (string) — qualified id of the form `path/to/file.py::ClassName::method_name`. Both `::` and `.` are accepted as the symbol separator (`Class::method` and `Class.method` resolve identically).
-
-**Returns:**
-- `symbol_id`, `name`, `kind` (`class`, `function`, `method`, …)
-- `file_path`, `start_line`, `end_line`
-- `signature` (recovered from source so base classes, decorators, and full type annotations are preserved)
-- `body` (the symbol's source code)
-- `docstring`
-
-**When to use:** When the question names a specific class, function, or method and you want its source without a separate `Read` call.
-
----
-
-### `get_overview()`
-
-Returns a high-level architecture summary of the indexed repository: key modules, entry points, tech stack, git health (churn percentiles, bus factors), and recent activity trends.
-
-**When to use:** Start every new task by calling this. It orients the AI and surfaces risk signals before any code is read.
-
-**Example response:**
-```
-Repository: repowise
-Architecture: Python monorepo (cli, core, server, web)
-Entry points: packages/cli/src/repowise/cli/main.py
-Tech stack: Python, FastAPI, SQLite, LanceDB, Next.js
-Top hotspots: init_cmd.py (99.8th %ile), test_mcp.py (99.5th %ile)
-Bus factor risk: git_indexer.py (1 author)
-```
-
----
-
-### `get_context(targets, include?, compact?)`
-
-Returns rich context for one or more files, modules, or symbols: documentation, ownership, last change, governing decisions, and freshness status.
-
-**Parameters:**
-- `targets` (list of strings) — file paths, module names, or symbol names
-- `include` (optional) — opt-in blocks such as `"ownership"`, `"last_change"`, `"decisions"`, `"callers"`, `"metrics"`, `"skeleton"`, `"health"`, and `"doc_drift"` (the documents that name this file)
-- `compact` (optional, default `True`) — when `True`, drops the `structure` block, the `imported_by` list, and per-symbol docstrings/end-line fields to keep the response under ~10K characters. Pass `compact=False` to receive the full payload, e.g. when you specifically need the import-graph dependents or every symbol docstring on a dense file.
-
-**When to use:** Before reading or editing any file. Faster and richer than reading the raw source.
-
-**Example:**
-```
-get_context(targets=["packages/cli/src/repowise/cli/commands/init_cmd.py"])
-
-→ Purpose: Orchestrates the 4-phase init pipeline
- Owner: RaghavChamadiya (89% of commits)
- Last changed: 3 days ago (14 commits in 90d — 99.8th %ile)
- Decisions: "Use interactive mode when stdin is a TTY"
- Freshness: current
-```
-
----
-
-### `get_risk(targets)`
-
-Returns a modification risk assessment for each target file.
-
-**Parameters:**
-- `targets` (list of strings) — file paths
-
-**Returns per file:**
-- Churn percentile rank
-- Number of direct and transitive dependents
-- Co-change partners (files that tend to change together)
-- Bus factor (number of authors with meaningful ownership)
-- Change trend: increasing / decreasing / stable
-
-**When to use:** Required before making changes to any file, especially in hotspot areas.
-
-**Example:**
-```
-get_risk(targets=["packages/core/src/repowise/core/ingestion/git_indexer.py"])
-
-→ Hotspot: 99.3th %ile (9 commits in 90 days)
- Dependents: 7 direct, 23 transitive
- Co-change partners: init_cmd.py, update_cmd.py
- Bus factor: 1 (sole author: RaghavChamadiya)
- Trend: increasing
- Recommendation: High risk — coordinate before changing
-```
-
----
-
-### `get_why(query?, targets?)`
-
-Searches for architectural decisions and intent behind code structure.
-
-**Parameters:**
-- `query` (string) — natural language question ("why JWT instead of sessions?")
-- `targets` (optional, list) — file paths to focus on
-
-**Returns:**
-- Matching decision records with title, rationale, and status
-- Git archaeology: commit messages and PR descriptions that explain design choices
-- Origin story for specific files (if `targets` provided)
-- Decision health (staleness scores for applicable decisions)
-
-**When to use:** Before any architectural change. Ask "why is this structured this way" before refactoring.
-
-**Example:**
-```
-get_why(query="why is rate limiting done in the app layer")
-
-→ Decision: "Rate limiting at application layer"
- Rationale: Need per-user limits; load balancer can't distinguish users
- Status: active
- Source: cli (manually recorded)
- Affected: server/middleware/rate_limit.py
-```
-
----
-
-### `search_codebase(query, limit?, mode?, kind?, symbol_kind?, page_type?)`
-
-Hybrid code search. Depending on the query, it searches the indexed **symbols**, **file paths**, or the **wiki** — a single tool for "find this function", "find this file", and "find code about this topic".
-
-**Parameters:**
-- `query` (string) — identifier, path, or natural-language query
-- `limit` (int, default 5) — max results
-- `mode` (optional) — `auto` (default) \| `concept` \| `symbol` \| `path` \| `hybrid`
-- `kind` (optional) — `implementation` \| `test` \| `config` \| `doc`
-- `symbol_kind` (optional) — restrict symbol hits by kind (`function`, `class`, `method`, …)
-- `page_type` (optional) — restrict to one page type. The two you will reach for are `file_page` (the always-on per-file docs) and `module_page` (the subsystem/concept pages).
-
-**Modes:** `auto` routes by shape — an identifier searches indexed symbols (results carry `symbol_id` + line bounds, pipe into `get_symbol`), a path searches file pages (pipe into `get_context`), prose runs wiki-semantic search, and mixed queries run hybrid (symbols first). Force a branch with an explicit `mode`.
-
-**Returns:** Symbol hits (`symbol_id`, `file`, line bounds, `signature`, `next: "get_symbol"`), file hits (`page_id`, `file`, `next: "get_context"`), or ranked wiki pages with relevance scores and a `search_method`. Recently-changed files receive a freshness boost.
-
-**When to use:** Locating a symbol or file by name, or discovering code by topic — prefer over `grep`/`find`.
-
-**Example:**
-```
-search_codebase(query="GitIndexer index_repo")
-
-→ 1. symbol packages/core/.../git_indexer/indexer.py::GitIndexer.index_repo
- async def index_repo(...) -> tuple[GitIndexSummary, list[dict]] (lines 75-306)
- next: get_symbol
-
-search_codebase(query="how database connections are pooled")
-
-→ 1. packages/server/src/repowise/server/db.py (0.92)
- "Creates async SQLAlchemy engine with connection pooling..."
-```
-
----
-
-### `get_change_risk(revspec?, extensions?, exclude_patterns?, baseline?)`
-
-Live risk scoring for one commit or a `base..head` range. Unlike `get_risk`
-(indexed files), this scores the shape of the live diff and needs no index
-refresh.
-
-**Parameters:**
-- `revspec` (optional, string) — commit or `base..head`; omit it to score uncommitted work
-- `extensions` (optional) — file suffixes to count (e.g. `[".py", ".ts"]`)
-- `exclude_patterns` (optional) — gitignore-style paths; combined with root `.riskignore`
-- `baseline` (optional, int) — recent commits for percentile ranking (default `200`)
-
-**Returns:** `risk_percentile` ranks the change among recent commits by diff
-size and spread; it is not a bug predictor. `fix_history` reports the
-recency-weighted bug-fix record of the files touched (manifests and lockfiles
-excluded), which is what distinguishes a small dangerous change from a large
-boring one. `diff_shape` is one sentence on size and spread and its limits, plus
-`impacted_tests` when a per-test coverage map is ingested
-(`repowise coverage add`). The raw 0-10 `score` and its absolute
-`fallback_band` sit behind `include=["diagnostics"]`: the score ranks 0.99
-against lines added, so the percentile already carries the ranking.
-`include=["scales"]` adds the `review_priority` / `classification` tercile and
-the kind, units, range and shared thresholds for each value.
-
-**When to use:** Before merging a commit or PR range, or on work you have not
-committed yet.
-
-**Example:**
-```
-get_change_risk(revspec="main..HEAD", extensions=[".py"], exclude_patterns=["tests/"])
-```
-
----
-
-### `get_health(targets?, include?, limit?)`
-
-Code-health marker scores (defect risk, maintainability, performance) — the
-same deterministic markers as `repowise health`. Zero LLM calls.
-
-**Parameters:**
-- `targets` (optional) — file paths, or `module:foo`; empty = dashboard mode
-- `include` (optional) — opt-in blocks such as `"biomarkers"`, `"refactoring"`,
- `"trend"`, `"coverage"`, `"accuracy"`, `"signals"`, `"churn_complexity"`,
- `"doc_drift"`
-- `limit` (optional, int) — max lowest-scoring files (default 20)
-
-**When to use:** Self-check a change before opening a PR, or find the worst
-files before refactoring. Pair with `get_risk` on hotspots.
-
-**Example:**
-```
-get_health()
-get_health(targets=["src/api/server.py"], include=["signals"])
-```
-
----
-
-### `get_dead_code(kind?, min_confidence?, safe_only?, tier?, directory?)`
-
-Returns a tiered report of unused code.
-
-**Parameters:**
-- `kind` — filter by `unreachable_file`, `unused_export`, `unused_internal`, `zombie_package`
-- `min_confidence` — 0.0–1.0, default 0.4
-- `safe_only` — only return findings marked `safe_to_delete`
-- `tier` — `high`, `medium`, or `low`
-- `directory` — limit to a specific directory
-- `group_by` — `directory` or `owner`
-
-**When to use:** Before any cleanup or removal tasks. Gives confirmed unused code rather than guesses.
-
-Also always on by default: `list_repos()` (repo aliases for the `repo=` parameter
-on other tools). See [Supplementary tools](#supplementary-tools) below.
-
-Full parameter tables and return shapes live in the repo guide:
-[docs/agent/MCP_TOOLS.md](https://github.com/repowise-dev/repowise/blob/main/docs/agent/MCP_TOOLS.md).
-
----
-
-## Supplementary tools
-
-### `list_repos()` (default in a workspace)
-
-Lists every configured alias in a workspace. It is not advertised in
-single-repo mode, where the server is bound to the only repository.
-
-### Workspace-only (opt-in)
-
-These need a workspace and are off by default there too. Enable them the same
-way as the opt-in tools below:
-
-| Tool | Purpose |
-|------|---------|
-| `get_architecture()` | Whole-system coupling, cyclic core, 1–10 architecture score |
-| `get_blast_radius(targets, …)` | Cross-repo downstream impact of changing a service |
-| `get_conformance(…)` | Architecture-rule violations and dependency cycles |
-
-### Opt-in tools (off by default)
-
-Registered everywhere but not advertised until enabled via
-`mcp.tools: ["+name"]` in `.repowise/config.yaml`, the dashboard Settings page,
-or `repowise mcp --tools "+name"`:
-
-| Tool | Purpose |
-|------|---------|
-| `get_dependency_path(source, target)` | Shortest graph path between two files/modules |
-| `get_execution_flows(…)` | Top entry points and call traces |
-| `generate_refactoring_code(…)` | Code for a ranked refactoring plan from `get_health` |
-| `set_finding_status(…)` | Record a triage status on a refactoring plan |
-
----
-
-## How AI editors use these tools
-
-The tools are designed to form a decision workflow:
-
-1. **Before any task** → `get_overview()` to orient
-2. **Before reading a file** → `get_context(targets=[...])` instead of reading raw source
-3. **Before editing a file** → `get_risk(targets=[...])` to assess impact
-4. **Before merging a commit / PR** → `get_change_risk(revspec="main..HEAD")`
-5. **Before refactoring** → `get_health()` (and `get_dead_code` for cleanup)
-6. **When facing an architectural question** → `get_why(query="...")` before changing structure
-7. **When locating code** → `search_codebase(query="...")` before grep
-
-The [CLAUDE.md generator](claude-md-generator) writes these instructions directly into your project's CLAUDE.md, so Claude Code follows this workflow automatically. Codex setup writes the same workflow into managed `AGENTS.md`.
diff --git a/website/opencode.html b/website/opencode.html
new file mode 100644
index 000000000..2af1ad140
--- /dev/null
+++ b/website/opencode.html
@@ -0,0 +1,14 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>Repowise docs moved to docs.repowise.dev</title>
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<meta http-equiv="refresh" content="1; url=https://docs.repowise.dev/getting-started/for-agents">
+<link rel="canonical" href="https://docs.repowise.dev/getting-started/for-agents">
+</head>
+<body>
+<h1>Repowise docs moved to docs.repowise.dev</h1>
+<p>This page is now at <a href="https://docs.repowise.dev/getting-started/for-agents">https://docs.repowise.dev/getting-started/for-agents</a>.</p>
+</body>
+</html>
diff --git a/website/opencode.md b/website/opencode.md
deleted file mode 100644
index 194ff3d53..000000000
--- a/website/opencode.md
+++ /dev/null
@@ -1,105 +0,0 @@
----
-layout: default
-title: OpenCode Integration
-nav_order: 5.6
----
-
-# OpenCode Integration
-{: .no_toc }
-
-Use Repowise with OpenCode via the `opencode` LLM provider. No API keys — OpenCode manages auth and model selection.
-{: .fs-6 .fw-300 }
-
----
-
-## Table of contents
-{: .no_toc .text-delta }
-
-1. TOC
-{:toc}
-
----
-
-## Quick setup
-
-```bash
-curl -fsSL https://opencode.ai/install | bash
-opencode # first-run setup: configure your provider
-
-cd /path/to/your-repo
-repowise init --provider opencode --yes
-```
-
-OpenCode is detected automatically when it's on `PATH`. No API keys to store.
-
-## Provider
-
-`opencode` uses your local OpenCode CLI:
-
-```bash
-repowise init --provider opencode --yes
-```
-
-It runs `opencode run --format json` with the repository as the working
-directory:
-
-```bash
-cd <repo> && opencode run --format json
-```
-
-Repowise sends the prompt on **stdin**, parses OpenCode's **JSONL** output, and treats `opencode/*` cost as `$0.00`.
-
-### Model selection
-
-`opencode/default` uses OpenCode's configured default model. To pick a specific model:
-
-```bash
-repowise init --provider opencode --model opencode/deepseek-v4-pro
-```
-
-List available models:
-
-```bash
-opencode models
-```
-
-### Interactive selection
-
-When you run `repowise init` interactively, the provider table includes `opencode` with a status indicator. If OpenCode is installed, it shows as available and you can select it directly.
-
-If OpenCode is not installed, the interactive prompt shows:
-
-```
-Install: curl -fsSL https://opencode.ai/install | bash
-Setup: opencode (first run sets up your provider)
-Models: opencode models (list available models)
-```
-
-## Reasoning
-
-The opencode provider does not pass reasoning effort flags. OpenCode handles reasoning through its own model and agent configuration.
-
-## Concurrency
-
-Up to 4 `opencode run` subprocesses run at once. Set `REPOWISE_OPENCODE_CONCURRENCY` to change the limit; values below 1 are treated as 1.
-
-```bash
-REPOWISE_OPENCODE_CONCURRENCY=2 repowise generate --unwritten
-```
-
-## Comparison with Codex CLI
-
-| Aspect | `opencode` | `codex_cli` |
-|--------|-----------|-------------|
-| CLI | `opencode run` | `codex exec` |
-| Auth | OpenCode providers | `codex login` |
-| Format | `--format json` JSONL | `--json` JSONL |
-| Reasoning | N/A (OpenCode manages) | `model_reasoning_effort` |
-| Editor integration | None | MCP, hooks, plugin |
-| Key storage | No | No |
-
-## Official docs
-
-- [OpenCode](https://opencode.ai)
-- [OpenCode GitHub](https://github.com/anomalyco/opencode)
-- [OpenCode Docs](https://opencode.ai/docs)
diff --git a/website/self-hosting.html b/website/self-hosting.html
new file mode 100644
index 000000000..5d8f2d1a3
--- /dev/null
+++ b/website/self-hosting.html
@@ -0,0 +1,14 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>Repowise docs moved to docs.repowise.dev</title>
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<meta http-equiv="refresh" content="1; url=https://docs.repowise.dev/installation/install">
+<link rel="canonical" href="https://docs.repowise.dev/installation/install">
+</head>
+<body>
+<h1>Repowise docs moved to docs.repowise.dev</h1>
+<p>This page is now at <a href="https://docs.repowise.dev/installation/install">https://docs.repowise.dev/installation/install</a>.</p>
+</body>
+</html>
diff --git a/website/self-hosting.md b/website/self-hosting.md
deleted file mode 100644
index 53ef66305..000000000
--- a/website/self-hosting.md
+++ /dev/null
@@ -1,258 +0,0 @@
----
-layout: default
-title: Self-hosting & Deployment
-nav_order: 10
----
-
-# Self-hosting & Deployment
-{: .no_toc }
-
-Docker setup, environment variables, and running repowise in production or CI.
-{: .fs-6 .fw-300 }
-
----
-
-## Table of contents
-{: .no_toc .text-delta }
-
-1. TOC
-{:toc}
-
----
-
-## Docker (quickstart)
-
-The Docker image bundles the Python backend, the Next.js frontend, and all dependencies. No Node.js required on the host.
-
-```bash
-docker pull ghcr.io/repowise-dev/repowise:latest
-
-docker run \
- -p 7337:7337 \
- -p 3000:3000 \
- -v $(pwd):/repo \
- -v $(pwd)/.repowise:/data \
- -e ANTHROPIC_API_KEY="sk-ant-..." \
- ghcr.io/repowise-dev/repowise:latest \
- serve /repo
-```
-
-Open [http://localhost:3000](http://localhost:3000) to access the dashboard.
-
----
-
-## Docker Compose
-
-A full setup with the API server, web UI, and a PostgreSQL database:
-
-```yaml
-# docker-compose.yml
-services:
- db:
- image: postgres:16
- environment:
- POSTGRES_DB: repowise
- POSTGRES_USER: repowise
- POSTGRES_PASSWORD: repowise
- volumes:
- - postgres_data:/var/lib/postgresql/data
- healthcheck:
- test: ["CMD-SHELL", "pg_isready -U repowise"]
- interval: 5s
- timeout: 5s
- retries: 5
-
- repowise:
- image: ghcr.io/repowise-dev/repowise:latest
- ports:
- - "7337:7337"
- - "3000:3000"
- volumes:
- - ./:/repo
- - lancedb_data:/data/lancedb
- environment:
- REPOWISE_DB_URL: postgresql+asyncpg://repowise:repowise@db:5432/repowise
- REPOWISE_HOST: 0.0.0.0
- ANTHROPIC_API_KEY: ${ANTHROPIC_API_KEY}
- depends_on:
- db:
- condition: service_healthy
- command: serve /repo --host 0.0.0.0
-
-volumes:
- postgres_data:
- lancedb_data:
-```
-
-```bash
-ANTHROPIC_API_KEY=sk-ant-... docker compose up
-```
-
----
-
-## Environment variables
-
-| Variable | Default | Description |
-|----------|---------|-------------|
-| `ANTHROPIC_API_KEY` | — | Anthropic API key |
-| `OPENAI_API_KEY` | — | OpenAI API key |
-| `GEMINI_API_KEY` | — | Google Gemini API key |
-| `REPOWISE_PROVIDER` | auto | Override provider detection |
-| `REPOWISE_DB_URL` | SQLite (`.repowise/wiki.db`) | PostgreSQL connection string |
-| `REPOWISE_HOST` | `127.0.0.1` | API server bind host |
-| `REPOWISE_API_KEY` | — | Bearer token for the API. Required to serve callers on other hosts; without it requests from off-host are refused |
-| `REPOWISE_PORT` | `7337` | API server port |
-| `REPOWISE_MCP_PORT` | `7338` | MCP SSE server port |
-
----
-
-## Building from source
-
-```bash
-git clone https://github.com/repowise-dev/repowise.git
-cd repowise
-
-# Python dependencies
-uv sync --all-extras
-
-# Web frontend
-npm install
-npm run build
-
-# Run
-repowise serve
-```
-
----
-
-## Running in CI
-
-Use `--no-prose` for CI pipelines that don't need model-written prose, just the analysis signals and a structural wiki:
-
-```yaml
-# GitHub Actions example
-- name: Index codebase
- run: |
- pip install repowise
- repowise init --no-prose --yes
-
-- name: Check dead code
- run: repowise dead-code --safe-only --format json > dead-code-report.json
-
-- name: Upload report
- uses: actions/upload-artifact@v4
- with:
- name: dead-code-report
- path: dead-code-report.json
-```
-
-Documentation drift needs no index at all, so it can gate a pull request on its
-own. It fails the job when a document names a path, heading or build target the
-tree no longer has:
-
-```yaml
-- name: Check documentation drift
- run: repowise doc-drift --check --format github
-```
-
-For full documentation generation in CI (with LLM):
-
-```yaml
-- name: Generate docs
- env:
- ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
- run: |
- pip install repowise
- repowise init --yes --concurrency 10
-
-- name: Export to markdown
- run: repowise export --format markdown --output ./wiki-export
-```
-
----
-
-## Keeping the index current in CI
-
-Update the wiki on every push to main:
-
-```yaml
-on:
- push:
- branches: [main]
-
-jobs:
- update-wiki:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v4
- with:
- fetch-depth: 0 # Full history for git analysis
-
- - name: Restore index cache
- uses: actions/cache@v4
- with:
- path: .repowise
- key: repowise-${{ github.sha }}
- restore-keys: repowise-
-
- - name: Update wiki
- env:
- ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
- run: |
- pip install repowise
- repowise update --yes
-```
-
-{: .note }
-Use `fetch-depth: 0` to include full git history. repowise uses git log for ownership and churn analysis — shallow clones will produce incomplete results.
-
----
-
-## Reverse proxy (nginx)
-
-To serve the dashboard at a custom domain:
-
-```nginx
-server {
- listen 80;
- server_name docs.yourcompany.com;
-
- location / {
- proxy_pass http://localhost:3000;
- proxy_set_header Host $host;
- proxy_set_header X-Real-IP $remote_addr;
- }
-
- location /api/ {
- proxy_pass http://localhost:7337/;
- proxy_set_header Host $host;
- proxy_set_header X-Real-IP $remote_addr;
- }
-}
-```
-
----
-
-## Database migrations
-
-On startup the API brings the schema up to the running version on both SQLite and PostgreSQL: it creates missing tables, adds missing columns and indexes, drops NOT NULL from columns that became optional, and widens text columns that got longer. The Docker image needs no separate migration step for an upgrade.
-
-PostgreSQL schema history is also kept as Alembic migrations, which add what startup does not: the pgvector `embedding` column and the full-text search index. On a database that Alembic created, apply them from a source checkout:
-
-```bash
-cd packages/core
-DATABASE_URL=postgresql://user:pass@host/dbname alembic upgrade head
-```
-
----
-
-## Requirements summary
-
-| Component | Requirement |
-|-----------|-------------|
-| Python | 3.11+ |
-| Git | Any recent version |
-| Node.js | 20+ (for web UI without Docker) |
-| Docker | Any version (alternative to Node.js) |
-| PostgreSQL | 14+ (optional, SQLite is the default) |
-| LLM API key | Anthropic, OpenAI, Gemini, or Ollama (not needed for `--no-prose`) |
diff --git a/website/web-dashboard.html b/website/web-dashboard.html
new file mode 100644
index 000000000..fc0556eae
--- /dev/null
+++ b/website/web-dashboard.html
@@ -0,0 +1,14 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<title>Repowise docs moved to docs.repowise.dev</title>
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<meta http-equiv="refresh" content="1; url=https://docs.repowise.dev/dashboard">
+<link rel="canonical" href="https://docs.repowise.dev/dashboard">
+</head>
+<body>
+<h1>Repowise docs moved to docs.repowise.dev</h1>
+<p>This page is now at <a href="https://docs.repowise.dev/dashboard">https://docs.repowise.dev/dashboard</a>.</p>
+</body>
+</html>
diff --git a/website/web-dashboard.md b/website/web-dashboard.md
deleted file mode 100644
index 8f37ec961..000000000
--- a/website/web-dashboard.md
+++ /dev/null
@@ -1,183 +0,0 @@
----
-layout: default
-title: Web Dashboard
-nav_order: 6
----
-
-# Web Dashboard
-{: .no_toc }
-
-Browse your codebase wiki, explore architecture, and search from a browser.
-{: .fs-6 .fw-300 }
-
----
-
-## Table of contents
-{: .no_toc .text-delta }
-
-1. TOC
-{:toc}
-
----
-
-## Starting the dashboard
-
-```bash
-repowise serve
-```
-
-This starts two servers:
-
-| Server | URL | Purpose |
-|--------|-----|---------|
-| API | `http://localhost:7337` | REST API (FastAPI) |
-| Web UI | `http://localhost:3000` | Next.js frontend |
-
-Open [http://localhost:3000](http://localhost:3000) in your browser.
-
-On first run, repowise downloads and caches the frontend automatically. Node.js 20+ must be installed. For Docker-based setup without Node.js, see [Self-hosting →](self-hosting).
-
-### Custom ports
-
-```bash
-repowise serve --port 8080 --ui-port 4000
-```
-
-### API only (no UI)
-
-```bash
-repowise serve --no-ui
-```
-
-### Expose on your network
-
-```bash
-repowise serve --host 0.0.0.0
-```
-
----
-
-## Dashboard views
-
-### Wiki browser
-
-The main view. Shows all indexed pages organized by module and file. Each page contains:
-
-- AI-generated documentation for the file or module
-- Key symbols (functions, classes, interfaces) with signatures
-- Dependency list (what this file imports and what imports it)
-- Git sidebar: last commit, contributors, churn percentile, change history
-
-Pages marked stale (underlying file has changed since last generation) show a regeneration prompt.
-
-### Dependency graph
-
-An interactive force-directed graph built with D3.js. Handles repositories with 2,000+ nodes without degrading.
-
-- **Zoom and pan** to navigate large graphs
-- **Click a node** to open its wiki page
-- **Hover** to see the file name and module
-- **Filter by module** to isolate a subsystem
-- **Toggle heat map** to color nodes by churn intensity (red = high churn, green = stable)
-- **Search** to highlight matching nodes
-
-### Search
-
-Full-text and semantic search across the entire wiki. Press `Ctrl+K` (or `Cmd+K`) from anywhere in the dashboard to open the global command palette.
-
-Search modes:
-- **Full-text** — keyword matching against page content
-- **Semantic** — natural language queries using vector embeddings
-- **Symbol** — search by function name, class name, or method signature
-
-### Symbol index
-
-A filterable table of every indexed symbol: functions, classes, methods, interfaces, types. Columns include:
-
-- Name and signature
-- File and module
-- Kind (function, class, method, etc.)
-- Usage count (how many other files reference it)
-
-Click any symbol to jump to its wiki page.
-
-### Coverage dashboard
-
-Shows documentation freshness across the codebase:
-
-- **Fresh** — page is current with the source file
-- **Stale** — source file has changed since the page was generated
-- **Missing** — file exists but has no wiki page
-
-One-click regeneration for individual stale pages, or bulk-regenerate all with `repowise update`.
-
-### Ownership view
-
-Shows contributor attribution across modules:
-
-- Per-file owner (contributor with the most commit weight)
-- Bus factor risk detection (files where one person holds >80% of knowledge)
-- Contributor activity over time
-- Module-level ownership breakdown
-
-### Hotspots
-
-A ranked list of high-churn files. Each entry shows:
-
-- File path and module
-- Churn percentile (e.g., "99.8th %ile")
-- Number of commits in the last 90 days
-- Primary owner
-- Trend direction (increasing / stable / decreasing)
-
-### Dead code finder
-
-Lists unused code with confidence scores and bulk actions:
-
-- **Unreachable files** — files with no inbound imports
-- **Unused exports** — exported symbols with no external consumers
-- **Unused internals** — internal symbols never called
-- **Zombie packages** — installed dependencies never imported
-
-Each finding shows confidence score and a "safe to delete" flag for high-confidence cases. Findings can be exported as a Markdown checklist.
-
-### Decision tracker
-
-All architectural decisions captured by repowise, organized by:
-
-- **Status** — proposed, active, deprecated, superseded
-- **Source** — git archaeology, inline markers, README mining, manually added
-- **Health score** — staleness relative to how much the affected code has changed
-
-Proposed decisions (mined automatically) can be confirmed or dismissed from this view.
-
-### Codebase chat
-
-Ask natural language questions about your codebase. The chat endpoint uses the wiki index as retrieval context, so answers are grounded in your actual code — not a hallucination.
-
-Example questions:
-- "How does authentication work?"
-- "Which module handles database migrations?"
-- "What are the entry points for the CLI?"
-- "Show me all files that depend on the session module"
-
----
-
-## REST API
-
-The API at `http://localhost:7337` exposes everything in the dashboard programmatically. Key endpoints:
-
-| Endpoint | Description |
-|----------|-------------|
-| `GET /health` | Server health check |
-| `GET /repos/{id}/pages` | List all wiki pages |
-| `GET /repos/{id}/pages/{page_id}` | Get a wiki page |
-| `GET /repos/{id}/search?q=...` | Full-text search |
-| `GET /repos/{id}/symbols` | List all symbols |
-| `GET /repos/{id}/graph` | Dependency graph data |
-| `GET /repos/{id}/dead-code` | Dead code findings |
-| `GET /repos/{id}/decisions` | Decision records |
-| `POST /repos/{id}/chat` | Codebase chat |
-| `GET /repos/{id}/generate-claude-md` | Generate CLAUDE.md content |
-
-Full API docs are available at `http://localhost:7337/docs` (Swagger UI) when the server is running.