@nxuss/lemma 1.32.0 → 1.34.0

package/README.md

@@ -35,6 +35,17 @@ lemma start     # gateway + dashboard on http://localhost:8081
 >
 > **🆕 v1.22.0 — Lemma auto-activates in every LLM client.** `npm i -g @nxuss/lemma` registers the skill in your **user** catalog (auto-loads in every `muse` session, any project) and `lemma init` wires each project for Muse, Claude Code, Cursor, Codex, Windsurf, Kiro and OpenCode. Health check: `lemma doctor`.
 >
+> **🆕 v1.34.0 — Dashboard fixes.** The header shows the real running version (from `/health`), the debugger's pause/resume now works against the proxy, the Vite dev proxy points at the right port, and `npm run build` rebuilds the dashboard so the published UI is never stale.
+>
+> **🆕 v1.33.0 — C# (.NET) support, honestly labeled.** New per-project language detection
+> (`.csproj/.sln`, target frameworks, mixed repos) and a read-only `capability_matrix` tool so clients
+> stop guessing what works outside TypeScript. `get_ast_hologram` and `get_symbol_surgical_context` now
+> serve C# (zero-dependency parser), `depgraph` gives using-based graphs with explicit `unresolved`
+> externals, and `validate_patch_sandbox` runs `dotnet build` on a temp project copy — or says `NOT a
+> build` when there's no SDK. `refactor`, `surgical_ast_insert`, `type_coverage_report`, `entropy_score`
+> and `affected_tests` return `support level: fallback` on C# targets instead of faking it: nothing is
+> modified. No new runtime dependencies. See the [changelog](CHANGELOG.md).
+>
 > **🆕 v1.32.0 — what a command can see and reach.** `run_workspace_command` no longer hands the
 > child the host's whole environment (tokens, API keys, the license key): it gets a short allowlist,
 > extendable via `mcp.commandEnv.allow`. `cat`, `ls`, `grep`, `find`, `sed`… must keep their paths
@@ -209,6 +220,9 @@ lemma start     # gateway + dashboard on http://localhost:8081
   read and workspace search, before anything leaves your machine.
 - **Zero-token static intelligence** — dependency graphs, entropy/coupling/risk scores, and an AST
   symbol index, computed locally with the TypeScript Compiler API. No LLM calls, no tokens.
+  C# projects get the same treatment where it's real: symbol holograms and surgical context via a
+  zero-dependency parser, using-based dependency graphs, and `dotnet build` patch validation —
+  everything else reports `fallback` instead of pretending (see `capability_matrix`).
 - **Command output distillation** — a failing `npm test`/`tsc` run is parsed by deterministic
   per-format rules (jest, tsc, eslint) down to the failures that matter; the full output is never
   lost, just stored and retrievable on demand.
@@ -216,7 +230,7 @@ lemma start     # gateway + dashboard on http://localhost:8081
   compiler-verified AST location instead of asking the model to output a full-file rewrite.
 - **Infrastructure Command Center** — 22 free tools for Jenkins, OKD/OpenShift, and Terraform:
   discover, connect, deploy, diagnose, and detect drift, all via MCP.
-- **Scoped tool surface** — of the 110 registered tools, only the ones your project shows evidence
+- **Scoped tool surface** — of the 111 registered tools, only the ones your project shows evidence
   of needing are advertised to the model each turn; the rest stay one `lemma_toolbox` call away.
 
 See [`CHANGELOG.md`](CHANGELOG.md) for the full, per-version history.
@@ -225,7 +239,7 @@ See [`CHANGELOG.md`](CHANGELOG.md) for the full, per-version history.
 
 ## 💎 Free vs Pro
 
-60 of the 110 registered tools work with no license; 50 require Pro. Enforced by one allowlist in
+61 of the 111 registered tools work with no license; 50 require Pro. Enforced by one allowlist in
 code (`FREE_TOOLS` in `src/mcp/tools.ts`, including all 22 infrastructure tools), not by narrative.
 A session without a license doesn't even advertise the Pro tools — they stay registered and
 discoverable via `lemma_toolbox`.

package/dashboard/README.md

@@ -1,351 +1,47 @@
 # Lemma Dashboard
 
-Real-time visualization and monitoring dashboard for the Lemma agent orchestration hub.
+Live view of a running Lemma proxy: token savings, cache behaviour, connected agents, MCP
+activity and the Brain's knowledge base.
 
-## Features
+The proxy serves the production build itself at `http://localhost:8081/dashboard/`
+(`lemma start`). The version shown in the header comes from the proxy's `/health`.
 
-### 1. Agent Graph
-- Live visualization of connected agents
-- Node graph showing agent relationships
-- Real-time status updates (active, idle, busy)
-- Agent capabilities display
-- Connection lines to central hub
+## Panels
 
-### 2. Token Economics
-- Real-time cost savings tracking
-- Token usage metrics
-- Cache hit rate visualization
-- Performance charts:
-  - Cache performance over time
-  - Latency trends
-  - Cumulative cost savings
-- ROI calculator with projections
+- **Metrics bar / charts** — requests, hit rate, latency, tokens and cost saved
+  (`/api/metrics`, `/api/cache-stats`, `/api/savings-breakdown`).
+- **The Hub** — connected agents (`/api/agents`), charts, savings breakdown, Brain knowledge
+  stats (`/api/brain/stats`), cache stats and the event timeline (`/api/events`).
+- **The Tools** — live feed of MCP tool calls; the header badge shows MCP status
+  (`/api/mcp-status`) and toggles it (`/api/mcp/toggle`).
+- **The Brain** — semantic search over the cache (`/api/search`).
+- **Debugger** (bottom panel) — pause/resume. While paused the proxy refuses new completions
+  with `503` + `Retry-After` (`/api/debugger/pause|resume|state`).
+- **Flush Cache** — `/api/cache/clear`.
 
-### 3. Time-Travel Debugger
-- Event timeline with all agent interactions
-- State inspector for any point in time
-- Playback controls (pause, step back/forward)
-- State editing capabilities
-- Event filtering by type
+`TimeTravel.tsx` and the rewind call (`/api/debugger/rewind`) exist in the code but are not
+wired into the proxy: rewind is only implemented by the standalone API server
+(`src/api/dashboardRoutes.ts`).
 
-## Quick Start
-
-### Installation
+## Develop
 
 ```bash
-cd dashboard
 npm install
+npm run dev        # Vite on http://localhost:8082/dashboard/
 ```
 
-### Development
-
-```bash
-npm run dev
-```
-
-Dashboard will be available at `http://localhost:3000`
+The dev server talks to the proxy on `http://localhost:8081` (start it with `lemma start`).
+Override with `VITE_API_URL` / `VITE_WS_URL` in `.env`.
 
-### Production Build
+## Build
 
 ```bash
-npm run build
-npm run preview
-```
-
-## Configuration
-
-Create a `.env` file:
-
-```env
-VITE_ROUTER_URL=ws://localhost:8080
-VITE_API_URL=http://localhost:8080
-```
-
-## Architecture
-
-### Tech Stack
-
-- **React 18**: UI framework
-- **TypeScript**: Type safety
-- **Vite**: Build tool and dev server
-- **TailwindCSS**: Styling
-- **Recharts**: Data visualization
-- **Zustand**: State management
-- **WebSocket**: Real-time communication
-
-### Project Structure
-
-```
-dashboard/
-├── src/
-│   ├── components/
-│   │   ├── AgentGraph.tsx      # Agent visualization
-│   │   ├── MetricsPanel.tsx    # Token economics
-│   │   ├── TimeTravel.tsx      # State debugger
-│   │   ├── ConnectionStatus.tsx # WebSocket status
-│   │   └── Layout.tsx          # App layout
-│   ├── hooks/
-│   │   └── useWebSocket.ts     # WebSocket connection
-│   ├── App.tsx                 # Main app component
-│   ├── main.tsx               # Entry point
-│   └── index.css              # Global styles
-├── index.html
-├── package.json
-├── tsconfig.json
-├── vite.config.ts
-└── tailwind.config.js
-```
-
-## WebSocket Protocol
-
-The dashboard connects to the Lemma router via WebSocket and exchanges IAP (Inter-Agent Protocol) messages.
-
-### Connection
-
-```typescript
-const ws = new WebSocket('ws://localhost:8080');
-
-// Send handshake
-ws.send(JSON.stringify({
-  type: 'HANDSHAKE',
-  messageId: crypto.randomUUID(),
-  timestamp: Date.now(),
-  payload: {
-    agentId: 'dashboard-client',
-    agentName: 'Dashboard',
-    version: '1.0.0',
-    capabilities: [{ name: 'monitoring', version: '1.0.0' }],
-  },
-}));
+npm run build      # tsc + vite build -> dist/
 ```
 
-### Message Types
-
-#### Metrics Update
-```json
-{
-  "type": "METRICS_UPDATE",
-  "payload": {
-    "totalRequests": 1000,
-    "cacheHits": 800,
-    "cacheMisses": 200,
-    "averageLatency": 45.2,
-    "tokensSaved": 150000,
-    "costSaved": 0.3,
-    "hitRate": "80.0%"
-  }
-}
-```
-
-#### Agent Connected
-```json
-{
-  "type": "AGENT_CONNECTED",
-  "payload": {
-    "id": "agent-123",
-    "name": "Research Agent",
-    "capabilities": ["research", "analysis"],
-    "status": "idle",
-    "connectedAt": 1234567890
-  }
-}
-```
-
-#### State Event
-```json
-{
-  "type": "STATE_EVENT",
-  "payload": {
-    "id": "event-uuid",
-    "timestamp": 1234567890,
-    "type": "TASK_REQUEST",
-    "agentId": "agent-123",
-    "data": {},
-    "snapshot": {}
-  }
-}
-```
-
-## Components
-
-### AgentGraph
-
-Visualizes the agent swarm as a node graph.
-
-**Props:**
-- `agents: Agent[]` - Array of connected agents
-
-**Features:**
-- Circular layout around central hub
-- Color-coded status indicators
-- Capability badges
-- Connection lines with animation
-
-### MetricsPanel
-
-Displays token economics and performance metrics.
-
-**Props:**
-- `metrics: Metrics` - Current metrics object
-
-**Features:**
-- 6 key metric cards
-- 3 interactive charts
-- ROI calculator
-- Historical data tracking
-
-### TimeTravel
-
-State debugger with time-travel capabilities.
-
-**Props:**
-- `events: StateEvent[]` - Array of captured events
-
-**Features:**
-- Event timeline
-- State inspector
-- Playback controls
-- State editing
-
-### ConnectionStatus
-
-Shows WebSocket connection status.
-
-**Props:**
-- `isConnected: boolean` - Connection state
-
-## Customization
-
-### Theme
-
-Edit `tailwind.config.js` to customize colors:
-
-```javascript
-theme: {
-  extend: {
-    colors: {
-      primary: { /* your colors */ },
-      success: { /* your colors */ },
-      // ...
-    },
-  },
-}
-```
-
-### Metrics
-
-Add custom metrics in `useWebSocket.ts`:
-
-```typescript
-export interface Metrics {
-  // ... existing metrics
-  customMetric: number;
-}
-```
-
-### Charts
-
-Add new charts in `MetricsPanel.tsx` using Recharts:
-
-```typescript
-<LineChart data={historicalData}>
-  <Line dataKey="customMetric" stroke="#color" />
-</LineChart>
-```
-
-## Performance
-
-### Optimizations
-
-- **Lazy Loading**: Components loaded on-demand
-- **Memoization**: React.memo for expensive components
-- **Virtual Scrolling**: For large event lists
-- **Data Limiting**: Keep only recent data points
-
-### Metrics
-
-- **Bundle Size**: ~200KB gzipped
-- **Initial Load**: <1s on fast connection
-- **Memory Usage**: ~50MB typical
-- **CPU Usage**: <5% idle, <15% active
-
-## Deployment
-
-### Static Hosting
-
-Build and deploy to any static host:
-
-```bash
-npm run build
-# Upload dist/ folder to:
-# - Vercel
-# - Netlify
-# - AWS S3 + CloudFront
-# - GitHub Pages
-```
-
-### Docker
-
-```dockerfile
-FROM node:20-alpine AS builder
-WORKDIR /app
-COPY package*.json ./
-RUN npm ci
-COPY . .
-RUN npm run build
-
-FROM nginx:alpine
-COPY --from=builder /app/dist /usr/share/nginx/html
-EXPOSE 80
-CMD ["nginx", "-g", "daemon off;"]
-```
-
-### Environment Variables
-
-Set in deployment platform:
-
-- `VITE_ROUTER_URL`: WebSocket URL of Lemma router
-- `VITE_API_URL`: HTTP API URL (if different)
-
-## Troubleshooting
-
-### WebSocket Connection Failed
-
-1. Check router is running
-2. Verify URL in `.env`
-3. Check CORS settings
-4. Verify firewall rules
-
-### Metrics Not Updating
-
-1. Check WebSocket connection status
-2. Verify router is broadcasting metrics
-3. Check browser console for errors
-4. Verify message format
-
-### Charts Not Rendering
-
-1. Check data format matches Recharts requirements
-2. Verify ResponsiveContainer has height
-3. Check for console errors
-4. Verify data is not empty
-
-## Development
-
-### Adding a New Tab
-
-1. Create component in `src/components/`
-2. Add tab button in `App.tsx`
-3. Add route in tab navigation
-4. Update state management
-
-### Adding a New Metric
-
-1. Update `Metrics` interface in `useWebSocket.ts`
-2. Add metric card in `MetricsPanel.tsx`
-3. Update backend to send metric
-4. Add to historical data tracking
+From the repo root, `npm run build` also builds the dashboard. `dashboard/dist` is
+git-ignored but published to npm, so rebuild before releasing.
 
-## License
+## Stack
 
-MIT
+React 18, TypeScript, Vite, Tailwind, Zustand, Recharts, Socket.IO client.