chore: remove unused desktop app, cloud deployment infra, and monitoring stack

Deletes desktop/ (Electron wrapper), deployments/ (Helm/Kustomize/
Terraform/CI for cloud deploy), and monitoring/ (Prometheus + Grafana
stack) along with DESKTOP.md, DEPLOYMENT.md, docker-compose.full.yml,
their npm scripts, and every dangling reference across README,
ARCHITECTURE, INSTALL, SETUP, docs/, and the repeated per-file
MODULE_GUIDE "Observability" boilerplate comment. The GET /api/metrics
endpoint itself is untouched — it's the dashboard's own route, not
part of the removed monitoring stack.

mcp/build/.srchash

@@ -1 +1 @@
-2e9282b25c6d10d236ad0fd91bceeebf9a5c08cdbea74f1c780c1bae5303ca81
+4a478bdd2063e99f6bc7cf62ec091b03757fd54fd99fba4b662d02b1f51543bc

mcp/build/clients/dashboard-api-client.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `../config/app-config.js`
  * - `../core/logger.js`

mcp/build/config/app-config.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Public surface
  * - `LogLevel` — exported API; see TSDoc on the symbol for behavior.
  * - `TransportMode` — exported API; see TSDoc on the symbol for behavior.

mcp/build/core/logger.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `../config/app-config.js`
  *

mcp/build/core/tool-registry.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `./logger.js`
  * - `./tool-result.js`

mcp/build/core/tool-result.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `../clients/dashboard-api-client.js`
  *

mcp/build/index.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `./clients/dashboard-api-client.js`
  * - `./config/app-config.js`

mcp/build/policy/tool-guards.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `../config/app-config.js`
  *

mcp/build/server.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `./config/app-config.js`
  * - `./clients/dashboard-api-client.js`

mcp/build/tools/domains/agent-tools.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `../../core/tool-registry.js`
  * - `../../policy/tool-guards.js`

mcp/build/tools/domains/event-tools.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `../../core/tool-registry.js`
  * - `../../policy/tool-guards.js`

mcp/build/tools/domains/maintenance-tools.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `../../core/tool-registry.js`
  * - `../../policy/tool-guards.js`

mcp/build/tools/domains/observability-tools.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `../../types/tool-context.js`
  * - `../../core/tool-registry.js`

mcp/build/tools/domains/pricing-tools.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `../../core/tool-registry.js`
  * - `../../policy/tool-guards.js`

mcp/build/tools/domains/session-tools.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `../../core/tool-registry.js`
  * - `../../policy/tool-guards.js`

mcp/build/tools/index.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `../types/tool-context.js`
  * - `./domains/observability-tools.js`

mcp/build/tools/schemas.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Public surface
  * - `SessionStatusSchema` — exported API; see TSDoc on the symbol for behavior.
  * - `AgentStatusSchema` — exported API; see TSDoc on the symbol for behavior.

mcp/build/transports/http-server.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `../config/app-config.js`
  * - `../core/logger.js`

mcp/build/transports/repl.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `../config/app-config.js`
  * - `../clients/dashboard-api-client.js`

mcp/build/transports/tool-collector.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `../config/app-config.js`
  * - `../clients/dashboard-api-client.js`

mcp/build/types/tool-context.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Internal dependencies
  * - `../config/app-config.js`
  * - `../clients/dashboard-api-client.js`

mcp/build/ui/banner.js

@@ -23,11 +23,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Public surface
  * - `printBanner` — exported API; see TSDoc on the symbol for behavior.
  * - `printServerInfo` — exported API; see TSDoc on the symbol for behavior.

mcp/build/ui/colors.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Public surface
  * - `bold` — exported API; see TSDoc on the symbol for behavior.
  * - `dim` — exported API; see TSDoc on the symbol for behavior.

mcp/build/ui/formatter.js

@@ -20,11 +20,6 @@
  * how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
  * scoped GET via `?sources=`. Health checks and import history surface in Settings.
  *
- * ## Observability
- * Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
- * provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
- * Docker Compose profiles are documented in `monitoring/README.md`.
- *
  * ## Public surface
  * - `box` — exported API; see TSDoc on the symbol for behavior.
  * - `divider` — exported API; see TSDoc on the symbol for behavior.