docs: Phase 6 — README for the skeleton; drop unused Database model

README documents run instructions (workspace + local NodeDB path dep),
project structure, and the ConnectionService backend seam. Removed the
unused Database model (no-dead-code); per-database collection models plug
in via models/ + ConnectionService when needed. Build is warning-clean
(only a transitive future-incompat from a Dioxus macOS dep).

added specs

Author: laksamanakeris

.gitignore

@@ -105,4 +105,5 @@ dmypy.json
 
 # Local reference only — not tracked
 docs/nodedb_lab_studio_mockup_v4.html
+specs/*
 .DS_Store

README.md

@@ -1,47 +1,94 @@
 # NodeDB Studio
 
-**GUI client for [NodeDB](https://github.com/NodeDB-Lab/nodedb).** Query editor, data browser, and administration -- built with Dioxus for desktop and web.
+**Desktop GUI client for [NodeDB](https://github.com/NodeDB-Lab/nodedb)** — a single-engine,
+multi-modal database. Built with Dioxus + Rust. Studio is the visual surface for one NodeDB
+instance, which exposes eight internal **storage modes** (Document, Strict, Vector, Graph,
+Timeseries, KV, Spatial, FTS) — not separate engines. Studio renders a purpose-built UI per mode
+within one connection.
 
-## Features (Planned)
+## Status: UI skeleton
 
-- **Query editor** -- SQL editor with syntax highlighting, auto-complete, and query history
-- **Data browser** -- Browse, filter, and edit documents, vectors, graph nodes, timeseries, and KV pairs
-- **Graph explorer** -- Interactive visualization of graph relationships and traversal results
-- **Vector space viewer** -- 2D/3D projection of vector collections with cluster visualization
-- **Collection management** -- Create, alter, drop, and inspect collections across all engines
-- **Real-time monitor** -- Live metrics, active queries, CDC streams, and resource usage
-- **Sync dashboard** -- CRDT sync status, pending deltas, conflict resolution, device overview
-- **Multi-connection** -- Connect to multiple NodeDB instances and switch between them
+This repository is currently a **production-quality UI skeleton**: real Dioxus components,
+routing, signal/context state, a faithful CSS port of the design, typed models, and hardcoded
+mock data wired into the full interactive flow. There is **no network/database I/O yet** — every
+backend touchpoint is a typed stub behind the `ConnectionService` seam (see below).
 
-## Install
+Implemented:
 
-```bash
-cargo install nodedb-studio
-```
+- Connection Manager → studio shell two-state flow
+- Capability-driven rail and Admin sub-tabs (hide per the active connection's `Capabilities`)
+- Engine-aware Explorer (collection click swaps the per-storage-mode viewer)
+- Connection / database / notification / avatar popovers; per-connection identity
+- Command palette (⌘K), Preferences (⌘,), Disconnect (⌘D), Esc — pure Rust, no JS interop
+- Streams lateral nav, Admin sub-tabs with cluster gating, and all Phase-6 standalone views
+- New-connection and Preferences modals
+- Light/dark theme follows the OS
+
+Heavy widgets (graph/chart/map renderers, code editor) are intentionally static SVG / `<pre>` /
+`<textarea>` placeholders — the production library for each is a `// TODO` decision, not made here.
 
-Pre-built binaries for Linux, macOS, and Windows will be available on the [releases page](https://github.com/NodeDB-Lab/nodedb-studio/releases).
+## Building & running
 
-## Building from Source
+This is a Cargo workspace; the app is the `nodedb-studio` member crate.
 
 ```bash
-git clone https://github.com/NodeDB-Lab/nodedb-studio.git
-cd nodedb-studio
-cargo build --release
+cargo run -p nodedb-studio      # opens the desktop window (1440x900)
+cargo build --release           # binary at target/release/nodedb-studio
 ```
 
-The binary is at `target/release/nodedb-studio`.
+### Local NodeDB dependency
 
-For local development against the NodeDB workspace, create `.cargo/config.toml`:
+The crate depends on `nodedb-client` / `nodedb-types`. The published `0.0.0` crates are broken
+placeholders, so the workspace points these at a **local NodeDB checkout** via path deps in the
+root `Cargo.toml`:
 
 ```toml
-[patch.crates-io]
 nodedb-client = { path = "../nodedb/nodedb-client" }
-nodedb-types = { path = "../nodedb/nodedb-types" }
+nodedb-types  = { path = "../nodedb/nodedb-types" }
+```
+
+Adjust those paths if your NodeDB checkout lives elsewhere. (The skeleton does not yet import these
+crates — they compile as dependencies only.)
+
+## Project structure
+
+```
+nodedb-studio/                  workspace root
+└── nodedb-studio/              the app crate
+    ├── assets/styles.css       CSS ported verbatim from the design (tokens + classes)
+    └── src/
+        ├── main.rs             desktop launch + window config
+        ├── app.rs              root: context providers + two-state machine
+        ├── routes.rs           studio Route enum + StudioLayout (chrome + Outlet)
+        ├── state/              live UI state (signals): connection, registry,
+        │                       notifications, preferences, ui (popover/modal kinds)
+        ├── models/             typed data: StorageMode + Collection, Notification
+        ├── data/mock.rs        ALL hardcoded mock data, in one place
+        ├── services/           ConnectionService trait + MockConnectionService
+        ├── components/         shell chrome: rail, topbar, statusbar, command_palette,
+        │                       modal, snav, subnav, popovers/
+        ├── modals/             new_connection + preferences bodies + ModalHost
+        └── views/              one screen per rail destination
+            ├── connection_manager.rs, studio_shell.rs
+            ├── explorer/       sidebar + viewers/ (one per storage mode)
+            ├── streams/        landing + cdc/mv/topics/notify/cron
+            ├── admin/          cluster/shards/nodes/raft/rbac/rls/audit
+            └── query, designer, graph_explorer/, vector_space, sync,
+                console, timeseries_dashboard, spatial_view, fts_inspector
 ```
 
-## Status
+## Where the backend plugs in
+
+Everything the UI needs from the outside world goes through one trait:
+
+`src/services/connection_service.rs` — `ConnectionService` (`list_connections`, `notifications`,
+`connect`). Today the only implementor is `MockConnectionService`, reading `src/data/mock.rs`. It
+is provided as `Rc<dyn ConnectionService>` via context in `app.rs`, so a real NodeDB-client-backed
+implementor is a one-line swap. **Async** (`use_resource`) is introduced at this boundary when the
+real client lands — not sprinkled through the views.
 
-Early development. Not yet usable.
+When richer per-database data is needed (e.g. an Explorer that lists a database's collections), add
+the model under `src/models/` and surface it through `ConnectionService`.
 
 ## License
 

nodedb-studio/src/models/database.rs

@@ -2,5 +2,4 @@
 //! databases, notifications); live UI state lives in `crate::state`.
 
 pub mod collection;
-pub mod database;
 pub mod notification;