Main with UI

.github/skills/commit-staged/SKILL.md

@@ -0,0 +1,13 @@
+---
+ name: commit-staged
+ description: Commit all staged files with an accurate, informative commit message. Use when asked to commit, make a commit, or save changes.
+ ---
+
+ 1. Run `git diff --cached` to review all staged changes.
+ 2. Analyze the changes to understand what was modified and why.
+ 3. Write a commit message following conventional commit style:
+    - A concise subject line (≤72 chars) summarizing the change
+    - A blank line followed by a body explaining what and why
+    - Include the Co-authored-by trailer
+ 4. Let the user review the commit message and make edits if necessary before finalizing the commit. Never commit without user approval of the message.
+ 4. Commit with `git commit -m "..."`.

.gitignore

@@ -37,3 +37,9 @@ logs/
 
 # Vendored native libraries (downloaded from OCI registry)
 vendor/
+
+# UI build artifacts
+ui/node_modules/
+ui/dist/
+
+.vscode

CLAUDE.md

@@ -15,11 +15,21 @@ This is the Drasi Server repository - a standalone server wrapper around DrasiLi
 - Run server: `cargo run` or `cargo run -- --config config/server.yaml`
 - Run with custom port: `cargo run -- --port 8080`
 - Run with plugin verification: `cargo run -- --verify-plugins --config config/server.yaml`
+- Run with UI disabled: `cargo run -- --disable-ui`
+- Run with UI enabled (override config): `cargo run -- --enable-ui`
+- Validate config (structure only): `cargo run -- validate --config config/server.yaml`
+- Validate config (with plugins): `cargo run -- validate --config config/server.yaml --plugins-dir ./plugins`
 - Check compilation: `cargo check`
 
 ### Plugin Loading
 Plugins (sources, reactions, bootstrap providers) are loaded at runtime as cdylib shared libraries (`.so`/`.dylib`/`.dll`) from a `plugins/` directory next to the binary. Each plugin is self-contained with its own tokio runtime, communicating via a stable C ABI. Plugin building is managed by drasi-core, not this repository.
 
+**Important: `[patch.crates-io]` does NOT affect plugins.** Cargo patches only affect compile-time dependency resolution for the server binary. Plugins are separate shared libraries loaded at runtime — they must be built separately. When developing with local drasi-core changes, always use `make build-local-plugins` to rebuild plugins from local source. Registry-downloaded plugins (`autoInstallPlugins: true`) will NOT be ABI-compatible with local drasi-core changes.
+
+- Build all plugins from local drasi-core (release): `make build-local-plugins`
+- Build all plugins from local drasi-core (debug): `make build-local-plugins-debug`
+- Build test-only plugins (mock, log, scriptfile): `make build-test-plugins`
+
 ### Testing
 - Run all tests: `cargo test`
 - Run unit tests only: `cargo test --lib`
@@ -103,6 +113,7 @@ logLevel: "info"
 persistConfig: true  # Enable persistence (default)
 persistIndex: false  # Use RocksDB for persistent indexing (default: false, uses in-memory)
 verifyPlugins: true  # Enable cosign signature verification for downloaded plugins (default: false)
+enableUi: true       # Enable the web UI at /ui (default: true)
 
 # Optional trusted identities for plugin signature verification
 # trustedIdentities:
@@ -182,6 +193,8 @@ The REST API is exposed under `/api/v1/instances/{instanceId}/...` for multi-ins
 
 ### Configuration Persistence
 
+Persistence uses a snapshot-based approach: when saving, `ConfigPersistence::save()` calls `snapshot_configuration()` on each DrasiLib instance via the ComponentGraph. The ComponentGraph is the single source of truth — there are no shadow caches or separate registration steps. Mutations flow through the ComponentGraph, and the persisted YAML is reconstructed from the current graph state at save time.
+
 DrasiServer separates two independent concepts:
 
 1. **Persistence** - Whether API changes are saved to the config file
@@ -206,7 +219,7 @@ DrasiServer separates two independent concepts:
 - This allows dynamic query creation without persistence (useful for programmatic usage)
 
 **Behavior:**
-- When persistence enabled: all API mutations (create/delete queries) are automatically saved to the config file using atomic writes (temp file + rename) to prevent corruption
+- When persistence enabled: `save()` snapshots component state from the ComponentGraph and writes to YAML using atomic writes (temp file + rename) to prevent corruption
 - When persistence disabled: API mutations work but changes are lost on restart
 - When read-only: all create/delete operations via API are rejected
 
@@ -291,6 +304,8 @@ The server exposes a versioned REST API on port 8080 by default. All API endpoin
 ### Instance Management
 
 - `GET /api/v1/instances` - List all DrasiLib instances
+- `GET /api/v1/instances/{instanceId}/snapshot` - Get configuration snapshot of an instance
+- `POST /api/v1/instances/{instanceId}/clone` - Clone components from another instance
 
 ### Component Management (Instance-Specific)