chore: add graph explorer make target

Makefile

@@ -0,0 +1,21 @@
+PYTHON ?= python3
+REGISTRY_DB ?= .railiance-fabric/registry.sqlite3
+HOST ?= 127.0.0.1
+PORT ?= 8765
+
+.DEFAULT_GOAL := help
+
+.PHONY: help graph-explorer registry
+
+help:
+	@printf "Available targets:\n"
+	@printf "  make graph-explorer  Start the registry-backed graph explorer on HOST:PORT.\n"
+	@printf "                       Defaults: HOST=$(HOST), PORT=$(PORT), REGISTRY_DB=$(REGISTRY_DB)\n"
+	@printf "  make registry        Alias for graph-explorer.\n"
+
+graph-explorer:
+	@mkdir -p $(dir $(REGISTRY_DB))
+	@echo "Starting Railiance Fabric graph explorer at http://$(HOST):$(PORT)/ui/graph-explorer"
+	$(PYTHON) -m railiance_fabric.server --db "$(REGISTRY_DB)" --host "$(HOST)" --port "$(PORT)"
+
+registry: graph-explorer

README.md

@@ -81,7 +81,22 @@ See `docs/ecosystem-registry-service.md` for the standards comparison and
 service direction for registering repos and interacting with the combined
 ecosystem model. See `docs/registry-api.md` for the current registry HTTP API.
 
-Start the first registry service slice with:
+List available Make targets from the repo root:
+
+```bash
+make
+```
+
+Start the first registry service slice and graph explorer explicitly:
+
+```bash
+make graph-explorer
+```
+
+The target serves `http://127.0.0.1:8765/ui/graph-explorer` by default. Override
+`PORT`, `HOST`, or `REGISTRY_DB` if the local port or database path differs.
+
+Equivalent raw command:
 
 ```bash
 railiance-fabric-registry --db .railiance-fabric/registry.sqlite3 --port 8765

docs/graph-explorer-operations.md

@@ -6,18 +6,38 @@ verified, and how to extract the shared engine once the second adapter is ready.
 
 ## Launch
 
-Start the registry against the local SQLite database:
+List available Make targets from the repo root:
 
 ```bash
-railiance-fabric-registry --db .railiance-fabric/registry.sqlite3 --port 8765
+make
 ```
 
-Open the map:
+Start the registry-backed graph explorer explicitly:
+
+```bash
+make graph-explorer
+```
+
+This serves the graph explorer at:
 
 ```text
 http://127.0.0.1:8765/ui/graph-explorer
 ```
 
+The target defaults to `.railiance-fabric/registry.sqlite3`, host
+`127.0.0.1`, and port `8765`. Override those when needed:
+
+```bash
+make graph-explorer PORT=8876
+make graph-explorer HOST=0.0.0.0 PORT=8765 REGISTRY_DB=/tmp/railiance-fabric.sqlite3
+```
+
+Equivalent raw command:
+
+```bash
+railiance-fabric-registry --db .railiance-fabric/registry.sqlite3 --port 8765
+```
+
 Useful supporting endpoints:
 
 ```text

workplans/ADHOC-2026-06-03.md

@@ -0,0 +1,44 @@
+---
+id: ADHOC-2026-06-03
+type: workplan
+title: "Ad Hoc Fixes 2026-06-03"
+domain: railiance
+repo: railiance-fabric
+status: finished
+owner: codex
+topic_slug: railiance
+created: "2026-06-03"
+updated: "2026-06-03"
+---
+
+# ADHOC-2026-06-03 - Ad Hoc Fixes
+
+## Add Graph Explorer Make Target
+
+```task
+id: ADHOC-2026-06-03-T01
+status: done
+priority: medium
+```
+
+The graph explorer is served by the registry HTTP service, but starting it
+currently requires remembering the full registry command and database path.
+
+Add a Makefile target that starts the registry-backed graph explorer from the
+repo root with defaults for the local database, host, and port. Calling `make`
+without an explicit target should list available targets rather than start a
+long-running service. Document the target and available overrides.
+
+Result: Added `make graph-explorer`, with `registry` as an alias, defaulting to
+`.railiance-fabric/registry.sqlite3`, `127.0.0.1`, and port `8765`. Plain
+`make` now prints the available targets instead of starting the service. The
+target uses `python3 -m railiance_fabric.server`, so it works from the checkout
+without requiring an installed console script. Updated the README and graph
+explorer operations guide with the target and override examples.
+
+Verification:
+
+- Confirmed plain `make` lists available targets.
+- Started `make graph-explorer PORT=9877 REGISTRY_DB=/tmp/railiance-fabric-make-test.sqlite3`.
+- Confirmed `GET http://127.0.0.1:9877/status` returned `status: ok`.
+- Stopped the temporary verification server on port `9877`.