docs: rename remaining code-explorer references to codescout

Updates CONTRIBUTING.md, CHANGELOG.md, scripts, tests, copilot
instructions, issue template, and renames CODE-EXPLORER-EMBEDDINGS-SETUP.md.
Preserves code-explorer-routing plugin name (separate project).

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

Author: mareurs

.github/ISSUE_TEMPLATE/bug_report.md

@@ -22,5 +22,5 @@ labels: bug
 
 - OS:
 - Rust version:
-- code-explorer version:
+- codescout version:
 - MCP client (e.g., Claude Code):

CHANGELOG.md

@@ -4,13 +4,13 @@ All notable changes to codescout are documented here.
 
 ## [0.2.0] — codescout
 
-> **TL;DR:** The project was renamed from `code-explorer` to `codescout`. If you're
+> **TL;DR:** The project was renamed from `codescout` to `codescout`. If you're
 > migrating, update your MCP config and any scripts that reference the old binary name.
 > [Full story and migration guide →](docs/manual/src/history.md)
 
 ### Breaking changes
 
-- **Binary renamed:** `code-explorer` → `codescout`
+- **Binary renamed:** `codescout` → `codescout`
 - **MCP server ID renamed** — update `.mcp.json` or Claude Code settings accordingly
 - **Tool renames** (API consistency):
 
@@ -198,7 +198,7 @@ All notable changes to codescout are documented here.
 - `check_onboarding_performed` — check if onboarding has run
 
 ### Infrastructure
-- `.mcp.json` — Claude Code MCP config for using code-explorer on its own source
+- `.mcp.json` — Claude Code MCP config for using codescout on its own source
 - 141 tests: 136 unit + 5 end-to-end integration tests
 - Integration tests cover: read→search→replace, AST analysis, memory+config roundtrip,
   git history creation, onboarding+explore

CLAUDE.md

@@ -148,11 +148,11 @@ This project has a companion Claude Code plugin at **`../claude-plugins/code-exp
 The `PreToolUse` hook will **block** any attempt to use the native `Read`, `Grep`, or `Glob` tools on source code files (`.rs`, `.ts`, `.py`, etc). You will see `PreToolUse:Read hook error` if you try.
 
 **You MUST use codescout's own MCP tools to read source code:**
-- `mcp__code-explorer__list_symbols(path)` — see all symbols in a file/dir
-- `mcp__code-explorer__find_symbol(name, include_body=true)` — read a function body
-- `mcp__code-explorer__search_pattern(pattern)` — regex search
-- `mcp__code-explorer__semantic_search(query)` — concept-level search
-- `mcp__code-explorer__read_file(path)` — for non-source files (markdown, toml, json)
+- `mcp__codescout__list_symbols(path)` — see all symbols in a file/dir
+- `mcp__codescout__find_symbol(name, include_body=true)` — read a function body
+- `mcp__codescout__search_pattern(pattern)` — regex search
+- `mcp__codescout__semantic_search(query)` — concept-level search
+- `mcp__codescout__read_file(path)` — for non-source files (markdown, toml, json)
 
 **Configuration:**
 - Auto-detects codescout from `.mcp.json` or `~/.claude/settings.json`

CODE-EXPLORER-EMBEDDINGS-SETUP.md CODESCOUT-EMBEDDINGS-SETUP.mdCODE-EXPLORER-EMBEDDINGS-SETUP.md renamed to CODESCOUT-EMBEDDINGS-SETUP.md

@@ -1,7 +1,7 @@
 # Code Explorer — Embedding Setup on WSL2 Behind Zscaler
 
 This document captures the full journey of getting semantic search working in
-`code-explorer` on a WSL2 machine behind a Zscaler corporate proxy. It is
+`codescout` on a WSL2 machine behind a Zscaler corporate proxy. It is
 written as a troubleshooting narrative so that future developers can skip the
 trial-and-error and go straight to the working solution.
 
@@ -13,7 +13,7 @@ trial-and-error and go straight to the working solution.
 |---|---|
 | OS | Ubuntu on WSL2 (Windows host) |
 | Network proxy | Zscaler (SSL-inspecting corporate proxy) |
-| Tool | `code-explorer` MCP server (built from source) |
+| Tool | `codescout` MCP server (built from source) |
 | Target | `local:AllMiniLML6V2Q` — CPU-only, INT8-quantized, ~22 MB |
 
 ---
@@ -24,19 +24,19 @@ trial-and-error and go straight to the working solution.
 
 ```
 The local embedding model isn't available in this environment. The
-code-explorer server was built without the local-embed feature, so
+codescout server was built without the local-embed feature, so
 semantic search isn't supported here.
 ```
 
 ### Cause
 
-`code-explorer` has an optional Cargo feature `local-embed` that pulls in
+`codescout` has an optional Cargo feature `local-embed` that pulls in
 `fastembed-rs` and the ONNX Runtime. The default build omits it.
 
 ### Fix
 
 ```bash
