ops: add status endpoint and docs link checks

Author: argahsuknesib

.github/workflows/docs-links.yml

@@ -0,0 +1,20 @@
+name: Docs Link Check
+
+on:
+  pull_request:
+    branches: [main, develop]
+    paths:
+      - "**/*.md"
+      - ".github/workflows/docs-links.yml"
+      - "scripts/check_doc_links.sh"
+
+jobs:
+  docs-links:
+    name: Validate Markdown Links
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Check local markdown links
+        run: bash scripts/check_doc_links.sh

GETTING_STARTED.md

@@ -40,10 +40,7 @@ cargo run --example http_client_example
 That example covers query registration, start, stop, replay control, and
 WebSocket result consumption.
 
-## Optional Local Demo UI
-
-This repository keeps a small static demo at
-`examples/demo_dashboard.html` for manual browser testing.
+## Optional Frontend
 
 The maintained Svelte dashboard lives in the separate
 `SolidLabResearch/janus-dashboard` repository.
@@ -75,7 +72,7 @@ make ci-check
 - `src/stream`: live stream processing
 - `src/storage`: segmented RDF storage
 - `src/bin`: executable binaries
-- `examples`: runnable examples and a minimal static demo
+- `examples`: runnable examples, including the HTTP client example
 - `tests`: integration coverage
 - `docs`: current product docs plus a small amount of retained background material
 

Makefile

@@ -1,4 +1,4 @@
-.PHONY: help build test clean fmt lint check ci-check install run dev doc bench audit deps update watch all release
+.PHONY: help build test clean fmt lint check ci-check install run dev doc bench audit deps update watch all release doc-links
 
 # Default target
 .DEFAULT_GOAL := help
@@ -59,6 +59,10 @@ lint: ## Run clippy lints
 check: fmt-check lint ## Run all checks (formatting and linting)
 	@echo "$(GREEN)All checks passed!$(NC)"
 
+doc-links: ## Check local markdown links
+	@echo "$(BLUE)Checking markdown links...$(NC)"
+	@bash ./scripts/check_doc_links.sh
+
 ci-check: ## Run full CI/CD checks locally before pushing
 	@echo "$(BLUE)Running CI/CD checks...$(NC)"
 	@./scripts/ci-check.sh

README.md

@@ -127,10 +127,7 @@ This example demonstrates:
 The maintained web dashboard lives in the separate
 `SolidLabResearch/janus-dashboard` repository.
 
-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.
+Frontend development should happen in the dedicated dashboard repo.
 
 ## Development
 
@@ -154,7 +151,6 @@ The repository includes runnable examples under [`examples/`](./examples), inclu
 
 - [`examples/http_client_example.rs`](./examples/http_client_example.rs)
 - [`examples/comparator_demo.rs`](./examples/comparator_demo.rs)
-- [`examples/demo_dashboard.html`](./examples/demo_dashboard.html) for a minimal local demo
 
 ## Documentation
 

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 an optional minimal manual demo
+- `examples/http_client_example.rs` is the fastest local API exercise
 - the maintained Svelte dashboard lives in the separate `janus-dashboard` repository
 
 ## Current Docs

docs/DOCUMENTATION_INDEX.md

@@ -60,7 +60,6 @@ This is the shortest path to understanding the current Janus implementation.
 
 ## Dashboard Boundary
 
-- Local demo dashboard in this repository: `examples/demo_dashboard.html`
 - Maintained dashboard repository: `https://github.com/SolidLabResearch/janus-dashboard`
 
 ## Related Code

docs/HTTP_API.md

@@ -857,7 +857,7 @@ Options:
 ## Additional Resources
 
 - [JanusQL Query Language Documentation](./JANUSQL.md)
-- [Stream Bus CLI Documentation](./STREAM_BUS.md)
+- [Stream Bus CLI Documentation](./STREAM_BUS_CLI.md)
 - [Benchmark Results](./BENCHMARK_RESULTS.md)
 
 ---

docs/HTTP_API_CURRENT.md

@@ -39,6 +39,17 @@ Service Unavailable` with:
 }
 ```
 
+### Ops Status
+
+`GET /ops/status`
+
+Returns a richer operational snapshot with:
+
+- overall service status
+- storage background-flush health
+- replay metrics
+- query lifecycle counts
+
 ### Register Query
 
 `POST /api/queries`

docs/LIVE_STREAMING_GUIDE.md

@@ -50,9 +50,9 @@ docker-compose up -d mosquitto
 ./scripts/start_http_server.sh --clean
 ```
 
-### 3. Open Demo Client
+### 3. Start a Client
 
-Open `examples/demo_dashboard.html` in your browser.
+Use the maintained dashboard repository or run the local HTTP client example.
 
 ### 4. Start Replay (Publishes to MQTT + Storage)
 

docs/QUICKSTART_HTTP_API.md

@@ -12,6 +12,7 @@ cargo run --bin http_server
 
 ```bash
 curl http://localhost:8080/health
+curl http://localhost:8080/ops/status
 ```
 
 ## 3. Register a query
@@ -65,14 +66,7 @@ Check replay metrics:
 curl http://localhost:8080/api/replay/status
 ```
 
-## Optional Demo Client
-
-This repository still contains a static demo HTML client for manual API
-testing:
-
-```bash
-open examples/demo_dashboard.html
-```
+## Optional Frontend
 
 For the maintained frontend, use: