Remove dashboard feature from devcontainer

Dashboard extracted to separate CodeDirective repository. Remove:
- codeforge-dashboard devcontainer feature
- Dashboard port forwarding and config from devcontainer.json
- Dashboard documentation page and sidebar references
- Dashboard mentions from README, CLAUDE.md, and related docs

Author: claude

CLAUDE.md

@@ -10,11 +10,6 @@ This repository contains three packages. Each package manages its own dependenci
 | `cli/` | Bun | bun |
 | `docs/` | Node.js | npm |
 
-> **Dashboard → CodeDirective**: The `dashboard/` package is deprecated and being
-> extracted to its own repository as **CodeDirective** — an independent app. It is
-> gitignored and will be removed from this repo. Do not add dashboard dependencies
-> or make cross-package changes involving dashboard code.
-
 ## Development Rules
 
 ### Branching Strategy

README.md

@@ -8,7 +8,6 @@ Monorepo for CodeForge — an AI-powered development environment for Claude Code
 |---------|-------------|---------|
 | [`container/`](container/) | CodeForge DevContainer (`@coredirective/cf-container` on npm) | 2.1.0 |
 | [`cli/`](cli/) | CodeForge CLI (`codeforge-cli`) | 0.1.0 |
-| [`dashboard/`](dashboard/) | Session analytics dashboard (Svelte 5 SPA + Bun backend) | — |
 | [`docs/`](docs/) | Documentation site ([codeforge.core-directive.com](https://codeforge.core-directive.com)) | — |
 
 ## Quick Start
@@ -31,9 +30,6 @@ cd container && npm test
 # CLI (Bun)
 cd cli && bun test
 
-# Dashboard (Bun)
-cd dashboard && bun test
-
 # Docs (npm)
 cd docs && npm run build
 ```

container/.devcontainer/devcontainer.json

@@ -73,7 +73,7 @@
 	// then Claude Code native binary (no Node dependency), then custom features.
 	// npm-dependent features (agent-browser, ccusage,
 	// biome, lsp-servers) must come after Node. bun-dependent features
-	// (codeforge-dashboard) must come after Bun. uv-dependent features (ruff, claude-monitor) must
+	// uv-dependent features (ruff, claude-monitor) must
 	// come after uv. notify-hook is second-to-last (lightweight, no dependencies).
 	// dbr (devcontainer-bridge) is last — standalone binary, no dependencies.
 	"overrideFeatureInstallOrder": [
@@ -92,7 +92,6 @@
 		"./features/claude-code-router",
 		// "./features/ccburn",
 		"./features/ccstatusline",
-		"./features/codeforge-dashboard",
 		"./features/ast-grep",
 		"./features/tree-sitter",
 		"./features/lsp-servers",
@@ -157,12 +156,6 @@
 		},
 		// Uncomment to add ccms (requires Rust):
 		// "./features/ccms": {},
-		"./features/codeforge-dashboard": {
-			"version": "latest",
-			"port": "7847",
-			"autostart": true,
-			"username": "automatic"
-		},
 		"./features/ast-grep": {},
 		"./features/tree-sitter": {},
 		"./features/lsp-servers": { "version": "none" },
@@ -192,12 +185,7 @@
 		"ghcr.io/bradleybeddoes/devcontainer-bridge/dbr:0.2.0": {}
 	},
 
-	"forwardPorts": [7847],
 	"portsAttributes": {
-		"7847": {
-			"label": "CodeForge Dashboard",
-			"onAutoForward": "notify"
-		},
 		"*": {
 			"onAutoForward": "notify"
 		}

container/.devcontainer/features/codeforge-dashboard/devcontainer-feature.json

@@ -54,20 +54,6 @@ Language Server Protocol servers provide inline diagnostics, go-to-definition, a
 
 3. Rebuild the container.
 
-## Dashboard
-
-The CodeForge Dashboard is a Svelte 5 SPA for visual session analytics, conversation replay, task/plan/agent views, and cost tracking. It is opt-in.
-
-### Enabling
-
-Uncomment or add the `claude-session-dashboard` feature in `devcontainer.json`, or use the `codeforge-dashboard` feature:
-
-```json
-"./features/codeforge-dashboard": {}
-```
-
-Rebuild the container after enabling. The dashboard runs on a forwarded port — check the container's port list after startup.
-
 ## ccms (Claude Code Memory Search)
 
 A Rust-based session search tool. Replaced in the default build by `codeforge session search`, but still available as an opt-in feature.

container/.devcontainer/features/codeforge-dashboard/install.sh

@@ -50,7 +50,6 @@ These counts are the canonical inventory numbers. Some deeper reference pages in
 |------|--------|-------|
 | `cc`, `claude`, `ccw`, `ccraw`, `cc-orc` | Default | Session launch commands |
 | `check-setup`, `cc-tools`, `ccusage`, `claude-monitor` | Default | Everyday operational tools |
-| `codeforge-dashboard` | Optional | Dashboard feature may need enabling |
 | LSP servers | Disabled by default | Require feature enablement and plugin toggle |
 | `ccms` | Deprecated | Replaced by `codeforge session search` |
 | `ccburn` | Disabled by default | Older burn-rate view, largely superseded by `ccstatusline` |
@@ -60,7 +59,6 @@ These counts are the canonical inventory numbers. Some deeper reference pages in
 
 | Component | Status | Where to configure |
 |-----------|--------|--------------------|
-| Dashboard | Optional | `devcontainer.json` feature config |
 | LSP servers | Disabled by default | `devcontainer.json` + plugin enablement |
 | Rust toolchain | Optional | `devcontainer.json` |
 | Go toolchain | Optional | `devcontainer.json` |

docs/src/content/docs/customize/optional-components.md

@@ -1,11 +1,11 @@
 ---
 title: Accessing Services
-description: How to reach dashboards, previews, and forwarded ports from a CodeForge container across different clients.
+description: How to reach previews and forwarded ports from a CodeForge container across different clients.
 sidebar:
   order: 10
 ---
 
-CodeForge runs inside a Docker container. When a service inside the container listens on a port (e.g., a dev server on port 3000 or the Claude Dashboard on port 7847), you need a forwarding mechanism to access it from your host machine. Which mechanism to use depends on your DevContainer client.
+CodeForge runs inside a Docker container. When a service inside the container listens on a port (e.g., a dev server on port 3000), you need a forwarding mechanism to access it from your host machine. Which mechanism to use depends on your DevContainer client.
 
 :::tip[When to read this page]
 If you use VS Code, you usually only need this page when automatic forwarding is not enough. If you use the DevContainer CLI, JetBrains, or direct SSH, this page matters much earlier.
@@ -24,7 +24,6 @@ If you use VS Code, you usually only need this page when automatic forwarding is
 VS Code automatically detects ports opened inside the container and forwards them to your host. CodeForge configures this in `devcontainer.json`:
 
 - **All ports** are auto-forwarded with a notification prompt
-- **Port 7847** (Claude Dashboard) gets a friendly label in the Ports panel
 
 No setup required — ports appear in the VS Code **Ports** panel as services start. Click the local address to open in your browser.
 
@@ -95,7 +94,7 @@ For one-off port forwarding or environments where `dbr` isn't available, use SSH
 ssh -L 3000:localhost:3000 <container-user>@<container-host>
 
 # Forward multiple ports
-ssh -L 3000:localhost:3000 -L 7847:localhost:7847 <container-user>@<container-host>
+ssh -L 3000:localhost:3000 -L 8080:localhost:8080 <container-user>@<container-host>
 ```
 
 This requires SSH access to the container, which is available when connecting via the `devcontainer` CLI or any Docker SSH setup.
@@ -116,19 +115,14 @@ This requires SSH access to the container, which is available when connecting vi
 Port forwarding behavior is configured in `.devcontainer/devcontainer.json`:
 
 ```jsonc
-"forwardPorts": [7847],
 "portsAttributes": {
-    "7847": {
-        "label": "CodeForge Dashboard",
-        "onAutoForward": "notify"
-    },
     "*": {
         "onAutoForward": "notify"
     }
 }
 ```
 
-- `forwardPorts` — static port list (dashboard port 7847 is pre-configured; VS Code also auto-detects dynamically)
+- `forwardPorts` — static port list for specific services you always want forwarded
 - `portsAttributes` — labels and behavior for auto-detected ports (VS Code / Codespaces only)
 
 These settings are ignored by non-VS Code clients. Use `dbr` or SSH tunneling instead.