-cd /home/vradu/work/tools/code-explorer
+cd /home/vradu/work/tools/codescout
 git pull
 cargo install --path . --features local-embed
 ```
@@ -125,7 +125,7 @@ Missing Input: encoder.layer.0.attention.output.LayerNorm.weight
 
 ### Cause
 
-`code-explorer` statically links ORT 1.20.0 via the `ort-download-binaries`
+`codescout` statically links ORT 1.20.0 via the `ort-download-binaries`
 Cargo feature. The Qdrant model `Qdrant/bge-small-en-v1.5-onnx-Q` was
 exported with:
 
@@ -173,10 +173,10 @@ not graph-fused operators.
 
 ### Step-by-step setup
 
-**1. Rebuild code-explorer with local-embed** (if not already done)
+**1. Rebuild codescout with local-embed** (if not already done)
 
 ```bash
-cd /home/vradu/work/tools/code-explorer
+cd /home/vradu/work/tools/codescout
 cargo install --path . --features local-embed
 ```
 
@@ -284,9 +284,9 @@ models, weights) are stored in XetHub LFS and always redirect to
 `cas-bridge.xethub.hf.co`, which Zscaler blocks. The workaround is to
 download from the Windows host browser and copy into WSL2.
 
-### 4 — ORT is statically compiled into code-explorer
+### 4 — ORT is statically compiled into codescout
 
 The `ort-download-binaries` Cargo feature downloads the ORT binary at build
 time and links it statically. You cannot swap the ORT runtime at runtime via
 `LD_PRELOAD` or environment variables. If a model requires a different ORT
-version, you must rebuild code-explorer targeting that version.
+version, you must rebuild codescout targeting that version.

CONTRIBUTING.md

@@ -1,12 +1,12 @@
-# Contributing to code-explorer
+# Contributing to codescout
 
 We welcome contributions! Whether it's a bug fix, new language support, or documentation improvement — we're happy to review it.
 
 ## Getting Started
 
 ```bash
-git clone https://github.com/mareurs/code-explorer.git
-cd code-explorer
+git clone https://github.com/mareurs/codescout.git
+cd codescout
 cargo build
 cargo test
 ```
@@ -36,7 +36,7 @@ cargo test
 
 ## Using Claude Code?
 
-PRs generated with Claude Code are welcome. Just mention it in the PR description. If you're using code-explorer itself as an MCP server while contributing to code-explorer — that's the dream. Let us know how it went.
+PRs generated with Claude Code are welcome. Just mention it in the PR description. If you're using codescout itself as an MCP server while contributing to codescout — that's the dream. Let us know how it went.
 
 ## Project Structure
 

scripts/capture-screenshot.sh

@@ -7,9 +7,9 @@ OUTPUT="$PROJECT_ROOT/docs/images/dashboard.png"
 SCRIPTS_DIR="$PROJECT_ROOT/scripts"
 
 # --- Check binary ---
-BINARY=$(command -v code-explorer 2>/dev/null || echo "$PROJECT_ROOT/target/release/code-explorer")
+BINARY=$(command -v codescout 2>/dev/null || echo "$PROJECT_ROOT/target/release/codescout")
 if [[ ! -x "$BINARY" ]]; then
-  echo "ERROR: code-explorer binary not found."
+  echo "ERROR: codescout binary not found."
   echo "Build it first: cargo build --release"
   exit 1
 fi

scripts/install-lsp.sh

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 #
-# Install LSP servers for code-explorer.
+# Install LSP servers for codescout.
 #
 # Usage:
 #   ./scripts/install-lsp.sh --check          # show what's installed / missing
@@ -17,7 +17,7 @@ set -euo pipefail
 # ── Globals ──────────────────────────────────────────────────────────────────
 
 INSTALL_DIR="${HOME}/.local/bin"
-DOWNLOAD_DIR="${TMPDIR:-/tmp}/code-explorer-lsp-install"
+DOWNLOAD_DIR="${TMPDIR:-/tmp}/codescout-lsp-install"
 
 ALL_LANGS=(rust python typescript go java kotlin c csharp ruby)
 
@@ -382,7 +382,7 @@ usage() {
     cat <<EOF
 Usage: $(basename "$0") [OPTIONS] [LANGUAGES...]
 
-Install LSP servers for code-explorer.
+Install LSP servers for codescout.
 
 Options:
   --check   Show which LSP servers are installed / missing

tests/mcp-smoke-kotlin.sh

@@ -1,5 +1,5 @@
 #!/usr/bin/env bash
-# End-to-end MCP smoke test for code-explorer against a Kotlin project.
+# End-to-end MCP smoke test for codescout against a Kotlin project.
 # Calls the real binary over stdio via the `mcp` CLI tool.
 # Run from the project root: ./tests/mcp-smoke-kotlin.sh
 #
@@ -51,13 +51,13 @@ fail() {
 
 # ── Setup ────────────────────────────────────────────────────────────────────
 
-echo "Building code-explorer (release)..."
+echo "Building codescout (release)..."
 cargo build --release 2>&1 | tail -1
 echo "done"
 echo ""
 
 export PATH="$HOME/.local/bin:$PATH"
-mcp alias add ce-kt-test ./target/release/code-explorer start --project "$KOTLIN_PROJECT"
+mcp alias add ce-kt-test ./target/release/codescout start --project "$KOTLIN_PROJECT"
 
 cleanup() {
     mcp alias remove ce-kt-test 2>/dev/null || true