refactor: unify host runtime and remove adapters

Author: FloSch62

PUBLISHING.md

@@ -9,7 +9,7 @@
 
 The `publish-package.yml` workflow publishes `@srl-labs/clab-ui` to GitHub Packages.
 
-No wrapper packages are published separately; consume core/explorer/inspect APIs from
+No wrapper packages are published separately; consume browser runtime, core, explorer, and inspect APIs from
 `@srl-labs/clab-ui` subpath exports.
 
 ## Local publish (manual)
@@ -36,5 +36,4 @@ node scripts/set-clab-package-source.mjs --source=github --version=<version>
 npm install
 ```
 
-Host adapters (`@srl-labs/clab-adapter-vscode`, `@srl-labs/clab-adapter-api`,
-`@srl-labs/clab-adapter-memory`) are workspace packages used for integration and testing.
+Browser-side runtime integration is owned by `@srl-labs/clab-ui/host`.

README.md

@@ -12,7 +12,7 @@ Primary consumer today: [`vscode-containerlab`](https://github.com/srl-labs/vsco
 
 - React UI and topology editing logic used by containerlab webviews
 - Shared parsing/core utilities used by the extension host
-- A local browser dev harness (`npm run dev`) for fast UI iteration
+- A standalone-backed local development flow (`npm run dev`) that exercises the real browser/runtime integration
 - Build tooling that produces webview-ready assets in `dist/`
 
 ---
@@ -32,12 +32,8 @@ Primary consumer today: [`vscode-containerlab`](https://github.com/srl-labs/vsco
 
 | Component | Package | Status | Notes |
 | --- | --- | --- | --- |
-| Main UI package | `@srl-labs/clab-ui` | Published | Published to GitHub Packages |
-| Host contract | `@srl-labs/clab-host-contract` | Workspace-only | `private: true` |
-| API adapter | `@srl-labs/clab-adapter-api` | Workspace-only | `private: true` |
-| VS Code adapter | `@srl-labs/clab-adapter-vscode` | Workspace-only | `private: true` |
-| Memory adapter | `@srl-labs/clab-adapter-memory` | Workspace-only | Used by local dev harness |
-| Standalone app | N/A | Planned | Dev harness exists; production standalone distribution is not complete yet |
+| Main UI package | `@srl-labs/clab-ui` | Published | Owns the shared browser-side host contract and constructors |
+| Standalone app | `@srl-labs/clab-standalone` | Workspace app | Local dev/runtime host backed by the API proxy server |
 
 ---
 
@@ -63,28 +59,27 @@ npx playwright install chromium
 
 ## Getting Started
 
-Start the dev harness:
+Start the standalone-backed dev flow:
 
 ```bash
 npm run dev
 ```
 
 Then open `http://localhost:5173`.
 
-Dev harness runtime model:
+Local dev runtime model:
 
-- Pure frontend runtime (no Node middleware backend in this repo)
-- In-memory topology host using shared `TopologyHostCore`
-- File/session persistence in browser `localStorage`
-- Reset action restores seeded topologies from `dev/topologies-original/`
+- Browser frontend served by the standalone Vite app
+- Fastify backend proxy for auth, topology snapshot/command, files, and lifecycle actions
+- Shared `ClabUiHost` runtime used by both standalone and VS Code webviews
 
 ---
 
 ## Common Commands
 
 | Command | Description |
 | --- | --- |
-| `npm run dev` | Run Vite dev harness from `dev/` |
+| `npm run dev` | Run the standalone-backed local development flow |
 | `npm run build` | Build production webview assets into `dist/` |
 | `npm run build:watch` | Build in dev mode (inline sourcemaps, no minify) |
 | `npm run build:dev` | Build in dev mode (same output profile as `build:watch`) |
@@ -143,8 +138,8 @@ Frequently used exports:
 
 Notes:
 
-- The workspace also ships host adapter packages, but they are not published externally yet.
-- Current UI host context APIs are imported from service subpaths (for example `@srl-labs/clab-ui/services/topologyHostClient`).
+- Browser runtime integration is exposed from `@srl-labs/clab-ui/host`.
+- Current UI host context APIs are still imported from service subpaths (for example `@srl-labs/clab-ui/services/topologyHostClient`).
 
 ---
 
@@ -153,28 +148,18 @@ Notes:
 The UI currently uses host messaging via `services/topologyHostClient`:
 
 ```ts
-import { App } from "@srl-labs/clab-ui";
-import { setHostContext } from "@srl-labs/clab-ui/services/topologyHostClient";
-import { refreshTopologySnapshot } from "@srl-labs/clab-ui/services/topologyHostCommands";
+import { createWindowClabUiHost, setClabUiHost } from "@srl-labs/clab-ui/host";
 
-setHostContext({
-  path: "labs/my-lab.clab.yml",
-  mode: "edit",
-  deploymentState: "undeployed"
-});
-
-await refreshTopologySnapshot();
+setClabUiHost(createWindowClabUiHost());
 ```
 
-The adapter packages in `packages/adapter-*` are part of the transport direction but are currently workspace-only.
-
 ---
 
 ## Troubleshooting
 
 - `npm install` fails with engine mismatch: ensure Node `>= 24` (`node -v`).
 - Playwright tests fail before opening a browser: run `npx playwright install chromium`.
-- Dev harness state feels stale: clear browser localStorage keys `containerlab-gui.dev.in-memory-labs.v1` and `containerlab-gui.dev.session.v1`.
+- Local dev flow cannot reach the backend: ensure the standalone dev server on `http://localhost:3000` is starting successfully.
 
 ---
 
@@ -193,8 +178,8 @@ Detailed steps: [`PUBLISHING.md`](PUBLISHING.md)
 
 ---
 
-## Standalone Roadmap Note
+## Standalone Runtime
 
-The standalone browser experience exists today as a dev harness (`npm run dev`) and is useful for UI iteration and testing.
+The standalone browser experience is the supported local development runtime for `containerlab-gui`.
 
-A fully supported standalone distribution is planned but not complete yet. Until that lands, the production integration target remains `vscode-containerlab`.
+It uses the same browser-side host contract as VS Code, with only platform-specific differences in backend transport and shell behavior.

apps/standalone/server/index.ts

@@ -20,7 +20,7 @@ import { registerTopologyEventsProxy } from "./topologyEventsProxy.js";
 
 const PORT = parseInt(process.env.PORT ?? "3000", 10);
 const DEFAULT_CLAB_API_URL = process.env.CLAB_API_URL ?? "http://localhost:8080";
-const VITE_DEV_URL = process.env.VITE_DEV_URL ?? "http://localhost:5174";
+const VITE_DEV_URL = process.env.VITE_DEV_URL ?? "http://localhost:5173";
 const IS_DEV = process.env.NODE_ENV !== "production";
 
 async function start(): Promise<void> {

apps/standalone/server/topologyProxy.ts

@@ -1,9 +1,8 @@
 /**
  * Topology host protocol endpoints.
  *
- * Exposes /api/topology/snapshot and /api/topology/command — the same
- * endpoints the dev harness uses, so the UI's topologyHostClient.ts
- * works without changes.
+ * Exposes /api/topology/snapshot and /api/topology/command so the shared
+ * UI topologyHostClient.ts works unchanged across standalone and VS Code hosts.
  *
  * Each lab gets a TopologyHostCore backed by ClabApiFileSystemAdapter.
  */