Add dashboard package and update monorepo docs

New Svelte 5 SPA + Bun backend for session analytics, conversation
replay, task/plan/agent views, and cost tracking. Updates root
CLAUDE.md to reflect four-package monorepo with dashboard-specific
test commands and Dashboard vs CLI guidance.

Author: AnExiledDev

CLAUDE.md

@@ -1,6 +1,6 @@
 # CodeForge Monorepo
 
-This repository contains three packages. Each package manages its own dependencies independently.
+This repository contains four packages. Each package manages its own dependencies independently.
 
 ## Packages
 
@@ -9,6 +9,7 @@ This repository contains three packages. Each package manages its own dependenci
 | `container/` | Node.js | npm |
 | `cli/` | Bun | bun |
 | `docs/` | Node.js | npm |
+| `dashboard/` | Bun | npm (frontend) / bun (server) |
 
 ## Development Rules
 
@@ -26,6 +27,7 @@ Each package has its own `CLAUDE.md` with package-specific development rules:
 - [`container/CLAUDE.md`](container/CLAUDE.md) — changelog, documentation, and configuration rules for the devcontainer package
 - `cli/` — Bun/TypeScript CLI; run `bun test` for tests
 - `docs/` — Astro/Starlight site; run `npm run build` to verify
+- [`dashboard/CLAUDE.md`](dashboard/CLAUDE.md) — Svelte 5 SPA + Bun backend for session analytics
 
 ### Cross-Package Changes
 
@@ -39,3 +41,21 @@ Run tests for each affected package before committing:
 - **Container**: `cd container && npm test`
 - **CLI**: `cd cli && bun test`
 - **Docs**: `cd docs && npm run build`
+- **Dashboard**: `cd dashboard && bun test`
+
+### Dashboard vs CLI
+
+The `dashboard/` and `cli/` packages serve different audiences:
+
+- **CLI** (`codeforge` command) — terminal-first, text/JSON output, scriptable,
+  runs inside or outside the container. Features: session search, task search/list/show,
+  plan search, plugin management, index/config commands.
+- **Dashboard** (Svelte 5 SPA) — visual analytics, charts, expandable detail views,
+  real-time SSE updates. Features: session browsing with conversation replay,
+  task/plan/agent/memory views, project analytics, cost tracking.
+
+When adding a new data view:
+- If it's browsable/visual (tables, charts, detail drill-down) → dashboard
+- If it's scriptable/automatable (piped output, filters, JSON) → CLI
+- If it's both → implement in both, but don't import CLI as a dashboard dependency.
+  Fork patterns instead.