repo: expose storage health and trim stale docs

Author: argahsuknesib

.github/copilot-instructions.md

@@ -186,7 +186,6 @@ Minimal dependency philosophy:
 - `src/storage/indexing/dictionary.rs` (172 lines) - Dictionary encoding
 - `tests/dictionary_encoding_test.rs` (624 lines) - Comprehensive integration tests
 - `BENCHMARK_RESULTS.md` - Performance metrics and analysis
-- `ARCHITECTURE.md` - High-level design (note: mentions TypeScript, but actual impl is Rust)
 - `Makefile` - Common development commands
 
 # Copilot Instructions

GETTING_STARTED.md

@@ -77,7 +77,7 @@ make ci-check
 - `src/bin`: executable binaries
 - `examples`: runnable examples and a minimal static demo
 - `tests`: integration coverage
-- `docs`: current docs plus older design notes
+- `docs`: current product docs plus a small amount of retained background material
 
 ## Where to Read Next
 

README.md

@@ -70,8 +70,6 @@ The maintained dashboard lives in a separate repository:
 
 - `https://github.com/SolidLabResearch/janus-dashboard`
 
-The `janus-dashboard/` folder in this repository is a lightweight local demo client, not the primary frontend.
-
 ## Performance
 
 Janus uses dictionary encoding and segmented storage for high-throughput ingestion and historical reads.
@@ -129,9 +127,10 @@ This example demonstrates:
 The maintained web dashboard lives in the separate
 `SolidLabResearch/janus-dashboard` repository.
 
-This repository keeps a small static demo at
+Frontend development should happen in the dedicated dashboard repo. This
+repository only keeps a small static demo at
 [`examples/demo_dashboard.html`](./examples/demo_dashboard.html) for manual API
-testing, but frontend development should happen in the dedicated dashboard repo.
+testing.
 
 ## Development
 
@@ -169,7 +168,8 @@ Start here:
 
 ## Notes
 
-- `src/main.rs` is currently a benchmark-style executable, not the main user-facing interface.
+- `src/main.rs` is now a lightweight entry binary that points to the main Janus
+  executables and benchmark helpers.
 - The primary user-facing entry point is `http_server`.
 
 ## Licence

START_HERE.md

@@ -18,7 +18,7 @@ cargo run --example http_client_example
 
 - `http_server` is the main backend entry point
 - `stream_bus_cli` is the ingestion and replay CLI
-- `examples/demo_dashboard.html` is a minimal manual demo
+- `examples/demo_dashboard.html` is an optional minimal manual demo
 - the maintained Svelte dashboard lives in the separate `janus-dashboard` repository
 
 ## Current Docs

docs/ARCHITECTURE.md

@@ -58,17 +58,6 @@ This is the shortest path to understanding the current Janus implementation.
 - [README_HTTP_API.md](./README_HTTP_API.md)
 - [QUICKSTART_HTTP_API.md](./QUICKSTART_HTTP_API.md)
 
-## Legacy Material
-
-The following files remain useful as background, but they are not the main entrypoint for the current code:
-
-- [ARCHITECTURE.md](./ARCHITECTURE.md)
-- [EXECUTION_ARCHITECTURE.md](./EXECUTION_ARCHITECTURE.md)
-- [MVP_ARCHITECTURE.md](./MVP_ARCHITECTURE.md)
-- [MVP_TODO.md](./MVP_TODO.md)
-- [RSP_INTEGRATION_COMPLETE.md](./RSP_INTEGRATION_COMPLETE.md)
-- [SPARQL_BINDINGS_UPGRADE.md](./SPARQL_BINDINGS_UPGRADE.md)
-
 ## Dashboard Boundary
 
 - Local demo dashboard in this repository: `examples/demo_dashboard.html`